Either of following error messages can occur when an OPS/REXX program is invoked:
OPS3092O RUNNING pgname LINE nn: COMPILER WORK SPACE OVERFLOW (1574640 1572864)
OPS0998O RUNNING pgname LINE nn: COMPILER WORK SPACE OVERFLOW (var1 var2)
Workspace size limits the maximum number of nested calls, symbols, and values that can be used during program execution. If your programs have large memory requirements, use the size value to specify a workspace that is larger than the default. The default size is 1.5 MB.
Use the following syntax when calling your OPS/REXX program:
If using OPSIMEX/OI:
ADDRESS OSF "OI PROGRAM(pgmname) WS(5000000)"
If using OPSEXEC/OX:
ADDRESS OSF "OX PROGRAM('library(pgmname)') WS(5000000)"
In the above examples the value of 5000000 (5Mbytes) is just an example.
Note: the keyword PROGRAM is required when allocating a bigger work space.
For additional information please see the following sections of the OPS/MVS manual for the appropriate release:
OPSEXEC Command Processor in the Command and Function Reference of the OPS/MVS Reference Information manual.
OPSIMEX Command Processor in the Command and Function Reference of the OPS/MVS Reference Information manual.
For release 14.0 the links are as follows:
https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/reference-information/command-and-function-reference/poi-command-processors/opsexec-command-processor-run-a-specified-program.html
https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/reference-information/command-and-function-reference/poi-command-processors/opsimex-command-processor-executes-a-member-as-a-rexx-program.html