Nucleus Startup Error Messages

#### Search Results

Search

# Nucleus Startup Error Messages

This section describes error messages and response codes issued by the Adabas nucleus. These errors may occur during nucleus startup, usually as the result of an ADARUN parameter error. The nucleus prints an error message and then terminates with an abnormal end (abend) code of 20 (see the abend code descriptions).

Refer to the Adabas Operations documentation for a description of the ADARUN parameters.

These error messages have the following format:

    PARM-ERROR nnn [detected during system open]

-where "nnn" is one of the startup errors and has the corresponding meaning described here. The error message may be followed by a brief error description.

### Overview of Messages

`PARM-ERROR 1 | PARM-ERROR 2 | PARM-ERROR 3 | PARM-ERROR 4 | PARM-ERROR 5 | PARM-ERROR 6 | PARM-ERROR 7 | PARM-ERROR 8 | PARM-ERROR 9 | PARM-ERROR 10 | PARM-ERROR 11 | PARM-ERROR 12 | PARM-ERROR 13 | PARM-ERROR 14 | PARM-ERROR 15 | PARM-ERROR 16 | PARM-ERROR 17 | PARM-ERROR 18 | PARM-ERROR 19 | PARM-ERROR 20 | PARM-ERROR 21 | PARM-ERROR 22 | PARM-ERROR 23 | PARM-ERROR 24 | PARM-ERROR 25 | PARM-ERROR 26 | PARM-ERROR 27 | PARM-ERROR 28 | PARM-ERROR 29 | PARM-ERROR 30 | PARM-ERROR 31 | PARM-ERROR 32 | PARM-ERROR 33 | PARM-ERROR 34 | PARM-ERROR 35 | PARM-ERROR 36 | PARM-ERROR 37 | PARM-ERROR 38 | PARM-ERROR 39 | PARM-ERROR 40 | PARM-ERROR 41 | PARM-ERROR 42 | PARM-ERROR 43 | PARM-ERROR 44 | PARM-ERROR 45 | PARM-ERROR 46 | PARM-ERROR 47 | PARM-ERROR 48 | PARM-ERROR 49 | PARM-ERROR 50 | PARM-ERROR 51 | PARM-ERROR 52 | PARM-ERROR 53 | PARM-ERROR 54 | PARM-ERROR 55 | PARM-ERROR 56 | PARM-ERROR 57 | PARM-ERROR 58 | PARM-ERROR 59 | PARM-ERROR 60 | PARM-ERROR 61 | PARM-ERROR 62 | PARM-ERROR 63 | PARM-ERROR 64 | PARM-ERROR 65 | PARM-ERROR 66 | PARM-ERROR 67 | PARM-ERROR 68 | PARM-ERROR 69 | PARM-ERROR 70 | PARM-ERROR 71 | PARM-ERROR 72 | PARM-ERROR 73 | PARM-ERROR 74 | PARM-ERROR 75 | PARM-ERROR 76 | PARM-ERROR 77 | PARM-ERROR 78 | PARM-ERROR 79 | PARM-ERROR 80 | PARM-ERROR 81 | PARM-ERROR 82 | PARM-ERROR 83 | PARM-ERROR 84 | PARM-ERROR 85 | PARM-ERROR 86 | PARM-ERROR 87 | PARM-ERROR 90 | PARM-ERROR 91 | PARM-ERROR 92 | PARM-ERROR 93 | PARM-ERROR 94 | PARM-ERROR 95 | PARM-ERROR 96 | PARM-ERROR 97 | PARM-ERROR 98 | PARM-ERROR 99 | PARM-ERROR 100 | PARM-ERROR 101 | PARM-ERROR 102 | PARM-ERROR 103 | PARM-ERROR 104 | PARM-ERROR 105 | PARM-ERROR 106 | PARM-ERROR 107 | PARM-ERROR 109 | PARM-ERROR 110 | PARM-ERROR 111 | PARM-ERROR 113 | PARM-ERROR 115 | PARM-ERROR 116 | PARM-ERROR 117 | PARM-ERROR 118 | PARM-ERROR 120 | PARM-ERROR 121 | PARM-ERROR 123 | PARM-ERROR 124 | PARM-ERROR 127 | PARM-ERROR 128 | PARM-ERROR 129 | PARM-ERROR 130`

PARM-ERROR 1 |
Explanation | 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.
Action | For single-user mode, the appropriate Adabas job control statements must be specified.

PARM-ERROR 2 |
Explanation | Data Storage data set(s) could not be opened. This probably indicates missing or invalid JCL or data sets for DATA.
Action | For single-user mode, the appropriate Adabas job control statements must be specified.

