Nucleus Startup Error Messages

The Associator data set(s) could not be opened or an error occurred during processing of the GCBs:

• invalid or incorrect DEVICE parameter;

• missing or invalid JCL or data sets for ASSO;

• mismatching database ID; or

• missing checkpoint file.

This error may result from a data set not located on a cylinder boundary.

For single-user mode, the appropriate Adabas job control statements must be specified.

Data Storage data set(s) could not be opened. This probably indicates missing or invalid JCL or data sets for DATA.

For single-user mode, the appropriate Adabas job control statements must be specified.

The Work data set could not be opened, or the last Work block was not readable. This probably indicates invalid DD/WORKR1 JCL or data set, or a data set not located on a cylinder boundary.

For single-user mode, the appropriate Adabas job control statements must be specified.

The value of the ADARUN statement's number of threads (NT) parameter is invalid. The allowed range is from 4 to 250.

The value of the ADARUN statement's number of hold queue elements (NH) parameter is invalid. The allowed range is from 20 to 16,777,215.

The value of the ADARUN statement's user queue element count (NU) parameter is invalid. The allowed range is from 20 to 16,777,215.

The value of the ADARUN statement's user ISN hold queue count (NISNHQ) is invalid. The allowed maximum is the smaller of 1/4 the NH parameter value and 65,535.

The value of the ADARUN statement's command queue element count (NC) parameter is invalid. The allowed range is from 20 to 32,767.

The value of the ADARUN statement's Adabas cluster nucleus ID (NUCID) is invalid. The maximum value is 65000.

The value of the ADARUN statement's ISN list table length (LI) parameter is invalid. The minimum value is 2000.

The value of the ADARUN statement's sequential command table (LQ) parameter is invalid. The minimum value is 2000.

The value of the ADARUN statement's buffer pool length (LBP) parameter is invalid. The minimum value is 80,000.

The value of the ADARUN statement's internal format pool (LFP) parameter is invalid. the minimum value is 6000.

The value of the ADARUN statement's work pool length (LWP) parameter is invalid. The minimum value is 80,000.

The value of the ADARUN statement's sort area length size (LS) parameter is invalid. The allowed range is from 19,968 to (LWP/2) -19,968.

The value of the ADARUN statement's security pool length (LCP) parameter is invalid. The allowed range is from 2000 to 16,777,215.

