Providing SOLVE:Operations dump information

Products

• SOLVE
• SOLVE:Operations Automation

Issue/Introduction

On occasion there are some SOLVE:Operations problems that may require more in-depth diagnosis. A running

SOLVE:Operations region may contain the clues that can assist Broadcom Technical Support

to determine the cause of the problem.

Resolution

Technical Support may ask for a DUMP of a running SOLVE:Operations region.

A DUMP of SOLVE:Operations can provide a wealth of information, but only if the DUMP provided was done properly.

Here are some tips for providing a SOLVE:Operations DUMP that contains information required by Broadcom Technical Support personnel.

• Ensure that the JCL parameter XOPT=( option [, option [,...) includes the SDUMP option. The SVCDUMP can be found

         on SYS1.DUMP or equivalent. The JCL parameters can be found in the RUNSYSIN 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 SOLVE:Operations region:

         DUMP COMM=(Dump of SOLVE)

 

         R nn,JOBNAME=jobname,

 

         SDATA=(CSA,PSA,RGN,TRT,LPA,SQA,LSQA,SUM),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 it.
• Send results of (=CMD) command $$SYSPRO.
• Use the IBM TRSMAIN terse utility 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.

• For FTP information please see Case FTP Help Document.

 

Additional Information

This information also applies to an abnormal termination of SOLVE:Operations. During an abnormal termination, you should also

send the SOLVE:Operations formatted dump along with all the other data.