APPLCONTROL

Syntax

To control the processing of CICS applications input data:

To control the processing of Db2 applications input data:

To control the processing of IMS applications input data:

To control the processing of MQ applications input data:

To control the processing of WAS applications input data:

Syntax explanations

• The SUBSYSTYPE subparameter is a required value and indicates the subsystem type for this APPLCONTROL command. This can have the values: CICS, Db2, IMS, MQ, WAS.

• SID and SUBSYS are comma separated lists of System IDs or patterns and Subsystem IDs or patterns, respectively. Subsystem ID applies to Db2, IMS, and MQ.

  Important

  SID, SUBSYS, CICSREGION, CONNAME, IMSREGION, CICSJOB, SERVER, PRIMEVAL and SECONDVAL accept a list of values or patterns, as follows:

  A pattern can be a combination of the wildcard character *, the wild character ?, and standard EBCDIC characters. An * denotes 0 or more characters preceding and/or following a character string. A ? denotes that any character can appear in this position within the string. The pattern cannot exceed the field length of the element. A maximum of three * are allowed per pattern.

  Some valid patterns for an 8-byte element can be:

  AB*
  *AB
  *AB*
  *A*B
  *A*B*
  ????????
  ??*ABC
  *A??B*

  • The absence of SID means that this command applies to all SIDs.
  • The absence of SUBSYS means that this command applies to all SUBSYS IDs.
• The CICSREGION subparameter specifies a comma separated list of CICS regions for this APPLCONTROL command.
• The DBCTLJOB subparameter specifies the job name of the IMS DBCTL control region for this APPLCONTROL command. The IMS subsystem name should also be specified on the same APPLCONTROL command.
• The SERVER subparameter specifies a comma separated list of WAS servers for this APPLCONTROL command.
• The IMSMATCH subparameter can be specified with a SUBSYSTYPE of Db2 or MQ and indicates whether Db2 or MQ data should be matched to IMS data. You can also specify this subparameter with a SUBSYSTYPE of IMS to indicate that IMS data is not present in the input data.
• The CICSMATCH subparameter can be specified with a SUBSYSTYPE of Db2, IMS, or MQ and indicates whether Db2, IMS, or MQ data should be matched to CICS data.
• The PACKAGE subparameter indicates whether to produce a Db2 transaction record for each package or DBRM found in the Db2 SMF record.
• The AGGBATCH subparameter indicates whether to aggregate all batch jobs calling Db2 or MQ into a single caller subsystem called DB2BATCH for Db2 and MQBATCH for MQ. The default value is YES. Specifying NO can result in a large number of rows being inserted into Visualizer tables because each batch job calling Db2 or MQ is treated as a separate caller.
• The AGGTSO subparameter indicates whether to aggregate all TSO sessions calling Db2 or MQ into a single caller called DB2TSO for Db2 and MQTSO for MQ. The default value is YES. Specifying NO can result in a large number of rows being inserted into Visualizer tables because each TSO user is treated as a separate caller.
• AGGREMOTE subparameter indicates whether to aggregate all Db2 or MQ REMOTE DDF into a single subsystem name.
  • YES means to aggregate all Db2 or MQ REMOTE DDF into a single subsystem name of DB2REMOT or MQREMOT for Visualizer reporting.
  • NO means use the UIE determined requestor as the subsystem requestor name.
  • The default is AGGREMOTE=YES for both Db2 and MQ.

• The MRO subparameter can be specified with a SUBSYSTYPE of CICS and indicates whether CICS MRO processing should be performed. MRO processing means that UIE can follow a CICS unit-of-work as it uses resources in different CICS regions. With MRO processing, UIE matches the unit-of-work ID for each CICS transaction and accumulates the total resources used by the unit-of-work. When applications are created from CICS transactions, UIE combines the resources used by the unit-of-work to report total application resource usage. With MRO=YES, you still see region utilization for each application in Visualizer. If MRO is not being used, or it is important to model the resource utilization by region, turn this subparameter off.

  Important

  If you specify MRO=NO in addition to turning off MRO processing, you also turn off CICS-Db2, CICS-IMS, and CICS-MQ processing. If you want to match CICS data to Db2, IMS, or MQ data, MRO=YES must be specified or implied by default UIE processing.

