Adabas Console Messages (ADAN* & ADACM*)

The Adabas nucleus at release level v.r.s has been initiated successfully. Multi- or single-user mode is indicated, and whether the nucleus is running with or without the Adabas Recovery Aid (ADARAI) log.

The Adabas nucleus session has been initiated and database protection logging either has or has not been specified. The subsequent execution of the REGENERATE and BACKOUT functions of the ADARES utility for any updates applied during the session is only possible when protection logging has been specified. However, transaction recovery for ET logic users is not affected by PLOG specification since data protection information for such users is still maintained on the Adabas Work file.

Adabas session initialization is in progress.

Initialization is in progress for the specified external nucleus ID (nnnnn) with the specified internal nucleus ID (xx). This message is useful for determining the internal system-assigned nucleus ID associated with the external user-assigned NUCID.

The Adabas nucleus detected an overflow condition on the Work data set that could not be rectified by normal Adabas backout processing. The Adabas session was therefore terminated abnormally.

In a non-cluster environment:

When running in a non-cluster environment, the quickest way to recover the database is to run an ADARES REGENERATE from the last protection log data sets at the time of the abend. The regenerate should start at the checkpoint created by the last ADASAV SAVE operation or the last nucleus start (SYN2 or SYNC checkpoint). This way of recovery is valid if no ADADBS (or AOS) DELETE FILE, RENUMBER FILE, ADAORD STORE OVERWRITE, or ADASAV RESTORE/RESTONL OVERWRITE functions were performed after the start checkpoint of the ADARES REGENERATE run.

An alternative way to recover the database that is always valid is to run an ADASAV RESTORE/RESTONL from the last database save, followed by an ADARES REGENERATE starting at the checkpoint created by that SAVE operation.

In a cluster environment (Adabas Cluster Services or Adabas Parallel Services):

When running in a cluster environment, the remaining active nuclei will perform an online recovery process. The failed nucleus can simply be restarted to continue processing after the online recovery.

If the online recovery process also gets a Work overflow, all remaining active nuclei will go down, too. In this case, any of the cluster nuclei that have not yet gotten a Work overflow can be started in an attempt to recover the database. Alternatively, or if this fails, a new nucleus can be added to the cluster. Its Work data set needs to be the same size as those of the other nuclei in the cluster and its LP parameter should be set as high as possible within that size. The failed nuclei can be restarted after the recovery has succeeded.

If all else fails, the database can be recovered as described above for the non-cluster environment.

Adabas has begun to write data protection log data to the data set identified by DD/PLOGRn. This means that the data set can no longer be copied to tape for subsequent use as input to the REGENERATE or BACKOUT functions of the ADARES utility. A user exit 2 (dual log processing) or a user exit 12 (multiple log processing) call either was not made or did not successfully copy the DD/PLOGRn data set with the ADARES utility.

Normally, the from and to blocks and the from and to timestamps being overwritten are given in the message. The last two lines are printed only if an error occurs when the nucleus determines the contents of the PLOG that is about to be overwritten.

An I/O error occurred on the dual or multiple protection log data sets. The Adabas nucleus terminates abnormally with user abend 21.

This message is displayed in response to the operator command DNH. The number of ISNs currently in the Adabas hold queue is represented by "nnn".

An I/O error occurred on sequential protection log SIBA. If the nucleus runs with PLOGRQ=YES or FORCE, the nucleus terminate with user abend 22; otherwise, the SIBA is set to DUMMY and processing continues without protection logging.

This message may follow an ADAN06 message.

This message is produced in response to DHQ and DHQA operator commands. The response consists of a header line followed by one or more file/ISN detail sections. Each file/ISN detail section is followed by information about the user who holds the ISN. When there are no active hold queue elements, the response is the single "Current HQ is empty" line.

The following table describes the possible substitutions provided in the message for each hold queue element.

This message is displayed in response to the operator command DNU. "nnn" indicates the number of user queue elements currently active.

This message is displayed in response to the DUQ, DAUQ, DUQA, DUQE, and DUUQE operator commands. Not every line of this message will appear; the actual text of the message is determined by the actual command that is issued.

• The "Current UQ is empty" line appears when there are no active user queue elements.

• The "Current UQ" header line appears only in responses to the DUQ, DAUQ, and DUQA commands.

• The optional "(restricted)" text is displayed if you issued an OP command with Command Option 1 set to "R" and is restricted to using only the listed files.

• The "No UQEs selected for display" line appears in DUQA, DUQE and DDUQE command responses when no UQEs satisfy the filter criterion.

The following table describes the possible substitutions provided in the message for each user queue element.

This message is displayed in response to the DNC operator command. "nnn" indicates the number of posted command queue elements.

This message is displayed in response to DCQ operator commands. The response consists of a header line followed by one or more detail sections describing active CQEs and a trailer line. When there are no active command queue elements, the response is the single "Current CQ is empty" line.

The following table describes the possible substitutions provided in the message for each command queue element.

The specified or available buffer pool space may not be large enough for the number of threads specified by the ADARUN NT parameter. This message is a warning. Adabas allocates 50 kilobytes per thread and processing continues.

Either increase the buffer pool size (specified by the ADARUN LBP parameter) or decrease the thread count (with the ADARUN NT parameter). Restart Adabas. If the error occurs again, allocate more address space for the Adabas nucleus and check the session I/O statistics for buffer efficiency.

This message is displayed on the console in response to the operator command DPARM. The current setting for each ADARUN parameter specified for an Adabas nucleus is given using this message number.

No action is required for this informational message.

This message is displayed in response to the operator command DSTAT. Various Adabas statistics appear for adabas-statistic, including statistics such as the number of Associator, Data Storage, and Work read and write I/Os and buffer flush statistics.

In response to the operator command DTH, shows the following information for each thread:

This message and the asynchronous buffer flush occur when the ADARUN LFIOP parameter specifies a nonzero value.

This message is used to display statistics about the number of ASSO and DATA I/Os by volume serial (VOLSER) number. The number of reads and writes to each volume is displayed. This message is printed as output for the operator command DVOLIO.

No action is required for this informational message.

This message is used to display statistics about the number of commands by file. This message is printed as output for the operator command DFILESTAT.

No action is required for this informational message.

This message is used to display statistics about the distribution of commands by type.

No action is required for this informational message.

An error occurred using file file. The operation may be either opening, closing or writing. The ADAIOR return code is rc and system code is any operating system return code.

If you are unable to resolve the error, contact your Software AG technical support representative.

When product license check did not pass, the product ppppp with product code ccccc was disabled in a utility or nucleus session.

In order to activate the product, provide a valid license from the start or - provided that the product supports this - during a nucleus session by replacing the old license file or load module and issue a LICREFRESH operator command.

In response to the operator command ZIIP=NO, this message indicates the Adabas nucleus is now executing in TCB mode (disabling the use of System z Integrated Information Processors). The ZIIP parameter value was changed to NO, from YES.

No action is required for this informational message.

In response to the operator command ZIIP=NO, this message indicates the Adabas nucleus was already executing in TCB mode (disabling the use of System z Integrated Information Processors). The ZIIP parameter value was not changed; it had already been NO.

No action is required for this informational message.

In response to the operator command ZIIP=YES, this message indicates the Adabas nucleus is now executing in SRB mode (enabling the use of System z Integrated Information Processors). The ZIIP parameter value was changed to YES, from NO.

No action is required for this informational message.

In response to the operator command ZIIP=YES, this message indicates the Adabas nucleus was already executing in SRB mode (enabling the use of System z Integrated Information Processors). The ZIIP parameter value was not changed; it had already been YES.

No action is required for this informational message.

In response to the operator command DZSTAT, these messages display the zIIP-related statistics of Adabas.

The first line shows the current execution mode: "SRB" (execution on zIIP enabled) or "TCB" (execution on zIIP disabled).

