Utilities Error Messages

This document lists the error messages and warnings of the Adabas utilities. The messages have the general format:

%<utility name>-<severity>-<message ID>, text

The following severities can occur:

Severity Code Explanation
I Information only. These messages are not documented here.
W Warning: The user should pay attention to the fact reported by this message.
Normally, the requested function is executed without error.
E Error. The requested function is not or not completely executed.
F Fatal error. The utility cannot continue processing.

The messages in this chapter are sorted by message ID and are accompanied by explanations and suggested actions to recover these errors.

Overview of Messages

1NCE | 2MANYPARM | A2ALIC | A2AREX | AARADARSP | AARDUPLICATE | AARERDBFI | AARIDEXIST | AARNOBT | AAROPTION | AARRI | ACACTINVT | ACACTINVV | ACDDAT | ACEXTOVL | ACFADINVI | ACFADINVV | ACFADNFND | ACFADNRD | ACFAUNFND | ACFAUNRD | ACFMTINVI | ACFMTINVT | ACFRBINVI | ACFRBINVV | ACFRBNFND | ACFRBNRD | ACFRBSYN | ACINVERR | ACLEXST | ACLLOAD | ACLOGCL | ACLOGINVI | ACLOGINVV | ACLOGOP | ACLOGPERM | ACLOGW | ACMODINVI | ACNISN | ACNOPERM | ACNPE | ACNSP | ACRABN | ACSEPINVI | ADA_77 | ADAnnn | ADAASH | ADAGSH | ADAMCI | ADAMIV | ADAMNF | ADAMNU | ADAMPI | ADAMPM | ADAMSU | ADAMUQ | ADAREXE | ADAREXF | ADCERR | ADDDE | ADOERR | ADRERR | ADTERR | ADTSIZ | AEXCLWO | AIOERR | ALLCRE | ALLERR | ALLERROVFL | ALLOAD | ALLOCISN | ALLOPT | ALLPH | ALLUQ | ALRACT | ALRLOCK | ALRSET | AMBKEY | ARERR | ARIWR | ARIXER | ARPARDEC | ARSUPP | ASSOTS | ASYERR | BADMAG | BCKBLKW | BCKMACT | BCKNHUP | BCKNOPARAL | BCKPARAL | BCKRSTV | BCKWAIS | BCRSP1 | BEGNLEND | BFNOTS | BINVRR | BKALFA | BKALRAC1 | BKBEMP | BKBLIGN | BKCSCH | BKINTY | BKIREC | BKIREC2 | BKISBCF | BKNDNCH | BKNNDB | BKNOTER | BKNPC | BKNRDB | BKPRERR | BKSYNC | BKWAIST | BKWODB | BLKINT | BLKREQ | BLKTOSMALL | BLSCORR | BLSMAW | BLSMM | BLUNUSED | BMISGX | BOPABO | BOVRLAP | BPMERR | BS2SMALL | BSAD | BSADREQ | BSUBS | BTRSP | BUFEXC | CANTOF | CHARMAX | CHARMIN | CHKREQ | CHPERR | CLOGDIS | CLOGER | CMPREC | CONBLCOR | CONFIG | CONFILUSED | COMMINIERR | CONVER | CPBOVFL | CPFAIL | CPLPE | CPNWRT | CPULIC | CPYERR | CRDBLIC | CREERR | CSAERR | CSZMM | CSZMMF | CTOOBIG | CVDBS | CVINVCV | CVTFDTTL | CVTINI | CVTOPTNO | CVTREFNO | DALERR | DATAOVL | DATEMP | DATFPP | DATIOR | DATNOD | DATUGR | DATWRB | DBABORT | DBERR | DBERRS | DBIDMIS | DBIDMM | DBNOACT | DBSIZEXC | DBSLMM | DBSTRAR | DBSTRXA | DBSTRXAR | DBUUACT | DCUCCB | DCUFCV | DCUICB | DCULIT | DCUMCB | DCUMFN | DCUREC | DEALLSE | DEALLUS | DEERRCNT | DEIU | DELSYS | DEMU | DENC | DENOTDEF | DENOTUQ | DENU | DESNO | DEVFULL | DEVNOTAVL | DFW | DMPONL | DMPPRO | DPFACAD | DROPFAIL | DSETEMP | DSEXTOVL | DSRECOFF | DSSIZEAD | DSSTALL | DSTNLS | DUPISN | EALCFGERR | EALCONNABORT | EALCONNLOST | EALELGERR | EALEVENT | EALFILTER | EALINIERR | EALINVEVTAREA | EALINVEVTFIELD | EALINVEVTNAME | EALIOERR | EALMAXRETRY | EALSOCKFAIL | EFCERR | ELEM | ELNP | ENAOBS | ERASERR | ERR1 | ERR2 | ERR3 | ERR4 | ERR5 | ERR6 | ERR8 | ERR9 | ERR10 | ERR11 | ERR13 | ERR14 | ERR20 | ERR30 | ERR31 | ERRASYNC | ERRFIL | ERRIUP | ERRNOM | ERROR | ERRRES | ERRSYNC | ERRUNX | ETYPEREMNOTFOUND | EXTBAL | EXTBNF | EXTBNO | EXTBNP | EXTENT | EXTERR | EXTLOCK | FCAL | FCBDSLCK | FCBERR | FCBERRFX | FCBEXE | FCBFDTL | FCBFGT | FCBFLE | FCBIFF | FCBILI | FCBILU | FCBIMA | FCBIRC | FCBIRO | FCBNAC | FCBRAN | FCBRBF | FCTNFND | FDFILITL | FDT... | FDTCHN | FDTDIFF | FDTL | FDTMM | FDTNOP | FDUSYN | FECACR | FILEMP | FILN | FINU | FIXOCC | FKDRPCNST | FLDERR | FLDFIL | FLK | FMTERR | FNIU | FNLOAD | FNNOTFND | FNPGTP | FNRNOT | FONLYRAW | FREADTYPE | FROMNOT | FSSSEC | FSTMAX | FTOOBIG | FUN | FUNONL | GCBAFL | GCBFCB | GCBFDT | GCBINUSE | GCBMAX | GCBOVFL | GCBSYS | GCBWERR | GRNDES | GRPINX | GRPLN | GRPVM | HEURB | HEURC | HFNFD | HFNOP | HILIMRE | HILIMTO | HYERR | HYNA | HYUEXERR | IBPERR | ICKW | IDOP | IFSD | ILLLOG | ILLSUB | INBLN | INCL | INEDM | INFM | INFN | INICF | INISEC | INITERR | INLE | INLIT | INPERR | INTERR | INUSE | INVBP | INVBS | INVCHARS | INVCHN | INVENV | INVEXT | INVFDT | INVFILE | INVKEY | INVPE | INVPLN | INVPV | INVSEC | INX... | IOCFTB | IODERR | IOERROR | IOSUBERR | IOT | IOTRES | IRABN | IRABNVAL | IRANGE | IREC | IRECL | IRECSZ | IREMUQ | ISAINI | ISDESC | ISNINUSE | ISNNLS | ISNUSED | KCONAL | KEYPOS | KEYREQ | LABLINV | LABTB | LBPLIC | LBPINCW | LBPRED | LCCINV | LCEINT | LCLEXP | LCMISM | LCMFIL | LCSAGE | LDERR | LELE | LESSHW | LOBDESC | LOBFNEMP | LOBFNP | LOBFNTCR | LOCNAME | LOCNUC | LOSERR | LOSTNI | LOSTUI | LTOOL | LVOR | LWPLIC | LWPTSM | M1MU | MANPARM | MAXDOVL | MAXISN | MDBID | MDEFU | MDVTREC | MEMMAP | MFLD | MISDATA | MISINDX | MISSPAR | MNPF | MNTAB | MOUNT | MPGDTAE | MPGDTPE | MSGGET | MSGNF | MULTDEF | MUPG | NABOBS | NCLIC | NCLSERR | NCMUT | NCPE | NCRQ | NEMAFP | NETREPLY | NETWORKB | NEWCERR | NEWFDTNE | NEWPAT | NFSTSPACE | NIEXTOVL | NO2BYTEISN | NOABB | NOBLKGE | NOBLKLT | NOBLKPOS | NOCONTALL | NOCPDB | NOCPF | NODB | NODBBCK | NODCUFDT | NODESC | NODEVSP | NODS | NODSS | NOEND | NOETD | NOFD | NOFIAV | NOFIELDS | NOFSEL | NOFUNCP | NOGCB | NOINDALL | NOISNRU | NOLOG | NOMUL | NOOFFLF | NOONLF | NOPARMOD | NORDONL | NORES | NOSHM | NOSPACE | NOSPST | NOTALB | NOTALLAD | NOTALM | NOTAUTH | NOTAVL | NOTDESC | NOTEXST | NOTLOAD | NOTLOCK | NOTNUM | NOTPOSS | NOTPRES | NOTR | NOTRSPA | NOTSET | NOTSUP | NOTUQ | NOTZ | NOUQDESCS | NOWOEX | NSPALL | NSPSEC | NTLIC | NUCLOST | NUCNOA2A | NUCVTE | NULIC | NUMADEXH | OBCKTIR | OFFCAP | ONLALL | ONLDBA | OP1P | OPNERR | OPNFAIL | OPNP | OPRDONL | ORDEXPERR | ORDINTERN | OVLSYSF | PAGFILE | PARMVAL | PAROBS | PARTLOAD | PCREATE | PEMU | PEMUNOT | PENDRES | PFAL | PFGR | PFND | PGL1 | PGOVL | PHNA | PKDRPCNST | PLACT | PLEMPTY | PLEXTOVFL | PLNOTO | PLOGLIC | PLOGSW | PLOGWRER | PLOVFL | PLPLINV | PLRFILE | PREDCONT | PREPEMAR | PWNF | PWUSE | RAWCORRUP | RCNOFL | RDBFDT | RDERR | RDEVPN | RDONLRQ | RDONP | READDBINIERR | READERR | READINIERR | RECACT | RECCMD | RECCORRUP | RECEEC | RECENN | RECENU | RECEPE | RECERR | RECFL2 | RECFLN | RECISB | RECMIS | RECMLN | RECNOTF | RECNUP | RECPEI | RECTOOBIG | RECUPD | REEXEC | REGDAT | REGENPL | REMSHM | REMUQ | RENUMERR | REPUI | REQDBID | REQFIL | REQLEV | RESDEN | REUCUT | REULOST | REXABORT | REXCANCEL | RIDEF | RIIDFL | RIINOR | RIMISF | RIRFSH | RKEYERR | RLLE | RNOTAV | RNOTFREE | RONLYDB | RPCPERR | RPLFID | RPOFFF | RQINVF | RSERR | RSFN | RTOOBIG | RUIERR | RULERR | RUNILOOP | RURERR | RUUILOOP | SACERR | SAMDIR | SAMEFIL | SAMOERR | SAMPLATF | SBVNOTEXP | SCACRE | SCADBC | SECNOE | SECINUSE | SECINVNAME | SEINVPW | SEMGET | SEMLOST | SEMNCR | SEMUCNT | SEPINV | SEPWOVF | SEQNA | SEV1FL | SEVFNL | SEVRBOVF | SEVSB | SEVSBF | SEVVB | SEVVBL | SFNOTPO | SFSLMM | SHMNOA | SHORTOPT | SIGNAL | SLOR | SMMSEC | SMPIERR | SMPNULL | SPAALL | SPADBA | SRTERR | SRTFIL | SRTWRK | SSAP | STAOVF | STARTERR | STDLNG | STNOTPO | STOP | STPnnn | STP054 | STRMDI | SVAMIS | SYNOMU | SYNTAX | SYOPUSER | SYSESSIONID | SYSFLOCK | SYSNOMATCH | SYTIME | TADEREQ | TEMPTS | TIMOT | TMOVBREQ | TMPFMT | TONOT | TOOSMALL | TPCO | TTLV | TRTABE | TZERR | UBFERR | UCBGERR | UCBNREM | UEXABO | UEXERR | UEXMUE | UEXSTA | UIEXTOVL | ULDCORE | ULDCORR | ULDLOB | ULDSEQ | UNEFILD | UNIQUEFILE | UNPRIV | UNPRRD | UNPRUN | UNXEOF | UNXIOERR | UNXNRSP | UNXRC | UQDE | UTIENA | VALEX | VALLOW | VALMAX | VALUP | VFADAM | VFERRCNT | VFYBLK | VFYERR | WMFEXP | WORK2TSM | WONOP | WORKSET | WPSIZE | WRONGIPT | WRFAIL | WSERR | XAERRRES | XALIC | XARMERR | ZERISN

1NCE 1-N element must be preceded by valid C element
Explanation

The 1-N element requires a valid C element. The C element defines the number of values to be processed by the 1-N element. Note that the C element must precede the 1-N element in the same line.

Action

Define a C element before the 1-N element in the same line.


2MANYPARM Too many parameters entered
Explanation

Too many parameters entered for the specified function.

Action

Correct the input line.


A2ALIC Adabas - Adabas replication not allowed by licensing
Explanation

Adabas - Adabas replication is only possible if it is permitted by your Adabas license file.

Action

Upgrade your license.


A2AREX Adabas - Adabas replication requires a replication exit
Explanation

Adabas-to-Adabas replication requires a replication exit (provided by the Adabas Event Replicator).

Action

If you intend to use A2A replication, install the Adabas Event Replicator before starting the nucleus again; in particular, the replication exit is required.

If you have already used A2A replication but you no longer want to use it, perform ADADBM REMOVE_REPLICATION.


AARADARSP Adabas response code during insert or update of a replication
Explanation

During the update of the replication meta data file an Adabas error occurred.

Action

Check the nucleus log for the specific response code.


AARDUPLICATE Replication target file already used
Explanation

A certain database ID and file number combination was specified twice as replication target. Obviously this does not work. But a file can be replicated to two targets.

Action

Choose a different target.


AARERDBFI File number or Database ID out of range
Explanation

Either the file number of the target file or the target database is out of range (beyond 255) or the source file number does not exist. The target database and target file do not have to exist.

Action

Choose valid target values. Make sure the source file exists.


AARIDEXIST Replication ID already exists
Explanation

An existing replication ID was used for ADAOPR ADD_REPLICATION.

Action

Choose a different replication ID. If omitted, the next free ID is chosen.


AARNOBT NOBT files cannot be replicated
Explanation

Since the replication is triggered at the end of a transaction NOBT files cannot be replicated.


AAROPTION Option not allowed for current replication status
Explanation

Option is the keyword specified for ADAOPR CHANGE_REPLICATION. Only certain options are allowed for a status to avoid inconsistences.

The valid keywords are documented.

Action

Consult the table in ADAOPR CHANGE_REPLICATION.


AARRI If a referential integrity constraint is defined, the same option must be specified also for the related file
Explanation

Cascading actions for a referential constraint could cause modifications which would not be replicated if the replication of the primary file is not active.

Action

Specify all connected files with ADAOPR CHANGE_REPLICATION.


ACACTINVT Topic AUTHZ or the item ACTION missing in ‘string’
Explanation

Either the topic AUTHZ or the item ACTION could not be located in the configuration file adaauth.ini.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACACTINVV Invalid value for item ACTION in ‘string’
Explanation

The value of item ACTION in the configuration file adaauth.ini is not valid.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACDDAT Records differ between address converter 'number' and data storage 'number'
Explanation

Address converter is inconsistent with DS.

Action

Unload/export the file in physical sequence and load/import it again.


ACEXTOVL Address Converter's extent overflowed
Explanation

The file's Address Converter is too fragmented.

Action

Unload/export the file, allocate larger extents, and load/import the file again.


ACFADINVI Item AUDIT_FILE invalid or missing in ‘string’
Explanation

The item AUDIT_FILE is invalid or missing in file adaauth.ini.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFADINVV Value of AUDIT_FILE too long in ‘string’
Explanation

The value of the item AUDIT_FILE in the configuration file adaauth.ini is invalid.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFADNFND File AUDIT_FILE not found ‘string’
Explanation

The file assigned via the item AUDIT_FILE in the configuration file adaauth.ini could not be located.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFADNRD File AUDIT_FILE not readable ‘string’
Explanation

An error has occurred while accessing the file assigned via the item AUDIT_FILE. The file was not accessible; a possible cause for this could be file access permissions.

Action

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE.


ACFAUNFND File adaauth.ini not found ‘string’
Explanation

The configuration file adaauth.ini could not be found in the given location.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFAUNRD File adaauth.ini not readable ‘string’
Explanation

An error has occurred while accessing the configuration file adaauth.ini. The file was not accessible; a possible cause for this could be file access permissions.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFMTINVI Item FORMAT invalid or missing in ‘string’
Explanation

The value of item FORMAT is either invalid or missing in the configuration file, which is assigned via the item AUDIT_FILE.

Action

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.


ACFMTINVT Topic AUDIT or item FORMAT invalid or missing in ‘string’
Explanation

Either the topic AUDIT or the item FORMAT could not be located in the configuration file, which is assigned via the item AUDIT_FILE.

Action

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.


ACFRBINVI Item RBAC_FILE invalid or missing in ‘string’
Explanation

The value of the item RBAC_FILE in the configuration file adaauth.ini is either invalid or missing.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFRBINVV Value of RBAC_FILE too long in ‘string’
Explanation

The value of the item RBAC_FILE in the configuration file adaauth.ini is not a valid file path.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFRBNFND File RBAC_FILE not found ‘string’
Explanation

The file assigned via the item RBAC_FILE in the configuration file adaauth.ini could not be located.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACFRBNRD File RBAC_FILE not readable ‘string’
Explanation

An error has occurred while accessing the file assigned via the item RBAC_FILE. The file was not accessible; a possible cause for this could be file access permissions.

Action

Contact your system administrator.

Check the content of and correct the file assigned via the item RBAC_FILE in file adaaudit.ini.


ACFRBSYN Syntax error in file RBAC_FILE ‘string’
Explanation

A syntax error has been encountered during the processing the security definitions in the file, which is assigned via the item RBAC_FILE .

Action

Contact your system administrator.

Check and correct the security definitions in the file assigned via the item RBAC_FILE in file adaaudit.ini.


ACINVERR An unexpected error has occurred: rc=’number’ in ‘string’
Explanation

An internal error has occurred.

Action

Contact your nearest support center.


ACLEXST 'name' is already loaded in file 'number'
Explanation

The RBAC system file already exists in the database with the given file number. The database was not modified.

Action

None.


ACLLOAD 'name' loaded in file 'number'
Explanation

The RBAC system file has been successfully loaded with the given file number.

Action

None.


ACLOGCL File LOG_FILE cannot be closed
Explanation

The file assigned via the item LOG_FILE could not be closed.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Action

Check the content of and correct the file LOG_FILE.


ACLOGINVI Item LOG_FILE invalid or missing in ‘string’
Explanation

The value of item LOG_FILE is either invalid or missing in the configuration file, which is assigned via the item AUDIT_FILE.

Action

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.


ACLOGINVV Value of LOG_FILE too long in ‘string’
Explanation

The file assigned via the item LOG_FILE could not be located.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Action

Contact your system administrator.

Check the content of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.


ACLOGOP File LOG_FILE cannot be opened
Explanation

The file assigned via the item LOG_FILE could not be opened. The file was not accessible; a possible cause for this could be file access permissions.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Action

Contact your system administrator.

Check the content of and correct the file LOG_FILE.


ACLOGPERM The permissions of the LOG_FILE directory are insufficient.
Explanation

The permissions of the directory in which the LOG_FILE is located are insufficient.

All users which are able to execute Adabas utilities require read and write permissions to the Audit Log file, which is located in this directory.

Action

Contact your system administrator.

Check the content of and correct the file LOG_FILE.


ACLOGW File LOG_FILE cannot be written
Explanation

The file assigned via the item LOG_FILE could not be written. Possible causes for this could be:

  • Insufficient amount of storage/disk space;

  • Insufficient permissions to access the file.

This configuration option is set in the file assigned via the item AUDIT_FILE in file adaaudit.ini.

Action

Contact your system administrator.

Check the content of and correct the file LOG_FILE.


ACMODINVI Item MODE invalid or missing in ‘string’
Explanation

The value of the item MODE in the configuration file adaauth.ini is either invalid or missing.

Action

Contact your system administrator.

Check the content of and correct the configuration file adaauth.ini.


ACNISN Address-converter 'number', ISN 'number' not in data RABN 'number'
Explanation

Address converter is inconsistent with DS.

Action

Unload/export the file in physical sequence and load/import it again.


ACNOPERM Security violation. Permission denied.
Explanation

The user is not permitted to execute the requested operation on the specified object.

This can occur for one or more of the following reasons:

  • The user is not defined;

  • The user does not have the required access privileges.

Action

Contact your system administrator.

Check the content of and correct the security definitions in the file assigned via the item RBAC_FILE in file adaaudit.ini.


ACNPE AC conversion not permitted, highest DS RABN 'num', permitted 'num'
Explanation

The conversion to 3-byte address converter could not be done because there are already block numbers which cannot be stored in 3 bytes.

Action

Investigate if the DATA container(s) with the higher RABNs can be removed.


