Report RPTRULES describes input rules or members that were processed by the utility. Each line of the report describes one input rule regardless of whether it was the only rule in the input member.
The following fields are included in report RPTRULES:
Table 18 Fields in the RPTRULES Report
Field |
Description |
---|---|
IN DSN ID |
Dataset ID of the PDS in which the member containing the input rule was found. For more information about dataset IDs, see RPTFILES – Input/Output File Report. |
MEMBER NAME |
Input member name. |
WARN |
Warning indicator field. This field contains an asterisk (*) if a warning message was issued while processing the rule described in this line of the report. If no warning was issued, this field is blank. |
INPUT RULE SEQ NUM |
Unique sequence number of the input rule within the input member (R0001, R0002, and so on.). |
TOTAL MEM |
Number of lines in the input member (including all rules in the member). The same value appears for all the rules in the same input member. |
SCRIPT |
Number of lines (in the input member) that contain text that is not a comment (for example, /* comment */), sequence number (columns 73 - 80 in numbered FB files or columns 1 - 8 in numbered VB files), or spaces. The same value appears for all the rules in the same input member. |
RULE |
Number of lines of code in the rule (excluding comment lines and blank lines). |
PRODUCT NAME |
The product (or the language) associated with the rule. Utility CTOFANCI currently recognizes the following types of member content:
|
EVENT TYPE CODE |
The event type code of the input member or rule. The utility automatically assigns one of the supported event type codes to each input rule or member. Input members that do not contain rules are assigned an event type code according to the product or language of the member. The following event type codes are used:
|
OUT DSN ID |
Dataset ID of the output dataset to which the corresponding output rule or member is written. |
OUTPUT TABLE/MEMBER |
Member or Rule Table name to which the corresponding output rule or member is written. |
INTENDED OUTPUT MEMBER |
Name of the member or Rule table to which the corresponding output rule must have been written (for rules or members that were assigned a duplicate name (@DUPnnnn). If the rule was actually written to the intended member, the Output Table or Member and Intended Output Table or Member fields contain the same value. |
FULL DETAILS |
Information about the event that triggers the rule (such as, message ID, time specification, name of a Global variable.). |
DETAILS SUMMARY |
A subset of the rule details supplied in the Detail field (for example, message ID, jobname). |
The following screen segment contains part of a RPTRULES report. Note that this report contains additional columns not shown in this sample.
Figure 4 Sample RPTRULE Report
------------------------------------------------------------------------------
CTOFANCI: INPUT RULE SUMMARY REPORT (RPTRULES) RUN ID = D1027.T1256
------------------------------------------------------------------------------
W INPUT NUM-OF-LINES
IN A RULE -------------- EVENT OUT OUTPUT
DSN MEMBER R SEQ TOTL SCR- PRODUCT TYPE DETAILS DSN TABLE/
ID NAME N NUM MEM IPT RULE NAME DESC SUMMARY ID MEMBER
---- -------- - ----- ---- ---- ---- -------- -------- -------- ---- --------
D001 $$$SPACE R0001 0 0 0 PDSMAN -
D001 C10ERR1 R0001 66 12 12 CLIST CLIST D101 MAIN
D001 DBASUN R0001 4 1 1 UNKNOWN UNKNOWN D101 @DPL0001
D001 IEF085I R0001 10 1 1 CLIST CLIST D101 @DPL0002
D001 INCBKUP R0001 80 67 67 CLIST CLIST D101 @DPL0003
Parent Topic |