SYSPLEX
With SYSPLEX, you select the data that is used in generating Analyzer reports. Data selection is based on SYSNAME or SYSID, and on DDNAME.
[RPTS={COMBINED|SEPARATE}]
[,SUBPLEX={(*|sysname1[,...,sysnamen])}]
[,TYPE={SYSID|SYSNAME}]
[,XDSDATE={SMF|RMF}]
[,INPUT={(dd1[,...,ddn])}]
[,LSNAME=logstream_name]
[,SIDMAP=(sysid1:sysname1,sysid2:sysname2,...sysid128:sysname128)]
Parameters
The parameters for the SYSPLEX control statement are as follows:
RPTS= | specifies whether the data collected is combined into one report per group of SYSNAMEs or is divided into separate reports for each SYSNAME; the default is SEPARATE |
---|---|
SUBPLEX= | specifies a list of SYSNAMEs that are used in selecting records for reporting You can specify up to 128 SYSNAMEs. The default is SUBPLEX=*, which specifies that records from all SYSNAMEs or SYSIDs (depending on what you specify in the TYPE parameter) found in the input data are accepted. |
TYPE= | specifies whether the names used in the SUBPLEX parameter are SYSNAMEs or SYSIDs; the default is SYSNAME |
XDSDATE= | specifies the type of SMF record date/time filtering that is used when Analyzer uses XDS as the input source XDSDATE=SMF, the default, filters SMF records according to the date and time the record was written (that is, the time that SMF processing moved the record into its buffers). XDSDATE=RMF filters SMF records according to the interval time that appears in the product section of the SMF record. XDSDATE=RMF is valid only for SMF record types 70-78 and 240. Product sections do not appear in SMF record types 42-6, 103, and 108; therefore, those record types cannot be retrieved when XDSDATE=RMF has been specified. In both cases, when Analyzer uses XDS as the input source, SMF records are filtered according to any time range specified in the DATETIME Analyzer control statement (see DATETIME). You can specify the XDSDATE= parameter only in the first SYSPLEX control statement. If the parameter appears in any other SYSPLEX control statement, the parameter is ignored. |
INPUT= | specifies a list of DDNAMEs that define data sets that contain the input to the Analyzer You can specify up to 128 DDNAMEs, the data sets of which are read in the order in which they are specified. The default is EXTDATA. |
LSNAME= | specifies the name of the logstream from which the SMF records are read. Because a logstream can contain several days of data, consider using the DATETIME control statement (see DATETIME) to specify the desired time frame and thus reduce the execution time of the Analyzer batch job. |
SIDMAP= | (optional) specifies a list of SMF SYSIDs and corresponding SYSNAMEs to which the SYSIDs can be converted In the parameter, a colon separates each SYSID from its respective SYSNAME, and a comma separates each SYSID:SYSNAME set. A list of up to 128 SYSID:SYSNAME pairs can be specified, with the list enclosed in parentheses. Non-RMF/non-CMF records that are processed by CMF MONITOR Analyzer, such as SMF 42-6, 103 and 108 records, do not contain a SYSNAME field. Thus, when one of these records is encountered in the input data set and a SYSNAME is needed by Analyzer, the SYSID from the record is assumed to be the same as the SYSNAME. However, some installations use SYSIDs that are different from their SYSNAMEs, and assuming a SYSID is a SYSNAME causes problems creating the desired reports. When the SIDMAP parameter is specified, Analyzer attempts to match the SYSID in the SMF record to a SYSID in the SIDMAP parameter. If a match is found, the corresponding SYSNAME is substituted. The SYSIDs are processed left to right as coded. If a match is not found, the SYSID is used as the SYSNAME. The SYSID values are from one to four characters, and the SYSNAME values are from one to eight characters. The SYSID values can contain an asterisk as the last character of the value, effecting a begins with comparison. The SYSID value of a single asterisk effects an all others specification. If specified, it must be the very last SYSID:SYSNAME pair of the parameter. |
Examples
The following examples illustrate the use of the SYSPLEX control statement.
Related topics