Version 8.1.4
 —  Messages and Codes  —

ADAS* (Adabas SVC) System Messages

Overview of Messages

ADAS00 | ADAS01 | ADAS03 | ADAS04 | ADAS05 | ADAS06 | ADAS07 | ADAS08 | ADAS09 | ADAS10 | ADAS11 | ADAS12 | ADAS13 | ADAS14 | ADAS15 | ADAS20 | ADAS21 | ADAS30 | ADAS31 | ADAS32 | ADAS33

ADAS00 SIRMVS ( yy yy - 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 ADAB 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 ADAB Adabas Vv ID table for SVC svc initialized
Explanation

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


ADAS04 ADAB 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 ADAB 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 ADAB 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 ADAB 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 ADAB 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 ADAB 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 ADAB 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 ADAB Adabas Vv ID table for SVC svc initializaed with cccc entries IDT:address IDTExt:address FIIBS: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, 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 ADAB 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.
5 The operating system is not z/OS.
6 The RMODE of the Adabas SVC is not 24
7 The SVC table entry is unused.
8 Either the RMODE or AMODE is not 24.
9 The system could not find the requested SVC. Check for system message IEA826I.

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.

10 SVCUPDTE macro failure.
Action

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


ADAS13 ADAB 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 ADAB 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 ADAB SVC svc table entry changed without prompting operator
Explanation

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


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
IDTEES
IDTHE
IDT Extension

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 workareas 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 APF authorization is required
Explanation

An attempt was made to use an ADASVC function for which APF authorization is required.

Action

Provide APF authorization for all load libraries in the JOBLIB or STEPLIB concatenation.


Top of page