Unload and reload function restrictions

The following restrictions apply to the database unload and reload function:
  • Only one UNLOAD or RELOAD command per job step can be specified, and it must be the only command in the PFPSYSIN input.

  • When executing an UNLOAD process, the database must be offline. This process is not designed to execute against an online DEDB.

  • You cannot change segment names of root segments (except in databases consisting only of root segments). You can change other segment names.

  • You cannot change the hierarchical path of a dependent segment (cannot insert segments between existing segments).

  • You cannot change a direct dependent segment to an SDEP or an SDEP to a direct dependent segment.

  • If SMS-managed storage classes are used for initialized areas and the defined cluster spans the area across multiple volumes, you must allocate the area to a guaranteed space storage class. Fast Path Reorg/EP will not format out any portion of the area that resides on a candidate volume.

Note

If you use the CONFIGURE_AREA, CONFIGURE_IOVF, CONFIGURE_RAA or CONFIGURE_SDEP keyword with the ALLOCATE subcommand to dynamically define the output area for a RELOAD command process, do not allocate the area to a guaranteed space storage class. If you do so, the guaranteed space storage class will override the configuration specifications.

  • When a change is made to the key of a dependent segment with an unload or reload process, segments must remain in ascending key sequence under the root key. Fast Path Reorg/EP does not have a facility to resequence the dependent segments. A failure of the reload process occurs if the change to a dependent segment key is not specified in ascending key sequence.

  • If an image copy is used as input to the database unload function, an IBM MVS dataspace is used. The size of the required dataspace cannot be greater than 2GB. If this limit is exceeded, Fast Path Reorg/EP issues an error message and terminates.

Note

The 2 GB limit applies to the combined size of the IOVF and SDEP portion of the database, not the size of the image copy. Fast Path Reorg/EP tries to minimize the size of the required dataspace by using an internal compression algorithm on the IOVF and SDEP blocks.

  • When using SDEP_PROCESS=PHYSICAL on the UNLOAD command, you cannot perform any of the following tasks:

    • Change the CI size of the area

    • Change the compression parameters for the SDEP segment

    • Specify the OUTPUT subcommand for the SDEP segment

    • Use the FABEUR6 and FABEUR7 program extensions to process the unload file

    • Modify the randomization parameters such that root segments are randomized to a different area

    • Create a single unload file from multiple areas (you must create an unload file for each area)

  • When a full-function unload file with compressed segments is input to the reload step, do not convert segments from VL to FL or FL to VL:

    • FL is fixed length.

    • VL is variable length.

Converting the segments causes unpredictable results.




This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments