Use of ALTLIB in CA OPS/MVS Event Management and Automation
Article ID: 93114
Updated On:
Products
OPS/MVS Event Management & Automation
Issue/Introduction
We tried to adapt OPSVLBDF (ISPF interface) from CCLXSMP by adding ALTLIB commands like this to avoid allocating CCLXCLS0 and CCLXEXEC in the TSO LOGON procedure:
When we use ISPF interface, we get, for example, the message "Cannot find program ASOTEAPI in SYSEXEC " on option 2.6 (Table Edit).
Is it possible to allocate OPS/MVS datasets using ALTLIB EXEC/CLIST instead of allocating them in the TSO logon procedure ?
"ALTLIB ACTIVATE APPLICATION(CLIST) DA('"prefix".CCLXCLS0'" ,")"
"ALTLIB ACTIVATE APPLICATION(EXEC) DA('"prefix".CCLXEXEC.VB259')"
"ALTLIB ACTIVATE APPLICATION(EXEC) DA('"prefix".CCLXEXEC.VB259')"
When we use ISPF interface, we get, for example, the message "Cannot find program ASOTEAPI in SYSEXEC " on option 2.6 (Table Edit).
Is it possible to allocate OPS/MVS datasets using ALTLIB EXEC/CLIST instead of allocating them in the TSO logon procedure ?
Environment
CA OPS/MVS Event Management and Automation release 13.0
z/OS
z/OS
Resolution
No, it is not possible to use ALTLIB for execs for OPS/Rexx programs. We do not support ALTLIB for the SYSEXEC allocation.
Feedback
Yes
No
Powered by
