On occasion there are some Unicenter SOLVE:Operations problems that may require more in-depth diagnosis. A running Unicenter SOLVE:Operations region may contain the clues that can assist Technical Support to determine the cause of the problem. To that end, Technical Support may ask for a DUMP of a running Unicenter SOLVE:Operations region. A DUMP of Unicenter SOLVE:Operations can provide a wealth of information but only if the DUMP provided was done properly.
Here are some tips for providing a Unicenter SOLVE:Operations DUMP that contains everything required by Technical Support personnel.
- Ensure that the Unicenter SOLVE:Operations JCL parameter XOPT=( option [, option [,...) includes the SDUMP option. The SVCDUMP can be found on SYS1. DUMP or equivalence. The JCL parameters can be found in the RUNJCLIN member.
- Ensure that the SDATA parameters for SDUMP contain the following options (CSA,LPA,LSQA,PSA,RGN,SQA,SUM,TRT).
- Issue the following command to dump a Unicenter SOLVE:Operations region.
DUMP COMM=(Dump of Unicenter SOLVE:Operations) R nn,JOBNAME= jobname, SDATA=(CSA,LPA,LSQA,PSA,RGN,SQA,SUM,TRT),END
- Preferably, block the dump DSN at LRECL 4160, BLKSIZE 24960.
- If possible, keep all the logs since the system was started, and send all logs. The latest Activity Log will provide a history of events.
- Also send the JES system log just in case we need to check.
- Send results of $$SYSPRO.
- Use the IBM utility TERSE to reduce the sizes of the dumps, activity logs, and other information gathered. It will also remember the original DCB so that the correct format is used when untersed.
- FTP to FTPU.CA.COM.
Note: This information also applies to an abnormal termination of Unicenter SOLVE:Operations. During an abnormal termination, you should also send the Unicenter SOLVE:Operations formatted dump along with all the other data.