Considerations when loading LOB data
Requirements when using referenced files
If your input data set contains a reference to the file that contains your LOB data, note the following requirements:
- If your referenced file is a PDS or PDSE, you must include a member name in the name provided in the input file.
If your referenced file is an HFS file, you must preallocate and mount the file system before running the load job.
Also, your input file must specify the full path name of the file, as in the following example:
/home/rdajdm/lobfr1
Copy data set requirements
If you specify COPY YES, you must enable dynamic allocation for at least the primary local LOB copy data set (DDTYPE LOCPLCPY). In general, LOADPLUS ignores any LOB copy data set allocation in your JCL.
LOADPLUS allocates your LOB copy data sets by using the following naming convention. If you include a DD statement in your JCL that uses the non-numeric portion of this naming convention as the ddname (or prefix), LOADPLUS terminates.
L[L|R][P|B]nnnnn
These variables indicate the following information:
- [L|R] is either L for local copy or R for the remote copy.
- [P|B] is either P for the primary copy or B for the backup copy.
- nnnnn is a number that LOADPLUS generates for that particular copy data set.
For example, LLP00002 indicates a local primary copy.
Incompatible options
The following table describes restrictions that apply to options when loading LOB data.
Additionally, LOADPLUS terminates if you specify a LOB column on any predicate of a WHEN statement.
Option | LOADPLUS response |
|---|---|
DEFAULTIF | Terminates if DEFAULTIF is specified on a LOB column |
FORMAT BMC FORMAT BMCUNLOAD FORMAT UNLOAD FORMAT CSV | Terminates |
INDEX UPDATE | Terminates |
INLINE YES | Changes this option to INLINE NO |
PRELOAD ANALYZE PRELOAD PAUSE | Terminates |
SKIPIX | Ignores this option for row ID or auxiliary indexes |
VALUE | Terminates if VALUE is specified on a LOB column |
Additional considerations
The following additional considerations apply when loading LOB data:
- If the LOB table space and index space are defined with DEFINE NO, LOADPLUS materializes these data sets only if the LOB column in the base table is participating in the load. For partitioned base table spaces, LOADPLUS materializes LOB spaces only for the partitions that are participating in the load.
- If you specify LOAD RESUME YES TABLE tableName REPLACE, LOADPLUS loads the base table as usual. The LOB table space for this table is loaded as if you specified LOAD REPLACE.
- You might need to increase the size of your BMCSYNC table. Estimate this allocation based on the following factors:
- Number of utilities that you are executing concurrently
- Number of LOB columns that you are loading or unloading
- Number of partitions in the base table space
- Number of files that you are allocating dynamically