LOAD

The LOAD utility loads data into an SQL-defined database.
idmscu19
The LOAD utility loads data into an SQL-defined database.
The process of loading a database has three major phases:
Phase
Description
Load
Loads the data.
Build
Builds indexes and linked indexed referential constraints.
Validate
Ensures the validity of referential constraints.
Each phase is composed of multiple steps.
You can run the LOAD utility in several ways:
Type of LOAD
What It Does
Complete LOAD
Runs all three phases.
Phased LOAD
Runs either the LOAD and BUILD phases or just the LOAD phase.
Stepped LOAD
Runs the first or second step of the LOAD phase, with intermediate file sorting required between each step.
For more information about the phases and steps involved in loading a database, and help in deciding what kind of load you should run, see .
This article describes the following information:
Authorization
To
You need this privilege
On
Load into a table
INSERT
The table
Only one LOAD, BUILD, or VALIDATE statement can be performed during one execution of the Batch Command Facility (IDMSBCF).
Syntax
Complete LOAD:
Syntax for complete or phased LOAD
  ►►─── LOAD ───────────────────────────────────────────────────────────────────►    ┌──────────────────────────────┐  ►─▼─ target-table-specification ─┴───────────────────────────────────────────►  ►─┬───────────────────┬──────────────────────────────────────────────────────►    └─ WITHOUT PRESORT ─┘  ►─┬────────────────────┬─────────────────────────────────────────────────────►    ├─ NO BUILD ─────────┤    ├─ BUILD INDEX ONLY ─┤    └─ NO VALIDATE ──────┘    ►─┬─────────────────────┬────────────────────────────────────────────────────►    └─ FROM start-record ─┘  ►─┬──────────────────────────┬───────────────────────────────────────────────►    └─ FOR ─┬─ record-count ─┬─┘            └─ ALL ◄─────────┘  ►─┬───────────────────────────────┬──────────────────────────────────────────►    └─ LRECL logical-record-length ─┘    ►─┬──────────────────────────────┬───────────────────────────────────────────►    └─ NOTIFY notify-record-count ─┘  ►─┬───────────────────────────────────────────────┬──────────────────────────►◄    │ ┌───────────────────────────────────────────┐ │    └─▼─┬────────────┬─ ERRORS ─┬─ error-count ─┬─┴─┘        ├─ LOAD ─────┤          └─ CONTINUE ────┘        ├─ BUILD ────┤        ├─ VALIDATE ─┤        └─ ALL ◄─────┘  
Expanded syntax for target table specification
►►─── INTO ─┬────────────────┬─ table-id ─────────────────────────────────────►             └─ schema-name. ─┘  ►─┬───────────────────────────────────────────────────┬──────────────────────►    └─ WHERE ─┬─ select-column-name ──────┬─ = literal ─┘              └─ POSITION start-position ─┘  ►─┬──────────────────────────────────────────────────────────────────────┬───►◄    │┌──────────────────────────────── , ───────────────────────────────┐  │    └▼─target-col-name POSITION start-pos data-type ┬─ NULL IF literal ┬┴)─┘                                                    └─ SQLIND (length) ┘  
Stepped LOAD
Syntax for STEP 1
  ►►─── LOAD STEP1 ─────────────────────────────────────────────────────────►    ┌──────────────────────────────┐  ►─▼─ target-table-specification ─┴───────────────────────────────────────►  ►─┬───────────────────┬──────────────────────────────────────────────────►    └─ WITHOUT PRESORT ─┘    ►─┬─────────────────────────────┬────────────────────────────────────────►    ├─ EXTRACT ─┬─ INDEXES ─────┬─┤    │           ├─ CONSTRAINTS ─┤ │    │           └─ BOTH ◄───────┘ │    └─ NO EXTRACT ────────────────┘  ►─┬─────────────────────┬────────────────────────────────────────────────►    └─ FROM start-record ─┘    ►─┬──────────────────────────┬───────────────────────────────────────────►    └─ FOR ─┬─ record-count ─┬─┘            └─ ALL ◄─────────┘  ►─┬───────────────────────────────┬──────────────────────────────────────►    └─ LRECL logical-record-length ─┘    ►─┬──────────────────────────────┬───────────────────────────────────────►    └─ NOTIFY notify-record-count ─┘  ►─┬────────────────────────────┬─────────────────────────────────────────►◄    └─ ERRORS ─┬─ error-count ─┬─┘               └─ CONTINUE ────┘  
