You can execute this command in either Single User or Multi-User mode. Execute the LOAD function using the following command format.
►►─ LOAD ─ DBID=n,FORMAT= ─┬─ NONE ──────────────────────┬────────────────────► └─ BACKUP,DEVICE=x,DTFNAME=d ─┘ ►─┬────────────────────────────┬─┬───────────────────────┬───────────────────► └─ ,CLUSTER= ─┬─ SPARSE ◄ ─┬─┘ └─ ,INDEX= ─┬─ YES ◄ ─┬─┘ └─ DENSE ────┘ └─ NO ────┘ ►─┬───────────────┬─┬───────────────────────┬────────────────────────────────► └─ ,KBYTES=yyy ─┘ └─ ,LABEL= ─┬─ YES ◄ ─┬─┘ └─ NO ────┘ ►─┬─────────────────────────┬─┬────────────────────────┬─────────────────────► └─ ,LOADDUPS= ─┬─ NO ◄ ─┬─┘ └─ ,LOADID= ─┬─ YES ◄ ─┬─┘ └─ YES ──┘ └─ NO ────┘ ►─┬───────────────────────────┬─┬─────────────────────────┬──────────────────► └─ ,MISMATCH= ─┬─ FAIL ◄ ─┬─┘ └─ ,OPTIMIZE= ─┬─ NO ◄ ─┬─┘ └─ IGNORE ─┘ └─ YES ──┘ ┌─────────────────────┐ ►─┬───────────────────────────────────────┬─▼─┬─────────────────┬─┴──────────► └─ ,OPTION1='PRINT=CRITICAL,ROUTE=LOG' ─┘ └─ ,REMAP=fffttt ─┘ ►─┬─────────────────────────┬─┬────────────────────────┬─────────────────────► └─ ,RESETRCE= ─┬─ NO ◄ ─┬─┘ └─ ,REWIND= ─┬─ YES ◄ ─┬─┘ └─ YES ──┘ └─ NO ────┘ ►─┬──────────────────────┬─ ,SORT=n ─┬─────────────┬─────────────────────────► └─ ,SLACK= ─┬─ 0 ◄ ──┬─┘ └─ ,SORTWK=n ─┘ └─ nnnn ─┘ ►─┬──────────────────────┬───────────────────────────────────────────────────►◄ └─ ,STATS= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘ ►►─ LOAD ─ AREA=a,DBID=n,FORMAT= ─────────────────────────────────────────────► ►─┬─ NONE ───────────────────────────────┬───────────────────────────────────► ├─ BACKUP,DEVICE=x,DTFNAME=d ──────────┤ ├─ EXTRACT,DEVICE=x,DTFNAME=d,TABLE=t ─┤ └─ VAR,DEVICE=x,DTFNAME=d,TABLE=t ─────┘ ►─┬────────────────────────────┬─┬───────────────────────┬───────────────────► └─ ,CLUSTER= ─┬─ SPARSE ◄ ─┬─┘ └─ ,INDEX= ─┬─ YES ◄ ─┬─┘ └─ DENSE ────┘ └─ NO ────┘ ►─┬───────────────┬─┬───────────────────────┬────────────────────────────────► └─ ,KBYTES=yyy ─┘ └─ ,LABEL= ─┬─ YES ◄ ─┬─┘ └─ NO ────┘ ►─┬─────────────────────────┬─┬────────────────────────┬─────────────────────► └─ ,LOADDUPS= ─┬─ NO ◄ ─┬─┘ └─ ,LOADID= ─┬─ YES ◄ ─┬─┘ └─ YES ──┘ └─ NO ────┘ ►─┬──────────────────────────┬─┬────────────────────────┬────────────────────► └─ ,LOADPTN= ─┬─ FAIL ◄ ─┬─┘ └─ ,MULTUSE= ─┬─ NO ◄ ─┬─┘ └─ SKIP ───┘ └─ YES ──┘ ►─┬─────────────────────────┬─┬───────────────────────────────────────┬──────► └─ ,OPTIMIZE= ─┬─ NO ◄ ─┬─┘ └─ ,OPTION1='PRINT=CRITICAL,ROUTE=LOG' ─┘ └─ YES ──┘ ┌─────────────────────┐ ►─▼─┬─────────────────┬─┴─┬─────────────────────────┬────────────────────────► └─ ,REMAP=fffttt ─┘ └─ ,RESETRCE= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘ ►─┬────────────────────────┬─┬──────────────────────┬─┬───────────┬──────────► └─ ,REWIND= ─┬─ YES ◄ ─┬─┘ └─ ,SLACK= ─┬─ 0 ◄ ──┬─┘ └─ ,SORT=n ─┘ └─ NO ────┘ └─ nnnn ─┘ ►─┬─────────────┬─┬──────────────────────┬─┬─────────────────────┬───────────►◄ └─ ,SORTWK=n ─┘ └─ ,STATS= ─┬─ NO ◄ ─┬─┘ └─ ,URI= ─┬─ YES ◄ ─┬─┘ └─ YES ──┘ └─ NO ────┘
Command
Invokes the function to build or restore an area.
Required Keywords
Identifies the database containing the area to be loaded. Beginning with Version 11.0, LOAD by DBID may require more GETVIS than was required in previous versions.
DATACOM-ID of the database
(No default)
Specifies the device type for the input data set.
This parameter is not allowed if you specify FORMAT=NONE. This parameter is required when you specify any value other than NONE for FORMAT=.
DEVICE=VSAM specifies a VSAM cluster, accessed either directly or through a VSAM path. The other values specify physical sequential data sets.
When DEVICE=TAPE is specified, the system logical unit (SYS) number must be 5 (SYS005).
Use DEVICE=Snnn to specify a specific SYS number (for tape only).
DISK, VSAM, TAPE, or Snnn (Certain values from previous versions are still accepted but are treated as DISK.)
(No default)
Specifies the z/VSE JCL TLBL/DLBL name for the input data set.
This parameter is not allowed if you specify FORMAT=NONE. This parameter is required when you specify any value other than NONE for FORMAT=.
If DEVICE=TAPE, this name must match the name which you code in your z/VSE JCL TLBL statement. Otherwise, this name must match the name you code in your z/VSE JCL DLBL statement.
Any name valid to z/VSE JCL specifications
(No default)
Specifies the format of the input data.
Indicates the data being read was created by using the BACKUP function of DBUTLTY.
Specifies that the data being loaded is expanded fixed-length images of the data records. Such data can have been created by an application program or when the EXTRACT function of DBUTLTY is used. This option requires the TABLE parameter to direct the data to the correct table.
Note: The block size of the input file cannot exceed 32K - 1.
Specifies a null area load, no data being loaded. If the current index has entries for more than several hundred records, using SORT= with a value of 1 is recommended. As part of null loading a data area, CA Datacom/DB must search the index for entries pointing to previous data in the area and delete those entries. This deletion occurs more rapidly and completely if SORT=1.
Note: If you specify FORMAT=NONE, do not specify the DEVICE=, DTFNAME=, and TABLE= parameters.
Indicates that the input data has the IBM variable-blocked format. This option is used to load variable-length data to be processed by the CA Datacom VSAM Transparency and must be specified if the input is a VSAM file with variable-length records and you want to load directly to CA Datacom/DB. The table must be defined with user compression. See the CA Datacom VSAM Transparency User Guide for more information.
The VAR option requires the TABLE parameter to direct the data to the correct table. The VAR option is needed only on the first load of an area with input that is IBM variable-blocked format. Thereafter, the BACKUP function produces a format that can be input to the LOAD using the FORMAT=BACKUP option.
Valid Entries: BACKUP, EXTRACT, NONE, and VAR
Default Value: (No default)
Optional Keywords
Identifies the area to be loaded. If you omit the AREA= keyword and use LOAD DBID=, you can do a load of a full database. For additional comments relating to a database level load, see the description of the DBID= keyword.
DATACOM-NAME of the area in the database specified in the DBID= parameter
(No default)
We do not recommend that you specify a BLKSIZE=, because this parameter is ignored. It is provided for compatibility with an earlier version of CA Datacom/DB, because of the possibility that it may be part of previously specified JCL. If BLKSIZE is specified, it must be a number.
Specifies whether the data is to be loaded sparsely with each cluster to its own data block(s) or densely with data packed in the next block location with no regard to cluster value.
Should only be used during the initial loads of a multi-table area to build the required format and sequence of the input records to load the clustered area correctly.
Is required for normal clustering.
DENSE or SPARSE
SPARSE
Specifies whether the data indexes are to be built. Specifying NO is only intended for use with forward recovery in cases where the total recovery time is expected to be better by doing no data index work until a RETIX function is issued after the recovery. The index must be and is built with correct URI and space information.
NO or YES
YES
Specifies the number of 1024-byte blocks of memory needed to build the buffers for CA Datacom/DB. CA Datacom/DB chain writes up to one cylinder of data buffers if sufficient memory is available. In general, providing buffers to contain 5-6 tracks of data is optimal. You can use the following formula to calculate the value for this parameter:
blksize * #-of-blks-per-trk * #-trks * 2 / 1024
Where:
The data area block size. See the Directory (CXX) report for this value.
Number of blocks that fits on a track for the specified device type. You can see the Directory (CXX) report for this value.
Number of tracks that the user desires to have written for each physical I/O. This need not exceed the number of tracks per cylinder.
For double buffering.
A 4K block size on a 3390 device using two track writes:
(4096 * 12 * 2 * 2 / 1024) = 192
Note: The value obtained should be rounded up to the next whole number. The maximum value cannot exceed 9999. Sufficient memory is required for these extra data buffers.
1 to 9999 (integers only) multiplied by 1024 is the number of bytes requested through GETMAIN.
This number multiplied by 1024 is the number of bytes allocated for data buffer chaining in the partition. If loading by database, the number of bytes allocated is: (KBYTES*1024)*(areas in the database)). The LOAD does not run if sufficient memory is not available.
four tracks of memory buffering
Note: If a value is specified which results in less than 4 tracks of data, the input is rounded up during execution to be 4 tracks.
If DEVICE=TAPE (either TAPE or the Snnn form), specifies whether tape labels are processed. We recommend that you always use labeled tapes.
Note: LABEL= has no effect when DEVICE=DISK.
NO or YES
YES
Specifies whether to load duplicate Master or Unique Key values when the table is defined as having no duplicates. If CA Datacom/DB encounters a duplicate value for a Master Key for a table defined with no duplicate Master Key or for a Unique Key, CA Datacom/DB issues a return code 10 and aborts the run. If you specify YES for this parameter, CA Datacom/DB accepts your override and loads the key values. CA Datacom/DB produces a snap dump of the first 500 duplications. When MULTUSE=YES, the snap dumps are written to the Multi-User Facility Statistics and Diagnostics Area (PXX). See the section on using dumps in the CA Datacom/DB Database and System Administration Guide for a sample.
NO or YES
NO
(Applies to FORMAT=BACKUP) Specifies match on input row to a table in the area or database to be loaded using the table DATACOM-ID (YES) or the table DATACOM-NAME (NO). For a normal backup and load, this parameter is not important because the input row matches on both. However, when changing definitions between the backup and load, it is critical to a successful load. If changing table names or IDs, the matching allows flexibility. It may be necessary when backing up from one Directory (CXX) and loading into another.
If the input or output is a record in a partitioned table, the parameter must be specified as LOADID=NO to force matching on name. The name to be matched is only the Full Parent name or an unpartitioned table name.
If the table is a partition, a row can be rejected and not loaded if the partition value criteria does not match. How the utility handles the rejection is determined by the value set for the LOADPTN= parameter.
For more information about table partitioning and the LOAD function, see The LOAD Utility.
NO or YES
YES
Specifies how the utility handles a rejected row for a table partition. If it is set to SKIP, the row is ignored with no error condition. If it is set to FAIL, the row is dumped, and the utility function terminates.
FAIL or SKIP
FAIL
Specifies whether to load records when the length of the records on the backup do not match the record size in the Directory (CXX).
We strongly recommend that a backup be taken of the area to be loaded before using LOAD with MISMATCH=IGNORE, and that you exercise caution when executing a LOAD with MISMATCH=IGNORE. If an expanded row length exceeds the CXX table length and MISMATCH=IGNORE is specified, all data beyond the CXX length is truncated and therefore lost. If an expanded row length is less than the CXX table length and MISMATCH=IGNORE is specified, the balance of the expanded row is filled with spaces (hex 40s).
FAIL or IGNORE
FAIL
(For area level DBUTLTY control only.) Specifying MULTUSE=YES allows a single area in a database to be loaded with no loss of read and update access to other areas in the database. When MULTUSE=YES, the function executes in a new format that is a combination of Multi-User Facility and Single User modes. The database involved must be able to be opened for update in the Multi-User Facility address space. The area must have no tables open. If the database is currently open, CA Datacom/DB closes this area with the area close (you would need to close the area yourself only if the database is open and you need Multi-User Facility to close it, so that any type of open data set lock can be released, which could be necessary in order to scratch and reallocate the data set). Once started, the function does not allow other tasks to open any tables in the area being processed. Other tables in the involved database, but not in the area, may be open for read or update in the same Multi-User Facility. With MULTUSE=YES:
When MULTUSE=YES, the SORT= option must be specified but not as zero (0). The data area must currently be set to the URI format. This can be done with a data INIT or a previous LOAD using URI=YES. The keyword URI=NO may not be specified (the area may only be loaded in the URI format).
When MULTUSE=NO is specified or is allowed to default in the LOAD and RETIX functions, the function executes as in versions prior to Version 11.0, that is, the database involved may not be open for update, and all processing executes in the Single User mode.
For more information on area level control, see Area Level DBUTLTY Control.
NO or YES
NO
Specifies whether the Index entry creation optimization option is to be used.
All Index entries are not to be completed until the load terminates. This option enhances performance by deferring Index pointer validation and complete Index structure update.
Note: OPTIMIZE=YES is ignored if MULTUSE=YES is also specified.
Note: When YES is selected, if this load fails for any reason, reinitialize the Index Area. If any other data areas are already loaded, re-create the Index entries using the RETIX function of DBUTLTY, or reload all areas. If you select YES, you must also specify a value in the SORT= parameter.
All Index entries are to be validated as they are created.
NO or YES
NO
(z/VSE only) Specifies the options for the associated sort/merge program application. The values for this keyword must be 44 characters or less and they must be enclosed in quotes. Depending on the features of your installation's sort, the values that apply to this keyword can vary. CA Datacom/DB does not edit anything that you place inside of the quotes.
Any values that your installation's sort allows. These values must be less than 44 characters and be inside quotes.
CRITICAL for PRINT
LOG for ROUTE
(Applies to FORMAT=BACKUP, values are ignored by other formats.) When LOADID=NO is specified for matching input data to output tables based upon table name, REMAP= allows a table name to be remapped. This parameter allows you to load data when the table has been renamed between the backup and the load.
To use REMAP=, specify six characters fffttt after REMAP=, where fff is the input table name (the from table on input) and ttt is the output or current Directory (CXX) name (the to table in the database ID that is being loaded). CA Datacom takes the data records for the from table and loads them into the to table, effectively renaming the table.
Message DB13022E can occur if the BACKUP used RECID=YES.
six characters fffttt as previously described.
(No default)
(Applies to FORMAT=BACKUP, values are ignored by other formats.) When a table is defined with recovery, the Record Control Element (RCE) contains the Transaction Sequence Number (TSN) of the transaction that last did maintenance to a record. CA Datacom/DB uses this information to know if secondary exclusive control is necessary on a record. The master transaction sequence number is stored and maintained in the Log Area. If you have multiple Log Areas that share in any context the updating of a data area (though obviously not at the same time), the master transaction sequence number must be in a different range or unnecessary waits may occur. Using RESETRCE can prevent this from happening.
For example, if you have production and test systems using similar numbers through the Log Area, you could use RESETRCE to ensure that no waiting is done on the wrong transaction. Such as, if you had backed up production data, loaded it to the test system, and initialized the Log Area on a system, the transaction sequence numbers would be repeated on one system, resulting in possible waits on the wrong transaction. A backup and load with RESETRCE would prevent this condition, avoiding unnecessary waits.
Note: For EXTRACT input or when RESETRCE=YES is specified, the TSN is set to zero. Otherwise, the TSN is copied from the BACKUP record.
NO or YES
NO
If DEVICE=TAPE (either TAPE or the Snnn form), YES indicates that the tape is to be rewound before OPEN and after CLOSE. NO indicates no rewind before OPEN or after CLOSE. If omitted, the tape is rewound before the OPEN and rewound with unload after the CLOSE.
Note: REWIND= has no effect when DEVICE=DISK.
NO or YES
The tape is rewound before the OPEN and rewound with unload after the CLOSE.
Specifies the number of bytes to reserve in each data block for future expansion of records in that block, or for addition of records when using a space reclamation option. The number entered applies only to blocks loaded to an area during this execution of the LOAD function. Blocks not loaded with data use the SLACK value specified in the AREA definition in CA Datacom/DB.
A number that is less than the block size, up to a maximum of 9999.
0
Activates the Index entry sort option.
Note: The sort option is required when specifying the LOAD function for the full database, or if MULTUSE=YES.
When you specify a value greater than zero, no Index entries are created as the data is loaded. The required Index entries are sorted at the end of the data LOAD and are merged into the Index in ascending sequence. Selecting this option enhances the performance of the LOAD process for large databases.
The SORT option is highly recommended when the number of records exceeds several hundred. Specify that the sort is to be used by entering a non-zero number. If sort is selected by entering a non-zero number, the Index entries in the Index Area (IXX) are not deleted by a separate Index pass. The Index Area is updated and only the Index blocks that reflect change are written.
If the SORT option is used, the partition size should be at least nine megabytes (9MB).
Note: Do not specify over 99 million unless you verify that the sort package you are using allows a larger number.
Specifying SORT=0 (or any number of zeros) is the same as not specifying the keyword.
Many features introduced in previous releases require a non-zero value for SORT=, and the following two features are also blocked during LOAD or RETIX executions, when the sort option is not being used are, as follows:
Most user-JCL is expected to already have a non-zero value for SORT= specified. If, however, a user has a LOAD or RETIX function coded in their JCL with SORT=0 specified or defaulted (SORT= not specified at all), this information is added to the history report, and the first time in each MUF execution that an area is opened in a database that has a LOAD or RETIX coded without the sort option, an informational message is generated. The message alerts you to the condition and can therefore help you know to first add the sort option, then see the results.
Note: A load with FORMAT=NONE (and either SORT=0 or SORT= not specified) is handled by DBUTLTY in a special, "simulated sort" manner and therefore does not require SORT= to be specified as a number greater than 0. For consistency, however, we recommended that SORT=1 be specified with FORMAT=NONE.
Two messages related to using LOAD and RETIX without the sort option are messages DB02809I and DB13128E. For details about these messages, see the CA Datacom/DB Message Reference Guide.
0 to 99999999999
(No default)
Specifies the number of sort work areas.
Note: Do not specify a 2-digit number unless the sort package you are using allows a 2-digit number. Sort packages that do not support a 2-digit number can fail in an unpredictable manner, if you specify a 2-digit number.
0 to 99
Note: Do not use two-digit numbers unless the SORT package to be used supports the larger number.
3
Specifies whether compression statistics are to be computed and displayed.
YES specifies to compute and print the compression statistics. Specifying YES when no tables are compressed significantly increases LOAD runtime. Only use YES to determine the space savings of compression.
NO or YES
NO
Indicates a single table is to be loaded. This parameter is required when EXTRACT or VAR is specified for FORMAT. It cannot be specified when FORMAT=BACKUP or FORMAT=NONE.
DATACOM-NAME of a table in the database and area being loaded
(No default)
Specifies whether to use URI record ID formats. The URI format is required for SQL access and for tables with unique keys. All tables in the area must be defined to CA Datacom/DB with RECOVERY=Y.
If you have defined the tables in this area with unique keys, you must specify URI=YES.
When the backup being loaded was created with RECID=YES, DBUTLTY ignores this keyword and loads the data area using the record ID format of the backup.
Note: URI=NO may not be specified if MULTUSE=YES is specified. Allowing the code to run in the URI mode is highly recommended.
For further information about URI, see the CA Datacom/DB Database and System Administration Guide.
NO or YES
For RECID=YES backups: format of the backup
YES
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|