Version 7.4.4
 —  Messages and Codes  —

ADADEF Error Messages

Overview of Messages

ERROR-121 | ERROR-122 | ERROR-123 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-128 | ERROR-129 | ERROR-130 | ERROR-132 | ERROR-133 | ERROR-134 | ERROR-135 | ERROR-136 | ERROR-137 | ERROR-138 | ERROR-139

ERROR-121 MISSING FUNCTION PARAMETER
Action:

Add one of the following parameters and rerun the job:

  • ADADEF DEFINE - define a new database

  • ADADEF NEWWORK - define a new work


ERROR-122 INVALID VALUE FOR THE PARAMETER DBID
Explanation:

The value for the database ID must be in the range 1 to 65,535.

Action:

Supply the correct parameter value and rerun the job.


ERROR-123 CHECKPOINT-FILE DEFINITION MISSING IN PARAMETER-LIST
Explanation:

Each Adabas database requires a checkpoint file.

Action:

Add the following parameter and rerun the job.

ADADEF FILE=xx,CHECKPOINT, ...

ERROR-124 MULTIPLE SYSTEM FILE DEFINITION NOT PERMITTED
Explanation:

The Adabas checkpoint and security file can be defined only once per database.

Action:

Supply the correct parameter value and rerun the job.


ERROR-125 INVALID VALUE FOR THE PARAMETER WORKSIZE
Explanation:

The value of the WORKSIZE parameter must be at least 300 + WALT + number of blocks per track.

Action:

Increase the WORKSIZE value and rerun the job.


ERROR-126 ADADEF NOT PERMITTED TO RUN
Explanation:

An attempt was made to run ADADEF in parallel with an active nucleus. The Adabas nucleus returned response "response-code". (A short explanation is given here).

Action:

The only acceptable response code is 148. Shut down the nucleus and rerun the job.


ERROR-127 INCONSISTENT PARAMETER LIST
Explanation:

A corresponding extent parameter is required for

ASSOSIZE/ASSODEV/AALT, and DATASIZE/DATADEV/DALT.

Action:

Supply the correct parameter value and rerun the job.


ERROR-128 FILE TYPE MISSING OR INVALID
Explanation:

The file number must be followed by a keyword defining the type of the system file to be loaded.

Action:

See the Adabas Utilities documentation for further information. Supply the correct parameter value and rerun the job.


ERROR-129 DSST-EXTENT SPACE ALLOCATION FAILED
Explanation:

Not enough free Associator space is available to allocate a DSST extent.

Action:

Supply a larger Associator extent and rerun the job.


ERROR-130 INVALID VALUE FOR MAXDS/MAXNI/MAXUI
Explanation:

The value for the mentioned parameters must be specified in blocks and must be in the range 1B to 65535B.

Action:

Specify the correct parameter value and rerun the job.


ERROR-132 DATABASE NOT FORMATTED
Explanation:

The supplied ASSO contains a valid GCB.

Action:

Run ADAFRM before running ADADEF, or specify the OVERWRITE parameter in the ADADEF job.


ERROR-133 INVALID SIZE SPECIFICATION
Explanation:

The (ASSOSIZE / DATASIZE / WORKSIZE) parameter value specified for (DDASSO / ASSOR1/2, DDDATA / DATARn, or DDWORK / WORKR1) is greater than the space physically available (an actual parameter / job control value is printed with the message text).

Action:

Supply the correct parameter value, and rerun the job.


ERROR-134 NO DATABASE TO BE OVERWRITTEN
Explanation:

The parameter OVERWRITE was specified, but the datasets assigned do not contain a database.

Action:

Remove the OVERWRITE parameter, and rerun the ADADEF job.


ERROR-135 VALUE OF PARAMETER MAXRECL TOO LARGE
Explanation:

The MAXRECL value is either

  • greater than the default value "def-value"; or

  • less than 7.

Action:

Supply the correct MAXRECL parameter value, and rerun the ADADEF job.


ERROR-136 INVALID VALUE FOR THE PARAMETER RABNSIZE
Explanation:

Either 3 or 4 may be specified for the RABNSIZE parameter.

Action:

Correct the value specified for the RABNSIZE parameter and rerun the ADADEF job.


ERROR-137 dataset SIZE TOO LARGE
Explanation:

The DATA/ASSO/WORK dataset SIZE parameter value exceeds the maximum "nnnn" blocks.

Action:

Correct the value specified for the specified dataset SIZE parameter and rerun the ADADEF job.


ERROR-138 CANNOT SET UES=NO WHILE FILE file-number LOADED
Explanation:

The specified file contains at least one element such as a wide-character formatted field that require the database to be enabled for universal encoding; that is, UES=YES is required.

Action:

Reexamine your need to set UES=NO and adjust the file accordingly.


ERROR-139 SPECIFY UES=NO TO DISABLE UES
Explanation:

It is not possible to turn UES off by setting all xxCODE parameters to 0. ADADEF does not differentiate between a parameter set to zero (0) and a parameter not specified.

Action:

To disable UES, set the UES parameter equal to NO.


Top of page