The following tableBASE error codes and subcodes are returned by tableBASE as a result of events detected in the processing of commands. The error code is returned in the ERROR field of the COMMAND-AREA parameter, and the subcode is returned in the ERROR-SUB-CODE field.
To distinguish tableBASE abend codes from those of the operating environment when running tableBASE with CICS, the tableBASE abend codes are prefixed with a G for abends under 1000 (for example, G009) and prefixed with V for abends over 1000, where V replaces the 1 (for example, 1072 becomes V072). In all other environments, tableBASE abend codes appear as listed.
In addition, tableBASE internal logical errors are indicated in CICS as LGIC abends and in other environments as U301 abends. If an abend causes the tableBASE control blocks to be purposely dumped by tableBASE, the transaction dump code generated in CICS is DKL1.
Additional errors generated by VTS (prefixed by TBV1) and tablesONLINE (prefixed by TB-) may also be encountered.
If the “Abend on Errors” switch is set to ‘N’ the return code and subcode are returned to the caller in the command area. If the “Abend on Errors” switch is set to ‘Y’ the thread will abend, and a message will be written to the JES log. Below is an example:
THE SPECIFIED LIBRARY IS NOT SUITABLE Â Â Â Â Â Â RC = 0060 SC = 0006
In this example, you would reference 60-06 in the following table. Depending upon the error condition, there may or may not be a subcode.
In the event that the application thread abends, the tableBASE error code is used as the user abend value, and any associated error subcode is used as the abend reason code.
|
Return Code |
Text |
Meaning / Instructions |
|---|---|---|
|
00-00 |
tableBASE command executed successfully |
No action is indicated. |
|
00-01 |
Hash High and/or Low Density values for table adjusted based on region limits |
tableBASE command executed successfully. Table density values were substituted with region limits because:
|
|
00-03 |
The table specified on the open command was already open. |
tableBASE command executed successfully. Table specified was already open in the designated TSR. |
|
01-00 |
The specified command is invalid. |
The two-character Command code specified is not a valid tableBASE command. |
|
02-00 |
The specified table must be open for this command. |
Open the table before processing this command. |
|
02-01 |
The table is in the process of being opened by another process. |
This table is being opened and this command cannot wait for the open to complete. Retry the request. |
|
02-98 |
Invalid parameter(s) were specified for the CL command. |
Correct the parameters and resubmit the command (the CL command does not take any parameters). |
|
03-00 |
The table is not closed. |
The table must not be open in the TSR for this command. |
|
03-01 |
The command requires that the table be closed |
Close the table in the TSR and resubmit the command. |
|
03-02 |
The table specified by the LD command has an incorrect row size. |
Correct the row size for the LD table and resubmit the command. The row size depends on the DIRTYPE specified; see the Programming Guide. |
|
03-03 |
The table specified by the LD command has an incorrect key size. |
Correct the key size for the LD table and resubmit the command. The key size depends on the DIRTYPE specified; see the Programming Guide. |
|
03-04 |
The table specified by the LD command has an incorrect key location. |
The key location for the table created by the LD command is always 1. Correct the table definition and resubmit the command. |
|
03-05 |
The table specified by the LD command is an alternate index. |
The table used by an LD command must be defined as a data-table. Correct the table type and resubmit the command. |
|
03-06 |
The table specified by the LD command is a linked VTS table |
The table used by an LD command cannot be a linked VTS table. |
|
03-07 |
The library specified by the LD command cannot be a VTSNAME |
The LD command only works with tableBASE libraries on DASD. LD command usage with a VTS-TSR in the library list is not supported. Use the LT command to list tables in a VTS-TSR. |
|
03-08 |
The table is already open from a library with a different DSN |
The table cannot be opened from the specified DSN. It is already opened in the TSR from a different DSN. |
|
03-09 |
The table is in the process of being opened by another process. |
This table is being opened. Retry the request after closing the table. |
|
03-10 |
The command requires that the table be closed. |
The table is open in the local TSR. Close the table and resubmit the command. |
|
04-00 |
The FG command is not allowed; the table is not sequential (S or D) |
Change the table organization to sequential (S or D) and resubmit the command. |
|
05-00 |
The indirect open search criterion was not found in the primary table |
The indirect open search criterion set by the SI command did not match any keys in the primary table specified on this command. See the Programming Guide for details on using INDIRECT-OPEN. |
|
06-00 |
The count specified is invalid |
Correct the COUNT value in the COMMAND AREA and resubmit the command. |
|
06-01 |
The COUNT must be a positive number. |
The COUNT value in the COMMAND AREA cannot be negative or zero. Correct and resubmit the command. |
|
06-02 |
The COUNT exceeds the number of rows |
The COUNT value in the COMMAND AREA cannot exceed the number of rows in the table (except for hash tables). Correct and resubmit the command. |
|
06-03 |
The COUNT points to an empty row in a hash table. |
The COUNT value in the COMMAND AREA for RC and DC commands for a hash table must point to a valid row. |
|
07-00 |
The library DSN or DDNAME has been changed. Use DV or DW before STore. |
If the library DSN or DDNAME for an open table has changed, the DV or DW command must be issued for the table before the table can be STored. |
|
08-00 |
The generation number specified for this table is invalid. |
Correct the generation number specified and resubmit the command. Generation numbers can be specified as absolute numbers from 1 to 255 or as negative numbers relative to current generation. The current generation is 0. (See the Programming Guide for details on specific commands) |
|
09-00 |
The table is not found. |
The table is not open in the TSR and cannot be found in the current library list (ML-list). |
|
09-01 |
The table could not be found in any of the libraries in the ML list. |
Ensure the ML-list includes the library where the table can be found and resubmit the command. |
|
09-02 |
The table specified could not be found in the linked VTS-TSR. |
The table search is linked to a table in a VTS-TSR and the table is not open there. |
|
09-03 |
The table specified could not be found in the designated library. |
Either ensure the ML-list includes the library where the table resides or ensure the table is resident in the currently designated library. If the command specifies a specific library DDNAME, ensure the table exists on that library. |
|
10-00 |
The STATUS-SWITCHES parameter provided for the CS command is invalid |
Correct the STATUS-SWITCHES parameter and resubmit the command. (See the Programming Guide for details on specific switches) |
|
11-00 |
The Number of Generations to keep in the DT parameter must be 1 to 9. |
tableBASE supports up to 9 generations of a table on a library. The number of generations to keep in the DT parameter must be 1 to 9. Correct the value and resubmit the command. |
|
12-00 |
The table name specified is invalid. |
A valid table name is a string of 8 bytes that are not all blanks, all low values, all high values, or :TMPNAME. Please refer to the Programming Guide for more details. In some applications, such as TBOL/CICS, more restrictive rules may be implemented. |
|
13-00 |
The command is invalid in this environment |
The two-letter command code is invalid. It is not supported in this execution environment. |
|
13-01 |
This command is only supported for a VTS Agent. |
The strobe-request internal command is only supported in the VTS Agent. |
|
13-02 |
The DL (Define Library) command is not supported in CICS. |
The DL command is only supported in the Batch interface. |
|
13-03 |
Library expansion process may not be initiated from CICS. |
The library expansion process is only supported by the TBEXEC (DK1TEXEC) Batch utility running in a non-multitasking environment. |
|
13-05 |
Updates not permitted on a linked VTS table. |
Only READ access is permitted on a table linked to a table in a VTS-TSR. (See the Programming Guide for more details on linked tables) |
|
13-06 |
Update commands are not permitted when a TSR is read only. |
Update commands are not permitted when TSRACCESS=RO (TSR is read only). |
|
13-07 |
Command not supported in this environment. |
The command specified is not supported in this environment. |
|
13-08 |
tableBASE Library Access is not allowed for this interface. |
Access to a tableBASE Library is not allowed for this interface. Refer to run time option ALLOW_TB_LIB_IO for further details (see tableBASE Administration Guide or tableBASE Programming Guide). |
|
13-11 |
The command is invalid against a VTS-TSR. |
When a VTS is being accessed either directly via the TBPARM or as a linked list, this command is invalid. |
|
14-00 |
The ROW-SIZE specified is invalid. Must be from 1 to 32767. |
The row size specified must be from 1 to 32767. Correct it and resubmit the command. |
|
15-00 |
The KEY-SIZE specified is invalid. Must be from 1 to 256 and fit in row. |
The key size specified must be from 1 to 256, and must fit in the row based on key location. Correct the key-size and resubmit the command. Note that date-sensitive processing can affect this. |
|
16-00 |
The KEY-LOCATION specified is invalid. Must be from 1 to row-size. |
Correct the key-location specified and resubmit the command. Note that the key location must allow the key size to fit within the row size. |
|
17-00 |
The key will not fit within the row. |
The key will not fit within the row because either the key’s location in the row or its length is beyond the bounds of the row. Correct the key-size/key-location and resubmit the command. Note that date-sensitive processing can affect this. |
|
18-00 |
Insufficient space is available on the tableBASE library. |
The library must be enlarged. A table cannot be stored on the library because there is insufficient free space available. Note that during the processing of a Store command there must be room in the library to hold 2 copies of the table on the library. There are 2 options: 1) create a new larger library and copy the existing library into it, or 2) expand the library. Both options are supported by the Batch Utility DK1TEXEC (TBEXEC). (See the Batch Utilities Guide for details.) |
|
19-00 |
This table already exists on the target library. |
A new table cannot be STored on a library when it already exists on that library. Preceding the STore with a DW command will allow the table to overlay the previous table. |
|
20-00 |
The maximum number of open tables has been exceeded. Check MAXNMTAB. |
The MAXNMTAB option for the region must be increased to allow more tables into the TSR. Temporarily, tables can be CLosed. To change this value permanently, override the value in a TBOPT DD or update DK1Txx34. (See the Installation Guide for the latter option.) |
|
21-00 |
The Organization specified is invalid, must be blank, R, U, S, D, H. For date-sensitive processing, Organization can only be S. |
Correct the organization specified and resubmit the command. |
|
28-00 |
Paged tables are not supported in V6. |
Paged tables are not supported starting with Version 6. All paged tables were converted to resident during the upgrade to V6. Storage Mode Code (SMC) of “P” (for Paged) is no longer allowed on the DT or CD command. |
|
29-00 |
The secondary table is not located on same library as primary table |
When the Open Indirect option is invoked for an Open command, the tables to be opened must reside in the same library as the primary table. (See the Programming Guide for details on Open Indirect, or the SI command for more details). |
|
30-00 |
The password supplied is invalid. |
Accessing this table on a tableBASE library requires a valid password. Supply the correct password and resubmit the command. |
|
31-00 |
The write password is either missing or incorrect. |
Opening this table for write access from this tableBASE library or updating it on this tableBASE library requires the Write Password. Correct the password and resubmit the command. |
|
32-00 |
The ST command requires that the table be opened for write. |
A table can be STored on a tableBASE library only if it is Open for Write in the TSR. Execute the OW command before attempting to STore the table. |
|
33-00 |
A different generation of the table is already open. |
Two generations of the same table cannot be open in a TSR at the same time. Close the table and open it again in the region in order to access the latest generation on the library. |
|
39-00 |
The RN command failed. The new name already exists in the library. |
The table rename (RN) command failed because a table with the new name already exists in the library. |
|
40-00 |
The library DDNAME does not exist. |
A library name specified in the library list (ML-list) or a command parameter does not correspond with an allocated DDNAME. |
|
40-01 |
The specified library DDNAME is not allocated. |
Correct the library names in the library list (ML-list) or the command parameter and/or allocate the DDNAME in the region (add a DD statement to the JCL) and rerun the job. For CICS, this could be due to a missing entry in the FCT (File Control Table for BDAM libraries) or the CSD (CICS system definition file for VSAM libraries). The CICS region will need to be recycled for newly added FCT entries. |
|
40-02 |
The ST command failed because an ML entry is required. |
When a new table is defined in the TSR without any library DDNAMEs in the library list, the library on which the table is to be stored must be provided either by a DV or DW command before the STore command is issued or by specifying a valid library DDNAME in the ML-list in effect when the STore command is issued. |
|
40-03 |
A blank or null DDNAME was used as a library list entry. |
A library DDNAME must be specified in the library list (ML-list) in effect when the command is being invoked. |
|
40-04 |
The CA command failed because an ML entry is required. |
A CA command stores the alternate index definition on the first library in the library list (ML-list). A null or blank library list is not valid for this command. |
|
40-05 |
The library list DDNAME entry is not allocated. |
The current library list (ML-list) contains an entry that does not correspond to an allocated DDNAME. Correct the library list or add the DDNAME to the JCL and rerun or ALLOCATE with AL. For CICS, this could be due to a missing entry in the FCT (File Control Table for BDAM libraries) or the CSD (CICS system definition file for VSAM libraries). The CICS region will need to be recycled for newly added FCT entries. |
|
41-00 |
The STORAGE-MODE-CODE (SMC) specified must be R or blank. |
Change the SMC value to “R” and resubmit the command. “P” for Page Table is not supported in V6. |
|
42-00 |
The TBPARM sub parameter TB-FORMAT must be either 0 or A. |
Correct the value in the TB-FORMAT sub-parameter and resubmit the command. (See the Programming Guide for details on TBPARM sub-parameters.) |
|
43-00 |
The estimated NUMBER-OF-ROWS value in the DT block is out of range. |
When a table is defined, the estimated number of rows times the row size cannot exceed 2G. It also cannot be negative. |
|
44-00 |
The EXPANSION-FACTOR specified in the DT block must be from 1 to 999. |
Correct the value in this field and resubmit the command. Consult the Programming Guide for the usage of this parameter. |
|
49-00 |
This command requires more parameters than were supplied. |
Supply the minimum number of parameters required for this command. Consult the Programming Guide and resubmit the command. |
|
50-00 |
The DIRTYPE specified for the LD command must be V, D, T, L, or blank. |
Correct the DIRTYPE used by the LD command and resubmit the command. (Consult the Programming Guide for the usage of the DIRTYPE parameter) |
|
51-00 |
HIGH/LOW DENSITY specified in DT block must be from 1 to 999. |
Correct the DENSITY value being used and resubmit the command. Consult the Programming Guide for the usage of these parameters. Note that the specified HIGH-DENSITY and LOW-DENSITY parameters can be adjusted dynamically by the HASH_HI_DEN_LIM and HASH_LOW_DEN_LIM run-time options. |
|
55-00 |
The SEARCH-METHOD must be either S, Q, B, C, or H. |
Correct the SEARCH-METHOD value being used and resubmit the command. Consult the Programming Guide for the usage of this parameter. |
|
56-00 |
The SEARCH-METHOD is incompatible with ORGANIZATION specified. |
Correct the SEARCH-METHOD and/or the ORGANIZATION field ensuring they are compatible and resubmit the command. (Consult the Programming Guide for the relationship of these two parameters). |
|
58-00 |
The requested module cannot be found in the load libraries searched. |
Add the missing module to the load libraries accessed through STEPLIB, LPA or linklist. |
|
60-00 |
The specified library is not suitable. |
The dataset specified is not a valid tableBASE library. |
|
60-01 |
The specified library’s data definition must be DASD |
Ensure that the library DDName is allocated to DASD, and resubmit the command. Note that if you are using VSAM tableBASE libraries with LSR, they are not supported in the tableBASE Batch interface. For more information, see the “Best Practices” chapter in the tableBASE Administration Guide. |
|
60-02 |
The specified library’s BLKSIZE must be at least 600. |
Increase the library BLKSIZE to at least 600 and resubmit the job. |
|
60-03 |
The specified library must contain at least 10 blocks. |
Increase the number of blocks in the library; 10 is the minimum. Correct the allocation and resubmit the command. |
|
60-04 |
tableBASE libraries are limited to 8,388,607 blocks. |
Reduce the number of blocks in the library. The maximum for a BDAM library dataset is the number of blocks that can be contained in 65,535 tracks (approximately 4369 cyl). The maximum for a un-extended VSAM RRDS library dataset is the number of blocks that does not exceeed 4G bytes of data (approx 6145 cyl). Correct the allocation and resubmit the command. |
|
60-05 |
The BLKSIZE of the source and target libraries differ. |
The process being invoked requires that the source and target libraries have the same block size. Correct the block sizes and resubmit the command. |
|
60-06 |
The size of the designated library is smaller than that of the source. |
Reallocate the target library dataset to contain the same as or more blocks than the source dataset and rerun the job. |
|
60-07 |
The specified library’s BLKSIZE is not known |
The library is not a valid tableBASE library. Ensure that the library has been successfully DEFINEd with either the DL command or the DK1TEXEC (TBEXEC) Batch utility. Rerun this job after the library is successfully defined. |
|
60-08 |
The library expansion is not complete. Recreate the library. |
An I/O error was experienced performing the library expansion. Recreate the library and resubmit the job. |
|
60-09 |
The target library cannot be a V5 Bridge library. |
Library Expand failed. Ensure the target library is a V6 format library and resubmit the job. |
|
61-00 |
The library status is invalid. |
The tableBASE library DD is not allocated appropriately |
|
61-01 |
The library DDNAME may not be concatenated with another dataset. |
tableBASE Library DDNAME concatenation is not supported. Ensure each library has a separate DDNAME and resubmit the command. Note that tableBASE VSAM libraries using LSR (Local Shared Resources) is not supported by the tableBASE Batch interface. |
|
61-02 |
The DSNAME is open with another DDNAME. |
Only 1 DDNAME is allowed per library DSNAME. Correct the JCL and resubmit the job. Note that tableBASE retains the reference of a DDName to a DSName for the life of a region; that relationship is established the first time the library is accessed in the region. This applies only to DDName and DSName relationships established using JCL. |
|
61-03 |
The DL command or library expansion failed, the library was open. |
The library was already in use. Ensure the process has exclusive use of the library and resubmit the job. |
|
61-04 |
The DL command or library expansion failed, DISP must be NEW or OLD. |
Correct the library disposition in the JCL and resubmit the job. |
|
61-05 |
The DL command failed; a VSAM library was not defined as reusable. |
Redefine the VSAM library as reusable and resubmit the job. |
|
61-06 |
The designated library access method must be BDAM or VSAM. |
Correct the DSORG of the library and resubmit the job. |
|
61-07 |
The library DISP must be OLD or SHR for this command. |
Correct the library disposition in the JCL and resubmit the job. |
|
61-08 |
OPTCD=C and Z mutually exclusive on tableBASE library DD statement. |
Correct the OPTCD DD statement and resubmit the job. See the Administration Guide for documentation on tableBASE use of the OPTCD subparameters C and Z. |
|
61-09 |
The BDAM library must be RECFM=F or FB. |
This error will be returned in the following cases:
For BDAM library definitions, only RECFM=F is allowed. For BDAM library access, RECFM=F or FB are allowed if LRECL is equal to BLKSIZE. |
|
61-10 |
The VSAM library definition must be RRDS (Relative Record dataset). |
Correct the VSAM library definition and resubmit the job. |
|
61-11 |
A write operation to the library was terminated, library read-only. |
No updates are allowed to this library because it is defined with read-only access. In Batch jobs, LABEL=(,,,IN) on the DD statement defines a library dataset as read-only; in CICS, the library file definition is read-only. If updates to the library are to be allowed, change the JCL or CICS file definition. If no updates are allowed, inform the owners of the application to change their practices. |
|
61-12 |
The specified library is RACF protected for this type of access. |
The RACF/AUTHORITY does not allow the specified access to the library dataset. Determine whether to request RACF changes or inform the owners of the application to change their practices. |
|
62-00 |
Format of the specified library is not compatible with Version 6 or higher versions. |
Starting with Version 6, tableBASE does not support libraries that have not been converted from V5 or defined under V6. To determine library format run job DK1TLCHK. Ensure the library is in a compatible format and resubmit the job. |
|
64-00 |
The INDEX parameter specified must be P, T or blank. |
Correct the index parameter and resubmit the command. (Consult the Programming Guide for the usage of the INDEX parameter) |
|
68-00 |
The COUNT value is too small for the DU command to dump all rows. |
This Error Code may be OK if only a portion of the rows were to be dumped. If all the rows in the table were to be dumped, increase the COUNT value to the total number of rows and resubmit the command. (Consult the Programming Guide for the parameters of the DUmp command). |
|
70-00 |
tableBASE cleanup unable to complete due to CICS shutdown processing. |
tableBASE‘s attempts to clean up control blocks in the CICS region at termination cannot complete due to CICS termination processing. |
|
71-00 |
Lock is unavailable after waiting LOCKTIMERC seconds. |
A tableBASE lock was not available for use after waiting LOCKTIMERC seconds. Resubmit the command. If a longer wait time for the resource is desired, update the TBOPT LOCKTIMERC value and resubmit the command. |
|
72-00 |
The table is unavailable at this time; WAIT switch is off. |
The table was in use at the time of the command. Retry the command. |
|
72-01 |
The table is unavailable after waiting TABLEWAITRC seconds. |
With the WAIT switch on, the table enqueue was unavailable after waiting TABLEWAITRC seconds. If the wait time is to be increased, update the TBOPT TABLEWAITRC value and resubmit the command. The table enqueue is an MVS enqueue with a major name of TBLBASE and a minor name starting with T followed by the table name and the library DSN. It is held while a table is open for write in a TSR. |
|
73-00 |
An update command was issued for a table that was not open for write. |
An update command was issued for a table that has not been opened for write. See descriptions for other sub-codes for detailed explanation. The command being issued requires that the table be OPEN for WRITE (OW). For correct operation, issue an OW command for the table and retry the command. |
|
73-01 |
An update command was issued for a table that is open for read in a local or VTS-TSR. |
An update command was issued for a table that has been opened for read in a local or VTS-TSR and this is not a single-tasked application i.e. MULTITASKING=Y or it is a CICS, IMS region or DB2 SP Address Space. The command being issued requires that the table be OPEN for WRITE (OW). For correct operation, issue an OW command for the table and retry the command. |
|
73-02 |
An update command was issued for a table that is open for read in a VTS-TSR. |
An update command was issued for a table that has been opened read in a VTS-TSR and this is a single-tasked application i.e. MULTITASKING=N. The command being issued requires that the table be OPEN for WRITE (OW). For correct operation, issue an OW command for the table and retry the command. |
|
73-03 |
An update command was issued against the local TSR for a closed table |
An update command was issued against the local TSR for a table that is not open in the TSR, implicit open is ON, and this is not a single-tasked application. The table will not be opened after the command completes. The command being issued requires that the table be OPEN for WRITE (OW). For correct operation, issue an OW command for the table and retry the command. |
|
73-04 |
An update command was issued against a VTS-TSR for a closed table. |
An update command was issued against a VTS-TSR for a table is not open in that TSR and implicit open is ON. The table will not be opened after the command completes. The command being issued requires that the table be OPEN for WRITE (OW). For correct operation, issue an OW command for the table and retry the command. |
|
73-05 |
An update command was issued for a linked table. |
An update command was issued for a table that is opened for read as a linked table (this appears to always be preceded by error 13-5 so may never be encountered). The command being issued requires that the table be OPEN for WRITE (OW). For correct operation, issue an OW command for the table and retry the command. |
|
74-00 |
The LOCK-LATCH specified is invalid. |
If a lock latch is set on a table in a TSR, any update command must match the lock latch value. Correct the LOCK-LATCH value and resubmit the command. If the lock-latch is not known, the tableBASE Administrator can perform the required command overriding the lock-latch with the Master Password. |
|
75-00 |
Dynamic allocation (AL) or un-allocation (UL) failed |
tableBASE command AL (Allocate library) or UL (Un-allocate library) was not successful. |
|
75-01 |
TBTSLIB not allowed as parameter in AL command. |
TBTSLIB is obsolete in V6. It cannot be dynamically allocated with the AL command. |
|
75-02 |
DDNAME specified in AL command already in use. |
Ensure the DDNAME is not already allocated and resubmit the command. |
|
75-03 |
DSNAME specified in AL command not catalogued. |
Ensure the DSNAME for the DDNAME is cataloged and resubmit the command. The AL command only supports catalogued library datasets |
|
75-04 |
DSN enqueue conflict with another region for AL command. |
Determine which region has the SYSDSN enqueue for this table and resolve the conflict. Then reissue the AL command with the appropriate SHR parameter. (Consult the Programming Guide for the usage of the AL command) |
|
75-05 |
Error in DDNAME specified in AL command. |
Correct the DDNAME syntax and resubmit the command. |
|
75-06 |
Syntax error in DSNAME specified in AL command. |
Correct the DSNAME syntax and resubmit the command. |
|
75-07 |
SVC99 failure during execution of AL command. |
An MVS error was generated. Contact your MVS systems programmer to determine why the AL command failed. |
|
75-08 |
DDNAME specified by UL command must be allocated by an AL command. |
The UL (Unallocate) command failed because tableBASE was not used to allocate the DDNAME. Deallocate the DDNAME (TSO FREE) and use the tableBASE AL command to allocate the library dataset. |
|
75-09 |
DDNAME specified by UL command not known or library not open. |
Ensure the DDNAME is allocated. |
|
75-10 |
SVC99 failure during execution of UL command. |
An MVS error was generated. Contact your MVS systems programmer to determine why the UL command failed. |
|
76-00 |
OI (Open Indirect) failed: primary table not sequential or KLOC not 9. |
Ensure the Open Indirect primary table has sequential organization and the key location is 9. Resubmit the command. (See the Programming Guide for details on Open Indirect, or the SI command for more details.) |
|
77-00 |
An alternate index is defined for a table that is not TYPE=P. |
Ensure the data table is defined as a pointer table (TYPE=P) and resubmit the command. |
|
78-00 |
The AL command failed, the SHARE-STATUS parameter must be S or O. |
Correct the SHARE-STATUS sub-parameter of the LIBRARY-ALLOC parameter. (See the Programming Guide for the usage of the AL command.) |
|
79-01 |
The request code for the VV command is invalid. |
The request code value should be 0, 1 or 2. Correct the request code and re-submit the command. (See the tableBASE Administration Guide for more details.) |
|
79-02 |
A VTS initialized as RW cannot be switched to RO mode. |
Only VTS-TSRs initialized as RO can be switched back to RO mode after being switched to RW mode. |
|
79-03 |
The job name does not match the job holding the RW lock for the VTS. |
A VTS can only be switched back to RO mode by the same job step that switched the VTS to RW mode. |
|
79-04 |
The time stamp of the job does not match that holding the RW lock for the VTS. |
A VTS can only be switched back to RO mode by the same job step that switched the VTS to RW mode. |
|
79-05 |
Lock reset failed when switching VTS access to RO. |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support. |
|
79-06 |
Attempt to switch VTS to RW unsuccessful; VTS already locked in RW mode. |
The VTS is already locked in RW mode. If the job locking it is still running, wait for it to complete. If the VTS was left in RW mode due to an abend or some other error, it can be forced back to RO mode using the VV command. See the tableBASE Administration Guide for details. |
|
79-07 |
Lock failed when switching VTS access to RW. |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support. |
|
79-08 |
VTS name mismatch |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support. |
|
79-09 |
No pointer to TSRCNTL |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support. |
|
79-10 |
No pointer to GCE |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support. |
|
79-11 |
VTS-TSR not available |
Ensure that the VTS is not terminating or starting up when the command is issued. |
|
79-12 |
Getmain failed |
Try running the entire job in a larger region. |
|
79-13 |
SAF authorization could not be obtained to switch the access mode for this VTS. |
CONTROL or higher SAF authorization is required. Check with your security administrator to obtain the correct authorization. |
|
79-14 |
VTS in RO mode cannot be switched to RO. |
The VTS is already in RO mode. No switching is required. |
|
79-15 |
Program not authorized for switching VTS access mode. |
In order to switch the access mode of a VTS, a program must be linked with AC(1) and in an authorized library. |
|
80-00 |
Data table is not open; the use of an alternate index not allowed. |
The IA command requires the data table be opened first. The OR command will dynamically open a data table. |
|
80-01 |
Data table must be opened before IA (Invoke Alternate) is issued. |
Open the data table before issuing the IA command. |
|
80-02 |
IA (Invoke Alternate Index) may not reference a linked VTS table. |
Both the alternate and the data table must be opened in the VTS-TSR or opened in the local TSR for IA to succeed. The base table cannot be a linked VTS table. |
|
80-03 |
Open/Invoke Alternate Index must reference a data table. |
Ensure the IA command includes the BASE-TABLE-NAME parameter and resubmit the command. The IA or OR command must reference a data table, either in BASE-TABLE-NAME or the stored definition on the library. |
|
80-04 |
Alternate Index cannot be opened as a linked VTS table. |
The IA command specified an alternate index name which was found in a VTS-TSR. This is not supported. Either specify the complete alternate index definition in the IA command parameters, remove the VTS-TSR from the library list (ML-list), or close the alternate index table in the VTS-TSR and resubmit the command. |
|
81-00 |
The specified Alternate Index definition is not found. |
It the complete alternate index definition is not specified in the IA command parameters, the alternate index definition must be found in a library in the current library list (ML-list). Correct this error and resubmit the command. |
|
83-00 |
Data table INDEX sub-parameter of the DT block must be defined as P. |
If the base table is specified in the IA command, it must be defined as a pointer table (TYPE=P). Redefine the base table. |
|
85-00 |
The command is invalid for an Alternate Index |
The command being invoked is not supported for use with an alternate-index. Correct the error and resubmit the command. |
|
85-01 |
An alternate index may not have the same name as the data table. |
Correct the alternate-index parameters ensuring that the alternate index and base table names are different and resubmit the command. |
|
85-02 |
DV and DW commands are not supported for Alternate index tables |
The DV and DW commands are only supported for base tables since they apply to ensuing STore commands. An alternate index is never stored, only the base table is. |
|
86-00 |
Data table of an Alternate Index may not be a linked VTS table. |
The table failed to open because the alternate-index is in the local TSR, and the data-table is linked to a table in a VTS-TSR. The alternate index must be opened in the same TSR as the data-table. |
|
87-00 |
The KEY-COUNT must be 1 for the definition of the Alternate Index. |
Only a value of 1 for the key-count is supported when defining an alternate-index. Correct the key-count value and resubmit the command. |
|
89-00 |
An invalid parameter was encountered in the TBOPT file. |
During initialization of tableBASE in the region, an error was discovered in the tableBASE runtime options in the TBOPT dataset. Correct the TBOPT parameter(s) and resubmit the job. |
|
90-00 |
Insufficient storage available in region: increase region size. |
There is insufficient main storage available for tableBASE control blocks. Increase the executing region size and resubmit the job (modify the ‘REGION=’ parameter for the jobstep). |
|
91-00 |
I/O Error. |
Determine the reason for the I/O error from the JESMSGLG. Correct the problem and resubmit the command. |
|
91-01 |
I/O Error while attempting to read/write to a tableBASE library. |
Determine the reason for the I/O access error to the tableBASE library. Correct the problem and resubmit the command. |
|
91-02 |
I/O Error while attempting to read from the TBOPT file. |
Determine the reason for the error trying to read from the TBOPT file. Once resolved, resubmit the job. |
|
91-03 |
Error in I/O subtask in multitasking environment. |
The subtask was unable to complete due to an I/O error when TBOPT MULTITASKING=Y. Correct the problem and resubmit the process. |
|
92-00 |
Insufficient Table Space Region (TSR) size. |
The TSR is too small for the tables being opened. Either enlarge the TSR or close unnecessary tables in the TSR to free up the required TSR space. |
|
92-01 |
The space request is bigger than the TSR. |
The table to be opened is too large for the current TSR. The TSR size will need to be increased to accommodate the table to be opened. |
|
92-02 |
Insufficient free space in the TSR: close tables or enlarge TSR. |
The TSR is full and no longer has enough free space available to allow the table to be opened, defined, expanded or changed. Either enlarge the TSR appropriately or close unnecessary tables to free up the required TSR space. |
|
92-03 |
There is insufficient free contiguous space in the TSR |
The TSR is full. There is no longer any contiguous memory left to accommodate the index for the table being opened, defined, expanded or changed. Either enlarge the TSR or close unnecessary tables to free up required TSR space. |
|
92-04 |
There is insufficient space in the TSR to initiate the TCE |
The TSR is full. There is no room to accommodate the tableBASE control block created when opening a table into the TSR. Either enlarge the TSR or close unnecessary tables to free up the required TSR space. |
|
93-00 |
The RF command did not complete |
Correct the error and resubmit the command. |
|
93-01 |
The table must be open for read in order to be refreshed |
Open the table for read (OR) or ReLease the table before submitting the RF command. |
|
93-02 |
The data table or alternates were closed since the table was opened |
There is a change in either the alternate or the data-table that is preventing successful completion of the RF command. CL the table and re-open it from the desired library to get the most recent version of the table into the TSR. |
|
93-03 |
The ROWSIZE changed since the table was opened |
RF failed because the row size for the table on the library was different compared to the table opened in the TSR. CL and reopen the table to get the most recent version of the table into the TSR. |
|
93-04 |
The KEYSIZE changed since the table was opened |
RF failed because the key size for the table on the library was different compared to the table opened in the TSR. CL and reopen the table to get the most recent version of the table into the TSR. |
|
93-05 |
The KEYLOC changed since the table was opened |
RF failed because the key-location for the table on the library was different compared to the table opened in the TSR. CL and reopen the table to get the most recent version of the table into the TSR. |
|
93-06 |
The ORGANIZATION changed since the table was opened |
RF failed because the organization for the table on the library was different compared to the table opened in the TSR. CL and reopen the table to get the most recent version of the table into the TSR. |
|
93-07 |
The SEARCH METHOD changed since the table was opened |
RF failed because the Search-Method for the table on the library was different compared to the table opened in the TSR. CL and reopen the table to get the most recent version of the table into the TSR. |
|
95-00 |
The transaction was terminated during tableBASE processing. |
tableBASE cleanup was invoked because a transaction was terminated while tableBASE was processing. The subcodes document what tableBASE process was executing when the transaction was terminated. This is usually related to a transaction timeout or cancellation. |
|
95-02 |
tableBASE found an invalid row (item) area address |
See 95-00 description. This can be caused by an error in the input parameters provided. |
|
95-03 |
tableBASE found an invalid row address in the Table Space Region (TSR) |
See 95-00 description. Send the documentation (JESMSGLG, TBDUMP, any other dumps) to tableBASE support. |
|
95-04 |
tableBASE abended during an index resorting process. |
See 95-00 description. |
|
95-05 |
tableBASE abended during an index expansion process. |
See 95-00 description. |
|
95-06 |
tableBASE abended during an index entry insertion process. |
See 95-00 description. |
|
95-07 |
tableBASE abended during an index entry deletion process. |
See 95-00 description. |
|
95-08 |
tableBASE abended during an open command. |
See 95-00 description. |
|
95-09 |
tableBASE abended during a close command. |
See 95-00 description. |
|
97-00 |
The ML or LL parameter list is invalid |
Correct the ML or LL parameter list and resubmit the command. |
|
97-05 |
An ML list must not contain a reference to TBTSLIB. |
Remove the reference to TBTSLIB in the ML-list and resubmit the command. |
|
97-08 |
The ML list is invalid in VTS. It contains a reference to a VTS-TSR. |
Remove the reference to the VTS-TSR in the ML-list and resubmit the command. |
|
98-00 |
An internal error occurred in tableBASE Shutdown processing. |
tableBASE termination (XX command) problems. |
|
98-01 |
The XX command is being processed on a subordinate task. |
When multi-tasking is ON, the XX command must be performed by the persistent (mother) task. This command will fail if it is submitted by sub-tasks invoked by the persistent (mother) task. Send the documentation (JESMSGLG, TBDUMP, any other dumps) to tableBASE support. |
|
98-02 |
tableBASE shutdown process did not complete. |
If multi-tasking and a sub-task submitted the XX command, other tasks will first issue a warning, then they will abend. This is the warning. Send the documentation (JESMSGLG, TBDUMP, any other dumps) to tableBASE support. |
|
98-03 |
The subtask that shutdown tableBASE has tried to invoke tableBASE. |
If multi-tasking and a sub-task submitted the XX command, no tasks are allowed to issue tableBASE commands. Send the documentation (JESMSGLG, TBDUMP, any other dumps) to tableBASE support. |
|
1072-00 |
VTS access failed because the specified VTS-TSR is not available. |
VTS access failed because the specified VTS-TSR is not available. Ensure that the VTS job which creates the specified VTS-TSR name is running. |
|
1072-01 |
VTS access failed because the specified PC Server was not running. |
Access to VTS-TSRs depends on a PC Server at the same or higher level than the application is running on the same LPAR. |
|
1072-02 |
VTS close connection failed. |
An attempt to close the VTS connection failed. Refer to message DK100303I in the JESMSGLG for more details. |
|
1072-03 |
SAF READ access required for this operation. |
These operations on the VTS require READ or higher SAF authorization. |
|
1072-04 |
SAF UPDATE access required for this operation. |
These operations on the VTS require UPDATE or higher SAF authorization. |
|
1072-05 |
VTS could not be accessed due to getmain failure for the VTS control block. |
Run the job in a larger region. |
|
1072-06 |
VTS could not be accessed due to corrupt VTS control block. |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support: 1-613-523-5588. |
|
1072-07 |
VTS has stopped running. |
The VTS is terminating or is no longer running. |
|
1072-08 |
VTS could not be found in this version. |
The VTS name does not match any VTS in this version. |
|
1072-09 |
VTS could not be found in the region list of VTS names. |
The VTS does not exist in the region list of VTS names for this version. |
|
1072-10 |
VTS no longer running. |
The VTS was running but has been quiesced. |
|
1072-11 |
VTS re-initialization failed during VTS close. |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support: 1-613-523-5588. |
|
1072-12 |
VTS re-initialization failed during VTS open. |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support: 1-613-523-5588. |
|
1072-13 |
VTS not running. |
The VTS is not running. |
|
1072-14 |
VTS name in region list has been zeroed. |
This is an internal error and cannot be fixed by the client. Please contact DataKinetics Technical Support: 1-613-523-5588. |
|
1072-15 |
The VTS generation number or time stamp does not match the current generation or time stamp. |
The generation number or time stamp of the VTS increases if it has been switched from RO to RW and vice versa or if it has been shut down and restarted. An S in the START-TBUOW field of the COMMAND-AREA can be used to access the most current generation of the VTS. See the tableBASE Programming Guide for more details. For a RO VTS, this error sub-code is returned if the VTS was switched to RW and has now been switched back to RO and the START-TBUOW field does not contain an S. If S is used in the START-TBUOW field after a 1072-15 is issued, and the VTS is still locked in RW mode, a 1072-18 will be returned. |
|
1072-16 |
The VTS is not available for transaction processing. |
The VTS is terminating or is initializing. |
|
1072-17 |
SAF CONTROL access required for this operation. |
These operations on the VTS require CONTROL or higher SAF authorization. |
|
1072-18 |
The VTS is currently locked in RW mode. |
When locked in RW mode, the VTS is only accessible to the RW locker until the job completes. This error sub-code will be returned for the first call, after the VTS is locked in RW mode, when it is accessed by the same transaction or job that had previously accessed it; on subsequent calls, a 1072-15 will be returned. |
|
1072-19 |
SAF ALTER access required for this operation. |
These operations on the VTS require ALTER SAF authorization. |