Example 2: creating a Rule where MLWTO minor = SINGLE

This example Rule fires based on the message ID of the major and additional information from the minor messages. The following MLWTO message is the same as the message used for Example 1: creating a Rule where MLWTO minor = ALL.

M 05109 02:28:39.43 STC07239 00000281  IEA995I SYMPTOM DUMP OUTPUT 672
D                        672 00000281  SYSTEM COMPLETION CODE=0C4 
D                        672 00000281   TIME=02.28.39  SEQ=00112  CPU=0000  ASID=005A        
D                        672 00000281   PSW AT TIME OF ERROR  078D1000   80007954  ILC 2  INTC 01
D                        672 00000281     ACTIVE LOAD MODULE        ADDRESS=00007708  OFFSET=0000024C 
D                        672 00000281     NAME=ACCTPAY         
D                        672 00000281     DATA AT PSW  0000794E - 00011311  0A019140  B7F14770  
D                        672 00000281     GR 0: 00000000_00000001   1: 00000000_FFFF6F70    
D                        672 00000281        2: 00000000_0000943C   3: 00000000_00009098    
D                        672 00000281        4: 00000000_000090CA   5: 00000000_000090F2    
D                        672 00000281        6: 00000000_00000004   7: 00000000_0000917C    
D                        672 00000281        8: 00000000_000091A4   9: 00000000_00009210    
D                        672 00000281        A: 00000000_00009706   B: 00000000_00008707    
D                        672 00000281        C: 00000000_80007708   D: 00000000_00008E60    
D                        672 00000281        E: 00000000_800078FE   F: 00000004_807EF278    
E                        672 00000281   END OF SYMPTOM DUMP

To create this Rule

1. Fill in the Selection Criteria - MSG panel as follows:

   BMC Software --------- Selection Criteria - MSG  --------- MAINVIEW AutoOPERATOR
   COMMAND ===>                                                 TGT  --- AOAO     
   
          Rule-set === RUL01                          Rule-id  === SLIPX33E
   
   Text Description:
   Text ID     ===> IEA995I                           Ignore leading plus:         
   Text String (Enter Below):
   
   
   Issuer Identification:
   Job name    ===> PROD                              Name of issuer
   Type        ===>                                   (JOB, STC, or TSO)
   Jobclass    ===>                                   Job class of issuer
   Acct Info   ===>                                   Job accounting information
   RACF User   ===>                                   RACF Userid
   RACF Group  ===>                                   RACF Group name
   Route Codes ===>
   Desc Codes  ===>
   Console Name ==>                                   Destination Console Name
   MLWTO Minor ===> SINGLE                            Single/All 
   Press ENTER to continue, END return to Detail Control, CANCEL to cancel changes

   When MLWTO Minor ===> SINGLE is specified, each individual line of multiline WTO message are processed by the Rule as separate events. BMC Software recommends that you use the variables &LINE2_WORDn variables on the Variable Dependencies panel so that the Rule can fire based on specific content of the MLWTO.

   Note

   When creating a Rule for a MLWTO message, the Rule compares the selection criteria values to the content of only the first line (Major line) of the MLWTO.

   With the &LINE2_WORDn variable, LINE2 resolves to each and every line of the MLWTO and a WORDn variable resolves for each word of each line of the MLWTO.

2. Press Enter; the Variable Dependencies - MSG panel is displayed as shown in the following figure.

   Figure 1. Variable Dependencies for MLWTO Minor=SINGLE

   BMC Software  ------------ Variable Dependencies - MSG  ---------- AutoOPERATOR
   COMMAND ===>                                                 TGT  --- AOAO     
                                                                                  
          Rule-set === RUL01                Rule-id  === ABNDPROD                    
                                                                              OR/ 
    Variable-name                    Op  Variable-Value                      AND  
                                                                                  
    LINE2_WORD3:6:3_________________ EQ  0C4________________________________  AND 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________  ___ 
    ________________________________ __  ___________________________________      
                                                                                   
    --> ATTENTION: Use ASV command to add ASV criteria to the rule <--             
                                                                                   
    Press ENTER to continue, END return to Detail Control, CANCEL to cancel changes

   In this example, when you specify the variable LINE2_WORD3:6:3, the Rule Processor checks the third word in each and every line of the MLWTO message and checks the value of the last 3 characters starting at position 6.

   When these characters resolve to 0C4 on any line of the MLWTO, the Rule fires. In this case, the Rule fires because on line 2 of the MLWTO, in the third word, the last 3 characters starting at position 6 contain 0C4.

   You should contrast this example with the one in Example 1: creating a Rule where MLWTO minor = ALL because the same MLWTO is used in both examples but based on the MLWTO Minor setting and the variables used, the Rule processes the major and minor lines of the MLWTO differently.