3901
| USER IS NOT ADMINISTRATOR, THEN ONLY THE “COPY ” STATEMENT IS ALLOWED
Relevant statement: OPEN-DATABASE or
/SET-FILE-LINK command with LINK-NAME=DATABASE
Meaning The message informs the user that only “COPY” is allowed as subsequent statement as the userid of the BOUTLOAD user is not identical to that of the database administrator. Response Enter “COPY” or “END” statement. |
3902
| AFTER “RECORD-NAME =*ALL ” ONLY THE “END ” STATEMENT IS ALLOWED
Relevant statement: COPY or REMOVE or EXPORT with RECORD-NAME =*ALL Meaning The message informs the user that only “END” is allowed as subsequent statement because the current statement contains “RECORD-NAME = *ALL”, thus this statement must be the only executable statement. Response Enter “END” statement. |
3903
| AFTER “REALM-NAME=realmname ” ONLY THE “END ” STATEMENT IS ALLOWED
Relevant statement: COPY with REALM-NAME=realmname Meaning The message informs the user that only “END” is allowed as subsequent statement because the current statement contains “REALM-NAME=realmname”, thus this statement must be the only executable statement. Response Enter “END” statement. |
3910
| NO EXECUTABLE STATEMENT POSSIBLE
Meaning No COPY-RECORD, EXPORT-RECORD or REMOVE-RECORD statement is permitted. The existing database is inconsistent and cannot be processed, since the database directory is incompatible with its administration data. Response Make the database consistent or address it under the database user ID. |
3911
| NO CORRECT EXECUTABLE STATEMENT SPECIFIED
Relevant statement: COPY or REMOVE or EXPORT Meaning Entry of any of these statements was incorrect. Response Restart BOUTLOAD and enter correct executable statements. |
3921
| REALM realmname NOT FOUND IN THE SCHEMA
Relevant statement: COPY with REALM-NAME=realmname Meaning The specified realm does not exist in the schema of the opened database. Response Check schema (using a BPSIA REPORT if available), correct realm name. |
3922
| REALM realmname CONTAINS NO RECORDS
Relevant statement: COPY with REALM-NAME=realmname Meaning The specified realm contains no record types according to the definition in the schema. Response Check schema (using a BPSIA REPORT if available), correct realm name. |
3923
| RECORD recordname NOT FOUND IN THE SCHEMA
Relevant statement: COPY with RECORD-NAME=recordname Meaning The specified record type does not exist in the schema of the opened database. Response Check schema (using a BPSIA REPORT if available), correct record name. |
3924
| RECORD recordname NOT FOUND IN THE SPECIFIED REALM
Relevant statement: COPY with RECORD-NAME=recordname and REALM-NAME=realmname Meaning The specified realm is not contained in the WITHIN clause (DDL) of the specified record type. Response Check schema (using a BPSIA REPORT if available), correct realm or record name. |
3925
| “RECORD-NAME=*ALL ” IS NOT ALLOWED AT THIS TIME Relevant statement: COPY or REMOVE or EXPORT with RECORD-NAME= *ALL Meaning The indicated statement has not been entered as the first executable statement; it can thus not be the only statement to be executed (as it requires). The statement is ignored. Response Enter executable statements with “RECORD-NAME=recordname” only or “END”. |
3926
| ONLY “REALM=NAME=*ALL ” ALLOWED AT THIS TIME
Relevant statement: COPY with REALM-NAME=realmname Meaning The indicated statement has not been entered as the first executable statement; it can thus not be the only statement to be executed (as it requires). The statement is ignored. Response Enter executable statements with “REALM-NAME=*ALL” only or “END”. |
3930
| THERE ARE NO OCCURRENCES PRESENT FOR RECORD recordname
OUTPUT FILE filename IS EMPTY
Relevant statement: COPY or EXPORT Meaning No records of the specified record type recordname exist in the database. The assigned output file is empty. BOUTLOAD deletes any empty output files which it has created internally. Response Delete any other empty output files which have been made available or prevent them from being processed. |
3931
| SYSTEM BREAK OCCURRED FOR DBDIR -
ONLY ‚REMOVE *ALL’ OR ‚COPY...SET-INFO=NO‘ POSSIBLE
Meaning The database is inconsistent. Response Specify one of the two indicated statements or reset the database. |
3932
| STRING CONVERSION WITH SUBSTITUTION BY DEFAULT CHARACTERS PERFORMED FOR RECORD recordname
Meaning Conversion replaces characters of source by a default character because of no equivalent representation in user defined character set. |
3933
| ITEM itemname OF UNKNOWN ITEM TYPE IN RECORD recordname
Meaning Self-explanatory. |
3935
| NATIONAL CHARACTERS CANNOT BE CONVERTED: XHCS RETURN CODE: returncode
Meaning Self-explanatory. Response See description of the return code in the XHCS manual. |
3936
| USER CODED CHARACTER SET CANNOT BE DETERMINED: SRMUINFI RETURN CODE: returncode
Meaning Self-explanatory. |
3944
| filename AMBIGUOUS WITHIN USERID
Meaning In a multi-public volume set the file is not unique within the userid. Response Ensure uniqueness and repeat BOUTLOAD. |
3945
| AFIM-LOGGING IS SPECIFIED FOR ACTUAL VERSION OF DATABASE, THEREFORE FORMATTING OF USER-REALMS NOT POSSIBLE
Relevant statement: REMOVE or EXPORT with RECORD-NAME= *ALL Meaning All user realms are to be reformatted; this is, however, not possible if AFIM logging has been specified for the database. |
| Response Deactivate logging for the database in a BMEND run, then repeat BOUTLOAD run. |
3946
| MORE THAN ONE LINKNAME FOR filename
Meaning More than one link name exist for the indicated SAM output file. Response Assign unique link name for file and repeat BOUTLOAD. |
3951
| THERE ARE OCCURRENCES STILL PRESENT FOR MEMBER RECORD recordname
Relevant statement: REMOVE or EXPORT with RECORD-NAME=recordname Meaning Member records of an owner record type to be deleted are still present in the database. The member records have to be deleted with or prior to the owner record however. An error message is output for each member record type concerned. Response Restart BOUTLOAD and specify deletion for the member record type (combined with selection if required). |
3970
| SYSTEM BREAK OCCURRED FOR DBDIR.
AT THIS TIME ONLY ‚REMOVE *ALL’ OR ‚COPY...SET-INFO=NO‘ POSSIBLE
Meaning A statement other than those shown was entered despite the preceding WARNING 3931. The database is inconsistent. Response Reset the database or specify one of the indicated statements. |
3971
| SYSTEM BREAK OCCURRED FOR REALM realmname
Meaning The indicated realm has not been closed normally in a previous update transaction. The current state of the database is inconsistent. In the case of a DBDIR realm, the causing transaction and its date can be obtained from the dump of the first page (using DPAGE). If the realm is a user realm (i.e. any realm other than the DBDIR), the realm file is not part of the current database version. Response In the case of the DBDIR the database must be reset to the state prior to the update transaction; in the case of a user realm the error must have been caused by an illegal manipulation on the file. |
3973
| FPA-ENTRY OUT OF RANGE FOR BLOCK-ACTKEY actkey
Meaning The FPA entry for the indicated database page is negative or exceeds the maximum permissible value. When encountering this error, BOUTLOAD aborts immediately. Response Check consistency of the database using BCHECK; if the message: “START UPDATE FOR DATABASE” has already been output, the database must be reset to the state prior to BOUTLOAD beforehand. |
3974
| NR_PAGE_INDICES OUT OF RANGE FOR BLOCK-ACTKEY actkey
Meaning The number of page index entries for the indicated database page is negative or exceeds the maximum permissible value. When encountering this error, BOUTLOAD aborts immediately. Response Check the consistency of the database using BCHECK; if the message: “START UPDATE FOR DATABASE” has already been output, the database must be reset to the state prior to BOUTLOAD beforehand. |
3975
| DUMMY_ENTRY INVALID FOR BLOCK-ACTKEY actkey
Meaning The indicated database page contains an error in the address of the CALC table in the CALC page or in the end address of the page if it is not a CALC page. Response Check consistency of the database using BCHECK; if the message: “START UPDATE FOR DATABASE” has already been output, reset database to the state prior to BOUTLOAD beforehand. |
3976
| DBTT TOO LARGE FOR RECORD recordname
Meaning A DBTT has been created for the indicated record type with RSQ entries which exceed the maximum permissible value of 224-1 for 2-Kbyte records or 224-1 for 2-Kbyte records or 231-1 for 4/8-Kbyte records. When this high value range of the DBTT is used for RSQ entries, the associated records are likely not to be accessible. Response Reduce size of DBTT using BREORG while high value range is not used. Otherwise reset database to consistent state first. |
3978
| BFORMAT NOT EXECUTED COMPLETELY
Meaning Not all user realms of the current database have been formatted. Database creation has not yet been completed. Response Start BFORMAT, specifying the missing user realms. |
3979
| DELETION OF LIST FOR A SINGULAR SET setname ANCHORED IN BLOCK WITH ACTKEY actkey UNSUCCESSFUL
Meaning A table node always exists for an empty table of a SYSTEM set. Not enough space was available when this node was created for a list. Response Reorganize the list using BREORG, specifying an occupancy level, in order to restructure it. |
3986
| CLOSE UNSUCCESSFUL FOR filename WITH DMS-CODE:dmscode
Meaning Failure to close the indicated file. Response According to the indicated DMS code; if the message: “START UPDATE FOR DATABASE” has already been output, reset the database to the state prior to the BOUTLOAD run beforehand. |
3992
| WRITE INTO OUTPUT FILE UNSUCCESSFUL FOR filename WITH DMS-CODE:dmscode
Meaning Failure to write a record to the indicated output file (SAM file, disk or tape). Response According to the indicated DMS code; if the message: “START UPDATE FOR DATABASE” has already been output, reset the database to the state prior to BOUTLOAD beforehand. |
3993
| FILE UNSUCCESSFUL FOR filename WITH DMS-CODE:dmscode
Meaning Failure to open a non-existent output file. The database has not yet been updated. Response According to the indicated DMS code. |
3994
| RELEASE UNSUCCESSFUL FOR linkname WITH DMS-CODE:dmscode
Meaning Failure to release the link name DATABASE or the link name for an output file. Response In the case of DATABASE, terminate task with /LOGOFF as the database has already been closed; for the link name of an output file, refer to message 3986. |
3996
| RDTFT UNSUCCESSFUL FOR linkname WITH DMS-CODE:dmscode
Meaning Failure to read the TFT entry for LINK-NAME=DATABASE. The database has not yet been updated. Response According to the indicated DMS code. |
3998
| FSTAT UNSUCCESSFUL FOR filename WITH DMS-CODE:dmscode
Meaning Failure to read the BS2000 catalog entry for the indicated file. The database has not yet been updated. Response According to the indicated DMS code. |
3999
| ERASE UNSUCCESSFUL FOR filename WITH DMS-CODE:dmscode
Meaning The empty output file created internally by BOUTLOAD could not be deleted. Response According to the indicated DMS code. |
8901
| FUNCTION:operation R-CODE:retcode MODULE:module
SUPPLEMENT:explanation
Meaning During the program run a BOUTLOAD error was encountered for the current constellation which has not existed in this form before. Additional information is output on SYSLST. Response Retain entire documentation and submit to your system consultant staff. If the message: “START UPDATE FOR DATABASE” has already been output, reset the database to the state prior to the BOUTLOAD run. |