Printing Rules and Rule Sets

You can print hardcopy versions of MainView AutoOPERATOR Rules and Rule Sets by using the BBSAMP member RULPRINT JCL in a batch job.

This job prints selected Rules or Rule Sets that are defined in the BBIPARM DD data set concatenation.

You can specify that the output is written to SYSOUT or to a data set. When writing to a data set, the SYSPRINT DD requires the following DCB specification:

DCB=(RECFM=FB,LRECL=133,BLKSIZE=13300)

To use the RULPRNT JCL

  1. Make a copy of BBSAMP(RULEPRNT).
  2. Modify the JCL and parameters as directed within the comments of BBSAMP(RULEPRNT).
  3. Submit the job.

    The following table describes the available RULPRNT input parameters that you can use to specify which Rules or Rule Sets should be printed.

    Table 1. Reporting options

    Parameter

    Description

    RS | RULESET=

    required parameter that specifies the name of one or more Rule Sets to be printed

    If specifying multiple Rule Sets, use commas to separate the names, and enclose the group within parentheses.

    You can use generics (*) and wildcards (+) in the Rule Set names. Examples follow:

    • RULESET=AAORULAA prints a single Rule Set named AAORULAA.

    • RULESET=(AAORULAA,AAORULAB,AAORULAC) prints the three Rule Sets named AAORULAA, AARULAB, and AARULAC.

    • RULESET=AAORULA* prints all Rule Sets whose names start with AAORULA.

    • RULESET=RUL+++A* prints all Rule Sets whose names start with RUL, followed by any three characters, followed by A. (The name can either end with the A or include additional characters.)

    • RULESET=* prints all of the Rule Sets.

    RU | RULE=

    optional parameter that specifies one or more Rules from the Rule Set (or Sets) that the RULESET parameter indicates

    If specifying multiple Rule Sets, use commas to separate the names, and enclose the group within parentheses.

    You can use generics (*) and wildcards (+) in the Rule Set names. Examples follow:

    • RULE=MYRULE1 prints a single Rule named MYRULE1.

    • RULE=(MYRULE1,MYRULE2,MYRULE3) prints the three Rules named MYRULE1, MYRULE2, and MYRULE3.

    • RULE=MYRULE* prints all of the Rules that start with MYRULE.

    • RULE=MY+++E* prints all of the Rules that start with the characters MY, have any 3 characters followed by E, and after which can have additional characters in the name.

    • RULE=(MY*,YOUR*,ANY*) prints all Rules that start with the characters MY, YOUR, or ANY.

    TY | TYPE=

    optional parameter that specifies printing only the Rules for indicated event type (or types)

    If you do not specify a value, the event type attribute is not considered.

    Valid values are any valid event types (for example, MSG, ALRT, JRNL, CICS, and so on).

    If specifying multiple event types, separate them with commas, and enclose them within parentheses. Examples follow:

    • TYPE=MSG prints Rules for the MSG event type.

    • TYPE=(MSG,JRNL,ALRT) prints Rules for event types MSG, JRNL, and ALRT.

    ST | STAT=

    optional parameter that specifies printing only the Rules that match the specified state

    If you do not specify a value, the Rule's state is not considered.

    Examples follow:

    • STAT=ENA prints Rules that are ENABLED.

    • STAT=DIS prints Rules that are DISABLED.

    H | HAS=

    optional parameter that specifies printing only Rules that match the criteria specified

    If you do not specify a value, the Rule's contents are not considered.

    Valid values are

    • SV (for Set Variables specifications, standard or advanced)

    • AV (for Variable Dependencies specifications, standard or advanced)

    • AA (ALERT Actions specifications). Examples follow:

    Examples follow:

    • HAS=SV means the Rule must have Set Variables specifications.

    • HAS=(SV,AA) means the Rule must have both Set Variables and ALERT Actions specifications.

    U | UDATE=

    optional parameter that specifies printing only Rules that have been updated since the indicated date

    If you do not specify a value, the Rule's last update date is not considered.

    The format of the value must match the pattern yyyy/mm/dd.

    The following example indicates March 29, 2012:

    UDATE=2012/03/29

Was this page helpful? Yes No Submitting... Thank you

Comments