ADADSP messages apply only to Adabas Parallel Services.
All of the following messages are printed first to the system log and then later to the Dssdddd data set (where ss is the last two digits of the SVC number and ddddd is the DBID) that was automatically created for cluster data space message output.
Each message begins with a timestamp in the format hh:mm:ss, followed by the message number and text.
DSP001 | DSP002 | DSP003 | DSP004 | DSP005 | DSP006 | DSP007 | DSP008 | DSP010 | DSP011 | DSP099| DSP001 | Initializing DBID=dbid [SVC=svc] [IDTNAME=idtname] |
| Explanation |
ADACOM is initializing an ADADSP subtask for the processing of a Adabas Parallel Services cluster database that might subsequently be started. |
| Action |
No action is required for this informational message. |
| DSP002 | Data space acquisition authority acquired Data space acquisition handled by job jobname |
| Explanation |
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. |
| DSP003 | Dataspace being allocated is {cache | lock | message} Name is data-space-name {Size in decimal bytes: number-of-bytes | not allocated - length is zero | not allocated - size is less than 4096 bytes} {function completed normally | data spaces already allocated} Dataspace may already exist, attempting delete |
| Explanation |
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. |
| Action |
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. |
| DSP004 | Unable to delete/exit - NUCS up Checking every 5 seconds Next message in 5 minutes |
| Explanation |
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. |
| Action |
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). |
| DSP005 | Dataspace being deleted is data-space-name Function completed normally | Error: abend code abend-code, reason code reason-code | Error: return code ret-code, reason code reason-code} |
| Explanation |
The specified cluster data space is being deleted. Either the deletion is completed successfully or an IBM error code and reason code are returned. |
| Action |
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. |
| DSP006 | Unable to secure process token |
| Explanation |
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. |
| Action |
Contact your Software AG technical support representative for assistance. |
| DSP007 | Length of process token too long |
| Explanation |
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. |
| Action |
Contact your Software AG technical support representative for assistance. |
| DSP008 | Unable to open output data set |
| Explanation |
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. |
| Action |
Contact your Software AG technical support representative for assistance. |
| DSP010 | S64 object being allocated is {cache | lock | message} S64 object may already exist at address Attempting delete Allocation token is token Requested size in MB (rounded) is size Function completed normally Address is\ address Error: return code 12, reason code zOS-return-code zOS-reason-code Error: abend code system-code, reason code reason-code |
| Explanation |
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. |
| Action |
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. |
| DSP011 | S64 object being deleted is {cacne | lock | message} S64 object may already exist at address Allocation token is token Actual size in MB is size Address is address Function completed normally Error: return code 12, reason code zOS-return-code z/OS-reason-code Error: abend code system-code, reason code reason-code |
| Explanation |
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. |
| Action |
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. |
| DSP099 | SVC=svc, DBID=dbid function exiting |
| Explanation |
The specified Adabas Parallel Services cluster is terminating. |