The following statistics correspond and are equivalent to the zIIP-related statistics at the end of the nucleus session statistics. See Understanding the zIIP-Related Statistics in the Adabas for zIIP documentation for detailed information about the various statistical figures.

No action is required for this informational message.

Online execution of the ADASAV utility's SAVE database function has started. The message shown above occurs for both database and file SAVEs and specifies the following:

Save this session/RABN information and the related PLOG and other SAVE output for later ADASAV restore activity.

Adabas is now ready to begin writing data protection information to the dual or multiple data protection log identified by DD/PLOGRn.

Execute the PLCOPY function of the ADARES utility at this time.

The online ADASAV SAVE FILE execution has begun. The SAVE operation begins with session session-number, using the SYN4 start point indicated by RABN block-number.

Save this session/RABN information and the related PLOG and SAVE output for later ADASAV RESTORE activity.

An online process has started, is ongoing or has completed, terminated due to an error, or was stopped. The type of process is displayed, as well as the file number and details about the process as appropriate.

In response to operator command DPPT (Display PPT), this and subsequent messages show the contents of the Participating Plex-ID Table (PPT).

In response to operator command DDIB (display DIB block), this message either indicates an empty DIB block or provides the following DIB information:

In response to the DDIB operator command, this message displays the file-number of a file that is locked because it is being used by an Adabas utility.

In response to the DRES operator command, the first line of the message is a text header line. The second and subsequent lines of the message will display the resource name, allocated size or value, current usage value, and the highest usage value reached ("high water mark") in the current session for the following resources:

The following is an example of the messages produced. The database ID and actual values shown in the example are variable, depending on the database and situation.

17:32:07 ADAN28 00035 2016-11-29 17:32:05 Resource       Size       Current    Highwater
17:32:07 ADAN28 00035 2016-11-29 17:32:05 AB  -Pool    1228800          N/A        1536 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 CQ  -Pool      96000            0         192 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 DUQ -Pool       7000            0           0 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 FI  -Pool     100000            0         160 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 HQ  -Pool     416000            0        5200 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Redo-Pool   10485760            0         176 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Sec -Pool      10000            0           0 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 TBI -Pool       4000            0           0 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 TBS -Pool      30000            0           0 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 UQ  -Pool     183456         1092        1456 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 UQF -Pool      48384           72         144 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Wrk1-IO B         50            0           5 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 WORK-Pool    5242880          128       34584 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Work Part1      1200            0           7 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Work Pt 1b         4            4           4 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Work Part2        20            0           0 
17:32:07 ADAN28 00035 2016-11-29 17:32:05 Work Part3       270            0           0 

In response to the STOPI operator command, this message displays either as "users stopped" or "no users stopped", depending on the action performed by the STOPI command.

There are already 32 entries in the parallel participant table. The nucleus ID entry specified was inactive and is being overwritten.

A Work data set was specified that is different from the one used in the previous session. This message is displayed only when the previously used Work data set contains a pending autorestart.

A Work data set was specified that is different from the one used in the previous session. An attempt to read the Work data set used in the previous session to search for a pending autorestart failed.

A Work data set was specified that is different from the one used in the previous session. The previously used Work data set was read and contains a pending autorestart. The ADAI63 message identifies the previous Work data set.

The protection log (PLOG) data sets have changed from the previous session and the previous PLOG data sets have not been copied. Because FORCE=YES was not specified, the parallel participant table (PPT) entry for these data sets has been overwritten.

Software AG recommends that you use the ADARES PLCOPY NOPPT function to copy the PLOGs from the previous session.

An attempt to add an extent to the Free Space Table (FST) was unsuccessful because the free space has become highly fragmented. Some free space could not be added and is therefore unavailable.

The ADAORD REORDER DB utility function will compress free space and reconstruct the FST.

In response to the operator command DLOCKF, this message displays the files that have been locked by LOCKF, LOCKU, LOCKX, or ALOCKF (if any). Different versions of this message appear, depending on the results. For file locked by LOCKF, LOCKU, or LOCKX, the type of lock (type) is displayed after the file number (nn). Possible types are:

Files locked by ALOCKF (advanced file locks) are identified with the "A-Files=nn" version of this console message. Finally, if no files are locked, the "No files locked" message appears.

No action is necessary for this informational message.

This message is produced in response to DFILES operator commands. The response consists of a header line followed by one or more detail sections describing active files and any active users of the files. Up to five users of each file are displayed. The following table describes the possible substitutions provided in the message for each file.

No action is necessary for this informational message.

In response to the operator command DFILUSE, this message displays the number of active commands (USAGE=n) for the specified file (FILE=n), or that the specified file does not exist in the database.

In response to operator command STOPF, this message indicates that no users were active when the command was issued.

In response to the operator command DONLSTAT, this message lists all online processes present in the nucleus session, the kind of process, the file number, the current RABN or ISN (depending on the function), the ID of the process, and whether the process is active or suspended.

A CLOG or PLOG data set has been dynamically added or deleted by an ADADBS utility function or using the Adabas Online System (AOS). The CLOG or PLOG data set name (dsn) and number (x) are given in the message.

The command or function issued was completed successfully.

The command issued was accepted by Adabas.

Either the request request was invalid or it was not correctly entered.

Check the request/command syntax and validity, then retry the request.

• A request to end a nucleus session with DUMP is invalid, and should not be retried.

• An operator command to change the cache space parameters for a file (CFILE) that has an existing cache space is invalid. It is necessary to first delete the existing cache space and then add a new one with different parameters.

Adabas could not perform the function because of

• space restrictions;

• a conflict between the requested command/function and the system status.

Check for other related messages, correct any previously indicated errors, then retry the operation. Otherwise, contact your DBA, system support personnel, or Software AG technical support.

Various message texts are provided with message ADAN45:

The requested function/command was valid but could not be executed. This message occurs preceded by one of the following ADAN46 messages, which provide reasons why the current nucleus status does not allow the requested function:

A SYNCC, ADAEND, HALT, or CANCEL operator command was issued, but is not permitted during the current online save operation.

Wait until the online save has ended, then retry the command.

In Entire Net-Work, target node IDs must be unique across all connected systems. If an attempt is made to connect to a target node ID that is not unique, the system terminates abnormally (ADAEND).

Identify the conflicting node IDs and determine which one is to be active under the specified ID number.

A LOCKF, LOCKU, or LOCKX operator command was issued but the file specified is currently in use.

Wait until the file is no longer in use, then retry the command.

The file specified in the ALOCKF function is not loaded.

The last, incomplete transaction of the specified user (or job, if the user is not displayable) has been backed out during Adabas session autorestart or at the end of REGENERATE processing. The user ID (or job name) and communication ID are shown.

The user ID is the user's ET-ID. For users without an ET-ID, "ADAEND" is displayed as their user ID.

The field following UID= is the last 8 bytes of the 28-byte communication ID of the user in hexadecimal format; that is, the terminal ID for an online user or a STCK time stamp for a batch or TSO user.

None required. This is an information message only. The transaction status of the specified users may need to be checked.

ET-SYNC has occurred for the TRANSACTIONS SUSPEND process. This message is followed by the ADAN4E message.

All verifications in the nucleus are complete and the SUSPEND process has started. TT indicates when the transactions will time out. The TT value is derived either from the TTSYN parameter in the ADADBS TRANSACTIONS SUSPEND TTSYN=nn job or the nucleus default ADARUN TT setting.

TPC is in effect and there are transactions on PET status. This is followed by the ADAN4B message displaying the original TT value.

The timer specified by TRESUME in the ADADBS TRANSACTIONS SUSPEND process has been exceeded. The database returns to normal processing. This message is followed by the ADAN4F message.

ET-SYNC has occurred for the SUSPEND function and updates are discontinued until either the RESUME function is issued or the timer specified by TRESUME expires.

The database once again accepts and processes update commands as a result of either the RESUME function or a timeout.

