Version 8.1.4
 —  Messages and Codes  —

ADASIP* (Adabas VSE SVC) System Messages

Overview of Messages

ADASIP00 | ADASIP01 | ADASIP02 | ADASIP03 | ADASIP04 | ADASIP05 | ADASIP06 | ADASIP08 | ADASIP09 | ADASIP10 | ADASIP11 | ADASIP12 | ADASIP13 | ADASIP14 | ADASIP15 | ADASIP16 | ADASIP17 | ADASIP18 | ADASIP19 | ADASIP20 | ADASIP21 | ADASIP22 | ADASIP23 | ADASIP24 | ADASIP26 | ADASIP27 | ADASIP28 | ADASIP29 | ADASIP30 | ADASIP31 | ADASIP32 | ADASIP33 | ADASIP36 | ADASIP37 | ADASIP38 | ADASIP39 | ADASIP40 | ADASIP41 | ADASIP50 | ADASIP60 | ADASIP61 | ADASIP62 | ADASIP63 | ADASIP64 | ADASIP65 | ADASIP66 | ADASIP67 | ADASIP68 | ADASIP69 | ADASIP70 | ADASIP71 | ADASIP72 | ADASIP73 | ADASIP74 | ADASIP75 | ADASIP76 | ADASIP77 | ADASIP78 | ADASIP79 | ADASIP80 | ADASIP81 | ADASIP85 | ADASIP86 | ADASIP87 | ADASIP88

ADASIP00 Adabas Vav.ar VSE SIP started
SIP is running under z/VSE Vvv.vr.vm
( yyyy-mm-dd. SM=sm-level , ZAP=zap-level)
SIP IS LOADING ADABAS SVC LEVEL sv.sr.sm
ADASIP IS LOADING ADABAS SVC AMODE=a-mode
Explanation

The ADASIP program has started. The following substitutions appear in the message:

Substitution Description
av.ar version and release of Adabas.
vv.vr.vm version, release, and modification level of z/VSE
yyyy-mm-dd date of ADASIP module assembly
sm-level system maintenance (SM) level of the ADASIP module
zap-level Zap level of the ADASIP module
sv.sr.sm version, release, and modification level of the Adabas SVC
a-mode the AMODE setting of the Adabas SVC

ADASIP01 SUBSID macro error
Explanation

ADASIP received a nonzero return code from the operating system.

Action:

The VSE operating system release level is too low for installing Adabas. Refer to the Adabas Installation documentation 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 documentation 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.


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-256
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 documentation .


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 Unknown keyword in PARM field
Explanation

ADASIP found an incorrect keyword in the PARM field.

Action:

Correct the keyword parameter and rerun the job.


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.


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 your Software AG technical support representative.


ADASIP16 WARNING -- IDT table already exists
Explanation

ADASIP detected that an IDT table for this SVC already exists.

Action:

No action is required for this warning message.


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


ADASIP24 The IDT has been pagefixed by user option
Explanation

UPSI (X'20') was selected to pagefix the IDT in the system GETVIS area.


ADASIP26 Could not load the ADAOPD table
Explanation

ADASIP was unable to load phase ADAOPD.

Action:

Ensure that ADAOPD is available for loading and rerun the job.


ADASIP27 ADASVCxx must be AMODE=31, RMODE=24
Explanation

ADASIP detected that the Adabas SVC has invalid link-edit attributes.

Action:

Relink the Adabas SVC with the correct attributes and rerun the job.


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 (Date yyyymmdd)
Explanation

ADASIP has installed SVC number svc successfully.


ADASIP31 address=SVC address
Explanation

The SVC has been loaded at the indicated address.


ADASIP32 address=IDT address
Explanation

The ID table has been allocated at the indicated address.


ADASIP33 Invalid value specified for REPLACE parameter
Explanation

An invalid value was specified on the REPLACE parameter.

Action:

Specify YES, Y, NO or N for the REPLACE parameter and rerun the job.


ADASIP36 address=extended IIBS address
Explanation