Syntax for STEP 2
  ►►─── LOAD STEP2 ─────────────────────────────────────────────────────────►  ►─┬──────────────────────────────┬───────────────────────────────────────►◄    └─ NOTIFY notify-record-count ─┘  
Parameters
Parameters for complete or phased LOAD
  • target-table-specification
    Specifies the tables and columns to be loaded.
    See parameter descriptions under "Parameters for Target Table Specification".
  • WITHOUT PRESORT
    Directs the LOAD utility not to sort the input data in SYS001 before starting to load.
    By default, if you do not specify WITHOUT PRESORT, the LOAD utility will sort the input data into target page sequence before beginning to load.
    For more information and help in deciding whether to suppress the presort, see .
  • NO BUILD
    Directs the LOAD utility to perform neither the BUILD nor the VALIDATE phase.
    If you specify NO BUILD, you must run the BUILD utility before you can use the table(s).
  • BUILD INDEX ONLY
    Directs the LOAD utility to build indexes but not referential constraints.
    If you specify BUILD INDEX ONLY, you might have to run the BUILD utility before you can use the table(s).
  • NO VALIDATE
    Directs the LOAD utility to stop before validating referential constraints.
    If you specify NO VALIDATE, you will have to run the VALIDATE utility before you can use the table(s).
  • FROM
    Directs the LOAD utility to begin processing input data from a specified record in the input file.
    By default, if you do not specify a
    start-record
    , the LOAD utility will begin with the first record of the input file.
  • start-record
    Specifies the number of the first record to process.
  • FOR
    Directs the LOAD utility to stop after processing a specified number of records from the input file.
    By default, if you do not specify a FOR option, the LOAD utility will continue until it has processed the last input record.
  • record-count
    Specifies the number of records to process before stopping.
  • ALL
    Directs the LOAD utility to continue processing until it has loaded the last record in the input file.
    All is the default.
  • LRECL
    Specifies that the SYS001 input records are fixed length records.
    By default, if you do not specify LRECL, the LOAD utility assumes that the SYS001 records are variable length.
  • logical-record-length
    Specifies the length, in bytes, of the fixed length input records.
  • NOTIFY
    Directs the LOAD utility to send a message to the operator whenever a specified number of records are processed.
    The message states the phase and step currently being executed and the number of records processed.
    By default, the LOAD utility will not notify you of its progress until it is finished.
  • notify-record-count
    Specifies the number of records to process before sending a message.
  • ALL ERRORS
    Directs the LOAD utility either to continue when any errors are detected or stop after a specified number of errors are detected.
    By default, the LOAD utility will stop after the first error is detected.
    Detected errors are listed in the report generated by LOAD and sent to the SYSLST file.
  • LOAD ERRORS
    Directs the LOAD utility either to continue when errors are detected in the LOAD process or stop after a specified number of errors are detected.
    By default, the LOAD utility will stop after the first error is detected.
    Detected errors are listed in the report generated by the LOAD utility and sent to the SYSLST file.
  • BUILD ERRORS
    Directs the LOAD utility either to continue when errors are detected while indexes and referential constraints are being built or stop after a specified number of errors are detected.
    By default, the LOAD utility will stop after the first error is detected.
    Detected errors are listed in the report generated by the LOAD utility and sent to the SYSLST file.
  • VALIDATE ERRORS
    Directs the LOAD utility either to continue when errors are detected in the validation or stop after a specified number of errors are detected.
    By default, the LOAD utility will stop after the first error is detected.
    Detected errors are listed in the report generated by the LOAD utility and sent to the SYSLST file.
  • error-count
    Specifies the number of errors to detect before stopping.
  • CONTINUE
    Directs the LOAD utility to continue regardless of the number of errors detected.