ACNSP No space for new address converter, need 'number' blocks ('number'KB)
Explanation

There is no more ASSO space for building the new Address Converter. The message shows the total amount of space needed by the AC_CONVERT function.

Action

Calculate free ASSO space in database and see how much missing. Then add a new ASSO container with sufficient space with ADADBM ADD_CONTAINER or check if you can use ADADBM DEALLOCATE. Alternatively, you can increase the ASSO container by using ADADBM with the EXTEND_CONTAINER parameter.


ACRABN Unable to get address converter RABN 'number'
Explanation

Physical problem with reading of address converter or FCB corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


ACSEPINVI Item SEPARATOR invalid or missing in ‘string’
Explanation

Item SEPARATOR invalid or missing in ‘string’

Action

Contact your system administrator.

Check the contents of and correct the file assigned via the item AUDIT_FILE in file adaaudit.ini.


ADA_77 * ASSO/DATA storage exhausted ('string')
Explanation

See nucleus response code 77.

Action

See nucleus response code 77.


ADAnnn 'text'
Action

Refer to nucleus response codes, response nnn.


ADAASH No shared-memory region available
Explanation

The shared memory required by Adabas cannot be created or attached due to resource problems.

Action

Check the UNIX kernel parameters that relate to the resources and increase them if necessary. Check the documentation of your operating system for

  • shmget error ENOSPC or

  • shmat error EMFILE


ADAGSH Cannot attach to shared-memory region
Explanation

The shared memory region cannot be attached. The reason for this may be missing user rights, for example a terminal server user does not have the "create global objects" user right.

Action

Assign the appropriate user rights to the user.


ADAMCI ADAM key file not supported with ciphering
Explanation

The ADAM key option and the CIPHER option of ADAFDU are incompatible.

Action

Select either ADAM or CIPHER but not both.


ADAMIV Invalid usage of the ADAM parameter, check semantics
Explanation

The specified ADAM parameter does not fit to the ADAM key.

Action

Check the format of the ADAM field name and see the documentation on how to use the ADAM parameter.


ADAMNF ADAM key 'name' not found in FDT
Explanation

The ADAM key specified by the parameter ADAM_KEY was not present.

Action

Check the FDT specification.


ADAMNU NU/NC option not permitted with ADAM
Explanation

An ADAM key must not have one of these options.

Action

Check the FDT specification.


ADAMPI ADAM parameter mismatch with ISN option
Explanation

The given ADAM parameter cannot be used the ADAM ISN option.

Action

Correct ADAM_KEY or ADAM_PARAMETER.


ADAMPM ADAM key must not be a MU field or within periodic group
Explanation

An ADAM key is not permitted for multiple-value fields or for fields within periodic groups.

Action

Check the FDT specification.


ADAMSU ADAM key must not be a sub/super/phonetic/hyper descriptor
Explanation

An ADAM key must not be a special descriptor.

Action

Check the ADAM_KEY parameter of ADAFDU.


ADAMUQ Unique descriptor option for ADAM key required
Explanation

An ADAM key does not have the unique option in the FDT.

Action

Check the FDT specification.


ADAREXE Replication exit error: 'error'
Explanation

An error occurred in the replication exit provided, for example, by the Adabas Event Replicator. ‘error’ describes the error that occurred.

Action

Refer to the documentation of the product that provided the replication exit.


ADAREXF Replication exit fatal: 'error'
Explanation

A fatal error occurred in the replication exit provided, for example, by the Adabas Event Replicator. ‘error’ describes the error that occurred.

Action

Refer to the documentation of the product that provided the replication exit.


ADCERR can't configure asynchronous IO driver 'string'
Explanation

A system call used to configure the asynchronous I/O driver failed.

Action

Check that the driver is correctly installed (use errno number as help).


ADDDE Adding descriptor 'name' not possible
Explanation

A field without the NC or NU option can only be added as a descriptor (with the DE option) if the file is empty.

Action

Add the field without the DE option and invert the field with ADAINV afterwards.


ADOERR can't open asynchronous IO driver 'string'
Explanation

The open system call on the asynchronous I/O driver failed.

Action

Check that the driver is correctly installed (use errno number as help).


ADRERR error during asynchronous IO driver request
Explanation

An error occurred while performing an asynchronous I/O. A following ERRNOM message gives you more details about the error. Note that the reason for an errno(5): I/O error may not only be a real I/O error, but also one of the following:

  • Not all required operating system patches are applied (see Installation).

  • The system parameters, in particular AIO_LISTIO_MAX are not set correctly (see Installation).

Instead of increasing AIO_LISTIO_MAX, you can also set the ADANUC parameter BFIO_PARALLEL_LIMIT (see Utilities).

Action

Verify that the required operating system patches are applied, and that the system parameters are correct. If these points are OK, check your hardware.


ADTERR error during retrieval of completed asynchronous IOs
Explanation

An error occurred when reading from the asynchronous I/O driver.

Action

Check that the driver is correctly installed. If it is correctly installed. call your nearest support center (tell them the errno number as a help).


ADTSIZ request size 'number', returned size 'number'
Explanation

An error occurred when writing the asynchronous I/O driver.

Action

Check that the driver is correctly installed. If it is correctly installed. call your nearest support center (tell them both numbers as a help).


AEXCLWO already exclusive opened for write
Explanation

A TEMP or SORT container file is already being used by another user.

Action

Create another TEMP or SORT, or wait until the other user terminates.


AIOERR Unexpected AIO error: 'rc', counts: 'comp', 'free', 'active', 'retry', 'err_cnt'
Explanation

Asynchronous IO error.

Action

Send the output to your nearest support center.


ALLCRE Space difference between allocation and creation
Explanation

The amount of space preallocated for a container file is different from the size specified with ADAFRM or ADADBM.

Action

Correct the preallocation, or correct the SIZE parameter for ADAFRM or ADADBM.


ALLERR Error during space allocation in disk section 'string'
Explanation

A problem occurred during space allocation in a disk section (e.g. space bottleneck).

Action

Check second message for a detailed analysis of the problem.


ALLERROVFL Overflow on raw section 'string'
Explanation

An overflow on a raw disk section occurred. Please note, that his error may occur, even though there is still enough free space on the disk section. The reason for this is that the space reserved for the directory describing the contents of the disk section is limited, and the error occurs if there are too many entries in the disk section.

Action

Move data from the disk section to the file system.


ALLOAD file 'number' already loaded
Explanation

The specified file is already present in the database.

Action

Check the file number.


ALLOCISN Cannot allocate user defined ISN 'number'
Explanation

There is not enough free ASSO space to increase the Address Converter of the file to store the user-defined ISN.

Action

Increase the size of the ASSO container.


ALLOPT asterisk required
Explanation

Only a wildcard is permitted.

Action