PARM-ERROR 3 |
Explanation | 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.
Action | For single-user mode, the appropriate Adabas job control statements must be specified.

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

PARM-ERROR 5 |
Explanation | 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.

PARM-ERROR 6 |
Explanation | 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.

PARM-ERROR 7 |
Explanation | The value of the ADARUN statement's user ISN hold queue count (NISNHQ) is invalid. The allowed maximum is either the NH ADARUN parameter setting or 16,777,215 (whichever is smaller).

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

PARM-ERROR 9 |
Explanation | The value of the ADARUN statement's Adabas cluster nucleus ID (NUCID) is invalid. The maximum value is 65000.

PARM-ERROR 10 |
Explanation | The value of the ADARUN statement's ISN list table length (LI) parameter is invalid. The minimum value is 2000.

PARM-ERROR 11 |
Explanation | The value of the ADARUN statement's sequential command table (LQ) parameter is invalid. The minimum value is 2000.

PARM-ERROR 12 |
Explanation | The value of the ADARUN statement's buffer pool length (LBP) parameter is invalid. The minimum value is 80,000.

PARM-ERROR 13 |
Explanation | The value of the ADARUN statement's internal format pool (LFP) parameter is invalid. the minimum value is 6000.

PARM-ERROR 14 |
Explanation | The value of the ADARUN statement's work pool length (LWP) parameter is invalid. The minimum value is 80,000.

PARM-ERROR 15 |
Explanation | 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.

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

PARM-ERROR 17 |
Explanation | With Adabas Transaction Manager, 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).

PARM-ERROR 18 |
Explanation | Fewer than 50 blocks are available for Work part 3. Autorestart has been executed.

PARM-ERROR 19 |
Explanation | The Work data set contains autorestart information for a different DBID or from a different Adabas version.
Action | Provide the correct Work data set and restart the nucleus.

PARM-ERROR 20 |
Explanation | GETMAIN below the 16MB line failed.

PARM-ERROR 21 |
Explanation | The general control blocks (GCBs) contain an invalid device type. The GCBs may have been overwritten, damaged, or otherwise destroyed.

PARM-ERROR 22 |
Explanation | An I/O error occurred when writing ASSO. The region is too small. The RABN that was to be written is printed.

PARM-ERROR 23 |
Explanation | 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.
Action | 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.

PARM-ERROR 24 |
Explanation | An I/O error occurred when reading ASSO. The RABN that was to be read is printed.

PARM-ERROR 25 |
Explanation | 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.
Action | 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.

PARM-ERROR 26 |
Explanation | Interregion communication could not be established.
Action | 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.

PARM-ERROR 27 |
Explanation | 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.

PARM-ERROR 28 |
Explanation | 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.

PARM-ERROR 29 |
Explanation | Invalid command log (CLOG) device definition.

PARM-ERROR 30 |
Explanation | FREEMAIN error.

PARM-ERROR 31 |
Explanation | System autorestart error (see the nucleus response code).

PARM-ERROR 32 |
Explanation | Error during buffer flush.

PARM-ERROR 33 |
Explanation | Error during Work initialization.

PARM-ERROR 34 |
Explanation | The nucleus is not allowed to start with READONLY=YES when an autorestart is pending.

PARM-ERROR 35 |
Explanation | File control block (FCB) check failed. The FCB may have been overwritten or otherwise destroyed.

PARM-ERROR 36 |
Explanation | Timer initialization failed, or operator communication could not be established.

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

PARM-ERROR 38 |
Explanation | DIB overflow.

PARM-ERROR 39 |
Explanation | Work pool is too small for the number of threads.
Action | Increase the LWP parameter value to at least 25 kilobytes times the number of threads.

PARM-ERROR 40 |
Explanation | Database version mismatch: the database is not version version revision-level.
Action | Run the ADACNV utility to bring the database to the correct version.

