Loading logical children (PROCOPT=L)

A logical child is a segment that has a physical parent and a logical parent.

A logical relationship allows for a different view of segments in a database by providing a new set of pointers (LP,LT,LCH). HALDB only uses the LP equivalent as an EPS pointer. The LP-EPS pointer requires the ILK of the logical parent, which is not known at that time.

HALDB does not allow loading of logical child segments because there is no WF1 work file, and the extended pointer set (EPS) of the logical parent and the paired segment are unavailable at load time.

WF1 is the work file created during reorganization reload or by a database load application.

In addition, load segments in the hierarchy below the logical child segment (variable intersection data) are not allowed.

IMS HALDB Toolkit improves this situation by allowing these load segments with the following restrictions:

• The logical child segment must contain the LPCK in the IO area.
• The application will receive a BB status code.

  The segments (1 child and dependents) are inserted later.

• JCL is structured as follows:
  • Step 1 is the load program. File DFSURWF1 is used to store the delayed segments.
  • Step 2 is prefix update. This step inserts all delayed segments. All WF1 data sets created by step 1 must be included in the DFSURWF3 file.
• You must change your JCL as follows:
  • Use IHCWRC00 instead of DFSRRC00 to accommodate steps 1 and 2
  • Include the SIHCLOAD target load library in the STEPLIB
• When the IMS management of ACBs is enabled:
  • The IMS Catalog Definition exit routine (DFS3CDX0) must be specified in the STEPLIB concatenation in both steps 1 and 2. The DFSDF and IMSID parameters are not supported.
  • IMS HALDB Toolkit ignores the IMS DD statement.

At the end of the load (prefix update), all databases are labeled IC needed unless they are defined as NONRECOV.