This message documents the files that were excluded from autorestart due to the ADARUN AREXCLUDE parameter. These files remain unavailable for normal users and must be recovered (restore - regenerate).

Adabas repeats the operator command "command" before continuing. The second message is written for an operator command issued by an Adabas Online System user.

During session start, the nucleus detected the specified descriptor of the file fnr left over from an incomplete online invert operation. If the previous session terminated abnormally, the nucleus automatically releases the incomplete descriptor.

If the nucleus did not release the descriptor and no regenerate on the file in question is to follow, release the incomplete descriptor using the AOS or ADADBS RELEASE function.

The nucleus is trying to perform an action that only one nucleus or utility can do at a time. Another nucleus or utility is performing a similar action at the moment, so this nucleus must wait. rrrddddd identifies the logical resource used for serialization. The resource name comprises three letters followed by five digits representing the database ID. Possible resource names include:

• SSEddddd for serializing nucleus session start and end.

• DIBddddd for serializing DIB updates.

• FSTddddd for serializing FST updates.

None required. This message is for information only.

If the nucleus hangs after displaying this message, another nucleus or utility is blocking the logical resource specified in the message. Identify the other job and either allow it to continue or terminate it.

An attempt to lock or unlock a logical resource failed. The ADAIOR function number was ff (in hexadecimal), its response code cc (in hexadecimal). Depending on the circumstances, the nucleus terminates abnormally or ignores the error.

This is an unexpected error. Contact your Software AG technical support representative.

During session start (or, with Adabas nucleus clusters, during online recovery), the Adabas nucleus found recovery data on the Work data set (or Work data sets, in the case of nucleus clusters) that is needed to recover the database from a previous failure. The nucleus performs session autorestart logic.

These message lines are printed when the Adabas nucleus finishes a phase of session autorestart (backward repair, forward repair, autobackout). The statistics (block counts and time durations) indicate how much repair and recovery work has already been done and how much remains to be done.

Session autorestart repairs physical inconsistencies in the database, redoing updates belonging to completed transactions and backing out updates belonging to incomplete transactions.

The following is an example of the messages produced. The database ID and actual values shown in the example are variable, depending on the database and situation.

ADAN56 dbid backward repair done
ADAN56 dbid work blocks processed    =             887
ADAN56 dbid work blocks remaining    =           1,269
ADAN56 dbid time used so far         =     00000:00:03

 
ADAN56 dbid forward repair done
ADAN56 dbid work blocks processed    =           1,774
ADAN56 dbid work blocks remaining    =             382
ADAN56 dbid time used so far         =     00000:00:05

ADAN56 dbid Autobackout done
ADAN56 dbid time used so far         =     00000:00:06

Various message texts can appear for this message number. The explanation and action for each is given in the following table.

An autorestart operation found that a buffer flush was being performed when the action that caused the autorestart occurred; the buffer flush was therefore incomplete. The nucleus completes autorestart processing before terminating.

• If the cause of the autorestart was a power failure, the database may be inconsistent in a way that cannot be repaired by autorestart.

• If the cause of the autorestart was not a power failure, the database has already been made consistent and needs only to be restarted.

If a power failure caused the autorestart and your storage subsystem does not guarantee that no block is partially written, perform the following utility operations to ensure database consistency:

• ADASAV RESTORE (database)

• ADARES REGENERATE

If your storage subsystem technology does guarantee that no block is partially written, even in the case of power failure, there is no need to restore/regenerate after this message is received: simply restart the nucleus.

You may restrict the RESTORE - REGENERATE to the files modified by autorestart (see the ADAN5A message) but be sure to run the REGENERATE FILE with transaction logic (autobackout at the end of the regenerate) by specifying the ADARES parameter CONTINUE.

If the autorestart operation was not caused by a power failure, do not perform the utility operations described above. Simply restart the nucleus.

An internal error occurred that caused the nucleus to terminate abnormally. The message shows the abend code and the address, if possible also the module and offset, where the error was detected, as well as the contents of the general registers at that time.

Contact your Software AG technical support representative.

During nucleus startup, an autorestart was performed that modified the files listed in the message text.

The ARM ELEMENTNAME parameter has been specified and the nucleus has successfully registered or deregistered this element with the Automatic Restart Manager (ARM).

The ARMELEMENTNAME parameter has been specified, but registering or deregistering with the Automatic Restart Manager (ARM) has failed. ARM has returned the reason code shown. The possible reason codes are described in the IBM manual MVS Programming Sysplex Services Reference. Common reason codes include:

• X`002C' The ARMELEMENTNAME parameter value is invalid.

• X`013C' The Adabas nucleus has improper SAF authorization to register with ARM.

• X`0150' ARMELEMENTNAME is not unique across the sysplex.

• X`0004' The system does not support ARM.

The nucleus ignores the error and continues processing.

Look up the meaning of the reason code. If this explains the error, correct it. Otherwise, contact your systems programmer or your Software AG technical support representative.

This message is displayed in response to the DNFV operator command.

• FNR supplies the file number

• A is set to either "Y", indicating that the file is being used by access-only users, or blank, indicating that it is not being used by access-only users.

• U is used in the same way as A, but indicates usage by update users.

• ID shows the ID of the database which has exclusive control over the file

• CA provides the count of how many access-only users are using the file.

• CU is the count of how many update users are using the file.

A LOB file group consisting of a file with LB fields (base file) and a file containing the associated LB field values (LOB file) has become inconsistent. An illogical sequence of utility operations has exported (saved, restructured, unloaded) the files from, and subsequently reimported (restored, stored, loaded, defined) them into the database in a way that the two files no longer reflect the same point in time during processing.

The base and LOB file have gotten out-of-sync. It is possible that the base file contains references to LB field values that should be, but are not, stored in the LOB file. Also, the LOB file may contain LB field values that should be, but are not, referenced by records in the base file.

Investigate the cause of the base and LOB file getting out-of-sync. Take corrective action, such as reloading or restoring both files, depending on the findings. If necessary, you can use the following function to just mark the two files as being back in sync:

ADADBS MODFCB FILE=base-fnr,LOBFILE=lob-fnr

The nucleus is retrying the attempt to switch PLOGs or CLOGs. The retry is performed when the FEOFPL/CL attempt is made and there is currently no free PLOG or CLOG.

Submit an ADARES PLCOPY or CLCOPY to copy the appropriate data sets.

A user's attempt to submit database calls has failed because the user's security system user ID is unknown. The following table describes the possible substitutions provided in the message.

This message occurs when the ADARUN SECUID parameter is set to "REQUIRE".

Determine why the user's security system user ID is not known to Adabas and resolve the problem. Changing the ADARUN SECUID setting to WARN or ALLOW is one possible solution. For additional assistance, contact your Software AG technical support representative.

A security error occurred because the security system user ID changed. Adabas calls by this user are being rejected. The following table describes the possible substitutions provided in the message.

This message occurs when the ADARUN SECUID parameter is set to "REQUIRE".

Determine why the user's security system user ID has changed and resolve the problem. For additional assistance, contact your Software AG technical support representative.

The security system user ID is unknown, but calls made by the user are being allowed. The following table describes the possible substitutions provided in the message.

This message occurs when the ADARUN SECUID parameter is set to "WARN".

Determine why the user's security system user ID is not known to Adabas and resolve the problem. Changing the ADARUN SECUID setting is one possible solution to controlling the display of this message. For additional assistance, contact your Software AG technical support representative.

A security error occurred because the security system user ID changed. Adabas calls by this user are being allowed. The following table describes the possible substitutions provided in the message.

This message occurs when the ADARUN SECUID parameter is set to "WARN".

Determine why the user's security system user ID has changed and resolve the problem. For additional assistance, contact your Software AG technical support representative.

The nucleus prints this message to the operator console and DD/PRINT when certain response codes are set. This message is used to inform your database administrator of a potential problem. The nucleus will print the message and then continue processing as it did before.