Parameters for Target Table Specification
  • INTO
    Specifies a table in which to load data.
  • schema-name
    Specifies the name of the schema that contains the table.
  • table-id
    Specifies the identifier of the table.
  • WHERE
    Directs the LOAD utility to insert a row into the table from an input record only if a field beginning at a specified position in the input record, or the contents of an input column, equals a given literal value.
  • select-column-name
    Specifies the name of the column whose contents must equal a literal value.
    The column name you specify must also be a column name of the table and must be named in the column list of the target table specification if target column names are used.
  • literal
    Specifies the value the column must contain.
    The data type of the literal must be comparable to that of the column.
    For more information about comparable data types, see .
  • POSITION
    start-pos
    Specifies the beginning position of the field whose value is to be tested.
  • literal
    Specifies the value the field must contain. The literal must be a character or hexadecimal literal value.
  • target-column-name
    Specifies the columns of the table for which input values are present in the input file.
    If no column names are specified, the input file must contain values for all columns of the table and the order, data type, and null indications must exactly match those of the table as defined in the dictionary. VARCHAR and VARGRAPHIC input values must be preceded by a 2-byte binary length of the value.
    If you specify more than one
    target-column-name
    , specify them in increasing order; the position of each must be greater than the sum of:
    • The position of the one listed before
    • plus
    • The size of the data type for the one listed before
      • The size of VARCHAR is the maximum length, plus 2.
      • The size of VARGRAPHIC is the maximum length times the number of bytes for one character, plus 2.
  • POSITION
    Specifies the position of the column value in the input record.
  • start-pos
    Specifies the position of the first byte of the value relative to one.
  • data-type
    Specifies the SQL data type of the column value in the input record.
    For a list of SQL data types and for the SQL standards of data-type specification, see .
  • NULL IF
    Directs the LOAD utility to substitute a null value if it encounters a specified input value.
  • literal
    Specifies the value for which a null will be substituted. The data type of the literal must be comparable to the data type of the column.
  • SQLIND
    Indicates that a null indicator immediately follows the data value on the input file.
    The possible values of the null indicator and their meanings are as follows:
Value
Meaning
Binary zeros
The column value is not null
Binary X'FF's
The column value is null
  • (
    length
    )
    Specifies the length of the indicator. The length must be 1, 2, or 4.
Parameters for STEP 1
  • LOAD STEP1
    Directs the LOAD utility to perform only the first step of the load process.
  • target-table-specification
    Specifies the tables and columns to be loaded.
    For the syntax expansion and parameter descriptions of
    target-table-specification
    , see "Complete LOAD" earlier in this section.
  • WITHOUT PRESORT
    Directs the LOAD utility not to sort the input data before starting to load.
    By default, if you do not specify WITHOUT PRESORT, the LOAD utility will sort the input data before beginning to load. The records are sorted so that target pages will be loaded in order.
    For more information and help in deciding whether to suppress the presort, see .
    If you specify WITHOUT PRESORT, then do not run LOAD STEP2. After LOAD STEP1 is completed, and you have sorted the output of LOAD STEP1, run the BUILD utility.
  • EXTRACT
    Directs LOAD to extract information needed for building indexes or referential constraints.
    By default, if you do not specify otherwise, LOAD STEP1 will extract the information needed for building both indexes and indexed referential constraints. In this case, you can begin BUILD processing with BUILD STEP2.
  • INDEXES
    Directs the LOAD utility to extract only the information needed for building indexes. Therefore, the LOAD utility will not extract the information needed for building indexed referential constraints.
  • CONSTRAINTS
    Directs the LOAD utility to extract only the information needed for building linked indexed referential constraints. Therefore, the LOAD utility will not extract the information needed for building indexes.
  • BOTH
    Directs the LOAD utility to extract the information needed for building both indexes and referential constraints. In this case, when you run the BUILD utility, you can begin with BUILD STEP2.
    BOTH is the default.
  • NO EXTRACT
    Directs the LOAD utility not to extract information needed for building either indexes or referential constraints. In this case, run STEP1 of the BUILD utility to do the extraction.
