Adabas SVC Installation Messages (ADASIP)

This page describes all Adabas ADASVC messages. Some of these messages may occur during installation of EntireX. Not all messages are applicable to EntireX.

Overview of Messages

ADASIP01 | ADASIP02 | ADASIP03 | ADASIP04 | ADASIP05 | ADASIP06 | ADASIP07 | ADASIP08 | ADASIP09 | ADASIP10 | ADASIP11 | ADASIP12 | ADASIP13 | ADASIP14 | ADASIP15 | ADASIP17 | ADASIP18 | ADASIP19 | ADASIP20 | ADASIP21 | ADASIP22 | ADASIP23 | ADASIP24 | ADASIP27 | ADASIP28 | ADASIP29 | ADASIP30 | ADASIP31 | ADASIP32 | ADASIP33 | ADASIP34 | ADASIP36 | ADASIP40 | ADASIP41 | ADASIP50 | ADASIP60 | ADASIP61 | ADASIP62 | ADASIP63 | ADASIP64 | ADASIP65 | ADASIP66 | ADASIP67 | ADASIP68 | ADASIP69 | ADASIP70 | ADASIP71 | ADASIP72 | ADASIP73 | ADASIP74 | ADASIP75 | ADASIP76 | ADASIP77 | ADASIP78

ADASIP01	SUBSID MACRO ERROR
Explanation	ADASIP received a non-zero return code from the operating system.
Action	The VSE operating system release level is too low for installing Adabas. Refer to the Adabas Installation Manual for the minimum allowed VSE levels.

ADASIP02	UNSUPPORTED VSE RELEASE BASED UPON SUBSID
Explanation	An ADASIP validation check indicates an unsupported operating system level.
Action	The VSE operating system release level is too low for installing Adabas. Refer to the Adabas Installation Manual for the minimum allowed VSE levels.

ADASIP03	NO SYSPARM VALUE SPECIFIED FOR SVC
Explanation	ADASIP could not find a SYSPARM input, and a ZAP has not be applied to the specified SVC.
Action	Either provide the SVC with SYSPARM or apply a ZAP to the specified SVC with ADASIP.

ADASIP04	DEFAULT VALUE USED FOR THE SVC
Explanation	No SYSPARM SVC has been used. ADASIP defaults to using the SVC that has a ZAP applied.
Action	This message is for your information only; no error has occurred.

ADASIP05	NON-NUMERIC DATA FOUND IN SYSPARM FIELD
Explanation	Either SYSPARM or the default ADASIP SVC contains a nonnumeric value.
Action	Correct the specified SYSPARM value, or set the default SVC value to 30.

ADASIP06	INVALID RANGE SPECIFIED FOR THE SVC 31-120
Explanation	ADASIP found an SVC outside the allowed range in SYSPARM or the ADASIP default SVC.
Action	Set the SVC to an unused SVC value within the allowed range. SVC ranges and recommended values are described in the Adabas Installation Manual.

ADASIP07	SVC SPECIFIED NOT WITH VALID RANGE - NO UPSI
Explanation	The value specified for the SVC in the VSE SYSPARM with the UPSI option was incorrect. SVC ranges and recommended values are described in the Adabas Installation Manual.
Action	Correct the UPSI or SVC value, as appropriate.

ADASIP08	ADASVCvv WAS NOT FOUND IN THE SVA
Explanation	While performing a VSE load, ADASIP found that the specified level ADASVC was not in the SVA.
Action	Issue the SET SDL for ADASVCvv. It may be necessary to relink the Adabas SVC with SVA using the PHASE statement if the Adabas SVC is not found in the Adabas library.

ADASIP09	NO MATCH ON ID - INCORRECT ADASVC LOADED
Explanation	ADASIP found an incorrect SVC version while attempting a load operation.
Action	Relink ADASVCvv with the correct SVC module.

ADASIP10	NO KEYWORD SPECIFIED FOR NRIDTES
Explanation	ADASIP found an incorrect NRIDTES keyword.
Action	Respecify the keyword parameter as NRIDTES=nn, where "nn" specifies the number of databases to be supported in the ID table.

ADASIP11	NON-NUMERIC DATA SPECIFIED FOR NRIDTES
Explanation	The ADASIP NRIDTES= keyword parameter specified non-numeric data.
Action	Correct the NRIDTES= data, then resubmit ADASIP.

