r 590 FORWARD BALANCE
12. Lata from cards with higher prEcedEncE can bE available when frocessing
match-ing cards cf lower prEcedencE, but nct vice versa.
13. The crder in which sFecificaticn lines for a card type with Matching Fields are EnterEd nEEd not ccnform tc the level of the Matching-Fields
specifieations--e.g., ttE line with M3 in cels. 61-E2 could fall [EtwEEn the lines with M1 and M2.
Alse~ specificaticn linES witheut Matching-Fields entry in cels. 61-62 may intervene between lines with Matching-Fields entry.
14. Matching-Fields (M1, M2, M3) ofErations are independent cf Ccntrel-levEl
(L1-IS) operations. (However, thEY are related to thE extent that
centrcl-U
ield ce~parisons are enly performEd when pertinent cards are preeessed--and that, in turn, is based on theMatching-Fields operatien.)
Note: Additional rules apply to Matching FiElds used in conjunction with Field-Record RElation (cols. 63-E4), and are dis-cussed in that--the next--sectien.
These columns are used in cenjunction with records in an OR relationshif (see Recerds in_~n_OR~~gl~!igQ§hi~). Entries in-cols.-63-64 fermit asseeiating fields enly with a particular ene of several eard types in an OR relationship. The distinction is made by entering in cels. 63-64 the ccde ef one of tbt Resulting Indicatcrs assigned in cols. 19-20 to the several eard types in an OR relationshif.
Field-Record Relation can be USEd when two or mere card tYPES differ in their Record Identification Codes (cels. 23-41) but a majority of their infut fields are in the same columns, have the same format, and identical field names affly--and these fields are dEscribed only ence. However, some of the input fields differ in field name, location of source celumns, and/er format, and/or size--and Each differen~
field requirEs a separate field description line. (The field name may be the same, provided the sole difference fer that field betWEen the eard types is in lecation of source celumns; etherwise the name must also be different.)
Different card-type Resulting Indicators are assigned in cols. 19-20 to scme or all of the several card types in the OE rela-tionship. Ey entry of tte card-tYFe Resulting Indicator for the appropriate card tYPE in li£lQ~]§~gfQ_]gl~ti~B (cels.
63-64), a field descrirtion is associntEd only with a particular cne ef the card types in an OR relationship. ,Field descriptions without an entry in Field-Record Relatien apfly to all the ~ard types in the OR relationship. This saves enter-ing sfecification lines and, if the propor-tion of identical fields preponderates, i t also saves core sterage space.
Control-Level fields and/or Matching Fields may alse te asseciated with particu-lar card types in an OR rElatienship by entry of the relevant card-type Resulting
~ndicator in Field-Record Relation. An entry for the same 1- or M-indicator (eols.
59-6C or 61-62, respectively)~ithout a Field-Record Relatien entry then applies only when nene of the pertine~tcard-type
Resulting Indicators, in Field-Record Rela-tion for the L- or M-indieator, is on.
]gi~: The core storaqe saved by the single entry of field description lines that apply to all the card types in an OR relationship must tE WEighed against the core sterage cost to the object program in having to test indicators for the field descriptions that differ for the separate card types.
Half the fields common to all card types in the OR relatienshif may be used as 2 rule of thumb for the break-even point.
Special Rples for Use of Field-Record Rela-tion (cols. 63-64)
For each set of card types in an OR relationship:
1. Core storage space is conserved by greuping together (i.e., in consecutive lines) all field descriptions with the same indicator in Field-Record Relation
(cols. 63- 64), a nd by grouping togethe r all field descriptions without Field-Record Relation indicator.
2. When the same Central level (11-L9--cels. 59-60) or Matching-Fields level
(IIJ1-M3--cols. 61-62) is assignEd roth to field descrirtien without Field-Record Relation indicator, and to one or more field descriptions with FiEld-Record Relation indicator(s), the Central-Level and Matching-FiElds entries without Field-Record Relation indicator must appear first.
3. In view of (1) and (2) above, all the field-description lines without Field-Record Relaticn entries sheuld appear before those with FiEld-Record
Relatien.
4. The program treats split centrol fields
(~eE Control Level, eols. 59-6C) of one Centrol-Level-a;-a single entity, for purfoses of Control-Level operations.
In pu t S pee if ica ti ons (Manda tor y) 91
Therefore, i t is net pcssitle (for Centrcl-level operaticns) to assign different field porticns of a single Control Level to different Field-Fecord Relaticn indicators, er to assign a porticnto a Field-Record Relaticn indicator and have another portion in a field-description line without Field-Record Relatien indicator.
The same result is easily achieved ty repeating all perticns of the split control field--even that which might apply regardless of OR-relation eard type--for all pertinent Field-Record Relation field-descripticn lines.
(Figure 26B, lines 06 and 17, illus-trates this--see explanation in point 3, under ].!.E..!anation_s.:LE:n tri.§s
il}
I.!~±§_16B·l
5. When the same Control level or
Matching-Field level is assigned beth to field descripticn without
Field-Record Relation indicator, and tc cne or more field descripticns with Field-Record Relation indicator(s), enly the specificaticn with the pertinent Field-Record Relation indicator is used--for Centrol-level and/or Matching-Fields eperaticns--when that indicator is turned on. If none of the Field-Record Relation indicators for that Centrol Level or Matching-Fields level is cn,
th~ specification without Field-Record Relation indicator assigned is used for that level.
Ccntrol-Level and Matching-Fields specificaticns to which no Field-Record Relations indicator is assigned for any c-ftt€card-type-s--in the Off-Teia tien--ship are used with all card types in the CR relationship.
6. The number of ~atchinq Fields specified (one, two, or three) ~ust be uniform for all card types for which Matchinq Fields are specified.
It is net allowed, therefore, to match (or sequence cleck by entry in cels. 61-62) on a di1fg£en1-Q~~t§£_Qf 1ielQ~ for different card types in an OR relaticnship. It is, however,
permissitle to match (or sequence-check ty entry in ccls. 61-62) on the
appropriate numter of fields for some card types--and nQl_~l_~ll for others in the OR relationship. The latter implies that all field-descriptien lines with Matchinq Fields specified contain also a Field-Record Relation indicator entry; otherwise--as explained in 5, above--a
Matching-Fields line wit~out
Field-Record Relation indicator is applied whenever ne such indicator is on for that Ie vel. (See also l:1~.:t£hiJl..g
Ii.§lds, cols. 61-62, and ]~tc£inB-of fJ:l.§~)
7. The number of Ccntrol Levels (11-19) specified for different card types in the OR relationship may differ. It is alsc permitted to have no Control Level for certain card types, and any numrer ef Central Levels for other card types.
8. While--for Control-level and Matching-Fields cperatiens--entries with Field-Record Relation indicator assigned take precedence, when the relevant indicator is on, over those withqut an indicator entry in ccls. 63-64, this is not true for other processing cf the data in these fields:
The data from the card field defined in every field-description line which has no Field-Record Relation entry is read frem all card types in "the OR relationship. This data is read into the core storaqe area assigned by the prcqram to that field name, which is not the same area where Control-Level or Matching-Fields information--which ignores field name--is stored.
If i t is desired to read into the field-name storaqe area for a field only from certain card types in the OR relationship--or to read the same field from different card columns for the different card types--then each field-description line fer that field must have an appropriate indicator entered in Field-Record Relation.
Fiqures 26A, B, and C illustrate input-specificaticns entries for Control Level, Matching Fields, Field-Record Relation, and other OR relaticnships. (SEe also Fiqure 25 and earlier fiqures.)
92 System/36C Medel 20 CPS Report Fr09ram Generator
IBM
INTERNATIONAL IUSINess MACHINes CORPORATION Form X2.t-33.50. I Prinfed in U. S. A ..REPORT PROGRAM GENERATOR INPUT SPECIFICATIONS
Dale _ _ _ _
Program _ _ _ _ _ _ _ _ _ _ _
Programmer _ _ _ _ _ _ _ _ _ _ _
Punching Instruction
IBM System/360
Record Identification Codes
1 2 3
0 2 I OR 1 CB 14 D 2
o 3, l O R 1 C C 7" D
r
3o ~ l O R 85 14 D8 3
0 5 I OR 98 7+ 1>9
o 6 I
o 7 I
_ ...
o 8 I
o 9 I I
1 0 I 1 I I
1 2 I
1 3 ISECIIFILE.AC
1 ~ I AND 74 Z K.
1 5 I
I , 17 I I 8 I
19 I
FigurE 2EA. Field DEscrifticn~--part II
"Explanation of Entries in Figure 26A--Control lEvels, File Matcbinq, and OF BEla-tionshif TYfes 1 ana 2 (seE Bg~2fQ~iTI~n
Q1LB.§1 a t ~Q,D~ hi.I)
Ii,DgE_Q1L_02 L_§TIQ_03 sho~ three IEcords in an OR relaticnship of TYfe 1 (seE abcvE):
Resulting Inoicator 80 apflies tc all three tYfes (it coula have bEen IEpeatEd in Each line). Nc distinction can bE made (cn the basis of cara type) in the calculation andl or output-format sfecifieations tetweEn the threE caro types, bEcausE thE sarr.e indica-tor is assigned to all three.
lines 04 and 05 sho~ two merE rEcords in an cR-relationship to the first three; tut they are cf TYPE-2 OF relaticnshif: sEpa-ratE REsulting Indicators are assignea to them, to permit calculaticn- and output-specifications distincticn tEtwEEn trE fourth cara type, the fifth, and the first threE (a s a grou p) •
Lines 02-04 alsc illu~trate that card types in any kind of OR relationship--Even
I' 7.51677787980
Page
OJ
Id:~~~<Oo~onI I I I I I I
Field Fieid
location Indicators
;-' ~
:!
Field Name i .;; ~ Ze'o S~~~gFrom To 1.
1
~ ~ 1 Plus Minus or Position,1 0 or _§I ~ Bla:1k
/ .. /J / /! / i ~ / ~ / / / / I
... .:;.;c. .. 7.a.v:M,l:'JI:lLI:I,J:a • .).))&575BS96016162636 ... 6S66676869707173~
5
1, ;£MPLNO
L 1 11.1 30 WAME
Sf}
S,
1>IVI5N J43 31 31 SHIFT2 5 DEPT L3 1ft
75 7~ ZPAYRAT
7'
8~ C OftPOR L45 l'IEMPL/JOL1M1 11 14 DEPT liZ 75 7811J.1RSWRK
Card Electro Number _ _ _
when no distinguishing REsulting Inaicator is assignEd--may bE directed to non-normal stackers by entries in the input
specifications.
rinEs 01-05 illustrate only OR relation-ships of Types 1 ana 2: the data fields
(lines 06-12) arE aEfined only onCE, and none arE limitea to a particular one, or group, of the five card types in the CB relationship--Field-Fecord Belation (cols.
63-64) is thereforE blank.
1in~~_1]_§TIQ_l~ are another example of AND relatienships betWEen four criteria fer the aefinition of one card type.
Li,Des Q~_an~12 spEcify that Control revel L1 will te a numeric contrel only (all zones strippea), bEcause col. 52 has an entry.
ling~_06~_J~_~nQ_J2L_~nQ_lin~§~-End~2 sho~ Centrol-Level indicators to be in ascending order of significance--as they must te, even if the data appears in the
Input Specifications (Mandatory) 93
IBM
INTERNATIONAL BUSINESS MACHINES CORPORATION form X24-3350 1 Printed in U. S. A.REPORT PROGRAM GENERATOR INPUT SPECIFICATIONS IBM System 360
Record Identificotion Codes
2 3
Position Position
~j
.! 0 ... V 2627 28293031 33 35363738C1
1YPE10R2 is preserved, and ccmpared aaainst the nExt eard processEd frem that file.
If ,L4 turns on \o/hen reading a card from SECNFIIE, 13, 12, and r1 alse turn cn, even thouqh L3 and L2 arE not assigred in this file.
li~~§_lf_End~ illustrate that tne
Materinq-FieldE EpEeificaticrs (~1, ~2, M3
i ;,; hiah-crder (most-sianificar.t) field, and M1 the lew-oroEr field. 1hus, DIVISN contains the mest-significant (leftmost) data for the card match and sequence ChECk, DEPT the which matchina fields are specified
(three fields in all cards of this example) ;
c.
That Matchina Fielos Leeo not be the same as Control-~evel fields;c. 1hat other field-description lines may te placea tEtwEen Ccntrcl-level and Matclina-?iElds lines.
94 Sys~err/360 rcdel 20 CFS Fercrt Frccram Generatcr
Lin~§_if~_i~L-~n~_J] show how to spEcify FiEld Lccatien (in cel~. 46-47 and 5C-51) for singlE-column fiElds.
Iin§§_Q~_~n~_l~L_~ng_l§_End_12 ~how that fiElds fer Contrel Level and Matching FiElds may overlap. Lines ~~~~~_~ show that fields for different Ccntrol Levels and for different Matching-Fields levels may ever lap.
F'i!~_!:~1~ti2!!.§.bi.E: File TYPE 10R2 is the primary file, bEcausE it is specifiEd ahead of SECNFJTE. When cards frcm the twe files match on the data in the three fields spec-ified as Matching Fields, matched primary cards arE processed ahead cf matched
secondariEs~
Therefore, when processing a card from SECNFILE, data from the last preceding card from the file labeled TYPE10R2 can be uti-lized. For example, gross pay ceuld re calculatEd by multiplying HRSWEK in each SECNFILE card by PAYRAT frem the last pre-ceding card from file TYPE10E2. The EE indicator is en only fer matchEd cards.
Conditioning the calculaticn specification to be performed, at detail time, only if the indicators ME and 89 are both on, gross pay would ce calculated cnly on card~ from SECNF'ILE and only if the last card from the file TYPE10R2 matched the SECNFIlE card on DIVISN, [EFT, and EMPINO. Gres~ pay cculd not re calculated during the precessing of a card from the file TYPE10E2, because all matching primary cards have completed pro-cessing tefere data (in thi~ caSE, HES~RK)
beccmes available frcm a matched secondary card.
To illustrate the point that data fer fields with different Field Names is stored at different lccatiens, regardless of
source cclumns, PAYRAT and HRSWRK were assigned the same card ccl~mns in different card types.
Explanation of Entries in Figure 26E--Split Control Fields, Selective sequence Check, and OR Relatien~hip Type 3
lin~§_QJ~~~ provide for identifying each of the four different card types in an OF relationship, and assiqning a different Resulting Indicator to each. Indicator 94 is assigned to cards trat do net satisfy the criteria for indicators 91-93 (i.e., not 1, 2, or 3 in col. 80); these cards are selected to stacker 2. No Record Identifi-cation Codes are nEeded in line 04, because lines in an OR relationship are tEsted in sequence; therefore, cara-type Resultinq Indicator 94 turns on only if the card does not meet the criterion in line 01, 02, or 03.
Iig~!:~_~6C itemizes the card columns frem which Central-Level data will ce taken for each of the four card types in the OR rela-tionship. The follewing peints are note-worthy in Figures 26B and C with regard to Control Level:
1. ~hen neither indicator 91 nor 92 is on, L1 Control Level is based on the L1 entries with no Field-Record Relation specified (line~ 05 and 06). "When indicator 91 or 92 is on, L1 Control-Level data is based on the entries in lines 11-13 or 16-17, respectively--lines 05 and 06 are then ianored for Centrol-Level data.
Similarly, 12 Centrol Level is based cn the entries in linE 19 (data-card cols. 61-63) when indicator 92 is on
(i.e., the seccnd type ef card was read); otherwise; it is based on the entries in line 08 (cols. 11-13).
Likewise, 13 Control Level is based on line 14 (data-card columns 51-70) whEn indicatcr 91 is en (first type of card) ; otherwise i t is based on lines 09 and 10 (cols. 51-60 and 31-40).
r---,---,
I Card-Type I Card Columns Read for Central-Level Operations I I Resulting ~----~-.---T---~---~
I Indie. eN I L4 I L3 I L 2 ! L 1 I
~---t---t_---_t---_+___---_.----_.---~
I 91 I L1-2~ I ~1-7C I 11-13 I 71-75 I 26-27 I 48-50 I
~---~---+---~.---_t---+_---~-,-_.---i---~
I 92 I No L4 I 51-60 I 31-40. I 61-63 I 6-10 I 46-5C I
I I control I I I I I I
1---I---I---I---t---+---t_---I
I S3 I No L4 I ~1-6C I 31-4C I 11-13 I 1-5 I 46-50 I
I I control I I ' I I I
I---+---t_---t---t---+---+---~
I 94 I 21-2~ I ~1-6C I 31-40 I 11-13 I 1-5 I 46-50 I
L - - I ~ _ _ _ _ _ _ i _ _ _ _ _ _ _ ~ _ _ _ _ _ _ _ L _ _ _ _ _ _ _ _ _ _ _ L -_________ ~
Figure 26C. Card Columns frem which Ccntrol Fields will be Taken whEn One of the Card Types Defined in Figure 2EB is Read
Input Specificaticns (~andatory) 95
2. Control level r4 is operative only when indicator 91 or 94 is cn, becaUSE 14 is not spEcifiEd at all without a Field-Record Re lation. Ca rd types to wh ich Resultinq Indicator 92 cr 93 is
assiqnEd therefore dc not turn on indi-cator 14. The L4 Control-leVel data is preSErvEd frem the last FrEceding card with indicator 91 or 94, tc be compared against thE 14 data in the next card of type 51 or 94.
3. The 11 Control Level is split into threE fields for cards with indicator 91, and into two fieldE for thE ctber card types. Note that, in all three cases, the total length for L1 is unif erm (ten celumns): the aggregate length of fields fer a Eplit Centrel Level must be uniform for all card type s.
Ir lines 06 and '7 the field entries for the low-erder Forticn ef the split 11 Centrol Level are identical (FIDA2, source cols. 4E-5C). Ncnetheless, the field description had to be repeated fer Field~Recold Relaticn indicatcr 92, bEcausE the other Forticn ef L1 differs betWEEn card type 92 and etherE (Ecurce cols. 6-10 versus 1-5, and Field Name FLDA6 versus FIDA1): part of a split ccntrcl field cannct be conditicred by a FiEld-Record Relation indicator unless all Farts are se conditicned, even if this means repetition of an identical entry.
4. In lines 09 and 10, thE fields tc which Contrcl Level L3 is assigned are
~l~ "fiI1J::.d_;;t~"I)JJJl!~J;:i~_"_i9.9J_" ."_ 5 )""J~? __ §" __
EntriEs). Each of the two pcrtienE (subfields) is within the limit of 15 columns for a numeric field, althcugh the aggregate length of the L3 control field exceeds 15 columns~-it adds up to 20 celumns. This is permissible, so lcng as no individual numeric subfield EXCEeds 15 celumns.
In line 14, the sa~e L3 Ccntrcl Level is not split when card-type Resulting Indicator 91 is cn. To be uniferm for all card types, it must be 20 celumns leng--which eXCEeds the 15-column limit for a numeric field. Note that FIDC in line 14 is defined as alphameric (col. 52 is blank); it may therefore legitimately exceed 15 columns in length.
It is permissible te designate dif-ferently named fields for the same Con-trol Level in different formats (i.e., with different Decimal Pe~iticns spEci-ficatien). For processing of the data in trE fields, fermat accords with the specification in col. :2; for
Control-Level operations, compare is purely numeric (zones stripped) if one of the fields or split portions for that Con-trol Level is defined as numeric. L3 is, therefore, a numeric control field.
5. Control-Level entries must be in
ascending order of significance (i.e., L1 appears in an earlier line than L2, etc.) within FiEld-Record Relation greup, and within the qroup without Field-Record Relation specifications.
6. The Control-Level entries without Field-Record Relation specifications must appear ahead of those conditioned by Field-Record Relation.
7. Lines without Control-Level specifica-tion may appear between those with dif-ferent Control-Level specifications, but (to be compatible with other RPGs) not between entries for the same split Ccntrol Level.
Lines_05=JQL-11-12L_l§=1~_Egg-1Q illus-trate thcit field-description lines should be grouped by Field-Record Relation indica-tor, to minimize core stcraqe requirements.
1ig~§_lJ_~n~1]L_~g~-1~~Q~~ contain Matching Fields specifications (in cols.
61-62). The contents of fields FLDA3 and FLDA5 in card type 91, and FLDA6 and FLDE2 in card type 92 will bE sequence checked.
Card types 93 and 94 are not sequence checked, because M1 and M2 are not spEci-fied with FiEld-Record Relation 93 or 94;
nor are they specified without any Field-Record Relation. (If M1 and M2 were also specified in lines without.a.Field-Record
R-elat-Ic-n-enTry ,-The-
-flETci"sint-h-e-s-e"
rfne-s-would be sequence checked whenever neither indicator 91 nor 92 is on.)
Note that, for card types for which Matching Fields are specified, the same number of fields must be specified for matching, and the field size for each M-level must bE the sarre in all such cards.
Da!~=iield_§£gciiifEiion§ are not affected by Field-Record Relation in the same manner as Contrcl Level or Matching Fields:
As pointed out above, whenever a
Control-Level or Matching-Fields specifica-tion appears in the same line as a Field-Record Relation indicator, only the
Control-LeVEl or Matching-Fields specifica-tion in that line applies for that level--even if the same Control-Level or Matchinq-Fields code is also specified in a line without Field-Record Relation.
However, the data for the field speci-fied in a field-description li~e without Field-Fecord Relation entry is read into 96 SYStEffij3EO ~odEl 2C CPS Befort Frccram Generator
the core storaae area assigned to that
the core storaae area assigned to that