PARM-ERROR 41 |
Explanation | 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.
1 | An error occurred reading the PPT block (RABN) to determine the PLOG entries from the last database session.
2 | An error occurred trying to obtain the constant set for the PPT.
3 | An error occurred in the PPT verification routine.
4 | The PPT area is full and already contains 32 PPT entries that may be from cluster or non-cluster nuclei. To prevent losing data the nucleus is not permitted to start. Please make sure all relevant PLOG data sets are copied. An ADACHK PPTPRINT will help identify all the PLOG data sets.
5 | An error occurred attempting to check for any active PPT blocks.
6 | An error occurred while reading the PPT block prior to updating it.
7 | A bad file name was detected in the PPT for the Work data set.
8 | An error occurred trying to obtain the constant set for the PPT in order to log the Work data set in the PPT for the first time (no previous entry was found in the PPT for the Work data set).
9 | A bad file name was detected in the PPT for the Work data set when logging the PPT entry for the first time (no previous entry was found for the Work data set).
10 | An error occurred trying to obtain the constant set for the PPT entry in order to override a previous PPT entry.
11 | A bad file name was found when attempting to log the PLOGR1 data set in the PPT.
12 | A bad file length was found when attempting to compare the new PLOGR1 data set against the old one.
13 | A bad file name was found when attempting to log the PLOGR2 data set in the PPT.
14 | A bad file length was found when attempting to compare the new PLOGR2 data set against the old one.
15 | An error occurred trying to obtain the constant set for the PPT prior to updating the PPT. Either a different PLOG data set was detected or no PLOGs are being used.
16 | An error occurred when trying to obtain the constant set for the PPT prior to writing the PPT.
15 | An error occurred when attempting to read the PPT block to ensure that no other nucleus is currently using the same PLOG.
18 | An error was detected in the PLOG data set name when attempting to compare the current entry against other active entries in the cluster.
20 | An internal error occurred attempting to initialize the PPT. Please contact your Adabas support representative supplying the DDPRINT and dump from the current session, a PPTPRINT, and the DDPRINT from the previous session.

PARM-ERROR 42 |
Explanation | Error detected during system open: error writing PPT RABN; or a Work data set was already in use by another nucleus.

PARM-ERROR 43 |
Explanation | 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.

PARM-ERROR 44 |
Explanation | 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.

PARM-ERROR 45 |
Explanation | GETMAIN above the 16MB line failed; memory-related parameters probably too big.

PARM-ERROR 46 |
Explanation | UQE could not be generated.
Action | Increase NU parameter.

PARM-ERROR 47 |
Explanation | 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.

PARM-ERROR 48 |
Explanation | An error occurred during checkpoint generation: the takeover of checkpoints generated by offline utilities failed; or creation of the session start checkpoint failed.

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

PARM-ERROR 50 |
Explanation | Dual or multiple PLOG contains data from another database.

PARM-ERROR 51 |
Explanation | Parameter conflict: READONLY=YES is not permitted with UTIONLY=YES.

PARM-ERROR 52 |
Explanation | No dual or multiple PLOG available for protection logging. All PLOGs are due to be copied.

PARM-ERROR 53 |
Explanation | At least one of the specified PLOG data sets is already in use by another nucleus in the cluster.

PARM-ERROR 54 |
Explanation | IGNDIB=YES was specified but the DIB does not contain a conflicting nucleus or utility entry.
Action | Remove the IGNDIB parameter.

PARM-ERROR 55 |
Explanation | 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.

PARM-ERROR 56 |
Explanation | 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.

PARM-ERROR 57 |
Explanation | DIB entry missing. Another cluster nucleus is already active on this database, but its DIB entry is not present.

PARM-ERROR 58 |
Explanation | The Work block size is too small to store the maximum compressed data record permitted in this database according to MAXRECL definition.
Action | Increase the Work block length.

PARM-ERROR 59 |
Explanation | The Work block size is too small for the largest Associator block size present in this database.

PARM-ERROR 60 |
Explanation | The PLOG block size is too small to store the maximum compressed data record permitted in this database according to MAXRECL definition.

PARM-ERROR 61 |
Explanation | Important fields in the GCBs changed while this nucleus was starting. The nucleus is not able to handle this situation.
Action | Restart the nucleus.

PARM-ERROR 62 |
Explanation | CPU timer initialization failed.

PARM-ERROR 63 |
Explanation | RRDF=YES is not allowed. Note that the RRDF/ENET option for maintaining shadow databases is currently unavailable for cluster nuclei.

PARM-ERROR 64 |
Explanation | An attempt was made to start a nucleus without first formatting the protection logs (PLOGs).

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

PARM-ERROR 66 |
Explanation | 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.

PARM-ERROR 67 |
Explanation | 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.
Action | Review the message(s) that precede this parameter error to determine the cause and resolution of the problem.

PARM-ERROR 68 |
Explanation | With Adabas Transaction Manager 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.

PARM-ERROR 69 |
Explanation | The value specified for the DTP parameter is invalid.
Action | Specify "RM" or "TM" or "NO".

PARM-ERROR 70 |
Explanation | 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.

PARM-ERROR 71 |
Explanation | With Adabas Transaction Manager 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.

PARM-ERROR 72 |
Explanation | Initialization of recovery logging failed.