The extended IIBs have been loaded at the indicated address.


ADASIP37 address=IDT Extension address
Explanation

The IDT extension has been allocated at the indicated address.

Action:

No action is required for this informational message.


ADASIP38 address=SVC Work Area address
Explanation

The SVC work area has been allocated at the indicated address.

Action:

No action is required for this informational message.


ADASIP39 Error -- Targets still active on SVCnnn
Explanation

ADASIP detected that there are still active targets on the SVC listed in the message (nnn) and is unable to continue processing.

Action:

No action is required for this informational message.


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:

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


ADASIP50 The command queue has been dumped to SYSLST
Explanation

ADASIP has completed listing the command queue for the specified database.


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 active
Explanation

Adabas Turbo support is now active on this VSE machine.


ADASIP70 VSE supervisor hook install failed
Explanation

Either this version of the VSE 2 supervisor is not supported, or the vendor installation logic for the first-level interrupt handler is incorrect.

Action

Call Software AG; 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 : code
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.


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.


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 nn
Explanation

Version of VSE Turbo Dispatcher.


ADASIP79 Should we stop the CPUs? (yes/no)
Explanation

This message appears following ADASIP60 if more than one CPU is active during ADASIP processing.

Action

Replying "no" terminates the job. Replying "yes" causes CPUs to be temporarily deactivated while ADASIP runs. ADASIP will reactivate any deactivated CPUs before terminating.


ADASIP80 SVCnnn Target ID id is active in partition pp
Explanation

ADASIP does not allow an SVC to be reinstalled if there are active targets using the SVC, unless parameter REPLACE=YES is specified. If ADASIP parameter REPLACE=YES was specified, ADASIP replaces the current SVC regardless of any active targets.

An attempt to reinstall an SVC by rerunning ADASIP when there are active targets using the SVC results in warning messages ADASIP80 and ADASIP81 being issued. If the reply to ADASIP81 is "no", ADASIP terminates processing. If the reply to ADASIP is "yes", ADASIP will check again for active targets. If active targets are found, messages. ADASIP80 and ADASIP81 will appear again. To proceed with ADASIP processing, active targets must be terminated before replying "yes" to message ADASIP81.

Note:
ADASIP will only flag a target as active if the job which activated the target is still running.

Action

No action is required for this warning message.


ADASIP81 Should we continue processing? (yes/no)
Explanation

An attempt was made to reinstall an SVC while there are active targets using the SVC. Unless the ADASIP parameter REPLACE=YES is specified, ADASIP does not allow an SVC to be reinstalled if there are active targets using the SVC. This prompt allows you to continue or stop processing.

Action

Enter "yes" to continue or "no" to terminate processing.


ADASIP85 SVA-24 storage allocated: nnnnnK
SVA-31 storage allocated: nnnnnK
Explanation

ADASIP has allocated nnnnnK of SVA storage below (SVA-24) or above (SVA-31) the 16 MB line.

Action

No action is required for this informational message.


ADASIP86 Reuse previous ADASTUB loaded at address? (yes/no)
SVA-31 storage allocated: nnnnnK
Explanation

ADASIP detected that ADASTUB has already been loaded.

A SET SDL for ADANCHOR should only be issued once per IPL. However, if ADASIP is rerun, and a SET SDL for ADANCHOR is issued a second time in error, it should be possible to preserve the existing Adabas communications environment by answering "yes" to message ADASIP86.

Action

Reply "yes" to reuse the ADASTUB or "no" to load a new copy of ADASTUB. The recommended reply is "yes". Do not reply "no" to this message unless directed to do so by your Software AG technical support representative.


ADASIP87 SYSLST unavailable
Explanation

ADASIP is not able to print messages on SYSLST, as this is unavailable. Console messages only will be issued. ADASIP continues processing.,

Action

No action is required for this informational message.


ADASIP88 Invalid parameter combination
Explanation

ADASIP detected an invalid combination of PARM parameters or UPSI bytes.

Action

Correct the parameters or UPSI bytes and rerun the job.


Top of page