DSP* - Cluster Data Space (ADADSP) Messages

ADACOM is initializing an ADADSP subtask for the processing of a Adabas Parallel Services cluster database that might subsequently be started.

No action is required for this informational message.

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 (PLXCB, cache, lock, or message) with the specified name and the specified size. A PLXCB data space is allocated during ADACOM initialization when it is requested by initialization parameters. Its size is based on the number of users specified to ADACOM. Cache, lock and message data spaces are allocated when the first Parallel Service database starts and 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.

Similarly, if a PLXCB dataspace entry is found in the IDTH prefix when attempting to allocate a new PLXCB, the IDTH prefix entry is first cleared.

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 ADADSP subtask of ADACOM has been asked to exit or to delete the shared dataspaces of an Adabas Parallel Services cluster, but one or more cluster nuclei are still active. An ADADSP subtask exits when an ADAEND command is issued to ADACOM for the associated the DBID/SVC (or DBID/IDTNAME) combination.

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

If ADACOM is canceled while Adabas Parallel Services nuclei are active on the associated database, these nuclei will most likely incur program checks and terminate abnormally. Thus, ADACOM should be canceled only when none of its ADADSP subtasks holds dataspaces for active Adabas Parallel Services nuclei, so as not to crash the Adabas Parallel Services cluster(s).

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.

The ADADSP subtask of ADACOM failed to obtain its own process token, which Adabas Parallel Services nuclei need to communicate with ADADSP. The ADADSP subtask terminates abnormally. Adabas Parallel Services nuclei for the associated database cannot start.

Contact your Software AG technical support representative for assistance.

The process token of the ADADSP subtask of ADACOM is invalid. The ADADSP subtask terminates abnormally. Adabas Parallel Services nuclei for the associated database cannot start.

Contact your Software AG technical support representative for assistance.

The ADADSP subtask of ADACOM failed to open its message output data set. The data set has the DD-name or link name Dssddddd in z/OS and z/VSE environments, or Diiddddd in BS2000 environments, where ss represents the last two digits of the SVC number, ii represents the fourth and last nonblank character of the IDT name, and ddddd is the database ID.

ADADSP will continue to run, but write its messages only to the console.

Contact your Software AG technical support representative for assistance.

This series of messages describe an attempt to allocate 64-bit addressable memory object of the specified type. The x before the "64" in the message identifies the type of 64-bit addressable memory: "S" (shared addressable memory), "G" (2G large page addressable memory), or "L" (1M large page addressable memory).

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 "Storage allocated but not backed by large pages" is printed, insufficient large pages of the type requested (1M large pages or 2G large pages) were available. Instead, storage was allocated and backed by pageable 4 kilobyte pages. In this case, the same action applies as given for the ADAN8G message.

If the "Error" line is printed, the storage allocation request failed. The message reports the system return code and reason code of the IARV64 macro used for the allocation request.

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 representative.

This series of messages describe an attempt to delete a shared 64-bit addressable memory object of the specified type. The x before the "64" in the message identifies the type of 64-bit addressable memory: "S" (shared addressable memory), "G" (2G large page addressable memory), or "L" (1M large page addressable memory).

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 "Error" line is printed, the deletion request failed. The message reports the system return code and reason code of the IARV64 macro used for the deletion request.

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 representative.

An attempt to obtain an ALET for the PLXCB dataspace was unsuccessful. The return and reason codes are from the operating system service. Under z/OS the service is ALESERV.

Use operating system documentation to understand the return and reason codes. Contact your Software AG technical support representative if the reason for the failure is unclear.

An attempt to acquire ADACOM local storage into which the PLXCB would be mapped was unsuccessful.

Contact your Software AG technical support representative if the reason for the failure is unclear.

The request to map the PLXCB into ADACOM local storage was unsuccessful. The return and reason codes are from the operating system service. Under z/OS the service is IARVSERV.

Use operating system documentation to understand the return and reason codes. Contact your Software AG technical support representative if the reason for the failure is unclear.

The PLXCB was mapped to the specified address in ADACOM local storage.

A nucleus requested ADACOM map the PLXCB dataspace into nucleus local storage. An attempt to obtain an ALET for the nucleus address space was unsuccessful. The return and reason codes are from the operating system service. Under z/OS the service is ALESERV.

Use operating system documentation to understand the return and reason codes. Contact your Software AG technical support representative if the reason for the failure is unclear.

A nucleus requested ADACOM map the PLXCB dataspace into nucleus local storage. The request to map the PLXCB into local storage was unsuccessful. The return and reason codes are from the operating system service. Under z/OS the service is IARVSERV.

Use operating system documentation to understand the return and reason codes. Contact your Software AG technical support representative if the reason for the failure is unclear.

An attempt to establish Resource Manager recovery routines was unsuccessful. These routines clear the IDTH prefix entry for a PLXCB dataspace in the event of ALET-related program checks in ADACOM that cannot be handled by normal error processing. The return and reason codes are from the operating system service. Under z/OS the service is RESMGR.

Use operating system documentation to understand the return and reason codes. Contact your Software AG technical support representative if the reason for the failure is unclear.

The ADACOM support for the specified Adabas Cluster Services or Adabas Parallel Services dataspaces is terminating.