ADASIP12	NO OVERRIDING NRIDTES SPECIFIED
Explanation	The default NRIDTES was used. No error has occurred.
Action	None required. This message is for your information only.

ADASIP13	SVC TABLE ENTRY WAS FOUND TO BE INVALID
Explanation	The SVC number provided by SYSPARM is either not valid, or does not represent either the old or new version of the VSE Adabas SVC. This error can occur if the UPSI statement's C parameter specified 0.
Action	Respecify the UPSI statement, or specify another unused SVC value. Rerun ADASIP.

ADASIP14	GETVIS FAILURE FOR IDT IN SVA
Explanation	The GETVIS of the IDT passed a nonzero return code back to ADASIP, meaning the GETVIS size was insufficient.
Action	Increase the SVA GETVIS size, re-IPL the operating system, and rerun ADASIP.

ADASIP15	ROUTER UNABLE TO INITIALIZE IDT
Explanation	ADASIP received a nonzero return code from the 56 call to the SVC.
Action	Contact Software AG support.

ADASIP17	INCORRECT SVC SUFFIX AFTER COMMA IN SYSPARM
Explanation	An attempt was made to run this program more than once for the current IPL. A second IDT for the program is not required.
Action	Correct the SYSPARM specification for the two-byte SVC suffix, and rerun the job.

ADASIP18	NON-NUMERIC DATA SPECIFIED FOR DMPDBID
Explanation	The ADASIP DMPDBID keyword parameter contains nonnumeric data.
Action	Correct the DMPDBID specification, and rerun the job.

ADASIP19	DBID CANNOT BE FOUND IN IDTE
Explanation	The ADASIP program could not find an entry for the DMPDBID database in the IDT area.
Action	Either correct the DMPDBID specification or start the specified database, then run ADASIP to perform a "snap" dump of the command queue.

ADASIP20	THE IDT AND SVC HAVE BEEN DUMPED TO SYSLST
Explanation	A request to ADASIP to dump the IDT and then SVC via UPSI 80.
Action	This message is for your information only; no error has occurred.

ADASIP21	NO IDT TABLE WAS FOUND FOR SPECIFIED SVC
Explanation	ADASIP found that the SVC has no address for the IDT.
Action	Specify the correct SVC, or initialize with ADASIP first.

ADASIP22	THE SVC HAS ALREADY BEEN INSTALLED
Explanation	ADASIP found that the same program is being run again.
Action	The SVC is not installed and no IDT table is needed. To reinstall the same SVC, you must first perform a SET SDL.

ADASIP23	THE SVC TABLE CANNOT BE LISTED UNDER DOS/MVT
Explanation	The option to display the SVC table is specified under VSE.
Action	None required. This message is for your information only.

ADASIP24	THE IDT HAS BEEN PAGEFIXED BY USER OPTION
Explanation	UPSI (X'20') was selected to pagefix the IDT in the system GETVIS area.
Action	None required. This message is for your information only.

ADASIP27	ADASVC IS RMODE=ANY
Explanation	ADASIP detected that the Adabas SVC is linked RMODE=ANY.
Action	Relink the Adabas SVC RMODE=24.

ADASIP28	ADASIP IS AMODE=31
Explanation	ADASIP detected that it is AMODE=31.
Action	Relink ADASIP AMODE=24.

ADASIP29	PRODID MACRO FAILURE
Explanation	ADASIP received a nonzero response code from the PRODID DEFINE macro.
Action	Investigate the cause of the error. Correct it and rerun the job.

ADASIP30	ADASVCvv svc INSTALLED
Explanation	ADASIP has installed SVC number svc successfully.
Action	None required.

ADASIP31	address=SVC ADDRESS
Explanation	The SVC has been loaded at the indicated address.
Action	None required. This message is for your information only.

ADASIP32	address=IDT ADDRESS
Explanation	The ID table has been allocated at the indicated address.
Action	None required. This message is for your information only.

ADASIP33	address=ALET TABLE ADDRESS
Explanation	The ALET table has been loaded at the indicated address.
Action	None required. This message is for your information only.

ADASIP34	count=MAXIMUM USER/TARGET COMBINATIONS
Explanation	Total number of client/server combinations within the VSE system.
Action	None required. This message is for your information only.

ADASIP36	address=EXTENDED IIBS ADDRESS
Explanation	The extended IIBs have been loaded at the indicated address.
Action	None required. This message is for your information only.

ADASIP40

