ADARUN Statement/Parameter Messages

#### Search Results

Search

# ADARUN Statement/Parameter Messages

The Adabas ADARUN statements and parameters define the nucleus operating environment. The error messages that can result from ADARUN statements and parameters are described in this section. These messages have the following format:

    ADARUN error-nn,message-text

where nn is the message number and message-text describes the error. All ADARUN error messages are accompanied by a user abend 35 (abnormal end without a dump) code.

For information regarding ADARUN parameter syntax, refer to the Adabas operations documentation.

### Overview of Messages

`Error-1 | Error-2 | Error-3 | Error-5 | Error-6 | Error-7 | Error-8 | Error-9 | Error-12 | Error-13 | Error-20 | Error-21 | Error-22 | Error-23 | Error-25 | Error-29 | Error-31 | Error-32 | Error-33 | Error-34 | WARNING 26 | WARNING 27 | WARNING 28`

Error-1 | I/O error Reading DDCARD
Explanation | A job control (JCL/JCS) error occurred.
Action | Correct the error and rerun the job.

Error-2 | Unknown module
Explanation | The library allocation JCL is incorrect.
Action | Correct the error and rerun the job.

Error-3 | Keyword ADARUN missing
Explanation | The ADARUN parameter statement is missing the literal "ADARUN" at the beginning of the statement.
Action | Add the ADARUN keyword and rerun the job.

Error-5 | Invalid parameter syntax
Explanation | One of the following errors has occurred: An ADARUN input line was encountered without a valid parameter. A delimiter is missing between ADARUN parameters. A parameter value is missing. A parameter value is too long. The numeric value specified for the ADARUN parameter is too large. An invalid unit indicator has been specified for a numeric parameter. An invalid hexadecimal string has been specified. Too many values have been specified in a list of values. A parameter keyword is missing.
Action | Correct the error and rerun the job.

Error-6 | Ambiguous keyword ambkey
Explanation | ADARUN detected an ambiguous keyword (ambkey) in its specifications.
Action | Correct the error and rerun the job.

Error-7 | Unknown keyword keyword
Explanation | ADARUN detected the invalid keyword shown in the message (keyword).
Action | Correct the error and rerun the job.

Error-8 | Error loading module modname
Action | ADARUN detected a nonzero return code from the operating system's load function.
Action | Refer to any related ADAInn or other messages for the specific return code value, then refer to the appropriate operating system information to determine what action to take.

Error-9 | ADARUN not called from USER program
Explanation | ADARUN was not called by a user program but the ADARUN PROGRAM parameter was specified with a value of "USER" or "RENTUSER".
Action | Correct the JCL or control statements and rerun the job.

Error-12 | Invalid CMDQMODE = operand (above, below)
Explanation | BS2000 only. The CMDQMODE parameter specified an incorrect syntax option.
Action | Job terminates. Set the correct parameter value.

Error-13 | Invalid TAPEREL = operand (NO, RELEASE, KEEP, UNLOAD, KEEPUNL)
Explanation | BS2000 only. The TAPEREL parameter specified an incorrect syntax option.
Action | Job terminates. Set the correct parameter value.

Error-20 | Wrong AMODE-24 for RMODE-31
Explanation | ADARUN detected one or more loaded modules linked with RMODE={ANY | 31} while it runs in AMODE=24.
Action | Check the load library and either relink modules linked with AMODE=24 to AMODE={ANY | 31}, or relink modules linked with RMODE=ANY to RMODE=24.

Error-21 | Inconsistent CLUSTER parameter
Explanation | ADARUN detected an inconsistent CLUSTER parameter setting: Invalid CLUSTER or CLUCACHEUNCHANGED parameter, CLUSTER=SYSPLEX or LOCAL, and NUCID=0, CLUSTER=NO (default) but NUCID is nonzero, or CLUCACHEUNCHANGED=YES but CLUSTER is not LOCAL.
Action | Correct the error and rerun the job.