Within the message, the following information is supplied:

No action is required for this informational message.

The Adabas nucleus detected an internal I/O error.

Contact your Software AG technical support representative.

A security violation occurred.

The following table describes the possible substitutions provided in the message.

Review the Adabas response code documentation to determine the cause of the security violation.

The function INCREASE or ADD for an Associator or Data Storage extent has been performed by the nucleus. The nucleus terminates and permits the newly added part of the Associator to be allocated and formatted, which is necessary before another Adabas session can be started and the new extent can be used.

Perform the necessary allocation/reformatting utility operations, and then restart the nucleus.

An I/O error occurred during asynchronous buffer flush operation. The nucleus ends operation.

Correct the cause of the I/O error.

ECS is the Entire Conversion Services, a subsystem of the Adabas universal encoding support (UES) system. This message is written after a function of the subsystem has failed.

Error codes produced by the ECS component are described in Universal Encoding System (UES) Component Error Codes.

The following ECS functions may return errors:

Resolve the problem and try again.

The specified version of Entire Conversion Services was successfully initialized.

The specified collation descriptor user exit was successfully initialized.

The nucleus prints this message to the console and DD/PRINT when a command tries to reference a logically-deleted descriptor. The command will receive response code 39. This message is used to inform your database administrator that the logically-deleted descriptor is still used. The nucleus will print the message and then continue processing as it did before.

Within the message, the following information is supplied:

No action is required for this informational message.

To avoid flooding the event log and the console with redundant events and messages, Software AG has set limits on the number of security error messages created. This message occurs when that security error message limit has been exceeded.

No action is necessary for this informational message. Use other security error messages that have been sent to determine the cause (and solution) for the problem.

To avoid flooding the event log and the console with redundant events and messages, Software AG has set limits on the number of security warning messages created. This message occurs when that security warning message limit has been exceeded.

No action is necessary for this informational message. Use other security warning messages that have been sent to determine the cause (and solution) for the problem.

Adabas Caching Facility was successfully initialized.

No action is required for this informational message.

Adabas Caching Facility determined that 64-bit virtual storage that can be backed by non-pageable, 1M large pages is available for use.

No action is required for this informational message.

Adabas Caching Facility determined that 64-bit virtual storage that can be backed by non-pageable, 2G large pages is available for use.

No action is required for this informational message.

Adabas Caching Facility determined that 64-bit virtual storage is available for use.

No action is required for this informational message.

In an Adabas nucleus cluster environment prior to version 7.2, caching is available only for Work parts 2 and 3.

No action is required for this informational message.

The highest RABN of an ASSO or DATA extent, as defined in the GCBs, is not readable. Most likely, an Adabas Online System or ADADBS INCREASE function was performed without allocating and formatting the new database area. The nucleus continues. Any attempt to access an unallocated area of the database causes an I/O error.

Ensure that the defined extents are completely allocated and formatted.

An attempt was made to change cache space parameters for a file without first deleting its existing cache space.

Delete the existing cache space for the file; then add a new cache space with the changed parameters.

This message displays the output of the CSTAT, CFSTAT, and CSUM operator commands of the Adabas Caching Facility. See the Adabas Caching Facility documentation for more information.

The CSTAT command is used to display the current cache space statistics. A sample report display is shown below:

+--------------------------------------------------------+
+ 005 DATA SPACE, DATA, RABNS 81 THRU 135                +
+--------------------------------------------------------+
+ ALLOCATED, LA=17:04:26                                 +
+--------------------------------------------------------+
+        253 CACHE WRITES  +            47 BLKS IN CACHE +
+         47 READ EXCPS    +       172,032 DATA SPC SIZE +
+        408 CACHE READS   +            55 BLKS/DATA SPC +
+        455 TOTAL READS   +          1320 INDXSPCE SIZE +
+       89.6 DSP EFFICIENCY+       167,936 MAX DSP USED  +
+   0.071810 MAX NIOT (SEC)+      0.698682 MAX EXCPT(SEC)+
+   0.000080 MIN NIOT (SEC)+      0.009600 MIN EXCPT(SEC)+
+   0.000245 AVE NIOT (SEC)+      0.167286 AVE EXCPT(SEC)+
+--------------------------------------------------------+

The CFSTAT command is used for file-level caching to display the current cache space statistics for one or more files. When file-level caching is active, a report is produced for each RABN range associated with the file request. A sample report display is shown below:

+--------------------------------------------------------+
+ FNR 00001 AC CL1 EXT RABNS 91 THRU 93
+--------------------------------------------------------+
+   ALLOCATED, LA=09:55:36           
+--------------------------------------------------------+
+         60 CACHE WRITES  +             0 BLKS IN CACHE +
+          2 READ EXCPS    +    32,767,404 EXTM  SIZE    +
+         52 CACHE READS   +        16,351 BLKS/EXTM     +
+         54 TOTAL READS   +            28 RABN TAB SIZE +
+       96.2 ESP EFFICIENCY+         4,008 MAX ESP USED  +
+   0.001503 MAX NIOT (SEC)+      0.092800 MAX EXCPT(SEC)+
+   0.000018 MIN NIOT (SEC)+      0.092071 MIN EXCPT(SEC)+
+   0.000062 AVE NIOT (SEC)+      0.092435 AVE EXCPT(SEC)+
+--------------------------------------------------------+

The CSUM command is used to display, for a session, the accumulated cache summary for all active and inactive cache spaces, including statistics from previously deleted cache spaces. A sample report display is shown below:

+--------------------------------------------------------+
+ A D A B A S DYNAMIC CACHING SESSION SUMMARY            +
+        52.5 CURRENT ADABAS BUFFER EFFICIENCY           +
+         7.2 PROJECTED NON-CACHE BUFFER EFFICIENCY      +
+           3 ACTIVE CACHE SPACES                        +
+           4 CACHE SPACES DEFINED                       +
+ ------------ -----ASSO---- -----DATA---- -----WORK---- +
+ CACHE WRITES        27,367         6,674           212 +
+   READ EXCPS            78           444             0 +
+  CACHE READS        27,288         6,203         4,865 +
+  TOTAL READS        27,366         6,647         4,865 +
+   EFFICIENCY          99.7          93.3         100.0 +
+--------------------------------------------------------+

The READONLY status of the nucleus has been switched. This message occurs as a response to the operator command or Adabas Online System function READONLY.

The "utility use only" (UTIONLY) status of the nucleus has been switched. This message occurs as a response to the operator command or Adabas Online System function UTIONLY.

The ADARUN LP parameter was increased in the current Adabas session. Therefore, additional Work part 1 RABNs had to be formatted.

None required. Consider increasing the Work data set to ensure that sufficient Work part 3 space is available.

Various message texts can appear for this message number. The explanation and action for each is given in the following table.

Examine error ADAN86 for the cause of the error.

Various message texts can appear for this message number. The explanation and action for each is given in the following table.

User actions are given in the explanation.

Various message texts can appear for this message number. The explanation and action for each is given in the following table.

User actions are given in the explanation.

During initialization of a nucleus defined with DTP=RM, a logic error was detected while executing DTP functions.

The nucleus terminates abnormally with abend 19. The registers at entry to the abend and the load addresses of ADANC0-ADANCB are printed.

Contact your local Software AG technical support representative.

Various message texts can appear for this message number. The explanation and action for each is given in the following table.

User actions are given in the explanation.

The file specified for caching is already being cached by Adabas Caching Facility. This error can occur if you use operator or Adabas Online System commands in an attempt to define different types of memory to cache Associator and Data Storage RABNs of the same file.

It is possible at startup using ADARUN CFILE parameters to specify different types of memory to cache Associator and Data Storage RABNs of the same file. However, once a memory type is set for caching any RABNs of a file, Adabas Online System and operator commands do not allow you to specify any other memory type for the same file. If you want to change the memory type for the file, you must delete the existing cache space and then add a new one with different parameters.

