Previous Topic: Create a Rule to Tailor the Display of MessagesNext Topic: Lesson 7: Suppress Messages Using the Automation Analyzer


Create a Rule to Suppress Messages

To practice using EasyRule, access OPSVIEW to create your second rule, a message suppression rule.

Follow these steps:

  1. Access the EasyRule Primary panel. Begin at the OPSVIEW Primary Options Menu.
  2. Enter 2.3 into the Option field. As a result, the EasyRule Primary panel appears.
  3. Specify a data set and member for this second rule. You should now be on the EasyRule Primary panel. You now tell EasyRule the name of the rule set that you want to contain the second rule. As you did for the first rule, use the Project, Group, and Type fields on the EasyRule Primary panel to do so. You must also specify a new member name in the Member field. Specify these values:

    Your panel should now look like the one shown here:

    EasyRule --------------- MSI1 --- O P S V I E W --------------- Subsystem OPSS Command ===> EEEEE AAAA SSSSS YY YY RRRRR UU UU LL EEEEE EE AA AA SS YYYY RR R UU UU LL EE EEEE AAAAAA SSSSS YY RRRRR UU UU LL EEEE EE AA AA SS YY RR RR UU UU LL EE EEEEE AA AA SSSSS YY RR RR UUUU LLLLL EEEEE ISPF LIBRARY: PROJECT ===> SYS1.OPS GROUP ===> TEST TYPE ===> RULES MEMBER ===> MNSTATUS OTHER PARTITIONED DATA SET: DATA SET NAME ===> Do You Wish To AUTOMATICALLY step thru EasyRule? ===> N (Y/N)

    After you enter the data set and member name for the new rule, the Rule Type Selection panel appears.

    A sample follows.

  4. Select the type of rule that you want to create. From the Rule Type Selection panel, choose option 1 to create a message rule. Notice that following sample panel already selected this option:

    EasyRule --------------------------------------------------------------------- Option ===> 1 R U L E T Y P E S E L E C T I O N 1 MSG - Create Message Event Rule 2 CMD - Create Command Event Rule 3 GLV - Create Global Variable Event Rule 4 TOD - Create Time-Of-Day Event Rule 5 OMG - Create OMEGAMON Event Rule 6 DOM - Create Delete-Operator-Message Event Rule 7 EOJ - Create End-Of-Job Event Rule 8 EOM - Create End-Of-Memory Event Rule 9 EOS - Create End-Of-Step Event Rule 10 TLM - Create Time-Limit-Exceeded Event Rule 11 USS - Create UNIX System Services (USS) Message Event Rule Press END to return

    After you select option 1, the Message Rule Main Menu appears. A sample follows.

  5. Select MESSAGE ID from the Message Rule Main Menu. From the Message Rule Main Menu, select 1, for MESSAGE ID. Notice that 1 has been specified in the Option field in the following sample:

    EasyRule --------------------------------------------------------------------- Option ===> 1 M E S S A G E R U L E M A I N M E N U 1 MESSAGE ID - Specify the ID of the message(s) to be processed 2 DOCUMENTATION - Add comments to this Rule 3 CONDITIONS - Supply additional criteria for this Rule to fire 4 ACTIONS - Take action with respect to the message(s) 5 INITIALIZATION - One-time initialization done when Rule is ENABLEd 6 TERMINATION - Specify actions to be taken when Rule is DISABLEd

    When you choose 1 from the Message Rule Main Menu, the Primary Event Specification panel for message rules appears. A sample follows.

  6. Supply the primary selection criterion. Use the Primary Event Specification panel to specify a primary event for the MNSTATUS rule. The primary event for a message rule is always a message ID. To continue with this example, type IEF285I in the MSG ID field. Also, specify D in the Just Delete field to indicate that you not only want to suppress the message, but you also want to keep it from appearing in SYSLOG. In the following sample, the MSG ID and Just Delete fields are completed:

    EasyRule ---------------------------------------------------------------------- Command ===> S P E C I F Y M E S S A G E I D MSG ID ===> IEF285I JUST SUPPRESS ===> N (Y/N/D) or JUST DELETE ===> D (Y/N/D) DELETE FROM OPSLOG === N (Y/N) MSG ID is used to determine if this Rule should perform an Action. It must be 1 to 10 characters in length and may optionally include a "wildcard" character '*'. MSG ID is the only required field. If you just want to SUPPRESS or DELETE the message, type Y next to the appropriate entry. Subsequent panels are bypassed if using Step-thru mode. DELETE is like SUPPRESS, but also deletes the message from SYSLOG. D is the same as Y except that in Step-thru mode, you will be given a chance to enter comments about the rule.

    When you finish specifying values on the Primary Event Specification panel and press Enter, EasyRule returns you to the Message Rule Main Menu, as shown in the following step.

  7. Select DOCUMENTATION from the Message Rule Main Menu. From the Message Rule Main Menu, select 2, for DOCUMENTATION. Notice that this selection has been done in the sample shown here:

    EasyRule --------------------------------------------------------------------- Option ===> 2 M E S S A G E R U L E M A I N M E N U 1 MESSAGE ID - Specify the ID of the message(s) to be processed 2 DOCUMENTATION - Add comments to this Rule 3 CONDITIONS - Supply additional criteria for this Rule to fire 4 ACTIONS - Take action with respect to the message(s) 5 INITIALIZATION - One-time initialization done when Rule is ENABLEd 6 TERMINATION - Specify actions to be taken when Rule is DISABLEd

    When you select 2, the Create Rule Comments panel appears. A sample Create Rule Comments panel follows.

  8. Document the MNSTATUS rule. To continue following along with this example, type the comments that are shown in the following example onto your own Create Rule Comments panel:

    EasyRule --------------------------------------------------------------------- Command ===> C R E A T E R U L E C O M M E N T S Rule Name ===> MNSTATUS Rule Type ===> Message Rule Function ===> Monitor status is enabled to get not cat 2 msg.________ ===> This rule deletes normal disp messages.________________ ===> _______________________________________________________ ===> _______________________________________________________ ===> _______________________________________________________ ===> _______________________________________________________ ===> _______________________________________________________ Author ===> CA Customer Support__________________ Support ===> _______________________________________________________ Related Rules ===> NOTCTLG (IEF287I)______________________________________ Related CPs ===> _______________________________________________________ History ===> 93/10/31 - Original Development________________________ ===> _______________________________________________________ ===> _______________________________________________________ ===> _______________________________________________________

    After you enter comments for the rule, EasyRule returns you to the following Message Rule Main Menu:

    EasyRule --------------------------------------------------------------------- Option ===> M E S S A G E R U L E M A I N M E N U 1 MESSAGE ID - Specify the ID of the message(s) to be processed 2 DOCUMENTATION - Add comments to this Rule 3 CONDITIONS - Supply additional criteria for this Rule to fire 4 ACTIONS - Take action with respect to the message(s) 5 INITIALIZATION - One-time initialization done when Rule is ENABLEd 6 TERMINATION - Specify actions to be taken when Rule is DISABLEd

  9. Access the EasyRule Final Options Menu. From the Message Rule Main Menu, press PF3 to access the EasyRule Final Options menu (shown next).
  10. Review the OPS/REXX code that EasyRule built. On the EasyRule Final Options menu, choose option 3, as shown here:

    EasyRule --------------- MSI1 --- O P S V I E W --------------- Subsystem OPSS Option ===>3 EEEEE AAAA SSSSS YY YY RRRRR UU UU LL EEEEE EE AA AA SS YYYY RR R UU UU LL EE EEEE AAAAAA SSSSS YY RRRRR UU UU LL EEEE EE AA AA SS YY RR RR UU UU LL EE EEEEE AA AA SSSSS YY RR RR UUUU LLLLL EEEEE 1 SAVE - SAVE the Rule that was built and EXIT 2 CANCEL - EXIT and DO NOT SAVE the Rule that was built 3 BROWSE - Browse the generated OPS/REXX code 4 ALTER - Return to the panels to modify the Rule DO YOU WANT TO BE ABLE TO MODIFY THIS RULE WITH EASYRULE? ==> Y (Y/N) DO YOU INTEND TO INSERT USER PROCESSING CODE IN THIS RULE? ==> N (Y/N) DO YOU INTEND TO INSERT USER INITIALIZATION CODE IN THIS RULE? ==> N (Y/N) DO YOU INTEND TO INSERT USER TERMINATION CODE IN THIS RULE? ==> N (Y/N)

    When you select option 3, a panel similar to the one in the following example displays:

    BROWSE -- EASY_RULE_BROWSE ------------------------- Line 00000000 Col 001 080 Command ===> Scroll ===> PAGE ******************************** Top of Data ********************************* MSG IEF285I **********************************************************************/ * Rule Name: MNSTATUS */ * Rule Type: Message */ * Rule Function: Monitor status is enabled to get not cat 2 msg. */ * This rule deletes normal disp messages. */ * Author: CA Customer Support */ * Related Rules: NOTCLG (IEF287I) */ * History: 93/10/31 - Original Development */ **********************************************************************/ PROC *--------------------------------------------------------------------*/ * The following code is executed each time the rule is fired. */ *--------------------------------------------------------------------*/ return "DELETE" /* from console and SYSLOG */ ******************************* Bottom of Data *******************************

    This panel presents the OPS/REXX code EasyRule generates as a result of the panel entries suggested in the second part of this sample session. This code exists only in storage; later you save it to the data set and member you indicated on the EasyRule Primary panel. The next sample panel shows the OPS/REXX code and the panel entries that correspond to it.

    The CA OPS/MVS base product has the following components:

    OPS/REXX Code: MSGIEF285I

    Panel Entries: Rule Type Selection Panel and Specify Message ID Panel

    OPS/REXX Code: Comments box

    Panel Entries: Create Rule Comments Panel

    OPS/REXX Code: Return DELETE

    Panel Entries: Specify Message ID Panel

    When you finish browsing the generated OPS/REXX code, press PF3 to return to the EasyRule Final Options menu. A sample menu is shown next.

  11. Save the OPS/REXX code as a new rule. From the EasyRule Final Options menu, select 1, for SAVE. Notice that 1 appears in the following Option field:

    EasyRule --------------- MSI1 --- O P S V I E W --------------- Subsystem OPSS Option ===> 1 EEEEE AAAA SSSSS YY YY RRRRR UU UU LL EEEEE EE AA AA SS YYYY RR R UU UU LL EE EEEE AAAAAA SSSSS YY RRRRR UU UU LL EEEE EE AA AA SS YY RR RR UU UU LL EE EEEEE AA AA SSSSS YY RR RR UUUU LLLLL EEEEE 1 SAVE - SAVE the Rule that was built and EXIT 2 CANCEL - EXIT and DO NOT SAVE the Rule that was built 3 BROWSE - Browse the generated OPS/REXX code 4 ALTER - Return to the panels to modify the Rule DO YOU WANT TO BE ABLE TO MODIFY THIS RULE WITH EASYRULE? ==> Y (Y/N) DO YOU INTEND TO INSERT USER PROCESSING CODE IN THIS RULE? ==> N (Y/N) DO YOU INTEND TO INSERT USER INITIALIZATION CODE IN THIS RULE? ==> N (Y/N) DO YOU INTEND TO INSERT USER TERMINATION CODE IN THIS RULE? ==> N (Y/N)

    When you choose 1 from the EasyRule Final Options Menu, EasyRule saves the rule to the data set and member you specified earlier, and returns you to the EasyRule Primary panel.

More information:

Using EasyRule