MASSADD (Add Records to Table) › How to Use

How to Use

MASSADD can run in Single User mode if NO is specified for the MULTUSE= keyword. Execute DBUTLTY using the following command format:

►►─ MASSADD DBID=n,DDNAME=d,TABLE=t ─┬─────────────────────────┬──────────────►
                                     └─ ,MULTUSE= ─┬─ YES ◄ ─┬─┘
                                                   └─ NO ────┘

 ►─┬─────────────────────────────┬────────────────────────────────────────────►◄
   └─ ,STARTAFT= ─┬─ 0 ◄ ──────┬─┘
                  └─ nnnnnnnn ─┘

Command

MASSADD

Invokes the function to accept input records for a single table and add those records to the table.

Required Keywords

DBID=

Specifies the database identifier for the database containing the table to which the records are being added.

Valid Entries:

DATACOM-ID of the database

Default Value:

(No default)

,DDNAME=

Specifies the JCL DDname of the input data. If the input source is a VSAM file, CA Datacom/DB processes it as an ordinary file.

A DDNAME is not acceptable for sequential input or output files if it is a name reserved for a CA Datacom area. Names with the following patterns are therefore not acceptable for DDNAME=:

• 3-byte names that end with XX, meaning they are reserved as either current or future CA Datacom control areas.
• 6-byte names that end with what could be a database ID from 001 through 999.
• 7-byte names that end with what could be a database ID from 1000 through 9999.

  The DDNAME= value is verified for acceptability to protect you from unintentionally causing data corruption. The DDNAME check is the default but optional. You can prevent the DDNAME check by using a DBSIDPR parameter (DBUTLTY_EDIT_DATA_SET=) for individual MUF environments. However, we recommend that you allow the DDNAME check.

  The data corruption risk involves not the DDNAME itself but the content of the data set. For example, suppose that you used the CXX DDNAME as the output of a backup. You then copied the CXX DD statement and changed the DDNAME of the copy to be acceptable, avoiding the DDNAME= error. The backup would, however, then overlay the CXX data set, which is not the intent of a backup.

  If you specify an unacceptable name for DDNAME=, message DB10059E is generated. For more information about DB10059, see the CA Datacom/DB Message Reference Guide.

  Note: We recommend that you allow DDNAME= check protection. You can, however, disable DDNAME= protection. To disable protection, assemble the DBSIDPR module used for this CA Datacom environment and specify NONE for the DBUTLTY_EDIT_DATA_SET= parameter. The default is DBUTLTY_EDIT_DATA_SET=FULL_1, which allows DDNAME= protection. For more information about DBSIDPR and DBUTLTY_EDIT_DATA_SET=, see the CA Datacom/DB Database and System Administrator Guide.

  Valid Entries:

  Any name valid to JCL specifications

  Default Value:

  (No default)

,TABLE=

Specifies the table in the database to which the records are to be added.

Valid Entries:

DATACOM-NAME of the table in the database specified

Default Value:

(No default)

Optional Keywords

,MULTUSE=

Specifies whether the add commands are to be directed to the MUF.

YES

MASSADD directs its input to the MUF. Direct commands to the MUF when adding records to a table defined with integrity constraints.

NO

MASSADD executes as a Single User job. In Single User mode, logging is not supported, and you do not have a log file to restart to ensure that the data and Index Areas are synchronized. Before using MASSADD, obtain a backup of the area in case you need to reload and try the function again.

Valid Entries:

NO or YES

Default Value:

YES

,STARTAFT=

Specifies a number of records to skip in the input data set before beginning to add records.

Valid Entries:

Any 1- to 8-character integer

Default Value:

0