ADACSH (Adabas Caching Facility) could not acquire the Constant Set during initialization..

Contact your local Software AG technical support representative.

ADACSH could not acquire space for its working areas. Adabas Caching Facility is not started and the associated message ADAN8H is displayed.

Increase the region, partition, or address space size.

A RABN range has been activated. This generally occurs when Adabas writes a RABN from its buffer pool to cache storage.

Adabas Caching Facility could not allocate storage for the track or hiperspace I/O buffer, or for RABNINDX blocks. When the track I/O buffer is not available, a RABN I/O request being considered for read-ahead caching is issued normally. When the hiperspace I/O buffer is not available, caching using hiperspaces is not possible. When the RABNINDXes for a cache space area are not available, the attempt to allocate the associated cache space area fails and is not attempted again until at least CRETRY seconds have elapsed.

Increase the region, partition, or address space size.

The Adabas Caching Facility attempted to allocate 64-bit virtual storage backed by non-pageable large pages. The storage was allocated either for an L64 cache space backed by 1M large pages or for a G64 cache space backed by 2G large pages.

The original target size of the allocation request is given in the message (xxx). For an L64 cache space to be backed by 1M large pages, this was then rounded up to the next integral multiple of one megabyte. For a G64 cache space to be backed by 2G large pages, this was then rounded up to the next integral multiple of two gigabytes.

If the word "NOT" is omitted from the message, the storage allocation request was successful and the storage was backed by non-pageable large pages of the specified size. If the word "NOT" occurs in the message, insufficient large pages of the type requested were available. Instead, storage was allocated and backed by pageable 4 kilobyte pages.

This message is written to the operator console only.

If the message indicates that the storage is not backed by large pages, consider whether the number of fixed large pages specified for the operation system using the LFAREA parameter in SYS1.PARMLIB member IEASYSxx should be increased. If the message indicates that the storage is backed by large pages, no action is required for this informational message.

Adabas Caching Facility was not activated due to a previous parameter specification or error condition.

Depending on the utility, Adabas Caching Facility acted to maintain database integrity by releasing an entire cache space or a number of cache blocks because of a parallel utility operation.

A cache storage area was released after it was inactive for a continuous elapsed time period of CCTIMEOUT seconds.

This message is displayed whenever a RABN range is activated. This generally occurs when Adabas writes a RABN from its buffer pool to cache storage.

An attempt was made to add an additional cache storage area for a cache space.

When the request is successful, the additional storage is available for the cache space and "yyy" reflects the size of the new area which is equal to the current CASSOMAXS or CDATAMAXS setting.

If unsuccessful, the system simply uses the storage areas already allocated for the cache space until CRETRY seconds pass. Then another attempt is made to add a new storage area for the cache space if this is still required.

Check with the system programmer; the extension failure may be due to insufficient ESA capabilities (memory or page data sets), or too many data spaces or hiperspaces allocated at one time.

An Adabas Online System (AOS) operator issued a command to change one of the Adabas Caching Facility system parameters.

Demand caching is in effect and a RABN range or file has been inactive for a period longer than the CCTIMEOUT specification.

An error occurred during the processing of a hiperspace cache request. The system return code from the request (nn) is given in the message.

Generally speaking, this error causes a request to write to or read from a hiperspace cache to fail. In most cases, the system can continue by reading the RABN from disk or writing, ignoring the request from the nucleus.

However, where Work parts 1 or 2 are being cached 100%, the failure of a request to return a cached RABN may have more serious consequences because there is no copy of the RABN on disk and therefore the I/O cannot be satisfied.

Determine if the error was caused by some event or problem in the system that could impact on hiperspaces used by Adabas Caching Facility. If there is nothing evident, report the error and the circumstances surrounding the error to your Software AG technical support representative.

An attempt to allocate dynamic storage in extended memory failed due to a shortage of space in extended memory.

Review your storage estimates to insure that there is sufficient storage available for the parameters specified.

The write to hiperspace operation returned a nonzero condition code. The requested RABN is not written to hiperspace and is flagged as unused.

No operator intervention is required.

An attempt to allocate the first storage block for a cache area failed.

No storage is available for caching the RABNs for which the cache storage allocation was attempted. The situation continues at least until CRETRY seconds have elapsed and another attempt to allocate the storage is made, if required.

Check with the system programmer; the allocation failure may be due to insufficient memory or page data sets or too many data spaces and/or hiperspaces allocated at one time.

An operator command was received and was either successfully completed or not.

If the command was unsuccessful, check DDPRINT for warning messages to determine why the command failed. Alternately, insure that the syntax used for the command is correct.

This message is displayed for each inactive RABN range or file that is enabled when the Adabas buffer efficiency drops below the specified CDEMAND threshold level.

This message is displayed in response to the CPARM operator command. The parameters displayed are:

When Adabas Caching Facility first accesses a RABN belonging to a file to be cached, it learns about the extents and RABNs associated with the file and synchronizes its view of the file with the file's FCB.

If ADASCR detects that the structure of the file has changed (e.g., a new extent is added), ADASCR resynchronizes its view of the file at the next possible opportunity and issues this message.

File-level caching is active for the current nucleus.

A logic error occurred during Adabas Caching Facility processing.

Report the error and the hexadecimal offset to your Software AG technical support representative.

The Adabas trigger driver was unable to obtain enough storage within the region or address space to set up its I/O buffers.

Determine the source of the problem and correct it. Try increasing the region size for the MPM.

The Adabas trigger driver was unable to obtain enough storage within the region or address space to set up its I/O buffers.

Increase the region size for the MPM.

The triggers and stored procedures facility was initialized successfully. Commands for detecting triggers are now processed.

A request to refresh the trigger table buffer was made.

No action is required.

The trigger table buffer was refreshed. The triggers have been reloaded and the Adabas nucleus will continue to run normally.

The ADARUN parameter SPT=YES was specified; however, because the database administrator has overridden this using the Adabas triggers subsystem, triggers will not be activated.

To reactivate triggers, access the Adabas triggers subsystem function "modify profile information" (located on the Miscellaneous Functions Menu), and change the triggers status field in the profile to "active".

The Adabas nucleus has been started with SPT=YES and MODE=SINGLE. This is not allowed.

Start the nucleus with MODE=MULTI in the ADARUN parameters (DDCARD), or specify SPT=NO.

During the startup of the Adabas trigger driver, certain communication must occur with Adabas Parallel Services if it is active. The Adabas trigger driver was unable to complete the communication.

After obtaining a dump, contact your Software AG technical support representative and report the error.

During the refresh of the trigger table buffer, an error occurred. This error was identified by a previous console message. The error causes an inconsistent state in the triggers subsystem that necessitates a shut-down as indicated in the error action option setting in the profile.

Review previous console messages to determine the error. Correct it and, if necessary, restart the nucleus to restart the triggers subsystem.

During the triggers initialization process, Adabas needs to read the trigger file FDT; however, the FDT could not be found. As a result, triggers will not be activated.

Determine the reason why the FDT could not be found and correct the problem. Ensure that the file was correctly loaded as a system file.

During the triggers initialization process, Adabas needs to read the trigger file FCB; however, the FCB could not be found. As a result, triggers will not be activated.

Determine the reason why the FCB could not be found and correct the problem. Ensure that the file was correctly loaded as a system file.

During the triggers initialization process, Adabas needs to read the entries from the trigger file; however, a nonzero response code was received. As a result, triggers will not be activated.

Determine the source of the problem; that is, analyze the response code and take the necessary action to resolve the problem.

The nucleus terminates with a dump due to failure of the internal autorestart.

During the triggers initialization process, Adabas needs to read the entries from the trigger file; however, no valid trigger entries were found in the file. As a result, triggers will not be activated.

Verify that there are triggers defined on the trigger file and that the trigger file is set up correctly; that is, the file is loaded on the database where the error occurred.