The remaining parameters are identical to the like-named parameters for a complete LOAD presented earlier in this section. Refer to this section for parameter descriptions.
Parameters for STEP 2
  • LOAD STEP2
    Directs the LOAD utility to perform only the second step of the load process.
    Execute this only after executing LOAD STEP1 without specifying WITHOUT PRESORT.
The remaining parameters are identical to the like-named parameters for a complete LOAD presented earlier in this section. Refer to this section for parameter descriptions.
Usage
How to submit the LOAD statement
You submit the LOAD statement only through the batch command facility. You must run the batch command facility in local mode.
How LOAD works
The LOAD utility reads records sequentially from an input file whose external name is SYS001.
The specifications in the syntax tell the LOAD utility how to interpret each record in SYS001 and which table(s) to load. The LRECL parameter controls whether the input file is fixed or variable length.
When to use LOAD
Use the LOAD utility to load an SQL-defined database for the first time or to expand it afterwards.
When not to use LOAD
Do not use the LOAD utility to load a non-SQL-defined database. Instead, use the FASTLOAD utility.
When to use a phased or stepped LOAD
Considerations for using the LOAD utility for a phased or stepped load and detailed loading procedures are discussed in .
SYS001 input file contents
The LOAD utility does not perform any type of data translation against the input records within the SYS001 file. As a result, each column value in the SYS001 file must be in the proper internal format as specified by the corresponding column's data format. For example, if a column has a format of DECIMAL(5), the corresponding field in the SYS001 record must be a valid packed decimal number occupying 3 bytes.
Sorting intermediate work files
If you run the load process in steps or phases, use the sort parameters in the SYSPCH file to sort the intermediate files.
Checking error messages
Use the
CA IDMS Messages and Codes Section
to locate messages associated with return codes received from the LOAD utility. Additionally, other useful information about any errors that occurred during LOAD processing are generated on the listing produced by the LOAD utility.
JCL Considerations
When you submit a LOAD statement to CA IDMS/DB through the batch command facility, the JCL to execute the facility must include statements to define:
  • The dictionary containing table definitions
  • The files containing the areas associated with the tables being loaded
  • The intermediate work files
  • Sort work files, if doing a complete LOAD
LOAD utility uses intermediate work files
Each step of the load process produces intermediate work files to be used by later steps. If you run a complete LOAD without separating steps or phases, the LOAD utility sorts data in the intermediate files between the steps automatically. If you run a phased or stepped LOAD, you must run the intermediate sorts.
When running a complete or phased LOAD, SYS002 andSYS003 must point to the same intermediate file. When the database being processed is so large that the intermediate file must be a multi-volume data set, it is required that all extents be physically allocated before jobstep initiation. If this is not possible, then a stepped LOAD should be used. When running a stepped LOAD, SYS002 and SYS003 must point to different intermediate files. The data that is output in SYS003 by each step is input to the next step in SYS002.
The following table shows the output of LOAD STEP1 and LOAD STEP2:
Step
Output
Size
STEP1 (WITH PRESORT)
SYS003
For each record:
(MAX SORT CONTROL KEY SIZE) + (MAX FOREIGN KEY SIZE) + (MAX SCHEMA RECORD SIZE) + 24
 
SYSPCH contains sort parameters
80 bytes
STEP1 (WITHOUT PRESORT)
SYS003
For each record:
(MAX SORT CONTROL KEY SIZE) + (MAX FOREIGN KEY SIZE) + 24
 
