CA Symdump CICS configuration build using CSM fails on the PROTSYM allocation step

Document ID : KB000047261
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary:

While attempting to use CSM to configure CA SymDump CICS, the configuration build fails.  It fails on step 20:

20. Add product DSECTs to PROTSYM

It fails with the error:

JES Messages: 

12.28.05 IPO1 STC11715 IKJ56228I DATA SET MT.CAI.SYMDUMP.R91AT.PROTSYM NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED

Messages:
MSMC0232E MSMCSDAD error - DSN=MT.CAI.SYMDUMP.R91AT.PROTSYM Volume=*NONE* DDname=PROTSYM Dynamic file allocation error
 
Instructions:
 
The SymDump CICS configuration does not define a PROTSYM file, it uses an existing one.

If you are an existing CA SymDump CICS user, you would have a PROTSYM file or several PROTSYMs laying around.  You need to exit the configuration, clone a PROTSYM to the new dataset name that is expected by the configuration, delete the output artifacts of the failed configuration, and re-run the configuration build.

If you are a new user, exit the configuration build to initialize an empty PROTSYM using IN25UTIL with the dataset name expected by the configuration, delete the output artifacts of the failed configuration, and re-run the configuration build.