During the triggers initialization process, Adabas needs to load the entries from the trigger file into its buffer; however, the size calculated for the buffer is incorrect. The cause could be one of the following:

• triggers were added by some means other than the Adabas triggers subsystem, or

• the buffer size was not calculated or was specified incorrectly. As a result, triggers will not be activated.

Recalculate the size required for the buffer. Issue the NUMBER or CHECK command from the Modify Profile screen to verify that the number is recorded correctly by Adabas Online System. Also check the buffer size specified in the "trigger table size" field in the Adabas triggers and stored procedures profile.

An attempt was made to process triggers that are assigned to file numbers greater than the maximum acceptable file number; that is, the highest loaded file plus 10.

This message is a warning. Triggers should not be assigned to file numbers greater than the maximum file number allowed.

During the triggers initialization process, Adabas needs to read the profile definition from the trigger file; however, the profile definition could not be found. As a result, triggers will not be activated.

Using the Adabas triggers subsystem, add a profile for the subsystem.

During the triggers initialization process, Adabas needs to read the profile definition from the trigger file. However, an internal error occurred during the read. As a result, triggers will not be activated.

Determine the cause of the error and correct it using the Adabas triggers subsystem. Possibly modify the profile again to ensure that it is correct.

During the triggers initialization process, Adabas needs to acquire space for its buffer, but insufficient space was found. This can occur if the value specified for the LWP ADARUN parameter is too small. As a result, triggers will not be activated.

Check the value specified for the LWP ADARUN parameter and increase it as appropriate.

The Adabas nucleus started with SPT=YES; however, no trigger file exists for this database. As a result, triggers will not be activated.

Either set SPT=NO or load a trigger file that contains at least one trigger definition onto the database.

During the triggers initialization process, Adabas needs to start the subsystems for the execution of procedures; however, the name specified was invalid. As a result, triggers has been deactivated.

Check the batch Natural name setting in the Adabas triggers and stored procedures profile. Also ensure that the Natural nucleus module is concatenated in the JCS/JCL startup and is a loadable module.

A serious or fatal error occurred that created an inconsistent state in the system. The nucleus has been shut down.

Review previous console messages to determine the error. Correct it and restart the nucleus to restart the triggers subsystem.

Triggers incurred one or more errors and has been deactivated. The error action taken depends on the error action setting in the Adabas triggers and stored procedures profile.

Review previous console messages to determine the cause of the errors and correct the problem.

nn is the unique number and name is the name of the Natural nucleus subsystem. During the triggers initialization process, a specified number of Natural subsystems will be started for the execution of procedures. When a subsystem has aborted it will be restarted. This message informs the user of the successful initialization/restart of each subsystem.

No action is required. The subsystem will wait for work.

nn is the unique number and name is the name of the Natural nucleus subsystem. The specified subsystem incurred an error and terminated abnormally. The Adabas trigger driver will try three times to restart it. A subsequent message will inform the user of the type of abend.

Determine the cause and resolve the problem. The return code code given should provide additional information.

The action to be taken by Adabas Triggers and Stored Procedures after a processing error from which the system cannot recover is changed to reject/ignore.

No action is required.

nn is the unique number and name is the name of the Natural nucleus subsystem. Either a request was made to shut down the specified subsystem or three consecutive abends have occurred and the Adabas trigger driver has decided to deactivate the subsystem.

Determine the cause and resolve the problem. The return code given should provide additional information.

It was not possible to get an exclusive lock of the trigger table.

Retry the command.

nn is the unique number and name is the name of the Natural nucleus subsystem. The shut-down of triggers has completed successfully. This message is shown for each subsystem.

nnis the unique number and name is the name of the Natural nucleus subsystem. During the processing of a trigger, it was detected that the originating command had timed out or was canceled by AOS request. The trigger will not be processed successfully.

Retry the command.

nn is the unique number and name is the name of the Natural nucleus subsystem. The specified subsystem was canceled when a timeout occurred for a procedure that was executing in the subsystem. The subsystem will be restarted. A previous message gives specifics about the cancellation.

Determine the cause and resolve the problem. The reason code given should provide additional information.

The Error Action field in the Adabas triggers and stored procedures profile is set to halt, and either a fatal error occurred or Adabas Online System requested a shut-down of the Adabas triggers subsystem.

Review previous messages to determine whether a problem occurred and, if so, correct the problem.

The Adabas trigger driver determined that a triggered procedure exceeded the specified time limit. The procedure was canceled so that processing can continue with another procedure and queuing can be prevented. FIELD-UID is the last 8 bytes of the user ID in hexadecimal, as specified in the UQE. SECUID is the security ID of the user ID.

Check the procedure. Determine if it was looping, is doing too much work, or if the time-out parameter is too low. Correct the problem for the next time.

The Adabas trigger driver determined that a particular stored procedure exceeded the specified time limit. The procedure has been canceled so that processing may continue with another procedure and queuing may be prevented. UID is the last 8 bytes of the user ID in hexadecimal, as specified in the UQE. SECUID is the security ID of the user ID.

Check the procedure. Determine if it was looping, is doing too much work, or if the time-out parameter is too low. Correct the problem for the next time.

Triggers is shutting down and must queue the subsystems. However, a procedure is still running. The user ID (UID) and security ID (SECUID) are provided to help the database administrator investigate a potential problem.

No action is necessary. However, the database administrator may not want the Adabas trigger driver to wait; therefore, the user's procedure may be stopped.

nn is the unique number and name is the name of the Natural nucleus subsystem. Subsequent to ADAN9N, the Adabas trigger driver decided not to wait for the specified subsystem to complete processing; therefore, the subsystem was canceled.

The second line of this message appears during shutdown of TSP databases. It shows the number of triggers used during that nucleus session (count).

No action is required for this informational message.

Either the nucleus is terminating (ADAEND or HALT) or the triggers and stored procedures facility has requested a halt, probably due to an error, and the Adabas trigger driver has also been requested to shut down.

No action is required. The user is informed that this is in progress.

A display command is about to be processed with (ON) or without (OFF) a formatted dump.

Indicates whether the error handling and message buffering facility is active in the nucleus.

Indicates whether the error handling and message buffering facility's abnormal termination handler is active.

The error handling and message buffering facility has not encountered any of the errors it is looking for.

Indicates the date (yyyy-mm-dd) and time (hh:mm:ss) of the most recent error handled by the error handling and message buffering facility.

Identifies the abnormal termination that has occurred or the response code that has been received and indicates the location (if any) of the most recent error handled by the error handling and message buffering facility. Explanations of z/OS abnormal termination codes can be accessed in the System Codes Manual from IBM.

Indicates the number of times an error or abend code is trapped and actually handled by the error handling and message buffering facility.

Indicates the number of times a response code is actually handled (that is, a PIN routine is invoked) by the error handling and message buffering facility.

Indicates the total number of times the error handling and message buffering facility is invoked to handle a condition (response code or abend code).

Indicates the PIN routine invoked by the error handling and message buffering facility to handle the most recent error encountered.

Indicates the number of condition-handling PIN routines invoked and the number of errors they recovered.

Indicates the number of location-only PIN routines invoked and the number of errors they recovered.

Indicates the number of response-code PIN routines invoked and the number of errors they recovered.

Indicates the total number of PIN routines invoked and the number of errors they recovered.

Indicates whether message buffering in the error handling and message buffering facility is active.

Indicates the number of messages currently in the message buffer and the date (yyyy-mm-dd) and time (hh:mm:ss) of the oldest message.

Provides information about an active (PIN) or inactive (*PIN) routine: the number of times used, the condition it handles (the abnormal termination that occurred or the response code that was returned), and the location(s) for which it is valid. Explanations of z/OS abnormal termination codes can be accessed in the System Codes Manual from IBM.