Use an asterisk `*'.


ALLPH field already phonetized
Explanation

The same parent field is already used within another phonetic descriptor.

Action

Check the file number or the parent-field name.


ALLUQ descriptor already defined unique
Explanation

The descriptor to be set as unique is already defined as unique.

Action

Check the file number or the field name.


ALRACT ADABAS already active
Explanation

A nucleus is already active for this database.

Action

Check if there is really an Adabas nucleus for this database. (UNIX only: if not, use showipc -k <dbid> to remove the shared memory resources and restart the nucleus.)


ALRLOCK file already locked
Explanation

The required file is already locked.

Action

None.


ALRSET Option already set
Explanation

The specified option is already set in the nucleus.

Action

None.


AMBKEY ambiguous keyword
Explanation

The keyword's abbreviation is not unique.

Action

Make the keyword unique.


ARERR AUTORESTART on database 'number' completed with errors
Explanation

During auto restart, some errors have occurred. Check preceding messages for detailed error information. The nucleus can operate normally on all files on which no errors have occurred.

Action

Repair the errors. See also the messages ARIXER and ERRFIL.


ARIWR Invalid WORK P1 Block, BLSIZE not equal SUM_LEN of all records
Explanation

The consistency check failed during an autorestart.

Action

Make a copy of the WORK container file and send the copy to your nearest support center.


ARIXER Auto restart has disabled index on file 'number'
Explanation

During auto restart, an error in the index of this file occurred. The index for this file is destroyed and must be rebuilt using ADAINV REINVERT.

Action

Rebuild the index using ADAINV REINVERT.


ARPARDEC For auto restart, parameter 'name' must not be decreased - minimum required: 'value'
Explanation

If an auto restart is required after a nucleus crash, the nucleus may require the same resources as the previous session, in particular the number of users (NU) and the size of the buffer pool (LBP) should not be decreased. In order to avoid that the auto restart fails, the nucleus checks that these parameters are not decreased before starting the auto restart.

Action

Increase the parameter values accordingly for the next nucleus start.


ARSUPP Database 'number', AUTORESTART suppressed
Explanation

The last session was not terminated properly, but the WORK used in the current session does not contain the information needed for auto restart. The database may be in an inconsistent state.

Action

Restore/regenerate the database using ADABCK and ADAREC.


ASSOTS given ASSO-Size too small
Explanation

The size specified for the Associator is too small to contain the FCB and FDT blocks.

Action

Use a larger ASSO size.


ASYERR Asynchronous IO error for id 'number'
Explanation

An asynchronous IO failed. The utility is aborted.

Action

Check for problems with the device. Is the device online and writeable? If a logical volume spans several physical devices, are they all accessible? Try to access the affected devices using operating system commands. Have a look at system log files for appropriate error messages.


BADMAG bad magic number
Explanation

Access to a sequential file failed because of a structure mismatch. The file is not a sequential Adabas file, or it is a sequential file of an unexpected type, or it was generated on a wrong platform (most sequential Adabas files generated on a high-order-byte first platform cannot be processed on a low-order-byte first platform and vice versa).

Action

Check the assignment of the associated environment variable.


BCKBLKW backup in progress which blocks nucleus, wait ...
Explanation

An ADABCK DUMP function is active and blocking the nucleus. The nucleus must wait until ADABCK has completed.

Action

Wait for the DUMP function to complete.


BCKMACT nucleus cannot start, multiple adabcks active
Explanation

There is only one ADABCK DUMP function permitted if the nucleus is online or going to be online, but there is more than 1 DUMP function currently active.

Action

Wait until all ADABCK DUMP functions have completed (or only one backup still active).


BCKNHUP adabck not responding, hangup 'date'
Explanation

The nucleus has disabled a ADABCK DUMP function because it did not respond within 10 minutes. The backup got back control later and found this situation, so it aborted.

Action

Check your adabck process.


BCKNOPARAL Backup was created without option PARALLEL=MULTI_PROCESS
Explanation

A restore operation from a backup that was created without the option PARALLEL=MULTI_PROCESS cannot be performed using the PARALELL=MULTI_PROCESS option.

Action

Perform the restore operation without the PARALELL=MULTI_PROCESS option.


BCKPARAL Backup created with option PARALLEL=MULTI_PROCESS cannot be processed.
Explanation

A backup that was created with the option PARALLEL=MULTI_PROCESS cannot be restored to a platform with a different endian mode.

Action

Create a backup without the option PARALELL=MULTI_PROCESS if data is to be restored on a platform with a different endian mode.


BCKRSTV Restore from backup file created on a different platform with a different Adabas version is not supported
Explanation

ADABCK can restore a database from a backup file that was created on a different platform: all data that are dependent on the endian mode are converted into the target format (swapped). However, it is not possible to convert the data structures that were used by earlier releases at the same time.

Action

Use a more recent backup.


BCKWAIS wait for adabck synchronisation ... 'date'
Explanation

An ADABCK DUMP function is active while the nucleus is starting up. The processes must synchronize with each other.

Action

If the nucleus cannot proceed then check the ADABCK process (via the ps command). If the ADABCK process does not respond within 10 minutes, the nucleus will disable the backup run and will start up.


BCRSP1 Database 'number' aborted, Response 'number' during Backout command, file 'number', orig rsp 'number'
Explanation

An Adabas command was returned with an error (the response code is displayed as 'orig rsp'). This resulted in the command being backed out in order to reverse any changes. However, the backout did not succeed due to the error displayed as 'response'. The nucleus cannot continue, because its data are inconsistent.

Action

Restart the database. This will result in consistent data.


BEGNLEND beginning date/time not earlier than ending date/time
Explanation

The specified ending date/time is earlier than the specified beginning date/time or the current date/time.

Action

Correct the beginning or ending value.


BFNOTS Blocking factor is not supported, check your tape device
Explanation

The specified tape device cannot be written by Adabas because the blocking factor is not supported.

Action

Change the blocking factor on the tape device. It must either be variable or a multiple of 1024.


BINVRR invalid RABN range detected, file= 'number', type='string', from='number', to='number'
Explanation

An invalid range of RABNs was detected in the FCB for the specified file.

Action

The file in question cannot be used in this situation. To repair this, Unload/export the file, delete it, redefine it with ADAFDU, the load/import it again.


BKALFA allocation failed with 'string'-RABNs 'number' - 'number'
Explanation

While restoring files, the requested range of RABNs of 'string' type is not available.

Action

Use ADAREP's LAYOUT function to check the required blocks.


BKALRAC1 Online backup already active
Explanation

Another ADABCK DUMP function is active. Only one online backup is possible at one time.

Action

Identify the running ADABCK process. Check the UCB with ADAOPR DIS=UCB and check with the ps command (ps -ef). Note that an ADABCK process can be active although there is no entry in the UCB.


BKBEMP input file BCK00'number' is empty
Explanation

The specified backup file does not contain any data.

Action

Check the setting of the environment variable and the associated file.


BKBLIGN RABN 'number' ignored, run ADAVFY's INDEX function for file 'number'
Explanation

During ADABCK a corrupted index block is found which will not be dumped to the backup file.

Action

To verify that the block is not a relevant block, ADAVFY's INDEX function should be performed. If ADAVFY succeeds then the backup file is ok, the block in question will be reformatted if using the RESTORE function by ADABCK. If ADAVFY signals errors the index is corrupted. The given backup file cannot be used; the file must be repaired first with the REINVERT function of ADAINV.


BKCSCH invalid container size change 'container-file', expected rabn 'number'
Explanation

The container sizes are insufficient or have different block sizes when restoring a complete database. The specified container file must have at least as many blocks as given in the message.

Action

Check and compare the SUMMARY functions of ADAREP (database) and ADABCK (backup file).


BKINTY invalid block type 'string' for rabn 'number'
Explanation

LOGGING=IO is switched on and an I/O from an unexpected container is going to be logged, so command logging has been deactivated.

Action

Because this is an unexpected error, contact your nearest support center; you can re-enable command logging with ADAOPR's LOGGING function.


BKIREC invalid record detected, block (bck-block), rabn (rabn), session (session)
Explanation

The backup copy file has a structure error with printed information. This backup copy file cannot be used as input for a restore.

Action

Run ADABCK's DUMP function again.


BKIREC2 error occurred in I/O block 'number', last successful rabn 'number' ('type')
Explanation

This message provides additional information to the BKIREC message.


BKISBCF invalid sequence of backup copy files
Explanation

When restoring a database with multiple backup tapes, a tape was inserted in the incorrect sequence.

Action

Insert the tapes in the correct sequence.


BKNDNCH Dbid could not be changed
Explanation

During ADABCK's RESTORE function, the NEW_DBID request cannot be satisfied and is ignored because of mismatches in the disk section.

Action

Check the disk section of the current database and use ADADBM's NEW_DBID function.


BKNNDB function only permitted if restore database
Explanation

The requested function can only be executed if a complete database is being restored.

Action

Check the selected parameters.


BKNOTER terminator of backup copy not found
Explanation

The backup copy is not complete, the previous dump has not finished successfully.

Action

This backup copy cannot be used, try another one.


BKNPC Not permitted to continue, nucleus abnormally terminated
Explanation

During an online backup the nucleus went down abnormally. This will be detected by ADABCK at the end of this session.

Action

Perform autorestart for the Adabas nucleus and restart the backup.


BKNRDB restore database not permitted while nucleus running
Explanation

It is not possible to restore a database while the Adabas nucleus is active.

Action

Shut down the nucleus and start the restore again.


BKPRERR backup process terminated with an unexpected error <number>
Explanation

A parallel backup failed due to an error of an associated subprocess. The error number is the exit status of this process.

Action

Look at the subsequent error message that is displayed together with this one.


BKSYNC synchronisation with nucleus lost ('reason')
Explanation

The synchronisation between ADANUC and ADABCK during an online backup was lost due to the 'reason'.

Action

Restart the online backup with ADABCK. If it fails again, contact your nearest support centre.


BKWAIST Wait for startup of nucleus ... 'date'
Explanation

The nucleus is within its startup phase (e.g. autorestart). ADABCK will synchronize after the nucleus has come up and therefore it must wait.


BKWODB restore database NOT possible, files exist on a READONLY device
Explanation

One or more container files are located on a READONLY / WORM device which cannot be written to.


BLKINT block device path name not allowed
Explanation

A block device path name was used where a raw device path name was required.

Action

Use raw device path name.


BLKREQ block number required
Explanation

A checkpoint name has been supplied but no corresponding block number.

Action

Supply the block number where the checkpoint name is to be found.


BLKTOSMALL block size on output file too small
Explanation

The block size on the output file is too small.

Action

Use an output device with a larger block size.


BLSCORR 'path' appears to be damaged at offset 'number'
Explanation

The block at the given offset 'number' of the sequential Adabas file identified by 'path' has an unexpected block size.

Action

The file is corrupted. You cannot work with it. If you cannot determine the reason for the data set corruption, contact your nearest support center.


BLSMAW blocksize mismatch detected between ASSO and WORK
Explanation

The WORK block size must be larger than the largest ASSO block size, and the first ASSO extent must have a block size of at least 2KB.

Action

Change the block size of ASSO or WORK.


BLSMM blocksize mismatch detected on dataset (extent)
Explanation

Within an ADABCK restore, the block sizes between the database and the backup file are incompatible.

Action

Check the block sizes of the database and the backup file.


BLUNUSED 'number' blocks unused at WORM device end
Explanation

When a container is being created on a WORM disk, this warning message gives the amount of unused space (in units of blocks of the specified block size).

Action

This is an informational message and just informs you about wasted disk space. You could repeat the function to make use of that space also.


BMISGX 'string' RABN 'number' not found in GCB extent(s)
Explanation

The specified RABN was allocated to a file but not contained in the GCB.

Action

Run ADAVFY to check the FCB.


BOPABO aborted by operator
Explanation

The session has been explicitly aborted (ADAOPR ABORT).

Action

None.


BOVRLAP database is inconsistent, overlapping FCB extents detected
Explanation

The database contains overlapping FCB extents.

Action

Run ADAVFY to check the FCB.


BPMERR ADABPM internal error 'number'/'number'
Explanation

An internal error has occurred.

Action

Contact your nearest support center.


BS2SMALL Record length is 'number', max available size of block: 'number'
Explanation

IMPORT encountered a record, which is smaller than the block size of the user-defined device.

Action

Choose a device (with the DSRABN parameter) with a greater block size and rerun IMPORT.


BSAD wrong block size specified for ADAM-file 'number'
Explanation

A smaller block size than the original block size was specified for an ADAM file. The specification of the block size could also be given indirectly by specifying DSRABN.

Action

Correct the input line and rerun ADAORD.


BSADREQ minimum block size of 'number' bytes required for ADAM-file 'number'
Explanation

A smaller block size than the original block size was specified for an ADAM file.

Action

Correct the input line and rerun ADAORD.


BSUBS backup copy contains subset of files present in database
Explanation

This is a warning message to indicate that when you use the RESTORE=* function of ADABCK, some files will disappear because there are more files contained in the current database than on the dump file.


BTRSP Database 'number' aborted, Response 'number' during BT, in file
Explanation

An invalid response has been detected during a BT.

Action

Restart the database. This will result in consistent data.


BUFEXC Length of Record Buffer exceeds 64k. Cannot be used with acb interface.
Explanation

The ACB interface only supports records buffers less than 64 kilobytes.

Action

Use the ACBX interface for the Adabas call, or decrease the record buffer size for the Adabas call.


CANTOF can't open file
Explanation

The CSA dump file cannot be opened.

Action

Check that the file name is correct and check the file's access privilege.


CHARMAX only 'number' character(s) allowed
Explanation

The given string is too long.

Action

Enter a string that does not exceed the length given by the error message.


CHARMIN at least 'number' character(s) required
Explanation

The given string is too short.

Action

Enter a string that is not shorter than the length given by the error message.


CHKREQ checkpoint name required
Explanation

A block number has been supplied but no corresponding checkpoint name.

Action

Supply the checkpoint name to which the block number belongs.


CHPERR Invalid checkpoint data
Explanation

The checkpoint file contains invalid data.

Action

Contact your nearest support center.


CLOGDIS database 'number', command logging disabled
Explanation

An error has occurred while opening or writing the command log file. The command log feature is now disabled, the nucleus continues normally.

Action

Check the environment of NUCCLG. You can reactivate the command logging later on with ADAOPR FEOF=CLOG.


CLOGER Open error on CLOG file
Explanation

The new command log file could not be opened with an ADAOPR FEOF or LOGGING function.

Action

Look in the nucleus log file to find the detailed error message.


CMPREC Number of compressed records: 'number'
Explanation

This message is issued in each run of ADACMP. If records are compressed, it is an informational message. It is issued as a warning message if zero records are compressed. This may be because the input file does not contain any records or because the structure of the records does not agree with the FDT.

Action

Check the ADACMP input file CMPIN and the FDT.


CONBLCOR PLOG/WORK block 'block number' corrupted - database verification recommended
Explanation

The specified PLOG/WORK block is corrupted.

Action

Verify the consistency of the database.


CONFIG Software configuration error
Explanation

If you apply a hotfix to a wrong Adabas version, unexpected errors can occur. In order to avoid such errors, Adabas checks whether a hotfix that is applied to an Adabas version really has this Adabas version as prerequisite. If this is not the case, this error message is returned.

Action

Remove the hotfix from the wrong Adabas version, and apply it to the correct Adabas version.


CONFILUSED the container file to be removed is in use
Explanation

An Adabas file has allocated RABNs that are located in the last container file (REMOVE_CONTAINER function) or in that part of the last container file that is to be deallocated (REDUCE_CONTAINER function).

Action

All RABNs to be deallocated must be returned to the Free Space Table.


COMMINIERR Failed to commit configuration changes to the DBnnn.INI file
Explanation

Cannot write changes to the INI file.

Action

Check subsequent messages for a detailed error reason.


CONVER format conversion error
Explanation

A field's standard format cannot be converted to the required format.

Action

None.


CPBOVFL Checkpoint block (CPB) overflow
Explanation

An overflow has occurred in the checkpoint block. The utility action has been carried out but will not be reflected in the checkpoints of the database.

Action

Start the nucleus to transfer the entries in the checkpoint block to the checkpoint file. The ADANUC option AUTORESTART_ONLY can be used.


CPFAIL Checkpoint write failed with response 'number', session canceled
Explanation

An internal checkpoint I/O (e.g. during a utility action) failed with a response code. The nucleus will shut down in the same way as ADAOPR CANCEL.

Action

Analyze the response code given in the message and do the required action. Then restart the nucleus and the failed checkpoint will be recovered.


CPLPE descriptor contained in or derived from periodic group
Explanation

A descriptor that is contained in or derived from a periodic group cannot be used to control the unload sequence.

Action

Use a different descriptor or unload in physical or ISN sequence.


CPNWRT Checkpoint not written due to response 'number'
Explanation

The utility checkpoint could not be written because of response code 'number'.

Action

Refer to the response code description and perform its action. It is just a warning, the utility will continue.


CPULIC Number of CPUs restricted by licensing, CPUs online 'number', CPUs licensed 'number'
Explanation

Adabas cannot be run on a machine with more CPUs than the license allows.

Action

Run Adabas on a machine with less CPUs or upgrade your license.


CPYERR Copy (move) error during 'string' call on file 'string'
Explanation

A system call that was performed during the copy (move) process aborted.

Action

See the subsequent 'errno' message.


CRDBLIC Database size (DATA) 'number' exceeds size 'number' allowed by license
Explanation

The database size is restricted by license, so that a bigger database cannot be used or created.

Action

Check your license for the currently-allowed database size, and either create a smaller database or upgared your license.


CREERR dataset 'string', file 'string' could not be created
Explanation

The required data set could not be created. The reason is given in a subsequent error message.

Action

See the subsequent error message.


CSAERR CSA dump file 'string' could not be 'operation', errno ('number'): 'error text'
Explanation

A CSA dump file could not be created or written due to an operating system error. See 'errno' and 'error text' for a detailed problem analysis.


CSZMM container size mismatch between GCB and raw section
Explanation

The container file size registered in the database (GCB) and the size found in the raw section are not identical.

Action

Check the settings of the environment variables that point to the container files. Use ADADEV's LAYOUT function and ADAREP's SUMMARY function and compare the values given for the container file size.


CSZMMF container size mismatch at 'container name', expected size 'number'
Explanation

The container file in a file system is smaller than the size registered in the database (GCB).

Action

Check the settings of the environment variables that point to the container files. Compare the file size with the size given by ADAREP's SUMMARY function.


CTOOBIG Size of CONTAINER file too large
Explanation

The maximum size of Adabas container file has been exceeded.

Action

Reduce the file size.


CVDBS database 'number' at unexpected structure level ('number')
Explanation

The current database is not a Version 6.1, Version 6.2 or Version 6.3 database.

Action

None: ADACVT cannot be used to convert unsupported database versions.


CVINVCV only conversion to version 'vers' permitted
Explanation

Conversion to the destination version is not permitted. Please refer to the CONVERT parameter for information about the conversions that are supported.

Action

Use one of the valid keywords.


CVTFDTTL Conversion not permitted. FDT too long in file 'fnr'.
Explanation

The size of the FDT is larger than the maximum FDT size allowed in the target version of the conversion. Specifically, the FDT may be too large because more than 926 fields have been defined, which was the maximum up to Adabas Version 6.1.

Action

Remove all files where the FDT is too large.


CVTINI Structure level decreased. AUTOSTART option disabled
Explanation

AUTOSTART is disabled if ADACVT converts to a previous Adabas version.

Action

Use the destination Adabas version to register the database for AUTOSTART.


CVTOPTNO Conversion not permitted. Not supported field definition in file 'fnr'.
Explanation

ADACVT conversion to an older version is not allowed because of new features used.

Action

Remove all files that use new Adabas features.


CVTREFNO Conversion not permitted. Referential integrity in file 'fnr'.
Explanation

ADACVT conversion to an older version is not allowed because referential integrity is not supported in that version.

Action

Drop all referential integrity constraints.


DALERR double allocation error
Explanation

A double allocation has been detected between two or more files or a file and the free space table.

Action

Run ADAVFY without any options to determine which parts of which files are affected. Contact your nearest support center with the output of ADAVFY.


DATAOVL DATA could not be created due to Address Converter overflow
Explanation

The maximum number of blocks allowed for DATA is 16777215.

Action

Correct the value for the parameter DATASIZE.


DATEMP Data RABN 'number' empty.
Explanation

No data is loaded into DS RABN.

Action

Restore and regenerate file and contact your nearest support center.


DATFPP Data RABN's first free byte pointer is invalid, RABN 'number'
Explanation

DS RABN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data will be lost in the RABN), or

  • Restore and regenerate file and contact your nearest support center.


DATIOR ISN 'number' not between LOWISN and FFISN , rp='hex-number' in data RABN 'number'
Explanation

Inconsistency between DS and FCB.

Action

Unload/export the file in physical sequence and load/import it again.


DATNOD File 'number' has no data
Explanation

No data is loaded into DS of file.

Action

Restore and regenerate file and contact your nearest support center.


DATUGR Unable to get data RABN 'number'
Explanation

If RABN 'number' does not exist in DS, the FCB is corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


DATWRB ISN 'number' points to wrong data RABN 'number', expected 'number'
Explanation

Inconsistency between DS and FCB.

Action

Unload/export the file in physical sequence and load/import it again.


DBABORT Database 'number' aborted
Explanation

The nucleus aborted, a dump is automatically taken. Additional information concerning the reason is contained in the *.LOG file.

Action

Check the reason for the abort, contact your nearest support center if necessary.


DBERR DB not available or assignment of ASSO1 is not correct!
Explanation

The specified database cannot be accessed for the reasons given in the message.

Action

Correct the input line or assignment.


DBERRS File 'number', 'string' ,errors = 'number'
Explanation

Summary message of ADAVFY, checked file contains errors.

Action

Look at the displayed error messages and act accordingly.


DBIDMIS DBID missing
Explanation

A function was executed without the mandatory DBID parameter being set.

Action

Set the DBID parameter.


DBIDMM DBID mismatch: present 'number'
Explanation

A mismatch occurred between the DBID parameter and the database ID of the assigned ASSO data set.

Action

Enter the correct database ID or exit the utility and assign correct data sets.


DBNOACT Database no longer active for this session
Explanation

The nucleus session is now not active.

Action

Reenter the DBID parameter in order to access the new session.


DBNOACT Database no longer active for this session
Explanation

The nucleus session is now not active.

Action

Reenter the DBID parameter in order to access the new session.


DBSIZEXC Enlarging the database has failed, because the licensed database size would have been exceeded
Explanation

One of the following situations has occurred:

  • You aren't using a license file - there are some restrictions if you use Adabas without a license file, in particular the size of the database is limited.

  • Your license file has expired, in which case Adabas behaves as if you were using it without a license file.

  • You are using a license file with a limitation in the size of the database.

Action

Use an appropriate license file. You can activate the license file via the DBA workbench.


DBSLMM Structure level mismatch on database
Explanation

Either the database containers or an Adabas sequential file, for example a backup file created by ADABCK, belong to a different Adabas version. Please note that Adabas sequential files created with lower Adabas versions can usually be processed with a higher Adabas version, but not vice versa.

Action

Use an appropriate Adabas version to process the database containers or Adabas sequential files. If you have to load data stored in an Adabas sequential file with a newer Adabas version into a lower version database, you can first load the data to a newer version database, and then convert the database to the lower version with ADACVT, and then create an Adabas sequential file that belongs to the lower version. However, this is only possible if no features of the higher version were used which were not available in the lower version.


DBSTRAR READONLY option not allowed if auto restart is pending
Explanation

The database which is to be started with OPTIONS=READONLY had been used for updates in the previous session. The previous session had not been terminated properly.

Action

Restart the nucleus with OPTIONS=AUTORESTART_ONLY. After the nucleus has terminated, start it with OPTIONS=READONLY.


DBSTRXA Start DB with XA option because previous session has used XA
Explanation

The database which is to be started with OPTIONS=READONLY had been used with OPTIONS=XA in the previous session. There are still open global transactions.

Action

Start the nucleus with OPTIONS=XA, terminate all remaining global transactions, shut down the nucleus. Then start it with OPTIONS=READONLY.


DBSTRXAR READONLY option not allowed if global transactions are pending
Explanation

The database which is to be started with OPTIONS=READONLY had been used with OPTIONS=XA in the previous session. There are still pending global transactions.

Action

Start the nucleus with OPTIONS=XA, terminate all remaining global transactions, shut down the nucleus. Then start it with OPTIONS=READONLY.


DBUUACT Database or update utility active
Explanation

The user tried to copy/move an Adabas container which is at the moment used by a nucleus or an update utility.


DCUCCB PE/MU count converted
Explanation

A PE/MU count byte was converted (new length or format). This means that the FDT written to the ADADCU output file DCUFDT does not represent the standard PE/MU decompression output.

Action

Edit the DCUFDT/DCUOUT file.


DCUFCV Format/Edit-mask conversion done
Explanation

The format/edit mask conversion has been performed for a field.

Action

None.


DCUICB Count and actual number of occurrences may differ
Explanation

The count byte was written to the output file, but not all of the elements of the PE/MU group were included.

Action

Edit the DCUFDT/DCUOUT file.


DCULIT Literal inserted, unknown field name
Explanation

The specified format buffer contained a literal for which a field name has to be set.

Action

Edit the DCUFDT file.


DCUMCB Missing PE/MU count in format buffer
Explanation

No count byte was written to the DCUOUT file. The field is represented as a PE/MU group in DCUFDT, which means that the record structure does not match the FDT.

Action

Edit the DCUFDT/DCUOUT file.


DCUMFN Field name already in use
Explanation

A field name occurred more than once in the format buffer. Field names must be unique, which means that a new field name has to be set.

Action

Edit the DCUFDT file.


DCUREC number of decompressed records : 'number'
Explanation

This message is issued in each run of ADADCU. If records are decompressed, it is an informational message. It is issued as a warning message if zero records are decompressed. This may be because there are no records in the input file DCUDTA or because the records have the wrong structure.

Action

Check the input file DCUDTA.


DEALLSE deallocation only permitted from start/end of an extent
Explanation

RABNs can only be deallocated from the start or end of an extent. Otherwise the database would be fragmented.

Action

Specify correct values for the RABN and SIZE parameters.


DEALLUS no deallocation possible, extent is in use
Explanation

The extent to be deallocated is totally in use, no more unused space is present.


DEERRCNT Errors found for 'numbers' descriptors
Explanation

The VERIFY function of ADAINV has found inconsistencies between index and data storage.

Action

Use the REINVERT function of ADAVFY to repair the index.


DEIU descriptor name already in use
Explanation

The same descriptor name has already been specified.

Action

Correct the input line.


DELSYS system file cannot be deleted
Explanation

An attempt was made to delete one or more Adabas system files.

Action

If you want to delete replication system files, use the function ADADBM REMOVE_REPLICATION. Deletion of other system files is not allowed as they are required by the Adabas nucleus.


DEMU descriptor based on multiple value field
Explanation

A descriptor that is based on a multiple-value field may not be used to control the sequence in which a file's data records are exported.

Action

Check the field name.


DENC descriptor based on field defined with SQL null-value representation
Explanation

A descriptor that is based on a field defined with SQL null-value representation (NC) may not be used to control the sequence in which a file's data records are exported because this will result in data records being lost.

Action

Check the field name.


DENOTDEF descriptor 'string' not defined for file 'number'
Explanation

The specified descriptor is defined on the sequential input file for ADAMUP's ADD function, but is not present in the database file to be updated.

Action

Check the input file assignment(s) and the database file to be updated. ADAMUP's DE_MATCH=SUBSET can be used to continue.


DENOTUQ descriptor is not defined unique
Explanation

Descriptor defined without unique status.

Action

Check the file number or field name.


DENU descriptor based on field defined with null value suppression
Explanation

A descriptor that is based on a field defined with null value suppression (NU) may not be used to control the sequence in which a file's data records are exported because this will result in data records being lost.

Action

Check the field name.


DESNO file(s) in use, 'text' function currently not available
Explanation

If using ADAFIN, the given function cannot be used because the file is active (i.e. opened by another user).

Action

Check the file usage by displaying the user queue with ADAOPR.


DEVFULL Database 'number', PLOG device full
Explanation

The file system on which the current PLOG file is located is full. The nucleus is abnormally terminated.

Action

Either make space available in the file system, or assign the PLOG to another file system that has enough free space. Then restart the nucleus.


DEVNOTAVL device not available
Explanation

A non-existent device was specified.

Action

Correct the input line and rerun ADAORD.


DFW DCUFDT output file must be edited for further use
Explanation

The FDT file generated by ADADCU must be modified to be used as input file for an Adabas utility.

Action

Check the FDT file and perform the necessary changes.


DMPONL dump online block detected
Explanation

When processing an Adabas backup copy, the NOONLINE switch was used to allow unloading in one pass. However, this is only possible if there are no online data storage blocks for the file to be unloaded.

Action

Rerun ADAULD without setting the NOONLINE switch.


DMPPRO dump start address 'hex-number' in protected area
Explanation

An invalid CSA dump address was specified.

Action

Correct the area parameter value.


DPFACAD parameter DATAPFAC for ADAM-file 'number' not allowed
Explanation

The DATA padding factor must not be changed for ADAM files.

Action

Rerun ADAORD without changing the DATA padding factor.


DROPFAIL Referential constraint 'refname' could not be dropped
Explanation

The referential constraint ‘refname’ does not exist.

Action

Specify the correct name of the referential constraint.


DSETEMP dataset 'string' empty
Explanation

The data set assigned contains no data.

Action

Assign the correct data set.


DSEXTOVL Data Storage's extent overflowed
Explanation

The file's Data Storage is too fragmented.

Action

Export and reimport the file; the KEEP_LAYOUT option must not be specified. Alternatively, unload the file and then delete it. Redefine the file using larger extents and then mass-add the unloaded file.


DSRECOFF dataset 'string', record 'number', offset 'number'
Explanation

An error has been detected in data set `string', record `number', at offset `number'. The type of error is specified by a subsequent message.

Action

Provide the correct input.


DSSIZEAD wrong DSSIZE specified for ADAM-file 'number'
Explanation

The DATA block size must not be decreased for ADAM files.

Action

Correct the DSSIZE parameter and rerun ADAORD.


DSSTALL allocation error DSST
Explanation

The ASSO space required to store the DSST blocks is not available, or the maximum number of DSST extents (15) has already been allocated.

Action

If the error occurs during ADAFRM or when executing ADADBM's ADD_CONTAINER function with the NOCONTIGUOUS_DSST switch set, check whether the maximum number of DSST extents has been exceeded. If this is the case, reduce the number of DATA extents with different block sizes (ADAFRM), or make sure that the block size matches the block size of the previous DATA extent (ADADBM). If the error occurs when executing ADADBM's ADD_CONTAINER function with the CONTIGUOUS_DSST switch set, use a larger ASSO size, reduce the DATA extent size or free some space adjacent to the DSST allocation so the allocation can be made contiguously.


DSTNLS DST not allowed if NEWLINE_SEPARATOR keyword specified
Explanation

The DST parameter is not compatible with the RECORDS_STRUCTURE = NEWLINE_SEPARATOR parameter.

Action

Instead of using the DST parameter, use the FIELDS parameter and specify the daylight saving time indicator(s) explicitly.


DUPISN duplicate ISN 'number' detected in DATA - please run ADAVFY
Explanation

Multiple occurrences of ISN 'number' were detected in the DATA.

Action

Run the verify utility ADAVFY and contact your nearest support center.


EALCFGERR Loading Configuration of Adabas Analytics failed
Explanation

Adabas Analytics detected an unrecoverable error and initiated the termination of the Adabas nucleus process.

Action

Restart the ealconfig configuration tool.


EALCONNABORT Thread id lost the connection to the Analytics Server. Configured Action: ABORT
Explanation

Worker thread number id lost his connection to the Adabas Analytics Server and it was configured (ON_ERROR) to abort the nucleus.

Action

Start the Adabas Analytics Server and restart the database or change the configuration of this database.


EALCONNLOST Thread id lost the connection to the Analytics Server
Explanation

Worker thread number id lost his connection to the Adabas Analytics Server and it was configured (ON_ERROR) to ignore this error.

Action

Restart the Adabas Analytics Server.


EALELGERR Creation of Adabas Analytics NUCELG file failed
Explanation

The NUCELG file could be created during startup.

Action

Check whether the file can be created, or if the NUCELG file location is valid.


EALEVENT Problem sending Adabas Analytics event, returned code error
Explanation

Adabas Analytics detected an unexpected situation and generated a warning message in the nucleus log file. An error code is returned.

Action

Contact your nearest support center.


EALFILTER Problem calling Adabas Analytics filter, returned code error
Explanation

Adabas Analytics detected an unexpected situation with the filtering of events and generated a warning message in the nucleus log file. An error code is returned.

Action

Contact your nearest support center.


EALINIERR Initialization of the Adabas Analytics failed, returned code error
Explanation

Adabas Analytics detected an unrecoverable error during initialization and initiated the termination of the Adabas nucleus process. An error code is returned.

Action

Contact your nearest support center.


EALINVEVTAREA Invalid event type area found in line ‘number’
Explanation

The event type area for the event type defined in the event types file at line ‘number’ is not valid.

Action

Check the spelling of the event type definition.


EALINVEVTFIELD Invalid event type fieldlist found in line ‘number’
Explanation

One of the event type fields for the event type defined in the event types file at line ‘number’ is not valid.

Action

Check the spelling of the event type definition.


EALINVEVTNAME Invalid event type name found in line ‘number’
Explanation

The event type field name for the event type defined in the event types file at line ‘number’ is not valid.

Action

Check the spelling of the event type definition.


EALIOERR Adabas Analytics file operation failed
Explanation

An event could not be stored in the NUCELG file. A file write operation error occurred.

Action

Check the permissions and whether the file can be written.


EALMAXRETRY Max retry count = number reached, disable Adabas Analytics
Explanation

The Adabas Analytics Server cannot be reached and the configured number of retries (parameter MAX_RETRIES) to connect again has been reached.

Action

Start the Adabas Analytics Server and restart Adabas.


EALSOCKFAIL Thread id failed to create socket to Analytics Server
Explanation

During Adabas startup, the worker thread id could not create a socket connection to the Analytics Server. Depending on the configured ‘ON_ERROR’ action the nucleus terminates or tries to reconnect.

Action

Start the Analytics Server.


EFCERR Empty field count of zero, RABN 'number', rp='hex-number'
Explanation

Internal record structure corrupted in DS RABN.

Action

Do one of the following:

  1. Unload/export the file in physical sequence, decompress, compress and load/import it again (this will lose some data), or

  2. Restore and regenerate file and contact your nearest support center.


ELEM elementary field required
Explanation

A required elementary field has not been supplied.

Action

Correct the input line.


ELNP element not permitted
Explanation

This element type is not permitted in this context.

Action

Correct the input line.


ENAOBS keyword ENABLED for parameter LOGGING has become obsolete
Explanation

The keywords allowed for the LOGGING parameter have changed. The parameter is set to "OFF" by Adabas. This yields the behaviour expected by the user when specifying ENABLED.

Action

Change your input scripts to avoid this warning.


ERASERR deletion error
Explanation

An error occurred while deleting files during the reorder phase.

Action

Contact your nearest support center.


ERR1 Descriptor value too large
Explanation

You tried to define a descriptor value larger than the maximum supported descriptor value size, although the descriptor is defined without the TR option.

Action

Either redefine the descriptor with the TR option or change the descriptor vaalue.


ERR2 invalid content for specified format
Explanation

The input file contains invalid data for the required format.

Action

Correct the input file or check the FDT.


ERR3 input record too short
Explanation

The input record is too short for the defined FDT.

Action

Correct the FDT or the input file.


ERR4 PE-count invalid
Explanation

For ADACMP: a user-supplied PE count (which was specified in the input record) is invalid.
For ADADCU: a PE count is too big.

Action

For ADACMP: correct the input file.
For ADADCU: increase the setting of the ADADCU parameter MUPE_C_L.


ERR5 MU-count invalid
Explanation

For ADACMP: a user-supplied MU count (which was specified in the input record) is invalid.
For ADADCU: an MU count is too big.

Action

For ADACMP: correct the input file.
For ADADCU: increase the setting of the ADADCU parameter MUPE_C_L.


ERR6 invalid ISN
Explanation

A user-supplied ISN is invalid.

Action

Correct the input file.


ERR8 internal buffer overflow
Explanation

An unexpected overflow of an internal buffer occurred.

Action

Contact your nearest support center.


ERR9 record larger than RABN size
Explanation

A compressed record is larger than the DATA block size for the specified file.

Action

Allocate a DATA extent with a larger block size.


ERR10 conversion/truncation error - source length 'number', destination
Explanation

A field has been truncated and this record has been omitted from the DCUOUT file.

Action

If a format buffer is being used, provide a length parameter for the field. If the standard FDT is being used, change the standard length, using ADADBM, and unload the file.


ERR11 Resulting record too large
Explanation

The decompressed record created by ADADCU is larger than the ADADCU parameter MAX_DECOMPRESSED_SIZE. The reason for the large record size may be:

  • Multiple fields or periodic groups with large MU or PE counts.

  • LOB values

Action

Increase the value of MAX_DECOMPRESSED_SIZE.


ERR13 compressed record's structure in error
Explanation

A record in the DATA file has an erroneous structure.

Action

Run the RECORD option of ADAVFY and send the output together with the unloaded file and an export copy of the file to your nearest support center.


ERR14 empty NC field detected and S-element missing in FB
Explanation

An NC-option field being decompressed by ADADCU was null, which is not permitted without the S-element of that field. This can happen if the NULL_VALUE option of ADAFDU is not used.

Action

Use the FIELD option of ADADCU and specify all NC-option fields together with their S-elements (for example: AAS,AA,BBS,BB, ...) or use the NULL_VALUE option of ADADCU.


ERR20 unique conflict with ISN 'number'
Explanation

Descriptor value found for more than one record.

Action

Check the conflicting ISNs.


ERR30 ISN outside file's boundaries
Explanation

An ISN provided with the input data exceeds the limit (MAXISN) in effect for the file.

Action

Use a different ISN or extend the file's Address Converter.


ERR31 ISN not in use
Explanation

The ISN to be deleted was not in use in the file's Address Converter.

Action

Check the ISNs supplied.


ERRASYNC Asynchronuos 'action' operation on dataset 'dsname', RABN 'rabn' returned error 'err'
Explanation

An error occurred during an asynchronous I/O operation. action is the type of I/O operation; either 'read' or 'write'. dsname and rabn identify the container and RABN where the error occurred. err contains the error number and the textual description of the error (as returned by the operating system).

Action

Depending on the error type, check your I/O devices including the network (in case of remote access), the file system, the contents and/or permissions of the datasets.


ERRFIL error response 'number'
Explanation

During auto restart, an error occurred in the file indicated in the subsequent message. The file's contents are destroyed.

Action

Rebuild the file using ADABCK RESTORE=file and ADAREC REGENERATE=file.


ERRIUP Error response 'number' during index update
Explanation

While updating the index, an error resulted in a nucleus response code.

Action

Ensure that the correct BACKUP was restored; that the PLOGs were regenerated in the correct order; that the correct file was reloaded when reloading a file; that the nucleus was started with OPTIONS=UTILITIES_ONLY and that the correct utilities have been rerun.


ERRNOM errno ('errno-number'): 'text'
Explanation

A system call aborted.

Action

See the subsequent 'errno' text and contact your nearest support center if necessary.


ERROR Field = 'string', ISN = 'number', Offset = 'number'
Explanation

This message specifies field, ISN, and offset where the error occurred. A subsequent error description is displayed in a second line.


ERRRES error response 'number' from record 'number' in block 'number' in
Explanation

While processing the protection log, an executed command resulted in a nucleus response code.

Action

Examine the block at the record number associated with the error response, e.g. a file may not have been restored, with ADABCK, with the correct dump. This results in the file being in a state different to that when the original command was executed.


ERRSYNC System error ('errno-number'): 'text' occured during semaphore operation
Explanation

An error occured during semaphore operations. The reason is usually that IPC resources were not removed following the crash of another nucleus or utility process.

Action

Delete IPC resources with showipc -k and try again.


ERRUNX Unexpected error 'number'
Explanation

Error in the Adabas code - an unexpected internal error number occurred.

Action

Report the error to your nearest support center, so that the Adabas development team can fix the error.


ETYPEREMNOTFOUND Event type to remove ‘name’ not found in the event types file
Explanation

Cannot remove event type because it was not found.

Action

Correct the name of the event type to be removed.


EXTBAL external backup already prepared
Explanation

The external backup feature is already active, and the nucleus is in synchronization mode.

Action

Use the EXT_BACKUP=CONTINUE function if you want to continue processing.


EXTBNF function not permitted during external backup
Explanation

The selected function conflicts with the initiated external backup mode, which can lead to the execution of some functions being denied.

Action

Wait until the external backup mode has terminated.


EXTBNO external backup not prepared
Explanation

The external backup feature has not been started.

Action

Use the EXT_BACKUP=PREPARE function first.


EXTBNP external backup not permitted
Explanation

The external backup cannot be initiated because it conflicts with an Adabas utility that has exclusively locked some resources.

Action

Ensure that no Adabas utility that performs updates is active when you want to initiate an external backup.


EXTENT file 'number' ('name') has a 'number'th 'type'-extent
Explanation

This is a warning message that the given file is near the end of the maximum number of FCB extents permitted. Program execution continues normally.

Action

This file is a candidate for reorganizing later on (e.g. with ADAORD). In this case, allocate enough space for 'type' to avoid extending.


EXTERR invalid RABN extent
Explanation

An invalid RABN extend has been found for a file.

Action

Search for lost RABNs with the LOST option of ADAVFY and recover them using the ADADBM utility.


EXTLOCK Change not allowed, extent still locked
Explanation

It is not possible to change a sequential file which has the status "during creation" or a TEMP or SORT container which is locked.

Action

None.


FCAL 1st. character of field name must be alphabetic
Explanation

The first character of field name is not alphabetic.

Action

Correct the field name.


FCBDSLCK file 'number's' data storage incomplete
Explanation

A utility has terminated while updating the Address Converter or the Data Storage, leaving the file in an inconsistent state.

Action

Use ADAULD to unload the file in physical sequence, then reload it using ADAMUP. It is, however, not generally possible to determine which records have already been added/deleted. Therefore, if a backup copy is available, the file should be restored and then regenerated if necessary.


FCBERR Shutdown and retry to repair the FCB errors for file 'fnr'
Explanation

ADAVFY was executed while the nucleus was active. Some of the inconsistencies detected for file 'fnr' can be repaired.

Action

Shutdown nucleus and rerun ADAVFY.


FCBERRFX FCB errors for file 'fnr' have been fixed
Explanation

All errors detected by ADAVFY could be repaired.

Action

None.


FCBEXE File <number> has invalid <type> extent
Explanation

ADAVFY has detected that the file has invalid extent entries.

Action

Either restore the file from a backup, or, if the invalid extent is not a DS, you can unload the file in physical sequence and load it again as a new file.


FCBFDTL File 'number' has invalid FDT length in file control block
Explanation

The file control block of the file is partially corrupted.

Action

Contact your nearest support center.


FCBFGT unable to get file control block for file 'number'
Explanation

The file control block (FCB) for the specified file cannot be accessed.

Action

Contact your nearest support center.


FCBFLE File 'number' has invalid file number in file control block
Explanation

FCB of file is partially corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


FCBIFF File 'number' has invalid FFISN
Explanation

FCB of file is partially corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


FCBILI File 'number' has invalid last used UI/NI offset
Explanation

FCB of file is partially corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


FCBILU File 'number' has invalid lu_ds rabn/offset
Explanation

FCB of file is partially corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


FCBIMA File 'number' has invalid MAXISN
Explanation

FCB of file is partially corrupted.

Action

Unload/export the file in physical sequence and load/import it again.


FCBIRC Invalid DS reusage RABN count in file 'number'
Explanation

A RABN count in the FCB that is used for DS reusage, is invalid.

Action

With adadbm remove and re-add the space reusage flag for this file: adadbm db=xx reuse=nods, file=yy adadbm db=xx reuse=ds, file=yy


FCBIRO File 'number' has invalid rotating isn/count
Explanation

A count in the FCB that is used for ISN reusage, is invalid.

Action

Use adadbm to remove and re-add the ISN reusage flag for this file: adadbm db=xx reuse=noisn, file=yy adadbm db=xx reuse=isn, file=yy


FCBNAC file 'number's' index not accessible
Explanation

A utility has terminated abnormally while rebuilding the index, leaving the index in an inconsistent state. When using ADAREC, the index has been marked as not accessible due to an index response during regenerate.

Action

Use ADAINV to reinvert all descriptors or use ADAULD to unload the file in physical sequence and reload it using ADAMUP.


FCBRAN File 'number' has index level out of range in file control block
Explanation

FCB of file is partially corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


FCBRBF File 'number' has invalid highest RABN in file control block
Explanation

FCB of file is partially corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


FCTNFND function 'name' not found
Explanation

While loading a user exit the requested function was not found in the accessed shared library.

Action

Check your environment variable pointing to the shared library and check the entry points within the shared library.


FDFILITL FDT file line too long
Explanation

The FDT file contains a line that is more than 132 characters long.

Action

Correct the FDT file.


FDT... (error text ....)
Explanation

(This explanation applies to all error messages beginning with the letters "FDT", except for those listed below). The FDT of the file to be verified is corrupted.

Action

Restore and regenerate file and contact your nearest support center.


FDTCHN Field 'change' not allowed in field: 'field', option: 'option'
Explanation

Field change not allowed.

Action

Use only allowed field change options.


FDTDIFF number of fields present in both FDT differs
Explanation

A structural mismatch has been detected between the FDT contained on the sequential input file and the associated FDT in the database file to be updated.

Action

Check the assignments. The FDT keyword can be used to display both FDTs.


FDTL FDT overflow, too many entries defined
Explanation

There are too many entries defined in the FDT.

Action

Decrease the number of entries in the FDT, or use a larger block size for ASSO1.


FDTMM FDT mismatch at database field 'string'
Explanation

A mismatch at field `string' has been detected between the FDT contained on the sequential input file and the associated FDT in the database.

