One control card is required for every program. It provides special information about your program and describes your system to the
RPG
I1 compiler. Without this information your source program cannot be translated into an RPG I1 object program. To help you code the control card, one specification line is provided on the Control Card and File Description sheet (Figure 3-1).COLUMNS 1-2 (PAGE) See Chapter 2.
COLUMNS 3-5 (LINE) See Chapter 2.
COLUMN 6 (FORM TYPE)
An H must appear in column 6 . A control card with an
N
in column 6 must be entered for every program even if all the other control card columns are left blank.
l n m a a a l m u m MrhloarComontlon Form X27 Sl
prinw Pd" U ( RPG CONTROL CARD AND FILE DESCRIPTIWU SPECIFICATIONS
1 2 75 76 77 78 7% 1
rwammee
Conool Card Specifications
Refer to tharpecific Synem Rdaance Lbbrsry manual for actual enrrlar
File Oedption Specificationr
Name of label Exrt
1 4 5 5 8 6 5 7 5 8 '
File MdltionlUrardara:
N u m k of Tracks imber of Extern
Figure 3-1. Control Card and File Description Sheet
COLUMNS 7-9 (CORE SIZE T O COMPILE)
Columns 7-9 are not used. Leave them blank. Any entry in these columns is ignored by the compiler. The program is compiled in the available core storage.
COLUMN 10 (OBJECT OUTPUT) Entry Explanation
Blank Object program is written temporarily in the object library.
* C P Object program is written permanently
-
t in the object library.P Object program is punched into cards.
Column 10 is used to indicate the output you want as a result of compiling the source program. The object program is always written in the same object library in which the compiler resides.
You will usually want the object program written tem- porarily in the object library until you have corrected any
Column 11 provides for listing options at the time your source program is compiled. Compilation will cease after the program listing is complete if any severe errors are found.
The blank entry is the usual case, producing an object program (if no severe errors are found), an object program listing, and a core map. The program listing consists of the source program and error messages. The core map lists relative addresses of fields, constants, I/Q areas, etc.
The D entry means that no object program will be produced; however, a program listing with error messages and a core map are printed. This entry can be used if you think the program has many initial errors. In such a case, it is not advisable to produce an object program until these errors are reduced in number. The D entry overrides any entry made in column 10 of the Control Card Specifica- tions line.
severe errors in your program. When a program is written
temporarily in the object library, it will be overlaid by the - - A O L U M N S 12-14 (CORE SIZE TO EXECUTE) next program written in the object library.
COLUMN 11 (LISTING OPTIONS) E n 0 Explanation
Blank I . The object program is produced (if no severe errors are found).
A program listing is printed.
A core map is printed.
The object program is not produced.
(The D entry overrides any entry in column 10 of the Control Card Specifications.)
The program listing is printed.
A core map is printed.
Entry Explanation
Blank The core storage available for object pro- gram execution is the same as that used to compile the program.
00 1-029 The core storage available for program execution (if different from core storage available for object program generation).
Columns 12-14 define the core storage available for program execution. The entry must end in column 14. The entry is some multiple of 1K bytes of storage (K=1,024).
This entry may be different from the core storage avail- able for object program generation for two reasons: I) Your program may be executed on a different system from the one that compiled your program, or 2) You are using the Dual Program Feature.
If the system used for program execution is different from that used for compilation, subtract the amount of core storage occupied by the supervisor from the total core storage of the system used for execution.
If you are using the Dual Program Feature, subtract the amount of core storage occupied by the second object program and the supervisor from the total core storage of the system used for program execution.
COLUMN 15 (DEBUG) COLUMN 19 (OUTPUT-S
Entry Explanation Entry Explanatiorz
Blank DEBUG operation is not performed. Blank Sterling currency is not being used.
1 DEBUG operation is performed. 0 Output shilling field is to be printed only.
Use column 15 to indicate whether or not the DEBUG opera- 1 Output shilling field is to be punched in operation is performed. In order to perform a DEBUG IBM format.
operation:
2 Output shilling field is to be punched in 1. A 1 must appear in column 15 when the source pro-
gram is compiled,
BSI format.
2. The DEBUG operation code must appear in calcula-
tion specifications. COLUMN 20 (OUTPUT-PENCE)
See Operation Codes, Debug Operation in Chapter 10 for more information.
COLUMN 16
Column 16 is not used. Leave it blank.
--
- COLUMNS 17-20 (STERLING)Columns 17-20 are used to describe the format of the sterling fields used in sterling currency. If you are not using sterling, these columns must be left blank. See Sterling in Chapter 10 for more information.
- -
COLUMN 17 (INPUT-SHILLINGS) EntvY ExplanationBlank Sterling currency is not being used.
1 Input shilling field is in IBM format.
2 Input shilling field is in BSI (British Standards institute) format.
*.. 4 COLUMN 18 (INPUT-PENCE)
Entry Explanation
Blank Sterling currency is not being used.
1 Input pence field is in IBM format.
2 Input pence field is in BSI format.
Entry Explanation
Blank Sterling currency is not being used.
0 Output pence field is to be printed only.
1 Output pence field is to be punched in
2 Output pence field is to be punched in BSI format.
The same fields may be both punched and printed. Although they are always punched in the selected format (IBM or BSI), the printed output is not affected by the selected format. Printed fields always have two positions in both the pence and shilling fields. See Sterling in Chapter 10 for more information.
"-,COLUMN 21 (INVE
Entry Explanation Blank Domestic format.
I World Trade format.
J World Trade format (leading zero remains for zero balances).
D United Kingdom format.
Use column 21 to describe the format and punctuation used in numeric and UDATE fields. The blank entry specifies the domestic format of monthldaylyear for UDATE fields (10/15/69), and a decimal point for numeric fields (183.55).
The I entry specifies the World Trade format of
day.month.year for UDATE fields (1 5 .lO.69), and a decimal comma for numeric fields (18355).
The J entry specifies the same World Trade format as the I entry with one exception. When the J entry is used, zero balances are always written or punched with one zero to the left of the decimal comma (such as 0,OO). Also this leading zero appears for the J entry when there is some value in the field, but there is no value to the left of the decimal comma (such as 0,04 or 0,lO). The J entry overrides any edit codes used for zero suppression; that is, the leading zero that appears for the J entry cannot be removed by an edit code.
The D entry specifies the United Kingdom format of daylmonthlyear for UDATE fields (1 5/10/69), and a decimal point for numeric fields (183.55).
OLUMNS 22-25
Columns 22-25 are not used. Leave them blank.
COLUMN 26 (ALTERNATE COLLATING SEQUENCE) Entry Explanation
Blank Normal collating sequence is used.
S Alternate collating sequence is used.
Use column 26 only if you are altering the normal collating sequence for this job. See Alternate Collating Sequence in Chapter 10 for more information.
OLUMNS 27-36
olumns 27-36 are not used. Leave them blank.