After I initialize the CA SymDump Batch runtime, I run demo($Z91DEMO) and the CAIPRINT dump is not produced and captured. How do I correct this?
Article ID: 43741
Updated On:
Products
Issue/Introduction
Symptoms:
The CA SymDump Batch demo($Z91DEMO) abends with S0C7 as designed but CAIPRINT and repository dumps were not created as per parameter PRTREPT=BOTH.
The CA SymDump Batch's LE exit(CAOECEEX) was configured and the HLQ.CARXPROC(CAILPAQ) utility shows the runtime modules are initialized in the LPA and all modules are correct.
Also ran $Z91DEMO with CEEOPTS DD to override TRAP(ON) to TRAP(OFF) and the dump was still not captured by CA SymDump Batch(CAIPRINT).
Environment:
Z/OS
Cause:
The HLQ.CARXPROC(CAILPAQ) shows the CA SymDump Batch programs are in storage but CAOEPROL is not hooked into SVC 51.
During the first initialization, our attempt to place the address of CAOEPROL into the SVC table failed due to HLQ.CARXLOAD was not APF authorized.
From the standpoint of our initialization routine, if CAOESQAT is loaded the product is initialized.
Once the product is initialized, the CAIRIM does not reload CAOEPROL and does not place its address in the SVC table even after CAIRIM was reinitialized.
This is done to prevent the CA SymDump Batch from double hooking SVC 51 which would cause the system to go into a loop.
Resolution:
This problem requires an IPL of the affected LPAR to remove the existing CA SymDump batch modules from the system storage.
Make sure HLQ.CARXLOAD is APF authorized and initialize CA SymDump batch using the CAIRIM utility as outlined in the installation guide.
Additional Information:
The CA SymDump Batch install guide. Install CA Common Services section.
Environment
Component:
Feedback
