ADAS* (Adabas SVC) System Messages

#### Search Results

Search

# ADAS* (Adabas SVC) System Messages

### Overview of Messages

`ADAS00 | ADAS01 | ADAS03 | ADAS04 | ADAS05 | ADAS06 | ADAS07 | ADAS08 | ADAS09 | ADAS10 | ADAS11 | ADAS12 | ADAS13 | ADAS14 | ADAS15 | ADAS16 | ADAS17 | ADAS20 | ADAS21 | ADAS30 | ADAS31 | ADAS32 | ADAS33 | ADAS34 | ADAS35 | ADAS36 | ADAS37 | ADAS39`

ADAS00 | SIRMVS ( yyyy - mm - dd, SM=level, ZAP=zap-number)
Explanation | ADASIR has executed.
yyyy-mm-dd | the ADASIR assembly date
level | the maintenance (SM) level
zap-number | the highest zap number applied

ADAS01 | subsysname enter number of Adabas Vv ID table entries (1-nn)
Explanation | ADASIR found an invalid ID table entry.
Action | Enter the decimal ID table value. ADASIR operation continues.

ADAS03 | subsysname Adabas Vv ID table for SVC svc initialized
Explanation | ADASIR has installed the Adabas SVC and acquired the necessary storage successfully.

ADAS04 | subsysname Adabas Vv ID table initialization error
Explanation | 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
Action | ADASIR terminates, freeing any resources acquired.

ADAS05 | subsysname Adabas Vv ID table parameter(s) error
Explanation | ADASIR found an invalid input parameter. The message may be followed by messages requesting reentry of the input parameters.
Action | Enter the correct parameter or parameters and rerun ADASIR or enter "no" to end ADASIR operation.

ADAS06 | subsysname Enter Adabas Vv ID table subpool (228 or 241) or "NO" to abort ID table initialization
Explanation | This message occurs after error ADAS05 and requests that you verify the Adabas Vv ID table subpool where v is the version of Adabas.
Action | Enter either "228" (subpool 228 / fixed CSA), "241" (subpool 241 / pageable CSA) or enter "no" to end ADASIR operation.

ADAS07 | subsysname Enter number of Adabas Vv ID table entries or "NO" to abort ID table initialization
Explanation | This message occurs after error ADAS05 and requests that you verify the number of IDT entries.
Action | Enter a value ranging one to four digits representing the IDT entry count or enter "no" to end ADASIR operation.

ADAS08 | subsysname Enter Adabas Vv SVC number (200-255) or "NO" to abort ID table initialization
Explanation | This message occurs after error ADAS05 and requests that you verify the SVC number for the version of Adabas specified.
Action | Enter a three-digit SVC value ranging 200-255 or enter "no" to end ADASIR operation.

ADAS09 | subsysname Adabas Vv SVC svc table entry at svc-addr invalid is bad-entry bad-entry should be good-entry good-entry
Explanation | 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:
v | version of Adabas
svc | SVC number
svc-addr | address of the SVC table entry
bad-entry | current SVC table entry value in error
good-entry | desired SVC table entry value
Action | ADASIR follows this message with message ADAS10 asking if the SVC entry in error should be changed to the desired value.

ADAS10 | subsysname should SVC table entry be changed ('Y') or should Adabas ID table initialization be aborted ('N')
Explanation | 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.
Action | Enter "Y" (yes) to update the SVC entry. Entering any other value leaves the SVC entry as it was.

ADAS11 | subsysname Adabas Vv ID table for SVC svc initialized with cccc entries IDT:address IDTExt:address FIIBS:address RClass:class SSCT:address SVC:address VRS:vrs DATE:date
Explanation | 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, the SAF class name for authorization and the release and assembly date for the SVC are also provided in the message.
Action | No action is required for this informational message.

ADAS12 | subsysname Adabas Vv ID table initialization error n
Explanation | ADASIR detected error n, where n is one of the following:
1 | The GETMAIN for the ID table was unsuccessful.
2 | The Adabas SVC request to initialize the ID table returned a nonzero return code. Probable cause is that the subsystem name in the IEFSSNxx member of SYS1.PARMLIB does not match the contents of ADASVC + x'28'.
3 | The Adabas SVC request to initialize the ID table did not set the correct value in the SSCT. Probable cause is an incorrect SVC number.
4 | The operator terminated initialization.
7 | The SVC table entry for the Adabas SVC does not contain the address of the Adabas SVC.
10 | SVCUPDTE macro failure.
11 | The GETMAIN for the FIIBS and IDT extension tables was unsuccessful.
Action | Correct the error condition and re-IPL (if necessary) or rerun ADASIP.

