Collecting data about CSL-related problems

The Common Service Layer address spaces, Open Database Manager (ODBM), Operations Manager, Structured Call Interface, and Resource Manager, produce SDUMPs for internal errors. The CSL dumps are in the SYS1.DUMP data sets.

You might need to collect one or more of the following types of information to diagnose CSL related problems:

SYSLOG

To determine the sequence of events, collect the SYSLOG from every logical partition (LPAR) where a CSL member resides. CSL address spaces issue messages that begin with CSL

  • ODBM messages - CSLDxxxx
  • OM messages - CSLOxxxx
  • RM messages - CSLRxxxx
  • SCI messages - CSLSxxxx
  • CSL common messages - CSLZxxxx

QUERY IMSPLEX SHOW(ALL) command output

Issue the QUERY IMSPLEX command to display the members of the IMSplex and their status.

If there are problems accessing OM or RM services, verify that at least one OM or RM is active in the IMSplex and that an active SCI resides on every LPAR where a CSL address space resides.

Obtain z/OS® SVC dumps

Obtain a z/OS SVC dump of the CSL address spaces that appear to have a problem, are waiting, or are looping. CSL dumps contain the CSL traces, which can be very useful for diagnosing CSL related problems. Dump all of the CSL address spaces that appear to have a problem with the following series of commands: 
DUMP COMM=(dump title)
R id JOBNAME=(odbm1,om1,rm1,sci1)
SDATA=(CSA,PSA,RGN,SQA,SUM,TRT),END
In the previous example:
odbm1
An ODBM address space.
om1
An OM address space.
rm1
An RM address space.
sci1
An SCI address space.

For some CSL problems, IBM® Software Support might request additional trace level settings for the various trace types.