Action

Check the format, default length and options of the conflicting field. The FDT keyword can be used to display both FDTs.


FDTNOP FDT mismatch and option NEW_FDT not set
Explanation

ADAMUP can add data to an empty file with a different FDT, but only if NEW_FDT has been specified.

Action

Run ADAMUP with the option NEW_FDT.


FDUSYN Syntax error in FDT
Explanation

There is a syntax error in the FDUFDT file.

Action

Correct the FDUFDT file.


FECACR file extent 'source' cannot be created (reason 'reason', error 'err')
Explanation

A new extent for an Adabas sequential file, e.g. PLOG, could not be created. The most probable reason is that there is not sufficient space available.

Action

If there is sufficient space available and it is not clear why the error occurred, contact your nearest support centre. Please note that the reason displayed in the error message can often only be understood with sufficent knowledge of Adabas internals.


FILEMP High index RABN of file 'number', 'string' empty
Explanation

Index of file is not accessible.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


FILN FI only allowed if standard-length is given
Explanation

The FI option is only allowed if a non-zero standard length is given.

Action

Correct the input line.


FINU FI and NU or NB are mutually exclusive
Explanation

The FI and NU or NB options are mutually exclusive.

Action

Correct the input line.


FIXOCC specification of occurrences not allowed at this position
Explanation

A fixed occurrence count was specified for an MU field within a periodic group, but the periodic group does not have a fixed occurrence count.

Action

Correct the FDT by either removing the occurrence count from the MU field or setting an occurrence count for the periodic group element.


FKDRPCNST Descriptor 's' is a foreign key, drop referential constraint first
Explanation

A descriptor must not be released as long as it is used in a referential constraint.

Action

Drop the referential constraint(s) first.


FLDERR Field 'string' contains invalid data, RABN 'number', rp='hex-number',
Explanation

Specified field is corrupted.

Action

Unload/export the file in physical sequence, decompress, compress and load/import it again.


FLDFIL FIELDS already specified, FILE not allowed any more
Explanation

The keyword FILE was specified after a format buffer had been entered. Because the format buffer refers to the file entered, it is not possible to change the file number.

Action

Leave ADACMP and then start it again in order to change the file number.


FLK file 'file name' locked for another user
Explanation

The file could not be opened because another process, e.g. the Adabas nucleus, has locked the file.

Action

Try again after the other process has been terminated.


FMTERR Format invalid in FDT, run FCB option on file
Explanation

The FDT of the file to be verified is corrupted.

Action

Restore and regenerate file and contact your nearest support center.


FNIU field name already in use
Explanation

The specified field name was already used.

Action

Correct the input line.


FNLOAD file 'number' not loaded
Explanation

The file with the specified file number is not loaded in the database.

Action

Select another file or check the database.


FNNOTFND field not found
Explanation

The field specified cannot be found in the FDT for this file.

Action

Check the field name or file number.


FNPGTP function not permitted - global transactions pending
Explanation

The requested function cannot be performed because global transactions are still flagged on the WORK file.

Action

None.


FNRNOT File ‘number’ could not be created
Explanation

The file creation failed. There are other messages that explain the reason for this.

Action

This depends on the other messages that explain the reason for the error.


FONLYRAW Function only supported with raw device
Explanation

The selected function is only possible if the database/file is located on a raw device.

Action

Do not use the selected function unless the database/file is on a raw device.


FREADTYPE Failed to read event types from ‘filename’
Explanation

An error occurred reading the event types file.

Action

Check the contents of the event types file for illegal characters and syntax.


FROMNOT FROM checkpoint name not found in block 'number'
Explanation

The FROM checkpoint name was not found in the given block.

Action

Use the LIST=FULL function to print the checkpoint names with their associated block numbers and then rerun ADAREC.


FSSSEC No more space in first sector for management entries
Explanation

The maximum number of allocatable files (container file extents or database sequential files) for the disk section has been reached, so no more such files can be created in the disk section.

Action

Either: 1) use an additional disk section, or 2) try to remove unused files in the current section. Use the ADADEV LAYOUT function to get a list of the files in the section. Use ADADEV DEALLOCATE to remove unused files from the section.


FSTMAX invalid FST count 'number' - FST entries ignored
Explanation

The free space table contains an unexpected high number of entries. These entries cannot be displayed by the layout function.

Action

Call ADAREP FREE_SPACE and validate the result.


FTOOBIG File too big
Explanation

Because the record buffer size is limited to 2 gigabytes, it is not possible to read a file with a size of 2 gigabytes or more into a record buffer.

Action

Specify a smaller file.


FUN function not permitted on system file
Explanation

Because system files are used internally by the nucleus and other utilities, certain characteristics must not be changed.

Action

None.


FUNONL function not permitted on system file while nucleus is active
Explanation

Some functions on system files are not allowed while nucleus is active.

Action

Shutdown the nucleus and try again.


GCBAFL files loaded = 'number', GCB's actual number of files value = 'number'
Explanation

The actual number of files loaded differs from the file count stored in the general control block (GCB).

Action

Run the LOST, FILES = *, INDEX and DATA options of ADAVFY. Contact your nearest support center, giving an exact description of the utilities and functions that caused this error.


GCBFCB General control block's first file control block RABN is invalid, expected 'number', actual 'number'
Explanation

The GCB of database is corrupted.

Action

Restore and regenerate the database.


GCBFDT General control block's first file definition table RABN is invalid, expected 'number', actual 'number'
Explanation

The GCB of database is corrupted.

Action

Restore and regenerate the database.


GCBINUSE GCB is in use
Explanation

The shared memory for the general control block of the current database is in use, although this is not expected.

Action

If the shared memory for the GCB is still in use by another utility or the nucleus, try again after that utility or the nucleus has finished processing. If the GCB was not deallocated because of an abnormal termination of a utility or the nucleus, deallocate all IPC resources that are no longer in use with SHOWIPC.


GCBMAX Maximum files in entire database cannot be zero
Explanation

The GCB of the database is corrupted.

Action

Restore and regenerate the database.


GCBOVFL extent overflow in GCB
Explanation

Too many container files are defined.

Action

Try to reduce the number of container files by creating larger new ones.


GCBSYS Duplicated system file number in GCB
Explanation

The GCB of database is corrupted.

Action

Restore and regenerate the database.


GCBWERR Error when writing GCB
Explanation

An I/O error has occurred if writing the GCB block.

Action

Check the ASSO1 device for permissions and accessibility.


GRNDES group or PE group may not be a descriptor
Explanation

A group or PE group cannot be used to create a descriptor.

Action

Enter the name of an elementary or multiple-value field.


GRPINX index missing for periodic group
Explanation

A periodic group element requires an index between 1 - 99.

Action

Correct the input line.


GRPLN length not permitted with periodic group or group
Explanation

A length element may not be supplied after a group or periodic group.

Action

Correct the input line.


GRPVM group contains variable length or MU field
Explanation

A group containing a variable length or MU field may not be decompressed.

Action

Use the name of an elementary field.


HEURB database 'number' heuristically rolled back a global transaction time 'string'
Explanation

A global transaction, which has been in the state 'pending' for a long time, has been rolled back by Adabas without interaction with the transaction monitor (a so-called heuristic termination). This may be caused by:

  • a utility call that forces the users to synchronize at ET status, or

  • not enough space in the 2PC part of the WORK. In this case, the message PLOVFL is also displayed.

Action

During a running nucleus: Increase the size of the WORK container for the next nucleus session if this warning message is received several times.

During an Autorestart: Restore the database with ADABCK, and execute the ADAREC regenerate function to reapply all the updates.

During a regenerate function: Increase the size of the WORK container and rerun the regenerate.


HEURC database 'number' heuristically committed a global transaction time 'string'
Explanation

A global transaction, which has been in the state 'pending' for a long time, has been committed by Adabas without interaction with the transaction monitor (a so-called heuristic termination). This may be caused by:

  • a utility call that forces the users to synchronize at ET status, or

  • not enough space in the 2PC part of the WORK. In this case, the message PLOVFL is also displayed.

Action

During a running nucleus: Increase the size of the WORK container for the next nucleus session if this warning message is received several times.

During an Autorestart: Restore the database with ADABCK, and execute the ADAREC regenerate function to reapply all the updates.

During a regenerate function: Increase the size of the WORK container and rerun the regenerate.


HFNFD help file not found
Explanation

If online help feature is requested, Adabas cannot find the help file.

Action

Check for the existence of 'adahlp.eng' in $ADAPROGDIR (%ADAPROGDIR% if you are running on a PC).


HFNOP open error on help file
Explanation

The online help file could not be opened.

Action

Check to see whether the help file adahlp.eng exists. If it exists, check its permission levels.


HILIMRE High limit of 'string' extents reached, max = 'number'
Explanation

The maximum number of supported container files is already reached for container type 'string'. No more containers can be added.

Action

Try to reorganize the database to get free space. Check if you can combine more small containers to one larger.


HILIMTO High limit of total extents reached
Explanation

The total amount of physical extents in the database has reached its maximum.

Action

Try to reorganize the database to get free space. Check if you can combine several small containers into one larger.


HYERR HYPER EXIT 'number', descriptor 'name', file 'number', reason='number'
Explanation

The following reason was reported during the initialization of a hyperexit. A reason in the range 1-255 is an Adabas response code. A reason greater than 255 is a user-defined value.

Action

Correct the hyperexit.


HYNA HYPER-descriptor not allowed
Explanation

A hyperdescriptor may not be used to control the sequence in which a file's data records are exported.

Action

Check the field name.


HYUEXERR error response 'number' returned by HYPER-descriptor generation
Explanation

The specified error response was returned by the hyperexit or the hyperexit returned invalid data for the requested format, e.g. invalid packed/unpacked.

Action

Correct the hyperexit.


IBPERR Internal buffer pool error func: 'string' rc: 'string'
Explanation

An internal error occurred in the buffer pool management.

Action

Contact your nearest support center.


ICKW invalid combination of keywords
Explanation

An invalid combination of keywords was detected.

Action

Correct the input line.


IDOP unknown option
Explanation

The option specified is unknown.

Action

Correct the input line.


IFSD illegal format in SUB/SUPER-descriptor
Explanation

The specified format is not allowed for a sub/superdescriptor.

Action

Correct the input line.


ILLLOG Illegal log number detected, present 'number', expected 'number'
Explanation

