How do I use the Multi-User Facility Startup Option called SYSOUT?

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

Description:

There is a Multi-User Facility (called MUF) Startup Option called SYSOUT that looks like it contains data that used to be in my PXX file in previous releases. How do I use this option?

Solution:

The SYSOUT MUF startup option allows you to specify new output processing for diagnostic and tracing information that would otherwise be routed to the Statistics and Diagnostics Area (PXX). Here is a description of this functionality from the CA Datacom/DB Database and System Administration Guide:

The Statistics and Diagnostics Area (PXX) output data set is used and reused by and for many categories of output, including the following:

  • Documentation of return code errors or a SNAP command with a Master List dump that optionally includes buffers (category code ML)
  • CBS diagnostic report as requested using CA Ideal, CA Dataquery, or DBUTLTY TRACE= requests for SQL (category code CBS)
  • SQL trace information requested using DBUTLTY TRACE= requests (category code SQL)
  • CA Datacom/DB Datadictionary trace information if requested by CA Support (category code DD)
  • Dynamic system tables trace information (category code DST)
  • Statistics
  • Other diagnostic or debugging information

This option has the following syntax:
SYSOUT class,mlparm,cbsparm,sqlparm,ddparm,dstparm


Subparameter Description

class

The Job Entry Subsystems (JES) class to which a dynamically allocated SYSOUT data set is assigned when closed/deallocated.
Note: The class that is specified with this parameter is expected to be a throw-away class.
Valid Entries: any single-character class recognized by JES (Job Entry Subsystems)
Default Value: (No default)

mlparm

Used for Master List snaps

cbsparm

Used for CBS traces

sqlparm

Used for SQL Traces

ddparm

Used for CA Datacom/DB Datadictionary traces

dstparm

Used for DST traces
  For all of the "parm" subparameters above, there are multiple choices that can be used. For example, specifying ML for one or more of the parameters except mlparm (see exceptions below) redirects that output to the same output as the
Master List snaps, PXXML. Or, if ML is specified for sqlparm, SQL output is
redirected to PXXML, and if CBS is specified for mlparm, Master List output
is redirected to PXXCBS, and so on (see Example). Note that there are some exceptions to the below options:
  • A SYSOUT cannot be redirected to another SYSOUT that is itself redirected.
  • A SYSOUT can be redirected to a SYSOUT parameter for which zero has been
    specified. In this case, both are written to the PXX.
  • A SYSOUT parameter cannot specify itself as a redirection. For example, ML
    is not valid as a value for mlparm.
Allowable
"parm" values:
0 A numeric zero (this is the default) specified for one or more of the parameters indicates no special SYSOUT is desired, that is, any output is written to the PXX.
  100K to 16M Specifying 100K through 16M for one or more of the parameters indicates that you want special SYSOUT to be allocated and used for any output instead of its being written to the PXX (see example following these descriptions).
  ML Specifies that output is to be redirected to the same output as the Master List snaps, PXXML (not valid for mlparm).
  CBS Specifies that output is to be redirected to the same output as the CBS traces, PXXCBS (not valid for cbsparm).
  SQL Specifies that output is to be redirected to the same output as the SQL traces, PXXSQL (not valid for sqlparm).
  DD Specifies that output is to be redirected to the same output as the CA Datacom/DB Datadictionary traces, PXXDD (not valid for ddparm).
  DST Specifies that output is to be redirected to the same output as the Dynamic System Tables traces, PXXDST (not valid for dstparm).


Here is an example. For easy reference, here again is the SYSOUT syntax:
SYSOUT class,mlparm,cbsparm,sqlparm,ddparm,dstparm

Referring to the SYSOUT syntax, consider this example:
SYSOUT X,2M,100K,1M,ML,100K
In the example, note that:


X In the class position, represents the expected throw-away class.
2M In the mlparm position, means that Master List snap output is to be directed to PXXML to a maximum output limit (outlim) of 2M lines.
100K In the cbsparm position, means that CBS traces are to be directed to PXXCBS to a maximum output limit (outlim) of 100K lines.
1M In the sqlparm position, means that SQL traces are to be directed to PXXSQL to a maximum output limit (outlim) of 1M lines.
ML In the ddparm position, means that CA Datacom/DB Datadictionary traces are to be redirected to the PXXML file with a combined maximum output limit (outlim) of 2M lines. If a reset command results in redirection, the following message is issued:
DB02403I-PXXaaa REDIRECTED TO PXXbbb
100K In the dstparm position, means that DST traces are to be directed to PXXDST to a maximum output limit (outlim) of 100K lines.


Note that it is possible to set the values for mlparm, etc. to 0 (zero), which will then force all output to the PXX, but this would require reallocating the PXX to a proper size, and then running a job to report and clear the PXX. Be aware, though, that we have had a number of cases where we could not review the PXX reports, because the PXX was filled before the problem occurred that we were trying to address.

For more information about the SYSOUT MUF Startup Option, please refer to the CA Datacom/DB Database and System Administration Guide, in the sections

" Using the Multi-User Facility › Modifying MUF Startup Options › SYSOUT " and
" Creating and Maintaining the Statistics and Diagnostics Area (PXX) › Reporting › SYSOUT Processing in z/OS "

As always, please contact CA Technologies support for CA Datacom if you have further questions.

File Attachments:
TEC614157.zip