Report Command Reference - SYSPARMS command

SYSPARMS command

This section provides an overview of the SYSPARMS command.

Usage

Use the SYSPARMS command to generate System Parameter reports. This command replaces the SYSPRMDD card. You can still use the SYSPRMDD in existing jobs, but not concurrently with the SYSPARMS command.

Usage notes

With the SYSPARMS command, you can use the FILE subcommand to store system parameter information in FILE data sets, which can be loaded into the OMEGAMON® XE for DB2® PE Performance Database.
With the exception of the INCLUDE and EXCLUDE subcommand options with GROUP and MEMBER, the GLOBAL command does not affect the System Parameters reports. For example, if FROM or TO is used to limit the record timestamps, System Parameters reports are generated even when the timestamps of the records are outside these times. When INCLUDE or EXCLUDE is used with LOCATION, GROUP, MEMBER, or SUBSYSTEMID, no System Parameters reports are generated for those locations, groups, members, or subsystems excluded by this process.
You can filter records with the GLOBAL command first. This can minimize your report output and reduce processing time. See GLOBAL command for more information.

Syntax of the SYSPARMS command

                                (1)
             .-TRACE subcommand------.
>>-SYSPARMS--+-----------------------+-------------------------><
             |                 (2)   |
             '-FILE subcommand-------'

Notes:

You can specify TRACE only once.
You can specify FILE only once.

Subcommands

The subcommands are described in detail, together with their various options, in the following sections.

Sample JCL for requesting SYSPARMS functions

The following is a sample of the JCL required to produce SYSPARMS reports and traces. See DD statements for descriptions of the DD statements.

Figure 10. Sample JCL for requesting SYSPARMS functions

//SYSPBTCH JOB ,MSGCLASS=X,CLASS=A,NOTIFY=USER1,REGION=0M    
//* --------------------------------------------------
//* BATCH SYSTEM PARAMETERS JCL.
//* --------------------------------------------------
//PEMAIN   EXEC PGM=FPECMAIN
//STEPLIB  DD  DSN=FPE.FPLIB.RKANMOD,DISP=SHR       
//* ----------------------------------------             
//INPUTDD  DD  DISP=SHR,DSN=DEA.DPMOUT.V8I106            
//SYSOUT   DD  SYSOUT=*                                  
//SYSPRINT DD  SYSOUT=*                                  
//DPMLOG   DD  SYSOUT=*                                  
//JOBSUMDD DD  SYSOUT=*                                  
//SYSUDUMP DD  SYSOUT=*                                  
//* FOLLOWING ARE REPORT AND FILE DD NAMES
//SYFILDD1 DD  SYSOUT=*           -> Used for FILE
//SYTRCDD1 DD  SYSOUT=*           -> Used for TRACE
//* ----------------------------------------             
//SYSIN    DD  *   
 SYSPARMS          
 TRACE              
 FILE             
 EXEC              
 /*

The OMEGAMON XE for DB2 PE command language shown in this section is not appropriate in all circumstances. You must modify it to meet your requirements.

Most of the DD statements with a SYSOUT destination do not have to be specified because they are dynamically allocated by OMEGAMON XE for DB2 PE. See the individual DD statement descriptions for more information.

Note:

There is a performance advantage in omitting DPMOUTDD from your JCL. For more information, see DPMOUTDD statement.
The OMEGAMON XE for DB2 PE command stream is only processed if EXEC is included as the last command. Otherwise, OMEGAMON XE for DB2 PE only checks the syntax.