• The PROCESS subparameter indicates whether to process all records for the SUBSYSTYPE that match the SID and SUBSYS/CICSREGION/SERVER values.
• The USE110 subparameter indicates whether to process 110 data for the specified SID and CICSREGION values.
• The USEMVCICS subparameter indicates whether to process BMC AMI Ops Monitor for CICS data for the specified SID and CICSREGION values.
• The USETMON subparameter indicates whether to process TMON for CICS data for the specified SID and CICSREGION values.
• The USEIBMDB2 subparameter indicates whether to process IBM Db2 data for the specified SID and SUBSYS values.
• The USEMVDB2 subparameter indicates whether to process BMC AMI Ops Monitor for Db2 data for the specified SID and SUBSYS values.
• The USEMVIMS subparameter indicates whether to process BMC AMI Ops Monitor for IMS Offline data for the specified SID and SUBSYS values.
• The USEDCMON subparameter indicates whether to process DCMON for IMS applications.
• The USERFLDNAME subparameter identifies the name of the optional user field that was added to the CICS 110 record, if it was changed from the default name of USER.
• The DCMONDDN subparameter indicates the DDname in the JCL that points to the DCMON input data for the specified IMS subsystem.
• TOCCSID is a 1 to 5 digit Character Code Set Identifier that you use for UNICODE conversion. This is the target CCSID of the data. The default for all Subsystem types is 37. Currently, Db2 Version 8.1 supports UNICODE with UTF-8. If the SMF 101 IFCID 3 record indicates that data has been converted to UNICODE, the source CCSID is 1208. For WAS applications, double-byte coding is used. The source CCSID is 1200.
• TECHNIQUE is 1 to 8 characters as defined in the z/OS Support for Unicode: Using Conversion Services. Use the keyword NONE to specify a technique of all spaces. The default for all Subsystem types is ER. Currently Db2 Version 8.1 supports UNICODE with UTF-8 and a Technique of ER. WAS data uses double-byte coding. If ER is incorrect for your installation, refer to your WAS administrator.

Rules

• The SUBSYSTYPE subparameter is required.
• If you are using the PROCESS subparameter, always specify a SUBSYS. If you want to bypass all of the data for a given subsystem type, such as CICS or Db2, use the BYPASSREC command.
• Only one data source can be processed for any specified CICS region; that is, you cannot specify USE110 and USEMVCICS for the same CICS region.
• Only one data source can be processed for any specified Db2 subsystem; that is, you cannot specify USEIBMDB2 and USEMVDB2 for the same Db2 subsystem.
• Only one data source can be processed for any specified IMS subsystem; that is, you cannot specify USEMVIMS and USEDCMON for the same IMS subsystem.
• To process DCMON data, in addition to the USEDCMON subparameter, you must specify a single SID and SUBSYS value on the APPLCONTROL command. You must also specify the DCMONDDN subparameter and indicate the DDname for the DCMON data set that contains the DCMON data for the specified SID and IMS SUBSYS values.
• If you are inputting DCMON data for more than one IMS subsystem, you must specify a separate APPLCONTROL command for each IMS subsystem.

Examples

• You have an IMS test system called IMST, which does not collect BMC AMI Ops Monitor for IMS Offline data. This system is used to test subsystem DB2T and subsystem MQTT. By using the UIE defaults, each Db2 and MQ data record is written to a temporary file and sorted for matching to IMS. However, since BMC AMI Ops Monitor for IMS Offline records are not collected for IMST, there is no IMS data to match to for the Db2 and MQ records. Turning off the matching for the IMST subsystem reduces both the amount of temporary DASD space and the amount of processing time required by the UIE batch job. The syntax of the APPLCONTROL command would be:

  APPLCONTROL  SUBSYSTYPE=IMS
               SUBSYS=IMST
               IMSMATCH=NO

• CICS is executing on system SYSA and consists of CICS regions that do not perform MRO. By using the UIE default, each CICS data record is written to a temporary file and sorted for MRO processing. Turning off MRO processing reduces both the amount of temporary DASD space and the amount of processing time required by the UIE batch job. The syntax of the APPLCONTROL command would be:

  APPLCONTROL  SUBSYSTYPE=CICS
               SID=SYSA
               MRO=N

• You are collecting BMC AMI Ops Monitor for CICS data for system SYSA and the IBM 110 data for system SYSB. If you input the BMC AMI Ops Monitor for CICS data, by default, UIE will process only the BMC AMI Ops Monitor for CICS data and ignore all 110 data. To indicate to UIE that BMC AMI Ops Monitor for CICS data is present for only system SYSA, use the following APPLCONTROL command:

  APPLCONTROL SUBSYSTYPE=CICS
              SID=SYSA
              USEMVCICS=YES

  When UIE encounters this command, it will turn on processing of BMC AMI Ops Monitor for CICS data for system SYSA only and will, by default, process the 110 data for system SYSB.

• You are collecting BMC AMI Ops Monitor for Db2 data for system SYSA and the IBM 100/101 data for system SYSB. If you input the BMC AMI Ops Monitor for Db2 data, by default, UIE will process only the BMC AMI Ops Monitor for Db2 data and ignore all IBM 100/101 data. To indicate to UIE that BMC AMI Ops Monitor for Db2 data is present for only system SYSA and IBM 100/101 data is present for system SYSB, use the following APPLCONTROL commands:

  APPLCONTROL SUBSYSTYPE=DB2 SID=SYSA USEMVDB2=YES
  APPLCONTROL SUBSYSTYPE=DB2 SID=SYSB USEIBMDB2=YES

  When UIE encounters these commands, it will turn on processing of BMC AMI Ops Monitor for Db2 data for system SYSA only and will process the IBM 100/101 data for system SYSB.