ADAS* (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. The addresses of the SVC, major CSA data structures, and the release and assembly date for the SVC are also provided in the message.

No action is required for this informational message.

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

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

The nucleus attempted to initialize or access an ADASVC function that required authorization.

Provide the appropriate authorization. If the message indicates a security subsystem error, contact your security administrator or your Software AG technical support representative for assistance.

The Software AG Vector Table (SAGVT) is an internal z/OS CSA structure anchored in a CVT-based field assigned by IBM to Software AG. During SVC installation and initialization, Adabas SVC processing found an entry in Software AG's assigned anchor slot that did not point to a valid SAGVT. This may be because another vendor's product is using Software AG's assigned slot or the storage was corrupted.

The invalid address and 32-bytes of storage at that address are dumped and included in the message to aid in problem determination. The SAGVT anchor slot is cleared. Expect a subsequent ADAS35 message as a new SAGVT is installed.

This message appears in red on the operator's console and does not scroll off the display.

Contact your Software AG technical support representative.

The Software AG Vector Table (SAGVT) is an internal z/OS CSA structure anchored in a CVT-based field assigned by IBM to Software AG. During SVC installation and initialization, Adabas SVC processing did not find a usable SAGVT.

If the IBM-assigned pointer to the SAGVT is zero, a new SAGVT is allocated and installed.

If the IBM-assigned pointer to the SAGVT identifies a SAGVT version older than the one known to the installing ADASVC program, the SAGVT is reinstalled, replacing the older one.

No action is required for this informational message.

A z/OS resource manager recovery routine was entered after a server address space ABEND to POST any incomplete commands and release the IDTE.

No action is required for this informational message.

A non-zero return code was received from an ENFREQ request to activate or delete a z/OS Event Notification Facility (ENF) exit that detects time zone and leap second changes. The return code (rc) is given in the message.

Examine the ENFREQ return code description in IBM documentation. If the cause is not clear, notify your Software AG technical support representative.