2409
| DATABASE IS LOCKED WITH RESPECT TO WANTED ACCESS RIGHT
Meaning The database is exclusively locked by the DBH, BMEND or another utility routine. Response Restart BPSQLSIA once the exclusive lock on the database has been released. |
2411
| NO DATABASE DECLARED
Meaning The command assigning the link name DATABASE is missing. Response Enter a correct command assigning the link name and restart BPSQLSIA. |
2416
| DATABASE CURRENTLY USED
Meaning The database is currently in use and BPSQLSIA cannot be run in parallel. Response Wait until the database has been released and restart BPSQLSIA. |
4001
| RECORD IS MEMBER IN AT LEAST ONE SET, WHICH IS NOT IN SUBSCHEMA
Meaning The record type is a member record type in at least one set that has not been taken over into the subschema. Response None. |
4002
| TEMPORARY REALM NOT IN SUBSCHEMA
Meaning The temporary realm has not been taken over into the subschema. Response None. |
4003
| ASCENDING/DESCENDING/CALC/SEARCH - KEY NOT COMPLETE IN SUBSCHEMA
Meaning Not all the elements of a compound key are included in the subschema. Response None. |
4004
| RECORD recordname CONTAINS VARIABLE ITEM
Meaning Self-explanatory. Response None. |
4010
| RECORD recordname WITHIN MORE THAN ONE REALM
Meaning The record type recordname is distributed over more than one realm. Response None. |
4011
| SET setname HAS TYPE PRIOR/NEXT
Meaning The set setname has been defined with PRIOR or NEXT. Response None. |
4012
| COMPRESSION DEFINED FOR RECORD recordname
Meaning Self-explanatory. Response None. |
4013
| LOCATION MODE IS DIRECT IN RECORD recordname
Meaning LOCATION MODE IS DIRECT or DIRECT-LONG has been entered for the record type recordname. Response None. |
4014
| NEGATIVE SCALE DETECTED AT ITEM itemname
Meaning The item itemname has been defined with a negative scale factor. Response None. |
4015
| NUMBER DIGITS > 15 AT ITEM itemname
Meaning The item itemname has more than 15 relevant digits. Response None. |
4016
| SCALE GREATER THAN NUMBER DIGITS AT ITEM itemname
Meaning The item itemname has a scale factor greater than its relevant digits. Response None. |
4017
| INDEX CANNOT BE USED IN SQL (DESCENDING-KEY)
Meaning The printed index cannot be used in SQL in its present format since a DESCENDING KEY is involved. Response If possible, define a group in the subschema for the fields of the compound key. |
4018
| INDEX CAN BE USED ONLY WITHIN ’IN PREDICATE’ OR WITHIN ’COMPARISON PREDICATE’ WITH ’EQUALS OPERATOR’
Meaning The key can only be evaluated by SQL in the indicated cases. Response None. |
4019
| ATTRIBUTE itemname IS DEFINED AS DATABASE-KEY-LONG
Meaning The itemname attribute was defined as an item of type DATABASE-KEY-LONG. Response None. |
4030
| NO INSERT ON TABLE recordname POSSIBLE
Meaning An SQL INSERT is not possible for the base table recordname. Response None. |
4031
| NO UPDATE ON TABLE recordname POSSIBLE
Meaning An SQL UPDATE is not possible for the base table recordname. Meaning None. |
4032
| TABLE recordname CANNOT BE PROCESSED WITH SQL
Meaning Self-explanatory. Response None. |
4033
| RELATIONAL SCHEMA subschemaname CANNOT BE PROCESSED WITH SQL
Meaning Self-explanatory. Response None. |
4034
| ATTRIBUT itemname CANNOT BE PROCESSED WITH SQL
Meaning The item itemname cannot be accessed using SQL. Response None. |
4049
| WRONG SUBSCHEMA FORMAT FOR subschemaname
Meaning BPSQLSIA cannot process the subschema version generated by the DDL compiler. Response Use the BPSQLSIA of the UDS/SQL version which matches the COSSD. |
4050
| FILE COSSD COULD NOT BE OPENED DMS-CODE: dmscode
Meaning The COSSD file cannot be accessed. Response Remove cause and restart BPSQLSIA. |
4051
| ERROR BY READING schema-record/subschema-record/tss FROM COSSD
DMS-CODE: dmscode
Meaning The schema control record, the subschema control record or the transformed source (TSS) cannot be read from COSSD. Response Inform system administrator. |
4055
| SSIA FOR subschemaname NOT FOUND IN DBDIR
Meaning No SSIA could be found in the DBDIR for the subschema subschemaname in the COSSD. Response Check database structure and correct, if necessary. |
4056
| ERROR BY READING SSIA FROM DBDIR
Meaning An error occurred while the SSIA was being read out of the DBDIR. Response Inform system administrator. |
4057
| SUBSCHEMA subschemaname NOT FOUND IN COSSD
Meaning A subschema specified by the user could not be found in the COSSD. Response Enter correct subschema name. |
4058
| FILE COSSD COULD NOT BE CLOSED
DMS-CODE: dmscode
Meaning An error occurred during the COSSD close. Response Inform system administrator. |
4060
| FOR AT LEAST ONE {SET/AREA/RECORD} OF THE SUBSCHEMA A DESCRIPTION IN SIA CANNOT BE FOUND. COSSD AND DBDIR DONT CORRESPOND
Meaning No description exists in the SIA for a realm, set or record type belonging to the subschema. COSSD and DBDIR do not match. Response Inform system administrator; compare COSSD and DBDIR. |
4070
| ONLY 30 SUBSCHEMAS CONSIDERED AND PRINTED, REST IGNORED
Meaning More than 30 subschemas were entered explicitly in the PRINT statement in a BPSQLSIA run. Only 30 subschemas are processed. Response None. |
4071
| ONLY 30 SUBSCHEMAS CONSIDERED FOR EXCEPT, REST IGNORED
Meaning More than 30 subschemas were explicitly entered in the PRINT *ALL_EXCEPT statement in a BPSQLSIA run. Only 30 subschemas are excluded from processing, the others are processed. Response None. |