I have been requested to obtain a SYSMDUMP by CA Support. This request is being ignored by CA LDAP server because I have a SYSUDUMP or SYSABEND DD in my JCL.

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

Summary:

To be able to produce a SYSMDUMP as well as any other dump format that you have specified in your CA LDAP SERVER procedure, you will need to change the _CEE_RUNOPTS options in the slapd.env file (this file can be found in the CA LDAP install directory).

Instructions:

If CA Support requests a SYSMDUMP be produced by CA LDAP Server and you have a SYSUDUMP or SYSABEND DD in the CA LDAP startup jcl, you will not get the SYSMDUMP unless you change the _CEE_RUNOPTS parameters in the slapd.env file (which can be found in the CA LDAP runtime directory).

The supplied _CEE_RUNOPTS currently contains:

_CEE_RUNOPTS=all31(on),heappools(on,16,20,32,20,80,20,2048,20),stack(16K,16K,ANY,FREE,52K,160K),threadstack(on,32k,32k,anywhere,free),heap(1m,128k,anywhere,free,8k,4k),
anyheap(5m,128k,anywhere,free),belowheap(32k,1k,free),rptopts(on),rptstg(on),termthdact(uaimm),trap(on,nospie),dyndump(*userid,dynamic,tdump),trace(on,,nodump)

To be able to get multiple dumps including the required SYSMDUMP, change the _CEE_RUNOPTS to:

_CEE_RUNOPTS=all31(on),heappools(on,16,20,32,20,80,20,2048,20),stack(16K,16K,ANY,FREE,52K,160K),threadstack(on,32k,32k,anywhere,free),heap(1m,128k,anywhere,free,8k,4k),
anyheap(5m,128k,anywhere,free),belowheap(32k,1k,free),rptopts(on),rptstg(on),termthdact(uaimm),trap(on,nospie),dyndump(*userid,both,tdump),trace(on,,nodump)

Then you will receive whatever dump you have requested via your DD statements AND a SYSMDUMP will be produced.

Alternatively you can change your LDAP STC procedure to remove any SYSUDUMP or SYSABEND DD statements and the original _CEE_RUNOPTS will allow the SYSMDUMP to be taken.