Sample CA IDMS/DB Schema Module

CA IDMS DLI Transparency Load Utility › Sample Source Code For Database Load › Sample CA IDMS/DB Schema Module

Sample CA IDMS/DB Schema Module

GENERATE Schema Statement

Just as with the IPSB source code, you can use the syntax generator to make sure that you have a CA IDMS/DB schema module that will support a successful database load. The GENERATE statement in this case takes the following form:

GENERATE LOAD SCHEMA NAME IS LOADSCHM FOR DBD ITEMDBDP, PARTDBDP.

Note that physical DBD names are all that you need to produce the schema source.

Figure 60 shows the schema source code as it might be produced by the syntax generator using the DL/I physical DBD definitions in Figure 58.

Considerations

Here are some general considerations about the schema source code produced by the syntax generator:

The generated schema has OPTIONAL MANUAL set connection options for each logical child/logical parent set.
Generated schema source by itself is not sufficient for a database load. It must be edited to include site-specific standards, optimized database page ranges, and so on.
If you already have a suitable CA IDMS/DB schema, you can modify this schema without having to create a new load schema. Specifically, you must make sure that the logical child/logical parent set description has OPTIONAL MANUAL connection options. These options are required only during the load process and can be changed to MANDATORY AUTOMATIC after the load. The only exception is in the case of bill-of-materials relationships.
In this type of relationship the logical parent and physical parent of the child record are different occurrences of the same record type. Bill of materials sets must have OPTIONAL MANUAL connection options.
The page ranges specified for the CA IDMS/DB database in the schema/subschema must be consistent throughout the load process. A change in the page ranges will invalidate the database pages calculated by the preload CALC processing (Step 1). In this case, you will have to repeat both the CALC and load steps so the logical workfile produced by the load can give correct results for the prefix update step.

Generated Schema source statements:

 SIGNON
          USAGE MODE IS UPDATE .
 SET OPTIONS FOR SESSION
          INPUT     1 THRU     72.


 ADD SCHEMA NAME IS LOADSCHM VERSION     1
          MEMO DATE IS 12/22/86
          ASSIGN RECORD IDS FROM     101
          PUBLIC ACCESS IS ALLOWED FOR ALL.


 ADD AREA NAME IS PARTDBDP-REGION.


 ADD AREA NAME IS ITEMDBDP-REGION.


 ADD RECORD NAME IS PART
          RECORD ID IS AUTO
          LOCATION MODE IS CALC
          USING PARTNO
          DUPLICATES ARE NOT ALLOWED
          WITHIN AREA PARTDBDP-REGION.
 02       PARTNO            PIC X (18).
 02       FILLER            PIC X (132).


 ADD RECORD NAME IS ITEM
          RECORD ID IS AUTO
          LOCATION MODE IS CALC
          USING ITEMNO
          DUPLICATES ARE NOT ALLOWED
          WITHIN AREA ITEMDBDP-REGION.
 02       ITEMNO            PIC X (7).
 02       FILLER            PIC X (143).


 ADD RECORD NAME IS DETAIL
          RECORD ID IS AUTO
          LOCATION MODE IS VIA ITEM-DETAIL
          WITHIN AREA ITEMDBDP-REGION.
 02       FILLER            PIC X (25).
 02       ITMDTAIL          PIC X (3).
 02       FILLER            PIC X (129).

Figure 60 (Part 1 of 4). Generated Schema source statements

 ADD RECORD NAME IS PARTNDX
          RECORD ID IS AUTO
          LOCATION MODE IS VIA PART-PARTNDX
          WITHIN AREA PARTDBDP-REGION.
 02       PARTNO            PIC X (18).


 ADD RECORD NAME IS ITEMNDX
          RECORD ID IS AUTO
          LOCATION MODE IS VIA ITEM-ITEMNDX
          WITHIN AREA ITEMDBDP-REGION.
 02       ITEMNO            PIC X (7).


 ADD SET NAME IS ITEM-DETAIL
          ORDER IS SORTED
          MODE IS CHAIN LINKED TO PRIOR
          OWNER IS ITEM
               NEXT DBKEY POSITION IS AUTO
               PRIOR DBKEY POSITION IS AUTO
          MEMBER IS DETAIL
               NEXT DBKEY POSITION IS AUTO
               PRIOR DBKEY POSITION IS AUTO
          LINKED TO OWNER
               OWNER DBKEY POSITION IS AUTO
          MANDATORY AUTOMATIC
          ASCENDING KEY IS ITMDTAIL
          DUPLICATES ARE NOT ALLOWED.


 ADD SET NAME IS PART-DETAIL
          ORDER IS SORTED
          MODE IS CHAIN LINKED TO PRIOR
          OWNER IS PART
               NEXT DBKEY POSITION IS AUTO
               PRIOR DBKEY POSITION IS AUTO
          MEMBER IS DETAIL
               NEXT DBKEY POSITION IS AUTO
               PRIOR DBKEY POSITION IS AUTO
          LINKED TO OWNER
               OWNER DBKEY POSITION IS AUTO
          OPTIONAL MANUAL
          ASCENDING KEY IS ITMDTAIL
          DUPLICATES ARE LAST.

Figure 60 (Part 2 of 4). Generated Schema source statements

 ADD SET NAME IS PART-PARTNDX
          ORDER IS SORTED
          MODE IS CHAIN LINKED TO PRIOR
          OWNER IS PART
               NEXT DBKEY POSITION IS AUTO
               PRIOR DBKEY POSITION IS AUTO
          MEMBER IS PARTNDX
               NEXT DBKEY POSITION IS AUTO
          LINKED TO OWNER
               OWNER DBKEY POSITION IS AUTO
          MANDATORY AUTOMATIC
          ASCENDING KEY IS PARTNO
          DUPLICATES ARE NOT ALLOWED.


 ADD SET NAME IS ITEM-ITEMNDX
          ORDER IS SORTED
          MODE IS CHAIN LINKED TO PRIOR
          OWNER IS ITEM
               NEXT DBKEY POSITION IS AUTO
               PRIOR DBKEY POSITION IS AUTO
          MEMBER IS ITEMNDX
               NEXT DBKEY POSITION IS AUTO
          LINKED TO OWNER
               OWNER DBKEY POSITION IS AUTO
          MANDATORY AUTOMATIC
          ASCENDING KEY IS ITEMNO
          DUPLICATES ARE NOT ALLOWED.


 ADD SET NAME IS IX-PARTNDX
          ORDER IS SORTED
          MODE IS INDEX
               BLOCK CONTAINS  50 KEYS
          OWNER IS SYSTEM
          MEMBER IS PARTNDX
               INDEX DBKEY POSITION IS AUTO
          MANDATORY AUTOMATIC
          ASCENDING KEY IS PARTNO
          DUPLICATES ARE NOT ALLOWED.

Figure 60 (Part 3 of 4). Generated Schema source statements

 ADD SET NAME IS IX-ITEMNDX
          ORDER IS SORTED
          MODE IS INDEX
               BLOCK CONTAINS  50 KEYS
          OWNER IS SYSTEM
          MEMBER IS ITEMNDX
               INDEX DBKEY POSITION IS AUTO
          MANDORY AUTOMATIC
          ASCENDING KEY IS ITEMNO
          DUPLICATES ARE NOT ALLOWED.


 VALIDATE.
 SIGNOFF.

Figure 60 (Part 4 of 4). Generated Schema source statements