A PLOG with an invalid number was specified when reading several PLOG files.

Action

Specify the correct PLOG number.


ILLSUB Illegal subsequent 'medium' detected, present 'number', expected 'number'
Explanation

An invalid sequential file was specified. The message displays the sequence number detected together with the required one. This message can occur if using multiple tapes.

Action

Supply a file with a correct sequence number.


INBLN invalid blank element
Explanation

The blank element supplied is invalid.

Action

Correct the input line.


INCL incomplete line
Explanation

This line is incomplete.

Action

Correct the input line.


INEDM invalid edit mask
Explanation

The edit mask supplied is invalid.

Action

Correct the input line.


INFM unknown format
Explanation

The specified format is unknown.

Action

Correct the format.


INFN field name incorrect
Explanation

The specified field name is invalid.

Action

Correct the field name.


INICF user exit init call failed with 'response code'
Explanation

The init call of the user exit displayed in the previous message did not return ADA_NORMAL.

Action

Check your user exit for the init part. Check if if returns with a response code.


INISEC first sector corrupted or not initialized
Explanation

This message is normal if the first disk section is not initialized.

Action

Contact your nearest support center if you do not have an explanation for this behavior.


INITERR database 'number', error during session initialization
Explanation

An internal error occurred during session initialization.

Action

See the subsequent error message.


INLE invalid field length
Explanation

The length of the specified field is invalid.

Action

Correct the field length.


INLIT invalid literal element
Explanation

The literal element supplied is invalid.

Action

Correct the input line.


INPERR system error on reading input
Explanation

The utility cannot read from the input.

Action

Check the input file if input redirection is being used.


INTERR internal error 'number' occurred
Explanation

An internal error occurred.

Action

Contact your nearest support center.


INUSE file in use
Explanation

The required file cannot be locked because it is currently in use.

Action

Wait until this file is available or stop the users currently using this file.


INVBP function BREAKPOINT invalid for given DATASET
Explanation

ADAPLP's BREAKPOINT function is only valid for DATASET=WORK.

Action

None.


INVBS Invalid ADABAS block size 'number'
Explanation

Only the block sizes 1 kilobyte, 2 kilobytes, ..., 32 kilobytes are permitted.

For LOB files there are the following restrictions:

  • For Data Storage, only the block size 32 kilobytes is allowed.

  • For NI and UI, only block sizes < 16 kilobytes are allowed.

Action

Correct the block size.


INVCHARS invalid character set
Explanation

An invalid character set was specified.

Action

Correct the character set name.


INVCHN Invalid container change for current disk section
Explanation

One of the specified container extents was not in the current disk section.

Action

Use ADAREP's LAYOUT function to obtain more detailed information.


INVENV invalid environment variable
Explanation

A required environment variable has an invalid content.

Action

Check the environment variable.


INVEXT Extent number 'number' exceeds maximum (255) of structure level
Explanation

The extent number you specified exceeds the maximum number of extents available for this structure level of the disk section. The maximum available for structure level 1 and 2 is 255 extents.

Action

To have more then 255 extents you have to use a structure level 3 disk section, which is created using the INITIALIZE function of the Version 3.1 ADADEV. This message can appear if you created your database with a pre-Version 3.1 version of Adabas and you now want to take advantage of the increased maximum extents offered by Version 3.1. Before you can use this Version 3.1 feature, the disk section has to be re-initialized. This involves also moving all existing container files and database sequential files from the disk section to a temporary location (using Version 3.1 ADADEV MOVE), then resetting the disk section (with Version 3.1 ADADEV RESET), then initializing (with Version 3.1 ADADEV INITIALIZE). Then you can move the container files and database sequential files back into the disk section.


INVFDT invalid FDT for system file
Explanation

While loading an Adabas system file, an FDT is supplied that is unexpected by Adabas.

Action

Use the FDT that is supported by Adabas.


INVFILE invalid file-structure for ADABAS
Explanation

An invalid structure of a PLOG block was detected.

Action

Call your nearest support center.


INVKEY invalid keyword
Explanation

The specified keyword is invalid.

Action

Correct the input line.


INVPE Invalid PE-descriptor index
Explanation

The index following a PE descriptor name is invalid.

Action

Specify a number between 1 and 99.


INVPLN block 'number' contains invalid PLOG number 'number'
Explanation

