SMF SYSLIST and SYSLISTACTION Statements
The SYSLIST statement allows you to restrict the systems processed by the DAY030 step, at the analyzer level. By default, unit-level and complex-level parameters, such as prefix.MICS.PARMS(SYSID), control the systems (ORGSYSIDs) that are processed.
rm
For example, if prefix.MICS.PARMS(SYSID) contains entries for five ORGSYSIDs, SYS1 to SYS5, then all
MICS
components in the daily update run can accept data from SYS1 to SYS5. You can use the SYSLIST statement to instruct the daily update DAY030 step for the Batch and Operations Analyzer to only accept data from SYS1 and SYS2.The SYSLIST statement, if coded, must be accompanied by a SYSLISTACTION statement. The SYSLISTACTION statement instructs the analyzer on how to deal with data from unlisted systems. The format and rules associated with the coding of these two statements are described below:
SYSLIST statement
The SYSLIST statement has the following format:
SYSLIST sys1 sys2 ... sysn
Default
none
where
sys1 sys2 ... sysn
is the list of systems (ORGSYSID) that will be accepted by the analyzer. Each sysn must be 4 characters or less. Separate each sysn (ORGSYSID) by one or more spaces. See Computing System Parameters (SYSID).
Use as many SYSLIST statements as required to list the systems to be processed. Each SYSLIST statement must begin with the keyword SYSLIST.
SYSLISTACTION statement
The SYSLISTACTION statement has the following format:
SYSLISTACTION action
Default
none
where
action
must be either ABORT or REJECT.
ABORT instructs the analyzer to force an abend when the DAY030 step encounters SMF data from non-listed systems.
REJECT instructs the analyzer to continue processing, but ignore data from unlisted systems.
The Batch and Operations Analyzer only processes certain SMF record types. The SYSLISTACTION action is only invoked for SMF record types used by the analyzer. Other controls recognize and reject unwanted record types earlier in the SMF record processing logic.
Note:
If you use a SYSLIST statement and you code explicit OPTIONS statements for each ORGSYSID in the list, you do not need to code generic OPTIONS ???? statements.+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: SMF Processing Options | | | | PARMS Library Member is SMFOPS | | | +--------------------------------------------------------------------------+ | | | | | SYSLIST sys1 sys2 ... sysn | | | | | | SYSLIST ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ | | | | | | SYSLISTACTION action | | | | | | SYSLISTACTION _________ | | | | | | | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+