To resolve the problem add the CUSTOM.LOADLIB to the CDMSLIB concatenation of the UCFTSO clist.
Many different configurations of TSO clist statements can be used to run UCFTSO, but the most common variety allocates a CDMSLIB ddname.
Prior to r18.0, the CDMSLIB defined to the UCFTSO clist contained the DBA.LOADLIB and the base software library now called CAGJLOAD.
As of r18.0, a new loadlib was introduced called CUSTOM.LOADLIB. Typically, it contains all modules which need to be customized and are site-specific. CUSTOM.LOADLIB is required by all batch jobs and UCFTSO.
If the UCFTSO clist allocates CDMSLIB, you will need to add CUSTOM.LOADLIB to it.
Some sites prefer not to use CUSTOM.LOADLIB and instead copy its contents into either DBA.LOADLIB or CAGJLOAD. If you do this, then no changes are needed to your UCFTSO clist.
Note also that it is not enough to have the CUSTOM.LOADLIB in the target CV’s CDMSLIB concatenation. It must also be present in the CDMSLIB defined to the clist.
If the UCFTSO clist does not allocate a CDMSLIB, then the CALL statement must reference a library which includes all of the modules referenced collectively in the CDMSLIB.
Sample clist changes required:
FREE FI(CDMSLIB SYSCTL)
CONTROL LIST MSG
ALLOC F(SYSCTL) DA('your.idms.SYSCTL') SHR
ALLOC F(CDMSLIB) DA('your.idms.DBA.LOADLIB', -
FREE F(SYSCTL CDMSLIB)
A sample UCFTSO clist can be found in the install library member *.CUSTOM.SRCLIB(UCFTSO).