| The messages listed in this section are common to all utility routines. Error messages relating to general utilities have the same format for all the utility routines. These messages indicate the cause of the error and the execution module of the utility routine and have the following format: +++++ ERROR 00xx: ERROR AT ‚module‘ IN ‚operation‘
RETURN CODE: retcode
(DMS ERROR : dmscode)
|
module
operation
retcode
dmscode | Execution module of the utility routine
General utility operation
Error situation
Return value of a DMS macro |
|
ALOG FILE CREATED ACCORDING TO DEFAULT-SUPPORT
|
| Meaning
Self-explanatory. |
BALTER/BPRIVACY IS NECESSARY
|
| Meaning
The BCHANGE utility routine has completed; it is now necessary to run BALTER or BPRIVACY. |
BUFFERSIZE n MBYTE ASSUMED
|
| Meaning
A buffer size of n Mbytes was assumed for creation of the buffer pool. |
DIFFERENCE OF AK0 AND AKN IN REALM realmname
|
| Meaning
Act-key-0 and act-key-N of the realm indicated differ, i.e. the database is not consistent. |
DIFFERENCE OF BACKUP DATA BETWEEN REALM realmname AND CONSISTENCY RECORD
|
| Meaning
The indicated realm and the consistency record in DBDIR differ, i.e. the database is not consistent. |
DIFFERENCE OF CREATION DATA BETWEEN REALM realmname AND DBDIR
|
| Meaning
The indicated realm and database directory differ, i.e. the database is not consistent. |
DIFFERENCE OF VERSION BETWEEN REALM realmname AND VERSION RECORD
|
| Meaning
The indicated realm and the version record in DBDIR differ, i.e. the database is not consistent. |
EXCLUSIVE UTILITY OCCURRED IN REALM realmname
|
| Meaning
EXCL_UTILITY occurred in the indicated realm, i.e. the database is not consistent, it has just been modified by a utility routine. |
OCCURRED IN module AT operation
|
| Meaning
More details on an error message. |
REALM NAME : realmname
|
| Meaning
The message relates to the indicated realm. |
SYSTEM_BREAK OCCURRED IN REALM realmname
|
| Meaning
SYSTEM_BREAK occurred in the indicated realm, i.e. the database is not consistent. |
TRANSACTION CONTINUES WITHOUT LOGGING
|
| Meaning
An error occurred during logging. The utility routine attempts to continue to the end without logging. Response
Depends on the previous error message. |
TRANSACTION FOR ORIGINAL DB NORMALLY ENDED
|
| Meaning
The transaction updating the database was terminated normally. |
UTILITY ENDS ABNORMALLY ONLY DUE TO PREVIOUS LOGGING ERROR
|
| Meaning
The utility routine terminated abnormally due to a previous logging error. Response
Depends on the previous error (see information pertaining to the error). |
0006
| ERROR AT module IN operation
|
0006
| WARNING AT module IN operation
|
0006
| At module IN operation |
| Meaning
Error in module module or warning or note on module while executing operation. The next message contains a more detailed explanation of the 0006 messages. One of the following messages may be issued: |
AMBIGUOUS FILE NAME
|
| Meaning
The file name is not unique. Response
Make sure the file name is unique. |
BGSIA IS MISSING
|
| Meaning
BGSIA must be run before processing can continue. |
BLOCK INDEX NOT FOUND
|
| Meaning
No page index entry was found for a record in the database page. Response
Generate error documentation. |
BLOCK NOT EXISTING
|
| Meaning
The requested database page does not exist. Response
Generate error documentation. |
BLOCK NOT READ
|
| Meaning
The database page was not read. Response
Generate error documentation. |
BUFFERSIZE OUT OF RANGE
|
| Meaning
The buffer size specified is either too big or too small and has been set to STD. Response
Observe limitations the next time the program is run. |
COMMAND ERROR
|
| Meaning
A certain order for calling general utilities has not been observed. Response
Generate error documentation. |
CKPT_LEAVE_TIME IN DBDIR IS GREATER THAN UNIVERSAL TIME
|
| Meaning
Before the current utility routine run there was probably another run (utility routine or DBH) on the database with a different universal time setting. This previous run led to a CKPT_LEAVE_TIME time stamp in the AK0 of the DBDIR which is greater than the current time stamp obtained by the computer (UNIVERSAL TIME). The current run terminates before SYSTEM_BREAK is set. |
DATABASE IS EXCLUSIVE LOCKED
|
| Meaning
The database is locked. Response
Avoid concurrent access to the database. |
DATABASE NOT OPENED
|
| Meaning
The database could not be opened. Response
Analyze subsequent messages. |
DATABASE-KEY ERROR
|
| Meaning
The desired database key could not be found, possibly because no SIA/SSIA is present. Response
Generate error documentation. |
DBTT1 IS FULL
|
| Response
Increase the population of the record type SSIA-RECORD. |
DMS ERROR , DMS CODE : dmscode
|
| Meaning
Error during file processing. Response
Analyze dmscode. |
ERROR IN SORTU
|
| Meaning
Error in SORT. Response
Generate error documentation. |
ERROR ON SVC
|
| Meaning
Error during an SVC call. Response
Analyze subsequent messages. |
FILE ALREADY OPENED
|
| Meaning
The file may already have been opened with other attributes. Response
Generate error documentation. |
FILE NOT OPENED
|
| Response
Analyze subsequent messages. |
FIXING ERROR
|
| Meaning
Error occurred when processing a database page. Response
Generate error documentation. |
FORBIDDEN CALL
|
| Meaning
The desired general utility is not permitted. Response
Generate error documentation. |
FUNCTION NOT SUPPORTED
|
| Meaning
The desired general utility function has not been implemented in the current version or has been supplied with incorrect values. Response
Generate error documentation. |
INCONSISTENT ACTKEY
|
| Meaning
The requested act-key differs from the one actually received. Response
Generate error documentation. |
INCORRECT OR NO DATABASE-NAME SPECIFIED
|
| Meaning
The database name is missing or incorrect. Response
Enter a valid database name. |
IO ERROR ON ACT-KEY-0
|
| Meaning
Error while accessing act-key-0 of a database realm. Response
Generate error documentation. |
IO ERROR ON DATABASE
|
| Meaning
Error while accessing the database. Response
Generate error documentation. |
IO ERROR ON LOG FILE
|
| Meaning
Error while accessing the ALOG file. Response
Analyze subsequent messages. |
JOB VARIABLE NOT AVAILABLE
|
| Meaning
The JV cannot be accessed. |
LINK NOT IN TASK FILE TABLE
|
| Meaning
The link name does not exist. Response
Issue the SET-FILE-LINK command. |
LOG FILE EOF
|
| Meaning
The end of the ALOG file was reached. |
LOG FILE IS NOT AVAILABLE
|
| Meaning
The ALOG file the ALOG file cannot be accessed. Response
Analyze subsequent messages. |
LOG FILE IS ON TAPE
|
| Meaning
The ALOG file is not located on hard disk. Response
Transfer the ALOG file from tape to disk. |
NO ACCESS PERMISSION
|
| Meaning
The database may not be accessed because the program is not permitted in the current database state the program is attempting to access the database in an illegal access mode the database and program versions are incompatible the access mode of the program is incompatible with the open database the assigned file is not present
Response
Check the compatibility of the database (state) and the utility routine (version). |
NO ADDITIONAL MEMORY AVAILABLE
|
| Meaning
Memory bottleneck. Response
Analyze subsequent messages. |
NO AUTOMATIC EXTENSION FOR FPA
|
| Meaning
Error during automatic extension of a realm. Response
Remove the cause which is preventing the file from being extended; if necessary, execute utility routine again. |
NO CODING DONE
|
| Meaning
Error while coding the validation date. Response
Generate error documentation. |
NO DECODING DONE
|
| Meaning
Error while decoding the validation date. Response
Generate error documentation. |
NO FREE BUFFER AVAILABLE
|
| Meaning
The internal buffer is full. Response
Increase the buffer specification for program execution. |
NO SPACE FOR LOG BUFFER AVAILABLE
|
| Meaning
The buffer required for logging could not be created. Response
Reduce the requested buffer size. |
NO SPANNED RECORD
|
| Meaning
The page index for a spanned record contains an incorrect record type. Response
Generate error documentation. |
NO STCK TIME
|
| Meaning
The STCK call on the system did not return a value. Response
Inform the system administrator, compile error documentation. |
NOT ALL REALMS OPENED
|
| Response
Check whether all realms must be opened for the desired operation. |
NOT ALL TRANSACTIONS CLOSED
|
| Meaning
Logging should be deactivated although transactions are still open. Response
Generate error documentation. |
NOT ENOUGH EMPTY OR EMPTY CONTIGUOUS PAGES
|
| Meaning
The realm cannot provide the space required. Response
Enlarge the realm. |
PARAMETER ERROR
|
| Meaning
Error while supplying the internal interface to the operation indicated in the previous message with values. |
| Response
Generate error documentation. |
PARAMETER MISSING
|
| Meaning
Not all the transfer parameters in the internal interface were supplied with values. Response
Generate error documentation. |
PROGRAM IS NOT USED BY ADMINISTRATOR
|
| Meaning
The utility routine is not running under the database user ID. Response
Run the utility routine under the database user ID. |
RELEASE MEMORY ERROR
|
| Meaning
Error while releasing buffers. Response
Generate error documentation. |
REQUEST MEMORY ERROR
|
| Meaning
Error occurred while creating buffers. Response
If there is insufficient storage space, reduce the buffer sized requested. |
SECOLTP-PRIVILEGE DON’T ALLOW SHAREABLE FILE filename
|
| Meaning
The indicated file is shareable under the SECOLTP user ID. Response
Set the file to SHARE=NO. |
SECOND SCAN
|
| Meaning
The search for available space in the database was not successful until the second scan. Response
Enlarge the file if necessary, especially if contiguous free space is required. |
SOME RESOURCES NOT AVAILABLE
|
| Meaning
Some resources required by the general utility function could not be initialized. |
| Response
Generate error documentation. |
SPANNED RECORD LENGTH DIFFERENCE
|
| Meaning
The length of the spanned record to be written back has been changed. Response
Generate error documentation. |
SPANNED RECORD NAME NOT FOUND
|
| Meaning
A spanned record with the indicated name cannot be found. |
SUMMER SEASON ASSUMED
|
| Meaning
Daylight saving time is assumed for the time stamp. |
SYSTEM BREAK PENDING
|
| Meaning
The consistency point for a database that is already inconsistent is to be left
(set SYSTEM BREAK). Response
Make the database consistent. |
SYSTEM ERROR
|
| Meaning
Fatal error |
TOO MANY FILES OPENED
|
| Meaning
More than 255 files are to be opened. Response
Reduce the number of files to be opened. |
UNALLOWED FREE
|
| Meaning
Error while releasing a database page. Response
Generate error documentation. |
WRONG OR MISSING LOGFILE
|
| Meaning
The ALOG file is incorrect or does not exist. |
| Response
Make the correct ALOG file available or create the ALOG file with BMEND. |
WRONG RECORD LENGTH IN ALOG FILE
|
| Meaning
The length of a record in the ALOG file is incorrect. Response
Generate error documentation. |
0007
| INTERNAL ERROR IN utility AT internal-error
|
| Meaning
Internal error in the indicated utility at the internal-error location. Response
Generate error documentation. |
0008
| MODIFICATION OF JOB SWITCH NOT POSSIBLE
|
| Meaning
A job switch cannot be set. Response
Generate error documentation. |
0009
| SCRATCHFILE filename MUST HAVE BLKSIZE =(STD,nr)
|
| Meaning
The scratch file specified by the user has a BLKSIZE that does not match the database
page size. Response
Set the BLKSIZE file attribute correctly when creating the file. |
0012
| UDS-DBH RETURNS WITH DATABASE-STATUS ’dbstatus’
|
| Meaning
Error in the linked-in utility routines due to a DML statement that has not been executed. Response
Remove error situation or compile error documentation, if necessary. |
0015
| AMBIGUOUS FILE WITHIN USERID
|
| Meaning
USD/SQL file exists under several catalog identifiers (:catid:) within one userid. Response
Make sure that the UDS/SQL file exists only once within the userid. |
0017
| FILE filename ALREADY EXISTING
|
| Meaning
An attempt was made to create a database (BCREATE), but a DBDIR already exists. Response
First delete the file. |
0019
| WRONG PARAMETER IN modulename
|
| Meaning
The specified module was referenced with invalid parameters. Response
Generate error documentation. |
0020
| INVALID CHARACTER char READ ON PARAMETER CARD
|
| Meaning
The character specified is invalid. Response
Enter valid character. |
0021
| CHARACTER CONSTANT OVERFLOW
|
| Meaning
Too many characters in a literal (>63). Response
Limit literal to a maximum of 63 characters. |
0022
| NONCONVERTABLE CHARACTER char
|
| Meaning
Character cannot be interpreted. Response
Enter correct character. |
0023
| INTEGER CONSTANT OVERFLOW
|
| Meaning
The number is too large (>= 214748364). Response
Limit character to 214748363, maximum. |
0025
| ODD NUMBER OF HALF BYTES FOR A HEX LITERAL
|
| Meaning
The hexadecimal literal specified by the user contains an uneven number of hexadecimal
characters. |
| Response
Reenter the hexadecimal literal with an even number of hexadecimal characters e.g. by
adding a zero. |
0027
| FILE WITH LINK-NAME = ’SCRTCH1’ NOT ERASED
|
| Meaning
The file with the link name specified could not be deleted. Response
Delete the file with the appropriate BS2000 command. |
0042
| NO USER-HASH-ROUTINES LOADED
|
| Response
None. |
0043
| USER-HASH-ROUTINE NOT LOADED: hashname
|
| Meaning
The user hash routine specified by hashname could not be loaded. Response
Enter hash routine hashname in the hashlib. |
0044
| WRONG AMODE OF THE USER-HASH-ROUTINE hashname
|
| Meaning
The user hash routine was compiled with an incorrect AMODE. Response
Adjust the AMODE in the source and recompile. |
0045
| ERROR IN UDS PUBSET DECLARATION: reason JV CONCERNED IS: jv-name
|
| Meaning
In the syntax check of the UDS/SQL pubset declaration (separation into catid groups) an error which is described in detail in reason was detected in the jv-name job variable:
ELEMENT TOO LONG: A catid group exceeds the maximum length of 26 characters. TOO MANY ELEMENTS: More than 100 catid groups were defined. EXCLUDE ELEMENT NOT ALONE: The specification of a catid group which is to be excluded has been combined with other catid groups. The utility routine is terminated abnormally. Response
Correct the UDS/SQL pubset declaration. |
0048
| ERROR ACCESSING JV USING JV-LINKNAME jv-linkname
|
| Meaning
In the syntax check of the UDS/SQL pubset declaration an error was detected when checking whether an assignment exists for the JV link name specified in jv-linkname.
A subsequent message will provide further information relating to diagnosis.
The utility routine is terminated abnormally. |
| Response
Correct the assignment for the JV link name or property of the JV. |
0049
| ERROR ACCESSING JV jv-name
|
| Meaning
In the syntax check of the UDS/SQL pubset declaration it was not possible to access the assigned UDS-PUBSET-JV jv-name, for example because the JV does not exist (or has a length of 0) or is not accessible.
A subsequent message will provide further information relating to diagnosis.
The utility routine is terminated abnormally. Response
Correct the assignment for the JV link name or property of the JV. |
0050
| CLOSE OF CSV OUTPUT FILE FAILED.
|
| Meaning
The CSV output file could not be closed without error. Response
Check and, if required, correct the file properties. |
0051
| OPEN OF CSV OUTPUT FILE FAILED.
|
| Meaning
The CSV output file could not be opened without error. Response
Check and, if required, correct the file properties. |
0052
| CSV OUTPUT STOPPED BECAUSE OF PUT FAILURE.
|
| Meaning
The CSV output file could not be written to without error. No further attempts to write to it
are made in this program run. Response
Check and, if required, correct the file properties. |
0053
| DATABASE-DIRECTORY DEFECT
|
| Meaning
The file DBDIR has been destroyed or cannot be used. Response
Reconstruct the DBDIR file from a backup copy (by applying ALOG files if required). |
0054
| BLKSIZE DIFFERS FROM DATABASE-SIZE
|
| Meaning
DBDIR does not have a 2-Kbyte, 4-Kbyte or 8-Kbyte size. The BLKSIZE of the DBDIR does not match the database page size. |
| Response
Create the DBDIR file appropriately or check if the wrong DBDIR file was used. |
0055
| ERROR IN UDS PUBSET DECLARATION: CATID(S) REJECTED BY FSTAT DMS-CODE dms-code
RECEIVED FROM FSTAT USING CATID catid-group JV CONCERNED IS: jv-name
|
| Meaning
An error was detected in the syntax check of the UDS/SQL pubset declaration
(trial FSTAT for a test file name with each catid group).
dms-code is the DMS-CODE of the FSTAT.
catid-group is the catid group causing the error.
jv-name is the name of the JV.
UDS-PUBSET-DECLARATION-TEST-NAME is used as the test file name.
The utility routine is terminated abnormally. Response
Correct the UDS/SQL pubset declaration. |
0063
| VERSION DIFFERENCE BETWEEN UTILITY AND LOAD LIBRARY
|
| Meaning
The utility and the library from which the UDS/SQL modules are loaded are from different versions. |
0064
| SUPPLY OF DATABASE JV FAILED action
|
| Meaning
The DB job variable could not be processed without error in the action action. No further attempt to process is made in this program run. Response
Check and, if required, correct the properties of the DB job variable. |
0065
| FILE filename NOT FOUND, POSSIBLY OUTSIDE SCOPE OF UDS PUBSET DECLARATION
|
| Meaning
The filename file was not found by an FSTAT taking into account any UDS/SQL pubset declaration which may exist. The file was possibly created outside the pubset space of the UDS/SQL pubset declaration.
The utility routine is terminated abnormally or, in the case of an ALOG file, the utility routine is continued without updating ALOG logging. Response
Check whether the user specifications for the filename file are incompatible with the UDS/SQL pubset declaration; if required, correct the specifications or the UDS/SQL pubset declaration.
In the case of an ALOG file, remove the logging gap. |
0066
| PART OF THE LINK NAMES CANNOT BE RELEASED
Meaning Some link names for utility work files are still present in TFT table
Response Delete TFT entries for unused link names with REMOVE-FILE-LINK command |
0073
| AUTOMATIC EXTENSION BY number DATABASE-PAGES NOT POSSIBLE FOR REALM realmname
|
| Meaning
The attempt to extend the realmname realm automatically by the specified number of database pages failed. Response
Ask the system administrator to increase the SPACE limit or delete files which are no longer needed. |
0074
| REALM realmname HAS BEEN DYNAMICALLY EXTENDED BY number
|
| Meaning
The realmname realm has automatically been extended by the specified number of database pages. The new realm size will be displayed in a subsequent message. Response
Check the realm size and extend the specified realm again later, if necessary. |
0081
| NO CREATION OF ALOG FILE POSSIBLE
|
| Response
Remove the cause indicated by other messages or warnings. |
0082
| NO ACCESS TO OLD ALOG FILE POSSIBLE
|
| Response
None. |
0083
| ALOG FILE CREATED ACCORDING TO RESERVE-SUPPORT
|
| Response
Enter new volumes using the START-LOG command provided by BMEND. |
0084
| NEW ALOG FILE filename CREATED ACCORDING TO DEFAULT- OR RESERVE-SUPPORT
SUBSEQUENTLY NOT FOUND, POSSIBLY OUTSIDE SCOPE OF UDS PUBSET DECLARATION
|
| Meaning
The new ALOG file filename was created in accordance with the specification in the BMEND statement START-LOG for DEFAULT-SUPPORT or RESERVE-SUPPORT, but it was then not found by an FSTAT taking into account any UDS/SQL pubset declaration which may exist.
The file was probably created outside the pubset space of the UDS/SQL pubset declaration.
As it is unusable, it is deleted again. If this problem is also encountered with RESERVE-SUPPORT, depending on the reason for creating the new ALOG file the utility routine will be continued without updating ALOG logging or terminated abnormally. Response
Check whether the specifications of the BMEND statement START-LOG for DEFAULT-SUPPORT or RESERVE-SUPPORT are compatible with the UDS/SQL pubset declaration.
If necessary, correct the specifications or the UDS/SQL pubset declaration.
If necessary, remove any logging gap which exists. |
0091
| FSTAT-ERROR AT filename
|
| Meaning
FSTAT error involving the indicated file. Response
Analyze subsequent messages. |
0092
| THE FILE WITH LINK-NAME=linkname HAS A WRONG fileattribute
|
| Meaning
The file created by the user has an invalid format. Response
Omit the RECORD-FORMAT entries in the SET-FILE-LINK command. |
0097
| ERROR AT FUNCTION sam-operation
|
| DMS-CODE : dmscode
|
| FILE IN PROCESS: filename
|
| Meaning
sam-operation is the module entry in which the error occurred. Response
Respond according to dmscode. |
0098
| RESET SYSDTA IMPOSSIBLE, SYSDTA REMAINS ON OLD STATUS
|
| Meaning
SYSDTA cannot be reset to the old status. Response
Inform system administrator. |
0099
| SYSDTA-CHANGE NOT POSSIBLE
FILE=filename
|
| Meaning Assignment of SYSDTA to the indicated file was not possible. Response
Respond according to mnote for the SYSFL macro. |
5001
| UTILITY DOESN’T RUN WITH THIS VERSION (version) OF THE OPERATING SYSTEM
|
| Meaning
The utility routine cannot run with the indicated version of the operating system. Response
Change the operating system or UDS/SQL version. |
5002
| SDF - SYSTEM ERROR WITH SDF RETURN CODE retcode
|
| Meaning
SDF error with the indicated return code. |
| Response
Analyze the return code using the SDF manual. |
5003
| SDF - SYNTAX FILE DEFECT: internal-error
|
| Meaning
The SDF syntax file is not compatible with the program. Response
Update the SDF syntax file. |
5004
| PROGRAM utility NOT IN SYNTAX FILE OR SDF NOT LOADED
|
| Meaning
The indicated utility routine is not in the assigned SDF syntax file or SDF is not loaded. Response
Assign the correct SDF syntax file or load SDF, as appropriate. |
5005
| PLEASE CORRECT THE INCORRECT OPERAND(S)
|
| Meaning
Input could not be analyzed. Response
Correct input. |
5006
| ERROR IN STATEMENT DETECTED BY SDF
|
| Meaning
SDF has reported an error, and the spin-off has branched to //END or //STEP. Response
See SDF error message. |
5009
| FORBIDDEN PRINT CONTROL CHARACTER char IN SYSLST-LINE:
|
| Meaning
The indicated line contains an illegal control character char. Response
Generate error documentation. |
5011
| UTILITY DOESN'T RUN WITH THIS DATABASE-LAYOUT-VERSION = version
|
| Meaning
The utility routine cannot process the database with database version version that was specified by the user. Response
Choose a suitable database version or utility routine version. |
5024
| KEY LIST NOT INITIALIZED
|
| Meaning
The list of symbols for decoding the parameters has not been initialized; (utility routine error). |
| Response
Generate diagnostic documentation and write error report.
|
| Return codes of the utility routines Return codes are part of an error message if the utility routine receiving the return code cannot correct the error.
If the cause of the error cannot be determined with the aid of the return code, starting of a retrieving UDS/SQL utility routine (e.g. BSTATUS) or DPAGE should be attempted. In the event of a read error the page in question as well as its environment should be printed and the act-key checked. The return code consists of a 4-byte item, where the first 2 bytes indicate its origin. 0000 NO ERROR
0002 database ACC
0003 CHAIN ACC
0005 SCRATCH
0006 SORT
0106 SORT
|
The second 2 bytes in the messages indicate the hexadecimal value, and the following number shows the decimal value of the return code. In the case of some error messages, return codes are output without a breakdown. This is not required due to the accompanying plaintext. |
00020001
| 1 NO INIT
|
| Meaning
The I/O routines were not yet initialized or they are initialized for the second time
(utility routine error). |
00020003
| 3 READ ERROR
|
| Meaning
The act-key of the page that was read does not match the (explicitly or implicitly) transferred buffer (error in the database or utility routine). |
0002000B
| 11 PAGNR TOO BIG
|
| Meaning
Reading or writing would exceed end of file (or file end + secondary allocation);
(DMS-CODE = ..22 or 0C77) |
0002000D
| 13 PAMLIMIT
|
| Meaning
Because the storage space allocation in the JOIN entry of the userid is insufficient, the size of the file cannot be increased; (DMS-CODE = ..4D). |
0002000F
| 15 AMBIGUOUS FILENAME
|
| Meaning
The file name is not unique. |
00020013
| 19 OTHER ERROR
|
| Meaning
Usually an I/O error (further information from the DMS code output) or invalid suffix to the database name with configurationuser ID. |
00030001
| 1 NO REC
|
| Meaning
A spanned record to be read/deleted does not exist. |
00050001
| 1 NUM OF FIL ERR
|
| Meaning
Input parameter NR OF SUBFILES incorrect. Must be a value between 1 and 4. |
00050002
| 2 FILE NUMB ERR
|
| Meaning
Input parameter SUBFILE NUMBER incorrect. Must be a value between 1 and 4. |
00050013
| 19 OTHER ERROR
|
| Meaning
The page size of the SCRATCH file is not suitable. |
00060003
| 3 READ ERROR
|
| Meaning
The act-key of the page read in does not match the one transferred (explicitly or in the transferred buffer). |
0006000D
| 13 PAMLIMIT
|
| Meaning
A file cannot be enlarged due to insufficient storage space allocation in the JOIN entry of the userid; (DMS-CODE = ..4D). |
00060013
| 19 OTHER ERROR
|
| Meaning
Usually an I/O error (for more information cf. DMS code output) or invalid suffix to the database name with configurationuser ID. |
00060015
| 21 ILLEGAL CALL
|
| Meaning
Invalid sort parameter input (utility routine error). |
0006001E
| 30 INSUFFICIENT DISC MEMORY
|
| Meaning
Insufficient disk space. |
0006srt
|
|
| Meaning
srt sort error code (see “SORT (BS2000)“ manual). |
