ADASIP* (Adabas VSE SVC) System Messages

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

ADASIP received a nonzero return code from the operating system.

The VSE operating system release level is too low for installing Adabas. Refer to the Adabas Installation documentation for the minimum allowed VSE levels.

An ADASIP validation check indicates an unsupported operating system level.

The VSE operating system release level is too low for installing Adabas. Refer to the Adabas Installation documentation for the minimum allowed VSE levels.

ADASIP could not find a SYSPARM input, and a ZAP has not be applied to the specified SVC.

Either provide the SVC with SYSPARM or apply a ZAP to the specified SVC with ADASIP.

No SYSPARM SVC has been used. ADASIP defaults to using the SVC that has a ZAP applied.

Either SYSPARM or the default ADASIP SVC contains a nonnumeric value.

Correct the specified SYSPARM value, or set the default SVC value to 30.

ADASIP found an SVC outside the allowed range in SYSPARM or the ADASIP default SVC.

Set the SVC to an unused SVC value within the allowed range. SVC ranges and recommended values are described in the Adabas Installation documentation .

While performing a VSE load, ADASIP found that the specified level ADASVC was not in the SVA.

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.

ADASIP found an incorrect SVC version while attempting a load operation.

Relink ADASVCvv with the correct SVC module.

ADASIP found an incorrect keyword in the PARM field.

Correct the keyword parameter and rerun the job.

The ADASIP NRIDTES= keyword parameter specified non-numeric data.

Correct the NRIDTES= data, then resubmit ADASIP.

The default NRIDTES was used. No error has occurred.

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

Respecify the UPSI statement, or specify another unused SVC value. Rerun ADASIP.

The GETVIS of the IDT passed a nonzero return code back to ADASIP, meaning the GETVIS size was insufficient.

Increase the SVA GETVIS size, re-IPL the operating system, and rerun ADASIP.

ADASIP received a nonzero return code from the 56 call to the SVC.

Contact your Software AG technical support representative.

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

No action is required for this warning message.

An attempt was made to run this program more than once for the current IPL. A second IDT for the program is not required.

Correct the SYSPARM specification for the two-byte SVC suffix, and rerun the job.

The ADASIP DMPDBID keyword parameter contains nonnumeric data.

Correct the DMPDBID specification, and rerun the job.

The ADASIP program could not find an entry for the DMPDBID database in the IDT area.

Either correct the DMPDBID specification or start the specified database, then run ADASIP to perform a "snap" dump of the command queue.

A request to ADASIP to dump the IDT and then SVC via UPSI 80. No error has occurred.

ADASIP found that the SVC has no address for the IDT.

Specify the correct SVC, or initialize with ADASIP first.

ADASIP found that the same program is being run again.

The SVC is not installed and no IDT table is needed. To reinstall the same SVC, you must first perform a SET SDL.

The option to display the SVC table is specified under VSE.

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

ADASIP was unable to load phase ADAOPD.

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

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

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

ADASIP detected that it is AMODE=31.

Relink ADASIP AMODE=24.

ADASIP received a nonzero response code from the PRODID DEFINE macro.

Investigate the cause of the error. Correct it and rerun the job.

ADASIP has installed SVC number svc successfully.

The SVC has been loaded at the indicated address.

The ID table has been allocated at the indicated address.

An invalid value was specified on the REPLACE parameter.

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

The extended IIBs have been loaded at the indicated address.

The IDT extension has been allocated at the indicated address.

No action is required for this informational message.

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

No action is required for this informational message.

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

No action is required for this informational message.

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

None required. This message is for your information only. Do not use SVC50, even though it is indicated as "unused".

ADASIP has completed listing the VSE SVC table.

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

Use "SYSDEF TD,STOP=ALL" to stop all but one CPU so that ADASIP can run. Then restart your CPUs again.

Occurs in conjunction with ADASIP60.

Not enough SVA storage to load ADASTUB.

Consult with your system programmer.

Information message indicating module load address.

ADASTUB phase is incorrect.

Consult with your system programmer, or contact Software AG.

ADASTUB phase is incorrect.

Consult with your system programmer, or contact Software AG.

You have more than 10 SVCs active on this VSE machine.

Contact Software AG for information about increasing the table size.

Increase the SETPFIX value and rerun.

Consult with your system programmer.

Adabas Turbo support is now active on this VSE machine.

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

Call Software AG; have message ADASIP72 available.

The ADASTUB module was not found in the LIBDEF SEARCH chain.

Occurs after message ADASIP70.

The ADANCHOR module was not found in the SVA; no SET SDL has been done.

Adabas Turbo STUB has been installed by a previous ADASIP.

When attempting to dump Adabas control blocks with ADASIP, the modules were not dumped because Adabas Turbo support is not active.

An error occurred during the installation of the Adabas Turbo stub.

An error occurred during the installation of the Adabas Turbo stub. This SVC will run in non-Turbo mode from now on.

Version of VSE Turbo Dispatcher.

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

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

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.

No action is required for this warning message.

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.

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

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

No action is required for this informational message.

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.

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.

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

No action is required for this informational message.

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

Correct the parameters or UPSI bytes and rerun the job.