After assembling CICSOPTS and IDMSINTC in JOB03, these modules were added to the CUSTOM.loadlib. This loadlib was then added to the CICS region concatenation. When bringing up CICS, it failed with abend ESV1.
The IDMS Messages and Codes Guide Volume 1 contains this abend message and provides the following:
CICS/VSAMT no z/OS VSAMT subsystem installed. Run ESVSSBLD.
A CICS/VSAMT interface was started but there is no z/OS subsystem installed. Run ESVSSBLD to install the z/OS VSAMT subsystem.
Typically, this abend occurs when VTAM Transparency is installed, but the program ESVSSBLD has not been executed to install the z/OS VSAMT subsystem. Details on the IDMS VTAM Transparency install are in the IDMS VSAM Transparency User Guide, Appendix B CA IDMS VSAM Transparency Installation.
If IDMS VSAM Transparancy is not installed or should not be installed; then ensure the Product Intent Module (RHDCPINT) does not contain the #DEFPINT macro for VSAM Transparency.
Do that by commenting out the entry:
* #DEFPINT VSAM/T CA IDMS VSAM TRANSPARENCY
Reassemble and relink RHDCPINT and also CICSOPTS and IDMSINTC. Change the CICSOPTS source to ESCVSAM=NO.
Reassemble and link CICSOPTS and IDMSINTC.
Also ensure that the CICS region has the correct steplib concentration, in that the CUSTOM.LOADLIB is first, followed by the 18.5 CAGJLOAD loadlib.
CA IDMS Installation and Maintenance Guide, Chapter 5: Starting Your Product, Customized Source
CA IDMS VSAM Transparency VSAM Transparency User Guide, Appendix B, CA IDMS VSAM Transparency Installation, z/OS Installation