Create FILE Structures

FILEMAINT Mode - FILE Structure Maintenance › Add Structures › Create FILE Structures

Create FILE Structures

Use the CREATE function to define a root occurrence for a structure. In FILEMAINT Mode, there are only two structures, FILE and DATAVIEW. The root of a FILE structure is a FILE occurrence and the root of a DATAVIEW structure is a DATAVIEW occurrence. Use the ADD function to define the base occurrence of a substructure, such as a RECORD occurrence for a RECORD substructure.

You can define a FILE occurrence by using one of the following procedures:

Select the CREATE option on the FILE Structure Functions Menu panel, fill in the following prompter panel, and complete the FILE definition panel.
Use a CREATE command (see CREATE) for a FILE structure and complete the FILE definition panel.

When you select the CREATE function on the File Structure Maintenance Panel for FILE Structure Functions, you receive the following prompter panel:

 =>
 =>
 =>
 1-DDOL000196A - CMPP - PLEASE COMPLETE REQUIRED INFORMATION FOR COMMAND
 -------------------------------------------------------------------------------
 FILE Structure Maintenance
                                                                            TCCF
 CREATE FILE     ________________________________ in STATUS ____
 CRE    FIL      (name)                              STAT  (status)

 with PASSWORD      using LOCK 0     LIKE ________________________________
      PSWD    (pswd)      LOC (lock) LIKE (name)









 PF1=HELP  PF2=END  PF3=CLARIFY  PF4=PROCESS  PF5=MENU   PF6=STATUS
 PF7=SCB   PF8=SCF  PF9=APPLY    PF10=PATH    PF11=NEXT  PF12=INPUT

The following list describes each field, the valid entries, and the default (if one exists). Fields that require an entry are highlighted on your terminal. Fields which are not highlighted indicate that an entry is optional.

(name)

(Required) Specify the name of the FILE occurrence you are creating.

Valid Entries:: 1- to 32-character name
Default Value:: (No default)

(status)

(Required) Specify the status for the FILE occurrence.

Valid Entries:: T001—T999
Default Value:: (No default)

(pswd)

(Optional) Specify a password to protect this occurrence from unauthorized updates. See the section on protecting definitions in the CA Datacom Datadictionary User Guide.

Valid Entries:: 1 to 4 alphanumeric characters
Default Value:: (No default)

(lock)

(Optional) Specify a lock level to restrict access to this occurrence. For more information, see the section about protecting definitions in the CA Datacom Datadictionary User Guide.

Valid Entries:: 0, 1, 2
Default Value:: 0

LIKE (name)

(Optional) Specify the name of an existing FILE occurrence in the same status to use as the model for the occurrence you are creating.

Note: Any aliases or descriptors assigned to the existing occurrence are not duplicated for the new occurrence. Define these separately.

Valid Entries:: 1- to 32-character name
Default Value:: (No default)

 =>
 =>
 =>

 -------------------------------------------------------------------------------
 FILE Structure Maintenance                                               CREATE
                                                                            TUFU
 ............................. FILE ATTRIBUTES .................................
 Name: PER-REC-HISTORY                    Status: T001
 Record Format: ____    Recsz: _____    Blksz: _____
 Access Method: _____   Device: _____   Monitor Name: ________

 ............................ RECORD ATTRIBUTES ................................
        Name                             Type  Pswd  Lock
 ====== ====================== T O P === ====  ====   =
 000001 ________________________________ ____         _
 ====== =================== B O T T O M  ====  ====   =




 PF1=HELP  PF2=END  PF3=CLARIFY  PF4=PROCESS  PF5=MENU   PF6=STATUS
 PF7=SCB   PF8=SCF  PF9=APPLY    PF10=PATH    PF11=NEXT  PF12=INPUT

The FILE definition panel displays a FILE ATTRIBUTES region and a RECORD ATTRIBUTES region. The following list describes each field, the valid entries, and the default (if one exists). Fields that require an entry are highlighted on your terminal. Fields which are not highlighted indicate that an entry is optional.

Record Format:

(Required) Specify the 4-character record format for the file.

Valid Entries:: FBLK - fixed, blocked
FUNB - fixed, unblocked
VBLK - variable, blocked
VUNB - variable, unblocked
UNDF - undefined
Default Value:: (No default)

Recsz:

(Required) This attribute-value indicates the maximum size a record can reach before expanding the physical record on disk.

For more information about the MAX-RECORD-SIZE attribute-type, see the CA Datacom Datadictionary Attribute Reference Guide.

Valid Entries:: 1—65535
Default Value:: (No default)

Blksz:

(Required) Enter a value to indicate the maximum block size for the file. This value must be a multiple of MAX-RECORD-SIZE attribute-type (Recsz).

For more information about the BLOCK-SIZE attribute-type, see the CA Datacom Datadictionary Attribute Reference Guide.

Valid Entries:: 1 to 5 digits
Default Value:: (No default)

Access Method:

(Optional) Specify the name of the access method used with this file. CA Datacom Datadictionary does not perform edits for this entry. For more information about the ACCESS-MTHD attribute-type, see the CA Datacom Datadictionary Attribute Reference Guide.

Valid Entries:: Possible entries include BDAM, VSAM, and so on
Default Value:: (No default)

Device:

(Optional) Specify the name for the device type on which the file resides. For more information about the DEVICE attribute-type, see the CA Datacom Datadictionary Attribute Reference Guide.

Valid Entries:: FBA, MDISK, PRT, PUNCH, READER, TAPE, 2311, 2314, 3340, 3350, 3370, 3375, 3380, 3390, 9345
Default Value:: (No default)

Monitor Name:

(Optional) - (Required for CA Ideal access) Specify a data definition name if your site is z/OS, or the DLBL name if your site is z/VSE.

Valid Entries:: 1 to 8 characters
Default Value:: (No default)