Error-22 | Inconsistent NPLOG or NCLOG parameter
Explanation | ADARUN detected an inconsistent parameter: Both NPLOG/NCLOG and DUALPLD/DUALCLD are specified; or PPLOGDEV/CLOGDEV and PLOGSIZE/CLOGSIZE are specified but NPLOG/NCLOG is not specified; or UEX2 together with NPLOG/NCLOG instead of UEX12 was found in the ADARUN parameters. The CLOGMAX or CLOGBMAX parameter setting is smaller than 368 bytes.
Action | Correct the error and rerun the job.

Error-23 | Invalid value for parameter parmname
Explanation | ADARUN detected an invalid or inconsistent value for the parameter listed in the message (parmname).
Action | Correct the error and rerun the job.

Error-25 | Version mismatch in one or more modules
Explanation | One or more Adabas modules loaded by ADARUN have different version/release/patch-level indicators (or in some cases, version/release indicators) than ADARUN itself. The mismatching modules are listed in preceding "ADARUN Warning: Mismatching version indicators in module xxxxxx" messages, where xxxxxx is the load module name. ADARUN terminates with the Error-25 only if the Adabas SAF Security add-on product is installed.
Action | Provide a load library (or concatenation of load libraries) where all Adabas modules belong to the same Adabas version, release and patch-level, or for add-on products, the same version and release level.

Error-29 | Loaded modules do not support ENCRYPTION
Explanation | The Adabas load library is not correct and does not fully support Adabas Encryption, Adabas Auditing or Adabas SAF Security 8.3. Either the ADAIOR/IOS modules do not support Adabas Encryption or some of the required maintenance in the nucleus and utilities is missing.
Action | Review and correct the JOBLIB/STEPLIB concatenation or combined load library, as per the installation instructions for Adabas Encryption. Ensure that all zaps required for Adabas Encryption, Adabas Auditing or Adabas SAF Security 8.3 have been applied.

Error-31 | IDTNAME does not start "ADA"
Explanation | This is a BS2000 only error. The user has defined the IDTNAME or the ENVNAME in the SSFB2C parameter module which does not begin with "ADA". This will lead to a failure in communication between Client applications and nucleus.
Action | Correct the IDTNAME in the ADARUN parameter list so that it begins with "ADA" and restart the nucleus.

Error-32 | SWITCHNR out of range 0 - 31
Explanation | ADARUN detected an inconsistent Adabas BS2000 parameter. The job switch number to be set when a non-zero return code occurs is out of the range of 1 to 31.
Action | Correct the error and rerun the job.

Error-33 | SUBMPSZ needs to be higher than x100000
Explanation | ADARUN detected an inconsistent Adabas BS2000 parameter. The size of the declared subtask memory pool is too small.
Action | Correct the error and rerun the job.

Error-34 | PAMREQS must be a value > 0
Explanation | ADARUN detected an inconsistent Adabas BS2000 parameter. The maximum number of PAM blocks sent in one PAM macro must be greater than zero.
Action | Correct the error and rerun the job.

WARNING 26 | Parameter AMODE out of service
Explanation | BS2000 only. ADARUN statement AMODE=31 detected. This parameter has been removed from Adabas. Targets that use SSF must run in AMODE 31.
Action | The job continues. Remove AMODE= from your ADARUN statements.

WARNING 27 | Parameter IDTMODE out of service
Explanation | BS2000 only. IDTMODE=ABOVE statement detected. This parameter has been removed from Adabas. IDTs created by SSF are allocated above the 16-megabyte line.
Action | The job continues. Remove IDTMODE= from your ADARUN statements.

WARNING 28 | Parameter NECB out of service
Explanation | BS2000 only. NECB= statement detected. This parameter has been removed from Adabas. The posted ECB queue can no longer overflow.
Action | Job continues. Remove NECB= from your ADARUN statements.