There is a mismatch between the user-supplied protection log number and the protection-log number found in the block `number'.

Action

Supply the correct protection log or correct the protection-log number.


INVPV invalid parameter-value
Explanation

The specified parameter value is invalid.

Action

Correct the input.


INVSEC Invalid disk section name
Explanation

An invalid disk-section name was specified.

Action

Correct the disk-section name.


INX... (error text ....)
Explanation

The index of the file to be verified is corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


IOCFTB Container file too big
Explanation

The specified size for a container file is too large.

Action

Correct the value of the SIZE parameter.


IODERR Data error on external file 'file-name' detected
Explanation

When reading an external file (e.g. CMPIN with ADACMP), an unexpected file structure was detected.

Action

Check the settings of the RECORD_STRUCTURE and MAX_DECOMPRESSED_SIZE parameters and check the file's contents.


IOERROR IO-error on dataset 'string', RABN 'number'
Explanation

An I/O error occurred (probably due to a bad block).

Action

Check the system error log file to determine whether a hardware problem has occurred.


IOSUBERR IO subsystem error ('number'/'number'): 'text'
Explanation

An error occurred in the IO subsystem of Adabas. The numbers contain an internal error identification, and the text contains a short description of the error.

Action

The action depends on the short description of the error. For example, the error "Buffer too small for read" may be caused by using a CMPIN file that contains data incompatible with the FDT or with the ADACMP FIELDS, RECORD_STRUCTURE or SOURCE_ARCHITECTURE parameters specified. Then, some user data can be interpreted as record length, and a value larger than the length of the IO buffer used in ADACMP may occur. In this case, using the correct FDT or ADACMP FIELDS, RECORD_STRUCTURE or SOURCE_ARCHITECTURE parameters solves the problem.

If the short description doesn't help you to solve the problem, contact your nearest support center with details about the running utility, the environment, the disk configuration and the numbers given in the message.


IOT I/O time measuring enabled / disabled
Explanation

I/O time measuring has been enabled/disabled.

Action

None.


IOTRES I/O time measuring information reset
Explanation

I/O time measuring information has been reset.

Action

None.


IRABN Dataset = 'string', RABN 'number' invalid or non-existing
Explanation

The specified RABN does not exist and cannot be printed.

Action

Check the RABN.


IRABNVAL two index RABN values must specify both small and large blocks
Explanation

Specifying two index RABN values is only allowed if one of them has a block size <16 K and the other >=16 K.

Action

Specify both small and large blocks.


IRANGE invalid range specified
Explanation

The values in the range specification are not in ascending order.

Action

Enter a correct range specification.


IREC invalid record detected
Explanation

An invalid record was detected when processing a backup/export copy. This can result from a bad input tape or a backup/export copy which was not created successfully.

Action

Try to process the previous backup copy. If the error was caused by an unreliable tape drive, run the ADABCK READ_CHECK option after each dump to check whether the backup copy created can be read by the RESTORE function.


IRECL invalid record length
Explanation

The record length must be a multiple of four for DATA_FORMAT=BINARY.

Action

Check the input file.


IRECSZ Invalid record length 'number' found, RABN 'number', rp='hex-number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


IREMUQ SET_UQ abort, resetting UQ on all repeated descriptors
Explanation

The ADAINV SET_UQ function was aborted because duplicate values were detected, therefore the unique status was not set on all of the requested descriptors.

Action

The unique status can only be set after the uniqueness conflicts have been removed. If you run the ADAINV SET_UQ function with option UQ_CONFLICT=RESET, you will get the INVERR file describing all uniqueness conflicts.


ISAINI Disk section 'string' has already been initialized
Explanation

A disk section can only be initialized once.

Action

Reset the disk section before re-initializing it.


ISDESC field has already descriptor status
Explanation

The field to be inverted already has descriptor status.

Action

Check the file number or field name.


ISNINUSE ISN 'number' in use in file 'number'
Explanation

The specified ISN is in use in the specified file.

Action

Ensure that the correct BACKUP was restored; that the PLOGs were regenerated in the correct order; that the correct file was reloaded when reloading a file; that the nucleus was started with OPTIONS = UTILITIES_ONLY and that the correct utilities have been rerun.


ISNNLS USER_ISN not allowed if NEWLINE_SEPARATOR keyword selected
Explanation

If NEWLINE_SEPARATOR is specified, ADACMP only expects data of type alpha or unpacked because binary data like USER_ISN could contain the newline byte.

Action

None.


ISNUSED ISN already in use
Explanation

When adding records to a file by USERISN, a duplicated ISN was detected. Duplicated ISNs may occur if the input file was created by ADAULD using a descriptor defined with the MU option to control the unloading sequence or when adding records to a non-empty file.

Action

Investigate the use of the USERISN option.


KCONAL keyword combination not allowed
Explanation

The supplied keyword combination is invalid.

Action

Correct the input parameters.


KEYPOS keyword not allowed in this position
Explanation

This keyword is not allowed in this context.

Action

Enter a correct keyword.


KEYREQ keyword 'string' required
Explanation

The keyword displayed in the error message is required.

Action

Enter the required keyword or exit the utility.


LABLINV Last raw section block invalid
Explanation

With previous Adabas releases, it was possible for one more block to be allocated in a raw section than was actually available. This message indicates that this has happened.

Action

If the error is displayed for a database container, create a database backup. As long as the last block has not yet been used, the backup can be created without errors. Then deallocate the database containers, recreate the database, and restore the backup. If creating the backup failed because the last block was already in use, delete the database, recreate the database, restore the database from the last successfully created backup, and recover all updates made since the time when the backup was created.

If the error is displayed for a sequential file, the last block of the sequential file is usually no longer readable. Take care to ensure that the sequential file is no longer required, for example, if it is a PLOG, create a new backup. Then deallocate the sequential file.


LABTB LAB too big
Explanation

This message occurs only on HP-UX. On HP-UX, shared memory areas must be created with the special option IPC_SHARE32 in order for them to be accessible from 32-bit applications. This option is used by default for the attached buffer shared memories, where the sizes are specified via the ADANUC parameters LAB and LABX. However, the total size of shared memories available with the option IPC_SHARE32 is relatively small. If you start several databases with relatively large values for the LAB and/or LABX parameter, it may happen that no more space for this kind of shared memory is available. Then the ADANUC start fails with the message LABTB.

Note:
A shared memory is only released when there is no process that is still accessing the shared memory. Therefore, it may happen that you can start all your databases, but when you try to restart a database it fails with the message LABTB, because there is still a process that has accessed the database and which still accesses the attached buffer shared memory.

Action
  • If you don’t have 32-bit applications accessing Adabas locally, start the Adabas databases with the nucleus parameter NOAB32BIT. Note that you are not able to access a database started with nucleus parameter NOAB32BIT from a 32-bit application locally, but a 32-bit application can access the database remotely via Entire-Network. Therefore, you can also move the 32-bit applications to another (potentially virtual) machine and then access the databases started with parameter NOAB32BIT, or you can move one or more databases to another machine.

  • Otherwise, if you could originally start a database, and you get the LABTB message when you try to restart the database, stop all processes, which have accessed the database before.

  • Another alternative is to reduce the values for the LAB and/or LABX parameters.


LBPLIC Parameter LBP restricted by licensing, original LBP='number', now LBP='number'
Explanation

The requested buffer pool size is greater than allowed by the license. The database is started with the maximum allowed LBP.

Action

To avoid this message, reduce the LBP parameter to the given value or upgrade your license.


LBPINCW LBP too small for incore WORK, required: 'number'
Explanation

Using a readonly database without a WORK container, all the required space will be used in the buffer pool, but the size is not sufficient.

Action

Increase LBP by the number displayed in the message and restart the nucleus. Refer to the Administration Manual for more information.


LBPRED parameter LBP reduced to 'size'M
Explanation

The size of the LBP parameter was reduced during nucleus startup because not enough memory is available.

Action

Increase the amount of system memory.


LCCINV The checksum in the license file ('filename') is invalid
Explanation

The license file was modified.

Action

Use an original license file.


LCEINT Internal error in licensing
Explanation

An internal error occurred during license file processing.

Action

Contact your nearest support center.


LCLEXP The license in the license file ('filename') has expired
Explanation

Adabas cannot be used any more with the given license file.

Action

Get a new license.


LCMISM The product version ('string') and the license file version ('string') don't match
Explanation

You specified a license file for another version.

Action

Use the correct license file for the given version.


LCMFIL The license file ('filename') is missing
Explanation

The license file should be located in Install directory/common/LKey.

Action

Copy the license file to its correct location.


LCSAGE Error determining $'string', loading of license file failed
Explanation

The license file could not be located.

Action

Check if the given environment variable is set to its correct value, or copy the license file to Install directory/common/LKey.


LDERR image 'string', file 'string' could not be loaded
Explanation

The image file could not be loaded into memory.

Action

See the subsequent error message.


LELE FDT's last field must be an elementary field
Explanation

FDT's last field must be an elementary field or an MU field.

Action

Correct the input parameters.


LESSHW less than corresponding high water mark
Explanation

The current highwater value of the modified nucleus parameter is greater than the new parameter value. This means that the highwater percentage of the highwater display becomes more than 100%, so it is possible that not all past applications can be re-run.


LOBDESC LOB field ‘string’ cannot be used as descriptor
Explanation

The storage of descriptor valuesin a LOB file is not supported. For this reason, an ADAINV INVERT is rejected if the field to be inverted or a parent field of a derived descriptor to be created has the LA or LB option, and values are stored in the LOB file. Note that LA or LB fields can be descriptors or parent fields of derived descriptors, but then all values are stored in the base file, the field length is restricted to 16KB -3, and each record must fit into one DATA container block.

Action

Do not use this field as descriptor or parent of a derived descriptor.


LOBFNEMP LOB file ‘LOB file number’ of base file ‘base file number’ not empty
Explanation

Drop LOB file for a base file is not permitted if the LOB file is not empty.

Action

Remove all LOB values in the file first.


LOBFNP Function not permitted on LOB file
Explanation

Some utility functions, in particular those that modify the FDT, are not permitted on LOB files.

Action

None.


LOBFNTCR LOB file for file <nr> could not be created
Explanation

The LOB file for a base file could not be created, for example because not enough ASSO or DATA space was availabe (see preceding error message). Note that the base file is OK, but that you cannot store LOB data in the file.

Action

Remove the reason why creating the LOB file failed, for example increase the size of the database, then create the LOB file with ADAFDU ADD_LOBFILE or with the DBA workbench.


LOCNAME Invalid collation locale 'string'
Explanation

The specified locale is not valid.

Note:
To ensure compatibility with earlier versions, Adabas still uses ICU 3.2 on Unix and Windows, and ICU 3.6 on OpenVMS. Therefore, locales introduced in newer versions of ICU will be rejected.

Action

Use a valid locale.


LOCNUC nucleus required on local node
Explanation

ADABCK's DUMP online function has to be performed on the node where the nucleus is running.

Action

Run ADABCK and nucleus on the same node or take down ADANUC.


LOSERR lost RABNs verification errors, 'number' found
Explanation

Some lost blocks are in the database.

Action

Use ADADBM RECOVER to add these blocks to the free space table.


LOSTNI 'number' NI blocks lost
Explanation

If ADAINV terminates abnormally, it can happen that a file's index tree is consistent, but the reusage queue containing all NI blocks that can be reused by the nucleus is not up to date, and there are NI blocks that are neither in the index structure nor in the reusage chain.

Action

If you want to reuse the lost blocks, you must run ADAINV REINVERT ALL_FIELDS. It will also help if you export and import the file with ADAORD or ADAULD/ADAMUP.


LOSTUI 'number' UI/MI blocks lost
Explanation

If ADAINV terminates abnormally, it can happen that a file's index tree is consistent, but the reusage queue containing all UI/MI blocks that can be reused by the nucleus is not up to date, and there are UI/MI blocks that are neither in the index structure nor in the reusage chain.

Action

If you want to reuse the lost blocks, you must run ADAINV REINVERT ALL_FIELDS. It will also help if you export and import the file with ADAORD or ADAULD/ADAMUP.


LTOOL input line too long
Explanation

The utility input-line contains too many characters.

Action

Shorten the input or open a subsequent line with a backslash at the end of the line.


LVOR level number out of range
Explanation

The given level number is not in the range from 1 to 7.

Action

Correct the input line.


LWPLIC Parameter LWP restricted by licensing, original LWP='number', now LWP='number'
Explanation

The requested Work Pool size is greater than allowed by the license. The database is started with the maximum allowed LWP.

Action

To avoid this message, reduce the LWP parameter to the given value or upgrade your license.


LWPTSM nucleus LWP must be at least 'number' actual files 'af'
Explanation

During ADADBM's recover function, the LWP parameter of the nucleus was not sufficient.

Action

To get this function working, the nucleus must be restarted with LWP greater/equal 'number'.


M1MU SUPER-descriptor may only contain 1 MU-field
Explanation

No more than one MU field may be specified in a superdescriptor definition.

Action

Correct the input line.


MANPARM Mandatory parameter ‘name’ missing for command ‘command’
Explanation

A mandatory parameter is missing.

Action

Specify all parameters for the command.


MAXDOVL overflow on maximum descriptors permitted
Explanation

The maximum number of descriptors permitted for a file has been exceeded.

Action

Reduce the number of descriptors.


MAXISN the file's top ISN 'number' is greater than the specified MAXISN
Explanation

A new maximum ISN which is less than the file's top ISN has been specified. This will cause ADAORD to abort if an ISN greater than the new maximum ISN is found.

Action

Check the specified maximum ISN.


MDBID DBID may be specified only once
Explanation

User tried to re-enter DBID.

Action

None.


MDEFU database already given, DBID / BACKUP_COPY may be specified only once
Explanation

DBID and BACKUP_COPY are mutually exclusive, therefore only one can be selected.

Action

Correct the input parameters.


MDVTREC missing descriptor value table records
Explanation

The input file supplied containing the descriptor value tables (DVTs) is incomplete.

Action

Supply the correct input file.


MEMMAP memory mapping failed ('string')
Explanation

An error occurred while building up the connection to the Adabas IPC driver.

Action

Check the error text given. It comes from the operating system. Try to fix the operating system problem. If this does not work, contact your nearest support center.


MFLD FIELDS may be specified only once
Explanation

The parameter FIELDS may be specified only once.

Action

Continue with other parameter settings.


MISDATA no corresponding data records
Explanation

An entry (descriptor value + ISN) is found in the index, but no record with such an ISN exists in the data storage or the corresponding data record does not contain this value.

Action

Dump the file with ADABCK and send it to your nearest support center together with a description of the actions that caused the error. Then reinvert the corrupted descriptor using ADAINV or unload and refresh the file and add the data with ADAMUP.


MISINDX no corresponding index entries
Explanation

No entry (descriptor value + ISN) is found in the index for a data record.

Action

Dump the file with ADABCK and send it to your nearest support center together with a description of the actions that caused the error. Then reinvert the corrupted descriptor using ADAINV or unload and refresh the file and add the data with ADAMUP.


MISSPAR missing mandatory parameter 'string'
Explanation

The parameter displayed in the error message is required to execute the function. If the message is displayed for more than one parameter, one of the parameters displayed is required.

Action

Enter the missing parameter.


MNPF too many parent-fields defined
Explanation

A superdescriptor cannot contain more than 20 elements.

Action

Correct the input line.


MNTAB Error during processing mount table
Explanation

An unexpected error occurred while processing the mount table.

Action

Contact your nearest support center. You can continue by switching off the mount-table check with NOMOUNTCHECK, but make sure that the disk section does not overlap the file system.


MOUNT Disk section 'string' overlaps with a mounted one
Explanation

Disk sections which overlap with mounted file system must not be initialized.

Action

None.


MPGDTAE GDT access error by adanuc/adadmn, reason: 'string'
Explanation

The ENTIRE NET-WORK Global Database Table could not be accessed.

Action

Check the error text given. It comes from the operating system. Try to fix the operating system problem. If this does not work, contact your nearest support center.


MPGDTPE GDT refuses startup permission of database 'number'
Explanation

The ENTIRE NET-WORK Global Database Table could not be accessed.

Action

Check if the GDT contains data. If not, remove it via showipc -k 0 and retry. If this does not help, contact your nearest support center.


MSGGET Message queue could not be created
Explanation

Adabas could not create a semaphore. The reason for this may be that not enough IPC resources are provided by the operating system. In particular, the operating system parameter MSGMNI or other parameters beginning with "SEM" may be too small. Refer to the Installation document for more information.

Action

Adapt the operating system parameters.


MSGNF Message queue with ID 'id' no longer available
Explanation

This error can occur if somebody, by mistake, removes a message queue created by the Adabas nucleus. When this message occurs, an Adabas client program may get an unexpected Adabas response code 148, and response code 153 for subsequent calls.

Action

Refer to the description of the response code 148 for further information.


MULTDEF database already specified, CSA may be specified only once
Explanation

DBID and CSA are mutually exclusive. Multiple CSAs are also not supported.

Action

Ensure that DBID and CSA are not both specified, or that only one CSA is specified.


MUPG MU field within periodic group required
Explanation

Field name supplied is not that of an MU field or within a periodic group.

Action

Correct the input line.


NABOBS parameter NAB has become obsolete - please use LAB instead
Explanation

The parameter NAB has been replaced by parameter LAB.

Action

Remove NAB from the parameter list. Add LAB=value, where value is the NAB value multiplied by 4096.


NCLIC Parameter NC restricted by licensing, original NC='number', now NC='number'
Explanation

The requested Command Queue size is greater than allowed by the license. The database is started with the maximum allowed NC.

Action

To avoid this message, reduce the NC parameter to the given value or upgrade your license.


NCLSERR PLOG close error, return code 'number'
Explanation

The protection log file could not be closed.

Action

Close the protection log file via ADAREC CLOSE. Check the file using ADAREC LIST=FULL. If this reports errors, do a database backup (ADABCK DUMP=*).


NCMUT NC and 'string' are mutually exclusive
Explanation

The NC option cannot be specified with the option 'string'.

Action

Correct the options.


NCPE NC option not permitted in PE group
Explanation

Fields within a periodic group must not have the NC option.

Action

Check FDT specification.


NCRQ NC option required
Explanation

The NN option is only permitted with the NC option.

Action

Specify the NC option.


NEMAFP not enough memory available for process
Explanation

The utility cannot start because the memory it requires was not supplied by the operating system. Either too many processes are currently active on the system, or the swap space was configured too small.

Action

Check the swap space or number of active processes.

OpenVMS: adjust the working set quota (Wsquo) and the page file quota (Pdflquo) accordingly.


NETREPLY NET-WORK cannot be reached for posting of reply
Explanation

The error probably occurred because the environment variables required for NET-WORK are not set or are incorrect.

Action

Set the NET-WORK environment variables correctly.


NETWORKB The network is busy.
Explanation

Access to a file stored on a network device is currently not available because of network problems. If the problem persists for more than one minute, the utility or nucleus stops with the the error message STP054.

Action

Check your network if the problem occurs frequently.


NEWCERR Error when adding a new 'string' container
Explanation

An unexpected error occurred if adding a container.

Action

Check the device and the environment variable the new container has to be located.


NEWFDTNE NEW_FDT only allowed for empty files
Explanation

The keyword NEW_FDT for ADAMUP is only allowed for empty files.

Action

Run ADADBM REFRESH for the file to remove all data from that file before you rerun ADAMUP with the keyword NEW_FDT.


NEWPAT Auto restart is pending, start with new patch level not allowed
Explanation

New patch level nucleus could only be started without auto restart.

Action

Start the nucleus with the old version. Shut down the nucleus and then use the new patch level.


NFSTSPACE Allocation failed for 'type' of file 'number'
Explanation

No more space in Free Space Table.

Action

Enlarge the space for 'type' or restart the utility with appropriate parameters.


NIEXTOVL normal index's extent overflowed
Explanation

The file's normal index extent is too fragmented, the index remains inaccessible.

Action

Unload and refresh the file, allocate larger extents and add the unloaded data with ADAMUP.


NO2BYTEISN two byte ISN no longer supported
Explanation

The export copy from Adabas Version 3 contains a file defined with ISNSIZE=2. This cannot be imported into an Adabas Version 5 database.

Action

Copy the file from Adabas Version 3 to Adabas Version 5 with the utilities ADABCK or ADAULD and ADAMUP.


NOABB no abbreviation allowed for this keyword
Explanation

This keyword must not be abbreviated.

Action

Enter the non-abbreviated keyword.


NOBLKGE not enough 'type' blocks greater-equal 'number' bytes found for file 'number'
Explanation

If the RABNs have not been specified, ADAORD only allocates from devices with a block size that is greater than or equal to the smallest block size used in the original file. Not enough blocks of this block size are available.

Action

Add a new ASSO/DATA container with the appropriate block size or place the file with the xxRABN parameters on a device with a smaller block size.


NOBLKLT not enough ASSO blocks less than 16384 bytes found for file 'number'
Explanation

Adabas makes a distinction between small and large ASSO blocks. This message indicates that not enough small ASSO blocks with a block size of less than 16 KB are available.

Action

Add a new ASSO container with the appropriate block size, or extend the last ASSO container if it has a block size of less than 16 KB.


NOBLKPOS Not enough blocks or wrong block size at specified position
Explanation

There is not enough space or a wrong block size at the specified RABN position.

Action

Correct or omit the positioning parameter and rerun ADAORD.


NOCONTALL contiguous allocation not possible
Explanation

The DSST is too fragmented, all available extents are exhausted.

Action

Check the layout of the database.


NOCPDB checkpoint file 'number' not loaded
Explanation

The database contains no checkpoint file and is only accessible in offline mode.

Action

None.


NOCPF no checkpoint-file loaded
Explanation

An attempt was made to run the nucleus without a checkpoint file having been loaded.

Action

Load the checkpoint file.


NODB No Database given, DBID or CSA required
Explanation

An attempt was made to execute a function without the database being specified.

Action

Specify the DBID.


NODBBCK no Database given, DBID or BACKUP_COPY required
Explanation

An attempt was made to execute a function without having specified a database.

Action

Specify the DBID or BACKUP_COPY or EXPORT_COPY.


NODCUFDT could not write DCUFDT field definitions file
Explanation

An I/O error occurred while writing the DCUFDT output file.

Action

None.


NODESC no descriptors present
Explanation

The file specified with the RELEASE or VERIFY function has no descriptors defined.

Action

Check the file number.


NODEVSP No space left on device 'string' for 'string'
Explanation

The current file cannot be written because the file system became full.

Action

Check the space on the given file system.


NODS no DATASET specified
Explanation

A RABN was entered before specifying a data set.

Action

Specify a data set.


NODSS missing descriptor space summary
Explanation

The input file supplied containing the compressed data records is incomplete.

Action

Supply the correct data set.


NOEND no terminator found during AUTORESTART
Explanation

The Autorestart cannot be executed properly due to an error in the protection log area in the WORK data set.

Action

Save WORK1 and send it to your nearest support center together with a description of what caused the pending autorestart and, if possible, the dump directory and the PLOG. Then restore and regenerate the database.


NOETD no USER data file loaded
Explanation

The required USER data file was not available at nucleus startup.

Action

Load the USER data file with ADAFDU with the proper file number (see ADAREP SUMMARY). If you do not have the FDT, then generate a small database with ADAFRM and extract the FDT from that USER data file.


NOFD no Field-Definitions given
Explanation

No field definitions have been entered.

Action

Provide the field definitions.


NOFIAV No files available
Explanation

No files are present in the database or the SAM file with the specified range/list specification. Please note that LOB files which are specified are often ignored. This means that you will also get this error message if there are files with the specified file numbers, but all of these files are LOB files.

Action

Check your loaded files in the database.


NOFIELDS no fields supplied
Explanation

The FIELDS parameter has been specified but no valid field names have been supplied.

Action

Supply valid field names.


NOFSEL No files selected
Explanation

No valid file number has been specified.

Note:
In some cases, only base file numbers are processed, and then you can receive this message after specifying LOB file numbers.

Action

Specify the correct file numbers.


NOFUNCP Function not permitted - AUTORESTART pending
Explanation

The selected ADADBM function is not permitted when there is an autorestart pending.

Action

None.


NOGCB GCB missing on first input file
Explanation

The first input file does not contain the general control block (GCB).

Action

Check your input file assignments.


NOINDALL index not permitted on non-PE field
Explanation

An index can only be specified on fields contained within a periodic group.

Action

Check the field name.


NOISNRU no ISN reusage allowed for checkpoint file
Explanation

ISNs cannot be reused in the checkpoint file.

Action

None.


NOLOG logging not enabled during Nucleus startup
Explanation

An attempt was made to start command logging, to force end of file for protection or command logging and this logging was not enabled during startup.

Action

None.


NOMUL no multiple file specification allowed
Explanation

A file number has been specified twice.

Action

Check the specification and make the list of file numbers unique.


NOOFFLF no offline-functions possible, Nucleus is running
Explanation

No offline functions are possible while a nucleus is running.

Action

Shut down the nucleus.


NOONLF no online-functions possible, Nucleus not running
Explanation

The nucleus is required to execute the specified function.

Action

Start the nucleus.


NOPARMOD No parameter modification possible. Try DBID to re-enable
Explanation

The ADAOPR utility could not start a utility session, therefore only ABORT, CANCEL and display functions are permitted.

Action

Try "DBID=<dbid>" again to re-enable nucleus parameter modification.


NORDONL starting nucleus in read-only mode not permitted
Explanation

The start of a read-only nucleus failed because a utility updating the data base was active.

A read-only nucleus expects that no modifications to the data base can occur during the nucleus run. As this was not possible (because utilities were updating the data base) the start of the nucleus was aborted.

A nucleus run is considered to be read-only if either the access permissions to at least ASSO1 are read-only or if the session parameter OPTIONS=READONLY is set.

Action

Retry to start the read-only nucleus when the utility causing the conflict has terminated.


NORES restore database NOT possible, only file information dumped
Explanation

The Adabas backup copy has been created by dumping selected files only. A restore database cannot be performed, since only parts of the database have been dumped.

Action

Start a restore file(s) operation or use ADABCK's list functions for more information on your backup copy.


NOSHM no shared memory available of size 'number' available ('string')
Explanation

The creation of a shared memory failed. The operating system gave the reason quoted in the text string.

Action

UNIX users - check your memory usage. Remove unused shared memories (showipc -k). Check the shm_max parameter (showipc -s). PC users - check the configuration of the virtual memory on your system.


NOSPACE no virtual memory space available
Explanation

There is not enough space reserved for the utility.

Action

Contact your nearest support center.


NOSPST Not enough free space at chosen start sector
Explanation

There is not enough contiguous free space in the disk section, starting at the specified start sector.

Action

Use ADADEV's FREE_SPACE or LAYOUT functions to obtain more detailed information.


NOTALB not able to allocate 'number' block(s)
Explanation

ADADBM's ALLOCATE function cannot allocate the specified space.

In particular, you get this error in the following cases:

  • There is not enough space available with the required block size. For example, the block size for a new DATA storage extent for a file must not be less than the maximum block size that is already in use for the file's DATA storage.

  • You specified a RABN and this RABN is already in use, or the free space at this RABN is less than the size required.

  • You specified a RABN and the block size of this RABN cannot be used, for example, because it is less than the maximum block size already in use for the file when you allocate DATA storage.

Action

Check the free space table for available space.


NOTALLAD DATA storage exhausted - not all records added
Explanation

Not all records could be added to the file by ADAMUP because there is no more space available in the DATA container.

Action

Either provide additional DATA space (ADADBM EXTEND_CONTAINER or ADADBM ADD_CONTAINER), or delete one or more existing files (ADADBM DELETE) or deallocate some DATA space for one or more existing files (ADADBM DEALLOCATE). Afterwards you can add the missing data with ADAMUP. In order to prevent data from being added twice, you must specify SKIPREC as the number of records already added (see the message ADDREC displayed before the message NOTALLAD), plus the previous value of SKIPREC. If you specified a value for NUMREC, you must reduce the value of the NUMREC parameter by the number of records already added.


NOTALM not able to allocate 'number' megabyte(s)
Explanation

ADADBM's ALLOCATE function cannot allocate the specified space.

Action

Check the free space table for available space.


NOTAUTH No authorization to execute ‘utility’ on database ‘dbid’.
Explanation

If a user tries to execute a utility but is not authorized to perform this action, this message will occur.

Action

Terminate the utility.


NOTAVL file 'number' not available
Explanation

The specified file is not available for utility usage.

Action

Wait until this file is available or stop the user currently using this file.


NOTDESC field not a descriptor
Explanation

The field to be released from descriptor status or to be displayed is not a descriptor.

Action

Check the field name and file number.


NOTEXST Entry does not exist, content: 'topic' / 'entry'
Explanation

The entry 'entry' was not found in the Adabas configuration file (ADABAS.INI or DBnnn.INI) under topic (or subtopic) 'topic'.

Action

Update the Adabas configuration file.


NOTLOAD file not loaded
Explanation

The specified file is not loaded.

Action

Check the file number.


NOTLOCK file not locked
Explanation

The required file cannot be unlocked.

Action

None.


NOTNUM given value not numeric
Explanation

The value required must be numeric.

Action

Enter a numeric value.

Note:
Only valid unsigned integer values are accepted as numeric, i.e. values <2**32 on 32-bit platforms and values <2**64 on 64-bit platforms. There may be further restrictions for values not explicitly mentioned in the documentation, for example, sufficient memory must be available.


NOTPOSS database 'number' not converted to version 'number'
Explanation

The conversion failed. The reason for this has been explained in a previous message.

Action

This depends on the reason why the conversion failed. See the corresponding message.


NOTPRES ISN(s) to be deleted not present
Explanation

The ISN(s) to be deleted are either outside the specified file's limits (MAXISN) or are not in use. See the subsequent message given.

Action

Supply correct ISN(s) or use the ADAMUP option ISN_NOT_PRESENT=IGNORE.


NOTR No TR option for field 'string'
Explanation

The specified descriptor has the TR option in the sequential input file for ADAMUP's ADD function, but not in the database.

Action

Define the TR option for the descriptor in the database as well. Always consider the special handling of descriptors defined with the TR option when such descriptors are accessed.


NOTRSPA No trailing space, container could not be extended
Explanation

If a container extent is defined on raw device, it can only be extended if there is enough free space directly behind the container extent.

Action

Perform ADD_CONTAINER instead of EXTEND_CONTAINER.


NOTSET Option was not set previously
Explanation

The option to be deleted was not set previously.

Action

None.


NOTSUP device type not supported by Adabas
Explanation

Open error on file displayed in the previous message, because the device cannot be used. This is for example when a PLOG is assigned to a tape for more than 1 thread.

Action

Assign the file in question to a proper device (raw disk, file system).


NOTUQ unique conflict detected
Explanation

Duplicate values detected when inverting or verifying a descriptor defined with the unique option.

Action

If the error is reported by the VERIFY option of ADAINV for an existing descriptor, dump the file with ADABCK and send it to your nearest support center together with a description of the actions that caused the error. Remove the error using the REINVERT function with the UQ_CONFLICT=RESET option.


NOTZ No timezone database found
Explanation

Depending on the platform, Adabas expects that the time zone database is either provided by the operating system or that the time zone database is created during the Adabas installation.

Action

Contact your system administrator. It is possible that the time zone database is not available because a newer version of the time zone database is being installed.


NOUQDESCS no unique descriptors present
Explanation

There are no unique descriptors defined for the file.

Action

Check the file number.


NOWOEX WORK extend online not possible
Explanation

When the nucleus is active it is not possible to extend the WORK container.

Action

Shutdown the nucleus and retry.


NSPALL No space allocated for this container
Explanation

Space can only be deallocated or reallocated if it has already been allocated.

Action

None.


NSPSEC Not enough free space
Explanation

There is not enough contiguous free space in the disk section.

Action

Use ADAREP's FREE_SPACE or LAYOUT functions to obtain more detailed information.


NTLIC Parameter NT restricted by licensing, original NT='number', now NT='number'
Explanation

The requested number of threads is greater than allowed by the license. The database is started with the maximum allowed NT.

Action

To avoid this message, reduce the NT parameter to the given value or upgrade your license.


NUCLOST synchronization with nucleus lost
Explanation

Synchronization with nucleus lost by a utility due to:

  • utility's user-queue entry removed

  • nucleus termination.

Action

ADAREC: restore database or file and rerun utility. Others: rerun utility.


NUCNOA2A Adabas nucleus currently not able to perform A2A replication.
Explanation

The Adabas nucleus can only perform Adabas-to-Adabas replication if a replication exit is active. The replication exit is a part of the Adabas Event Replicator.

Action

Restart the Adabas nucleus with the replication exit. Refer to the Adabas Event Replicator documentation for further information.


NUCVTE Unexpected response code 'number' from system file conversion
Explanation

An error occurred after the database was converted from and old version by ADACVT and the nucleus wants to process the system files at startup.

Action

At the next nucleus shutdown, reload / reorder the system files and pay attention to the next nucleus startup.


NULIC Parameter NU restricted by licensing, original NU='number', now NU='number'
Explanation

The requested User Queue size is greater than allowed by the license. The database is started with the maximum allowed NU.

Action

To avoid this message, reduce the NU parameter to the given value or upgrade your license.


NUMADEXH Number of additional 'ASSO/DATA' extents currently exhausted
Explanation

The maximum number of created containers within one utility run is reached. Due to internal structures it is only possible to create a specific number of containers with one active utility.

Action

If the nucleus is active, shut it down and restart it Otherwise terminate ADADBM and restart it.


OBCKTIR Online backup not responding, hang up 'date'
Explanation

During an online backup synchronization between ADANUC and ADABCK, the ADABCK process did not signal to the nucleus. This can happen if, for example, ADABCK was killed with signal 9 at a specific point. The online backup will be disabled and the nucleus will continue normally.

Action

Check if the ADABCK process still exists and restart the dump.


OFFCAP CANCEL or ABORT possible
Explanation

The nucleus online connection to ADAOPR is aborted but CANCEL or ABORT is still possible via CSA access.

Action

CANCEL or ABORT or none.


ONLALL 'string' not created in disk section 'string'
Explanation

The displayed container or SAM file can only be accessed if it is created in the disk section.

Action

Check the environment variable and disk-section content.


ONLDBA 'string' of database 'number' not created in disk section 'string'
Explanation

The displayed container or SAM file of the displayed database can only be accessed if it is created in the disk section.

Action

Check the environment variable and disk-section content.


OP1P option only permits one parent field
Explanation

The HY option only permits one parent field to be used by a hyperexit.

Action

Check the hyper-definition.


OPNERR dataset 'string', file 'string' could not be opened
Explanation

The required data set could not be opened. The reason is given in a subsequent error message.

Action

See subsequent error message.


OPNFAIL Opening file ‘name’ failed: ‘reason’
Explanation

Failed to open the file.

Action

Check the error and fix the problem.


OPNP option not permitted
Explanation

The supplied option is not permitted for this function.

Action

Correct the input parameters.


OPRDONL dataset 'string', file 'string' opened for readonly access
Explanation

While opening the container files, the specified container can only be opened in read-only mode, but there is not a readonly database (ASSO1 is writeable). Beware that errors might occur later on if write requests to that container are issued.

Action

Make sure that this is what you want. If not change the file protection of the readonly container that the write operations will use.


ORDEXPERR ORDEXP corrupted
Explanation

The sequential dataset ORDEXP is corrupted.

Action

Rerun ADAORD EXPORT.


ORDINTERN ADAORD internal error rc: 'number'
Explanation

Internal error in ADAORD.

Action

Report 'number' to your nearest support center.


OVLSYSF Overlay of system file ‘number’ not allowed
Explanation

It is not allowed to overlay system files.

Action

Specify another file number.


PAGFILE Paging file too small
Explanation

The current utility or the Adabas nucleus has to abort because the system paging file is too small.

Action

Increase the size of the paging file.


PARMVAL missing parameter value(s)
Explanation

The utility has been terminated due to missing parameters.

Action

Rerun the utility with a complete set of parameters.


PAROBS parameter 'string' has become obsolete
Explanation

The specified parameter is no longer supported in Adabas, and is therefore ignored.

Action

Remove this parameter from your scripts.


PARTLOAD file only partially loaded
Explanation

Due to exhausted DS or extent overflow, the file was only partially loaded.

Action

Enlarge the database, or (in case of an extent overflow) reorder the file and rerun ADAMUP with the option SKIPREC = number of records already loaded.


PCREATE Failure on accessing image 'string': 'string'
Explanation

The specified image is not present or cannot be accessed.

Action

Check the associated environment variable and the image file.


PEMU periodic group or MU field required
Explanation

The element name supplied is not the name of a periodic group or MU field.

Action

Correct the input line.


PEMUNOT periodic group or MU field not permitted in name-name element
Explanation

Within a name-name element, the first name and last name must be an elementary field. A periodic group or MU field is not permitted between the names.

Action

Correct the input line.


PENDRES pending AUTORESTART
Explanation

An attempt was made to start a utility and the last nucleus session was terminated improperly. Alternatively, a utility was started after an ADAOPR SHUTDOWN, but before the Adabas nucleus actually terminated.

Action

Start the nucleus and perform the Autorestart. In the second case, wait until the message `shutdown completed' appears in the nucleus log file (NUC.LOG). When the utility is started again, the message `Pending Autorestart' should no longer be displayed.


PFAL parent-field must have alpha format
Explanation

The corresponding field must have alphanumeric format.

Action

Correct the input line.


PFGR parent field may not be group or PE-group
Explanation

A parent field used by a sub-, super- or phonetic descriptor may not be a group or a periodic group.

Action

Check the field name.


PFND parent field not defined
Explanation

The sub- or superdescriptor definition contains an undefined field.

Action

Correct the input line.


PGL1 periodic group may only be defined at level 1
Explanation

A periodic group can only be defined at level 1.

Action

