Using Hiperspace for Temporary File Storage

If you do not have sufficient memory to store documents temporarily, you may want to use hiperspace memory. Three tags affect how EngageOne™ Enrichment uses hiperspace: the Input group <IO> tag, the Environment group <HIPERMAX> tag, and the Environment group <HIPERTRANSFER> tag.

Note: Hiperspace is only available on mainframe systems when you use the IBM C run-time libraries.

<HIPERMAX> Tag

If you set <IO> to TRANSFER or OPTIMUM, the Environment group <HIPERMAX> tag specifies the maximum amount of hiperspace to use before switching to disk. The valid range for <HIPERMAX> is 1K to 2048M.

Note: If your application uses all available hiperspace, EngageOne™ Enrichment will abend when it tries to transfer to disk. To avoid this, set <HIPERMAX> to an amount less than the maximum available hiperspace.

<HIPERTRANSFER> Tag

The Environment group <HIPERTRANSFER> tag defines the size of a memory area used by EngageOne™ Enrichment to send data to and from hiperspace. The transfer area is only used if hiperspace is used. The valid range for <HIPERTRANSFER> is 0K to 2M.

Note: If EngageOne™ Enrichment issues a PDR2164 or PDR2165 error, it is probably caused by a hiperspace environment issue. Lower your <HIPERTRANSFER> setting until EngageOne™ Enrichment processes without issuing the error. If the error persists, set <HIPERTRANSFER> to 0 so EngageOne™ Enrichment only uses memory and disk for storage.

C run-time defaults to a transfer area size of 16K. EngageOne™ Enrichment's default for <HIPERTRANSFER> is 100K. We recommend that you set <HIPERTRANSFER> no lower than 16K, unless you set <IO> to OPTIMUM and want EngageOne™ Enrichment to go from memory straight to disk. In this case, as above, set <HIPERTRANSFER> to 0.