Using the start position

For work qualifiers longer than 8 characters, you can use a start position to indicate how far to index into the character string for a match. For example, you can assign all TSO/E users in a department to the same service class, assuming you follow a naming convention for accounting information for the department. Work qualifiers that run longer than 8 characters are:

Accounting information
Client accounting information
Client IP address
Client transaction name
Client userid
Client workstation name
Collection name
Correlation information
Package name
Procedure name
Process name
Scheduling environment
Subsystem parameter
zEnterprise service class name

The ISPF administrative application provides the Start field where you can specify the starting position Start of change for work qualifiers longer than 8 characters End of change . The name field for a work qualifier is 8 characters long. If you are matching on a string less than 8 characters using a start position, you must use wildcard notation (asterisk) at the end of the string. Otherwise, the qualifier is padded with blanks to be 8 characters, and the blanks are used when making a match.

Example 1: Using the start position

Assume you want to associate all JES2 work from department IRS with the service class JESFAST. You assigned the default for JES2 work as service class JESMED. If all JES2 accounting information from department IRS have the characters 'DIRS' starting in the eighth position, you enter a rule with qualifier DIRS* to match on just the four characters. If you want to filter out those jobs with the eight characters 'DIRS ' starting in the eighth position, you need another rule with qualifier DIRS to assign those jobs to JESMED. The example shows the rules:

Subsystem Type . . . . . . . : JES
Description  . . . . . . . . . All JES2 service classes

   -------Qualifier-------------            -------Class--------
   Type       Name     Start                Service     Report
                                   DEFAULT: JESMED      ________
1  AI        DIRS        8                  JESMED      ________
1  AI        DIRS*       8                  JESFAST     ________

In this case, all jobs that have accounting information with the eight characters 'DIRS ' starting in the eighth position are assigned to JESMED. All other jobs that have the four characters 'DIRS' starting in the eighth position are assigned to JESFAST. All other work coming into JES is assigned to service class JESMED.

When no start parameter is specified, WLM matches the name field for work qualifiers that run longer than 8 characters according to the number of characters specified. Note that this is different from work qualifiers that are 8 characters long. For those the qualifier name is always padded with blanks to be 8 characters. Work qualifiers that are 8 characters long are the following:

Connection type
LU name
Net ID
Perform
Plan name
Priority
Sysplex name
Subsystem instance
Subsystem collection name
System name
Transaction class
Transaction name
Userid

Example 2: Blank padding for long and short work qualifiers

Assume you want to associate all JES2 work from accounts with numbers starting with 0201, and all work from user IDs starting with DEPT58 with the service class JESFAST. The example shows the rules:

Subsystem Type . . . . . . . : JES
Description  . . . . . . . . . All JES2 service classes

   -------Qualifier-------------            -------Class--------
   Type       Name     Start                Service     Report
                                   DEFAULT: JESMED      ________
1  AI        0201                           JESFAST     ________
1  UI        DEPT58*                        JESFAST     ________

Without a start position, WLM matches work qualifiers longer than 8 characters according to the number of characters specified. In the example, when matching the accounting information for 0201, WLM matches it as a 4 character string. Therefore, a job with accounting information '020175,D123' would match.

For work qualifiers that are 8 characters long, you must use wildcard notation at the end of the string. Otherwise, the qualifier is padded with blanks to be 8 characters, and the blanks are used when making a match. In the example, user ID DEPT58* will match on 'DEPT58XY', 'DEPT58Z', etc. If you had specified user ID DEPT58 without the asterisk at the end, it would match only on 'DEPT58 '.

The same applies to qualifiers longer than 8 characters when a start position is specified. The table below summarizes this behaviour:

--------------Qualifier-------------------------- -----Behaviour--------
Type                      Name     Start
8 characters long         DEPT58   not supported   Matches on 'DEPT58__' only,
                                                   nothing else. Must use
                                                   wildcard notation at the
                                                   end of the string to match
                                                   any 'DEPT58xx'.
longer than 8 characters  0201     none            Matches on '020175',
                                                   '0201XY', '0201Z', etc.
                                                   Same as if wildcard
                                                   notation at the end of the
                                                   string had been specified
longer than 8 characters  DIRS     8               Matches on 'DIRS____'
                                                   starting at the eighth
                                                   position only, nothing
                                                   else. Must use wildcard
                                                   notation at the end of the
                                                   string to match any
                                                   'DIRSXYZZ' starting at the
                                                   eighth position.

Start of change Work qualifiers that run longer than 8 characters can be nested. In combination with the start position, this allows matching more than 8 characters. End of change

Example 3: Nesting using the start position

Assume you want to associate all JES2 work from account number 020175 with service class JESSLOW, except if it originates in department D58I*, in which case JESFAST should be used. The example shows the rules:

 Subsystem Type . . . . . . . : JES
 Description . . . . . . . . . All JES2 service classes
 -------Qualifier------------- -------Class--------
 Type       Name     Start     Service     Report
                      DEFAULT: JESMED      ________
 1 AI       020175             JESSLOW     ________
 2 AI         D58I*    8       JESFAST     ________

A job with accounting information '020175,D58I1234' is then assigned service class JESFAST. A job that contains the job statement '020175,D64I9876' is assigned service class JESSLOW, because the department is different from D58I*. A job with accounting information '020177,D58I5678' is assigned the default service class JESMED, because the account number does not match, and therefore the system never checks any subrules.