If you have Adabas Transaction Manager version 7.4 or earlier installed, the size of Work part 1 (the value of the ADARUN statement's LP parameter) is less than 200 blocks or greater than the Work data set size minus the space required for Work part 2 (the LWKP2 parameter), Work part 3 (minimum of 50 blocks), and, if used, Work part 4 (the LDTP parameter).

If you have Adabas Transaction Manager version 7.5 or later installed, the size of Work part 1 (the value of the ADARUN statement's LP parameter) is less than 200 blocks or greater than the Work data set size minus the space required for Work part 2 (the LWKP2 parameter), and Work part 3 (minimum of 50 blocks).

Fewer than 50 blocks are available for Work part 3. Autorestart has been executed.

The DBID of the general control blocks (GCBs) and DBID stored on the Work data set do not match. The Work data set contains autorestart information for a different database (DBID).

GETMAIN below the 16MB line failed.

The general control blocks (GCBs) contain an invalid device type. The GCBs may have been overwritten, damaged, or otherwise destroyed.

An I/O error occurred when writing ASSO. The region is too small. The RABN that was to be written is printed.

A nucleus entry already exists in the data integrity block (DIB) for one of the following reasons:

• An attempt was made to start a nucleus while another update nucleus was still active; or

• The previous nucleus session terminated abnormally but the "nucleus" DIB entry was not removed.

If a DIB entry remained after an abnormal termination, rerun the job with the ADARUN IGNDIB=YES parameter. If the FORCE=YES parameter had been applied, then the nucleus must be started with FORCE=YES and IGNDIB=YES. Here the DIB entry will only be removed once the ID Table initialization had been successful. Running with IGNDIB=YES alone will result in a PARM-ERROR 26.

An I/O error occurred when reading ASSO. The RABN that was to be read is printed.

The Adabas nucleus cannot be started because a conflicting utility DIB entry was found. Either a utility with exclusive database control or an ADASAV (SAVE FILE or SAVE database) job is running.

If an ADASAV SAVE FILE or ADASAV SAVE (database) ended abnormally, the nucleus can be restarted with the ADARUN IGNDIB=YES parameter; however, the save tape cannot be used for future RESTORE operations.

Interregion communication could not be established.

This message should be preceded by message ADAM98. If the ADAM98 error reason is “DUPLICATE ID (LOCAL)” and a previous nucleus ended such that it was not able to clean up, you may wish to restart specifying FORCE=YES. Refer to ADAM98 message documentation for information about other possible errors.

If IGNDIB=YES was specified, then the nucleus must be started with FORCE=YES and IGNDIB=YES. Here the DIB entry will only be removed once the ID Table initialization had been successful. Running with FORCE=YES alone will result in a PARM-ERROR 23.

Note:
Specifying FORCE=YES with the DBID of a currently active nucleus can disrupt operations on that nucleus. In addition, users of the old database whose ID is overwritten by the FORCE=YES option lose access to the database. Therefore, FORCE=YES should only be specified if absolutely necessary . For more information, refer to the FORCE parameter description in the Adabas Operations documentation.

The ADARUN statement's PLOGRQ parameter is specified as or defaults to YES, FORCE, or SEL, but a protection log and related parameters have not been provided.

The protection log (PLOG) data set(s) could not be opened, or the last dual or multiple PLOG block was not readable. This is probably due to incorrect PLOG data set definition, specification, or job control statements.

Invalid command log (CLOG) device definition.

FREEMAIN error.

System autorestart error (see the nucleus response code).

Error during buffer flush.

Error during Work initialization.

The nucleus is not allowed to start with READONLY=YES when an autorestart is pending.

File control block (FCB) check failed. The FCB may have been overwritten or otherwise destroyed.

Timer initialization failed, or operator communication could not be established.

GETMAIN in common storage (CSA) failed; interregion communication could not be established. The specific reason is given in a detailed ADAMnn message.

DIB overflow.

Work pool is too small for the number of threads.

Increase the LWP parameter value to at least 25 kilobytes times the number of threads.

Database version mismatch: the database is not version version revision-level.

Run the ADACNV utility to bring the database to the correct version.

Parallel participant table (PPT) initialization error:

• an I/O error occurred reading or writing a PPT block (RABN); or

• a PPT length error occurred when a bad PPT block was encountered.

Error detected during system open:

• error writing PPT RABN; or

• a Work data set was already in use by another nucleus.

Error detected during system open:

• either a PLOG was supplied that was different from the one used in the previous session, or no PLOG was supplied. The PLOG from the previous session has not yet been copied.

• PLOGRQ=FORCE was specified and either the PLOG from the previous session has not yet been copied or a UEX2 or UEX12 has not been specified.

A noncluster nucleus attempted to start after a cluster failure; or, the first cluster nucleus is starting but there are already active blocks in the PPT. The nucleus is not allowed to start. Switching from single-nucleus mode to multi-nucleus cluster mode or from multi-nucleus cluster mode to single-nucleus mode is not allowed after an abnormal session termination.

GETMAIN above the 16MB line failed; memory-related parameters probably too big.

UQE could not be generated.

Increase NU parameter.

An I/O error occurred when reading or writing to the Work data set for one of the following reasons:

• The GCB doesn’t match the actual size of the Work data set

• ADARUN LP is larger than the Work data set,

• ADADEF NEWWORK was not run after allocating a new Work data set

The RABN that was to be read or written is printed.

An error occurred during checkpoint generation:

• the takeover of checkpoints generated by offline utilities failed; or

• creation of the session start checkpoint failed.

An I/O error occurred while reading or writing dual or multiple PLOGs. The RABN that was to be read or written is printed.

Dual or multiple PLOG contains data from another database.

Parameter conflict: READONLY=YES is not permitted with UTIONLY=YES.

No dual or multiple PLOG available for protection logging. All PLOGs are due to be copied.

At least one of the specified PLOG data sets is already in use by another nucleus in the cluster.

IGNDIB=YES was specified but the DIB does not contain a conflicting nucleus or utility entry.

Remove the IGNDIB parameter.

Error while attempting to lock or unlock a global resource. An ADAN54 message preceding this parameter error indicates the specific global resource that could not be locked/unlocked.

A DIB entry was found with an inconsistent group name. The associated nucleus may still be active. The DIB entry can be removed only by a nucleus of the same type (single, cluster) and the same CLUGROUPNAME as the DIB entry's owner.

DIB entry missing. Another cluster nucleus is already active on this database, but its DIB entry is not present.

The Work block size is too small to store the maximum compressed data record permitted in this database according to MAXRECL definition.

Increase the Work block length.

The Work block size is too small for the largest Associator block size present in this database.

The PLOG block size is too small to store the maximum compressed data record permitted in this database according to MAXRECL definition.

Important fields in the GCBs changed while this nucleus was starting. The nucleus is not able to handle this situation.

Restart the nucleus.

CPU timer initialization failed.

RRDF=YES is not allowed. Note that the RRDF/ENET option for maintaining shadow databases is currently unavailable for cluster nuclei.

An attempt was made to start a version 7.2 or above nucleus without first formatting the protection logs (PLOGs). PLOGs must be formatted when converting to version 7.2 or above.

The ADARUN statement's NSISN parameter value is greater than the allowed maximum of (Work block size - 6) / 4.

The ADARUN statement's LU parameter specifies a value greater than the byte count implied by the NAB (number of attached buffers) parameter. The error was detected during open operation.

Initialization failed for DTP=RM or DTP=TM either because of conflicts in the DTP (distributed transaction processing) ADARUN parameter settings (perhaps with the MODE, READONLY, or LOCAL parameter settings as well) or because of problems with the DDWORKR4/WORKR4 data set used in transaction management. For more information, read about the DTP ADARUN parameter in the Adabas Operations Manual and the DDWORKR4/WORKR4 data set in Adabas DBA Tasks.

Review the message(s) that precede this parameter error to determine the cause and resolution of the problem.

If you have Adabas Transaction Manager version 7.4 or earlier installed, an invalid parameter was specified with DTP=TM:

• single user mode (MODE=SINGLE) is not allowed.

• LOCAL=YES is not allowed.

• READONLY=YES is not allowed.

• LDTP (Work part 4) specified with a nonzero value is not allowed.

If it is necessary for some reason to hold data about incomplete transactions in the TM, LDTP with a nonzero value can be specified but IGNDTP=YES must also be specified. The IGNDTP parameter is for emergency use only and should only be used in consultation with your Software AG technical support representative.

Warning: Whenever the data on Work part 4 is ignored, the integrity of the incomplete global transactions that are related to that data cannot be guaranteed.

If you have Adabas Transaction Manager version 7.5 or later installed, an invalid parameter was specified with DTP=TM:

• single user mode (MODE=SINGLE) is not allowed.

• LOCAL=YES is not allowed.

• READONLY=YES is not allowed.

The value specified for the DTP parameter is invalid.

Specify "RM" or "TM" or "NO".

Error during generation of predefined formats:

• Reading system-file FCB or FDT failed;

• Translating internal format failed; or

• Pool for system-internal formats is too small.

If you have Adabas Transaction Manager version 7.4 or earlier installed, an invalid parameter was specified with NUCID:

• MODE=SINGLE is not allowed.

• READONLY=YES is not allowed.

• LFIOP must be nonzero.

• If protection logs are used, dual or multiple PLOGs must be specified.

• MXMSG must be between 1 and 32767.

• NUCID must not equal UBID.

If you have Adabas Transaction Manager version 7.5 or later installed, an invalid parameter was specified with NUCID:

• MODE=SINGLE is not allowed.

• READONLY=YES is not allowed.

• LFIOP must be nonzero.

• If protection logs are used, dual or multiple PLOGs must be specified.

• MXMSG must be between 1 and 32767.

• NUCID must not equal UBID.

Initialization of recovery logging failed.

Response code 75 (ADARSP075) or 77 (ADARSP077) was received because the checkpoint file is full. Checkpoints from offline utilities may have been lost.

Start the nucleus with UTIONLY=YES and reorder/increase the checkpoint file.

The database will not start until the PLOG data sets have been copied or reformatted. Most likely, the database was restored and the PLOG data sets had not yet been copied. They still may be needed for the regenerate function.

If the contents of the PLOG data sets are needed for a possible future regenerate function, run ADARES PLCOPY to copy them off. If the PLOGs are not needed, reformat them using the ADAFRM PLOGFRM function. In either case, start the nucleus after freeing the PLOG data sets.

The nucleus cannot run with the recovery log (RLOG) feature if it runs without PLOG or if PLOGRQ=SEL is specified. The protection log (PLOG) data set is not available; that is, PLOGRQ=SEL or PLOGRQ=NO is specified.

The nucleus was started with DTP=TM or DTP=NO, but Work Part 4 contains data about in-doubt transactions.

Start the nucleus with DTP=RM.

Machine clock (STCK) problem. The system was IPLed with the clock not set and running or set to an invalid date.

Correct the date (timestamp) and restart the nucleus.

Work part 2 has become too small because Work part 4 contains two-phase commit data that must be retained.

The ENET user exit 10 is missing.

ADACLU initialization failed and the nucleus terminated. A preceding PLXnnn message from ADACLU provided more detailed information.

Refer to the explanation and action of the preceding PLXnnn message.

A read-only (READONLY=YES) or single-user (MODE=SINGLE) nucleus cannot start if DTP=RM is specified.

During session open, the system detected that a Delta Save logging (DLOG) area was installed but parameter DSF was not set to YES. DSF=YES must be specified to run with the Delta Save Facility.

Restart the nucleus with parameter DSF=YES.

Alternatively, restart the nucleus with parameter DSF=NO; the nucleus then removes the DLOG area and runs in non-Delta Save mode.

Warning: After switching to non-Delta Save mode, it is not longer possible to perform delta save operations.

Initialization of the Delta Save Facility failed. A preceding Delta Save operator message indicates the cause of the failure.

Check messages from ADADSF.

The DSF logging area could not be removed. Another Adabas cluster nucleus is already running with Delta Save Facility active.

Start the nucleus with DSF=YES.

The previous nucleus session terminated with Work overflow. The nucleus has no free space on Work part 1 for protection information that will be produced during session autorestart.

In a cluster environment (Adabas Cluster Services or Parallel Services), start a different cluster nucleus (possibly a new one) with sufficient free space on Work part 1. In a non-cluster environment (base Adabas), restore and regenerate the database.

VOL-SER table could not be established.

Entire Conversion Services (ECS) initialization failed.

A database that uses Universal Encoding Support (UES) needs a version 7 or above Adabas router. If the database uses UES features, it cannot work with an Adabas router (ADASVC) version 6.2 or below.

Install a version 7.1 or above router (ADASVC).

Invalid ADATCP configuration or UES=NO. Running with TCPIP=YES requires universal encoding support.

Check and correct, if necessary, the TCPURL parameter. Install UES and specify UES=YES.

Adabas cluster initialization failed. Either the program was not running authorized or the GETMAIN failed.

Ensure that the program is APF-authorized. Review the space requirements for your system. If you are unable to determine the problem, contact your Software AG technical support representative.

During session open, an attempt to join the Adabas cluster communication group failed. This error initializing the Adabas cluster messaging service is preceded by other messages explaining the specific error.

Connect to lock structure failed.

Review the lock structure definition requirements. If you are unable to determine the problem, contact your Software AG technical support representative.

Connect to cache structure failed.

Review the cache structure definition requirements. If you are unable to determine the problem, contact your Software AG technical support representative.

Communication with other active Adabas cluster nuclei failed.

Review the requirements for communication between cluster nuclei running on the same operating system image and between operating system images running members of the cluster. If you are unable to determine the problem, contact your Software AG technical support representative.

Inconsistent structure name. Another Adabas cluster nucleus is already running with a different CLUCACHENAME or CLULOCKNAME parameter.

Ensure that all nuclei in a sysplex cluster use the same coupling facility cache and lock structure names.

Incompatible global parameters. Another Adabas cluster nucleus is already running with incompatible global parameters that cannot be modified online.

Reset nonmodifiable global ADARUN parameters the same for all cluster nuclei. You may be required to stop nuclei, change the parameter settings, and restart.

Locking/unlocking an Adabas cluster resource failed.

Contact your Software AG technical support representative.

Internal error.

Contact your Software AG technical support representative.

There are more than 31 nuclei in an Adabas Parallel Services cluster; this is not allowed.

Reconfigure your Adabas Parallel Services cluster so that you have 31 or fewer participating Adabas nuclei.

Invalid parameters specified with CLOGMRG=YES; LOGGING=YES is required; dual or multiple CLOGs are required.

Specify the correct ADARUN parameters and restart the session.

A cluster nucleus was started after abnormal termination with a different WORK data set. The PPT indicates that the previously used WORK data set still contains data, but this Cluster Service or Parallel Service nucleus was started with a different WORK data set.

Restart the cluster nucleus with the previously used WORK data set. Change the WORK data set only after normal termination.

Incompatible usage of dual PLOG data sets.

If the first active nucleus uses PLOG data sets, all subsequent nuclei must use PLOG data sets. If the first active nucleus does not use PLOG data sets, all subsequent nuclei must not use PLOG data sets.

Incompatible usage of UEX2 or UEX12.

If the first active nucleus uses either UEX2 or UEX12, all subsequent nuclei must use either UEX2 or UEX12. If the first active nucleus does not use UEX2 or UEX12, all subsequent nuclei must not use UEX2 or UEX12.

Improper configuration of Global Resource Serialization (GRS). A resource lock acquired by this nucleus was ineffective against a peer nucleus.

Contact your system programmer to ensure that GRS is configured in a way that GRS resource locks are mutually effective against one another on all systems on which you intend to run Cluster Services nuclei.

When LOCAL=YES is specified, all cluster nuclei for a database must start on the same system.

If LOCAL=YES is the intended parameter setting, start all cluster nuclei for the database on the same system. Otherwise, change the parameter setting to LOCAL=NO.

An error occurred during initialization of replication. Refer to the messages preceding Parm-Error 107 to determine what action to take.

Correct the condition specified in the message(s) displayed before Parm-Error 107 and restart initialization of replication.

If the replication definitions are stored on the Replicator system file and a change must be made to the Event Replicator Server definitions, complete the following steps:

1. Temporarily set the ADARUN parameter RPLPARMS to NONE.

2. Start the Event Replicator Server.

3. Make the related changes to the replication definitions in the Replicator system file.

4. Shut down the Event Replicator Server.

5. Change the ADARUN parameter RPLPARMS back to its original value.

6. Start the Event Replicator Server.

The Adabas nucleus tried to load a valid license module (load module ADALIC), but errors occurred. Other error messages providing more information about the error accompany this nucleus startup error

Verify that you have received a valid Adabas license (via installation tape or e-mail) and that it was installed correctly, according to the Adabas database installation steps specific to your operating environment. If problems persist, contact your Software AG technical support representative for assistance.

An error occurred when the Adabas nucleus called a hyperdescriptor exit for initialization.

Investigate the response code and subcode to determine the reason for the error.

A parameter value for cluster nuclei is invalid:

• MXCANCEL must be between 15 and 2,147,483,647 seconds.

• MXCANCELWARN must be zero (0) or between 4 and (MXCANCEL–1) seconds.

• MXMSG must be between 15 and 32,767 seconds.

• MXMSGWARN must be zero (0) or between 4 and (MXMSG–1) seconds.

• MXSTATUS must be zero (0) or between 15 and 21,474,836 seconds.

• MXWTOR must be zero (0) or between 15 and 64,800 seconds.

Correct the invalid parameter value to one of the valid values listed above.