APPLGROUPING

Syntax

To group CICS applications input data, use the following syntax:

To group IMS applications input data, use the following syntax:

To group Db2 or MQ applications input data, use the following syntax:

To group WAS applications input data, use the following syntax:

Syntax explanations

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

• SID and SUBSYS are comma separated lists of System IDs and Subsystem IDs, respectively.

  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_LIST means that this command applies to all SIDs.
  • The absence of SUBSYS_LIST means that this command applies to all SUBSYS IDs.
• The REGTYPE subparameter is used for IMS and indicates the region type for this APPLGROUPING command. This can have the values: IMSMPP, IMSBMP, DBC, FPU, or CPI.
• The CONNTYPE subparameter is used for Db2 and MQ and indicates the connection type for this APPLGROUPING command.
• The REGTYPE and CONNTYPE parameters do not apply to CICS.
• The CONTAINER subparameter indicates the WAS container type for this APPLGROUPING command. This can be J2EE for J2EE container, REQUEST for Server request data, or WEB for WebContainer data.

• The PRIMEKEY subparameter indicates the keyword value for the primary transaction grouping. This value is dependent on the SUBSYSTYPE value.

  For a list of possible transaction grouping values for each subsystype, see Defining-subsystem-transaction-groupings.

• The PRIMEDEF subparameter is optional and specifies the field name to be used if the PRIMEKEY value contains spaces in the data. The value used must be one of the field names listed for the SUBSYSTYPE. The field length of the PRIMEDEF element is 8 characters. Only 1 PRIMEDEF may be coded.

• The SECONDKEY subparameter indicates the keyword value for the secondary transaction grouping. A secondary grouping is optional. This value is dependent on the SUBSYSTYPE value and can be blank (for no secondary grouping).

  For a list of possible transaction grouping values for each subsystype, see Defining-subsystem-transaction-groupings.

• The SECONDDEF subparameter is optional and specifies the field name to be used if the SECONDKEY value contains spaces in the data. The value used must be one of the field names listed for the SUBSYSTYPE. The field length of the SECONDDEF element is 8 characters. Only 1 SECONDDEF may be coded.

• For the PRIMEKEY, PRIMEDEF, SECONDKEY, and SECONDEF values, you can optionally specify the offset where UIE should start collecting data, and the length of the data that should be collected (start:length). The default starting offset value is one and the default length value is the length of the grouping field or 16, whichever is the smallest. Use this optional field if you would like UIE to collect a subset of data or start collecting data at an offset other than position one. The syntax value for this field is x:y, where x is the starting offset and y is the length. A single value x (that is, (2)) can be specified if you only want to change the starting offset value. A single y preceded by a colon (that is, (:2)) can be specified if you only want to change the length value. For example, if your CICS transaction names contain a special two character code in the second and third character of the transaction name, you can specify the following command to collect just these two characters:

  APPLGROUPING SUBSYSTYPE=CICS PRIMEKEY=TRAN(2:2)

  From the transaction name field, UIE will only collect the two-character value starting at offset 2 and store this value in the primary grouping field.

Rules

• All subparameters in the APPLGROUPING command except SUBSYSTYPE and PRIMEKEY are optional.
• While reading the commands file, UIE analyzes the syntax of all commands and stores each APPLGROUPING command with its parameters sequentially in the same order that they are encountered in the command file. If more than one command refers to the same grouping values, the last one in the input stream is used.

• During subsystem processing, UIE analyzes each element of the data and tries to match it with the transaction grouping definitions. As soon as a particular data element matches a transaction grouping definition, the transaction grouping fields are collected from the data and UIE continues to analyze the next data element. For example, a command file contains the following commands:

  APPLGROUPING SUBSYSTYPE=CICS
               SID=SYSA
               PRIMEKEY=TRAN
               SECONDKEY=USERFLD
  
  APPLGROUPING SUBSYSTYPE=CICS
               SID=SYSB
               PRIMEKEY=TRAN
               SECONDKEY=USERID
  
  APPLGROUPING SUBSYSTYPE=DB2
               SUBSYS=DB2P
               CONNTYPE=TSO
               PRIMEKEY=CORR
               SECONDKEY=PLAN
• All CICS transactions on system SYSA are summarized based on the transaction ID and user field values. All CICS transactions on system SYSB are summarized based on the transaction ID and user ID field values. All CICS transactions on any other system use the default primary and secondary transaction grouping fields.
• All Db2 transactions on Db2 subsystem DB2P that have a connection type of TSO are summarized based on the values in the Correlation ID and the plan name fields. All other Db2 connection types use the default primary and secondary transaction grouping fields.

Examples

• All of the IMS systems have PSB and transaction names that relate to a business function. Payroll PSBs begin with PR, Human Resources begin with HR and inventory begins with IN. The transaction names correspond to the activity within the business unit. Therefore, logically we can group the IMS data by PSB name and transaction. The syntax of the APPLGROUPING command would be as follows:

  APPLGROUPING SUBSYSTYPE=IMS
               PRIMEKEY=PSB
               SECONDKEY=TRAN

• Db2 data is processed from CICS, IMS, and batch jobs. We have already combined all of the batch connection types into a type called BATCH (see the examples in COMBINE). We want to define our Db2-batch applications by job name and plan. The CICS and IMS data will use the defaults. The syntax of the APPLGROUPING command would be as follows:

  APPLGROUPING SUBSYSTYPE=DB2
               CONNTYPE=BATCH
               PRIMEKEY=JOB
               SECONDKEY=PLAN

  The equivalent APPLGROUPING command without using COMBINE would be as follows:

  APPLGROUPING SUBSYSTYPE=DB2
               CONNTYPE=TSO,DB2CALL,DLIBATCH,UTILITY,SYSDIRAC,APPDIRAC,RRSAF
               PRIMEKEY=JOB
               SECONDKEY=PLAN

• We want to include data from our Db2 test subsystem DB2T and will use the UIE default application values. We do want to reduce the number of records produced, however, to save on DASD work space. The following APPLGROUPING command in combination with the APPLControl command reduces the number of records being processed for the DB2T test system:

  APPLControl  SUBSYSTYPE=DB2
               SUBSYS=DB2T
               IMSMATCH=NO
               CICSMATCH=NO
  
  APPLGROUPING SUBSYSTYPE=DB2
               SUBSYS=DB2T
               PRIMEKEY=NONE
               SECONDKEY=NONE