Correct the input line.


PGOVL periodic group must have less/equal 255 elements
Explanation

An attempt was made to exceed the maximum number of elements allowed in a periodic group, namely 255.

Action

Redesign your FDT. Consider splitting the periodic group.


PHNA PHON-descriptor not allowed
Explanation

No phonetic descriptors can be specified in this context.

Action

Correct the input line.


PKDRPCNST Descriptor 's' is a primary key, drop referential constraint(s) first
Explanation

A descriptor must not be released as long as it is used in a referential constraint.

Action

Drop the referential constraint(s) first.


PLACT can't close active 'string' of database 'number' in disk section 'string'
Explanation

The current PLOG file of a running database must not be closed.

Action

Correct the input values.


PLEMPTY protection log empty
Explanation

Empty PLOG block found.

Action

Contact your nearest support center.


PLEXTOVFL PLOG extent overflow avoided, session cancelled
Explanation

The number of PLOF file extents reached 65535. The nucleus shut down in order to prevent the extent counter from overflowing.

Action

Start the database nucleus again.


PLNOTO there is no opened 'string' of database 'number' in disk section 'string'
Explanation

There is no unclosed PLOG file with specified PLOG number in the disk section pointed to by RECPLG.

Action

Correct the logical name RECPLG or the PLOG or DBID number.


PLOGLIC Parameter PLOG restricted by licensing, original PLOG=set, now PLOG=disabled
Explanation

The license does not let you run the database with a protection log, so logging is disabled.

Action

To avoid this message, start the database with NOPLOG or upgrade your license.


PLOGSW PLOG switch failed.
Explanation

A PLOG switch failed because not all blocks could be written to the old PLOG file. In particular, this may happen if the PLOG is stored on a remote file system. For performance reasons, the write error is not noticed during the write operation of the first block that cannot be written to the file, but rather for a subsequent I/O command.

Action

Do not specify either of the nucleus parameters UNBUFFERED=(...,NOPLOG) and UNBUFFERED=CLEAR - in this case, file synchronisation is performed after writing each PLOG block, and it is no longer possible to loose blocks that are written to the old PLOG. However, if you prefer to use UNBUFFERED=(...,PLOG), you must prevent the the file system that contains the PLOG from becoming full, for example by initiating a PLOG switch after a given amount of time.


PLOGWRER PLOG write error
Explanation

The write to the PLOG failed. Together with this message, some other messages are printed describing the kind of error that occurred.

Action

Assign the PLOG to a file system or raw device with enough free space and without I/O problems, and restart the nucleus.

Note:
In particular, if this error occurs because of an I/O error, it may also happen that parts of the PLOG, which are located in front of the PLOG block that could not be written, are corrupted. Therefore, it is recommended to create a new backup as soon as possible, in order to guarantee that no data are lost if a restore/regenerate is required.


PLOVFL Database 'number' overflow of WORK, time 'string'
Explanation

An overflow occurred in the protection log area in the WORK data set during

  • a running nucleus

  • an Autorestart

  • a regenerate function

This message informs the user that an implicit BT has been performed for a user, or that XA transactions have been heuristically terminated.

Action

Increase the size of the WORK data set (ADADBM EXTEND_CONTAINER function), or replace the existing WORK data set with a larger one (ADADBM NEWWORK function).


PLPLINV PLOG must be specified before DATASET
Explanation

The PLOG parameter of ADAPLP is only processed if it is specified before the DATASET parameter.

Action

Rerun ADAPLP and specify the PLOG parameter before the DATASET parameter.


PLRFILE FILE required if ISN is specified
Explanation

The ADAPLP parameter ISN is allowed only if a file is specified via the FILE parameter.

Action

Correct the input line.


PREDCONT not all requested blocks removed
Explanation

ADADBM REDUCE_CONTAINER could not remove all blocks

Action

Reduce only free blocks on the last container.


PREPEMAR Preparing emergency auto restart
Explanation

Due to a WORK overflow, the nucleus must be aborted, because otherwise it cannot be guaranteed that all open transactions can be rolled back, since a backout transaction may require additional space on WORK.

Action

Restart the nucleus.


PWNF password 'string' not found
Explanation

The specified password was not found in the security file.

Action

Enter the correct password.


PWUSE password 'string' already in use
Explanation

The specified password is already present in the security file.

Action

Enter a new password.


RAWCORRUP Raw section 'string' is corrupt or not initialized
Explanation

Either the raw disk section was not initialized, or a corruption was detected on the disk section. Reason for a corruption may be that another program has written to the disk section.

Action

If the raw section was not initialized, initialize it with ADADEV INITIALIZE. If the disk section is corrupt, you must recreate the disk section. Depending on the corruption, it may still be possible to access databases stored on the disk section. Then you should shutdown the databases and create a backup before you recreate the disk section. After recreation of the disk section you can recreate databases stored on the disk section, and restore recover the database contents from the latest backup and protection logs.


RCNOFL REGENERATE = file list is no longer supported
Explanation

ADAREC no longer supports regeneration without ET logic (see also the Release Notes).

Action

Use ADAREC REGENERATE = *. Using the EXCLUDE_FILES parameter allows you to regenerate only selected files.


RDBFDT DBID or FDT required as first input
Explanation

The first input parameter for the started utility must be either DBID or FDT.

Action

Correct the input line.


RDERR dataset 'string', RABN 'number' read error
Explanation

A read on the specified data set failed. The reason is given in a subsequent error message.

Action

See the subsequent error message.


RDEVPN Disk section device file path name required as first input
Explanation

The user has to specify the SECTION=<section name> parameter before any other input.


RDONLRQ Nucleus can only be started in read-only mode.
Explanation

The start of an update nucleus failed because a read-only utility was active. A read-only utility cannot write a UCB entry used to synchronize data base activity and utility updates. As synchronization between utilities and the nucleus is not possible an update nucleus cannot start.

Retry to start the nucleus when the utility causing the conflict has terminated or start the nucleus with OPTIONS=READONLY.

Action

Correct the environment variable WORK1 or restart the nucleus with the option READONLY.


RDONP Dataset WORK1, READONLY is not permitted
Explanation

WORK1=READONLY is defined, but the corresponding database is not located on a readonly device, or the current session is not running with the READONLY option.

Action

Correct the environment variable WORK1 or restart the nucleus with the option READONLY.


READDBINIERR Error reading DBnnn.INI file
Explanation

An error occurred when reading the DBnnn.INI file

Action

Check that the file exists and is readable.


READERR Error when reading container file
Explanation

An unrecoverable error occurred while attempting to read the container file.


READERR Error when reading SAM file
Explanation

An unrecoverable error occurred while attempting to read the SAM file.


READINIERR Error reading ADABAS.INI file
Explanation

ADABAS.INI file could not be read.

Action

Check the permissions of ADABAS.INI and try to read it again.


RECACT ADAREC REGENERATE currently active
Explanation

During regeneration, the database is exclusively locked by ADAREC.

Action

None.


RECCMD 'number' 'string' command(s)
Explanation

The displayed commands were processed by Adabas between nucleus startup and ADAREC REGENERATE startup.

Action

Check whether this violates the consistency of your database.


RECCORRUP Corrupted record has been found, ISN = 'number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  1. Unload/export the file in physical sequence, decompress, compress and load/import it again (this will lose some data), or

  2. Restore and regenerate file and contact your nearest support center.


RECEEC MU Field has an embedded empty field count in RABN 'number' , rp='hex-number', ISN='number'
Explanation

Data in RABN/ISN is corrupted.


RECENN Empty field count, rp='hex-number' found for NN option field 'string', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECENU Empty field count, rp='hex-number' found for non-NU option field 'string', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECEPE Field found in empty periodic group 'string', rp='hex-number', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECERR Record structure error in RABN 'number' , rp='hex-number', expected end address not the same as actual end address
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECFL2 Field 'string' invalid 2 byte length of 'number', RABN 'number', rp='hex-number', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECFLN Field 'string' invalid length of 'number', RABN 'number', rp='hex-number' ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECISB Invalid starting block 'number' found in first block
Explanation

An invalid block number was found in the first block of a PLOG.

Action

Use ADABCK to back up the database, as the PLOG cannot be used by ADAREC to regenerate the database. Send the PLOG in question to your nearest support center.


RECMIS Before image mismatch for ISN 'number' in file 'number'
Explanation

While processing the protection log, an executed command resulted in a nucleus response code.

Action

Inspect the block at the record number associated with the error response, e.g. a file may not have been restored, with ADABCK, with the correct dump. This results in the file being in a state different to that when the original command was executed.


RECMLN MU Field length of 'number' in RABN 'number' , rp='hex-number', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECNOTF record NOT found for ISN 'number' in file 'number'
Explanation

The record for the specified ISN cannot be found in the specified file.

Action

Ensure that the correct BACKUP was restored; that the PLOGs were regenerated in the correct order; that the correct file was used when the file was reloaded; that the nucleus was started with OPTIONS = UTILITIES_ONLY and that the correct utilities have been rerun.


RECNUP Empty field, rp='hex-number' found for NU option field 'string', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECPEI Periodic group 'string' has invalid index 'number', rp='hex-number', ISN='number'
Explanation

Data in RABN/ISN is corrupted.

Action

Do one of the following:

  • Unload/export the file in physical sequence, decompress, compress and load/import it again (some data might be lost), or

  • Restore and regenerate the file and contact your nearest support center.


RECTOOBIG record too big for data-storage device
Explanation

The compressed record is too big for the used device.

Action

Decrease the size of the records or use a device with larger block size, or decrease the padding factor.


RECUPD Updates performed between Nucleus and Regenerate's startup
Explanation

Updates have been performed between starting the nucleus and the regenerate startup. This may result in errors being reported by ADAREC's REGENERATE function.

Action

If errors are reported, the database must be restored and the regenerate rerun. The nucleus must be started with OPTIONS=UTILITIES_ONLY.


REEXEC Re-execute all SYNP Utility functions starting from block 'number'
Explanation

ADARC could not re-execute one or more utility functions. This must be done manually by the user.

Action

Re-execute the functions manually. If a RESTARTP message follows, you must restart the ADAREC utility to continue the regenerate; if a PROCESSED message follows, the regeneration of the Adabas protection log is completed after re-executing the utility functions.


REGDAT Regenerating ONLY data-storage for file 'number'
Explanation

An index error occurred during the regenerate. The data will, however, still be regenerated.

Action

When the regenerate has finished, run the ADAINV utility with REINVERT=file_number, ALL_FIELDS.


REGENPL protection log was generated by REGENERATE function
Explanation

The protection log assigned contains entries originating from ADAREC when regenerating a previous protection log.

Action

Make sure the correct protection log has been assigned.


REMSHM Unable to remove shared memory ('hex number')
Explanation

Within the detach shared memory procedure, the shared memory could not be removed.

Action

UNIX users - use the ipcs command or the showipc tool to look for the shared memory key 'hex number'. You can remove it with ipcrm or showipc -k. PC users - none.


REMUQ unique status removed on descriptor
Explanation

The unique status of a descriptor was removed due to a user-specified action.

Action

None.


RENUMERR Renumber error
Explanation

The specification of the RENUMBER parameter is not correct; refer to the description of this parameter in the Utilities manual for details.

Action

Specify the RENUMBER parameter correctly.


REPUI Invalid start flag in UI detected, now repaired
Explanation

The Adabas index processing detected an inconsistency and repaired itself.

Action

Continue with normal operation but contact your nearest support center if it happens often.


REQDBID DBID required as first input
Explanation

An attempt was made to execute a function without the database being specified.

Action

Specify the DBID.


REQFIL FILE required as next input
Explanation

The keyword FILE is required as the next entry.

Action

Enter the keyword FILE.


REQLEV database 'number' already at structure level for version 'vers'
Explanation

The database is already at the requested level.

Action

None.


RESDEN UCB reset denied, process with pid 'number' alive
Explanation

You cannot reset a UCB entry of a utility which is still active.

Action

UNIX users - correct the IDENT given in the RESET=UCB function or find out the utility with the 'ps' command. PC users - correct the IDENT given in the RESET=UCB function or find out the utility using the Windows NT task manager or any comparable tool.


REUCUT error detected in reusage chain at rabn <rabn>, cut chain
Explanation

The index reusage chain has an incorrect block, the chain is completely cut. This does not affect the database consistency, but does result in lost index blocks.

Action

Reinvert the index of the file which contains the RABN indicated in order to return the lost index blocks. You can use ADAVFY's INDEX function to display the number of lost blocks.


REULOST Reusage rabn 'number' of file 'number' out of range, not inserted
Explanation

An error occurred while inserting an index block into a reusage chain.

Action

Check the block number given if present within the allocated index blocks of the given file. Use ADAVFY INDEX if there are many lost index blocks.


REXABORT Adabas nucleus terminated by replication exit with dump
Explanation

A replication exit provided, for example, by the Adabas Event Replicator, detected an unrecoverable error and initiated the termination of the Adabas nucleus process with a dump.

Action

Refer to the documentation of the product that provided the replication exit for further information.


REXCANCEL Adabas nucleus terminated by replication exit
Explanation

A replication exit provided, for example, by the Adabas Event Replicator, detected an unrecoverable error and initiated the termination of the Adabas nucleus process.

Action

Refer to the documentation of the product that provided the replication exit for further information.


RIDEF Definition of referential constraint 'name' failed, reason 'reason'
Explanation

The definition of the referential constraint 'name' failed. The reason is given by a number:

Number Explanation
1 Primary/foreign file not loaded
2 RI not with system file
3 Primary/foreign key not found
4 Primary not unique
5 Length/format mismatch
6 Error in constraint name or not unique
7 Constraint action invalid/not permitted
8 SET_NULL and NC/NN options mismatch
9 Primary/foreign field name is not a descriptor or the descriptor options are not allowed
10 Error in self-referencing specification
11 Primary/foreign field is already referenced or RI constraint already exists
12 Data integrity violation
13 Invalid superdescriptor reference
14 RI not with NOBT files
Action

The action depends on the reason number returned.


RIIDFL invalid specification for a default (reason='rsp')
Explanation

The default value specified was invalid. The reason value is the Adabas response code that is signalled by the nucleus.

Action

Correct the default value.


RIINOR ISN 'isn' of file 'file' has no reference in file 'rfile'
Explanation

Referential integrity error when loading data.

Action

Provide the missing data in the file ‘rfile’which are required for referential integrity.


RIMISF Reference to missing file 'file' detected
Explanation

A referential integrity constraint was found referencing a file that was not specified to be processed by the utility.

Action

Remove the referential integrity constraint first, or specify the referenced file as well..


RIRFSH Primary file of referential constraint
Explanation

Setting PGM_REFRESH is not allowed for a file that is the primary file of a referential integrity constraint.

Action

Do not use an E1 command with ISN 0 to delete all the records on the file. Instead, you can, for example, specify the primary and secondary file of the referential constraint in ADADBM REFRESH.


RKEYERR Cannot read ‘key’ key from DBnnn.INI file
Explanation

Reading the key from the DBnnn.INI file failed.

Action

Ensure that the DBnnn.INI file is accessible and the key is in the file.


RLLE resulting length has to be less-equal 'number'
Explanation

The resulting superdescriptor length must be less than or equal to the displayed value.

Action

Correct the input line.


RNOTAV RABNs not available
Explanation

In case of ALLOCATE, the RABNs are not contained in the database or are already in use.

In case of DEALLOCATE, the RABNs do not belong to the specified file, or RABNs to be deallocated are in use, or the Address Converter RABNs are not in the last extent.

Action

Check which RABNs are available using the ADAREP printout.


RNOTFREE RABN 'number' not available
Explanation

RABN 'number' as specified in the parameter ACRABN, DSRABN, UIRABN or NIRABN is already used.

Action

Specify a valid RABN.


RONLYDB Readonly database, some functions disabled
Explanation

There are two possible reasons for this message:

  1. You are running a utility against a readonly database, so only those functions are available which do not make any modifications in the database.

  2. You don't have update permissions for the database containers. This can happen if you don't belong to the administrator group (typically "sag").

Action

If the changes are required for a read-only database, change the database to a normal database and try again. If you have missing permissions, somebody with sufficient permissions must perform the utility operation.

Note:
Because of the missing write permissions, utilities do not write checkpoints.


RPCPERR Structure error in checkpoint record (ISN 'number')
Explanation

The checkpoint record with ISN 'number' has an internal structure error.

Action

Unload the Adabas checkpoint file and send it to your nearest support center. Decompress the checkpoint file then compress and load again.


RPLFID Replication system files already defined
Explanation

If the replication system files already exist, ADADBM REPLICATION_FILES must not be executed again.

Action

If you want to ignore all existing Adabas - Adabas replications and define new replication definitions, you must first perform ADADBM REMOVE_REPLICATION.


RPOFFF Offline database access failed
Explanation

You used ADAREP which works with an online database but the nucleus went down meanwhile and the physical container assignments are not set.

Action

Set the container assignments and restart ADAREP which now will access offline.


RQINVF INV, REINV, REL, SET_UQ, SUM, RESET _UQ or VER. required next
Explanation

The next keyword must be one of: INVERT, REINVERT, RELEASE, SET_UQ, SUMMARY, RESET_UQ or VERIFY.

Action

Correct the input line.


RSERR dataset 'string', read error
Explanation

A read on the specified data set failed. The reason is given in a subsequent error message.

Action

See the subsequent error message.


RSFN reserved field name
Explanation

The specified field name is reserved.

Action

Correct the field name.


RTOOBIG format buffer generates a record buffer larger than 'number'
Explanation

The given format buffer causes a record overflow.

Action

Contact your nearest support center.


RUIERR invalid index level 'number' in reusable RABN 'number'
Explanation

The index reusage chain is corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


RULERR invalid length of 'number' in reusable RABN 'number'
Explanation

The index reusage chain is corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


RUNILOOP Loop in NI reusage chain
Explanation

The index reusage chain is corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


RURERR invalid RABN 'number' in reusable RABN 'number'
Explanation

The index reusage chain is corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


RUUILOOP Loop in UI/MI Reusage chain
Explanation

The index reusage chain is corrupted.

Action

Run adainv with option reinvert descriptor or all fields if message contained no descriptor and contact your nearest support center.


SACERR Access error to the disk section string
Explanation

A system call performed on a disk-section device-file aborted.

Action

See the subsequent 'errno' message.


SAMDIR Directory must not be specified for SAM file 'string'
Explanation

It is not allowed to specify a directory for the Adabas sequential file.

Action

Set the environment variable for the Adabas sequential file to the file in the directory that is to be processed.


SAMEFIL same input file assigned twice
Explanation

When unloading from a multi-file Adabas backup copy, the same input file has been assigned twice.

Action

Check the input file assignments and rerun the utility.


SAMOERR Error when opening SAM file
Explanation

There is a problem opening a sequential file.

Action

Check the reason for the open failure (e.g. wrong filename, insufficient permissions). The reason is displayed in previous message.


SAMPLATF SAM file created on different platform
Explanation

The utility can only process SAM files created on a platform with the same endianness.

Action

Process the SAM file on a platform with the correct endianness.


SBVNOTEXP Security by value definition not exported
Explanation

One or more security-by-definition values could not be exported. The reason for this is that the export was made with a mainframe as the target platform and a search buffer contains W formatted fields. This error is the result of WMFEXP warnings which occur before while exporting the security-by-value definitions.

Action

See the action for WMFEXP.


SCACRE 'string' already created in disk section 'string'
Explanation

The displayed container or SAM file already exists in the disk section.

Action

Deallocate the space or change the environment variable.


SCADBC 'string' of database 'number' already created in disk section 'string'
Explanation

The displayed container or SAM file of the displayed database already exists in the disk section.

Action

Deallocate the space or change the environment variable.


SECNOE Disk section not empty
Explanation

The user tried to do a RESET on the disk section, but the section still contains container or sequential files.

Action

Deallocate all containers and sequential files in the disk section before the RESET.


SECINUSE 'filename' in raw section 'sectionname' is in use and must not be deallocated
Explanation

As long as an Adabas database container or sequential file is in use by the nucleus or a utility, it is not possible to deallocate it.

Action

Wait until the nucleus or utility has terminated. In the case of a CLOG or PLOG in use by the nucleus, you can perform the ADAOPR FEOF function to close the CLOG or PLOG.


SECINVNAME Invalid raw section name 'string' (returned type 'number')
Explanation

The specifed raw section name is invalid. The returned type number indicates the file type of the name:

Type Number Meaning
-2 Unexpected file type
-1 System error (invalid file name, access permission etc.)
0 Regular file
1 Tape device
2 Block device
3 Raw device
5 Named pipe
6 Directory
Action

Action

Specify a valid raw section name.


SEINVPW password must not contain any special characters
Explanation

Invalid password given.

Action

Correct password specification.


SEMGET Semaphore could not be created
Explanation

Adabas could not create a semaphore. The reason for this may be that not enough IPC resources are provided by the operating system. In particular, the operating system parameter SEMMNI or other parameters beginning with "SEM" may be too small. Refer to the Installation document for more information.

Action

Adapt the operating system parameters.


SEMLOST Synchronization semaphore lost, recreated
Explanation

