Reason:
A result column is too small to accommodate all significant data from the source and has been truncated.
Severity:
0
Reason:
Row skipped - column or variable does not accept null values or null indicator not provided
Severity:
0
Reason:
More than one row exists that satisfies a single-valued subquery.
Severity:
0
Reason:
No rows exist that satisfy a single-valued subquery.
Severity:
0
Reason:
An update statement has been attempted but the transaction state is READ ONLY.
A SET TRANSACTION has been attempted but a transaction has already been initiated.
A SET ACCESS MODULE has been attempted but a transaction has already been initiated.
Multiple SET ACCESS MODULE statements attempted.
Severity:
0
Reason:
The SQLCIB contains an unrecognizable SQL statement code, likely due to an application error or overlayed storage.
Severity:
0
Reason:
The named module does not conform to the expected structure of an access module.
Severity:
0
Reason:
The load of the named module failed because of insufficient free space in the program pool.
Severity:
0
Reason:
The named module could not be found.
Severity:
0
Reason:
The load of the named module failed because of a deadlock.
Severity:
0
Reason:
The named SQLPIB program identifier cannot be found in the application's access module.
Severity:
0
Reason:
The compile stamps in the SQLPIB and application's access module RCM do not match.
Severity:
0
Reason:
A matching SQLCIB section identifier cannot be located in the application's access module.
Severity:
0
Reason:
A need to automatically recompile the access module has arisen, but the access module was generated with AUTO RECREATE OFF.
Severity:
0
Severity:
0
Reason:
A cursor is closed when it should be open or open when it should be closed.
Severity:
0
Reason:
The size of the parameter buffer is too small for the needs of the current statement.
Severity:
0
Reason:
The current statement requires a parameter buffer but none was provided.
Severity:
0
Reason:
The requested number of rows to process is less than zero.
Severity:
0
Reason:
The current statement requires a data (tuple) buffer but none was provided.
Severity:
0
Reason:
The size of the data (tuple) buffer is too small for the needs of the current statement.
Severity:
0
Reason:
The specified starting row for a BULK statement is outside the dimensions of the data (tuple) buffer.
Severity:
0
Reason:
The current statement violates a check constraint.
Severity:
0
Reason:
Storage for the identified structure could not be acquired.
Severity:
0
Reason:
An attempt to assign invalid data to a column has been detected.
Severity:
0
Reason:
An error has been detected while attempting to convert data from one datatype to another.
Severity:
0
Reason:
Divisor or multiplier of DECIMAL datatype exceeds 15 digits.
Severity:
0
Severity:
0
Reason:
Parameter list contains too few or too many operands.
Severity:
0
Reason:
As an error level message, this indicates that a DATE or TIMESTAMP value has been computed in which the year is greater than 9999.
As a warning level message, it indicates that an arithmetic operation on a DATE value has resulted in a day beyond the valid range of values for that month. In such cases, a warning is issued. For a select statement, the day is set to the last day of that month, but for an update the target column is left unchanged. For example, March 31 + 1 month = April 30 and February 29, 1992 + 1 year = February 28, 1993.
Module:
IDMSEXP.
Severity:
0
Reason:
This message represents IDMSTAT reporting as follows:
C-7Mnnnn = Severity and Module Number DB error nnnn = IDMS Error Code Tbl:<name> = Last Good Table/Record Name Area:<name> = Last Good Area Name ErrSet:<name> = Error Set/Index Name ErrTbl:<name> = Error Table/Record Name ErrArea:<name> = Error Area Name
Severity:
0
Reason:
An unexpected error has occurred during the execution of an internal SQL sort.
<Identifier> may be one of:
1: bad function code 2: QPL destroyed 3: invalid datatype code 4: invalid record length 5: missing QKY address 6: missing number of QKYs 7: missing input record address 8: invalid keylength 9: short on storage 10: invalid record count 11: putscratch error 12: getscratch error 13: deletescratch error 14: error returned from external sort 15: records-in not equal records-out 16: not enough buffers 17: scratch space exhausted
Severity:
0
Reason:
An unexpected error has occurred while attempting to write to a scratch file.
<Identifier> may be one of:
4: invalid request 20: record already exists in scratch area 28: I/O error
Severity:
0
Reason:
An unexpected error has occurred while attempting to read from a scratch file.
<Identifier> may be one of:
4: invalid parmlist 8: SAID cannot be found 12: SRID cannot be found within named SAID 24: output area too small 28: I/O error
Severity:
0
Reason:
An unexpected error has occurred while attempting to delete a scratch record.
<Identifier> may be one of:
4: invalid parmlist 8: SAID cannot be found 12: SRID cannot be found within named SAID 28: I/O error
Severity:
0
Reason:
The named table's catalog and database timestamps do not match.
Severity:
0
Reason:
No row exists to satisfy a 'WHERE CURRENT OF CURSOR' predicate.
Severity:
0
Reason:
A deadlock has occurred involving the identified row.
Severity:
0
Reason:
CONNECT statement attempted but a session has already been started.
First statement of a SUSPENDed session must be RESUME.
RESUME statement issued against un-SUSPENDed session.
Severity:
0
Reason:
The identified value is not a valid run tree node type (internal error).
Severity:
0
Reason:
The identified value is not a valid run tree operation code (internal error).
Severity:
0
Reason:
The named area's free space has been exhausted.
Severity:
0
Reason:
The value of a string column has been truncated.
For FETCH or SELECT, the corresponding host variable's indicator variable (if any) is set to the full length of the string.
For INSERT or UPDATE, the statement cannot be executed because significant characters would be truncated.
Severity:
0
Reason:
Internal error in pseudocode generation.
Severity:
0
Reason:
Internal error in pseudocode or run tree generation.
Severity:
0
Reason:
Internal error in pseudocode generation.
Severity:
0
Reason:
Internal error in pseudocode generation.
Severity:
0
Reason:
Internal error in pseudocode generation.
Severity:
0
Reason:
Internal XMJ sequencing error.
Severity:
0
Reason:
DDL which may alter the catalog definition of tables is not permitted when one or more cursors are concurrently open.
Severity:
0
Reason:
More rows exist that satisfy a non-cursored SELECT than were requested.
Severity:
0
Reason:
Attempt to PREPARE a statement for which PREPARE is not allowed.
Severity:
0
Reason:
The current statement requires an SQL descriptor area and one was not provided.
Severity:
0
Reason:
Attempt to EXECUTE IMMEDIATE a statement for which EXECUTE IMMEDIATE is not allowed.
Severity:
0
Reason:
PREPAREd SELECT statements may not be the object of an EXECUTE statement.
Severity:
0
Reason:
DB001057 is used by AMC as a generic message code.<Message-text> is replaced by AMC with error-specific text.
Severity:
0
Reason:
An attempt to INSERT or MODIFY a row has resulted in a uniqueness violation.
Severity:
0
Reason:
A row in the named referenced Table cannot be UPDATEd or DELETEd because it contains a primary key for which exist one or more referencing rows in the table defined by the named constraint.
Severity:
0
Reason:
A row in the named referencing Table cannot be INSERTed or UPDATEd because no referenced row exists with a matching primary key as defined by the named Constraint.
Severity:
0
Reason:
Data Transfer Services (DTS) between the front-end and the back-end have failed. The return code is explained on the second line of the message. Generally the actual cause of the failure must be determined by examining the log for the task.
If the log fails to clarify the reason for the failure contact Technical Support.
Severity:
0
Reason:
The result of subtracting a duration from a date/time value must never be negative. The duration must be smaller than the date or time from which it is to be subtracted.
Module:
IDMSEXP
Severity:
0
Reason:
Internal error in the specification of a datetime expression.
Module:
IDMSEXP
Severity:
0
Reason:
Arithmetic operation generated invalid date(for example, Feb. 30).
Module:
IDMSEXP
Severity:
0
Reason:
Start and length operands must be positive and within the range of the string operand.
Module:
IDMSEXP
Severity:
0
Reason:
The load of the named module failed because of an I/O or database error.
Severity:
0
Reason:
An error occurred during the processing of a statement after updates were made to the database. Since the statement was executed in local mode, the database changes could not be rolled out, thus leaving the database in an inconsistent state. All area(s) updated within the transaction remain locked.
Recover areas affected by the failing statement and recover or unlock other areas updated within the transaction.
Module:
IDMSTMGR
Severity:
0
Reason:
Authorization call return code of 12 or greater was received.
Severity:
0
Reason:
A CONNECT was made to a DBNAME which is neither specified in the dbname table, nor is it a SEGMENT defined in the DMCL.
Module:
IDMSQSRV
Severity:
0
Reason:
A CONNECT was made to a DBNAME which has no associated DDLCAT or DDLDML area.
Module:
IDMSQSRV
Severity:
0
Reason:
Each set defined for a native VSAM record must be represented by a KSDS or PATH File in the DMCL.
Module:
IDMSHLDB
Severity:
0
Reason:
An exception was returned by the named Procedure.
Module:
IDMSHLDB
Severity:
0
Reason:
A warning was returned by the named Procedure
Module:
IDMSHLDB
Severity:
0
Reason:
The named Procedure returned an invalid SQLSTATE
SQLSTATEs which can be returned are:
Module:
IDMSHLDB
Severity:
0
Reason:
A SQL condition was returned by the named SQL routine
Module:
IDMSHLDB
Severity:
0
Reason:
An attempt has been made to allocate a dynamic cursor, however, the referenced statement was not a SELECT.
Module:
IDMSHLDB
Severity:
0
Reason:
Either a reference has been made to a dynamic cursor which has never been defined, or an ALLOCATE CURSOR statement identifies a cursor which was previously defined with that name. This error may be caused either because the identifier or the scope of the extended cursor name has been specified incorrectly.
Module:
IDMSHLDB
Severity:
0
Reason:
Either an INSERT, an UPDATE or a DELETE has been issued on a NonTable Procedure. Only CALL or SELECT can be issued on a NonTable Procedure
Module:
IDMSHLDB
Severity:
0
Reason:
A reference has been made to a dynamic SQL statement which has never been defined. This error may be caused either because the identifier or the scope of an extended statement name has been specified incorrectly.
Module:
IDMSHLDB
Severity:
0
Reason:
An attempt has been made to dynamically build a section using a section type for which this operation is not supported. (Internal error).
Severity:
0
Reason:
An attempt has been made to execute a statement which contains dynamic parameter markers, but no USING clause was supplied on the EXECUTE statement. A USING clause is required in order to pass the descriptions of the dynamic parameter values.
Severity:
0
Reason:
An attempt has been made to execute a statement which contains dynamic parameter markers, but the USING clause specified does not contain enough entries. Either the SQLD field of the descriptor indicates that there are too few SQLVAR entries, or there are too few host-variable references in the EXECUTE or OPEN statements. In either case, you must supply an entry for each dynamic parameter marker specified in the text of the dynamically prepared SQL statement which is the target of the OPEN or EXECUTE.
Severity:
0
Reason:
An attempt has been made to fetch from a dynamic cursor, but the USING clause specified doesn't contain enough entries. Either the SQLD field of the descriptor indicates that there are too few SQLVAR entries, or there are too few host-variable references in the FETCH statement. In either case, you must supply an entry for each result column of the dynamically prepared SELECT statement.
Severity:
0
Reason:
An attempt has been made to access a record which has been erased or modified by another database session sharing the same transaction.
Module:
IDMSHLDB
Severity:
0
Reason:
A non-rollback dml command has been issued within a database session whose transaction was forced to backout. This can occur when a shared transaction is backed out by some other session or is forced to backout because of conditions such as a deadlock.
Module:
IDMSQSRV, IDMSNSRV
Severity:
0
Reason:
An error occurred while attempting to start a database transaction. Refer to message DC329009 for a list of possible reason codes.
Module:
IDMSQSRV
Severity:
0
Reason:
An error occurred while attempting to commit a database transaction. Refer to message DC329009 for a list of possible reason codes.
Module:
IDMSQSRV
Severity:
0
Reason:
An error occurred while attempting to rollback a database transaction. Refer to message DC329009 for a list of possible reason codes.
Module:
IDMSQSRV
Severity:
0
Reason:
An error occurred while attempting to resume an SQL transaction. Refer to message DC329009 for a list of possible reason codes.
Module:
IDMSQSRV
Severity:
0
Reason:
An error occurred while attempting to register an interest in a new SQL session with the transaction manager. Examine the system log for more information on the reason for the failure.
Module:
IDMSQCLI
Severity:
0
Reason:
The SQL procedure referenced in an ALLOCATE CURSOR FOR PROCEDURE has not been called previously or the call did not return result sets.
Module:
IDMSHLDB
Severity:
0
Reason:
The open of the received cursor, the last phase in an ALLOCATE CURSOR FOR PROCEDURE failed.
Module:
IDMSHLDB
Severity:
0
Reason:
An internal error occurred in an ALLOCATE CURSOR FOR PROCEDURE.
Module:
IDMSHLDB
Severity:
0
Reason:
The cursor in a DESCRIBE CURSOR STRUCTURE is invalid or has not been allocated previously.
Module:
IDMSHLDB
Severity:
0
Reason:
The ALLOCATE CURSOR FOR PROCEDURE does internally a DESCRIBE to retrieve the definition of the result set. An error, possibly a broken link with the server occurred.
Module:
IDMSHLDB
Severity:
0
Reason:
A procedure call returned more result sets than allowed according to the DYNAMIC RESULT SETS attribute of the procedure.
Module:
IDMSHLDB
Severity:
0
Reason:
An UPDATE of a table which is related to another table as the owner of an unlinked constraint is not allowed. There is no means to verify that the parent row has no children.
Module:
IDMSHLDB
Severity:
0
Reason:
A DELETE of a table which is related to another table as the owner of an unlinked constraint is not allowed. There is no means to verify that the parent row has no children.
Module:
IDMSHLDB
Severity:
0
Reason:
The close of a received cursor was successful, but additional results are available.
Module:
IDMSHLDB
Severity:
0
Reason:
The call of an SQL-invoked procedure completed successfully and the specified number of result sets are available.
Module:
IDMSHLDB
Severity:
0
Reason:
An attempt has been made to compile a program that uses embedded SQL and a full SQL license was not found. The use of embedded SQL requires a full SQL license.
Module:
IDMSQRV
Severity:
0
Reason:
A severe error has occurred while trying to EXPLAIN an SQL statement. Indicates an internal error.
Module:
IDMSDEXP
Severity:
0
Reason:
An attempt has been made to EXPLAIN an access module or statement into a table whose definition is inconsistent with the definition of the standard ACCESS_PLAN table. Possible causes include an insufficient number of columns, an inconsistent data type in an expected column, NULLs allowed in an expected column, or NOT NULL for an extra column.
Redefine the table or specify a different table.
Module:
IDMSDEXP
Severity:
0
Reason:
An attempt has been made to EXPLAIN a statement that cannot be EXPLAINed, either because it is not an SQL DML statement (SELECT, INSERT, UPDATE, or DELETE), there is a syntax error, or there is a compilation error. Additional messages will be included for syntax and compilation errors.
Correct the statement and retry the EXPLAIN.
Module:
IDMSDEXP
Severity:
0
Reason:
An error was encountered while trying to create the ACCESS_PLAN table which contains the output EXPLAIN rows. This message should be preceded by another message which more specifically identifies the problem (for example, no schema qualifier was specified and no session default schema exists).
Correct the statement and retry the EXPLAIN.
Module:
IDMSDEXP
Severity:
0
Reason:
An unexpected database error has occurred. This message identifies the module that was making the database request, and is followed by error message 1031, which contains details of the actual error.
Module:
IDMSDDAM
Severity:
0
Reason:
The table named is defined incorrectly in the catalog area of the data dictionary. The reason text indicates the specific reason. This usually indicates an internal error.
Module:
IDMSTELL
Severity:
0
Reason:
The module named contains an invalid vector table of internal processing routines. Indicates an internal error.
Module:
IDMSDDAM
Severity:
0
Reason:
The module named does not contain the internal processing routine expected. Indicates an internal error.
Module:
IDMSDDAM
Severity:
0
Reason:
An error occurred building a runtime database definition block. Indicates an internal error.
Module:
IDMSTELL
Severity:
0
Reason:
The definition of the table cannot be found in the data dictionary.
Module:
IDMSDTAB, IDMSTELL
Severity:
0
Reason:
The definition of the SQL schema cannot be found in the data dictionary.
Module:
IDMSDTAB, IDMSTELL
Severity:
0
Reason:
The definition of the physical area cannot be found in the data dictionary.
Module:
IDMSDTAB, IDMSTELL
Severity:
0
Module:
IDMSDSCH
Severity:
0
Reason:
The non-SQL defined schema referenced in the SQL schema has not been validated. SQL statements cannot be compiled against a database described by an unvalidated non-SQL defined schema.
Use the schema compiler to validate the schema.
Module:
IDMSTELL
Severity:
0
Reason:
The table is already defined in the data dictionary.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to add a column to a non-empty table where the column definition specifies NOT NULL and does not include a WITH DEFAULT clause. CA IDMS requires that columns defined this way always contain a value, which is not the case if such a column is added to an existing row.
Change the column definition to either specify WITH DEFAULT or to allow a NULL value.
Module:
IDMSDTAB
Severity:
0
Reason:
The table already includes a column with the same name.
Module:
IDMSDTAB
Severity:
0
Reason:
The column would make a row too long to store in a CA IDMS database.
Module:
IDMSDTAB
Severity:
0
Reason:
The internal column definition contained an invalid data type. This indicates an internal error.
Module:
IDMSDTAB
Severity:
0
Reason:
The SQL schema is already defined in the data dictionary.
Module:
IDMSDSCH
Severity:
0
Reason:
An attempt has been made to DROP a table or view that is referenced by a view or referential constraint.
Specify CASCADE on the DROP statement, or individually DROP all referencing views and constraints.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt was made to create a view where the number of column name overrides is not the same as the number of columns referenced in the associated select clause.
Specify the same number of column names as are referenced in the select clause, or specify no column name overrides.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt was made to create a table without specifying the area where the data will be stored, and the SQL schema associated with the table does not contain a default area.
Specify a WITHIN AREA clause on the CREATE TABLE statement.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to create a table in a segment that has been defined as restricted to an SQL schema different from the schema in which the table is being created.
Module:
IDMSDTAB
Severity:
0
Reason:
Operation disallowed because the column is referenced in a check constraint.
Module:
IDMSDTAB
Severity:
0
Reason:
The temporary table has already been defined.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to create a table without specifying an SQL schema name for the table, and no default schema name is in effect.
Specify an SQL schema name as part of the table name.
Module:
IDMSDTAB
Severity:
0
Reason:
An element in the schema record defined with an OCCURS clause could not be transformed into a column for SQL access. Either the OCCURS is nested too many levels, or the generated subscripts make the element name too long.
Modify the element definition or define an SQL synonym for the record.
Module:
IDMSTELL
Severity:
0
Reason:
An error has occurred building a runtime database definition block. Indicates an internal error. When applicable, <entity name> identifies the database entity which caused the error. These errors are often the result of non-SQL records being accessed from SQL whose definitions are in conflict with SQL rules.
Module:
IDMSTELL
Severity:
0
Reason:
Tables cannot be created in a 'referencing' SQL schema.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to create a table in a segment restricted to non-SQL defined databases.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to modify an SQL Schema default area and no area name was specified. The segment name will be ignored.
Module:
IDMSDSCH
Severity:
0
Reason:
An attempt has been made to create or modify the definition of a table in the SYSTEM schema.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to create a view specifying the WITH CHECK OPTION clause, and the select clause that defines the view contains a subquery.
Module:
IDMSDTAB
Severity:
0
Reason:
An attempt has been made to specify a number of estimated rows greater than the number of rows allowed for a table. Estimated rows has been set to the maximum allowed.
Module:
IDMSDTAB
Severity:
0
Reason:
An error has occurred building a runtime database definition block due to encountering a non-SQL table (i.e., a network record) in the same network schema defined in a single dictionary but which occurs in multiple segments (or non-SQL schemas).
Module:
IDMSTELL
Severity:
0
Reason:
An error has occurred when generating a subschema. The record, set, or area referenced in a logical record facility path statement cannot be found in the subschema.
Module:
IDMSTELL
Severity:
0
Reason:
Before executing an ALTER CATALOG command, you must run the TABLEDDL file against the catalog.
Module:
IDMSDSCH
Severity:
0
Reason:
You must not create any SQL schemas (other than the SYSTEM schema from TABLEDDL) before executing the ALTER CATALOG command
Module:
IDMSDSCH
Severity:
0
Reason:
The character set name specified in an ALTER CATALOG command is unknown in the system. Check for proper spelling
Module:
IDMSDSCH
Severity:
0
Reason:
If attempting to create an Index, CALC key or Constraint, the specified object is not an SQL-defined base table. It is either a view, a non-SQL defined table or a Procedure and as such indexes, constraints and CALC keys cannot be defined on it.
or
If attempting to create a Key, the specified object is not a procedure.
Module:
IDMSDCON
Severity:
0
Reason:
Not all non-SQL data types are supported from SQL. A record which contains an element with an unsupported data type was referenced from an SQL statement.
Module:
IDMSTELL
Severity:
0
Reason:
A CALC, index or sorted set definition for a non-SQL record contains an element which violates SQL definition rules. The known causes of this error are as follows:
02 ELEM2 REDEFINES ELEM1.
03 ELEM2A PIC X(4).
03 ELEM2A PIC X(4).
If a CALC key (for example) was declared on (ELEM2A, ELEM2B), the error would be raised. The solution is to arrange the definition so that the base element definition is the group element whose subordinate elements represent the finest level of granularity of any of the redefinitions. In the example, ELEM2 should be the base definition and ELEM1 should redefine ELEM2.
Module:
IDMSTELL
Severity:
0
Reason:
A non-SQL set definition contains a foreign key mapping involving an element which violates SQL definition rules. Possible causes are that the element is declared as "filler" or that it is defined with an unsupported data type.
Module:
IDMSTELL
Severity:
0
Reason:
The definition of the table type in the catalog does not match the requested table type.
Severity:
0
Module:
IDMSDTAB
Reason:
On a CREATE INDEX, an INDEX ID was specified which conflicts with another INDEX ID already defined for that AREA.
Severity:
0
Module:
IDMSDCON
Reason:
On a CREATE TABLE, or ALTER TABLE, the TIMESTAMP syntax is only allowed if stamping by TABLE.
Severity:
0
Module:
IDMSDTAB
Reason:
A utility statement issued online is not allowed because there is already an open transaction from a previous statement. A COMMIT should be used after the previous statement in order to allow this statement to run.
Module:
IDMSUTIL
Severity:
0
Reason:
This is an informational message that is written to the JES log and the CV log if issued in CV. The message documents that the named utility was run on the specified date and time for the named area. Currently this message is issued by FIX PAGE and by FORMAT.
Module:
IDMSUFMT, IDMSUPFX
Severity:
0
Reason:
An ALTER SCHEMA command was entered that contains syntax that is not compatible with the existing SCHEMA defined in the catalog.
Module:
IDMSDSCH
Severity:
0
Reason:
An SQL transaction has attempted to access tables through one or more referencing schemas and those schemas have been defined in such a way that the two named tables appear to reside in the same area and have the same table ID. This is an illegal situation, since all tables residing in an area must have unique table IDs. This error is likely caused either because two referencing schemas have the same DBNAME specification or a referencing schema has the same DBNAME specification as that of a table in a non-referencing schema that is being accessed in the same transaction.
Module:
IDMSBLDR
Severity:
0
Reason:
An SQL transaction has attempted to access tables through one or more referencing schemas and those schemas have been defined in such a way that the two named indexes reside in the same area and have the same index ID. This error is likely caused either because two referencing schemas have the same DBNAME specification or a referencing schema has the same DBNAME specification as that of an index in a non-referencing schema that is being accessed in the same transaction.
Module:
IDMSBLDR
Severity:
0
Reason:
On a CREATE TABLE, the specified table id is invalid. Table id values must be in the range of 1024 through 4095.
Module:
IDMSDTAB
Severity:
0
Reason:
The external representation of a TIMESTAMP is invalid.
Module:
IDMSDTAB, IDMSDSEG
Severity:
0
Reason:
Issue a commit before issuing this command.
Module:
IDMSDDAM
Severity:
0
Reason:
Views in an SQL referenced schema cannot be accessed through a referencing schema
Module:
IDMSTELL
Severity:
0
Reason:
A referencing SQL schema must reference an SQL schema
Module:
IDMSDSCH
Severity:
0
Reason:
While trying to create a referencing SQL schema it was determined that there was an illegal inter-schema constraint for the referenced schema
Module:
IDMSDSCH
Severity:
0
Reason:
While trying to create a referencing SQL schema it was determined that there was an unlinked inter-schema constraint for the referenced schema
Module:
IDMSDSCH
Severity:
0
Reason:
This is an informational message to display the result of a SQL routine compilation.
Module:
IDMSDTAB
Severity:
0
Reason:
An #PUTSCR error in QRTN occurred. Internal routine QRTN.
Module:
IDMSDTAB
Severity:
0
Reason:
A #SSP call to build an ITREE to define SQL local variables failed. Internal routine QRTN.
Module:
IDMSDTAB
Severity:
0
Reason:
A #SSP call returned an invalid ITREE Internal routine QRTN
Module:
IDMSDTAB
Severity:
0
Reason:
SQL procedures or functions can not be altered for adding parameters. You must Drop and (re)Create the SQL routine.
Module:
IDMSDTAB
Severity:
0
Reason:
Certain attributes for SQL procedures or functions can not be changed, such as External Name, Protocol, Mode, Transaction Sharing...
Module:
IDMSDTAB
Severity:
0
Reason:
During the compilation of SQL routines with PROTOCOL ADS an ADS mapless dialog compilation failed. Check the ADS compilation messages in order to diagnose the cause for the failure.
Module:
IDMSDTAB
Severity:
0
Reason:
During the compilation of SQL routines with PROTOCOL ADS an ADS mapless dialog compilation failed. An unexpected GETSCR error occurred while retrieving the compile errors.
Module:
IDMSDTAB
Severity:
0
Reason:
One or more steps in the Drop of a SQL routine failed. For more information on the kind of failures, see the associated messages. Some objects may have been left in the dictionary.
Module:
IDMSDTAB
Severity:
0
Reason:
A SQL routine can not allocate more than 9999 blocks of local variables.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> already has/doesn't have a default clause.
Reason:
A default clause cannot be added if the column already has a default clause. A default clause cannot be dropped if the column doesn't have a default clause.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> is named in View(s): <view-name>(, <view-name>, ...).
Reason:
A column cannot be renamed if it is named in a view.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> already has/doesn't have a NULL indicator
Reason:
An attempt has been made to allow/disallow nulls in column however the column already has/doesn't have a NULL indicator set.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> is part of CALC key
Reason:
An attempt has been made to alter column's attributes however the column is part of a CALC key of populated table.
Or
An attempt has been made to drop a column, however the column is part of a CALC key and CASCADE option was not specified.
Or
An attempt has been made to drop a column, however the column is part of a CALC key of populated table.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> is referencing or referenced in a referential constraint
Reason:
An attempt has been made to alter column's attributes however the column is referencing or referenced in a referential constraint of populated table.
Or
An attempt has been made to drop a column, however the column is named in a referential constraint and CASCADE option was not specified.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> is a sort column of a linked constraint
Reason:
An attempt has been made to drop a column however the column is a sort column of a linked constraint.
The CASCADE option was not specified.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name> is an indexed column
Reason:
An attempt has been made to drop a column however the column is an indexed column.
CASCADE option was not specified.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Cannot drop the last column
Reason:
An attempt has been made to drop the last column in a table. This is not allowed.
Module:
IDMSDTAB
Severity:
0
COMPRESS parameter disallowed because CA IDMS Presspack not intended for use
Reason:
The COMPRESS parameter of the CREATE TABLE statement is disallowed because the product intent setting for CA IDMS Presspack in module RHDCPINT indicates that the product is not intended to be used. If this should be changed, you must recreate the RHDCPINT module. The easiest way to do this and ensure that all the required changes are made to your CA IDMS environment is to add the CA IDMS Presspack product using the configuration portion of the install. For more information, see the Installation Guide for your operating system.
Module:
IDMSDTAB
Severity:
0
C<sqlcode>M<module-number>: Column <column-name>is a sort column of an unique linked constraint
Reason:
An attempt has been made to alter a column to allow nulls however the column is included in the sort column of an unique linked constraint.
Module:
IDMSDTAB
Severity:
0
Reason:
Indicates an internal error.
Module:
IDMSSTOW **temp** Make generic, with Reason: parm
Severity:
0
Reason:
A column named as a key within an index or a constraint has not been previously defined within the specified table.
Module:
IDMSDCON
Severity:
0
Reason:
The attributes for columns named as keys for the tables participating within a constraint do not match.
Module:
IDMSDCON
Severity:
0
Reason:
An index has not been defined on the columns defined for the referenced table of an unlinked constraint.
Module:
IDMSTELL
Severity:
0
Reason:
The referenced table and constraint are defined such that a unique row cannot be identified.
Module:
IDMSDCON
Severity:
0
Reason:
A CREATE CONSTRAINT command names an existing constraint.
Module:
IDMSDCON
Severity:
0
Reason:
The named constraint was not defined for the specified table.
Module:
IDMSDCON
Severity:
0
Reason:
The index name or calckey specified on a CREATE command already exists.
Module:
IDMSDCON
Severity:
0
Reason:
The index or calckey named on other than a CREATE command has not been previously created.
Module:
IDMSDCON
Severity:
0
Reason:
The specified table has not been associated with an area.
Module:
IDMSDCON
Severity:
0
Reason:
Columns specified as part of the referenced table must not allow null values.
Module:
IDMSDCON
Severity:
0
Reason:
Specification of the CLUSTERED option is invalid because the referencing table has already been defined as having a calckey or is the referencing table in an earlier constraint that used the CLUSTERED option.
Module:
IDMSDCON
Severity:
0
Reason:
A constraint has specified that it is to be ordered and included the UNIQUE option but one or more of the columns making up the key can be null.
Module:
IDMSDCON
Severity:
0
Reason:
The column(s) specified as the foreign key of the referencing table of an unlinked constraint must be defined as a calckey or the key of an index.
Module:
IDMSDCON
Severity:
0
Reason:
An attempt to drop an index is not allowed because it is used by an existing constraint.
Module:
IDMSDCON
Severity:
0
Reason:
The area into which an index is to be defined does not exist.
Module:
IDMSDCON
Severity:
0
Reason:
After adding in overhead bytes for the constraint or index the row is too long. An uncompressed row cannot be longer than the (Page-size - Page-reserve - 40) while a compressed row cannot be longer than 32724 bytes.
Module:
IDMSDCON
Severity:
0
Reason:
The length of a sort column defined for an index or a constraint exceeds 2000 characters.
Module:
IDMSDCON
Severity:
0
Reason:
An attempt has been made to define a key (Index, CALC or ProcedureKey) with more than 32 columns. The maximum number of columns in a key is 32.
Module:
IDMSDCON
Severity:
0
Reason:
An attempt has been made to define a procedure key without specifying any columns. Procedure keys require at least one column to be specified as part of the key definition.
Module:
IDMSDCON
Severity:
0
C<sqlcode>M<module-number>: Constraint <constraint-name> is not indexed.
Reason:
An attempt has been made to alter a non-indexed constraint.
Module:
IDMSDCON
Severity:
0
Reason:
An attempt has been made to alter an index to NOT UNIQUE, but the index has at least one constraint that depends on index uniqueness and no other index exists that could be used by the constraint.
Module:
IDMSDCON
Severity:
0
Reason:
An attempt has been made to alter an index or linked index on constraint to UNIQUE or NOT UNIQUE but the uniqueness cannot be altered because the index is sorted on DBKEY.
Module:
IDMSDCON
Severity:
0
Reason:
IDMSIFR was called with an invalid command code. This is an internal error.
Module:
IDMSIFR
Severity:
0
Reason:
The table named contains rows and the current DDL statement requires the table to be empty.
Module:
IDMSIFR
Severity:
0
Reason:
The area named has no room to store a record.
Module:
IDMSIFR
Severity:
0
Reason:
The area named contains synchronization stamps and a request was made to install them.
Module:
IDMSIFR
Severity:
0
Reason:
The index named was not found in the generated access module. Possible error in building the Tell Request Header.
Module:
IDMSIFR
Severity:
0
Reason:
The area named has allocated all available record ids. No new tables can be defined to this area.
Module:
IDMSIFR
Severity:
0
Reason:
The area named was not found in the generated access module. Possible error in building the Tell Request Header.
Module:
IDMSIFR
Severity:
0
Reason:
The PR60 for the area named contains an invalid dbkey for the K0 system record type.
Module:
IDMSIFR
Severity:
0
Reason:
The synchronization stamp for the named table was not found in its defined area.
Module:
IDMSIFR
Severity:
0
Reason:
The named table was not found in the generated access module. Possible error in building the Tell Request Header.
Module:
IDMSIFR
Severity:
0
Reason:
A request was made to drop the named table and a constraint that references this table was found in the generated access module.
Module:
IDMSIFR
Severity:
0
Reason:
The catalog synchronization stamp for the named table does not match the stamp in the database area.
Module:
IDMSIFR
Severity:
0
Reason:
Duplicate keys were found while building the named index.
Module:
IDMSIFR
Severity:
0
Reason:
A TELL request returned an invalid JIB address. Internal error.
Module:
IDMSIFR
Severity:
0
Reason:
The ready for the named area failed because it was already in use.
Module:
IDMSIFR
Severity:
0
Reason:
The synchronization stamp level (by table or by area) in the catalog does not match what is in the DMCL load module.
Module:
IDMSIFR
Severity:
0
Reason:
The requested table ID for a new table is already assigned.
Module:
IDMSIFR
Severity:
0
Reason:
SQL DDL was requested for the named area, but it is a non-SQL defined area.
Module:
IDMSIFR
Severity:
0
Reason:
The referenced and referencing tables in a linked constraint must be in the same page group and have the same number of records per page. The same is true for an index and the table it indexes.
Module:
IDMSIFR
Severity:
0
The ALTER statement fails if nulls are being disallowed and some row has a null value for the column.
Module:
IDMSIFR
Severity:
0
Reason:
A column data type is being changed however data types are not compatible for conversion.
Module:
IDMSIFR
Severity:
0
Reason:
An attempt has been made to alter a constraint to UNIQUE however a column(s) included in the sort key was/were defined as ALLOW NULL.
Module:
IDMSIFR
Severity:
0
Reason:
IDMSULIO was called with an invalid function code. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
IDMSULIO was called to do the named function but no DDname was specified. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
IDMSULIO was called to do the named function for the DDNAME specified - but an error occurred calling the OpSys function.
Module:
IDMSULIO
Severity:
0
Reason:
IDMSULIO was called to do the named function for the DDNAME specified - but the file has not been opened. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
IDMSULIO was called to read from an output file or write to an input file. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
An error was discovered while opening the specified file. This is usually an internal error.
Following are some open error codes and their meaning.
100 File already open.
101 Tried to open native VSAM file.
102 Non-zero rc from RDJFCB.
103 Open Call Failed - did not open file.
104 Non-zero RC from GENCB exit list.
105 Non-zero RC from GENCB ACB input.
106 Non-zero RC from GENCB ACB output.
107 RC GT 4 from VSAM open.
108 Non-zero RC from SHOWCB after open ok.
109 Jrnl CI size diff from preceding jrnl.
110 Page size not less than CI-size - 7.
111 Page size not greater than 1/2 CI-size.
112 No record length supplied.
113 z/VSE open failed
114 Label function failed (z/VSE)
115 Invalid function
116 Invalid request for file
117 Invalid FCB passed
118 Invalid buffer address
119 No tape LUB supplied (z/VSE)
120 Unable to allocate I/O areas
Module:
IDMSULIO
Severity:
0
Reason:
An invalid DMCL FCB/JCB was passed for the requested function. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
A DMCL FCB/JCB must be passed for the requested function. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
Internal TCE stack overflowed. This is an internal error.
Module:
IDMSULIO, (Plus almost any utility)
Severity:
0
Reason:
IDMSULIO was passed an I/O buffer above the XA 16M line and the current file requires it to be below the line. This is an internal error.
Module:
IDMSULIO
Severity:
0
Reason:
An error occurred while trying to dynamically allocate a database file. The error code and info code are returned by IBMs SVC99 call.
Module:
IDMSULIO
Severity:
0
Reason:
An OS macro call failed for the named I/O function and file. The MACRO name and R15 Return code are displayed.
Module:
IDMSULIO
Severity:
0
Reason:
An attempt was made to write or read a record whose size is inconsistent with the Blocksize of the file. A fixed Length LRECL must be an even multiple of BLKSIZE. A variable Length LRECL must be at least four bytes smaller than the BLKSIZE.
Module:
IDMSULIO
Severity:
0
Reason:
This is a warning. RECFM=F and RECFM=V overrides were coded for the same filename. If the utility program does not specify RECFM, RECFM=V will be used.
Module:
IDMSULIO
Severity:
0
Reason:
This is a warning. The utility specified value will be used.
If the file-override value is RECFM, it means RECFM=F was coded in SYSIDMS, but the utility program specified that the file must be variable record format, or RECFM=V was coded and the utility specified that the file was fixed record format.
If the file-override value is LRECL, it means the utility program is expecting a specific record size and the SYSIDMS LRECL coded is incompatible.
These overrides are intended for utilities that do not hardcode these values at compile time, but can handle file attribute overrides at run time.
Module:
IDMSULIO
Severity:
0
Reason:
Dynamic Allocation failed because the DSN was in use by another job. This job will wait until the DSN becomes available or the specified time interval passes.
Module:
RHDCALOC
Severity:
0
Reason:
A call to DBIO returned the specified error code. The requested function and current database page are displayed.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU, IDMSUTIL
Severity:
0
Reason:
A read of an invalid DBKEY was requested. Possible internal error. Possible bad dbkey in database.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
The root portion of a relocated record was found, but the relocated portion was not found. This is an error in the database. The SR2 dbkey indicates what was found. The SR3 dbkey either does not exist or is not an SR3.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
The named page has no SR1 record at Line 00.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
The record identified was read while walking the current set, but it was not defined to the set being walked. Any remaining records in the set are ignored. The set name and owner are identified in a subsequent message. Possible broken chain.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
The DBkey identified is the next record in the current set, but it does not exist. Any remaining records in the set are ignored. The set name and owner is identified in a subsequent message. Possible broken chain.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
An error described in a previous message was found while walking the identified set occurrence. Any remaining records in the set are ignored.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
The named area was not found in the generated FIB.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
An Itree node with specified type was found but is not supported by this module.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
The requested table is not defined in the generated FIB.
Module:
IDMSCOLS, IDMSUCUS, IDMSURSU
Severity:
0
Reason:
A request to the Lock manager returned an error code for the identified function and dbkey.
Module:
IDMSCOLS
Severity:
0
Reason:
A page was found with no Line-0 record. This should not happen. The job is abended.
Module:
IDMSCOLS
Severity:
0
Reason:
A request for storage of length zero was requested. The job is abended.
Module:
IDMSCOLS
Severity:
0
Reason:
The calculated DTREE storage length was exceeded. The job is abended.
Module:
IDMSCOLS
Severity:
0
Reason:
A routine requested a lock on a dbkey but the value was zero. The job is abended.
Module:
IDMSCOLS
Severity:
0
Reason:
A CR55 for a null indicator was found. There should be one for the data field also, but it was not found. The job is abended.
Module:
IDMSCOLS
Severity:
0
Reason:
The command being attempted is only applicable to areas defined for SQL (relational) access.
Module:
IDMSCOLS
Severity:
0
Reason:
UPDATE STATISTICS can not process a view or a table procedure.
Module:
IDMSCOLS
Severity:
0
Reason:
The identified function was requested. but it is not supported.
Module:
IDMSUTIL
Severity:
0
Reason:
The named function requires an IOP (DBIO control block) but none was provided.
Module:
IDMSUTIL
Severity:
0
Reason:
A request to lock the named area was made but the area's current lock mode prevents the requested lock from being acquired.
Module:
IDMSUTIL
Severity:
0
Reason:
The named area or page number was not found in the DMCL.
Module:
IDMSUTIL
Severity:
0
Reason:
The named file was not found in the DMCL.
Module:
IDMSUTIL
Severity:
0
Reason:
A request was made to lock a database page buffer, but the max of 4 had already been locked.
Module:
IDMSUTIL
Severity:
0
Reason:
A request to lock the current database page buffer failed because there is no current buffer.
Module:
IDMSUTIL
Severity:
0
Reason:
The parmlist passed was invalid for the named function.
Module:
IDMSUTIL
Severity:
0
Reason:
A request to write a DB page was issued. But the page is not in a locked buffer.
Module:
IDMSUTIL
Severity:
0
Reason:
The named database segment was not found in the current runtime DMCL.
Module:
IDMSUTIL
Severity:
0
Reason:
A user written CALC exit returned a target page outside the specified page range.
Module:
IDMSUTIL
Severity:
0
Reason:
The MR53 passed on a CALC request was not for a calc record.
Module:
IDMSUTIL
Severity:
0
Reason:
A calc request was made for an index name, but its OR52 could not be found.
Module:
IDMSUTIL
Severity:
0
Reason:
The MR53 passed on the calc request is not associated with a particular area and is not supported.
Module:
IDMSUTIL
Severity:
0
Reason:
The named subarea was not found in the named area.
Module:
IDMSUTIL
Severity:
0
Reason:
A security check denied access to the requested resource
Module:
IDMSUTIL
Severity:
0
Reason:
A request requiring access to the LTE control block failed because there is no LTE associated with the current TCE.
Module:
IDMSUTIL
Severity:
0
Reason:
A request to unlock the named area was made but the area was not locked.
Module:
IDMSUTIL
Severity:
0
Reason:
A request to invalidate a synchronization stamp failed.This only happens in a data sharing environment. Possible reasons for the failure are:
Module:
IDMSUTIL
Severity:
0
Reason:
A verify or replace offset must be on a halfword boundary.
Module:
IDMSUPFX
Severity:
0
Reason:
The specified hex offset is larger than the database page.
Module:
IDMSUPFX
Severity:
0
Reason:
A verify value did not match the contents of the database page at the specified offset.
Module:
IDMSUPFX
Severity:
0
Reason:
The requested page range is invalid. The high page precedes the low page; or the low and high pages are not in the same area; or the page range is not in the requested area.
Module:
IDMSUPFX
Severity:
0
Reason:
Your site has chosen to apply an optional apar that prevents the use of the FIX PAGE utility.
Module:
IDMSUPFX
Severity:
0
Reason:
You are not allowed to do a REP on the SMP area lock field.
Module:
IDMSUPFX
Severity:
0
Reason:
Area lock mode unavailable for one or more areas.
Module:
IDMSUPFX
Severity:
0
C<sqlcode>M<module-number>:One or more areas were not locked.
Module:
IDMSUPFX
Severity:
0
Reason:
The specified SUBSCHEMA name or SEGMENT name is invalid. Refer to the console LOG for the specific error message that explains the reason for this error.
Module:
IDMSUIDX
Severity:
0
Reason:
Error occurred with MEMBER option with non-system-owned index
Module:
IDMSUIDX
Severity:
0
Reason:
Set name is not provided for FULL option, or the set is not an index set.
Module:
IDMSUIDX
Severity:
0
Reason:
DBKey not found on page - may be broken chain.
Module:
IDMSUIDX
Severity:
0
Reason:
SR8 chain may be broken.
Module:
IDMSUIDX
Severity:
0
Reason:
While printing the contents of an SR8 Index record, the sequence check on symbolic key field(s) has been skipped. In order to do a sequence check, we need information on the symbolic key field(s) from the subschema, but not subschema has been provided in the syntax. Only a starting SR8 index record was provided.
Module:
IDMSUIDX
Severity:
0
Reason:
Member DBKey is not a valid entry into the index.
Module:
IDMSUIDX
Severity:
0
Reason:
SR8 DBKey not provided on input.
Module:
IDMSUIDX
Severity:
0
Reason:
While printing the contents of an SR8 index record, one or more symbolic keys were found to be out of sequence. These keys are identified with the literal "*SEQ*ERR*" in the Print Index report.
Module:
IDMSUIDX
Severity:
0
Reason:
While printing the contents of an SR8 Index record, the sequence check on the symbolic key field(s) was skipped. The symbolic key field(s) from the subschema is needed to do a sequence check, but only a starting SR8 index record was provided in the syntax.
Module:
IDMSUIDX
Severity:
0
Reason:
The area where the owner of the specified set resides did not bind to an area in the specified segment or DBNAME.
Ensure the correct segment or DBNAME was specified for the named set.
Module:
IDMSUIDX
Severity:
0
Reason:
The area where the member of the specified set resides did not bind to an area in the specified segment or DBNAME, and access to the member area is required for the current processing option.
Ensure the correct segment or DBNAME was specified for the named set.
Module:
IDMSUIDX
Severity:
0
Reason:
The owner of the specifed set does not reside in the specified segment. It was bound to a different segment.
Ensure the correct segment or DBNAME was specified for the named set.
Module:
IDMSUIDX
Severity:
0
Reason:
The owner dbkey of a system index was specified and the internal index name found in the database does not match the internal index name for the requested set. The internal set name found is displayed with the dbkey used to find the set owner. The internal name may be the same as the set name or may be in the form INDEX-NNNNNNNNNN, where NNNNNNNNNN is a number assigned to the index.
Ensure the correct set name, table-name, and dbkey were specified.
Module:
IDMSUIDX
Severity:
0
Reason:
The specified owner or member dbkey was found but the record type is not defined to the index set being printed. The name of the record is displayed if it can be identified, otherwise the record type will be displayed.
Ensure the correct set name, table-name, and dbkey were specified.
Module:
IDMSUIDX
Severity:
0
Reason:
The specified owner or member dbkey is not in range for the named index or record.
Ensure the correct set name and dbkey were specified.
Module:
IDMSUIDX
Severity:
0
Reason:
The specified DMCL entity (area, file, etc.) is not in the DMCL.
Module:
IDMSUFMT, IDMSUPSP
Severity:
0
Reason:
The specified file contains multiple areas and the areas are not attached to the file in contiguous RBN sequence.
Module:
IDMSUFMT
Severity:
0
Reason:
The identified option is not supported.
Module:
IDMSUFMT
Severity:
0
Reason:
Mismatch of header information detected.
Module:
IDMSUFMT
Severity:
0
Reason:
The page size of the target SYSTRK file is out of the valid range of 4,088 and 32,674. The most likely cause is that the JCL blocksize is incorrect.
Module:
IDMSUFMT
Severity:
0
Reason:
A #SYSTRK call returned an unexpected return code.
Module:
IDMSUFMT
Severity:
0
Reason:
The specified file has not been found. Check JCL file definition.
Module:
IDMSUFMT
Severity:
0
Reason:
SYSTRK FILE SIZE is invalid. This can be caused by omitting the INITIAL keyword when formatting new SYSTRK files.
Module:
IDMSUFMT
Severity:
0
Reason:
Formatting the LIKE file is not allowed. But processing will continue if there are additional DD names specified.
Module:
IDMSUFMT
Severity:
0
Reason:
The specified file does not look like a valid SYSTRK file.
Module:
IDMSUFMT
Severity:
0
Reason:
The specified DD was formatted, but because of a difference between the LIKE file and the formatted file, the contents could not be copied. Look for more detailed messages in the body of the report.
Module:
IDMSUFMT
Severity:
0
Reason:
An unexpected situation has been detected.
Module:
IDMSUPSP
Severity:
0
Reason:
The archive file contains an invalid header. Either the file was not created by Backup or it has been corrupted.
Module:
IDMSURST
Severity:
0
Reason:
An AREA/FILE restore was requested but the archive file was not created using the AREA/FILE option.
Module:
IDMSURST
Severity:
0
Reason:
The archive file was created in a format that is unsupported by the current version of Restore. Possibly created by a later release of Backup.
Module:
IDMSURST
Severity:
0
Reason:
An unexpected record type was read from the archive file. Expected a control record.
Module:
IDMSURST
Severity:
0
Reason:
An error occurred that prevents the Backup or Restore from completing. The specific error is described in a previous message.
Module:
IDMSURST, IDMSUBKP
Severity:
0
Reason:
The control records indicated more DB pages should exist on the archive file than were found.
Module:
IDMSURST
Severity:
0
Reason:
The named file/area was not found on the archive file
Module:
IDMSURST
Severity:
0
Reason:
The named journal file was formatted with a different size than what is specified in the current DMCL. It cannot be processed.
Module:
IDMSUAJN
Severity:
0
Reason:
One or more journals had the 'CV active' flag on. ARCHIVE JOURNAL ALL/FULL may only be specified when CV is shut down.
Module:
IDMSUAJN
Severity:
0
Reason:
The selected file received an error during the CLOSE Status. Restart the ARCHIVE, as the output tape is bad.
Module:
IDMSUAJN
Severity:
0
Reason:
The Journals were formatted with a version of CA IDMS unsupported by this version of Archive Journal.
Module:
IDMSUAJN
Severity:
0
Reason:
When reading archive journal input, a journal record was encountered for a run unit for which no BGIN record exists. This can be an expected situation, however, it also might indicate that the input provided is incomplete.
Module:
IDMSUPJN, IDMSURJN
Severity:
0
Reason:
An unsupported archive option code was specified in the command node.
Module:
IDMSUAJN
Severity:
0
Reason:
The specified file (FCB/JCB) could not be found in the DMCL.
Module:
IDMSUAJN, IDMSUPJN, IDMSURJN
Severity:
0
Reason:
The segment location table contained in the JHDS records in the journal header contained an unexpected value.
Module:
IDMSUAJN
Severity:
0
Reason:
The named journal file contains out of sequence journal records. A preceding message will give more detailed information.
Module:
IDMSUAJN, IDMSUPJN, IDMSURJN
Severity:
0
Reason:
The previous time record had a later time than the current one. This is just a warning. A common cause is daylight-savings.
Module:
IDMSUPJN
Severity:
0
Reason:
The name file was selected with a Restart option, but the file was not in a offload or condense status.
Module:
IDMSUAJN
Severity:
0
Reason:
The named journal file was dummied or ignored in the JCL. It cannot be processed.
Module:
IDMSUAJN
Severity:
0
Reason:
The selected file was found to be in a Condense or Offload Status. Restart needs to be specified in order to process it.
Module:
IDMSUAJN
Severity:
0
Reason:
The named file is active and cannot be offloaded.
Module:
IDMSUAJN
Severity:
0
Reason:
The current segment in the named journal file is empty. There is nothing to offload.
Module:
IDMSUAJN
Severity:
0
Reason:
The selected journal file is currently being offloaded or condensed by another archive journal job.
Module:
IDMSUAJN
Severity:
0
Reason:
After the condense completed, a check found the low RBN for the new current segment was not 1 less than the next available RBN in the segment.
Module:
IDMSUAJN
Severity:
0
Reason:
All Inactive journals were either empty or already being offloaded by other Archive journal jobs.
Module:
IDMSUAJN
Severity:
0
Reason:
The Archive Journal function has been terminated. ErrorCode is an internal code that describes the error. This code may also show up on a DCMT Display Journal line for the journal file where the error occurred. Error codes:
Module:
IDMSUAJN
Severity:
0
Reason:
There is not enough room left in the journal file to write out the active run unit table.
Module:
IDMSUAJN
Severity:
0
Reason:
The number of concurrent run units has exceeded the maximum capacity of the current program.
Module:
IDMSURJN, IDMSUPJN
Severity:
0
Reason:
The named type found on the journal file is not supported.
Module:
IDMSURJN, IDMSUPJN
Severity:
0
Reason:
A before/after image for the named dbkey did not match the image on the database.
Module:
IDMSURJN
Severity:
0
Reason:
The SORT option was specified and a KSDS record was found. Rollback/Rollforward does not support the SORT option for KSDS native VSAM files. The sequential option must be used.
Module:
IDMSURJN
Severity:
0
Reason:
An abort checkpoint was found for the identified run unit by rollforward, but no begin checkpoint was found for this run unit on the archive file. After images for the run unit have been applied but cannot be restored. Probable cause is the begin checkpoint exists on an earlier archive file. Rerun the job including the earlier archive file.
Module:
IDMSURJN
Severity:
0
Reason:
An aborted run unit has been rolled out during a Rollforward process, but the attempt to reposition the archive file back to the point where the abort checkpoint was found failed. End-of-file was reached before the saved sequence number was found A previous message will contain more information.
Module:
IDMSURJN
Severity:
0
Reason:
The beginning of the archive file was reached before finding a begin or commit checkpoint for the run unit being rolled out.
Module:
IDMSURJN
Severity:
0
Reason:
An attempt to map a journal image to a database page failed because there was insufficient room on the database page to store it. If the sort option is specified the recovery stops because this condition should not occur. If the sequential option is used the record is saved with the assumption room will open up later. This error is issued when all other images have been applied and there is still no room for the image.
Module:
IDMSURJN
Severity:
0
Reason:
A call to IDMSAREC returned an error status.
Module:
IDMSURJN
Severity:
0
Reason:
ROLLFORWARD .. START AT <date-time stamp> was requested.The specified date-time stamp should specify a point in time at which the area(s) being recovered is quiesced. This was not the case. Preceding messages will indicate which areas are not quiesced.
Module:
IDMSURJN
Severity:
0
Reason:
A journal record for the named page was found, but the page is not defined in the current DMCL.
Module:
IDMSURJN
Severity:
0
Reason:
A BGIN/ENDJ was found with a run unit id the same as one in the current run unit table. This is considered an internal error and the job is abended.
Module:
IDMSURJN
Severity:
0
Reason:
The journal file contains data from more than one datasharing member or multiple tape journals. This is the list of conditions under which IDMSBCF statements ROLLBACK, ROLLFORWARD and EXTRACT JOURNAL mandate an archive journal created by the IDMSBCF command MERGE ARCHIVE COMPLETE in order to be able to correctly process the requested function:
Run the IDMSBCF command MERGE ARCHIVE COMPLETE and use its output to do the ROLLBACK, ROLLFORWARD or EXTRACT JOURNAL.
Module:
IDMSURJN
Severity:
0
Reason:
An error occurred while trying to rewrite the journal header block. Additional messages should precede this one.
Module:
IDMSUAJN
Severity:
0
Reason:
Zero tape blocks were written during offload process.
Module:
IDMSUAJN
Severity:
0
Reason:
A request to print the identified message number passed an invalid token type code. This is an internal program error.
Module:
IDMSMSGM
Severity:
0
Reason:
A request to print the identified message number and token type passed an invalid token length. This is an internal program error.
Module:
IDMSMSGM
Severity:
0
Reason:
A request to print the identified message number passed more tokens than can be handled. This is an internal program error.
Module:
IDMSMSGM
Severity:
0
Reason:
An ARCHIVE TRACE statement was issued but there is no DDLDCTRC area. Use the ARCHIVE LOG statement instead.
Module:
RHDCPTRC
Severity:
0
Reason:
A PRINT TRACE statement was issued but too many DDNAMEs were specified. The maximum number of DDNAMEs you can specify is 32.
Module:
RHDCPTRC
Severity:
0
C<sqlcode>M<module-number>:Too many TASKIDs specified on PRINT TRACE command
Reason:
A PRINT TRACE statement was issued but too many TASKIDs were specified. The maximum number of TASKIDs you can specify is 32.
Module:
RHDCPTRC
Severity:
0
Reason:
The expand page request ended prematurely. A previous message will contain the exact reason.
Module:
IDMSUXPG
Severity:
0
Reason:
An SMP page was found when none was expected or an expected SMP page was not an SMP page. The area and page where the error was detected is displayed. The current SMI based on clause in the PR60 does not match the area.
Module:
IDMSUXPG
Severity:
0
Reason:
The requested new page size was not larger than the old page size.
Module:
IDMSUXPG
Severity:
0
Reason:
The requested page size must be a multiple of 4 bytes.
Module:
IDMSUXPG
Severity:
0
Reason:
The page identified by file and number failed the corner check. The page number in the header did not match the page number in the footer or was not the expected page.
Module:
IDMSUXPG
Severity:
0
Reason:
The current utility request ended prematurely. A previous message will contain the exact reason.
Module:
IDMSURSU, IDMSUCUS
Severity:
0
Reason:
An error was detected during the processing of the requested utility function. A previous message will provide the details.
Module:
IDMSURSU
Severity:
0
Reason:
The record at dbkey was larger than expected and overflowed a work buffer. Possible previously expanded record read, or subschema description out of sync with database.
Module:
IDMSURSU
Severity:
0
Reason:
The control record needed by the DBLx programs was not the first record in the input data or was invalid. Input data may not have been sorted properly.
Module:
IDMSDBL2, IDMSDBL3, IDMSDBL4
Severity:
0
Reason:
The input data is not in the expected sequence . Input data may not have been sorted properly.
Module:
IDMSDBL2, IDMSDBL3, IDMSDBL4
Severity:
0
Reason:
The input file is empty. At least the control record must be there. Possible JCL error, or wrong input file provided.
Module:
IDMSDBL2, IDMSDBL3, IDMSDBL4
Severity:
0
Reason:
The UNLOAD specified a DMCL that was to be used for the reload phase and the unloaded data was formatted based on that DMCL. But the reload step found a different DMCL in use. Either unload the data with the correct DMCL name or specify the reload DMCL in the SYSIDMS parms.
Module:
IDMSDBL2, IDMSDBL3, IDMSDBL4
Severity:
0
Reason:
The BIND RUN-UNIT failed with the named code. The subschema, DMCL, and database name are identified.
Module:
IDMSDBL2, IDMSDBL3, IDMSDBL4
Severity:
0
Reason:
There is no REORG task that can be started because it conflicts with the STOP AFTER phase that was specified.
Module:
IDMSDBXD
Severity:
0
Reason:
The DIVIDE PROCESSING <divide-number> WAYS clause exceeds the maximum size allowed by the REORG utility.
Module:
IDMSDBXD
Severity:
0
Reason:
An input file was missing a trailer record. The file may be missing data.
Module:
IDMSDBXY
Severity:
0
Reason:
The input data does not match the requested function. Either Fastload data was used as input to a Reload or visa versa.
Module:
IDMSDBL2
Severity:
0
Reason:
The named module encountered an error or warning condition. The exact reason should have been displayed in a previous message.
Module:
IDMSDBL2, IDMSDBL3, IDMSDBL4, IDMSDBLX, IDMSDBLD, IDMSDBL1, IDMSUNL1, IDMSTABD, IDMSTABX, IDMSDBLY, IDMSDBXD
Severity:
0
Reason:
The named step was specified as a restart or step-mode step. But this step is not a valid choice.
Module:
IDMSDBLD, IDMSTABD
Severity:
0
Reason:
The named step was specified as a restart or step-mode step for FASTLOAD, but is valid only for RELOAD.
Module:
IDMSDBLD, IDMSTABD
Severity:
0
Reason:
End-of-file was reached on the named file, but the program expected more data or had not found the data it was looking for. Double check that the correct input file was used and verify it was identified properly in the JCL. Check for possible errors in the program that created the file.
Module:
IDMSDBLD
Severity:
0
Reason:
A request to build the named index was made but the index already contains entries. The index must be deleted before it can be built.
Module:
IDMSDBL3
Severity:
0
Reason:
A call to IDMSSORT failed. The requested function and return code are displayed. The return code was issued from the host systems SORT module. Usually a more specific error message is issued with the normal SORT output messages.
Module:
IDMSDBLY
Severity:
0
Reason:
The SORT FIELDS= parm card passed to DBLY was blank. Check the sort parm input file for blank cards. If it is OK then this could be an internal program error.
Module:
IDMSDBLY
Severity:
0
Reason:
An input file was missing a header record, or the contents of the header record did not match the DDname being read.
Module:
IDMSDBLY
Severity:
0
Reason:
The REORG utility detected a STOP AFTER clause conflict. A previous STOP AFTER <phase-name> is already in affect.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility detected a CREATE <work-file-type> WORKFILES clause conflict. A previous CREATE <work-file-type> WORKFILES is already in affect.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility was not able to open the RORGCTL file.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility tried to dynamically allocate a workfile, but the allocation failed. See the JES log for details.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility tried to dynamically deallocate a workfile, but the deallocation failed. See the JES log for details.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility found a reload subschema area that was not bound to an area in the DMCL. Check your DBNAME table to insure that the reload DBNAME specified contains all required segments.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility is trying to submit extra jobs to run in parallel with the manually submitted REORG job, but the RORGJCL file is empty or defined incorrectly. The RORGJCL must be FIXED length with an LRECL of 80.
Module:
IDMSDBXD
Severity:
0
Reason:
The REORG utility is trying unload the named record but after adding in overhead the resulting work record is greater than 32K and can not be written. This database must be offloaded using the Unload/Reload utility.
Module:
IDMSUNXD
Severity:
0
Reason:
A CONVERT CATALOG request has been successfully executed. The status will reflect NO CONVERSION REQUIRED if the catalog has already been converted or will produce counts, in the form CALC KEYS <n> TABLES <n> SYNTAX <n>, of the number of occurrences of the indicated type which were converted.
Module:
IDMSUCVT
Severity:
0
Reason:
The user either issued a utility command for which the user is not authorized or did not sign on before issuing the command. If appropriate, sign on to the DC/UCF system and reissue the command.
Module:
IDMSDDAM
Severity:
0
Reason:
The version of the table created by the #UTABGEN macro is not in sync with program that reads the table. Check if the table was generated by an older release and if so, regenerate the table using #UTABGEN from the current release.
Module:
IDMSDDAM
Severity:
0
Reason:
An attempt has been made to execute a utility statement that requires local mode processing in DC or batch CV.
Rerun the utility in local mode.
Module:
IDMSDDAM
Severity:
0
Reason:
See previous message for details on which error occurred.
Module:
IDMSLOAD
Severity:
0
Module:
IDMSUSYN
Severity:
0
Reason:
Only SQL segments and areas contain validation stamps, so processing is bypassed.
Module:
IDMSUSYN
Severity:
0
Reason:
An attempt has been made to change the security method for a type of resource to its current security method. No further action is necessary.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to alter or drop a group that has not been previously defined, or to associate a user with a group that has not been defined. Insure that the group authorization id has been correctly entered. If the group authorization id is correct define it using the CREATE GROUP statement.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to alter or drop an authorization ID that represents a user instead of a group. Check to ensure that the group authorization id has been correctly entered.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to create a group that has already been defined. Check to insure that the group authorization id has been correctly entered.
Module:
IDMSDSEC
Severity:
0
Reason:
While attempting to add or drop a user from the group the user authorization ID was determined to be nonexistent. Check to insure that the user authorization id has been correctly entered. If the user authorization id is correct, defined it using the CREATE USER statement before attempting to associate it with a group.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to add a user to a group that it is already associated with. No further action is necessary.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to create, alter, or drop a resource type that is unknown to the security system. Check the resource type specified to insure that it is valid.
Module:
IDMSDSEC
Severity:
0
Reason:
The category that is being altered or dropped has not been previously defined. Check to insure that the category name is valid.
Module:
IDMSDSEC
Severity:
0
Reason:
The indicated user has been granted a privilege on the category but the user definition is missing. This is a system internal error. If the user is SYSTEM check to insure that the security formatting utility was run during system installation. Otherwise, contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The indicated user has been granted a privilege on the category but the category map for the user is missing. This is a system internal error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The maximum number of categories that may be defined (32767) has been reached. Check to see whether any unused categories can be dropped before adding a new category.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to define a category that already exists. Check to insure that the correct category name has been specified before proceeding.
Module:
IDMSDSEC
Severity:
0
Reason:
The category bitmap for the indicated authorization id has been corrupted. During processing it was determined that a bit that was to be enabled or disabled was already enabled or disabled. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The resource to be added or dropped from a category has not been previously defined. Check to insure that the resource name has been correctly entered.
Module:
IDMSDSEC
Severity:
0
Reason:
The named resource has already been defined as part of another category. Resources may be associated with only a single category at a time. Check the resource name to insure that it is correct.
Module:
IDMSDSEC
Severity:
0
Reason:
The specified function number is invalid because it is not between 1 and 256.
Module:
IDMSDSEC
Severity:
0
Reason:
The application named in an ALTER or DROP RESOURCE FUNCTION statement has not been previously defined. Check the application name to insure that it has been specified correctly.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to alter a system managed function number has been made. Function numbers that are system maintained may not be altered.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to alter or drop a function that has not previously been defined has been made. Check the function name to insure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to change a functions number to the same value. Check the new function number to insure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to alter the indicated application has encountered no functions. This is an internal system error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The function bitmap for the indicated authorization id has been corrupted. During processing it was determined that a bit that was to be enabled or disabled was already enabled or disabled. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The function to be created has previously been defined. Check the function name to insure that is has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to assign a function number that has already been allocated to another function within the application. Check the function number to insure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to acquire the function map for the indicated user has failed. This is an internal system error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The indicated resource cannot be found. Check the resource type and name to insure that they have been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to create the indicated resource has failed because it has previously been defined.
Module:
IDMSDSEC
Severity:
0
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to alter or drop a system has failed because the system has not previously been defined. Check the system name to insure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to alter or drop a user has failed because the specified authorization id defines a group and not a user. Check the user name to ensure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to drop a user from a group has failed because the user had not been previously associated with the group.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to create a user has failed because the user has already been defined. This message displays one of the following status codes:
Check the user authorization ID to ensure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to alter or drop a user has failed because the user has not been previously defined. Check the user authorization id to ensure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
The indicated resource could not be located. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
During the execution of a DROP USER statement a privilege on either a CATEGORY or FUNCTION was found but the definition of the category or function was not found. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
Wildcarding is not allowed in catalog, dictionary, or library names. Specify only fully qualified catalog, dictionary, or library names.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to transfer ownership of a schema has failed because the schema has not been previously defined. Check the schema name to ensure it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to GRANT privileges to an authorization id has failed because an invalid privilege has been specified. The expected privileges are GRPADMIN, SYSADMIN, or USRADMIN.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to process a GRANT statement has failed because an invalid resource type has been specified. Check the resource type to ensure that it has been correctly specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to process a REVOKE statement has failed because the privilege had not been granted. This is most likely the result of revoking a privilege that has not been previously granted, or which has already been revoked.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to process a GRANT statement has failed because an authorization was for a different authorization id. This is an internal system error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt to process a GRANT statement has failed because the function bitmap is for an authorization id that is different from the one that is currently being processed. This is an internal system error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
This is an internal system error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
The user is not authorized to issue the statement. Contact the customer Security Officer for additional assistance.
Module:
IDMSDSEC
Severity:
0
Reason:
An unexpected error has occurred during security validation. See the CA IDMS/DB Messages and Codes to determine the cause of the error.
Module:
IDMSDSEC
Severity:
0
Reason:
This is an internal system error. Contact Technical Support.
Module:
IDMSDSEC
Severity:
0
Reason:
No authorization ids have been specified in the TO/FROM clause of a GRANT/REVOKE statement, or, the TO/FROM clause has not been specified.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to drop the PUBLIC group. This action is prohibited since the PUBLIC group must always exist.
Module:
IDMSDSEC
Severity:
0
Reason:
An attempt has been made to drop the SYSTEM user. This action is prohibited since the SYSTEM user must always exist.
Module:
IDMSDSEC
Severity:
0
Reason:
The specified DSN value is not valid.
Module:
IDMSDDSM
Severity:
0
Reason:
The specified DSN contains the invalid substitution parameter identified as <parm>. <rsn> indicates the nature the error:
Unknown keyword <parm> is an unrecognizable substitution parameter.
Invalid substring start <parm> is specified as a substring whose start value is not valid. It may be beyond the length of a value of the specified parameter type.
Invalid substring length <parm> is specified as a substring whose length value is not valid. Together with the starting position, it may be extend beyond the end of a value of the specified parameter type.
Module:
IDMSDDSM
Severity:
0
Reason:
UPDATE STATISTICS has been run against an area that does not contain any tables. There is nothing to process. Verify a CONNECT has been issued to the correct catalog and that the area specified contains tables.
Module:
IDMSDSTA
Severity:
0
Reason:
UPDATE STATISTICS has been run using an SQL-defined schema that references a non-SQL-defined schema.The non-SQL-defined schema contains the non-SQL record <record-name> and the system owned index set <set-name> that has a group element as part of the index key.In this case column statistics are only collected for the first column of the index key.
Module:
IDMSDSTA
Severity:
0
Reason:
The named occurrence has not been defined.
Module:
IDMSDSEG, IDMSDDMC, IDMSDDMG, IDMSDDSM
Severity:
0
Reason:
No occurrence of the indicated entity-type is current.Unqualified occurrence-name must be qualified by a valid occurrence-name of the indicated entity-type to establish processing currency.
Module:
IDMSDSEG, IDMSDDMC
Severity:
0
Reason:
The indicated definition already exists.Duplicate occurrences are not allowed.
Module:
IDMSDSEG, IDMSDDMC, IDMSDDSM
Severity:
0
Reason:
The indicated occurrence has been found in the catalog but is not the same type as requested. Example: Requested a Disk Journal but found an Archive Journal for the requested name.
Module:
IDMSDDMC
Severity:
0
Reason:
Only one occurrence of the named entity-type may be defined under the current component. Example: a DMCL can contain only one Journal Buffer.
Module:
IDMSDDMC
Severity:
0
Reason:
A DROP/DELETE SEGMENT request has been denied. One or more active AREA definition(s), containing TABLE and/or INDEX definitions, exist within the SEGMENT. This message will be preceded by message DB004037 for each identified AREA.
Module:
IDMSDSEG
Severity:
0
Reason:
The value identified has not been established for the named occurrence and is required before the DMCL can be generated (warning).
Module:
IDMSDDMC
Severity:
0
Reason:
The indicated field, either a SHARED CACHE for DMCL File Override or DATA SHARING for DMCL Area Override has been specified for a DDLDCLOG or DDLDCSCR area and will be ignored. Shared Cache does not apply to these areas (warning).
Module:
IDMSDDMC
Severity:
0
Reason:
The SCHEMA specified as the restricted schema for the current SEGMENT has not been defined in the catalog and will be ignored. (Warning).
Module:
IDMSDSEG
Severity:
0
Reason:
The PAGE GROUP specified for the current SEGMENT is not valid.
Module:
IDMSDSEG
Severity:
0
Reason:
The RECORDS PER PAGE specified for the current SEGMENT is not valid.
Module:
IDMSDSEG
Severity:
0
Reason:
The PAGE RESERVE specified for the named AREA is not valid.
Module:
IDMSDSEG, IDMSDDMC
Severity:
0
Reason:
MAXIMUM SPACE for a Native VSAM AREA must be the same as the PRIMARY SPACE for the AREA. Clause ignored (Warning).
Module:
IDMSDSEG
Severity:
0
Reason:
PAGE SIZE of the current AREA cannot be modified. AREA maps to a FILE which is mapped to other AREA(s). The PAGE SIZE of all areas mapped to a single File must be the same.
Module:
IDMSDSEG
Severity:
0
Reason:
The maximum high page number which is valid with the specified MAXIMUM RECORDS PER PAGE for the SEGMENT is less than the Maximum High Page Number assigned to an AREA within the SEGMENT.
Module:
IDMSDSEG
Severity:
0
Reason:
A request to increase the MAXIMUM SPACE of an AREA is denied- the page range required to expand the allocation is not available.
Module:
IDMSDSEG
Severity:
0
Reason:
The PAGE SIZE for the current component is missing or invalid.
Module:
IDMSDSEG, IDMSDDMC
Severity:
0
Reason:
The PAGE SIZE specified for the current component is not a multiple of the indicated value (that is, 4/8/12).
Module:
IDMSDSEG, IDMSDDMC
Severity:
0
Reason:
The required page count indicated has not been specified or is not valid.
Module:
IDMSDDMC
Severity:
0
Reason:
The KEY LENGTH specified for a Native VSAM LSR Buffer is invalid.
Module:
IDMSDDMC
Severity:
0
Reason:
The BUFNI specified for a Native VSAM NSR Buffer is invalid.
Module:
IDMSDDMC
Severity:
0
Reason:
The STRNO specified for a Native VSAM Buffer (LSR or NSR)is invalid.
Module:
IDMSDDMC
Severity:
0
Reason:
No JOURNAL BUFFER has been defined for the DMCL. A Journal Buffer is required before the DMCL can be GENERATEd.
Module:
IDMSDDMC
Severity:
0
Reason:
The IDMS STORAGE specified for a Native VSAM BUFFER is not supported and has been changed to OPSYS STORAGE (Warning).
Module:
IDMSDDMC
Severity:
0
Reason:
DATASPACE has been specified on a DMCL File Override for a Native VSAM File. Dataspace cannot be used for Native VSAM Files and will be ignored. (Warning)
Module:
IDMSDDMC
Severity:
0
Reason:
The block size assigned to multiple Archive Journals must be the same for all ARCHIVE JOURNALs.
Module:
IDMSDDMC
Severity:
0
Reason:
Required BLOCK COUNT has not been specified or is invalid.
Module:
IDMSDDMC
Severity:
0
Reason:
Required BLOCK SIZE has not been specified or is invalid.
Module:
IDMSDDMC
Severity:
0
Reason:
Required external-name (DDName/Linkname/Filename) has not been supplied or is invalid.
Module:
IDMSDDMC, IDMSDDMG
Severity:
0
Reason:
The specified VIRTUAL ADDRESS is invalid.
Module:
IDMSDSEG
Severity:
0
Reason:
The specified access method is invalid.
Module:
IDMSDSEG, IDMSDDMC
Severity:
0
Reason:
The indicated journal type is not allowed in context with previously defined journals. TAPE JOURNAL cannot be defined if DISK and/or ARCHIVE JOURNALs have been defined; DISK and/or ARCHIVE JOURNALs cannot be defined if TAPE JOURNAL has been defined.
Module:
IDMSDDMC
Severity:
0
Reason:
DISK JOURNAL(s) have been defined in the DMCL and no ARCHIVE JOURNAL(s) has been defined. An ARCHIVE JOURNAL is required before the DMCL can be GENERATEd (warning).
Module:
IDMSDDMC
Severity:
0
Reason:
A request to DROP the named occurrence is denied. The occurrence contains active definitions: FILE has been mapped to one or more AREA(s); AREA contains active TABLE, VIEW and/or INDEX definition(s).
Module:
IDMSDSEG
Severity:
0
Reason:
The number of pages requested in an EXTEND SPACE exceeds the number of unallocated pages for the AREA.
Module:
IDMSDSEG
Severity:
0
Reason:
The start-page or calculated end-page number is not 2 thru the highest allowable page number for the maximum records per page or the start-page is not less than the calculated end-page.
Module:
IDMSDSEG
Severity:
0
Reason:
The number of pages specified in the PRIMARY SPACE exceeds the number of pages specified in the MAXIMUM SPACE clause.
Module:
IDMSDSEG
Severity:
0
Reason:
The ORIGINAL PAGE SIZE specified for the AREA is not a valid page size or is greater than the PAGE SIZE of the AREA.
Module:
IDMSDSEG
Severity:
0
Reason:
The required PRIMARY SPACE clause for the AREA has not been specified.
Module:
IDMSDSEG
Severity:
0
Reason:
The number of blocks specified on a WITHIN FILE request for the named file exceeds the number of pages available in the area. The total number of assigned blocks for all Files mapped to the Area cannot exceed the number of pages in the primary space for the Area.
This message may be produced when a file assignment is attempted that conflicts with existing file assignment(s). It may be necessary to issue EXCLUDE FILE statement(s) to remove the conflicting assignment(s) before issuing the WITHIN FILE statement receiving this error.
Module:
IDMSDSEG
Severity:
0
Reason:
The page range specified for the named occurrence is not within the limits for the current Area.
Module:
IDMSDSEG
Severity:
0
Reason:
The number of pages specified for the named occurrence is not within the limits for the current Area.
Module:
IDMSDSEG
Severity:
0
Reason:
The percentage specified for the named occurrence is not valid.
Module:
IDMSDSEG
Severity:
0
Reason:
The key length specified for the named occurrence is not valid.
Module:
IDMSDSEG
Severity:
0
Reason:
The index count specified for the named occurrence is not valid.
Module:
IDMSDSEG
Severity:
0
Reason:
The key count specified for the named occurrence is not valid.
Module:
IDMSDSEG
Severity:
0
Reason:
No occurrences of the indicated required entity type have been defined in the DMCL.
Module:
IDMSDDMG
Severity:
0
Reason:
No occurrences of the indicated entity type have been defined in the named DMCL component.
Module:
IDMSDDMG
Severity:
0
Reason:
The external-name assigned to the identified component duplicates an external-name assigned to a Journal file in the DMCL.
Module:
IDMSDDMG
Severity:
0
Reason:
The external-name assigned to the identified component duplicates an external-name assigned to a File in the DMCL.
Module:
IDMSDDMG
Severity:
0
Reason:
No external name has been provided for the named file and no dynamic allocation information is available.
Module:
IDMSDDMG
Severity:
0
Reason:
No occurrence(s) of the required entity-type indicated have been defined in the DMCL.
Module:
IDMSDDMG
Severity:
0
Reason:
Definitions of the indicated entity-types are not allowed coexistent in the same DMCL.
Module:
IDMSDDMC
Severity:
0
Reason:
The indicated default buffer for the named occurrence has not been defined in the catalog and will be ignored (warning).
Module:
IDMSDDMC, IDMSDDMG
Severity:
0
Reason:
No buffer assignment has been provided for the named file.A BUFFER assignment, either explicit or using defaults established for the DMCL or SEGMENT, is required for each file in the DMCL.
Module:
IDMSDDMG
Severity:
0
Reason:
The page size of the buffer associated with the named file is not large enough to contain the block size of the file (page size of the area(s) mapped to the file).
Module:
IDMSDDMG
Severity:
0
Reason:
The named Native VSAM file has been associated with a BUFFER which is not identified as Native VSAM.
Module:
IDMSDDMG
Severity:
0
Reason:
The named non-Native VSAM file has been associated with a Native VSAM Buffer.
Module:
IDMSDDMG
Severity:
0
Reason:
The named Native VSAM area maps to Native VSAM file(s) which must be assigned to the same Native VSAM BUFFER.
Module:
IDMSDDMG
Severity:
0
Reason:
The set-name specified in the named Native VSAM File duplicates the set-name specified in another Native VSAM File within the Segment. Set-name must be unique within the Segment.
Module:
IDMSDDMG
Severity:
0
Reason:
The indicated page range assigned to the named area within the identified page group duplicates the page range assigned to another area within the Segment or DMCL. Each page group /page range must be unique within the Segment and must be unique within the DMCL.
Module:
IDMSDSEG, IDMSDDMG
Severity:
0
Reason:
The indicated page range associated with the named area has not been mapped to any file(s).
Module:
IDMSDSEG (W), IDMSDDMG (E)
Severity:
0
Reason:
The block size assigned to the Archive Journal cannot be less than the page size assigned to the Disk Journal(s). Since the page size of Disk Journal(s) is determined by the Journal Buffer Page Size, that value will be assigned to the Archive Journal as well.
Module:
IDMSDDMG
Severity:
0
Reason:
The named area maps to multiple files and can map only to one KSDS, ESDS or RRDS File.
Module:
IDMSDSEG, IDMSDDMG
Severity:
0
Reason:
The named area maps to both a PATH and a KSDS Native VSAM File and each File has been identified as FOR CALC. Only one File mapped to the area can be identified FOR CALC.
Module:
IDMSDSEG, IDMSDDMG
Severity:
0
Reason:
The named file has been mapped to one or more areas and the indicated block range has been duplicated or overlaps.
Module:
IDMSDSEG, IDMSDDMG
Severity:
0
Reason:
The named file block range has not been mapped to any area. This error is produced when a gap is detected between the block ranges of a file. All blocks of the file must be mapped.
Module:
IDMSDSEG, IDMSDDMG
Severity:
0
Reason:
The named Native VSAM File can map to only one area.
Module:
IDMSDSEG
Severity:
0
Reason:
The named file specified in an area WITHIN FILE is a Native VSAM PATH File.
Module:
IDMSDSEG
Severity:
0
Reason:
The named file specified in an area WITHIN PATH FILE is not a Native VSAM PATH File.
Module:
IDMSDSEG
Severity:
0
Reason:
The WITHIN FILE for the named file specified for an EXTEND SPACE of the area does not contain required block mapping information.
Module:
IDMSDSEG
Severity:
0
Reason:
The MAXIMUM RECORDS PER PAGE specified for the named segment must be the same as the Maximum Records Per Page specified for all Segments within the Page Group.
Module:
IDMSDDMG
Severity:
0
Reason:
The External Name associated with the named occurrence is not valid for DOS systems: external name must be 7 characters; if tape journal, must be in the form SYSnnn.
Module:
IDMSDDMG
Severity:
0
Reason:
The internal count for the identified type in the named segment is inconsistent with the number of occurrences of that type in the segment definition. Contact Technical Support.
To correct the count(s), the SEGMENT definition must be deleted from the catalog, re-added to the catalog, and must be included again within each DMCL in which it resides.
Module:
IDMSDDMG
Severity:
0
Reason:
For IBM Operating Systems, a dataset name has been specified which exceeds the maximum allowable length of 44 characters.
Module:
IDMSDDMG
Severity:
0
Reason:
The Page Size of the indicated area is invalid. For Native VSAM Areas, page size must be 0; for all other Areas, page size must be in the range 48-32764 and a multiple of 4.
The File(s) associated with the Area have been changed from Native VSAM to non-Native VSAM or vice versa without also modifying the associated Area(s) page size.
Module:
IDMSDDMG
Severity:
0
Reason:
The identified occurrence has been removed from the indicated DMCL(s). This is a warning-level message because re-adding the occurrence may require re-inclusion in the indicated DMCL(s).
Severity:
0
Module:
IDMSDSEG
Reason:
Data Sharing has been specified for the DMCL, but either the Default Shared Cache name is blank and/or the number of Lock Entries is not greater than 0 and/or the number of Members is not greater than 0.
If any Data Sharing value is specified, all values must be provided.
Severity:
0
Module:
IDMSDDMC
Reason:
The indicated area in the DMCL has been defined with DATA SHARING YES, either explicitly or by default, but the DMCL does not contain a Default Shared Cache name.
If any area in the DMCL is subject to data sharing, the DMCL must identify a Shared Cache name to be used as a default.
This message is a Warning on an ALTER DMCL command but indicates an Error on a GENERATE DMCL command.
Severity:
0
Reason:
On a CREATE AREA, or ALTER AREA, the TIMESTAMP syntax is only allowed if stamping by AREA.
Severity:
0
Module:
IDMSDSEG
Reason:
File Audit table exceeded.
Module:
IDMSDSEG
Severity:
0
Module:
IDMSDDMG
Severity:
0
Reason:
Storage acquired to build the DMCL load module was insufficient.
Module:
IDMSDDMG
Severity:
0
Module:
IDMSDDMG
Severity:
0
Module:
IDMSDDMG
Severity:
0
Module:
IDMSDSEG
Severity:
0
Reason:
The maximum number of the indicated entity has been exceeded during DMCL generate.
Module:
IDMSDDMG
Severity:
0
Reason:
One or more critical errors have been detected during the DMCL GENERATE process. No DMCL load module will be stored.
Module:
IDMSDDMG
Severity:
0
Reason:
The named DBTABLE has not been defined in the catalog.
Module:
IDMSDDBT
Severity:
0
Reason:
The indicated occurrence has not been defined in the catalog.
Module:
IDMSDDBT
Severity:
0
Reason:
The named occurrence has already been defined in the catalog. Duplicate occurrences are not allowed.
Module:
IDMSDDBT
Severity:
0
Reason:
No operations may be requested for the *DEFAULT DBName.
Module:
IDMSDDBT
Severity:
0
Reason:
No occurrence of the indicated entity-type is current.Unqualified occurrence-name must be qualified by a valid occurrence-name of the indicated entity-type to establish processing currency.
Module:
IDMSDDBT
Severity:
0
Reason:
The first (or only) subschema mapping for the specified DBNAME forces all subschemas to use DBTABLE mapping. While not illegal, this situation should be reviewed.
Module:
IDMSDDBT
Severity:
0
Reason:
The mapping for the specified SUBSCHEMA in the specified DBNAME indicates that DBTABLE mapping should be used; however, no matching subschema mapping exists at the DBTABLE level. While not illegal, this situation should be reviewed since it could result in bind rununit failures with an error status of 1495.
Module:
IDMSDDBT
Severity:
0
Reason:
No occurrences of the named required entity type have been defined in the DBTABLE.
Module:
IDMSDDBT
Severity:
0
Reason:
One or more critical errors have been detected during the DBTABLE GENERATE process. No DBTABLE load module will be stored.
Module:
IDMSDDBT
Severity:
0
Module:
IDMSDDBT
Severity:
0
Module:
IDMSDDBT
Severity:
0
Module:
IDMSDDBT
Severity:
0
Module:
IDMSDIDD
Severity:
0
Module:
IDMSDIDD
Severity:
0
Module:
IDMSDIDD
Severity:
0
Module:
IDMSDIDD
Severity:
0
Module:
IDMSDIDD
Severity:
0
Reason:
Errors/warnings were detected in processing a DISPLAY/PUNCH physical-database-component request or a request to IDD.
Module:
IDMSDIDD
Severity:
0
Reason:
This is an information message which precedes an actual error message. Its function is to identify the statement within an access module compilation which incurred the error.
<RCM-name> identifies the module which contains the statement in error. If the statement is a cursor declaration, the cursor name is used to identify it. Otherwise the statement-within- module number is displayed. This number is the same as the number assigned to SQLCLNO in the host language call expansion built for the statement by the precompiler.
Module:
IDMSAMC (JERROR)
Severity:
0
Reason:
An INSERT or UPDATE statement has assigned a value which will not fit in the corresponding column (usually CHAR or VARCHAR). Truncation will take place before the assignment is performed.
Module:
IDMSAMC (JGEIUP)
Severity:
0
Module:
IDMSAMC
Severity:
0
Module:
IDMSAMC
Severity:
0
Reason:
This is an information message which summarizes the activities induced by a CREATE, ALTER or DROP ACCESS MODULE statement. It is followed by messages which provide more detail on the statement execution, including the final access module size.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
This message indicates the number of RCMs added to an access module by a CREATE or ALTER ACCESS MODULE statement.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
This message indicates the number of RCMs replaced in an access module by an ALTER ACCESS MODULE statement.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
This message indicates the number of RCMs dropped from an access module by an ALTER ACCESS MODULE statement.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
This message indicates the final size of the access module generated by a CREATE or ALTER ACCESS MODULE statement.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
An invalid input tree was built by the SQL syntax processor. Contact Technical Support for assistance.
Module:
IDMSAMC (JTRDLN)
Severity:
0
Reason:
An invalid input tree was built by the SQL syntax processor. Contact Technical Support for assistance.
Module:
IDMSAMC (JTRDLN)
Severity:
0
Reason:
An invalid input tree was built by the SQL syntax processor. Contact Technical Support for assistance.
Module:
IDMSAMC (JTRDLN)
Severity:
0
Reason:
An invalid input tree was built by the SQL syntax processor or the number of elements has exceeded a limit for its context. Contact Technical Support for assistance.
Module:
IDMSAMC (JTRDLN)
Severity:
0
Reason:
An invalid input tree was built by the SQL syntax processor. Contact Technical Support for assistance.
Module:
IDMSAMC - (JGEFNDF)
Severity:
0
Reason:
An internal compiler error has occurred. Contact Technical Support for assistance.
Module:
IDMSAMC - (JGEFMT, JGELODN, JGENULT, JGEXGR)
Severity:
0
Reason:
An internal compiler error has occurred. Contact Technical Support for assistance.
Module:
IDMSAMC (JGEVALF,JGEXSQ)
Severity:
0
Reason:
Host variable null indicator fields must be 1, 2 or 4 bytes in length.
Module:
IDMSAMC (JGEXFE)
Severity:
0
Reason:
The internal buffer limitation has been exceeded (32764 bytes). This could only happen for an extremely complex query. Try to simplify the query, or break it down into several simpler queries.
Module:
IDMSAMC (JGEBFL, JGE1, JGE2, JGE3, JGE4, JGEOPD)
Severity:
0
Module:
IDMSAMC
Severity:
0
Module:
IDMSAMC (JGEFMT)
Severity:
0
Module:
IDMSAMC
Severity:
0
Reason:
An internal compiler error has occurred. Contact Technical Support for assistance.
Module:
IDMSAMC (many modules)
Severity:
0
Reason:
The definition of a table referenced in an SQL statement could not be found. This is typically caused by misspelling the table name or its schema qualifier. However, it could also be caused by referencing a temporary table before it has been created. In the case of access modules created from pre-compiled host language programs, statements which reference temporary tables which are not created until runtime will themselves be recompiled (automatically) at runtime.
Module:
IDMSAMC (JBITAB)
Severity:
0
Reason:
A statement makes an ambiguous column reference. Several tables in the statement may contain similarly named columns, or the same table may appear several times using different correlation names. The solution is to fully qualify such ambiguous names with table or correlation names.
Module:
IDMSAMC (JBICON)
Severity:
0
Reason:
A named column cannot be found in the definitions of any table referenced in a statement. This is typically the result of a misspelling.
Module:
IDMSAMC (JBICON, JBICRF)
Severity:
0
Reason:
A binary expression or a required conversion involves fields of incompatible data type - for example, an attempt to compare a character field with a numeric. Review the rules for mixing data types in expressions.
Module:
IDMSAMC (JGECNV, JGEMERF)
Severity:
0
Reason:
An expression involves data types which are incompatible with the operation being requested - for example, an attempt to perform arithmetic with two-character fields. Review the rules for data types in expressions.
Module:
IDMSAMC (JGELODN, JGEMERF)
Severity:
0
Reason:
An invalid node was detected in the run tree for the named cursor which is the target of an UPDATE or DELETE. Contact Technical Support.
Module:
IDMSAMC (JGESEC, JGEXRI)
Severity:
0
Reason:
An attempt was made to assign null to a database column with the NOT NULL attribute, or to an output column with no accompanying null indicator field.
Module:
IDMSAMC (JGELODN, JGEOJN, JGEXIN, JGEXI2)
Severity:
0
Reason:
An attempt was made to assign an integer constant which exceeds the capacity of the output column. Check the value limits of the supported integer data types.
Module:
IDMSAMC (JGECST)
Severity:
0
Reason:
The SELECT list of a statement containing the GROUP BY clause may only contain columns referenced in the GROUP BY clause, itself, or aggregate functions (MAX, MIN, COUNT, SUM, AVG).
Module:
IDMSAMC (JBLFXGP, JGEXGR)
Severity:
0
Reason:
Review the limits of CA IDMS SQL.
Module:
IDMSAMC (JBIREF)
Severity:
0
Reason:
Review the limits of CA IDMS SQL.
Module:
IDMSAMC (JBIUNI, JBLMABM)
Severity:
0
Reason:
Review the limits of CA IDMS SQL.
Module:
IDMSAMC (JBIJOI, JBIREF, JBLFXMG)
Severity:
0
Module:
IDMSAMC
Severity:
0
Reason:
An attempt was made to perform an INSERT, UPDATE or DELETE statement on a view whose definition included a join operation. Review the rules for the definition of updatable views.
Module:
IDMSAMC (JBIINS, JBINODE, JBIUPD)
Severity:
0
Reason:
An attempt was made to INSERT or UPDATE a derived column (one defined by an expression) in a view. In a view, only those columns derived directly from a base table column may be inserted or updated.
Module:
IDMSAMC (JBIINS, JBIUPD)
Severity:
0
Reason:
An attempt was made to perform an INSERT, UPDATE or DELETE statement on a view which defines aggregation operations on the underlying base table(s). Review the rules for the definition of updatable views.
Module:
IDMSAMC (JBIINS, JBINODE, JBIUPD)
Severity:
0
Reason:
An attempt was made to perform an INSERT, UPDATE or DELETE statement on a view which contains an ORDER BY clause. Review the rules for the definition of updatable views.
Module:
IDMSAMC (JBINODE)
Severity:
0
Reason:
An attempt was made to perform an UPDATE ... WHERE CURRENT OF statement in which columns included in the SET list were not included in the FOR UPDATE OF clause of the referenced cursor definition. The FOR UPDATE OF clause must include all columns which may be updated using the cursor definition.
Module:
IDMSAMC
Severity:
0
Reason:
The table referenced in a positioned UPDATE statement must be the same as the table referenced in the corresponding cursor definition.
Module:
IDMSAMC
Severity:
0
Reason:
A fully qualified column name could not be found in the definitions of any table referenced in the statement. This is typically caused by a spelling error.
Module:
IDMSAMC (JBIQCO)
Severity:
0
Reason:
In an INSERT statement, the number of supplied values does not match the number of columns in the target table (or the column list of the target table, if included). In a FETCH or SELECT ... INTO statement, the number of fields in the INTO list does not match the number of output columns in the corresponding SELECT definition.
Module:
IDMSAMC (JBIINS, JGEXFE)
Severity:
0
Reason:
The output table of an INSERT INTO ... SELECT statement cannot be referenced in the SELECT definition.
Module:
IDMSAMC (JBIINS)
Severity:
0
Module:
IDMSAMC
Severity:
0
Reason:
The number of output columns must be identical for each SELECT definition within a UNION operation.
Module:
IDMSAMC (JGEXUNI)
Severity:
0
Reason:
The output columns of each SELECT within a UNION operation must match in data type and length.
Module:
IDMSAMC (JGEXUNI)
Severity:
0
Reason:
The output columns of each SELECT within a UNION operation must match according to NULL/NOT NULL attributes.
Module:
IDMSAMC (JGEXSR1, JGEXUNI)
Severity:
0
Reason:
Review the limits of CA IDMS SQL.
Module:
IDMSAMC (JBLMABM)
Severity:
0
Reason:
Review the limits of CA IDMS SQL.
Module:
IDMSAMC (JBISRT,JBLMABM,JGEXSR1)
Severity:
0
Reason:
An attempt was made to assign a decimal or numeric constant which exceeds the capacity of the output column. Check the value of the constant with the size of the column.
Module:
IDMSAMC (JGECST)
Severity:
0
Reason:
The number of values in the VALUE list of an INSERT statement exceeds the number of columns in the table.
Module:
IDMSAMC (JBIINS)
Severity:
0
Reason:
Review the limits of CA IDMS SQL.
Module:
IDMSAMC (JBIGRP)
Severity:
0
Reason:
The precisions of operands of a division operator exceed those which will permit their computation of a result. The CAST operator can be used to control the precision of source values and intermediate results of complex computations.
Module:
IDMSAMC (JGEFPRE)
Severity:
0
Reason:
An attempt was made to perform an INSERT, UPDATE or DELETE statement on a view which contains the DISTINCT operator. Review the rules for the definition of updatable views.
Module:
IDMSAMC (JBIUPD)
Severity:
0
Module:
IDMSAMC (JGECST)
Severity:
0
Module:
IDMSAMC
Severity:
0
Reason:
In order to user ROWID in an ORDER BY clause, at least one real column must be projected from the table that the ROWID refers to.
Module:
IDMSAMC (JGEXSR, JBICRF)
Severity:
0
Module:
IDMSAMC (JGEXSR)
Severity:
0
Reason:
An attempt was made to perform an INSERT or UPDATE statement which cannot satisfy a defined check constraint on the target table.
Module:
IDMSAMC (JBLCCP)
Severity:
0
Module:
IDMSAMC (JBLSRC)
Severity:
0
Module:
IDMSAMC (JBLFXPF)
Severity:
0
Module:
IDMSAMC (JBIPRO)
Severity:
0
Module:
IDMSAMC
Severity:
0
Module:
IDMSAMC (JBLFXFI)
Severity:
0
Reason:
An ambiguous column reference was found, even though the column in question is qualified. This can happen when the same table appears in the main query and a subquery of the same statement. In this case, use correlation names for one or more of the table references to remove the ambiguity.
Module:
IDMSAMC (JBIQCO)
Severity:
0
Reason:
A fully qualified column name could not be found in the definitions of any table referenced in the statement. This is typically caused by a spelling error.
Module:
IDMSAMC (JBIQCO)
Severity:
0
Reason:
The same column name appeared more than once in an ORDER BY clause.
Module:
IDMSAMC (JBISRT)
Severity:
0
Reason:
A column number was specified in a SELECT statement, but was bigger than the number of columns available for reference.
Module:
IDMSAMC (JBICOL)
Severity:
0
Reason:
A cursor referenced by a FETCH, positioned UPDATE or DELETE, or an external cursor definition was not found in the access module. This could be because the cursor name was misspelled, because the cursor definition contained errors which prevented its compilation, or because the cursor is defined in an RCM which has yet to be added to the access module.
Module:
JGECLOC
Severity:
0
Reason:
An attempt was made to INSERT a row into a non-SQL defined record which is an AUTOMATIC member of a set with no referential key definition. Review the rules for performing SQL update statements on a non-SQL defined database.
Module:
JBITAB
Severity:
0
Reason:
An operation involving DATE/TIME operands was attempted which is inconsistent with the operand types - for example, the subtraction of two TIMESTAMP operands. Review the rules for expressions involving DATE/TIME operands.
Module:
JGECNV, JGECST, JGEMERF (IDMSAMC)
Severity:
0
Reason:
An operation involving DATE/TIME operands was attempted which is inconsistent with the operand types - for example, the subtraction of two TIMESTAMP operands. Review the rules for expressions involving DATE/TIME operands.
Module:
JGECNV, JGECST, JGEMERF (IDMSAMC)
Severity:
0
Reason:
An error was detected in the format of a DATE/TIME character constant. Review the rules for constructing DATE/TIME constants.
Module:
JGECST (IDMSAMC)
Severity:
0
Module:
JSMADEP (IDMSAMC)
Severity:
0
Reason:
An explicit WHERE clause reference to a non-SQL defined set was made, which cannot be compiled. This might happen, for example, if the set was specified to join a base table referenced inside an aggregate view to a table outside of the view definition.
Module:
JBLFXPF (IDMSAMC)
Severity:
0
Reason:
An explicit WHERE clause reference to a non-SQL defined set was made, but within an OR. Set names in WHERE clauses must be ANDed to the rest of the WHERE clause.
Module:
JBLSRC (IDMSAMC)
Severity:
0
Reason:
Reduce the number of invocations of functions defined in the catalog or the number of subqueries used in the statement.
Module:
JBINEST(IDMSAMC)
Severity:
0
Reason:
An ALTER ACCESS MODULE statement has a REPLACE clause which refers to an RCM not already contained in the access module. If it is desired to add an RCM to an existing access module, the ADD clause should be used.
Module:
AMCMAIN (IDMSAMC)
Severity:
0
Reason:
The MAP option was used in an ALTER ACCESS MODULE statement without the REPLACE ALL option. MAP options can be altered only if all RCMs in the access module are being recompiled.
Module:
AMCMAIN (IDMSAMC)
Severity:
0
Reason:
An ALTER ACCESS MODULE statement contains a REPLACE MODULE clause with a dictionary name qualifier which does not match the dictionary name of the corresponding RCM in the existing access module.
Module:
AMCMAIN (IDMSAMC)
Severity:
0
Reason:
The load of an RCM failed during the processing of a CREATE or ALTER ACCESS MODULE statement, or during an automatic recompilation at runtime. Assure that the dictionary which contains the referenced RCM is available for access.
Module:
AMCMAIN (IDMSAMC)
Severity:
0
Reason:
An access module, or some statement or RCM within an access module is being dynamically recompiled because of a change in the definition of some referenced table(s). During the recompilation, it was detected that the creation time of the RCM (the last precompilation) does not match the stamp contained within the access module version of the RCM. This indicates that the RCM was rebuilt since the creation of the access module, and the dynamic recompilation cannot proceed.
Module:
AMCD2S2 (IDMSAMC)
Severity:
0
Reason:
An attempt was made to assign a name to a global cursor which is already being used in some other global cursor definition in the access module. Global cursor names must be unique within an access module.
Module:
JBISEC (IDMSAMC)
Severity:
0
Reason:
The load of an access module failed during the processing of an ALTER ACCESS MODULE statement. Assure that the dictionary which contains the referenced access module is available.
Module:
IDMSAMC
Severity:
0
Reason:
An area READY clause was specified in a CREATE or ALTER ACCESS MODULE statement, for an area not associated with any table referenced in the access module. Assure that all areas referenced in CREATE/ALTER statements are spelled correctly and qualified by segment names, as appropriate.
Module:
IDMSAMC
Severity:
0
Reason:
A view reference was compiled which expanded to more columns than was expected. This is typically caused by using SELECT * in a view definition, then adding columns to tables in the FROM clause of the view.
Module:
IDMSAMC (JBITAB)
Severity:
0
Reason:
A failure of the authorization check occurred following the compilation of an access module or a single statement. Assure that all the correct table and view authorizations are held.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Module:
IDMSAMSC, IDMSHLDB
Severity:
0
Module:
IDMSAMSC
Severity:
0
Reason:
A reference to an undefined scalar function was detected.Assure that all functions referenced in the statement are supported by CA IDMS.
Module:
IDMSAMC (JGEFMT)
Severity:
0
Reason:
A reference to a function was detected in which the number of parameters is incorrect. Assure that the number of parameters specified is consistent with the function definition.
Module:
IDMSAMC (JGEFMT)
Severity:
0
Reason:
An error was detected in a BINARY constant which was being assigned or compared to a GRAPHIC or VARGRAPHIC field. Such binary constants must be delimited by shift out and shift in characters.
Module:
IDMSAMC (JGECST)
Severity:
0
Reason:
A non-SQL defined set name reference was detected in a WHERE clause for a multi-member set. Multi-member set references must be qualified by (at least) the name of the member record in question.
Module:
IDMSAMC (JBISET)
Severity:
0
Reason:
A non-SQL defined set name reference was detected in a WHERE clause which was in error. This is typically caused by a set reference in which the owner and/or member records were not included in the statement.
Module:
IDMSAMC (JBISET)
Severity:
0
Reason:
A reference to a function was detected in which the data type of one of the parameters is incorrect or the value was out of range. Assure that the data types and values of the parameters are consistent with the specifications of the function.
Module:
IDMSAMC (JGEFMT, JGEGFUN)
Severity:
0
Reason:
An attempt to assign a value (using INSERT or UPDATE) to the OCCURS DEPENDING ON control field of a non-SQL defined record was detected. Review the rules for performing SQL access to non-SQL defined databases.
Module:
IDMSAMC (JGEIUP, JGEXI2)
Severity:
0
Reason:
An attempt was made to issue a CREATE ACCESS MODULE statement for an access module which already exists. If it is desired to recompile some of the RCMs in an access module, the ALTER statement must be used. Otherwise, a DROP must be issued prior to the CREATE.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
An attempt was detected to use the ALTER statement to recompile some, but not all, of the RCMs in an access module which was compiled in an earlier release of CA IDMS. The REPLACE ALL option must be used to assure that the entire access module is compiled by the same level of software.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
The READ ONLY option of CREATE/ALTER ACCESS MODULE can be used only in conjunction with the TRANSIENT READ option. Conversely, READ WRITE cannot be used in conjunction with TRANSIENT READ.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
None of the RCMs referenced in the FROM clause of a CREATE ACCESS MODULE statement, or the ADD/REPLACE/DROP clauses of an ALTER ACCESS MODULE statement could be found. The access module compiler will perform the requested activities as long as at least some of the referenced RCMs can be found. But if none can be found, the statement is aborted.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
In SQLI, a DELETE WHERE CURRENT has been encountered which requires the recompilation of the referenced cursor. The cursor is not available for recompilation in the current execution context. This is likely because it is a global cursor and an ALTER ACCESS MODULE is being executed which has not specified the RCM which contains the global cursor itself. The cursor (and the DELETE) will eventually recompile at runtime, but you may also reissue the ALTER statement, including the RCM which contains the global cursor declaration.
Module:
IDMSAMC (JGESEC)
Severity:
0
Reason:
The optimizer could not find a valid access strategy to satisfy the input statement. In IDMS, this is caused by conflicts in set name factors included in the WHERE clause. In SQLI this is caused by requesting joins which cannot be satisfied using IMS multi-positioned PCBs. In both cases, the problem can be overcome by simplifying the input statement, or breaking it into several smaller statements.
Module:
IDMSAMC (JBLTAJN)
Severity:
0
Reason:
SQL DML access to non-SQL defined databases does NOT include access to native VSAM files.
Module:
IDMSAMC (JBITAB)
Severity:
0
Reason:
A schema name qualification must be included in the CREATE/ ALTER/DROP syntax, or a default schema must exist for the session from which the statement is issued.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
The schema name in the named access module found in the current dictionary environment does not match the schema name specified in the ALTER/DROP syntax. Confirm that the dictionary default and the specified schema name are consistent.
Module:
IDMSAMC (AMCMAIN), IDMSSTOW
Severity:
0
Reason:
The WHERE clause contains logically contradictory factors which make it impossible to retrieve any rows. For example, it may contain factors like "<column> EQ <value> AND <column> NE <value>", for the same <column>/<value> pair.
Module:
IDMSAMC (JBLVFAC)
Severity:
0
Reason:
An access module was recompiled dynamically because of one of the following reasons: - RCM/host program stamp mismatch - database definition/access module mismatch.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
Net effect of specified ALTER statement would be to DROP all modules from access module. DROP clauses were coded for all existing modules and either there were no ADD clauses or they were in error. If it is desired to discard a whole access module, the DROP ACCESS MODULE statement must be used.
Module:
IDMSAMC (AMCMAIN)
Severity:
0
Reason:
The ESCAPE operand of a LIKE predicate specified a value which was NOT a 1 byte character.
Module:
IDMSAMC (JGELODN), IDMSEXP
Severity:
0
Reason:
Internal error handling translate for alternate character set collating sequence support. Most likely there was no table defined for the requested language.
Module:
IDMSAMC (JGECST), IDMSEXP
Severity:
0
Reason:
INSERT is not supported for native VSAM RRDS files, and DELETE is not supported for native VSAM ESDS files.
Module:
IDMSAMC (JBITAB)
Severity:
0
Reason:
Physical file information for native VSAM files must be available when SQL statements are compiled to access them. This imposes two additional requirements on the coding of SQL access to native VSAM files:
Module:
IDMSAMC (JBITAB)
Severity:
0
Reason:
Changing the value of the primary key of a native VSAM KSDS is not permitted.
Module:
IDMSAMC (JBLOPT)
Severity:
0
Reason:
Procedure invocation syntax (parenthesized parameter list) was used in SELECT, UPDATE, DELETE or CALL statement or function invocation syntax was used, but the definition of the corresponding procedure could not be found in the catalog.
Module:
IDMSAMC (JBIRTI)
Severity:
0
Reason:
A parameter assignment was incorrectly specified. This could be the result of one of the following:
Module:
IDMSAMC (JBLVRTI)
Severity:
0
Reason:
Positioned UPDATE and DELETE (e.g. DELETE FROM table WHERE CURRENT OF cursor) is not permitted with table procedures. Only searched UPDATE and DELETE may be issued on table procedures.
Module:
IDMSAMC (JGESEC)
Severity:
0
Reason:
A reference has been made to a dynamic cursor in a positional update or delete statement. Both a declared dynamic cursor with a matching name and an allocated cursor with a matching name and a local scope exist. Since no scope clause was specified within the positioned update or delete statement, the DBMS cannot determine which of the two cursors is being referenced.
Module:
IDMSAMC (JGECLOC)
Severity:
0
Reason:
A positioned update or delete has been issued against a cursor defined to be READ ONLY.
Module:
IDMSAMC (JGESEC)
Severity:
0
Reason:
The specified dynamic parameter (relative to one) has been used incorrectly. For example, dynamic parameters have been specified as both operands of a binary operator. Review the rules for using dynamic parameters and correct the syntax.
Module:
IDMSAMC (JGEVALF)
Severity:
0
Reason:
A non-SQL defined set name reference was detected in a WHERE clause with the LAST option specified. The set does not have any prior pointers defined.
Module:
IDMSAMC (JBISET)
Severity:
0
Reason:
XML values are LOBs (Large Objects) that can be up to 2 GB in size.Increase the size of the storage pool for CV or the available address space for a batch job.
Module:
IDMSEXP (XAGB opcode)
Severity:
0
Reason:
The results of the dynamic recompilation of the identified access module could not be saved in the current catalog load area. The inability to save the new access module is a performance consideration. Until the access module is recompiled and saved, it will be repeatedly recompiled dynamically.
Module:
IDMSSTOW
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP (SPARSER)
Severity:
0
Module:
IDMSSSP (SPALEXI)
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP (xLNxxx)
Severity:
0
Module:
IDMSSSP (xLNxxx)
Severity:
0
Module:
IDMSSSP (SQLYACC)
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Reason:
Either the same transaction option has been specified more than once or you have specified conflicting options, such as READ WRITE and TRANSIENT READ.
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP (LLNSQDA)
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP (LLNSQDA)
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP (SLNSEL)
Severity:
0
Module:
IDMSSSP (SLNSEL)
Severity:
0
Module:
IDMSSSP (SGNHVL)
Severity:
0
Module:
IDMSSSP (SGNHVL)
Severity:
0
Module:
IDMSSSP (SGNHVL)
Severity:
0
Module:
IDMSSSP (SGNHVL)
Severity:
0
Module:
IDMSSSP (SCRMAIN)
Severity:
0
Module:
IDMSSSP (SCRMAIN)
Severity:
0
Module:
IDMSSSP (SCRMAIN)
Severity:
0
Module:
IDMSSSP (SPPRCM)
Severity:
0
Module:
IDMSSSP (SMEAL)
Severity:
0
Module:
IDMSSSP (xLNTRCH / SLNMALC)
Severity:
0
Module:
IDMSSSP (SISMAIN)
Severity:
0
Reason:
A GRANT or REVOKE was requested for an authorization on a resource type which does not support that authorization.
For example, GRANT DBAREAD ON DMCL is not supported.
Module:
IDMSSPSC (CLNSON)
Severity:
0
Reason:
Positional parameters may not follow non-positional parameters in the parameter list of a routine invocation. For example, DEMO.PROC1 (25, 'X', A = 30, D = 'AB') is a valid invocation, but DEMO.PROC2 ('QQ', -1.3, C = 17, 25) is invalid (because the positional parameter "25" follows the non-positional parameter "C = 17".
Module:
IDMSSPSQ (SLNPLST)
Severity:
0
Reason:
An extended cursor name may not be specified in the following statements:
A scope clause may not be specified in an embedded positioned UPDATE or DELETE statement unless it is part of an extended-cursor-name.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
A positioned UPDATE or DELETE statement must identify the target table when it is embedded in an application program. The table name may be omitted only when the statement is prepared or executed dynamically.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
A searched UPDATE or DELETE statement must identify the target table.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
An EXECUTE statement may not specify both output parameters and bulk input parameters.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
None of the following statements may be executed using pre-14.0 protocols:
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
The following options may only be used with 14.0 or later:
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
Because the CA IDMS SQL Option is not installed, only limited SQL functionality is available. The request violates the restriction because of the specified reason.
Module:
IDMSSPSQ
Severity:
0
Reason:
Because the CA IDMS SQL Option is not installed, only limited SQL functionality is available. The request violates the restriction because of the specified reason.
Module:
IDMSSPSQ
Severity:
0
Reason:
The XMLATTRIBUTES function can only be used in the XMLELEMENT function, as the second or third argument, depending on the presence or not of the XMLNAMESPACES function.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
The XMLNAMESPACES function can only be used as the second argument of the XMLELEMENT function, or as the first argument of the XMLFOREST function.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
The length of an XML identifier cannot exceed 128 characters. An XML identifier can be specified in the NAME clause of the XMLELEMENT and XMLPI functions, and in the AS clause of the XMLFOREST, XMLATTRIBUTES and XMLNAMESPACES functions.
Module:
IDMSSPSQ (SQLYACC)
Severity:
0
Reason:
IDMSSQ2A returned an internal system error. Contact Technical Support.
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Reason:
Condition-name must be defined using a DECLARE <condition-name> CONDITION FOR ... in a compound statement.
Module:
IDMSSQ2A
Severity:
0
Reason:
Use the SIGNAL statement to raise an exception.
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Reason:
identifier1 must refer to the SQL routine name for a parameter or to the label of a compound statement for a local variable. identfier2 is the name of parameter or local variable.
Module:
IDMSSQ2A
Severity:
0
Reason:
The identifier1 must refer to the schema of the SQL routine, identifier2 to the SQL routine name of the parameter, and identifier3 is the name of the parameter.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a compound statement, a Begin-Label must have been specified also.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a compound statement, it must be equal to the Begin-Label of the compound statement.
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Reason:
Values for SQLSTATE in condition declarations can not be duplicated.
Module:
IDMSSQ2A
Severity:
0
Reason:
There can not be more than 1 handler for a specific condition or SQLSTATE value.
Module:
IDMSSQ2A
Severity:
0
Reason:
A handler declaration specifies a condition that has not been defined previously.
Module:
IDMSSQ2A
Severity:
0
Reason:
There cannot be more than 1 handler for a condition or SQLSTATE value.
Module:
IDMSSQ2A
Severity:
0
Reason:
There can not be more than 1 handler for the exception class SQLEXCEPTION.
Module:
IDMSSQ2A
Severity:
0
Reason:
There can not be more than 1 handler for the event class SQLWARNING.
Module:
IDMSSQ2A
Severity:
0
Reason:
There can not be more than 1 handler for the event class NOT FOUND.
Module:
IDMSSQ2A
Severity:
0
Reason:
An SQLSTATE value is a string of 5 characters made up from a digit or a capital letter. The set of characters that can be used in an SQLSTATE value is "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789".
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Reason:
The label identifies the statement that has to be left.
Module:
IDMSSQ2A
Severity:
0
Reason:
The label must reference a LOOP, WHILE or REPEAT that contains the LEAVE or ITERATE statement. A label in a LEAVE statement can also reference a compound statement that contains the LEAVE.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a LOOP statement, a Begin-Label must have been specified also.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a LOOP statement, it must be equal to the Begin-Label of the LOOP statement.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a WHILE statement, a Begin-Label must have been specified also.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a WHILE statement, it must be equal to the Begin-Label of the WHILE statement.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a REPEAT statement, a Begin-Label must have been specified also.
Module:
IDMSSQ2A
Severity:
0
Reason:
If an End-Label is specified on a REPEAT statement, it must be equal to the Begin-Label of the REPEAT statement.
Module:
IDMSSQ2A
Severity:
0
Reason:
If identifier1 is referring to the schema of an SQL routine, and identifier2 refers to an SQL routine name, then identifier3 must specify a parameter of the SQL routine.
Module:
IDMSSQ2A
Severity:
0
Reason:
identifier1 must refer to the SQL routine name for a parameter or to the label of a compound statement for a local variable. identfier2 is the name of parameter or local variable.
Module:
IDMSSQ2A
Severity:
0
Reason:
identifier1 must refer to the schema of the SQL routine, identifier2 to the SQL routine name of the parameter and identifier3 is the name of the parameter.
Module:
IDMSSQ2A
Severity:
0
Reason:
Using SQLSTATE as the target of an assignment or as a local variable or parameter are examples of invalid usages.
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Reason:
Only SQL functions can have a parameter on the RETURN statement.
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSQ2A
Severity:
0
Reason:
Such a nested compound statement must not contain itself compound statements as handler actions.
Module:
IDMSSQ2A
Severity:
0
Reason:
Dropping a SQL routine implies the delete of the associated premap process module. During this delete process a failure occurred.
Module:
IDMSSQ2A
Severity:
0
Reason:
Creating a SQL routine implies the creation of an associated premap process module. Creation of MODULE-067 in DDLDML area of the dictionary was not possible.
Module:
IDMSSQ2A
Severity:
0
Reason:
Creating a SQL routine implies the creation of an associated premap process module. Creation of TEXT-088 records in the DDLDML area of the dictionary failed.
Module:
IDMSSQ2A
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Module:
IDMSSSP
Severity:
0
Reason:
This information message indicates that the IDMSLRBK module was entered to try to rollback unrecovered transactions.
Module:
IDMSLRBK
Severity:
0
Reason:
This information message indicates that the IDMSLRBK module was entered to do the LOCK TRANSACTIONS phase for rolling back unrecovered transactions.
Module:
IDMSLRBK
Severity:
0
Reason:
This information message indicates that the IDMSLRBK module was entered to do the ROLLBACK TRANSACTIONS phase for rolling back unrecovered transactions.
Module:
IDMSLRBK
Severity:
0
Reason:
This information message indicates that the IDMSLRBK module is exiting.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an error occurred while trying to OPEN the JOURNAL to try to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an error occurred while trying to READ the JOURNAL to try to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an error occurred while trying to CLOSE the JOURNAL to try to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an internal error occurred trying to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an internal error occurred trying to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an internal error occurred trying to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an internal error occurred trying to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message indicates an internal error occurred trying to rollback unrecovered transactions.
The task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message issued when an internal error of some kind is detected.The location-code is used when reading the dump and has no other special meaning. The CV or task is abended with a 5021 abend code.
Module:
IDMSLRBK
Severity:
0
Reason:
This message is displayed after other DB342nnn messages and indicates that IDMSLRBK detected an internal error. This message displays the routine name in IDMSLRBK where the error was detected and the offset in IDMSLRBK where the error was detected.
Module:
IDMSLRBK
Severity:
0
Reason:
The specified Transaction-ID number could not be rolled out because while reading the JOURNAL we encountered a ENDJ record or a ABRT record that prevents roll back for this transaction.
Module:
IDMSLRBK
Severity:
0
Reason:
This indicates that the specified Transaction-ID number will have all its associated records, areas, and space management pages locked until this transaction can be rolled out.
Module:
IDMSLRBK
Severity:
0
Reason:
This indicates that the specified Transaction-ID number will be rolled out.
Module:
IDMSLRBK
Severity:
0
Reason:
This indicates that the specified distributed transaction ID number was active in the journals across a warmstart. It will be restarted.
Module:
IDMSLRBK
Severity:
0
Reason:
This indicates that the specified distributed transaction ID number has successfully been restarted.
Module:
IDMSLRBK
Severity:
0
Reason:
This indicates that the specified local transaction ID was unrecovered by warmstart and has been restarted. Locks still need to be reacquired for this transaction.
Module:
IDMSLRBK
Severity:
0
Reason:
This indicates that the specified local transaction ID is part of a distributed transaction with a state of in-doubt, so warmstart did not roll it back. The transaction has been restarted. Locks still need to be reacquired for this transaction.
Module:
IDMSLRBK
Severity:
0
Reason:
The subschema specified on a bind run unit is an invalid subschema load module, or the internal name in the subschema load module does not match the subschema name specified.
The IDMS error status is 1467.
Module:
IDMSBLDR
Severity:
0
Reason:
There is not enough storage available to load the subschema load module. Increase storage size and rerun the job.
The IDMS error status is 1472.
Module:
IDMSBLDR
Severity:
0
Reason:
Subschema not found in load area or loadlib. This may be caused by an incorrect or misnamed database name table.
The IDMS error status is 1474.
Module:
IDMSBLDR
Severity:
0
Reason:
The subschema specified does not contain at least one logical area that maps to a physical area defined in the DMCL when using the dbname specified.
The IDMS error status is 1492.
Module:
IDMSBLDR
Severity:
0
Reason:
Subschema specified contains a symbolic name that is not found in the DMCL using the specified area.
The IDMS error status is 1493.
Module:
IDMSBLDR
Severity:
0
Reason:
There must be a DBNAME established before issuing a BIND run unit to the specified subschema.
The IDMS error status is 1491.
Module:
IDMSBLDR
Severity:
0
Reason:
The specified subschema must be defined in the default section of the DBNAME table, when a bind is issued with the specified dbname.
The IDMS error status is 1495.
Module:
IDMSBLDR
Severity:
0
Reason:
The specified subschema is a Release 10.x built subschema which requires that the DBNAME specified must be a dbname defined in the DBNAME table.
The IDMS error status is 1481.
Module:
IDMSBLDR
Severity:
0
Reason:
The specified subschema is required to be an entry in the DBNAME table. The DBNAME specified matches an entry in the DBNAME table that was defined with subschema mapping mandatory.
The IDMS error status is 1482.
Module:
IDMSBLDR
Severity:
0
Reason:
This message displays the contents of the registers at the time IDMSBLDR detected an internal error or an error that occurred during AREA VALIDATION in a SYSPLEX data sharing environment. This message follows message DB347028 which displays the routine name in IDMSBLDR where the error was detected and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
The dbname specified does not match any dbname defined in the DBNAME table, or any SEGMENT defined in the DMCL. This error can also occur if a dbname defined in the DBNAME table is invalid. See messages DB347026 and DB347027 for the reason why the dbname is invalid. If the program value is blank, the program did move its name into the SUBSCHEMA-CONTROL prior to issuing the BIND RUN-UNIT.
The IDMS error status is 1494.
Module:
IDMSBLDR
Severity:
0
Reason:
The current user is not allowed to access the subschema specified using the dbname specified.
The IDMS error status is 1410.
Module:
IDMSBLDR
Severity:
0
Reason:
The DBNAME TABLE load module is invalid.
The TASK is ABENDED with code 5002.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
While validating a DMCL VARY NEW COPY an internal error was detected in the DMCL AUDIT routine. The detailed reason for the error is displayed on the terminal.
Module:
IDMSBLDR
Severity:
0
Reason:
While performing a DMCL VARY NEW COPY an internal error was detected in the DMCL REBUILD routine.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
An unexpected internal error was returned from a call to RHDCTABL module.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
There was not enough storage available in the storage pool for the requested #GETSTG size.
The TASK is ABENDED with code 5003.
Module:
IDMSBLDR
Severity:
0
Reason:
The #LOAD of the indicated required load module failed. Either the module could not be found or there is not sufficient room in the (XA) program pool. The return code in R15 indicates the specific reason why the module could not be loaded.
The TASK is ABENDED with code 5004.
Module:
IDMSBLDR
Severity:
0
Reason:
An I/O error occurred while trying to issue a #LOAD of the module indicated.
The TASK is ABENDED with code 5004.
The most likely cause of this error is a load library has gone into multiple extents. If this is the case, the library needs to be condensed.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5005.
Module:
IDMSBLDR
Severity:
0
Reason:
A deadlock situation occurred while attempting to allocate storage for the requested #GETSTG size.
The TASK is ABENDED with code 5003.
Module:
IDMSBLDR
Severity:
0
Reason:
The DBNAME indicated is defined in the DBNAME table and is also a SEGMENT defined in the DMCL. However, the dbname entry in the DBNAME table does not INCLUDE the SEGMENT with the same name, which is required. Any run units trying to BIND to this DBNAME will receive a 1494 IDMS-STATUS preceded by a DB347011 error message.
Module:
IDMSBLDR
Severity:
0
Reason:
The DBNAME indicated is defined in the DBNAME table and includes SEGMENTs which own conflicting AREA names defined in the DMCL. Any run units trying to BIND to this DBNAME will receive a 1494 IDMS-STATUS preceded by a DB347011 error message.
Module:
IDMSBLDR
Severity:
0
Reason:
This message is displayed after other DB347nnn messages and indicates that IDMSBLDR detected an internal error or an error that occurred during AREA VALIDATION in a SYSPLEX data sharing environment. This message displays the routine name in IDMSBLDR where the error was detected and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
An internal error occurred while trying to convert a Release10.x subschema load module to a Release 12.0 subschema structure.
The TASK is ABENDED with code 5006.
Module:
IDMSBLDR
Severity:
0
Reason:
The subschema specified maps to multiple physical SEGMENTS in the DMCL that do not contain the same PAGE GROUP or DBKEY RADIX.
The TASK is ABENDED with code 5007.
Module:
IDMSBLDR
Severity:
0
Reason:
There is not enough space in the program pool to #LOAD the requested module.
The TASK is ABENDED with code 5003.
Module:
IDMSBLDR
Severity:
0
Reason:
The DMCL name specified is not a valid DMCL load module.
The TASK is ABENDED with code 5005.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during AREA VALIDATION in a SYSPLEX data sharing environment. The specific phase of AREA VALIDATION is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why AREA VALIDATION failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during AREA VALIDATION in a SYSPLEX data sharing environment. The specific process type of AREA VALIDATION is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why AREA VALIDATION failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during AREA VALIDATION in a SYSPLEX data sharing environment. The specific AREA name that failed VALIDATION is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why AREA VALIDATION failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during AREA VALIDATION in a SYSPLEX data sharing environment. The specific FILE name that failed VALIDATION is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why AREA VALIDATION failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during AREA VALIDATION in a SYSPLEX data sharing environment. The specific reason that VALIDATION failed is displayed.
The errors described below are internal errors. You should contact Technical Support.
The errors described next are validation errors. There is an explanation describing the error, and what action the user should take.
A member of a data sharing group has ended abnormally, with a shared area in update mode, and must be restarted before other members of the data sharing group can access the area in anything other than a transient retrieval mode. This occurs only when there was no inter-CV-interest in the area at the time the member failed and consequently, it was not acquiring global locks for the area.
There is a mismatch between the SYSPLEX coupling facility list structure and the current DMCL for this CV. The file name in the list structure does not match the file name in the DMCL. You should shutdown all your CVs and then synchronize area and file definitions for all DMCLs used by members of the group.
There is a mismatch between the SYSPLEX coupling facility list structure and the current DMCL for this CV. The file RBN range in the list structure does not match the file RBN range in the DMCL. You should shutdown all your CVs and then synchronize area and file definitions for all DMCLs used by members of the group.
There is a mismatch between the SYSPLEX coupling facility list structure and the current DMCL for this CV. The file DSN or VOLSER in the list structure does not match the file DSN or VOLSER in the DMCL. You should shutdown all your CVs and then synchronize area and file definitions for all DMCLs used by members of the group.
The file that is part of a shared area has no CACHE name defined in the DMCL, and the DMCL has no default CACHE name. Either define a CACHE name to the file, or establish a default CACHE name for the DMCL.
While doing validation an attempt was made to notify other CV group members in the data sharing group that Ster-CV-interest in an area has changed, so that each CV group member can update their member's inter-CV-interest in the area. If one or more CVs being notified is not responding to the notification, and their status to the data sharing group is active, the area validation will fail. The xxxxxxxx identifies the CV(s) that failed to receive the notification message. Each CV that failed to receive the notification message should be examined to determine why it is not receiving the notification message, and the problem should be corrected and the CV(s) that could not receive the notification message should be recycled.
Other DB347nnn error messages are displayed along with this message to give the complete reason why AREA VALIDATION failed. The final message given is DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This information message says that AREA VALIDATION is okay in a SYSPLEX data sharing environment. The specific AREA name is displayed along with the current AREA status (Off/Ret/Upd).
Module:
IDMSBLDR
Severity:
0
Reason:
This information message says that AREA VALIDATION is okay in a SYSPLEX data sharing environment. The specific AREA name is displayed along with the current Inter-CV-Interest AREA status (On/Off).
Module:
IDMSBLDR
Severity:
0
Reason:
This informational message says that while doing AREA VALIDATION in a SYSPLEX data sharing environment, a SYSPLEX message was sent from this CV to another CV that is in the same SYSPLEX data sharing group, informing the CV that is sent the message that the current Inter-CV-Interest in some AREA(s) has changed, and that the CV receiving the message take the appropriate action to record changes in the fact that some Inter-CV-Interest in some AREA(s) has changed.
Module:
IDMSBLDR
Severity:
0
Reason:
This informational message says that that while doing AREA VALIDATION in a SYSPLEX data sharing environment, a SYSPLEX message could not be sent to another CV that is in the same SYSPLEX data sharing group, and needs to be informed that the current Inter-CV-Interest in some AREA(s) has changed, and that the CV that the message cannot be sent to needs to take the appropriate action to record changes in the fact that some Inter-CV-Interest in some AREA(s) has changed. The CV that needs to be sent the SYSPLEX message is currently not in an ACTIVE state, and thus cannot be sent the SYSPLEX message at this time in order to record the fact that some Inter-CV-Interest in some AREA(s) has changed.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during a Global QUIESCE in a SYSPLEX data sharing environment. The specific phase of the GLOBAL QUIESCE is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why the Global QUIESCE failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during a Global QUIESCE in a SYSPLEX data sharing environment. The specific process type of the GLOBAL QUIESCE is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why the Global QUIESCE failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during a Global QUIESCE in a SYSPLEX data sharing environment. The CV node name that initiated the QUIESCE is displayed. Other DB347nnn error messages are displayed along with this message to give the complete reason why the Global QUIESCE failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
This message indicates errors occurred during a Global QUIESCE in a SYSPLEX data sharing environment. The specific reason that the Global QUIESCE failed is displayed.
The following errors are internal errors. You should contact Technical Support.
Other DB347nnn error messages are displayed along with this message to give the complete reason why the Global QUIESCE failed. The final message given is the message DB347028 which displays the routine name in IDMSBLDR where the error was detected, and the offset in IDMSBLDR where the error was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
An SQL transaction has attempted to access tables through one or more referencing schemas and those schemas have been defined in such a way that two or more logical areas map to the same physical area in the DMCL. This is an illegal situation, since each logical area in a subschema must map to a unique physical area in a DMCL. This error is likely caused because tables are being accessed both through non-referencing and referencing schemas and the referencing schema has no specified DBNAME.
Module:
IDMSBLDR
Severity:
0
Reason:
This informational message says that while doing AREA VALIDATION in a SYSPLEX data sharing environment, a SYSPLEX reply was received by this CV from another CV that was previously sent a DB347044 message, informing that CV that Inter-CV-Interest has changed, and that the CV receiving the message take the appropriate action to record changes in the fact that some Inter-CV-Interest in some AREA(s) has changed.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error. Contact Technical Support.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error. Contact Technical Support.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error. Contact Technical Support.
The TASK is ABENDED with code 5001.
Module:
IDMSBLDR
Severity:
0
Reason:
Even though the CV was previously shutdown, the DMCL was built from SYSTRK rather than the DMCL load module and a new version of the DMCL load module exists.
This message is always followed by messages DB347057 and DB347058 that show the different time stamps of what is recorded on the SYSTRK DMCL image, and the Load module DMCL image.
Module:
IDMSBLDR
Severity:
0
Reason:
This message shows the critical timestamp for the DMCL image recorded on the SYSTRK file and is always preceded by message DB347056.
Module:
IDMSBLDR
Severity:
0
Reason:
This message shows the critical timestamp for the DMCL load module and is always preceded by message DB347056.
Module:
IDMSBLDR
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5051.
Module:
IDMSCONN
Severity:
0
Reason:
There was not enough storage available in the storage pool for the requested #GETSTG size.
The TASK is ABENDED with code 5052.
Module:
IDMSCONN
Severity:
0
Reason:
A required load module could not be found when doing a #LOAD of the module indicated.
The TASK is ABENDED with code 5053.
Module:
IDMSCONN
Severity:
0
Reason:
An I/O error occurred while trying to issue a #LOAD of the module indicated.
The TASK is ABENDED with code 5053.
Module:
IDMSCONN
Severity:
0
Reason:
A deadlock situation occurred while attempting to allocate storage for the requested #GETSTG size.
The TASK is ABENDED with code 5052.
Module:
IDMSCONN
Severity:
0
Reason:
An invalid SYSIDMS parm was detected. The parm string in error is shown.
The TASK is ABENDED with code 5054.
Module:
IDMSCONN
Severity:
0
Reason:
There is not enough storage in the storage pool to #LOAD the requested module.
The TASK is ABENDED with code 5052.
Module:
IDMSCONN
Severity:
0
Reason:
An internal error has been detected in IDMSLOAD. The name of the routine and the approximate offset where the error was detected are displayed for debugging purposes.
The TASK is ABENDED with code 5071.
Module:
IDMSLOAD
Severity:
0
Reason:
The syntax specified a WHERE clause for the TABLE but the column name is unknown. The job is ended.
Module:
IDMSLOAD
Severity:
0
Reason:
A LOAD, BUILD, or VALIDATE statement conflicts with another previously executed IDMSBCF statement within the same job.
The TASK is ABENDED with code 5073.
Module:
IDMSLOAD
Severity:
0
Reason:
A previous step had extracted information for the specified Index, however the Index is no longer defined in the catalog.
The TASK is ABENDED with code 5071.
Module:
IDMSLOAD
Severity:
0
Reason:
A LOAD, BUILD, or VALIDATE statement was specified for a table defined as NATIVE VSAM, which is not supported.
The TASK is ABENDED with code 5074.
Module:
IDMSLOAD
Severity:
0
Reason:
Insufficient storage to do the LOAD, BUILD, or VALIDATE.Increase the storage size and rerun the job.
The TASK is ABENDED with code 5072.
Module:
IDMSLOAD
Severity:
0
Reason:
A fatal error has been detected by IDMSQSRT while sorting intermediate work file for a LOAD, BUILD, or VALIDATE statement.
The TASK is ABENDED with code 5075. Possible solutions are to increase the size of the Sortwork area or to try using both forms of sort: External and Internal.
Module:
IDMSLOAD
Severity:
0
Reason:
The maximum number of errors has been reached when running a LOAD, BUILD, or VALIDATE. The maximum error count is a variable established with the ERRORS CONTINUE syntax. The default is one.
Module:
IDMSLOAD
Severity:
0
Reason:
An unexpected database error was detected, and the job cannot continue. The SYSLST file will contain the description of the error including the IDMS error status.
Module:
IDMSLOAD
Severity:
0
Reason:
A previous step had extracted information for the specified Constraint, however the Constraint is no longer defined in the catalog.
The TASK is ABENDED with code 5071.
Module:
IDMSLOAD
Severity:
0
Reason:
While trying to BUILD indexes it was determined that the BUILD step that fills in owner DBKEYs was not executed prior to the BUILD indexes step.
The TASK is ABENDED with code 5071.
Module:
IDMSLOAD
Severity:
0
Reason:
This displays the number of records processed so far for the specified phase of the LOAD, BUILD, or VALIDATE. The interval is controlled by the NOTIFY syntax.
Module:
IDMSLOAD
Severity:
0
Reason:
When running IDMSDB2T you must include an IDMSPROG=xxxxxxxx parameter in the SYSIDMS parms file.
Module:
IDMSDB2T
Severity:
0
Reason:
When running IDMSDB2T the module specified in the IDMSPROG parameter in the SYSIDMS parms file could not be loaded successfully.
Module:
IDMSDB2T
Severity:
0
Reason:
When running IDMSEXEC you must include an IDMSPROG=xxxxxxxx parameter in the SYSIDMS parms file.
Module:
IDMSEXEC
Severity:
0
Reason:
When running IDMSEXEC the module specified in the IDMSPROG parameter in the SYSIDMS parms file could not be loaded successfully.
Module:
IDMSEXEC
Severity:
0
Reason:
Identifies trace information used by Technical Support.
Module:
IDMSXCLI
Severity:
0
Reason:
A program has attempted to execute an invalid XA transaction function or specified an unsupported client type. Contact Technical Support.
The task is abended with code XCLI.
Module:
IDMSXCLI
Severity:
0
Reason:
A call to an internal service has returned an unexpected return code. Contact Technical Support.
The task is abended with code XCLI.
Module:
IDMSXCLI
Severity:
0
Reason:
Change Tracking disabled, manual intervention required.
Change Tracking is disabled due to one of the following reasons:
Because Change Tracking is disabled, manual intervention is necessary to ensure correct recovery takes place.
Take the following corrective actions before restarting the CV:
The system ABENDs with code 5062.
Module:
IDMSTRAK
Severity:
0
Reason:
SYSTRK library full. Change Tracking inactivated.
The FILE SIZE specified on a FORMAT SYSTRK file is not large enough. To determine the minimum file size needed for the SYSTRK file(s) refer to the FORMAT utility.
Module:
IDMSTRAK
Severity:
0
Reason:
This message is generated when an unexpected error is detected while trying to access a SYSTRK file for Change Tracking support.
The Change Tracking support is inactivated.
Reason codes 0804 (Library full) and 080F (Directory full) are usually caused because the FILE SIZE specified on a FORMAT SYSTRK file is not large enough. To determine the minimum file size needed for the SYSTRK file(s) refer to the FORMAT utility.
All other reason codes are internal errors. Contact Technical Support.
Module:
IDMSTRAK
Severity:
0
Reason:
This is an internal error.
The TASK is ABENDED with code 5061.
Module:
IDMSTRAK
Severity:
0
Reason:
There was not enough storage available in the storage pool for the requested #GETSTG size.
The TASK is ABENDED with code 5063.
Module:
IDMSTRAK
Severity:
0
Reason:
A deadlock situation occurred while attempting to allocate storage for the requested #GETSTG size.
The TASK is ABENDED with code 5063.
Module:
IDMSTRAK
Severity:
0
Reason:
This message is displayed after other DB450nnn messages and indicates that IDMSTRAK detected an internal error. This message displays the routine name in IDMSTRAK where the error was detected and the offset in IDMSTRAK where the error was detected.
Module:
IDMSTRAK
Severity:
0
Reason:
Either too few SYSTRK files have been created or an error has been encountered trying to open or read one or more SYSTRK files. In order to provide fault tolerance for Change Tracking, at least two SYSTRK files must be available for use. Take the necessary steps to create or recover at least one more SYSTRK file and issue DCMT VARY CHANGE TRACKING to make it active.
Module:
IDMSTRAK
Severity:
0
Reason:
System startup will fail. Before restarting the system, take one of the following corrective actions:
Note: Either of the second two actions will disable the use of Change Tracking until the system is recycled.
The system ABENDs with code 5062.
Module:
IDMSTRAK
Severity:
0
Reason:
Either too few SYSTRK files have been created or an error has been encountered trying to open or read one or more SYSTRK files. In order to provide fault tolerance for Change Tracking, at least two SYSTRK files must be usable. System startup will fail. Before restarting the system, take the necessary steps to create at least one more usable SYSTRK file.
The system ABENDs with code 5062.
Module:
IDMSTRAK
Severity:
0
Reason:
The SYSTRK files indicate that they are currently in use by a CV whose node name does not match the DCNAME specified in the SYSIDMS parameters for the CV being started. This error is most likely caused by referencing the wrong SYSTRK files in the JCL or by not shutting down the CV before changing node names. Take one of the following corrective actions:
The system ABENDs with code 5062.
Module:
IDMSTRAK
Severity:
2
Reason:
The SYSTRK files indicate they are currently in use by the CV whose node name is <SYSTRK-node-name>. The journal files indicate they are in use by the CV whose node name is <JOURNAL-node-name>. This condition is most likely caused by a JCL error in which either the incorrect SYSTRK files or the incorrect journal files are referenced. Correct the JCL and restart the CV.
The system ABENDs with code 5062.
Module:
IDMSTRAK
Severity:
2
Reason:
Prior to warmstart, it was detected that the SYSTRK files referenced in the execution JCL were last used by the CVs whose node names are displayed in this message. In order to use a set of SYSTRK files together, they must have last been used by only one CV or not previously used at all. Conflicting node names may be the result of a JCL error in which one or more SYSTRK files were referenced erroneously. If that is the case, correct the JCL and restart the CV. If that is not the case, then you must format all SYSTRK files whose node name does not match the one for the CV being started.
The system ABENDs with code 5062.
Module:
IDMSTRAK
Severity:
2
Reason:
Conflicting SYSTRK node names: &01. - &02., &03. - &04. Change Tracking inactive.
During execution of a DCMT VARY CHANGE TRACKING ACTIVE command it was detected that the SYSTRK files being used have conflicting node names, most likely because they are in use by another CV. Resolve the conflict by shutting down one of the two CVs, changing its JCL to reference another set of SYSTRK files and formatting any SYSTRK file that was actively used by an incorrect CV. Change tracking will remain inactive on this CV until steps are taken to resolve the conflict and a DCMT VARY CHANGE TRACKING ACTIVE command is issued.
Module:
IDMSTRAK
Severity:
2
Reason:
The SYSTRK files indicate that they are currently in use by the CV whose node name is shown in the message. Change Tracking is inactivated. This error is most likely caused because two CVs are referencing the same set of SYSTRK files. To activate change tracking on both CVs, you must shutdown one of them and change its JCL to reference a different set of SYSTRK files.
Module:
IDMSTRAK
Severity:
2
Reason:
The SYSTRK file whose dataset name is <file-name>, is no longer in use by the CV and can be deleted.
This is an informational message only.
Module:
IDMSTRAK
Severity:
2
Reason:
This message shows the current space utilization within the SYSTRK files. It is issued during startup and whenever the set of SYSTRK files are refreshed. This is an informational message only.
Module:
IDMSTRAK
Severity:
2
Reason:
The SYSTRK files are too small. This may prevent the use of change tracking and the successful execution of certain DCMT commands. SYSTRK files should minimally have enough free space to hold a second copy of the DMCL and file override information plus additional space for expansion in response to DCMT commands that change the runtime database environment. In response to this message, you should create and format larger SYSTRK files and make them active using the DCMT VARY CHANGE TRACKING command.
Module:
IDMSTRAK
Severity:
0
Reason:
This is a debugging message that reports any of three events:
Initialization of the previously indicated record.
DB450080 AUTOTUNE=NO
This is a debugging message indicating that AUTOTUNE has been disabled.
DB450080 NEXT RECORD
This is a debugging message indicating that processing is advancing to the next record.
Module:
IDMSTRAK
Severity:
0
Reason:
This is a debugging message that reports the progress of processing in IDMSTRAK.
Module:
IDMSTRAK
Severity:
0
Reason:
This is a generic test debugging message issued by IDMSTRAK.
The entire message text is variable. It is used to display routine calling flow.
Module:
IDMSTRAK
Severity:
0
Reason:
This is a generic debugging message issued by IDMSTRAK.
The entire message text is variable. It is used to display data structure processing flow.
Module:
IDMSTRAK
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|