Diagnostic reports

Overview

The STC or batch job can write a diagnostic report, which contains system-related environment information on the started task or batch job. The diagnostic report is written to DD BSADIAG, which is allocated dynamically as necessary. The writing of BSADIAG can be initiated using the following alternative methods:

  • Service Manager option R.n
  • Operator console command
  • LST parameter DIAG=

Service Manager options

You can use the BSA Service Manager online options to create a diagnostic report (DD BSADIAG):

  • Use option R.1 to obtain BSADIAG via a separate batch job
  • Use option R.2 if the STC itself is to allocate BSADIAG

The fields of the panels displayed under Service Manager options R.1 and R.2 correspond to the parameters of the DIAG parameter and MODIFY command described below. For more information, see BSA Service Manager Manual.

Operator console command

The following MODIFY command initiates the writing of a diagnostic report to DD BSADIAG:

F stcname,DIAG[=ocl[#FREE|HOLD[#dcl[#DUMP|FDMP|NDMP[#chd]]]]]

where:

stcname

is the name of the started task.

ocl

is the output class to be used for DD BSADIAG. If * is coded, the message class of the batch job or STC is used.

FREE|HOLD

Specify FREE to control whether BSADIAG is to be released immediately, or HOLD to hold output until the batch job or STC terminates or until manual release. HOLD is the default.

dcl

is the output class to be used to the dump. If * is coded, the message class of the batch job or STC is used.

DUMP|FDMP|NDMP

Specify one of the following:

DUMP

causes the writing of a diagnostic dump; BSADIAGA/ BSADIAGD remains allocated until manual release or termination of the batch job or STC

FDMP

causes the writing of a diagnostic dump; BSADIAGA/ BSADIAGD is released after writing

NDMP

no dump

chd

is the problem number (if available) for which you are providing information. This number will be included in the diagnostic report.

# is used as separator between parameters. All parameters are optional, but if a parameter is coded, values for all preceding parameters must be coded as well.

Examples

F stcname,DIAG

F stcname,DIAG=*#HOLD

F stcname,DIAG=*#HOLD#*#NDMP#123-R123-1234

LST parameter DIAG=

The LST parameter DIAG= can be coded in the LST member or in the EXEC parameter of the JCL (recommended). It is mainly intended for use with batch jobs, but it can also be used for STCs as an alternative to the console command or the corresponding Service Manager options. The syntax of the LST parameter DIAG corresponds to the syntax of the MODIFY command:

DIAG=ocl[#FREE|HOLD[#dcl[#DUMP|FDMP|NDMP[#chd]]]]

Example

Following is an example where the LST parameter DIAG has been coded in the EXEC parameter of the Beta 93 archive batch utility. The diagnostic report is written after all function groups have been loaded. DD BSADIAG is allocated dynamically using the message class of the batch job.

+----------------------------------------------------------------------+
|jobcard |
|//B93DEARC EXEC PGM=BST01RFF,REGION=0M,PARM=('S=93', |
|// 'PGM=B93ARC', |
|// 'B01LST=00', |
|// 'B93LST=00', |
|// 'DIAG=*#HOLD#*#NDMP#123-R123-1234', |
|// 'SIGNON=YES') |
|//... |
+----------------------------------------------------------------------+

BSADIAG

The diagnostic report written to DD BSADIAG contains the following (amount of information varies depending on the object of the diagnostic report):

  • SFF SVC/EXIT information
  • LST parameters used
  • System symbol table
  • Subsystem interface control area (SICA)
  • Subsystem control table (SSCT)
  • Subsystem control area (SSCA)
  • Subsystem routine vector table (SSVT)
  • Overview of all Beta subsystems defined to z/OS (including information on OCF and XCF connections)
  • SFF transaction list
  • Program module information (Steplib and Linklist)
  • SMP/E package information (status of all packages; if status is MISMATCH or CHANGED, also package contents (load modules only))