An invalid autoincrease AUTOINCxxxxTOTAL operator command was specified. The specification for the AUTOINCASSOTOTAL or AUTOINCDATATOTAL operator command 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).

The DISPLAY=EXITS command was issued but no exits are currently in use.

Indicates whether the specified exit is active, active and critical, or inactive.

The nucleus detected that there is one or more CLOG data set that needs to be copied and the LOGWARN timer has expired. One message will occur for each data set that needs to be copied.

Check the status of the CLCOPY jobs affecting the oldest CLOG to be copied to determine why the copy has not worked correctly or in a timely fashion. If necessary, make corrections and resubmit the job. If all CLOG data sets become full, your nucleus may stall waiting for a free CLOG.

All CLOG data sets have now been copied.

No action is required for this informational message.

There are no free command log data sets. The nucleus is unable to write command log data. This also prevents Adabas from executing commands and the environment may appear to be completely stalled.

Check the status of the latest CLCOPY jobs, concentrating on the jobs affecting the oldest CLOG to be copied. If necessary, make corrections and resubmit the jobs.

Command logging has resumed after a stalled situation. An ADANC3 stalled message should have appeared sometime before this message.

No action is required for this informational message. The crisis of stalled command logging has been resolved.

Indicates that the abnormal termination handler of the error handling and message buffering facility is active.

Not enough memory is available to run the error handling and message buffering facility. Adabas runs without the facility.

Increase the region size available to the Adabas nucleus.

Not enough memory is available to run the error handling and message buffering facility. Adabas runs without the facility.

Increase the region size available to the Adabas nucleus.

An error occurred loading the license load module and then opening the license file specified by the DD/link statement. Where ddname is the DD/link name for the license sequential file. The name is concatenated from the string DDL and the product code ccccc.

Provide the license as load module or assign the license file to the ddname in the JCL.

The license being read is larger than expected (8000 bytes).

Verify that you are using the original license file obtained from Software AG.

An empty file or invalid record structure was detected. Where ddname is the DD/link name for the license sequential file. The name is concatenated from the string DDL and the product code ccccc.

Verify that the license file has been copied correctly to the license data set. The file should not be empty and the data should not have been converted to EBCDIC (it should be in ASCII format).

An unexpected error occurred while performing the Adabas license check.. The license function (fx), subfunction (sfx) and return code (err) are given in the message.

Examine the Adabas nucleus JCL and verify that the Adabas license is available as load module ADALIC or is assigned with the link (DD) name DDLIC.

The license processor module could not be loaded.

Verify that the modules from the MLCvrs load library can be loaded by the Adabas nucleus.

The license file is physically correct, but some license property was found that did not match your Adabas nucleus execution environment. Where ccccc is the product code where the license was checked. This is a final message, accompanied by another message specifying details of the failure.

Contact your Software AG sales representative to resolve the discrepancy between your license file and your execution environment.

The license check completed successfully. Where ccccc is the product code where the license was checked.

No action is required for this informational message.

The license module cccccLIC for Adabas or an add-on identified by product code ccccc could not be loaded.

Verify that the installation of the license file occurred correctly. For more information, read about the Adabas database installation steps for your operating environment. If problems persist, contact your Software AG technical support representative for assistance.

The product license check works with the separate component Mainframe License Check (MLC). For a correct interaction with MLC a minimum version vvvv is required.

Update the MLC component and rerun the job.

The NWCONNECT operator command received an unexpected response when attempting to define the DBID target to Entire Net-Work. The response and subcodes given in the message are from Entire Net-Work. Depending on the error, the Entire Net-Work node name may also appear. The most common response codes are 148 (ADARSP148 - Entire Net-Work not available) and 145 (ADARSP145 - target already defined on another Entire Net-Work node).

Resolve the Entire Net-Work problem. If the problem persists, contact your Software AG technical support representative for assistance.

The operands on an SMGT command were invalid.

Correct the operands and reissue the command.

The error handling and message buffering facility finished processing a command.

The error handling facility must be active (SMGT=ON) before the command can be issued. The command issued can be found in the ADANO1 message immediately following the ADANO5 message.

Activate the error handling facility and reissue the command.

The nucleus detected that there is one or more PLOG data set that needs to be copied and the LOGWARN timer has expired. One message will occur for each data set that needs to be copied.

Check the status of the PLCOPY jobs affecting the oldest PLOG to be copied to determine why the copy has not worked correctly or in a timely fashion. If necessary, make corrections and resubmit the job. If all PLOG data sets become full, your nucleus may stall waiting for a free PLOG.

All PLOG data sets have now been copied.

No action is required for this informational message.

There are no free protection log data sets. The nucleus is unable to write protection log data. This also prevents Adabas from executing update commands which could eventually lead to a complete stall of the environment.

Check the status of the PLCOPY jobs, concentrating on the jobs affecting the oldest PLOG to be copied. If necessary, make corrections and resubmit the jobs.

Protection logging has resumed after a stalled situation. An ADANP3 stalled message should have appeared sometime before this message.

No action is required for this informational message. The situation of stalled protection logging has been resolved.

The error handling facility has been invoked for the specified condition. Note that explanations of z/OS abnormal termination codes can be accessed in the System Codes Manual from IBM.

An error occurred in the specified, noncritical exit. The exit is not invoked until the error is corrected.

Consult diagnostic messages; correct the exit; reload the exit using the SGMT,XLOAD command; then reactivate the exit using the SGMT,XACT command.

Displays the PSW when the error was encountered.

Displays the registers when the error was encountered.

An unexpected response / subcode occurred when trying to post commands waiting for advance-locks in a cluster environment.

Ensure that the communication between the cluster nodes works.

The error handling facility is handling an error of the specified type.

The nucleus startup JCL did not define a data set to hold a formatted hexadecimal dump of an area in memory, either an address space or a data space.

To use the error handling and message buffering facility's SMGT,DUMP={ON| OFF } or SMGT,SNAP[=(start,end)] command successfully, the data set ADASNAP must be defined in the Adabas startup JCL.

Stop the Adabas session; add the required statement to the startup JCL, and start a new session.

This space usage message is printed during nucleus startup when the ASSOSPACEWARN or DATASPACEWARN ADARUN parameters are specified with a nonzero threshold percentage and the ASSO or DATA space use is greater than or equal to the threshold specification. Similarly, if autoincrease ADARUN parameters have been specified with nonzero parameters, this message appears when either of the AUTOINCASSOTHRESHOLD or AUTOINCDATATHRESHOLD settings are exceeded. Only the first line of the message (percentage) appears in these cases.

The message also appears in response to a DSPACE operator command. In this case, all four lines appear for both ASSO and DATA for a total of 8 lines.

The second detail line expresses the statistics in uu units, which may be "KB" (2¹⁰ bytes), "MB" (2²⁰ bytes), "GB" (2³⁰ bytes) or "TB" (2⁴⁰ bytes).

When more than one container is configured for a component (ASSO or DATA) the statistics represent the sum of all the component’s containers. If different device types are used for individual containers, the block size and the number of blocks per cylinder may be different for each container.

No action is necessary for this informational message. However, if the percentage is excessively high, determine the reason for the excessive ASSO or DATA space use. If necessary, adjust the ASSO or DATA space. For more information, read Dynamically Increasing Associator and Data Storage Space.

This space usage message is printed when the amount of ASSO or DATA space used in the database increases by the increment set by the ADARUN ASSOSPACEWARN or DATASPACEWARN parameters or by the ASSOSPACEWARN or DATASPACEWARN operator commands.

No action is necessary for this informational message. However, if the percentage is excessively high, determine the reason for the excessive ASSO or DATA space use. If necessary, adjust the ASSO or DATA space. For more information, read Dynamically Increasing Associator and Data Storage Space.

This space usage message is printed when the amount of ASSO or DATA space used in the database increases by the increment set by the ADARUN ASSOSPACEWARN or DATASPACEWARN parameters or by the ASSOSPACEWARN or DATASPACEWARN operator commands. The increase in space usage in the database is being reported by nucleus zzzz in a cluster environment.

