Limitations and restrictions when using HSSP

Though HSSP can execute in a mixed-mode environment as well as concurrently with other programs, and in an environment with global sharing using IRLM; a program using HSSP can only execute as a non-message-driven BMP.

Other restrictions and limitations of HSSP include:

• Only one HSSP process can be active on an area at any given time. The /DIS AREA command identifies the IMSID of any HSSP job processing an area.
• HSSP processing and online utilities cannot process on the same area concurrently.
• Non-forward referencing while using HSSP is not allowed.
• Programs using HSSP must properly process the 'GC' status code by following it with a commit process.

Restrictions and limitations involving image copies include:

• The image copy option is available only for HSSP processing.
• The utility private buffers for HSSP processing must be located in 31-bit extended common storage (ECSA) and not in 64-bit common storage.
• HSSP image copying is allowed only if PROCOPT = H.
• The image copy process can only be done if a database is registered with DBRC. In addition, image copy data sets must be initialized in DBRC.

The following restrictions and limitations apply for PROCOPT=H:

• PROCOPT=H is allowed only for DEDBs.
• PROCOPT=H is not allowed on the segment level, only on the PCB level.
• Backward referencing while using HSSP is not allowed. You cannot use an HSSP PCB to refer to a prior UOW in a DEDB.
• Only one PROCOPT=H PCB per database per PSB is allowed.
• A maximum of four PROCOPTs can be specified, including H.
• PROCOPT=H must be used with other Fast Path processing options, such as GH and IH.
• When a GC status code is returned, the program must cause a commit process before any other call can be made to that PCB.
• An ACBGEN must be done to activate the PROCOPT=H.
• H is compatible with all other PROCOPTs except for PROCOPT=O.