|
|
|
Control statements are used to tell CA JARS which reports you want generated, for what time period, and how you want them formatted. They are contained in a file of fixed-length 80-byte records. Each control statement is identified by an alphanumeric statement type of up to eight characters. The statement type is checked for syntax and discrepancies that might cause errors during the run. Should the report program encounter any erroneous data, the record is flagged and a message is printed indicating the problem area.
Control statements are divided into two groups. The first group consists of statements that govern the general aspects of the report program run; the second group controls the formatting of individual reports.
The following statement types belong to the first group--those that control the general aspects of your reports:
|
Required |
Optional |
|---|---|
|
|
CONFIG statement |
|
|
CONFIGX statement |
|
|
CRITERIA statement |
|
SELECT statement |
PARMS statement |
|
|
OPTION statement |
|
|
STDFORM statement |
|
|
STDPRINT statement |
|
|
STDPUNCH statement |
|
|
EXTDATA statement |
The statements on the next page are used to control the format of individual output reports. Since up to 15 reports can be requested for each run, this group can be composed of many sets of statements, with each set of statements used to define one particular report format. Each set can include a combination of any of the following statement types.
Statement types required for basic reporting are: HEADER, DISPLAY, and SORT.
The statements listed below are optional and are grouped by usage.
Computer Billing & Budget Control
Other Format Customization Features
Selection/Rejection Of Records
Each report is identified by a set code. This code ties together all control statements relating to a specific report. All the statements for a given set of reports must contain the same set code. The set code consists of any valid EBCIDIC character placed in the first position of all statement types, with the exception of the CONFIG, SELECT, CRITERIA, OPTION, and PARMS control statements which never require set codes due to their global nature.
Control statements with blank set codes are referred to as global control statements. The following statement types can have a blank set code that lets them be included in every report set. However, in the following list, those statements that can be overridden by a corresponding statement type containing a nonblank set code are indicated by an asterisk.
It is recommended that you include all sets of control statement when generating reports. Doing so ensures that the report program has access to all your user report formats, and relieves you of the necessity of combining the proper sets of control statements for the appropriate run. The SELECT statement is used to indicate which set(s) of statements are required to generate the desired report(s). For more information, see the section SELECT Statement in the "Control Statements and Tables" chapter.
| Copyright © 2012 CA. All rights reserved. |
|