SYSPCH contains sort parameters
80 bytes
STEP2
SYS003
For each record:
(MAX SORT CONTROL KEY SIZE) + (MAX FOREIGN KEY SIZE) + 24
For more information about the generic JCL used to execute the batch command facility, see the section specific to your operating system.
Examples
Phased LOAD
The following sample statement instructs the LOAD utility to load data from an input file into various tables when a record in the input file at position 60 matches the where clause criteria.
load into load.a where position 60 = 'a'      into load.b where position 60 = 'b'      into load.h where position 60 = 'h' no validate lrecl 80;
Complete LOAD
The next example instructs the LOAD utility to perform a complete load of data from an input file into various tables when a record in the input file at position 60 matches the where clause criteria. In addition, it will load data into two tables when a record in the input file matches the character string associated with the column name in the where clause.
load into load.c where position 60 = 'C'      into load.d where position 60 = 'D'      into load.e where position 60 = 'E'      into load.f where position 60 = 'F'      into load.g where position 60 = 'G'      into load.m where mchar = 'm1'    (mchar    position 1   char(2),     mvchar   position 3   varchar,     mbin     position 7   binary(2),     mhalf    position 9   smallint,     mfull    position 11  integer,     mlong    position 15  longint,     mdec     position 23  dec(2,1),     mdecu    position 25  unsigned dec(3,3),     mnum     position 27  num(2,1),     mnumu    position 29  unsigned numeric(3,3),     mdate    position 32  date,     mtime    position 42  time,     mts      position 50  timestamp)      into load.m2 where position 1 = 'M2'    (mgraph   position 3   graphic,     mvgraph  position 5   vargraphic(4),     mreal    position 15  real,     mfloat1  position 19  float(4),     mfloat2  position 23  float(50),     mdp      position 31  double precision)      errors continue          lrecl 80;
Sample Output
Complete LOAD
The following report was generated after executing the LOAD statement in example 1 shown previously.
IDMSBCF                                              IDMS Batch Command Facility CONNECT TO SYSCAT; Status = 0 SET BATCH     HEADINGS OFF WIDTH PAGE 79 UNDERLINE '-'     SQLCODE ERROR     COMPRESS ON; *DEBUG IDMS OFF --   ****  FORMAT segments      **** FORMAT SEGMENT USERDB; File USERDB.EMPF1                blocks 1 to 50. Area USERDB.EMP_AREA             pages 5,001 to 5,050. Page size in file 4,096. File USERDB.ORGF1                blocks 1 to 50. Area USERDB.ORG_AREA             pages 5,051 to 5,100. Page size in file 4,096. File USERDB.EMPIX                blocks 1 to 50. Area USERDB.EMPIX_AREA           pages 5,101 to 5,150. Page size in file 2,000. --   ****  Load data into Tables      **** *DEBUG IDMS ON LOAD INTO LOAD.A    WHERE POSITION 60 = 'A'      INTO LOAD.B    WHERE POSITION 60 = 'B'      INTO LOAD.H    WHERE POSITION 60 = 'H'    NO VALIDATE     LRECL 80; IDMSLOAD  -   volser     PRESORT TABLES FOR LOAD     yy-mm-dd-hh.mm.ss IDMSLOAD  -  1 records processed for table LOAD.H IDMSLOAD  -  1 records processed for table LOAD.B IDMSLOAD  -  1 records processed for table LOAD.A IDMSLOAD  -  7 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 136 characters IDMSLOAD  -         PRESORT TABLES FOR LOAD     processing completed IDMSLOAD  -   volser     LOAD TABLES AFTER SORT     yy-mm-dd-hh.mm.ss IDMSLOAD  -  1 records processed for table LOAD.A IDMSLOAD  -  1 records processed for table LOAD.B IDMSLOAD  -  1 intermediate records for constraint LOAD.PKIX_B IDMSLOAD  -  1 intermediate records for constraint LOAD.FKIX_B IDMSLOAD  -  1 intermediate records for constraint LOAD.AB_S2 IDMSLOAD  -  1 records processed for table LOAD.H IDMSLOAD  -  1 intermediate records for constraint LOAD.PKIX_H IDMSLOAD  -  3 records were stored in the database IDMSLOAD  -  12 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         LOAD TABLES AFTER SORT     processing completed IDMSLOAD  -   volser     FILL IN OWNERS DBKEY     yy-mm-dd-hh.mm.ss IDMSLOAD  -  12 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         FILL IN OWNERS DBKEY     processing completed IDMSLOAD  -   volser     CONNECT UP INDEXES     yy-mm-dd-hh.mm.ss IDMSLOAD  -  9 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         CONNECT UP INDEXES     processing completed IDMSLOAD  -   volser     BUILD RECORD PREFIX     yy-mm-dd-hh.mm.ss IDMSLOAD  -         BUILD RECORD PREFIX     processing completed AutoCommit will COMMIT transaction Command Facility ended with warnings
Complete LOAD specifying column name
The next report was generated after executing the LOAD statement in example 2.
Some errors occurred during the load of tables LOAD.M and LOAD.M2. The LOAD utility provides useful information about the type and location of the error. Additional status information can be found in .
IDMSBCF                                              IDMS Batch Command Facility *DEBUG IDMS OFF CONNECT TO SYSCAT; Status = 0 SET BATCH     HEADINGS OFF WIDTH PAGE 79 UNDERLINE '-'     SQLCODE ERROR     COMPRESS ON; --   ****  Load data into Tables      **** *DEBUG IDMS ON LOAD INTO LOAD.C    WHERE POSITION 60 = 'C'      INTO LOAD.D    WHERE POSITION 60 = 'D'      INTO LOAD.E    WHERE POSITION 60 = 'E'      INTO LOAD.F    WHERE POSITION 60 = 'F'      INTO LOAD.G    WHERE POSITION 60 = 'G'      INTO LOAD.M WHERE MCHAR = 'M1'    (MCHAR    POSITION 1   CHAR(2),     MVCHAR   POSITION 3   VARCHAR,     MBIN     POSITION 7   BINARY(2),     MHALF    POSITION 9   SMALLINT,     MFULL    POSITION 11  INTEGER,     MLONG    POSITION 15  LONGINT,     MDEC     POSITION 23  DEC(2,1),     MDECU    POSITION 25  UNSIGNED DEC(3,3),     MNUM     POSITION 27  NUM(2,1),     MNUMU    POSITION 29  UNSIGNED NUMERIC(3,3),     MDATE    POSITION 32  DATE,     MTIME    POSITION 42  TIME,     MTS      POSITION 50  TIMESTAMP     )      INTO LOAD.M2 WHERE POSITION 1 = 'M2'    (MGRAPH   POSITION 3   GRAPHIC,     MVGRAPH  POSITION 5   VARGRAPHIC(4),     MREAL    POSITION 15  REAL,     MFLOAT1  POSITION 19  FLOAT(4),     MFLOAT2  POSITION 23  FLOAT(50),     MDP      POSITION 31  DOUBLE PRECISION     )      ERRORS CONTINUE          LRECL 80; IDMSLOAD  -   volser     PRESORT TABLES FOR LOAD     yy-mm-dd-hh.mm.ss SQLCODE = -4__     Extended reason code = 1026     Messages follow: DB001026 C-4M322: Data conversion error IDMSLOAD  -  error in table LOAD.M  -  I/P record sequence number 10 IDMSLOAD  -  error in column 32  -  column name is MDATE ERROR RECORD -─►   +0     D4F10001 C2F1FFFF 00020000 00020000 M1..B1..........                    +10    00000000 0002022C 022FF2C2 F0F2F2E7 ..........2B022X                    +20    E7E7E760 E7E760E7 E7E7E74B F3F04BF0 XXX-XX-XXXX.30.0                    +30    F1F1F3F9 F060F0F1 60F0F260 F1F64BF3 11390-01-02-16.3                    +40    F04BF0F1 4BF0F0F0 F0F040            0.01.00000 SQLCODE = -4       Extended reason code = 1025     Messages follow: DB001025 C-4M322: Data exception IDMSLOAD  -  error in table LOAD.M2  -  I/P record sequence number 16 IDMSLOAD  -  error in column 5  -  column name is MVGRAPH ERROR RECORD -─►   +0     D4F2C7F4 0004C7F1 C7F2C7C7 C7C70000 M2G4..G1G2GGGG..                    +10    00000000 00000000 00000000 00000000 ................                    +20    00000000 0000                       ...... IDMSLOAD  -  3 records processed for table LOAD.M2 IDMSLOAD  -  3 records processed for table LOAD.M IDMSLOAD  -  1 records processed for table LOAD.G IDMSLOAD  -  1 records processed for table LOAD.F IDMSLOAD  -  1 records processed for table LOAD.E IDMSLOAD  -  1 records processed for table LOAD.D IDMSLOAD  -  1 records processed for table LOAD.C IDMSLOAD  -  19 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 136 characters IDMSLOAD  -         PRESORT TABLES FOR LOAD     processing completed IDMSLOAD  -   volser     LOAD TABLES AFTER SORT     yy-mm-dd-hh.mm.ss IDMSLOAD  -  1 records processed for table LOAD.C IDMSLOAD  -  1 intermediate records for constraint LOAD.FKIX_C IDMSLOAD  -  1 intermediate records for constraint LOAD.BC_S2 IDMSLOAD  -  1 records processed for table LOAD.D IDMSLOAD  -  1 intermediate records for constraint LOAD.PKIX_D IDMSLOAD  -  1 intermediate records for constraint LOAD.FKIX_D IDMSLOAD  -  1 records processed for table LOAD.E IDMSLOAD  -  1 intermediate records for constraint LOAD.PKIX_E IDMSLOAD  -  1 records processed for table LOAD.F IDMSLOAD  -  1 intermediate records for constraint LOAD.FKIX_F IDMSLOAD  -  1 intermediate records for constraint LOAD.FKIX_FB IDMSLOAD  -  1 records processed for table LOAD.G IDMSLOAD  -  3 records processed for table LOAD.M IDMSLOAD  -  3 intermediate records for constraint LOAD.IX_M IDMSLOAD  -  3 records processed for table LOAD.M2 IDMSLOAD  -  3 intermediate records for constraint LOAD.IX1_M2 IDMSLOAD  -  3 intermediate records for constraint LOAD.IX2_M2 IDMSLOAD  -  11 records were stored in the database IDMSLOAD  -  34 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         LOAD TABLES AFTER SORT     processing completed IDMSLOAD  -   volser     FILL IN OWNERS DBKEY     yy-mm-dd-hh.mm.ss IDMSLOAD  -  34 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         FILL IN OWNERS DBKEY     processing completed IDMSLOAD  -   volser     CONNECT UP INDEXES     yy-mm-dd-hh.mm.ss IDMSLOAD  -  19 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         CONNECT UP INDEXES     processing completed IDMSLOAD  -   volser     BUILD RECORD PREFIX     yy-mm-dd-hh.mm.ss IDMSLOAD  -         BUILD RECORD PREFIX     processing completed IDMSLOAD  -   volser     VALIDATE INDEXES STEP 1     yy-mm-dd-hh.mm.ss IDMSLOAD  -  1 records processed for table LOAD.C IDMSLOAD  -  0 intermediate records for constraint LOAD.BC_S1 IDMSLOAD  -  0 intermediate records for constraint LOAD.BC_S2 IDMSLOAD  -  0 intermediate records for constraint LOAD.BC_S3 IDMSLOAD  -  1 records processed for table LOAD.D IDMSLOAD  -  0 intermediate records for constraint LOAD.LOAD_DD IDMSLOAD  -  1 intermediate records for constraint LOAD.LOAD_AD IDMSLOAD  -  2 records processed for table LOAD.E IDMSLOAD  -  0 intermediate records for constraint LOAD.LOAD_AE IDMSLOAD  -  0 records processed for table LOAD.F IDMSLOAD  -  0 intermediate records for constraint LOAD.LOAD_EF IDMSLOAD  -  0 intermediate records for constraint LOAD.LOAD_BF IDMSLOAD  -  0 intermediate records for constraint LOAD.LOAD_HF IDMSLOAD  -  1 records processed for table LOAD.G IDMSLOAD  -  0 intermediate records for constraint LOAD.LOAD_BG IDMSLOAD  -  0 records processed for table LOAD.M IDMSLOAD  -  0 records processed for table LOAD.M2 IDMSLOAD  -  19 intermediate records were written to SYS003 IDMSLOAD  -       largest SYS003 record size is 56 characters IDMSLOAD  -         VALIDATE INDEXES STEP 1     processing completed IDMSLOAD  -   volser     VALIDATE INDEXES STEP 2     yy-mm-dd-hh.mm.ss IDMSLOAD  -         VALIDATE INDEXES STEP 2     processing completed Status = 1        Extended Reason Code = 2991     Messages follow: DB002991 C1M349: Error detected doing a LOAD/BUILD/VALIDATE statement AutoCommit will COMMIT transaction Command Facility ended with warnings
More Information