• Aucun résultat trouvé

FLD Control Card

Dans le document Information Management System/360 for the (Page 124-130)

One or more FLD control cards .may follow the FLDK control card. This card defines each of the fields, in the segment defined by the preceding 114

,/

(

(

I /

)

SEGM control card, that may appear as part of a Data Language/I call qualification statement. All fields do not have to be defined.. A maximum of 1000 FLDK and FLD cards may be defined in the en.tire DBD. A maximum of 2.54 FLD cards is allowed per SEGM card.

The format and parameters of the FLD control card are as outlined for the FLDK control card" above.

r---,

I I I I

I I

[FLD]

I t

I I I I

L _________________________________________________________ J

If a nonkey field is not referred to with a Data Language/I GET call, no field control card need be included in the DBDGEN.

FLD

is the card-type code that identifies this as the control card for an ordinary data field,. There can be many data fields for any given Data Language/I segment. If a field is to be used in a segment search argument, i t must be def~ned with a field control card.

DBDGEN Control Card

~ ~

r---,

1 I I I

1 I

DBDGEN

I I

I I I I

L _________________________________________________________ J

since i t is the key to generating the data base description from the parameters specified above, this control card must be included .•

FINISH Control Card

r---,

I I I I

I I

FINISH

I I

I I I I

L _________________________________________________________ J

This control card must be included. I t sets the on-zero condition code for link-edit if there are DBD generation errors,.

END Control Card

r--~---,

I I I I

I I

END

I I

I I I I

L _________________________________________________________ J

Since i t signifies the end of the DBDGEN, this control card must be entered.

DBDGEN Examples

1. Set up a hierarchical indexed sequential data base consisting of a single data set group (see Figure 41). Each data base record will contain two segments of two and three fields, respectively.

The data base will be stored on a 2311 disk pack. The access

NAME=Sl" PARENT=O ,BYTES=15 ,FREQ=100 NAME=KEY,TYPE=X,BYTES=4,START=1 NAME=KEY, TYPE=X" BYTES= 4, START=l NAME=DATA,TYPE=C,BYTES=11,START=5 DD1=DS22,DEV1=2311,DLIOF=OVFL4 NAME=S2, PARENT=Sl, BYTES=20

I,

FREQ=l

NAME=KEY1,TYPE=X,BYTES=4,START=1

/

l _______________________________ J

Multiple data set groups

Figure 43. Hierarchical sequential data base

DESCRIPTION OF DBO GENERATION OUTPUT

Three types of printed output and a load module which becomes a

member of the partitioned data set with the generic name of DBD library are produced by a DBD generation. Each of these outputs is described in the following paragraphs.

Control Card Listing

This is an exact reproduction of the character representation of the contents of each of the SO-column control cards. That is, i t is a

listing of the input card images to this job step.

Diagnostics

Errors discovered during the processing of each control card will result in diagnostic messages being printed immediately following the image of the last control card read before the error was discovered.

The message may reference either the control card immediately preceding' i t or the preceding group of control cards. I t is also possible for more than one message to'be printed per control card. In this case, they follow each other on the output listing. After all the control cards have been read, a further check is made of the reasonableness of the entire deck. This may result in one or more additional diagnostic messages.

Any discovered error will result in the diagnostic message(s) being printed, the control cards being listed, and the other outputs being suppressed. However, all the control cards will be read and checked before the DBD generation execution is terminated,. The link-edit step of DBD generation will not be processed if a control card error has been found.

Assembly Listing

An Operating System/360 Assembler Language listing of the DBD macro expansion created by DBD generation execution ,is provided. The

inclusion of the PRINT NOGEN eliminates assembly information and provides a synopsis of the DBD control information.

Load Module

DBD generation is a two-step Operating System/360 job. Step 1 is a macro assembly execution which produces an object module. Step 2 is a link-edit of the object module which produces a load module, that becomes a member of the generic DBD library.

DBD Generation Error Conditions

The following are the DBD generation error conditions and the messages displayed for these conditions:

Error Message DBD

DBD

OBO OBO

OMAN

OMAN

OMAN

OMAN OMAN

118

Condition

---DBD010---Incorrect or missing access method

---DBD020---DBD name parameter not specified

---DBD030---Too many DBD cards

---DBD040---0BD name must begin with an alpha character

---DMAN010---Incorrect device specification

---DMAN020---Incorrect access specification

---DMAN030---0D2 parameter invalid with ACCESS equal to ISAM

---OMAN040---Too many DMAN cards ---DMAN050---BLKFACT specified but no LRECL

(

(

OMAN

/ OMAN

OMAN

OMAN

DMAN OMAN

DMAN

SEGM

SEGM

SEGM

SEGM

)

SEGM

/

SEGM

SEGM

SEGM

SEGM

SEGM SEGM

FLD

FLD

FLD

)

FLO

---OMAN060---LRECL specified but no BLKFACT operand

---DMAN070---LRECLxBLKFACT greater than track length

---DMAN080---Missing DLIOF operand with access equal to ISAM

---OMAN090---DLIOF is present or DD2 is missing with access equal to SAM ---DMAN100---D01 operand omitted ---DMAN110---DD1 and DD2 have same ddnames for HSAM

---OMAN120---DD1/DLIOF duplicate ddnames for HISAM

---SEGM10---Segment name not specified

---SEGM20---Segment bytes parameter not specified

---SEGM30---Segment frequency parameter not specified

---SEGM40---Root segment parent must equal zero

---SEGM50---Parent operand not specified for dependent segment ---SEGM60---TOO many SEGM cards;

255 maximum

---SEGM70---Segment length greater than DASD track

---SEGM80---Segment length specified as zero

---SEGM90---Segment frequency of zero invalid

---SEGM100---Duplicate segment names J

---SEGMllO---Segment length greater than specified LRECL

---FLD010---Field name parameter not specified or invalid

(that is, more than 8 characters>

---FLD040---Type parameter not specified or invalid

---FLD050---FLDK card not first after SEGM card

---FLD060---Too many FLD ,or FLDK cards specified

Dans le document Information Management System/360 for the (Page 124-130)