PARM-ERROR 73 |
Explanation | Response code 75 (ADARSP075) or 77 (ADARSP077) was received because the checkpoint file is full. Checkpoints from offline utilities may have been lost.
Action | Start the nucleus with UTIONLY=YES and reorder/increase the checkpoint file.

PARM-ERROR 74 |
Explanation | 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.
Action | 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.

PARM-ERROR 75 |
Explanation | 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.

PARM-ERROR 76 |
Explanation | The nucleus was started with DTP=TM or DTP=NO, but Work Part 4 contains data about in-doubt transactions.
Action | Start the nucleus with DTP=RM.

PARM-ERROR 77 |
Explanation | Machine clock (STCK) problem. The system was IPLed with the clock not set and running or set to an invalid date.
Action | Correct the date (timestamp) and restart the nucleus.

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

PARM-ERROR 79 |
Explanation | The ENET user exit 10 is missing.

PARM-ERROR 80 |
Explanation | ADACLU initialization failed and the nucleus terminated. A preceding PLXnnn message from ADACLU provided more detailed information.
Action | Refer to the explanation and action of the preceding PLXnnn message.

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

PARM-ERROR 82 |
Explanation | 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.
Action | 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.

PARM-ERROR 83 |
Explanation | Initialization of the Delta Save Facility failed. A preceding Delta Save operator message indicates the cause of the failure.
Action | Check messages from ADADSF.

PARM-ERROR 84 |
Explanation | The DSF logging area could not be removed. Another Adabas cluster nucleus is already running with Delta Save Facility active.
Action | Start the nucleus with DSF=YES.

PARM-ERROR 85 |
Explanation | 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.
Action | 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.

PARM-ERROR 86 |
Explanation | VOL-SER table could not be established.

PARM-ERROR 87 |
Explanation | Entire Conversion Services (ECS) initialization failed.

PARM-ERROR 90 |
Explanation | Invalid ADATCP configuration or UES=NO. Running with TCPIP=YES requires universal encoding support.
Action | Check and correct, if necessary, the TCPURL parameter. Install UES and specify UES=YES.

PARM-ERROR 91 |
Explanation | Adabas cluster initialization failed. Either the program was not running authorized or the GETMAIN failed.
Action | 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.

PARM-ERROR 92 |
Explanation | 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.

PARM-ERROR 93 |
Explanation | Connect to lock structure failed.
Action | Review the lock structure definition requirements. If you are unable to determine the problem, contact your Software AG technical support representative.

PARM-ERROR 94 |
Explanation | Connect to cache structure failed.
Action | Review the cache structure definition requirements. If you are unable to determine the problem, contact your Software AG technical support representative.

PARM-ERROR 95 |
Explanation | Communication with other active Adabas cluster nuclei failed.
Action | 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.

PARM-ERROR 96 |
Explanation | Inconsistent structure name. Another Adabas cluster nucleus is already running with a different CLUCACHENAME or CLULOCKNAME parameter.
Action | Ensure that all nuclei in a sysplex cluster use the same coupling facility cache and lock structure names.

PARM-ERROR 97 |
Explanation | Incompatible global parameters. Another Adabas cluster nucleus is already running with incompatible global parameters that cannot be modified online.
Action | Reset nonmodifiable global ADARUN parameters the same for all cluster nuclei. You may be required to stop nuclei, change the parameter settings, and restart.

PARM-ERROR 98 |
Explanation | Locking/unlocking an Adabas cluster resource failed.
Action | Contact your Software AG technical support representative.

PARM-ERROR 99 |
Explanation | Internal error.
Action | Contact your Software AG technical support representative.

PARM-ERROR 100 |
Explanation | There are more than 31 nuclei in an Adabas Parallel Services cluster; this is not allowed.
Action | Reconfigure your Adabas Parallel Services cluster so that you have 31 or fewer participating Adabas nuclei.

PARM-ERROR 101 |
Explanation | Invalid parameters specified with CLOGMRG=YES; LOGGING=YES is required; dual or multiple CLOGs are required.
Action | Specify the correct ADARUN parameters and restart the session.

PARM-ERROR 102 |
Explanation | 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.
Action | Restart the cluster nucleus with the previously used WORK data set. Change the WORK data set only after normal termination.

PARM-ERROR 103 |
Explanation | 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.

PARM-ERROR 104 |
Explanation | 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.

PARM-ERROR 105 |
Explanation | Improper configuration of Global Resource Serialization (GRS). A resource lock acquired by this nucleus was ineffective against a peer nucleus.
Action | 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.

PARM-ERROR 106 |
Explanation | When LOCAL=YES is specified, all cluster nuclei for a database must start on the same system.
Action | 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.

