DSPnnn-Cluster Data Space (ADADSP) Messages

ADACOM is starting the Adabas Parallel Services cluster based on settings provided by the first cluster nucleus to start.

Data space acquisition authority is granted to the first ADACOM to start and the name of that ADACOM job is displayed. Subsequent ADACOMs set to manage the same DBID will not be granted the authority to allocate data spaces, since they have already been allocated.

ADACOM is in the process of allocating a data space of the specified type (cache, lock, or message) with the specified name and the specified size. Data spaces are allocated only if a valid size is provided: see the ADARUN CLUCACHESIZE and CLULOCKSIZE parameters.

The operating system does not allow data spaces with sizes less than 4096 decimal bytes (internal error). If the allocation parameters are valid, the data spaces are allocated when the first cluster nucleus starts. Once data spaces are allocated for a cluster, they are not reallocated when subsequent cluster nuclei start.

If the first member nucleus of an ADABAS Parallel Services cluster attempts to allocate a dataspace, a dataspace may already exist, possibly as the result of a previous abend for which recovery was unsuccessful. The deletion attempt will generate DSP005 messages, after which the allocation attempt will be retried.

If you receive an error due to invalid sizes, review your ADARUN parameters, correct the error, and restart ADACOM. All other messages are for information only and require no action.

This message occurs when an ADAEND, P, or CANCEL command have been issued for ADACOM, but data spaces are still allocated for clusters that it manages.

ADACOM should come down automatically when the last cluster nucleus terminates. If it does not, issue a CANCEL command to terminate it.

The specified cluster data space is being deleted. Either the deletion is completed successfully or an IBM error code and reason code are returned.

If the data space is successfully deleted, no action is required. If an IBM error and reason code are returned, refer to your IBM manuals to identify and correct the specified error.

This series of messages describe an attempt to allocate a shared 64-bit addressable memory object of the specified type. If the allocation is successful, the address of the object is shown. If ADAIOR reports return code 12, the z/OS return and reason codes are shown. If the request resulted in an abend, the system and reason codes are shown.

If the first member nucleus of an ADABAS Parallel Services cluster attempts to allocate a S64 object, one may already exist, possibly as the result of a previous abend for which recovery was unsuccessful. The deletion attempt will generate DSP011 messages, after which the allocation attempt will be retried.

If the request fails, examine the z/OS IARV64 abend, return, and reason code descriptions in IBM documentation. If the cause is not clear, notify your Software AG technical support representitive.

This series of messages describe an attempt to delete a shared 64-bit addressable memory object of the specified type. If ADAIOR reports return code 12, the z/OS return and reason codes are shown. If the request resulted in an abend, the system and reason codes are shown.

Specifically, what is being deleted is the z/OS system affinity. A z/OS S64 memory object will not actually be deleted until all local affinities are also deleted. A local affinity is created when a Parallel Services nucleus establishes a connection with the S64 object in its own address space. Local affinities are deleted when the nucleus ends.

If the request fails, examine the z/OS IARV64 abend, return, and reason code descriptions in IBM documentation. If the cause is not clear, notify your Software AG technical support representitive.

The specified Adabas Parallel Services cluster is terminating.