ADASnn (Adabas SVC) System Messages

ADASIR has executed.

ADASIR found an invalid ID table entry.

Enter the decimal ID table value. ADASIR operation continues.

ADASIR has installed the Adabas SVC and acquired the necessary storage successfully.

ADASIR detected one of the following possible errors:

• IDT GETMAIN failure

• a nonzero return code from ADASVC on the 56 call

• ADASIR did not set the SSCTSUSE

• the operator terminated ADASIR

• ADASIR detected a non-VS1 environment

ADASIR terminates, freeing any resources acquired.

ADASIR found an invalid input parameter. The message may be followed by messages requesting reentry of the input parameters.

Enter the correct parameter or parameters and rerun ADASIR or enter "no" to end ADASIR operation.

This message occurs after error ADAS05 and requests that you verify the Adabas Vv ID table subpool where 'v' is the version of Adabas.

Enter either "228" (subpool 228 / fixed CSA), "241" (subpool 241 / pageable CSA) or enter "no" to end ADASIR operation.

This message occurs after error ADAS05 and requests that you verify the number of IDT entries.

Enter a value ranging one to four digits representing the IDT entry count or enter "no" to end ADASIR operation.

This message occurs after error ADAS05 and requests that you verify the SVC number for the version of Adabas specified.

Enter a three-digit SVC value ranging 200-255 or enter "no" to end ADASIR operation.

This and any associated ADASnn messages occur when ADASIR finds an incorrect SVC table entry or when message ADAS14 was answered with "p" (prompt option). The variable values in the message have the following meanings:

ADASIR follows this message with message ADAS10 asking if the SVC entry in error should be changed to the desired value.

This message occurs after message ADAS09 and requests that you confirm a change of the SVC table entry in error to a "desired" value proposed by ADASIR.

Enter "Y" (yes) to update the SVC entry. Entering any other value leaves the SVC entry as it was.

SVC with the number "svc" has been installed and the ID table storage for a count of "cccc" entries was successfully allocated.

ADASIR detected error "n", where "n" is one of the following:

The table entry for the Adabas SVC does not contain the address of the SVC for the specified version of Adabas. An attempt was made to install a previous version SVC using the ADASIR of the specified version.

Correct the error condition and re-IPL (if necessary) or rerun ADASIP.

ADASIR keeps the display of the previous ADAS11 or ADAS12 message on the screen if you specify "Y"; otherwise, the message display is removed and lost.

Enter "Y" to keep the message display; otherwise, the message is removed.

This message asks whether the operator should be prompted to update the SVC table entry (P) or not (N).

Enter "P" to prompt the operator for the SVC table entry; messages ADAS09 and ADAS10 occur when "P" is entered. Enter "N" (no prompt) to let ADASIR select the SVC value; message ADAS15 occurs when "N" is entered.

SVC "svc" was changed without a prompt being sent to the operator.

When ADASIP refreshes an existing Adabas SVC, the common storage area (CSA) associated with the old SVC load module and its associated IDT-related structures is released. If a PLXCB is found, its components are released as well. This message appears for each attempt to release storage:

ADASIP is being used to reinstall a copy of the ADABAS SVC, replacing an existing instance that was installed in CSA with ADASIP. ADASIP cannot release the CSA storage used by the existing instance because one or more z/OS Resource Manager routines may be pending.

ADASIP installs the new SVC instance and does not release the CSA used by the previous instance.

During termination, the server will release work areas that were obtained in the server's address space by the SVC to process user commands. The number of work areas is the high-water mark of the number of simultaneous processes.

Information only, no action required.

A z/OS Resource Manager recovery routine was entered after a server address space abend to release the IDTE.

If the release was successful, it will not be necessary to specify ADARUN FORCE=YES when restarting.

A z/OS Resource Manager recovery routine was entered after an abend to release a local or system affinity to a z/OS shared 64-bit addressable memory object. Any non-zero return code received from z/OS IARV64 is shown.

If the attempt fails, examine the IARV64 return and reason code description in IBM documentation. If the cause is not clear, notify your Software AG technical support representitive.