Running the following Rexx, to schedule an OPS/REXX EXEC to run asynchronously in an OSF TSO server address space :
txt = '220.127.116.11:4567 2 |',
FQ' | ZN | ZOS |',
'OPSMAIN | Z-SW-TDS-IMS_ALERTS | 'EC' |',
'AUTO_IMS-CZY117A | EVENTMGT-EMAIL |',
'EAXI701E IMS CZY117A DFS3127I READ ERROR OCCURRED',
'ON THE RESTART DATA SET WIBBLE WOBBLE WABBLE 11:27'
Address 'OSF' 'OI rexxpgm' txt
it can happen that the argument txt is getting truncated at 244 characters:
OPS3724T TSO WTO1 Sent CMD=OI EAXHPMSG 18.104.22.168:4567 2 | 2020-05-22T11.27.3302.00 | RUPLX1E-RV00.DE.EDS.COM | Z
OPS3726T N | ZOS | OPSMAIN | Z-SW-TDS-IMS_ALERTS | RUPLX1E | AUTO_IMS-CZY117A | EVENTMGT-EMAIL | EAXI701E IMS CZY117A DFS3127
OPS3726T I READ ERROR OCCURRED ON THE RESTART DATA SET WIBB
Is there a Parm or an OSF setting that limits the amount of characters being parse'd to a rexx ? How to solve this issue?
Component : OPS/MVS
The ADDRESS OSF 'OI...' arg instruction is executed in an OPSOSF Server address space.
If the //SYSTSIN DD of the OPSOSF proc used, looks like the following:
//SYSTSIN DD SUBSYS=&SSID,DISP=SHR,DSN=PDEIX.CAO.&SYSNAME..OSFIN,
then the BLKSIZE value can limit/truncate the argument parm passed to the rexxpgm.
In order to correct the situation, the following definition should be used :
//SYSTSIN DD SUBSYS=&SSID,DISP=SHR,DSN=SYS2.OPS.ST02.OSFIN,