The semaphore used by Adabas was not available upon reaching a synchronization point. This could happen if someone removes the semaphore entry with the UNIX command "ipcrm". Adabas will recreate the semaphore and continue.

Action

Check if somebody used ipcrm.


SEMNCR Semaphore could not be created, system limit reached
Explanation

The requested semaphore could not be created by the utility.

Action

Check the UNIX semaphore table for a clean-up, or rebuild the UNIX kernel with a sufficient number of semaphores.


SEMUCNT number of files in list may not exceed 'number'
Explanation

Too many files given in the file list.

Action

Specify only 'number' files in one file list.


SEPINV FB not in FDT sequence for separator option (field 'name')
Explanation

If you use the SEPARATOR option of ADACMP, the fields you specify must be in the same sequence as defined in the FDT.

Action

Correct the field order.


SEPWOVF Too many passwords to display
Explanation

Password overflow for the display function.

Action

Contact your nearest support center.


SEQNA Export with SORTSEQ for ADAM file not allowed
Explanation

An ADAM file may only be exported in physical sequence.

Action

Correct the input line.


SEV1FL Exactly one file must be specified
Explanation

Within a security by value specification there must only be one file number.

Action

Correct file number expression.


SEVFNL Unable to specify value criteria, file 'number' not loaded
Explanation

The file specified with a security by value specification is not loaded in the database.

Action

Correct file number expression or load file first.


SEVRBOVF Value criterion too long, max record buffer length exceeded
Explanation

The value criterion in total exceeds the buffer to be transferred to the nucleus.

Action

Decrease the size of the value criterion and contact your nearest support center.


SEVSB Syntax error in 'string' search buffer
Explanation

The search buffer specified for the ACCESS/UPDATE criterion was incorrect.

Action

Refer to the Command Reference Manual for the valid search buffer syntax.


SEVSBF Format error in 'string' search buffer at field 'string'
Explanation

The field name given in ACCESS/UPDATE search buffer was invalid

Action

Refer to the Command Reference Manual for the valid search buffer syntax.


SEVVB Syntax error in 'string' value buffer
Explanation

The value buffer specified for the ACCESS/UPDATE criterion contains invalid data for a field.

Action

Check the values against the fields in the search buffer.


SEVVBL Field in 'string' value buffer inconsistent with search buffer
Explanation

The value buffer and search buffer of the ACCESS/UPDATE criterion have inconsistencies in their length. The search buffer expects more values at the field given.

Action

Check the value lengths against the fields in the search buffer.


SFNOTPO subsequent file extents not possible with input redirection
Explanation

Adabas attempts to prompt for a subsequent file, but input redirection is being used.

Action

Start the program interactively.


SFSLMM structure level mismatch on sequential file: 'filename'
Explanation

The utility attempted to access a sequential file that was created by a different version of Adabas. This was not possible as a result of structural changes. In general, input files that are created by previous versions can be supported, but input files that are created by later versions will be rejected.

The error can also occur in ADACLP if a command log is processed that was created by a nucleus session which was started with CLOGLAYOUT=6.

Action

Check the input file assigned.

In the case of ADACLP for a command log created by a nucleus session that was started with CLOGLAYOUT=6, use prilogc instead of ADACLP. Please refer to Utilities, Appendix B - prilogc for further information.


SHMNOA Adabas shared memory service not available
Explanation

Starting with Windows Vista and Windows Server 2008, Adabas requires a shared memory service on newer Windows operating systems. This service is not available.

Action

Start the service. Refer to Administration, Adabas Services on Windows, Adabas Shared Memory Service for more information.


SHORTOPT DVT required not present, file created using the SHORT option
Explanation

A mass add is to be made to a database file which has descriptors defined, but the input for the mass add does not contain the descriptor value table entries (DVT) required.

Action

Supply an input file containing DVT entries or release all descriptors currently present in the database file targeted for the mass add.


SIGNAL signal 'number' occurred
Explanation

An unexpected signal was generated by the system.

Action

Contact your nearest support center and tell them the signal number.


SLOR standard length out of range
Explanation

The specified length value is too large. A length value >253 is only allowed for fields with the LA or L4 option.

Action

Correct the length specification, or specify the LA or L4 option.


SMMSEC Structure level mismatch, first sector corrupted or not initialized
Explanation

This message is normal if the disk section is not initialized. It is possible that the disk section was initialized by a different version of Adabas: structural changes mean that it is not possible to access the disk section with this version.

Action

Contact your nearest support center if you do not have an explanation for this behavior.


SMPIERR SMP initialization failed with ('number'): 'string'
Explanation

An error occurred in the process initialization.

Action

Check the error text given. It originates from the operating system. Try to fix the operating system problem. If this does not work, contact your nearest support center.


SMPNULL Null pointer from SMP resource allocation in line <number>
Explanation

The allocation of a resource for the internal Adabas component SMP failed; in particular, this may happen if there is not enough memory available for the process.

Action

Check the swap space or number of active processes.

OpenVMS: adjust the working set quota (Wsquo) and the page file quota (Pdflquo) accordingly.


SPAALL Space already allocated for 'string' in disk section 'string'
Explanation

Space is already allocated in the disk section for the displayed container or sequential file.

Action

None.


SPADBA Space already allocated for 'string' of database 'number' in disk section 'string'
Explanation

Space is already allocated in the disk section for the displayed container or SAM file of the displayed database.

Action

None.


SRTERR Sorting: internal error 'number' (in hex)/ 'number' (in hex)
Explanation

An internal error occurred in the sort process.

Action

Contact your nearest support center.


SRTFIL sort file too small
Explanation

The SORT file provided is too small.

Action

Provide a larger SORT file or assign a second one.


SRTWRK Sort file too small or work pool too large
Explanation

The SORT file provided is too small or the specified work pool is too large for the given SORT file.

Action

Modify the size of the SORT file and/or work pool accordingly.


SSAP same sub-/super-descriptor already present
Explanation

A sub-/superdescriptor with the same structure already exists.

Action

Correct the input line.


STAOVF counter overflow ('string') occurred, info will be reset
Explanation

All information related to the given counter is reset.

Action

None. Counter overflows can only be avoided by stopping and starting the database more frequently.


STARTERR Starting 'utility name' failed
Explanation

The given utility could not be started.

Action

This is an informational message. The reason why the utility could not be started is given in subsequent error messages.


STDLNG standard length may not be changed
Explanation

The length of a field defined with the FI option must not be changed.

Action

None.


STNOTPO Subsequent tapes not possible with input redirection
Explanation

An Adabas utility is using output to a tape device. The utility was called with input redirection and the tape device becomes full.

Action

Restart the utility but without input redirection.


STOP STOP in location 'string'
Explanation

A severe internal error occurred.

Action

Report the complete message text to your nearest support center.


STPnnn 'text'
Explanation

A severe internal error occurred.

Action

You should report the complete message code and text to your nearest support center if the message is not explained explicity below.


STP054 Network busy for more than one minute.
Explanation

If access to a file that is stored on a network device is not possible for more than one minute because of network problems, the nucleus or utility stops with this error message.

Action

Check your network.


STRMDI structure modified during display
Explanation

The data structure referred to by the running ADAOPR display function has been modified during display.

Action

Try the display function again.


SVAMIS Exactly two parameters are needed
Explanation

The specified parameter requires exactly two values.

Action

Correct the input.


SYNOMU System generated fields must not be multiple and CR or within periodic group
Explanation

Only fields that are not defined within a periodic group can be defined with the option SY. Multiple-value fields must not be defined with the option CR.

Action

Change the field definition accordingly.


SYNTAX syntax error
Explanation

Syntax error.

Action

Correct the input.


SYOPUSER System generated OPUSER field must have alpha format and length 8
Explanation

The option SY=OPUSER field requires format A and length 8.

Action

Change the field definition accordingly.


SYSESSIONID System generated SESSIONID field must have alpha format and option NV set
Explanation

The option SY=SESSIONID requires format alpha and option NV.

Action

Change the field definition accordingly.


SYSFLOCK system-file locked by utility
Explanation

A system file is locked by a utility and the nucleus is not permitted to start.

Action

Wait for the utility to terminate and then restart the nucleus.


SYSNOMATCH system file 'number' does not match to system file in DB
Explanation

An attempt was made to import a non-system file with a file number of a system file in the target database.

Action

Renumber the system file of the target database with ADADBM and rerun ADAORD.


SYTIME System generated TIME-Field must be defined with DT-option
Explanation

The option SY=TIME is only allowed for fields with DT option.

Action

Change the field definition accordingly.


TADEREQ Tape device required
Explanation

An Adabas utility is using output to a tape device. After prompting for another device, an invalid file name was entered.

Action

Enter a valid tape-device name.


TEMPTS given TEMP size too small
Explanation

Size of TEMP not sufficient.

Action

Provide larger TEMP.


TIMOT incompatible time environment or structure level mismatch
Explanation

a) The system times between the utility and nucleus were different. A nucleus and utilities which run online must have the same system time environment.

b) The utility opened a database with a different Adabas version.

Action

a) Check the TZ variable of the nucleus and the utility session.

b) Check the version of the requested database.


TMOVBREQ Too many ADAM overflow blocks requested, limit = 'number'
Explanation

The ADAM_OVERFLOW parameter was greater/equal the DSSIZE parameter in ADAFDU.

Action

Re-specify the ADAM_OVERFLOW parameter, using a value less than 'number'.


TMPFMT TEMP dataset formatted improperly
Explanation

The TEMP container file cannot be used by utility, the first RABN is in use.

Action

Check if another utility is using the current TEMP or use another TEMP file.


TONOT TO checkpoint name not found in block 'number'
Explanation

The TO checkpoint name was not found in the given block.

Action

Use the LIST = FULL function to print the checkpoint names with their associated block numbers and rerun ADAREC.


TOOSMALL New raw section is not big enough to contain all data
Explanation

The ADADEV RESIZE function tried to decrease the size of the disk section but there is not enough free space in the smaller section, since this would cause existing data to be outside the section boundaries.

Action

To successfully resize the section, the data at the end of the section has to be removed or moved nearer to the start of the section.


TPCO XA part of WORK could not be opened
Explanation

This error occurs if ADAPLP tries to display the XA part of WORK and

  • the session is run with OPTIONS=NOXA

  • the WORK is corrupted.

Action

If the current session is run with OPTIONS=XA, contact your nearest support center.


TTLV transition to this level not allowed
Explanation

The specified level number is not allowed in this context.

Action

Correct the input line.


TRTABE translation table access error (error 'number'), ignoring
Explanation

The translation table user exit (ADATRT) could not be opened. The session will run without using that user exit.

Action

Check the shared library pointed to by the environment variable ADATRT and the error number which indicates why the shared library cannot be used.


TZERR Invalid timezone specification
Explanation

The time zone specified was invalid. Refer to the documentation of the ADACMP/ADADCU TZ parameter for further information.

Action

Correct the TZ parameter.


UBFERR Database 'number' previous session aborted during buffer flush
Explanation

The Autorestart has detected that the previous nucleus session aborted during a buffer flush.

If the nucleus had been started with AR_CONFLICT=ABORT, the autorestart will abort, otherwise it will continue. If the nucleus abort occurred due to a power failure or an I/O error, it is possible that the database is in an inconsistent state. We recommend you to verify the database using ADAVFY and ADAINV VERIFY in this case.

Action

If the autorestart aborts due to AR_CONFLICT=ABORT, you can either:

  • redo the autorestart by setting AR_CONFLICT=CONTINUE (see the explanation above), or

  • restore and regenerate the database. This should only be done if the nucleus abort occurred during a power failure or an I/O error, and ADAINV or ADAVFY reports errors.


UCBGERR UCB not available
Explanation

The UCB is not available.

Action

Contact your nearest support center.


UCBNREM unable to remove UCB entry and/or write offline checkpoint
Explanation

The utility was not able in its final phase to write the necessary checkpoint and/or to clean up its UCB entry. Nevertheless the utility will terminate successfully.

However, the following risks exist:

  • One reason why the UCB entry could not be removed may be the the UCB entry had already been removed by ADADBM RESET UCB. In this case, the file was no longer protected against usage by other utilities or the nucleus. If another utility or the nucleus modified the file before the utility writing the UCBNREM message was finished, the file may be corrupted.

  • If the checkpoint could not be written, and you do a restore/regenerate later, you may forget to re-execute the utility because you don't see the checkpoint - this can result in a corrupted database.

Action

Verify with ADAVFY and ADAINV VERIFY that the file is still consistent if a parallel update of the file may have happened. Take care to ensure that the re-execution of the utility is not forgotten if a restore/regenerate is required later.


UEXABO aborted in userexit, input record: 'number'
Explanation

ADACMP aborted while a user-written user exit was active.

Action

Check the user-written routine.


UEXERR USEREXIT 'number' disabled, response returned: ^X 'number'
Explanation

An error response was returned by an Adabas nucleus user exit. The user exit is disabled but database operation continues.

Action

Check the response returned by the user exit. In order to enable the user exit again, shut down the nucleus and restart it with the USEREXIT option.


UEXMUE User exits 1 and 11 mutually exclusive
Explanation

It is not allowed to activate user exit 1 and user exit 11 for the same nucleus session.

Action

Start the nucleus session again with only one of user exit 1 and user exit 11 activated.


UEXSTA invalid user exit output status returned
Explanation

An invalid output status has been returned by the user exit.

Action

Return valid output status.


UIEXTOVL upper index's extent overflowed
Explanation

The file's upper index extent is too fragmented, the index remains inaccessible.

Action

Unload and refresh the file, allocate larger extents and add the unloaded data with ADAMUP.


ULDCORE Skipping corrupted record, block 'number', isn 'number'
Explanation

The DATA record with that ISN contains corrupted fields. This record will not be written to the unload output file.

Action

If the corrupted file is in the database it should be deleted and reloaded with ADAMUP. The missing data can be investigated by dumping the DATA RABN with the corrupted record. Or run ADAULD with the SHORT option and then decompress with ADADCU. The corrupted record will be filtered out to the DCUERR file.


ULDCORR Skipping DATA block 'number' with corrupted record
Explanation

During the unload a corrupted DATA block with RABN 'number' is deleted. The unload will skip those blocks and continue.

Action

Because there were corruptions the unloaded file should be decompressed to find more inconsistencies. If the corrupted file is in the database it should be deleted and reloaded with ADAMUP. The missing data can be investigated by dumping the corrupted DATA RABN.


ULDLOB ADABAS nucleus not active - file with LOBS cannot be unloaded
Explanation

Unloading a file with LOB data requires an active Adabas nucleus.

Action

Start the nucleus and try again.


ULDSEQ ADABAS nucleus not active - only physical sequence supported
Explanation

Processing a file in descriptor or ISN sequence requires the Adabas nucleus to be active.

Action

Start the Adabas nucleus.


UNEFILD Unexpected file 'file-name' detected
Explanation

When opening an Adabas file, an unexpected type was detected (e.g. a DTA file was expected, but a DVT file was detected).

If the file name displayed begins with 'UTI', you must replace 'UTI' with the last 3 characters of the utility name in order to get the real (logical) file name. For example, if the file name displayed in ADADCU is UTIDTA, then the file DCUDTA is meant.

Action

Check the assignment of the environment variables.


UNIQUEFILE unique file specification required
Explanation

The parameter given requires the specification of a single file number.

Action

Specify a single file number.


UNPRIV utility has no privilege for access database 'number'
Explanation

The utility tried to use a database which cannot be accessed because of architectural differences. For example the utilities cannot access a database which runs on an IBM mainframe.

Action

Check the database you want to use and check NET-WORK if that database is active on a remote node.


UNPRRD Readonly database, utility not permitted to run
Explanation

The specified database is a read-only database. The utility function you requested is not allowed for a read-only database.


UNPRUN utility not permitted to run
Explanation

This utility is currently not permitted to run.

Action

Wait until the database is available again.


UNXEOF "file": Unexpected end of file
Explanation

The block size of the last block found on the file is larger than the number of bytes that follow. Either the file has a different record structure than assumed, or the file is incomplete.

Action

You must be aware that the file is not correct, however it may be possible to use the data in the file before the position where the error occurs. For example, if a CMPIN file was truncated, you can compress the records that are still available on the file.


UNXIOERR An unexpected I/O error has occurred
Explanation

The Adabas nucleus or utility must be aborted because an I/O error occurred.

Action

Check your file system, your storage devices and the network.


UNXNRSP Unexpected ADABAS nucleus response code 'number'
Explanation

An Adabas nucleus call received an unexpected nucleus response code.

Action

Check the meaning of the nucleus response code. If the explanation you find there does not help, contact your nearest support center.


UNXRC Function 'name': Unexpected return value: 'number'
Explanation

Error in the Adabas code: A function returned an unexpected return value.

Action

Report the error to your nearest support center so that the Adabas development team can fix the error.


UQDE UQ is valid only with DE
Explanation

The option UQ can be specified only for descriptors.

Action

Correct the input line.


UTIENA OPTIONS=UTILITIES_ONLY enabled in nucleus by ADAREC
Explanation

The utilities mode is enabled in the nucleus. All non-utility calls will be rejected.

Action

Reset the mode to OPTIONS=LOCAL_UTILITIES with the utility ADAOPR.


VALEX exactly 3 value(s) required
Explanation

The number of elements in a value list was incorrect.

Action

Enter a list of values with the correct number of elements.


VALLOW value has to be greater-equal 'number'
Explanation

The given value is too small.

Action

Enter a value not smaller than the displayed minimum.


VALMAX only 'number' value(s) allowed
Explanation

The number of elements in a value list was too large.

Action

Enter a list of values with a number of elements which is not larger than the number displayed in the error message.


VALUP value has to be less-equal 'number'
Explanation

The specified value is too large.

Action

Enter a value not larger than the value displayed in the error message.


VFADAM ADAM 'ISN|Key' error: ISN 'number' in RABN 'number', expected 'number'
Explanation

An error was detected while accessing an ADAM file.

Action

Unload/export the file in physical sequence and load/import it again.


VFERRCNT Inconsistencies found by 'number' verifications
Explanation

This is a summary message of adavfy, indicating that the checked databases or files contain errors.

Action

Look at the displayed error messages and act accordingly.


VFYBLK Invalid number of 'type' blocks ('number found'/'number expected')
Explanation

ADAVFY detected a discrepancy between the actual count for AC/UI/NI/DS blocks and the count held in the control structures. Some errors can be corrected.

Action

See subsequent messages.


VFYERR Verification error on disk section 'string'
Explanation

The consistency check of the disk-section management area failed.

Action

See the subsequent error message.


WMFEXP Format type W is not supported to export for mainframe
Explanation

If ADASCR is used to export security-by-value definitions from an open systems platform to a mainframe platform, this warning occurs if the search buffer of an access or an update criterion or both contains W formatted entries. The W format is not supported on mainframe platforms in security-by-value definitions. If only one defined access or update criterion contains W formatted entries, the other one will be exported; if both contain W formatted entries, the defined security-by-value definition will be ignored.

Action

If the rejected security-by-value criterion also contains other fields, manually add a new security-by-value criterion that contains these other fields to the export file so that these other fields can be checked. The checks for the W field must be made in the application on the mainframe platform.


WORK2TSM given WORK-Size too small, at least 'number' blocks required
Explanation

The given size of the WORK data set is too small to run the nucleus.

Action

Create a larger WORK data set using ADADBM's NEWWORK function with at least 'number' blocks.


WONOP WORK could not be opened
Explanation

The WORK file could not be opened.

Action

Enable WORK open for the nucleus.


WORKSET Working set too small
Explanation

The process working set is too small to satisfy all memory requirements.

Action

Contact your nearest support center.


WPSIZE work pool too small
Explanation

The LWP parameter is too small to use the complete SORT file and the usable part of the SORT file has overflowed.

Action

Increase the LWP parameter.


WRONGIPT wrong input file assigned
Explanation

The input file assigned is not the one expected by the utility.

Action

Check the assignments.


WRFAIL Writing to file ‘name’ failed: ‘reason’
Explanation

Write failed, the reason is given by the operating system.

Action

Check the error reason and fix it.


WSERR dataset 'string', write error
Explanation

A write error occurred on this data set. The reason is given in a preceding error message.

Action

See the subsequent error message.


XAERRRES XA error 'string' from record 'number' in block 'number' in PLOG 'number'
Explanation

While processing the protection log, an executed command resulted in a nucleus XA error.

Action

Examine the block at the record number associated with the error response, e.g. a file may not have been restored, with ADABCK, with the correct dump. This results in the file being in a state different to that when the original command was executed.


XALIC Parameter XA restricted by licensing, original XA=set, now XA=disabled
Explanation

The license does not allow you to run a database with disributed transaction processing, so the XA option is reset.

Action

To avoid this message, restart the database without the XA option or upgrade your license.


XARMERR XA_RMERR signalled ('number')
Explanation

An application using the XA protocol has received an XA_RMERR response code.

Action

Please contact your nearest support center.


ZERISN Zero ISN found in record, RABN 'number', rp='hex-number'
Explanation

An illegal ISN number 0 was found in a DS RABN.

Action

Unload/export the file in physical sequence and load/import it again.