PARM-ERROR 107 | Replication initialization error
Explanation | An error occurred during initialization of replication. Refer to the messages preceding Parm-Error 107 to determine what action to take.
Action | 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: Temporarily set the ADARUN parameter RPLPARMS to NONE. Start the Event Replicator Server. Make the related changes to the replication definitions in the Replicator system file. Shut down the Event Replicator Server. Change the ADARUN parameter RPLPARMS back to its original value. Start the Event Replicator Server.

PARM-ERROR 109 |
Explanation | 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
Action | Verify that you have received a valid Adabas license (via the installation media) 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.

PARM-ERROR 110 |
Explanation | An error occurred when the Adabas nucleus called a hyperdescriptor exit for initialization.
Action | Investigate the response code and subcode to determine the reason for the error.

PARM-ERROR 111 |
Explanation | 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.
Action | Correct the invalid parameter value to one of the valid values listed above.

PARM-ERROR 113 |
Explanation | GETMAIN above the 2G bar failed. The memory-related parameters are probably too big.
Action | Verify that the requested 64-bit space is available to the nucleus.

PARM-ERROR 115 |
Explanation | An error occurred initializing ADASMF
Action | Review other messages accompanying or preceding this error to determine what happened and what action should be taken.

PARM-ERROR 116 |
Explanation | Invalid parameters were specified with the LOGWARN ADARUN parameter. Either ADARUN parameter UEX2 or UEX12 must be supplied when the LOGWARN parameter has been specified.
Action | Remove the LOGWARN parameter or specify a UEX2 or UEX12 ADARUN parameter with it.

PARM-ERROR 117 |
Explanation | Invalid parameters were specified for the ASSOSPACEWARN or DATASPACEWARN ADARUN parameter.
Action | Correct the specification for ASSOSPACEWARN or DATASPACEWARN ADARUN parameter.

PARM-ERROR 118 |
Explanation | An invalid autoincrease parameter was specified. The AUTOINCASSOTHRESHOLD or AUTOINCDATATHRESHOLD were not set to "0" or in the range from 50-100.
Action | Correct the invalid parameter value and try again.

PARM-ERROR 120 |
Explanation | An invalid autoincrease AUTOINCxxxxTOTAL parameter was specified. The specification for the AUTOINCASSOTOTAL or AUTOINCDATATOTAL parameter is smaller than the currently allocated size for the ASSO or DATA data set or exceeds 2,147,483,647 blocks or 16,777,215 blocks (3-byte RABNs).
Action | Correct the invalid parameter value and try again.

PARM-ERROR 121 |
Explanation | An invalid parameter value was specified for AUTOINCASSOSIZE or AUTOINCDATASIZE. The value was specified in blocks, but the size specified was smaller than the number of blocks per track for the device. The value must be either zero (0) or a number not smaller than the device track size. In z/OS environments, the minimum extent size is one track.
Action | Correct the invalid parameter value and try again. Specify a size that is either zero (to disable autoincrease for the component) or the minimum number of blocks for one full track.

PARM-ERROR 123 |
Explanation | UPDATECONTROL / INDEXUPDATE parameter conflict: UPDATECONTROL=NODELAY is permitted only if INDEXUPDATE=ADVANCED is specified.
Action | Specify either INDEXUPDATE=ADVANCED or UPDATECONTROL=DELAY (or omit the UPDATECONTROL parameter) and start the nucleus again.

PARM-ERROR 124 |
Explanation | The software level of this nucleus is not compatible with that of active cluster nuclei. See the preceding ADAX6C messages for details.
Action | Check the Release Notes to confirm this is an incompatible combination. For more information contact your Software AG technical support representative.

PARM-ERROR 127 |
Explanation | Error in cluster-wide Work access. A preceding message indicates the nature of the error.

PARM-ERROR 128 | Invalid parameter specified with ZIIP=YES: – (list of possible reasons)
Explanation | An Adabas component or feature is being used or has been specified that is not supported by Adabas for zIIP (AZPAD). The message shows a list of components or features that are not compatible with ZIIP=YES.
Action | Either remove the ZIIP parameter or specify ZIIP=NO, or remove or deactivate the specified component or feature that is not supported with ZIIP=YES.

PARM-ERROR 129 | zIIP initialization failed
Explanation | The initialization of the zIIP-related services of Adabas failed. A preceding ADAZnn message provides more information about the failure.
Action | Consult the documentation for the ADAZnn message preceding this error message.

PARM-ERROR 130 | Auditing initialization error - detected during system open
Explanation | Once AUDITING is turned on, the only option allowed for the AUDITING parameter is YES.
Action | Set `AUDITING = YES`.