No action is necessary for this informational message. However, if the percentage is excessively high, determine the reason for the excessive ASSO or DATA space use. If necessary, adjust the ASSO or DATA space. For more information, read Dynamically Increasing Associator and Data Storage Space.

This space usage message is printed when the amount of ASSO or DATA space used in the database decreases by the increment set by the ADARUN ASSOSPACEWARN or DATASPACEWARN parameters or by the ASSOSPACEWARN or DATASPACEWARN operator commands.

No action is required for this informational message.

This space usage message is printed when the amount of ASSO or DATA space used in the database decreases by the increment set by the ADARUN ASSOSPACEWARN or DATASPACEWARN parameters or by the ASSOSPACEWARN or DATASPACEWARN operator commands. The decrease in space usage in the database is being reported by nucleus zzzz in a cluster environment.

No action is required for this informational message.

This message is printed if the ASSO or DATA autoincrease ADARUN parameters have been specified with nonzero parameters and the AUTOINCASSOTHRESHOLD or AUTOINCDATATHRESHOLD settings have been exceeded.

No action is required for this informational message.

This message is printed if the ASSO or DATA autoincrease ADARUN parameters have been specified with nonzero parameters, the AUTOINCASSOTHRESHOLD or AUTOINCDATATHRESHOLD settings have been exceeded and the nucleus has started the autoincrease process.

No action is required for this informational message.

This message is printed as a result of an autoincrease process after the database extents block (GCB2) has been updated. It indicates the number of blocks (nn) that have been added to the Associator or Data Storage data set.

No action is required for this informational message.

This message indicates that the autoincrease process has completed and the new space was added to the free space table (FST).

No action is required for this informational message.

An error has occurred while attempting an autoincrease process for the ASSO or DATA container. The AUTOINCASSOTHRESHOLD or AUTOINCDATATHRESHOLD setting (as appropriate) has been set to zero to prevent another attempt. The reason for the failure is given in the message (reason). Possible reasons include:

• Autoincrease total already reached

• Container change already in progress

• Container change already in progress in peer nucleus

• Error in calculation of used space

• FST update failed

• GCB lock unavailable

• Get VOLSER table failed

• Getmain VOLSER extent failed

• HALT pending

• Invalid message index idx autoincrease {ASSO|DATA}

• IOR-3D open extended failure

• IOR-3E extend ASSO/DATA failure

• IOR-3E extend did not get any space

• IOR-3E extend failure on peer nucleus

• IOR-5B format track failure

• No room in FST for additional extent

• Online recovery in progress

• Other ONLINCREASE in progress

• Too many ASSO, DATA and DSST extents

• VOLSER table inconsistent

• VOLSER table mismatch

Contact your Software AG technical support representative if you are unable to resolve the failure.

These status messages are produced at intervals during the execution of an autoincrease process. They are issued while the autoincrease process is active or when one of the following operating commands is run: ADAEND, DSTAT, or HALT. They provide you with information about the progress of the autoincrease process.

No action is required for this informational message.

The AUTOINCxxxxTOTAL parameter for the ASSO or DATA container specifies a value smaller than the current size of the container. The parameter is set to zero, which disables autoincrease processing for the container.

To reenable autoincrease processes, reset the AUTOINCASSOTOTAL or AUTOINCDATATOTAL parameter to a nonzero value greater than the current size of the ASSO or DATA container.

An attempt was made to initiate an autoincrease process for the ASSO or DATA container, but the current environment does not allow autoincrease processes. A reason (reason) is given in the message. Possible reasons include:

• ADAEND/HALT pending

• Autoincrease is not currently enabled

• Conflicting utility running

• Error reading FST

• FST allocation failure

• GCB2 overflow

• Global container change lock unavailable

• Highest possible RABN already reached

• Invalid device type (internal error)

• Invalid autoincrease size: too large/small

• Local container change lock unavailable

• No room in FST for additional extent

• Nucleus in read-only mode

• Nucleus in single-user mode

• Online recovery in progress

• ONLINEINCREASE in progress

• Threshold no longer exceeded

• Unable to calculate used percentage

• Unable to create ICQE

Conflicting utilities are those that require exclusive database control, for example the ADAORD function REORGDB.

The global lock is used only in cluster configurations.

Contact your Software AG technical support representative for assistance if you are unable to resolve the conflict.

This message is issued when a terminating cluster nucleus causes a threshold to be exceeded and there is at least one other active nucleus. Because autoincrease processes cannot be initiated during nucleus termination, a check of thresholds will occur on another nucleus.

No action is required for this informational message.

The SYNS-83 checkpoint contains data relating to an autoincrease attempt. The checkpoint could not be created.

Contact your Software AG technical support representative for assistance.

This message is printed as a result of an autoincrease process. It indicates that the formatting process of the increased space has started.

No action is required for this informational message.

This message is printed as a result of an autoincrease process. It indicates that the formatting process of the increased space has finished.

No action is required for this informational message.

An error described in a previous ADANSE or ADANSH message caused the nucleus to disable autoincrease processes for the specified component.

To re-enable autoincrease processes, reset the ASSO or DATA threshold parameter AUTOINCxxxxTHRESHOLD to a nonzero value. Contact your Software AG technical support representative if you are unable to resolve the earlier failure.

This message indicates that the first step of an autoincrease process has successfully completed. It shows the size of the allocated extent for the ASSO or DATA data set.

This size might be smaller than the size requested (see message ADAI79). For example, in z/OS environments, when the size specified in blocks is not a multiple of the blocks-per-track for the device, the size is rounded down to the last multiple.

No action is required for this informational message.

This message indicates that a problem occurred allocating memory for the number of work buffers requested for autorestart processing in the ADARUN ARNWORKBUFFERS parameter. The amount of memory requested (xxx,xxx) and actually amount of memory acquired (yyy,yyy) are provided in the message. Because of this problem, autorestart processing will run with only one work buffer.

No action is required for this informational message. However, you might consider adjusting your ADARUN ARNWORKBUFFERS parameter setting.

Indicates a change of status in the error handling and message buffering facility.

Indicates a change of status in message buffering.

Indicates a change of status in the abnormal termination handling or the error handling and message buffering facility.

Not enough memory was available to add new PINs. Adabas runs without the PIN module.

Increase the size of the region available to the Adabas nucleus.

Unable to load the specified module. The error handling and message buffering facility runs without the module.

Ensure that the module is available to the error handling facility by placing it in the Adabas program library.

The exit-code indicated in the message is not a valid code, or is not in the correct state for the command requested. Adabas rejects the command.

Ensure that the exit-code is correct. If it is, ensure that the exit is in a state that allows the requested command.

The exit-code specified in the message indicates an active exit. Adabas rejects the command.

Ensure that the exit-code is correct. If it is, ensure that the exit is in a state that allows the requested command.

Adabas cannot load the exit without the name of the module. Adabas rejects the command.

Retype the SGMT,XLOAD command and include a member name for the exit.

A command that requires an exit cannot be processed because the exit is not loaded. Adabas rejects the command.

Ensure that the exit-code is correct. If it is, load the exit.

The status (active, not active, loaded, critical, or not critical) of an exit changed as a result of an operator command, and this messages provides the details.

The parameters provided for a SNAP command are invalid. Adabas rejects the command.

Ensure that the addresses provided to the SNAP command are correct.

The specified PIN routine has been disabled.

The PIN routine for the previous command was not found. Adabas rejects the command.

Ensure that the PIN routine is correct and reissue the command.

The specified PIN routine has been enabled.

The specified PIN module has been loaded.

The specified PIN module has been removed from memory.

The PIN module for the previous command is not available. Adabas rejects the command.

Ensure that the PIN module name is correct, and that the PIN module is in the Adabas library; then reissue the command.