VSE SVC svc IS status AM=a-mode RM=r-mode AR=reg-mode SVCT=svc-tab-addr MODT=svc-mod-addr

Explanation

This message occurs when the option to list the SVC table is selected, and specifies the following values:

Value	Description
svc	the VSE SVC number
status	USED or UNUSED
a-mode	AMODE of this SVC, if used (24 or ANY)
r-mode	RMODE of this SVC, if used (24 or ANY)
reg-mode	access register mode of this SVC, if used (Y=yes, N=no)
svc-tab-addr	address of the SVC table entry for this SVC
svc-mod-addr	address of the SVC mode table entry for this SVC, if present

Action

None required. This message is for your information only.

Note:
Do not use SVC50, even though it is indicated as "unused".

ADASIP41	VSE SVC TABLE AUDIT COMPLETED
Explanation	ADASIP has completed listing the VSE SVC table.
Action	None required. This message is for your information only.

ADASIP50	THE COMMAND QUEUE HAS BEEN DUMPED TO SYSLST
Explanation	ADASIP has completed listing the command queue for the specified database.
Action	None required. This message is for your information only.

ADASIP60	ONLY 1 CPU CAN BE ACTIVE DURING ADASIP
Action	Use `SYSDEF TD,STOP=ALL` to stop all but one CPU so that ADASIP can run. Then restart your CPUs again.

ADASIP61	RERUN ADASIP AFTER USING TDSERV TO STOP CPUS
Explanation	Occurs in conjunction with ADASIP60.

ADASIP62	GETVIS FAILED FOR ADASTUB MODULE
Explanation	Not enough SVA storage to load ADASTUB.
Action	Consult with your system programmer.

ADASIP63	ADASTUB MODULE LOADED AT address
Explanation	Information message indicating module load address.

ADASIP64	NO MATCH ON ID - INCORRECT ADASTUB LOADED
Explanation	ADASTUB phase is incorrect.
Action	Consult with your system programmer, or contact Software AG.

ADASIP65	ADASTUB SVC TABLE NOT FOUND
Explanation	ADASTUB phase is incorrect.
Action	Consult with your system programmer, or contact Software AG.

ADASIP66	ADASTUB SVC TABLE IS FULL
Explanation	You have more than 10 SVCs active on this VSE machine.
Action	Contact Software AG for information about increasing the table size.

ADASIP67	PAGEFIX FOR ADASIP FAILED
Action	Increase the SETPFIX value and rerun.

ADASIP68	PAGEFREE FOR ADASIP FAILED
Action	Consult with your system programmer.

ADASIP69	TURBO DISPATCHER STUB A C T I V E
Explanation	Adabas Turbo support is now active on this VSE machine.

ADASIP70	VSE SUPERVISOR HOOK INSTALL FAILED
Explanation	Either this version of the VSE/ESA 2 supervisor is not supported, or the vendor installation logic for the first-level interrupt handler is incorrect.
Action	Contact Software AG support and have message ADASIP72 available.

ADASIP71	LOAD OF MODULE ADASTUB FAILED
Explanation	The ADASTUB module was not found in the LIBDEF SEARCH chain.

ADASIP72	CODE IS : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Explanation	Occurs after message ADASIP70.

ADASIP73	ADANCHOR INCORRECT OR NOT FOUND IN SVA
Explanation	The ADANCHOR module was not found in the SVA; no SET SDL has been done.

ADASIP74	INFO : STUB ACTIVATED BY PREVIOUS ADASIP
Explanation	Adabas Turbo STUB has been installed by a previous ADASIP.
Action	None. This message is for information only.

ADASIP75	ADANCHOR AND ADASTUB NOT DUMPED - NOT ACTIVE
Explanation	When attempting to dump Adabas control blocks with ADASIP, the modules were not dumped because Adabas Turbo support is not active.
Action	None. This message is for information only.

ADASIP76	ADABAS TURBO STUB NOT ACTIVATED DUE TO ERROR
Explanation	An error occurred during the installation of the Adabas Turbo stub.

ADASIP77	THIS ADABAS SVC WILL RUN IN NON-TURBO MODE
Explanation	An error occurred during the installation of the Adabas Turbo stub. This SVC will run in non-Turbo mode from now on.

ADASIP78	VSE TURBO DISPATCHER VERSION nn
Explanation	Version of VSE/ESA version 2 Turbo Dispatcher. 00 indicates TD level of pre-version 4.
Action	None. This message is for information only.