ADAS13 | subsysname leave message ADAS11 or ADAS12 (N or Y)
Explanation | 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.
Action | Enter "Y" to keep the message display; otherwise, the message is removed.

ADAS14 | subsysname prompt operator to update SVC table entry N or P
Explanation | This message asks whether the operator should be prompted to update the SVC table entry (P) or not (N).
Action | 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.

ADAS15 | subsysname SVC svc table entry changed without prompting operator
Explanation | SVC svc was changed without a prompt being sent to the operator.

ADAS16 | Existing ADASVC svc uses subsystem subsys
Explanation | ADASIP is being used to reinstall a copy of the Adabas SVC. Either the specified subsystem is currently being used by another SVC, or the specified SVC currently specifies a different subsystem.
Action | If the error relates to the specified subsystem, it is followed by user ABEND 435. If the error relates to the specified SVC number it is followed by user ABEND 436. User ABEND 436 may be overridden by the ADASIP FORCE=Y parameter.

ADAS17 | IDT for SVC svc has active IDTE for target target
Explanation | ADASIP is being used to reinstall a copy of the Adabas SVC. The IDT being used by the currently installed SVC has a possibly active target as indicated by an active IDTE. There is one message for each such target.
Action | It is followed by user ABEND 437. This ABEND may be overridden by the ADASIP FORCE=Y parameter.

ADAS20 | At address, length bytes action area-description
Explanation | 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:
address | CSA area address, in hexadecimal
length | CSA area length, in hexadecimal
action | One of the following: CSA RELEASED RELEASE FAILED
area-description | One of the following: Replaced SVC IDTH / IDT / IIBS Cluster Segment PLXCB Base PLXCUSER Segment SMP Segment Fat IIBS IDTH / IDTE IDT Extension SVC Fixed Area

ADAS21 | Replaced SVC CSA not released, nn pending resource managers
Explanation | 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.
Action | ADASIP installs the new SVC instance and does not release the CSA used by the previous instance.

ADAS30 | nn SVC work areas released
Explanation | 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.
Action | Information only, no action required.

ADAS31 | Service ABTERM resource manager { ADDRSPC TERM | TASK TERM } Service ABTERM resource manager released IDTE
Explanation | A z/OS Resource Manager recovery routine was entered after a server address space abend to release the IDTE.
Action | If the release was successful, it will not be necessary to specify ADARUN FORCE=YES when restarting.

ADAS32 | S64 scope affinity resource manager event S64 object at address S64 object user token is token S64 scope affinity released S64 scope affinity released return-code/reason-code
Explanation | 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.
Action | 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.

ADAS33 | Security subsystem denied authorization Security subsystem or APF authorization is required APF authorization is required Security subsystem error SAF/Ret/Rsn SAF return-code/security-subsystem-return-code/security-subsystem-reason-code
Explanation | The nucleus attempted to initialize or access an ADASVC function that required authorization.
Action | 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.

ADAS34 | Invalid pointer SAGVT Invalid pointer to SAGVT at addr cleared hex-storage-bytes-0-15 hex-storage-bytes-16-31
Explanation | 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.
Action | Contact your Software AG technical support representative.

ADAS35 | SAGVT {installed|reinstalled}
Explanation | 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.
Action | No action is required for this informational message.

ADAS36 | Service ABTERM resource manager task term cleanup
Explanation | A z/OS resource manager recovery routine was entered after a server address space ABEND to POST any incomplete commands and release the IDTE.
Action | No action is required for this informational message.

ADAS37 | ENFReq {Listen | Delete} event 53 return code rc
Explanation | 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.
Action | Examine the ENFREQ return code description in IBM documentation. If the cause is not clear, notify your Software AG technical support representative.

ADAS39 | ADADSP DBID dbid SVC svc AbTerm resource manager {AddrSpc term | Task term | cleared ALET}
Explanation | An ADADSP subtask in ADACOM failed such that it did not clean up the IDTH prefix entry for a PLXCB dataspace. The Resource Manager routine attempted recovery at either address space or task termination. If an ALET for this DBID/SVC combination was found in the IDTH prefix entry, the entry is cleared.
Action | Restart the failed ADACOM subtasks and any affected nuclei. Contact your Software AG technical support representative if the reason for the termination is unclear.