OpenFrame/Base Error Codes
This chapter describes the scope of error codes and individual errors associated with OpenFrame/Base.
1. Overview
The following is an overview of the scope of error codes and associated modules in OpenFrame/Base (hereafter Base).
Error Code Base | Module | Description |
---|---|---|
-0 |
Manages non-VSAM data sets and handles I/O. |
|
-1000 |
Manages VSAM data sets and handles I/O. |
|
-2000 |
Provides standardized interfaces for all data sets. |
|
-3000 |
Provides an integrated catalog function. |
|
-4000 |
Manages creation and deletion of data sets and catalog functions. |
|
-5000 |
Handles allocations for data sets. |
|
-6000 |
Shows information for volumes and manages VTOC. |
|
-7000 |
Lock server client module. |
|
-8000 |
Searches allocated data sets by DD name. |
|
-10000 |
Manages data sets including data set allocation. |
|
-11000 |
Provides functions such as SMS and ACS. |
|
-12000 |
data set common library module. |
|
-15000 |
Manages code page conversions. |
|
-17000 |
Manages OpenFrame system security. |
|
-22000 |
OpenFrame common library module. |
|
-23000 |
Provides an interface between SAF (OpenFrame system security module) and the authentication server. |
|
-24000 |
Provides an interface between SAF (OpenFrame system security module) and online products. |
|
-26000 |
Provides an interface between SAF (OpenFrame system security module) and Batch. |
|
-27000 |
Allocates and manages dynamic memory. |
|
-28000 |
Checks OpenFrame licenses. |
|
-29000 |
Manages memory in tree structure. |
|
-32000 |
Tmax server common library module. |
|
-34000 |
Provides OpenFrame console functions. |
|
-36000 |
Manages spool data sets and handles I/O. |
|
-93000 |
Manages SMF log files. |
2. Non-VSAM (-0)
The Non-VSAM module is responsible for managing non-VSAM data sets and I/O to data sets. This section lists error codes that can occur in the Non-VSAM module, descriptions of errors and suggested corrective actions.
NVSM_ERR_NOT_FOUND (-301)
Description |
There exists no records corresponding to a given key value. |
Action |
Check whether the key value is correctly configured. |
Note |
NVSM_ERR_END_OF_FILE (-302)
Description |
The end of a file (EOF) has been reached during sequential reading of a non-VSAM data set. |
Action |
Check for a valid logic that can be applied when an application reaches EOF. |
Note |
NVSM_ERR_MEMORY_ALLOC (-303)
Description |
Memory allocation failed. |
Action |
Check for a sufficient memory space in the system. |
Note |
NVSM_ERR_NOT_IMPLEMENTED (-304)
Description |
An attempt was made to use an ISAM that is not supported by non-VSAM in OpenFrame. |
Action |
Use VSAM. |
Note |
NVSM_ERR_NOT_ALLOWED (-305)
Description |
The I/O mode, DSORG, or DEVTYP (device type) is incorrectly configured for a submitted job. |
Action |
Check whether I/O mode, DSORG or DEVTYP is correctly configured. |
Note |
NVSM_ERR_INVALID_REQUEST (-306)
Description |
An invalid DCB value or mode is configured in Non-VSAM. |
Action |
Check whether the DCB value or mode is correctly configured. |
Note |
NVSM_ERR_INVALID_FILELIST (-307)
Description |
An attempt was made to execute OPEN a data set without specifying the file structure list containing non-VSAM data set information. |
Action |
Specify the file structure list. |
Note |
NVSM_ERR_INVALID_FILE (-308)
Description |
An attempt was made to execute CREATE, ERASE, RENAME or STAT for a data set without specifying the file structure list containing non-VSAM data set information. |
Action |
Specify the file structure list. |
Note |
NVSM_ERR_INVALID_DSNAME (-401)
Description |
An attempt was made to execute RENAME for a data set without specifying a new name. |
Action |
Specify a new name. |
Note |
NVSM_ERR_INVALID_STAT (-402)
Description |
An attempt was made to execute STAT for a data set without specifying the structure to contain the data set information. |
Action |
Specify the structure to contain the data set information. |
Note |
NVSM_ERR_INVALID_FD (-501)
Description |
The file descriptor specified for non-VSAM data sets is invalid. |
Action |
Check whether OPEN is successfully executed on non-VSAM data sets. |
Note |
NVSM_ERR_MAX_FILES (-502)
Description |
Exceeded the maximum number of non-VSAM data sets that can be concurrently opened. |
Action |
Close unused data sets and retry. |
Note |
NVSM_ERR_INVALID_ADDR (-503)
Description |
An attempt was made to FIND a data set with an address, whose value is out of the scope of the BLDL list. |
Action |
Check whether the address value does not exceed the number of BLDL lists. |
Note |
NVSM_ERR_MEMBER_NOT_FOUND (-504)
Description |
An attempt was made to FIND a data set with a member name that cannot be found by the given string. |
Action |
Check whether the string used for the member name is correct. |
Note |
NVSM_ERR_INVALID_BLDL (-505)
Description |
An attempt was made to FIND a data set with an address without a valid BLDL list. |
Action |
Check whether the BLDL command has been executed before executing FIND. |
Note |
NVSM_ERR_MEMBER_DUPLICATE (-506)
Description |
A duplicate member was added when executing the STOW command. |
Action |
Delete the existing member or change the name of a new member to be added. |
Note |
NVSM_ERR_SMALL_BUFFER_SIZE (-507)
Description |
The internal buffer size of non-VSAM is smaller than LRECL. |
Action |
Increase the VALUE of the NVSM_BUFFER_SIZE key, in the data set_DEFAULT section of the ds subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
NVSM_ERR_STOW_CHANGE_PARM (-508)
Description |
The CHANGE command was executed with an invalid parameter type in a STOW program. |
Action |
Check the parameter. |
Note |
NVSM_ERR_INVALID_MEMBER_LEN (-509)
Description |
A data set member name was specified with an invalid length. |
Action |
Check the length of the name. The length of a data set member name can contain 8 to 63 characters. |
Note |
NVSM_ERR_LOCK_DETECTED (-510)
Description |
A non-VSAM data set file is locked. |
Action |
Check whether the file is not occupied by another process. |
Note |
NVSM_ERR_INVALID_CONCATENATION_DSORG (-511)
Description |
An invalid data set was specified for data set concatenation. |
Action |
Do not specify a PDS or PDS member when concatenating. |
Note |
NVSM_ERR_INVALID_BUF_SIZE (-601)
Description |
The length of the data buffer is smaller than that of the record when executing the GET (READ) command. |
Action |
Modify the length of the data buffer to be at least as long as file’s record length. |
Note |
NVSM_ERR_INVALID_KEY (-602)
Description |
The READ and WRITE commands were executed using BDAM without specifying the key value. |
Action |
Check whether the key value has been specified. |
Note |
NVSM_ERR_GET_RDW_FAIL (-603)
Description |
Failed to read the Record Description Word (RDW) information. |
Action |
Check for a valid variable length data set. |
Note |
NVSM_ERR_PUT_RDW_FAIL (-604)
Description |
Failed to store the RDW information. |
Action |
Check for a sufficient storage space. |
Note |
NVSM_ERR_NOT_END_WITH_NEWLINE (-606)
Description |
\n is not found at the end of the record when RECFM is an L type (Line Sequential) and the specified mode is Move Mode. |
Action |
Add \n to the end of the record. |
Note |
NVSM_ERR_LOCATE_FAIL (-607)
Description |
An internal buffer error occurred when executing PUTX (REWRITE). |
Action |
Contact TmaxSoft Technical Support. |
Note |
NVSM_ERR_INVALID_GET_RECL (-608)
Description |
The length of the most recent record read by GET (READ) is not found. |
Action |
Check whether GET (READ) has been executed immediately before calling PUTX (REWRITE). |
Note |
NVSM_ERR_SIZE_LIMIT_OVER (-609)
Description |
The current data set size exceeds the available space. |
Action |
Check the DCB SPACE information to determine if the program’s I/O operation for the data set results in an endless loop. |
Note |
NVSM_ERR_PUTX_SIZE (-610)
Description |
The length of the record to execute PUTX (REWRITE) does not match the length of the last read record. |
Action |
Ensure the length of the record to execute PUTX matches the length of the last read record. |
Note |
NVSM_ERR_PUT_MULTIPLE_RECORDS (-611)
Description |
Multiple records are included in a single PUT (WRITE) action, when the record type is L. |
Action |
Write only one record in one action. |
Note |
NVSM_ERR_WRITE_LEGTH (-612)
Description |
The record was not written in a proper length. |
Action |
Retry the action. |
Note |
NVSM_ERR_OUTLIM_OVER (-613)
Description |
An output that takes place in the spool exceeds the OUTLIM configuration. |
Action |
Check the OUTLIM setting in JCL or the OUTLIM key in the DD section of the tjclrun subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. For JCL configuration, refer to OpenFrame JCL Reference Guide. |
NVSM_ERR_OVERLRECL_RECORD (-614)
Description |
The written length of a record is longer than LRECL. |
Action |
Check for the validity of the data set file by comparing the LRECL value with the actual record length. |
Note |
NVSM_ERR_BROKEN_data set (-615)
Description |
The length in data set DCB information is not the same as the actual data length. |
Action |
Check if the data set is broken. |
Note |
NVSM_ERR_INVALID_KEYLEN (-616)
Description |
The KEY length is invalid when starting non-VSAM. |
Action |
Contact TmaxSoft Technical Support. |
Note |
NVSM_ERR_BOUNDARY_VIOLATION (-617)
Description |
The written data is larger than BLOCK SIZE when handling a DAM file. |
Action |
Check the size of data to WRITE. |
Note |
NVSM_ERR_PDSDIR_OPEN_MODE (-701)
Description |
An incorrect open mode was specified when accessing a PDS directory. |
Action |
Specify read or read/write as open mode. |
Note |
NVSM_ERR_PDSDIR_CORRUPTED (-702)
Description |
The PDS directory is not valid. |
Action |
Check for the validity of the PDS directory. |
Note |
NVSM_ERR_PDSDIR_IO_FAILURE (-703)
Description |
An error occurred during a PDS directory I/O. |
Action |
Contact TmaxSoft Technical Support, with the PDS information for I/O. |
Note |
NVSM_ERR_PDSDIR_NO_PAGE (-704)
Description |
The PDS directory page is not found. |
Action |
Contact TmaxSoft Technical Support, with the PDS information for I/O. |
Note |
NVSM_ERR_PDSDIR_DIRECTORY_NOT_FOUND (-705)
Description |
The PDS directory is not found. |
Action |
Check whether the PDS has been correctly created, and create a new PDS directory if necessary. |
Note |
NVSM_ERR_PDSDIR_ELEMENT_NOT_FOUND (-706)
Description |
The PDS element is not found. |
Action |
Contact TmaxSoft Technical Support, with the PDS information for I/O. |
Note |
NVSM_ERR_PDSDIR_DUPLICATE (-707)
Description |
A member with a duplicate name already exists in the PDS directory. |
Action |
Specify another name that is unique in the PDS. |
Note |
NVSM_ERR_CONSOLE_DISPLAY (-851)
Description |
An error occurred while printing data set file information in console. |
Action |
Contact TmaxSoft Technical Support. |
Note |
NVSM_ERR_SYSTEM_CREAT (-900)
Description |
Failed to call the create() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_UNLINK (-901)
Description |
Failed to call the unlink() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_RENAME (-902)
Description |
Failed to call the rename() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_OPENDIR (-903)
Description |
Failed to call the opendir() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_MKDIR (-904)
Description |
Failed to call the mkdir() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_RMDIR (-905)
Description |
Failed to call the rmdir() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_ACCESS (-906)
Description |
Failed to call the access() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_OPEN (-910)
Description |
Failed to call the open() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_READ (-911)
Description |
Failed to call the read() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_WRITE (-912)
Description |
Failed to call the write() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_LSTAT (-913)
Description |
Failed to call the lstat() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_LSEEK (-914)
Description |
Failed to call the lseek() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_CLOSE (-915)
Description |
Failed to call the close() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_TRUNCATE (-916)
Description |
Failed to call the truncate() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_FCNTL (-917)
Description |
Failed to call the fcntl() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_MKSTEMP (-918)
Description |
Failed to call the mkstemp() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_CHMOD (-919)
Description |
Failed to call the chmod() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_FOPEN (-920)
Description |
Failed to call the fopen() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_FREAD (-921)
Description |
Failed to call the fread() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_FWRITE (-922)
Description |
Failed to call the fwrite() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_POPEN (-930)
Description |
Failed to call the popen() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_PCLOSE (-931)
Description |
Failed to call the pclose() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_LOCALTIME (-940)
Description |
Failed to call the localtime() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
NVSM_ERR_SYSTEM_SIGNAL (-950)
Description |
Failed to call the signal() system function. |
Action |
Check the system function call error messages printed in spool. |
Note |
3. TSAM (-1000)
The TSAM module is responsible for managing VSAM data sets and I/O to data sets. This section lists error codes that can occur in the TSAM module, descriptions of errors and suggested corrective actions.
TSAM_ERR_DUPLICATE_RECORD (-1001)
Description |
An attempt was made to add a record containing a duplicate record identifier to a KSDS or RRDS data set containing unique attributes. |
Action |
Throw an exception according to the requirements of the application, or modify the application logic or data. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DUPLICATE_KEY (-1002)
Description |
There are many duplicate records with the same key value, when sequentially reading records by using a non-unique alternate index path, therefore sequential reading is no longer possible. |
Action |
Handle the error according to the requirements of the application. If there are duplicate records with the same alternate key, use the READ NEXT option for a sequential read. To disregard the records having the same alternate key, perform direct access with the READ option after resetting the key. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_NOT_FOUND (-1003)
Description |
Records corresponding to the specified record identifier are not found in the data set. |
Action |
Handle the error according to the requirements of the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_END_OF_FILE (-1004)
Description |
The end of a data set (READ NEXT) or the beginning of a data set (READ PREV) is passed, during a sequential read operation. |
Action |
Handle the error according to the requirements of the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_RECORD_LOCKED (-1005)
Description |
The record to READ for an UPDATE or REWRITE with the NOSUSPEND option is locked by another application. |
Action |
Check if certain applications that cannot run simultaneously are running. If such concurrent operations are intended, remove the NOSUSPEND option and modify the application so that TSAM can resolve the problem. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_RECORD_BUSY (-1006)
Description |
A record to READ with the NOSUSPEND option is locked by another application. |
Action |
Remove the NOSUSPEND option and modify the application so that TSAM can resolve the problem, or retry the READ operation a few moments later. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_LENGTH_ERROR (-1007)
Description |
An attempt was made to save a record with a different length from the length specified in the data set definition (DEFINE), to a fixed-length data set, or to save a record with a longer length than the maximum record length defined in the data set definition, to a variable-length data set. |
Action |
Adjust the record buffer length transmitted to the application’s WRITE, or redefine the data set if the the data set definition is incorrect. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_INVALID_REQUEST (-1008)
Description |
Parameters submitted to use with the TSAM API are invalid. |
Action |
Modify the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_NOT_ALLOWED (-1009)
Description |
An attempt was made to use an action that is not allowed in a mode used to open the data set. For example, if you try to WRITE in a data set opened as Read-Only, this error will occur. |
Action |
Modify the application so that other necessary open modes are added or any not-allowed action cannot be used. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_NO_SPACE (-1010)
Description |
The data set has not enough storage space. |
Action |
Check the available tablespace for the TSAM data set and sufficient disk space in the file system. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_MEMORY_ALLOC (-1011)
Description |
Unable to operate additional applications because of insufficient memory. |
Action |
Check for a continuous memory leak from certain applications, or if there are any common application faults such as a request for an incorrect size of memory allocation (negative value). Also, verify whether the memory limit set in the user environment where the application runs is not too low. |
Note |
TSAM_ERR_IO_FAILURE (-1012)
Description |
An error occurred during disk I/O. |
Action |
Contact the system administrator. |
Note |
TSAM_ERR_INVALID_OPERATION (-1013)
Description |
A request for an action that is not valid in the data set architecture was made. For example, when deleting records from an ESDS data set, this error occurs. |
Action |
This error is Descriptiond by a request for an action that is not supported by the data set architecture. Therefore, modify the application so that any function call that can be problematic cannot be used. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_INTERNAL (-1015)
Description |
TSAM server’s internal error. In most cases, the tablespace to be used as the volume to store TSAM data sets is not created, or the VVDS table for the volume is not found. Other internal server errors that are not classified return this error code. |
Action |
Create the required tablespace. If the VVDS table does not exist, add the volume using the voladd tool. For any other unclassified internal server errors, contact TmaxSoft Technical Support. |
Note |
TSAM_ERR_NOT_IMPLEMENTED (-1016)
Description |
An attempt was made to use a non-supported function. |
Action |
Modify the application so that the non-supported function cannot be used. If modification is not possible, contact TmaxSoft Technical Support. |
Note |
TSAM_ERR_MISMATCH_KEY_FIELD (-1017)
Description |
The position of the specified key does not match with the boundary of the copybook field, when creating a KSDS. |
Action |
Check again the key position when creating a KSDS, and if there is no problem, match the key field of the copybook with the specified key position. The number of key fields can be more than two, but the fields must be used entirely, not partially. |
Note |
TSAM_ERR_MISMATCH_LRECL (-1018)
Description |
The specified record length does not match with the entire size of the copybook, when creating a TSAM. |
Action |
Match the record length with the size of the copybook. |
Note |
TSAM_ERR_INVALID_MI_COUNT (-1019)
Description |
The count of mass insert specified under OpenFrame Configuration for creating TSAM is invalid. |
Action |
Specify a valid value by referencing the MASSINSERT_COUNT key, in the TSAM_RDB section of the ds subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
TSAM_ERR_INVALID_OPEN_MODE (-1020)
Description |
An empty TSAM data set with the NOREUSE attribute is not allowed to open as output. |
Action |
Use another open mode, or execute the IDCAMS ALTER command to change the attribute from NOREUSE to REUSE. |
Note |
TSAM_ERR_INCOMPATIBLE_TEMPLATE_USED (-1021)
Description |
An attempt was made to execute TSAM OPEN/CREATE/COPY/LIBGEN by using a TSAM template file that is incompatible with the TSAM module currently in use. |
Action |
Use a compatible TSAM template file. |
Note |
TSAM_ERR_INVALID_CONN_ID (-1101)
Description |
An incorrect connection ID that had never been used for connection was provided as the connection ID for a TSAM API. |
Action |
Modify the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_MAX_CONNECTIONS (-1102)
Description |
The number of requests for tsam_connect() exceeds the maximum number of concurrent connections. |
Action |
Increase the maximum number of sessions for the TSAM server and restart the server. Also, check whether any unnecessary connections are made by applications. It is recommended to call tsam_disconnect() to end any unnecessary connections. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DUPLICATE_CONN_ID (-1103)
Description |
A duplicate connection ID that had been already provided to the CONNECT API was used. |
Action |
Modify the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_TX_STILL_ACTIVE (-1104)
Description |
A non-terminated transaction exists even after executing the DISCONNECT API. |
Action |
Modify the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_CONNECT_FAILURE (-1105)
Description |
Failed to connect because of a network or TSAM server failure. |
Action |
Check for proper operation of the TSAM server. If the TSAM server operates normally, verify if there is a network failure to the host where the TSAM server is operating. Additionally, use a parameter of the CONNECT API to check if the server host name, IP or port number has been correctly set. You can also verify whether the value specified to the TB_CONN_TIMEOUT or TB_READ_TIMEOUT (in seconds) environment variable is not too small. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_AUTHENTICATION_FAILURE (-1106)
Description |
Failed to authenticate the user through USERNAME and PASSWORD which have been passed as parameters to the CONNECT API. |
Action |
Check if the USERNAME and PASSWORD parameters passed to the CONNECT function are correct. Also, verify whether the user is found in the TSAM server and holds the proper privileges to perform CONNECT. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_INVALID_DATABASE (-1107)
Description |
Failed to determine which server to connect to because the database connection string, out of the connection information provided to the CONNECT API, is invalid. |
Action |
Check whether the connection information provided to the CONNECT API, the database connection string in particular, is correct. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DISCONNECTED (-1108)
Description |
Connection to the TSAM server through the CONNECT API is abnormally ended. |
Action |
Check if the TSAM server is normally operating and whether there is no network failure on the host. Also, verify if the value of the TB_CONN_TIMEOUT or TB_READ_TIMEOUT environment variable is not set too low. |
Note |
Refer to OpenFrame TSAM Guide. |
TSAM_ERR_FAIL_OVER_RECONNECT (-1109)
Description |
Reconnection occurred after the database used by a TSAM library had been disconnected. |
Action |
Operation is not affected. Check the logs for more information. |
Note |
TSAM_ERR_INVALID_TX_ID (-1201)
Description |
A negative or incorrect value is assigned to txid when using TSAM transaction control variable(s) or TSAM transaction control variables are used without first calling the CONNECT API. |
Action |
Check whether the application is properly coded according to the general TSAM API usage rules. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_MAX_TRANSACTIONS (-1202)
Description |
The maximum txid allowed for a single TSAM client program is exceeded. |
Action |
Since only one transaction is supported for a connection, too many simultaneous connections Description this error. Check if the application continuously calls the CONNECT API without calling the DISCONNECT API. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DUPLICATE_TX_ID (-1203)
Description |
A txid that has not been given to TX END after TX START is given to TX START again. |
Action |
Modify the application so that the same txid value is not used. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_TX_STARTED_ALREADY (-1204)
Description |
A connection initiated by TX START is repeatedly referenced by TX START. |
Action |
Modify the application to not repeatedly call TX START with the same connection ID. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_TX_START_FAILURE (-1205)
Description |
TX START failed in the TSAM server. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_TX_COMMIT_FAILURE (-1206)
Description |
A transaction commit failed in the TSAM server. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_TX_ROLLBACK_FAILURE (-1207)
Description |
A Transaction Rollback failed in TSAM server. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_INVALID_FD (-1301)
Description |
A negative value is assigned to the FD value which is used as a parameter for the OPEN API or functions that follow it, or an FD value that has not been opened is used. |
Action |
Check if the application calls functions to perform record I/O on a data set without calling the OPEN API. Also, verify if the FD that has been closed is still in use, and correct it. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_MAX_OPEN_FILES (-1302)
Description |
The maximum number of tsam_open() calls from a single TSAM client (1024) is exceeded. |
Action |
Check if there are cases where the OPEN API is called without the corresponding CLOSE API in the application, and correct it. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DUPLICATE_FD (-1303)
Description |
The OPEN API is called using the same FD as one that has already been used in another OPEN API without closing it. |
Action |
Modify the application to not use the same FD to call several OPEN APIs. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_FILE_NOT_FOUND (-1304)
Description |
A data set to be used by the OPEN API is not found. |
Action |
Run the application after the required data set is defined. (DEFINE CLUSTER) |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_VOLUME_NOT_FOUND (-1306)
Description |
The tablespace, corresponding to a volume serial that was passed as a parameter when calling the CREATE API to create a data set, has not been created on the TSAM server. |
Action |
Create the tablespace corresponding to the volume first, and add it by using the voladd tool before running the application. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_FILE_NO_PERMISSION (-1307)
Description |
An attempt was made to create a TSAM in the user account, without permission to access the copybook file. |
Action |
Check the user’s access to the copybook file. |
Note |
TSAM_ERR_FILE_NOT_REGULAR (-1308)
Description |
An attempt was made to create a TSAM with a copybook that is not a valid regular file. |
Action |
Check the validity of the copybook file. |
Note |
TSAM_ERR_ENTRY_DEFINED_ALREADY (-1317)
Description |
An attempt was made to redefine an already defined TSAM data set without deleting it. |
Action |
Schedule batch jobs in an appropriate order. Alternatively, delete the data set first before redefining it. Check if the jobs are running in the correct order. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DEADLOCK (-1325)
Description |
A deadlock has been detected in the TSAM server. |
Action |
Modify the application logic so that all locks are unlocked upon detection of a deadlock, then another attempt is made. Generally, end the application that received the DEADLOCK error and restart it. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_RBA_SEQ_NOT_FOUND (-1326)
Description |
The RBA sequence number information for the target ESDS is not found in the RBA table. |
Action |
Check whether any entries under the volume and name of the ESDS exist in the OFM_BASE_RBA. If no entries exist, contact TmaxSoft Technical Support. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_INVALID_TOKEN (-1401)
Description |
The token value given as a parameter to the REWRITE and UNLOCK API is not returned after being created with the READ FOR UPDATE API. Alternatively, the returned token value resulting from calling the READ FOR UPDATE API has been changed because of an application error. |
Action |
Check if the returned token value resulting from calling the READ FOR UPDATE API was changed because of an application error, and correct it. Also, if the READ FOR UPDATE APIs are repeatedly called in a row without using the UNLOCK API, correct it. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_MAX_LOCK_TOKENS (-1402)
Description |
The maximum number of lock tokens (1024) is exceeded by performing too many READ FOR UPDATE APIs sequentially, without using the UNLOCK API. |
Action |
Revise the code responsible for calling the READ FOR UPDATE API multiple times without first using the UNLOCK API, to avoid exceeding the maximum possible number of lock tokens. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_TX_NOT_STARTED (-1403)
Description |
A TSAM record I/O API (READ, WRITE, REWRITE, DELETE…) was used without having first called the TX START API. |
Action |
Check if the application is built according to the general TSAM API usage rules. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_KEYLENGTH (-1405)
Description |
The TSAM API function’s keylen value is different from the key length given when defining a data set. |
Action |
Check if the key length value is wrong in the application and correct it. Note that when setting the GENERIC option, the key length value can be set smaller than the one set when defining the data set. When setting the RBA or RRA option, the key length is always considered 4 bytes. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_GENERIC_KEYLENGTH (-1406)
Description |
A keylen and the GENERIC option conflict (such as by being the same size or a negative value), because when the TSAM API function’s keylen has the GENERIC option, the given keylen must be assigned a smaller value than the keylen assigned when the data set was defined. |
Action |
Remove the GENERIC option from the application or change the keylen value. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_INVALID_REQUEST_ID (-1501)
Description |
reqid is assigned an out-of-range value when calling the START BR, END BR, RESET BR, READ NEXT, and READ PREV APIs for the BROWSE operation or when calling the END BR, RESET BR, READ NEXT, and READ PREV APIs with a reqid that has not been given to START BR. |
Action |
Modify the application to assign an appropriate reqid value. The reqid value assigned when calling the END BR, RESET BR, READ NEXT, and READ PREV APIs must be the same as the reqid value assigned when calling START BR. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_MAX_REQUEST_IDS (-1502)
Description |
The maximum number of BROWSERs in a single data set OPEN call (16) is exceeded. |
Action |
Check if the application repeatedly performs START BR more times than the limit (16) without performing END BR, and then correct it. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_DUPLICATE_REQUEST_ID (-1503)
Description |
A previously created reqid of BROWSER by START BR is passed on to START BR without first using END BR. |
Action |
Modify the application to contain both START BR and END BR for a single reqid. |
Note |
Refer to OpenFrame Data Set Guide. |
TSAM_ERR_SCHEMA_FILE_OPEN (-1701)
Description |
Failed to open the copybook or include file required for creating a TSAM. |
Action |
Check the validity of the copybook or include file required for the TSAM data set to be created. |
Note |
TSAM_ERR_SCHEMA_PARSING_FAILED (-1702)
Description |
Failed to parse statements in the copybook or include file required for creating a TSAM. |
Action |
Check for syntax error in the copybook or include file required for the TSAM data set to be created, by referring to the displayed error message. If no syntax error is found, contact TmaxSoft Technical Support. |
Note |
TSAM_ERR_SCHEMA_COLUMN_ERROR (-1703)
Description |
The number of fields in the copybook or include file required for creating a TSAM is invalid. |
Action |
Check whether the number of fields falls within the range of 1 to 2000. |
Note |
TSAM_ERR_SCHEMA_INVALID_COPYBOOK (-1704)
Description |
An invalid syntax is found in the copybook file required for creating a TSAM. |
Action |
Correct the syntax error by referring to the displayed error message. |
Note |
TSAM_ERR_ALLOC_RDB_OBJECT (-1901)
Description |
Failed to allocate an RDB object. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_FREE_RDB_OBJECT (-1902)
Description |
Failed to free an RDB object. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_DEFINE_VARIABLE (-1903)
Description |
Failed to define an RDB host variable. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_BIND_VARIABLE (-1904)
Description |
Failed to bind an RDB host variable. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_PREPARE_STATEMENT (-1905)
Description |
Failed to prepare execution of an SQL statement. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_EXECUTE_STATEMENT (-1906)
Description |
Failed to execute an SQL statement. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_FETCH_STATEMENT (-1907)
Description |
Failed to fetch an RDB row. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_RETRIEVE_ROWID (-1908)
Description |
Failed to retrieve an RDB ROWID. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_RETRIEVE_ROW_COUNT (-1909)
Description |
Failed to retrieve the row counts in an RDB table. |
Action |
Refer to the displayed Oracle error message. |
Note |
Refer to Oracle Database Error Messages. |
TSAM_ERR_TABLE_NAME_LENGTH (-1910)
Description |
There exists a table name that exceeds 32 bytes when a data set name is converted to a table name during a data set creation in the TSAM server. |
Action |
When creating a TSAM data set by calling the CREATE API, if a data set name exceeds 26 bytes, the name of the data set must be changed into a table name, by using tsam_filename(), which converts the data set name into a table name with a length of 32 bytes. The table name must not exceed 32 bytes when creating a TSAM data set table by using SQL, without using IDCAMS or JCL. |
Note |
Refer to OpenFrame Data Set Guide. |
4. DSIO (-2000)
DSIO is a module responsible for providing a standardized interface for all data sets (non-VSAM, VSAM, and SPOOL). This section lists the error codes that can occur in the DSIO module, descriptions of errors and suggested corrective actions.
DSIO_ERR_DUPLICATE_RECORD (-2001)
Description |
A duplicate records with the same key value exists when executing WRITE to a VSAM KSDS or RRDS data set. |
Action |
Check for a record with the same key value in the data set. This error occurs as a result of an incorrect business logic or an improper job procedure. |
Note |
Refer to "Chapter 3. VSAM Data Set" in OpenFrame Data Set Guide. |
DSIO_ERR_DUPLICATE_KEY (-2002)
Description |
A duplicate key has been detected when executing READ or WRITE in a data set where duplicate keys are allowed (auxiliary index data set). |
Action |
This message merely informs you of the detection of a duplicate key, therefore you can ignore it. If you need to perform a special business logic when a duplicate key has been detected, fork the application logic. |
Note |
Refer to "Chapter 3. VSAM Data Set" in OpenFrame Data Set Guide. |
DSIO_ERR_NOT_FOUND (-2003)
Description |
The record given to perform READ from VSAM KSDS or RRDS data sets is not found. |
Action |
This is a common error that can occur from general business applications. A proper countermeasure against this situation must be implemented in the business logic. |
Note |
Refer to "Chapter 3. VSAM Data Set" in OpenFrame Data Set Guide. |
DSIO_ERR_END_OF_FILE (-2004)
Description |
The end of a file (EOF) has been reached while performing sequential READ commands for a sequential or VSAM data set. |
Action |
This is a common error that can occur from general business applications. A proper countermeasure against this situation must be implemented in the business logic. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_RECORD_LOCKED (-2005)
Description |
An attempt was made to execute READ FOR UPDATE to a VSAM data set, when the target record has been already locked by another application. |
Action |
Wait until the record is unlocked, then execute READ FOR UPDATE again. Alternatively, remove the NOSUSPEND option. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_RECORD_BUSY (-2006)
Description |
An attempt was made to execute READ from a VSAM data set, when the target record is locked by another application. |
Action |
Wait until the record is unlocked, then execute READ again. Alternatively, remove the NOSUSPEND option. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_INVALID_REQUEST (-2008)
Description |
A mandatory parameter was not passed when using the DSIO library API. |
Action |
Modify the source code that Descriptiond the error so that mandatory parameters are passed when calling the DSIO library API. |
Note |
DSIO_ERR_NOT_ALLOWED (-2009)
Description |
An attempt was made to perform an action that is not allowed in a mode used to open the data set. |
Action |
Check the data set type and modify the application to only use the allowed commands, or specify a correct open mode to open a data set. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_NO_SPACE (-2010)
Description |
A data set to perform WRITE has not enough storage space. |
Action |
Increase the available disk space for non-VSAM data sets, or the tablespace capacity for VSAM data sets. |
Note |
DSIO_ERR_MEMORY_ALLOC (-2011)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
DSIO_ERR_INTERNAL (-2012)
Description |
Internal error occurred in the DSIO library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_NOT_IMPLEMENTED (-2013)
Description |
Internal error (Not Implemented) occurred in the DSIO library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_FILE_NOT_FOUND (-2014)
Description |
The data set to be processed cannot be found. In many cases, the data set has been cataloged without physical storage allocated. |
Action |
In the case of a non-VSAM data set, check whether the file exists in the volume directory. In the case of a VSAM data set, check whether the table exists in the volume tablespace. |
Note |
DSIO_ERR_SHOULD_NOT_OCCUR (-2015)
Description |
Internal error (Unrealistic Condition) occurred in the DSIO library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_REWRITE_SIZE (-2016)
Description |
An attempt was made to REWRITE a record in a data set with a different length than that of the previous record. |
Action |
The record length to REWRITE must be the same as the previous record. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_BUFFER_OVERFLOW (-2017)
Description |
The length of the data set record to read is bigger than the buffer size. |
Action |
Provide a record buffer that is larger than the data set record. |
Note |
DSIO_ERR_CONFLICT_FLAGS (-2018)
Description |
An incompatible flag has been set for VSAM KSDS I/O. |
Action |
Request compatible I/O commands for the VSAM KSDS type. |
Note |
DSIO_ERR_INVALID_FILESEQUENCE (-2019)
Description |
An out-of-range file sequence has been requested during a non-VSAM data set I/O. |
Action |
Request a file sequence that falls within the range of the data set. |
Note |
DSIO_ERR_BOUNDARY_VIOLATION (-2020)
Description |
An attempt was made to WRITE data exceeding the BLOCK SIZE during a non-VSAM data set I/O. |
Action |
Check the length of the data to WRITE. |
Note |
DSIO_ERR_INVALID_OPEN_MODE (-2021)
Description |
An empty TSAM data set with the NOREUSE attribute is not allowed to open as output. |
Action |
Use another open mode, or execute the IDCAMS ALTER command to change the attribute from NOREUSE to REUSE. |
Note |
DSIO_ERR_INVALID_CONN_ID (-2101)
Description |
An invalid connection ID has been specified while using the DSIO library API directly. |
Action |
Modify the source code that Descriptiond the error, to pass a correct connection ID when calling the DSIO library API. |
Note |
DSIO_ERR_MAX_CONNECTIONS (-2102)
Description |
The number of connection requests exceeds the maximum number of simultaneous connections to use a VSAM or non-VSAM data set when using the DSIO library API directly. |
Action |
Modify the source code to share connections when using a VSAM or non-VSAM data set. |
Note |
DSIO_ERR_DISCONNECTED (-2103)
Description |
The connection to the VSAM server has been lost while performing I/O functions such as READ or WRITE on the data set. |
Action |
Check the status of the VSAM data set server and analyze the log to determine the reason for the disconnection. |
Note |
DSIO_ERR_INVALID_TX_ID (-2201)
Description |
An invalid transaction ID has been specified while using the DSIO library API directly. |
Action |
Modify the source code to send an appropriate transaction ID when calling the DSIO library API. |
Note |
DSIO_ERR_MAX_TRANSACTIONS (-2202)
Description |
The number of transactions exceeds the maximum number allowed for data set I/O, when using the DSIO library API directly. |
Action |
Modify the source code to close an existing transaction before starting a new transaction. |
Note |
DSIO_ERR_INVALID_FD (-2301)
Description |
An invalid file descriptor has been specified while using the DSIO library API directly. |
Action |
Modify the source code to send an appropriate file descriptor to call the DSIO library API. |
Note |
DSIO_ERR_MAX_OPEN_FILES (-2302)
Description |
More data sets are opened than allowed. |
Action |
Close any data sets that are no longer in use, before opening another data set. |
Note |
Up to 1,024 data sets can be opened concurrently in a single process. |
DSIO_ERR_TSAM_CONFIGURATION (-2401)
Description |
A problem occurred to the configuration file to access the VSAM data set server. |
Action |
Check whether the [TSAM_CLIENT] section in the dbconn.conf file to correct the problem. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_NOT_INITIALIZED (-2403)
Description |
The DSIO BATCH library API is used directly without calling the initialization function. |
Action |
Modify the source code to call the initialization function first before calling the DSIO library API. |
Note |
DSIO_ERR_CLOSED_WITH_LOCK (-2404)
Description |
A data set to OPEN is already locked with the CLOSE WITH LOCK option. |
Action |
Modify the application program. |
Note |
DSIO_ERR_LOAD_FILE_OPEN (-2405)
Description |
Failed to OPEN a file when copying the file to edit a data set. |
Action |
Check for the permissions to access the directory or file. |
Note |
DSIO_ERR_LOAD_FILE_WRITE (-2406)
Description |
Failed to WRITE to a file when copying the file to edit a data set. |
Action |
Check whether the directory has enough space. |
Note |
DSIO_ERR_SAVE_FILE_OPEN (-2407)
Description |
Failed to OPEN the copy file for a modified data set. |
Action |
Check for the permissions to access the directory or file. |
Note |
DSIO_ERR_SAVE_FILE_READ (-2408)
Description |
Failed to READ the copy file for a modified data set. |
Action |
Check whether the record has been saved in the file. |
Note |
DSIO_ERR_WRONG_INIT_FLAGS (-2410)
Description |
The flag setting to call the DSIO library initialization function is incorrect. |
Action |
Check the input flag settings. |
Note |
DSIO_ERR_WRONG_DCB_CONCATS (-2501)
Description |
There is a problem with the concatenated DCB provided from allocator. |
Action |
Do not concatenate heterogeneous data set types. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_INVALID_DS_ACCESS (-2502)
Description |
A command that is non-supported for non-VSAM data sets was executed. |
Action |
Execute adequate commands only, in accordance with the data set types. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_INVALID_OPERATION (-2503)
Description |
An attempt was made to call a DSIO API that is not suitable for the data set type. |
Action |
Use an adequate DSIO API only, in accordance with the data set types. |
Note |
Refer to OpenFrame Data Set Guide. |
DSIO_ERR_OPT_NOT_SUPPORTED(-2504)
Description |
A non-supported option was used for the data set I/O. |
Action |
Check whether the option is supported. |
Note |
DSIO_ERR_INVALID_DCB_TYPE(-2506)
Description |
aAn invalid DCB TYPE has been configured. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_INVALID_CONN_TYPE(-2507)
Description |
An invalid CONNECTION TYPE has been specified. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_INVALID_RID_TYPE(-2508)
Description |
An invalid RID TYPE has been configured. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_INVALID_DCB_NAME(-2509)
Description |
An invalid DCB name has been configured. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_INVALID_MEMORY_POINTER(-2601)
Description |
Failed to allocate the DCB information within the library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSIO_ERR_ODBC(-2602)
Description |
An error occurred to the database I/O during the metadata processing for the data set. |
Action |
Contact TmaxSoft Technical Support with the ODBC error logs. |
Note |
DSIO_ERR_SYSTEM_LSTAT(-2901)
Description |
Failed to call the lstat() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
DSIO_ERR_SYSTEM_POPEN(-2902)
Description |
Failed to call the popen() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
DSIO_ERR_SYSTEM_FREAD(-2903)
Description |
Failed to call the fread() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
DSIO_ERR_SYSTEM_OPEN(-2904)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
DSIO_ERR_SYSTEM_WRITE(-2905)
Description |
Failed to call the write() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
DSIO_ERR_SYSTEM_READ(-2906)
Description |
Failed to call the read() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
DSIO_ERR_SYSTEM_CLOSE(-2907)
Description |
Failed to call the close() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the system error message displayed when the error occurs. |
5. ICF (-3000)
The ICF module provides integrated catalog functions. This section lists the error codes that can occur in the ICF module, descriptions of errors and suggested corrective actions.
ICF_ERR_DUPLICATE_RECORD (-3001)
Description |
A duplicate catalog entry exists. |
Action |
Check whether the entry to register has already been cataloged. |
Note |
Refer to "Chapter 4 Integrated Catalog" in OpenFrame Data Set Guide. |
ICF_ERR_NOT_FOUND (-3002)
Description |
The catalog entry to search for is not found. |
Action |
Check whether the entry to search for has been cataloged. |
Note |
Refer to "Chapter 4 Integrated Catalog" in OpenFrame Data Set Guide. |
ICF_ERR_END_OF_FILE (-3003)
Description |
The end of a file has been reached while browsing a catalog by using the ICF library API. |
Action |
Add logic to use when the application using the ICF library API reaches the end of the catalog. |
Note |
ICF_ERR_MEMORY_ALLOC (-3004)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
ICF_ERR_INTERNAL (-3005)
Description |
Internal error occurred in the ICF library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
ICF_ERR_NOT_IMPLEMENTED (-3006)
Description |
Internal error (Not Implemented) occurred in the ICF library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
ICF_ERR_TABLE_NOT_FOUND (-3007)
Description |
The catalog table for OpenFrame is not found. |
Action |
Connect to the database to check for the OFM_BASE_CATALOG table. If the table does not exist, create it with the baseinit program. |
Note |
ICF_ERR_INVALID_CATALOG_NAME (-3011)
Description |
An invalid catalog name has been passed as parameter when using the ICF library API directly. |
Action |
Check if the catalog name is correct when calling the ICF library API function. |
Note |
ICF_ERR_INALID_ENTRY_NAME (-3012)
Description |
An invalid entry name has been passed as parameter when using the ICF library API directly. |
Action |
Check if the entry name is correct when calling the ICF library API function. |
Note |
ICF_ERR_INVALID_ENTRY_TYPE (-3013)
Description |
An invalid entry type has been passed as parameter when using the ICF library API directly. |
Action |
Check if the entry type is correct when calling the ICF library API function. |
Note |
ICF_ERR_INVALID_ATTR_TYPE (-3014)
Description |
An invalid attribute has been retrieved or specified when using the ICF library API directly. |
Action |
Modify the application using the ICF library API, to retrieve or specify only attributes that are compatible with the entry types. |
Note |
ICF_ERR_INVALID_HANDLE (-3015)
Description |
An invalid handle has been passed as parameter when using the ICF library API directly. |
Action |
Check if the handle is correct when calling the ICF library API function. |
Note |
ICF_ERR_INVALID_FILTER_KEY (-3016)
Description |
An invalid data set filter key has been assigned during a catalog search. |
Action |
Check whether the wild card provided for the catalog search has been used correctly. |
Note |
Refer to the "Chapter 4 Integrated Catalog" in OpenFrame Data Set Guide. |
ICF_ERR_ICF_CONFIGURATION (-3021)
Description |
A problem occurred to the default configuration file for the integrated catalog. |
Action |
Check the information set in the ICF_CATALOG section of the ds subject, under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
ICF_ERR_NOT_INITIALIZED (-3024)
Description |
The ICF library API is used directly without calling the initialization function. |
Action |
Modify the source code to call the initialization function before calling the ICF library API. |
Note |
ICF_ERR_SCAN_NOT_STARTED (-3027)
Description |
SCAN has not been started. An ICF library internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
ICF_ERR_MAX_ASSOCIATONS (-3028)
Description |
The number of entries associated with one catalog exceeds the maximum allowable count, when using the ICF library API directly. |
Action |
Modify the application so that the number of entries associated with one catalog does not exceed the maximum allowable count. |
Note |
The maximum allowable entry count for one catalog is 477. |
ICF_ERR_BUFFER_OVERFLOW (-3029)
Description |
The number of buffers given to a search catalog is smaller than the number of entries that have actually been searched. |
Action |
The buffer size for the result of catalog search must be correctly calculated before search. |
Note |
ICF_ERR_CATALOG_NOT_DEFINED (-3031)
Description |
The BCS data set with the given catalog name is not found. |
Action |
Check whether the specified user catalog has been defined in the master catalog. |
Note |
ICF_ERR_VOLUME_NOT_DEFINED (-3032)
Description |
The VVDS data set corresponding to the volume specified is not found. |
Action |
Check whether the specified volume of VVDS data set has been defined in the master catalog. |
Note |
ICF_ERR_SCAN_STARTED_ALREADY (-3035)
Description |
SCAN has been already started. An ICF library internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
ICF_ERR_NO_ALIAS_CATALOG (-3036)
Description |
The Alias Catalog corresponding to the data set is not found. |
Action |
Contact TmaxSoft Technical Support. |
Note |
ICF_ERR_ODBC (-3101)
Description |
Failed to call an ODBC API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
ICF_ERR_FAIL_OVER_RECONNECTED (-3102)
Description |
The DBMS server connected from the ICF library has been shut down, but a new connection is established on the server instance with the same DNS name. |
Action |
Contact the DBMS server administrator, even through this situation is intended rather than an error. |
Note |
6. AMS (-4000)
The AMS module is responsible for creating, deleting, and cataloging a data set. This section lists error codes that can occur in the AMS module, descriptions of errors and suggested corrective actions.
AMS_ERR_DUPLICATE_RECORD (-4001)
Description |
A duplicate record with the same key value already exists in the catalog. |
Action |
Check whether there is a record with an identical name and change the name of the record to be registered if needed. |
Note |
AMS_ERR_NOT_FOUND (-4002)
Description |
The catalog entry to search for is not found. |
Action |
Check whether the entry has been cataloged and then correct its name. |
Note |
AMS_ERR_MEMORY_ALLOC (-4003)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
AMS_ERR_INTERNAL (-4004)
Description |
An internal error occurred in the AMS library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMS_ERR_NOT_IMPLEMENTED (-4005)
Description |
An internal error (Not Implemented) occurred in the AMS library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMS_ERR_INVALID_CATALOG_NAME (-4011)
Description |
The catalog name passed as parameter is invalid. |
Action |
Ensure the catalog name is correct when running the application. |
Note |
AMS_ERR_INVALID_ENTRY_NAME (-4012)
Description |
The entry name passed as parameter is invalid. |
Action |
Ensure the entry name is correct when running the application. |
Note |
AMS_ERR_INVALID_ENTRY_TYPE (-4013)
Description |
The entry type passed as parameter is invalid. |
Action |
Ensure the entry type is correct when running the application. |
Note |
AMS_ERR_INVALID_DATASET_NAME (-4014)
Description |
The data set name passed as parameter is invalid. |
Action |
Ensure the data set name is correct when running the application. |
Note |
AMS_ERR_INVALID_MEMBER_NAME (-4015)
Description |
The member name passed as parameter is invalid. |
Action |
Ensure the member name is correct when running the application. |
Note |
AMS_ERR_INVALID_VOLUME_SERIAL (-4016)
Description |
The volume serial number passed as parameter is invalid. |
Action |
Ensure the volume serial number is correct when running the application. |
Note |
AMS_ERR_INVALID_GDS_ATTRIBUTE (-4017)
Description |
The GDS attribute passed as parameter is invalid. |
Action |
Ensure the GDS attribute is correct when running the application. |
Note |
AMS_ERR_INVALID_BASE_CLUSTER (-4018)
Description |
The data set type given as base cluster is invalid. |
Action |
Specify the name of an appropriate data set as base cluster. |
Note |
AMS_ERR_INVALID_DCB_TYPE (-4019)
Description |
The data set type is invalid for running the job. |
Action |
Specify an appropriate data set type for the job. |
Note |
AMS_ERR_INVALID_REQUEST (-4020)
Description |
An invalid parameter has been specified for running the job. |
Action |
Specify an appropriate parameter for the job. |
Note |
AMS_ERR_TSAM_CONFIGURATION (-4021)
Description |
There is a problem in the configuration for accessing the VSAM data set server used in the AMS library. |
Action |
Check whether the required items are correctly set in the [TSAM_CLIENT] or [SYS1_CLIENT] section of the dbconn.conf file. |
Note |
For information about configuration, refer to "Appendix B. System Configuration" in OpenFrame Base Guide. |
AMS_ERR_NOT_INITIALIZED (-4023)
Description |
The AMS library API is used directly without calling the initialization function. |
Action |
Modify the source code to call the initialization function first before calling the AMS library API. |
Note |
AMS_ERR_TOO_MANY_ENTRIES (-4024)
Description |
Multiple entries with the same name are found in the catalog while searching for information about a specific catalog entry. |
Action |
Specify correctly the name of the entry to search for when running the application. |
Note |
AMS_ERR_GDG_NOT_REGSTERED (-4025)
Description |
The GDG entry is not found when searching for or registering a GDS data set. |
Action |
Register the GDG entry for the GDS data set. |
Note |
AMS_ERR_NO_PREVIOUS_GDS (-4026)
Description |
The previous generation of the GDS data set is not found when searching for or registering a GDS data set. |
Action |
Respecify the generation number of the GDS data set to search for, or register the previous generation of GDS data set. |
Note |
AMS_ERR_BASE_ENTRY_NOT_FOUND (-4027)
Description |
The base catalog entry needed to register the AIX, PATH, or ALIAS catalog entry is not found. |
Action |
Specify correctly the name of the base entry or define the base catalog entry first. |
Note |
AMS_ERR_PDS_NOT_REGISTERED (-4028)
Description |
The PDS itself is not found when adding or deleting a PDS member. |
Action |
Check whether the name of the PDS data set is well-defined, or define the PDS data set. |
Note |
AMS_ERR_PDS_MEMBER_LIST (-4029)
Description |
A problem occurred when searching for the member list of a PDS data set. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_ENTRY_NOT_RENAMED (-4030)
Description |
Failed to rename a catalog entry. |
Action |
If there is a catalog entry associated with a non-VSAM data set, its name cannot be changed. |
Note |
AMS_ERR_GDS_ASSOC_FOUND (-4031)
Description |
Unable to delete a GDG catalog entry because there is a GDS data set associated with the GDG. |
Action |
Delete the associated GDS data set before deleting the GDG catalog entry, or use the FORCE option to forcefully delete the entry. |
Note |
AMS_ERR_ENTRY_NOT_SUPPORTED (-4032)
Description |
An invalid entry type has been specified for the job to perform. |
Action |
Specify a valid entry type for the job. |
Note |
AMS_ERR_NOPURGE_NOT_EXPIRED (-4033)
Description |
Unable to delete an unexpired data set by using the IDCAMS utility. |
Action |
Specify the PURGE option when using IDCAMS DELETE. |
Note |
For more information about the IDCAMS utility, refer to OpenFrame Utility Reference Guide. |
AMS_ERR_INVALID_DATA_NAME (-4101)
Description |
An invalid data component name has been specified for the job to perform. |
Action |
Specify a valid data component name to perform the job. |
Note |
AMS_ERR_INVALID_INDEX_NAME (-4102)
Description |
An invalid index name has been specified for the job to perform. |
Action |
Specify a valid index name for the job to perform. |
Note |
AMS_ERR_LOG_FILE_OPEN (-4801)
Description |
A problem occurred while opening a log file to write logs. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_LOG_FILE_CLOSE (-4802)
Description |
A problem occurred while closing a log file after writing logs. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_LOG_FILE_WRLCK (-4803)
Description |
A problem occurred while locking a log file to write logs. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_LOG_FILE_UNLCK (-4804)
Description |
A problem occurred while unlocking a log file after writing logs. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_LOG_FILE_LSEEK (-4805)
Description |
A problem occurred while finding the location to write a record in a log file. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_LOG_FILE_WRITE (-4806)
Description |
A problem occurred while writing a record by using the the write() function in a log file. |
Action |
Contact TmaxSoft Technical Support (Refer to the displayed error message). |
Note |
AMS_ERR_SYSTEM_CREAT (-4901)
Description |
Failed to call the creat() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
AMS_ERR_SYSTEM_UNLINK (-4902)
Description |
Failed to call the unlink() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
AMS_ERR_SYSTEM_OPEN (-4903)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
AMS_ERR_SYSTEM_UTIME (-4904)
Description |
Failed to call the utime() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
AMS_ERR_SYSTEM_RENAME (-4905)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
7. DSALC (-5000)
The DSALC module is responsible for allocation within data sets. This section lists the error codes that can occur in the DSALC module, descriptions of errors and suggested corrective actions.
DSALC_ERR_INVALID_REQUEST (-5001)
Description |
An invalid parameter has been passed for the job to perform. |
Action |
Specify a valid parameter for the job. |
Note |
DSALC_ERR_MEMORY_ALLOC (-5002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
DSALC_ERR_NOT_INITIALIZED (-5003)
Description |
The allocator library function is used without calling the initialization function. |
Action |
Call the initialization function before using the allocator library function. |
Note |
DSALC_ERR_INTERNAL (-5004)
Description |
An internal error occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_BUFFER_OVERFLOW (-5005)
Description |
The buffer size provided for the allocator report function is insufficient. |
Action |
Modify the application to call the report function after calculating the buffer size. |
Note |
DSALC_ERR_NOT_IMPLEMENTED (-5009)
Description |
An internal error (Not Implemented) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_SHMKEY (-5102)
Description |
The key value for the shared memory is invalid. |
Action |
Check the VALUE of the DATASET_SHMKEY key in the DATASET_RESOURCE section, from the ds subject under OpenFrame Configuration. |
Note |
For more information about the ds subject, refer to OpenFrame Configuration Guide. |
DSALC_ERR_SHMGET_FAILURE (-5105)
Description |
The shared memory corresponding to the specified key value is not accessible. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SHMAT_FAILURE (-5106)
Description |
Failed to attach the process to the shared memory for the specified key. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SHMDT_FAILURE (-5107)
Description |
Failed to detach the process from the shared memory for the specified key. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SHMCTL_STAT (-5108)
Description |
Unable to find the status information of the shared memory for the specified key. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SHMCTL_RMID (-5109)
Description |
Unable to delete the shared memory for the specified key. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SHMDS_SEGSZ (-5110)
Description |
The size of the shared memory for the specified key deviates from the expectation. |
Action |
If the allocator library is patched, remove the existing shared memory and restart. |
Note |
Refer to the ipcs and ipcrm parts in the Unix manual. |
DSALC_ERR_DD_UNALLOCATE (-5111)
Description |
An internal error (DD Unallocate error) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_DDNAME (-5201)
Description |
An invalid DD name has been specified. |
Action |
Check whether the DD name has been correctly specified and retry. |
Note |
DSALC_ERR_INVALID_DSNAME (-5202)
Description |
An invalid data set name has been specified. |
Action |
Check whether the data set name has been correctly specified and retry. |
Note |
DSALC_ERR_INVALID_HANDLE (-5203)
Description |
An allocator usage error (Invalid Handle) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_HEADER (-5204)
Description |
An allocator usage error (Invalid Header) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_DUPLICATE_HEADER (-5205)
Description |
An allocator usage error (Duplicate Header) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_CONCAT (-5206)
Description |
An allocator usage error (Invalid Concat) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_COUNT (-5207)
Description |
An allocator usage error (Invalid Count) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_REPORT (-5208)
Description |
An allocator usage error (Invalid Report) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_ALREADY_CATALOGED (-5211)
Description |
The new data set has been already cataloged. |
Action |
Delete the data set, depending on the situation, and retry. |
Note |
DSALC_ERR_DATASET_NOT_FOUND (-5212)
Description |
The existing data set is not found. |
Action |
Create a new data set, depending on the situation, and retry. |
Note |
DSALC_ERR_DATASET_DUPLICATE (-5213)
Description |
The new data set already exists. |
Action |
Delete the data set, depending on the situation, and retry. |
Note |
DSALC_ERR_UNSUPPORTED_ENTRY (-5221)
Description |
An entry registered in the catalog cannot be allocated. |
Action |
Use a catalog search to check whether another entry has been registered with the same name. |
Note |
DSALC_ERR_CONCATENATE_ENTRY (-5222)
Description |
An entry registered in the catalog cannot be concatenated. |
Action |
Concatenate only concatenatable entries. |
Note |
VSAM data set concatenation is not supported. |
DSALC_ERR_INVALID_SLOT_INFO (-5231)
Description |
An internal error (Invalid Slot Info) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_NO_AVAILABLE_SLOT (-5232)
Description |
There are no more available memory slots for an allocator. |
Action |
Use the allocator slot dump tool to check the status of the memory slot that is currently in use. |
Note |
The maximum number of available memory slots for the allocator is 65535. Check the VALUE of the DSALC_SLOT_COUNT key, in the DATASET_DEFAULT section of the ds subject under OpenFrame Configuration. For more information about the ds subject, refer to OpenFrame Configuration Guide. |
DSALC_ERR_OUTPUT_CONCATENATE (-5241)
Description |
An attempt was made to concatenate an output data set. Concatenation is not supported for output data sets. |
Action |
Do not try to concatenate output data sets. |
Note |
Refer to "Chapter 2. Non-VSAM Data Sets" in OpenFrame Data Set Guide. |
DSALC_ERR_VOLUME_ALLOC_DISP (-5242)
Description |
The DISP parameter has been incorrectly passed. |
Action |
Correct the DISP parameter and retry. |
Note |
When allocating the volume, use DISP=(SHR,KEEP,KEEP) or DISP=(OLD,KEEP,KEEP). |
DSALC_ERR_ABNORMAL_DISP_PASS (-5243)
Description |
The DISP parameter has been incorrectly passed. |
Action |
Correct the DISP parameter and retry. |
Note |
"PASS" cannot be used as an Abnormal Termination DISP parameter. |
DSALC_ERR_CONCAT_DISP_PASS (-5244)
Description |
The DISP parameter has been incorrectly passed. |
Action |
Correct the DISP parameter and retry. |
Note |
A concatenated data set cannot use 'PASS' as a DISP parameter. |
DSALC_ERR_PATH_ASSOC_INFO (-5245)
Description |
Unable to allocate a VSAM PATH because the PATH-related information in the catalog is invalid. |
Action |
Check the catalog to determine whether the PATH-related information has been correctly specified and make corrections to the catalog. |
Note |
Refer to "Chapter 3. VSAM Data Sets" in OpenFrame Data Set Guide. |
DSALC_ERR_AIX_ASSOC_INFO (-5246)
Description |
Unable to allocate a VSAM PATH because the AIX-related information in the catalog is invalid. |
Action |
Check the catalog to determine whether the AIX-related information has been correctly specified and make corrections to the catalog. |
Note |
Refer to "Chapter 3. VSAM Data Sets" in OpenFrame Data Set Guide. |
DSALC_ERR_UNIT_VOLUME_MISMATCH (-5247)
Description |
The UNIT and VOLUME parameters do not match each other when allocating a data set. |
Action |
Pass the parameters correctly after checking the UNIT and VOLUME information set in the system. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
DSALC_ERR_UNIT_NOT_GIVEN (-5248)
Description |
The required UNIT parameter has not been specified when allocating a data set. |
Action |
If DS_OLDSHR_UNIT_METHOD=NEW, in the DATASET_DEFAULT section of the ds subject under OpenFrame Configuration, then set DISP=OLD. If DISP=SHR, specify VOLUME and then ensure all UNITs are specified. |
Note |
For more information about the ds subject, refer to OpenFrame Configuration Guide. |
DSALC_ERR_MODEL_NOT_FOUND (-5251)
Description |
The model data set specified to set attributes of a data set is not found. |
Action |
Check whether the model data set specified in JCL exists. |
Note |
DSALC_ERR_VSAM_TERM_DISP (-5252)
Description |
The DISP parameter for a VSAM data set is not supported. |
Action |
Specify a DISP parameter supported by the VSAM data set in JCL. |
Note |
Refer to "Chapter 3. VSAM Data Sets" in OpenFrame Data Set Guide. |
DSALC_ERR_UNKNOWN_DCB_TYPE (-5253)
Description |
An internal error (Unknown DCB Type) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_DCB_NAME (-5254)
Description |
An internal error (Invalid DCB Name) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_CATNAME_DIFFERENT (-5255)
Description |
An internal error (Catname Different) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_ENTTYPE_DIFFERENT (-5256)
Description |
An internal error (Enttype Different) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_RECAT_NOT_ALLOWED (-5257)
Description |
Recataloging is not supported when closing the data set. |
Action |
Check the data set type, and then specify a compatible DISP parameter for the JCL where the problem occurred. |
Note |
Recataloging is not supported for GDS data sets or PDS members. |
DSALC_ERR_REMOVE_DATASET (-5258)
Description |
An allocator usage error (Remove Dataset) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_UPDATE_VTOC_ELEMENT (-5260)
Description |
An allocator usage error (Update VTOC Element) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOCK_INITIALIZE (-5261)
Description |
An allocator usage error (Lock Initialize) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_ALLOC_TYPE (-5262)
Description |
An allocator usage error (Invalid Alloc Type) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_REFDD_FORMAT (-5271)
Description |
The JCL reference DD format is invalid. |
Action |
Check the format of the REFDD parameter. |
Note |
DSALC_ERR_STEPPATH_REQUIRED (-5272)
Description |
An allocator usage error (Steppath Required) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_REFDD_NOT_FOUND (-5273)
Description |
The reference DD is not found in JCL. |
Action |
Check the REFDD parameter has been correctly set. |
Note |
DSALC_ERR_RENEW_GDS_DATASET (-5295)
Description |
The RENEW DISP parameter is not allowed for GDS data sets. |
Action |
Check whether the DISP parameter has been correctly specified. |
Note |
DSALC_ERR_RENEW_WITH_MEMBER (-5296)
Description |
The RENEW DISP parameter is not allowed for a member of a PDS data set. |
Action |
Check whether the DISP parameter has been correctly specified. |
Note |
DSALC_ERR_NO_EXPLICIT_VOLSER (-5297)
Description |
Unable to explicitly specify the volume when allocating a data set. |
Action |
Check whether the volume serial or unit information is clearly described. |
Note |
DSALC_ERR_INVALID_PARM_DSNTYPE (-5301)
Description |
The DSNTYPE parameter specified during allocation is invalid. |
Action |
Specify a valid DSNTYPE parameter. |
Note |
DSALC_ERR_INVALID_PARM_DSORG (-5302)
Description |
The DSORG parameter specified during allocation is invalid. |
Action |
Specify a valid DSORG parameter. |
Note |
DSALC_ERR_INVALID_PARM_RECFM (-5303)
Description |
The RECFM parameter specified during allocation is invalid. |
Action |
Specify a valid RECFM parameter. |
Note |
DSALC_ERR_INVALID_PARM_BLKSIZE (-5304)
Description |
The BLKSIZE parameter specified during allocation is invalid. |
Action |
Specify a valid BLKSIZE parameter. |
Note |
DSALC_ERR_INVALID_PARM_LRECL (-5305)
Description |
The LRECL parameter specified during allocation is invalid. |
Action |
Specify a valid LRECL parameter. |
Note |
DSALC_ERR_INVALID_PARM_EXPDT (-5306)
Description |
The EXPDT parameter specified during allocation is invalid. |
Action |
Specify a valid EXPDT parameter. |
Note |
DSALC_ERR_INVALID_PARM_RETPD (-5307)
Description |
The RETPD parameter specified during allocation is invalid. |
Action |
Specify a valid RETPD parameter. |
Note |
DSALC_ERR_INVALID_PARM_RECORG (-5311)
Description |
The RECORG parameter specified during allocation is invalid. |
Action |
Specify a valid RECORG parameter. |
Note |
DSALC_ERR_INVALID_PARM_KEYLEN (-5312)
Description |
The KEYLEN parameter specified during allocation is invalid. |
Action |
Specify a valid KEYLEN parameter. |
Note |
DSALC_ERR_INVALID_PARM_KEYOFF (-5313)
Description |
The KEYOFF parameter specified during allocation is invalid. |
Action |
Specify a valid KEYOFF parameter. |
Note |
DSALC_ERR_INVALID_PARM_RLSMODE (-5314)
Description |
The RLSMODE parameter specified during allocation is invalid. |
Action |
Specify a valid RLSMODE parameter. |
Note |
DSALC_ERR_CONCAT_LEADER_PASS (-5401)
Description |
A data set allocated with a disposition of PASS cannot be a concatenation leader. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_SWITCH_CONCAT_SLOT (-5402)
Description |
A concatenated data set is not allowed to have its attributes changed in the next step. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_SWITCH_NODISP_SLOT (-5403)
Description |
A spool data set is not allowed to have its attributes changed in the next step. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_DUMMY_SWITCH_DSNAME (-5411)
Description |
A dummy data set is not allowed to have the DSNAME attribute changed in the next step. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_DUMMY_SWITCH_VOLSER (-5412)
Description |
A dummy data set is not allowed to have the VOLSER attribute changed in the next step. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_VOLUME_SWITCH_DSNAME (-5421)
Description |
A volume data set is not allowed to have the DSNAME attribute changed in the next step. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_VOLUME_SWITCH_VOLSER (-5422)
Description |
A volume data set is not allowed to have the VOLSER attribute changed in the next step. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_VOLUME_SWITCH_DISP (-5431)
Description |
An invalid disposition has been specified when changing an attribute in the next JCL step of the volume data set. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_NOTAPE_SWITCH_DSNAME (-5441)
Description |
Changing the DSNAME attribute is not allowed in the next step for any other data sets than tape data sets. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_NOTAPE_SWITCH_VOLSER (-5442)
Description |
Changing the VOLSER attribute is not allowed in the next step for any other data sets than tape data sets. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_NONPDS_SWITCH_MEMBER (-5443)
Description |
Changing the MEMBER attribute is not allowed in the next step for any other data sets than PDS data sets. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_CATLDS_SWITCH_DSNAME (-5444)
Description |
A cataloged data set is not allowed to have the DSNAME attribute changed in the next step. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_CATLDS_SWITCH_VOLSER (-5445)
Description |
A cataloged data set is not allowed to have the VOLSER attribute changed in the next step. |
Action |
Check the DD statement in JCL. |
Note |
DSALC_ERR_SPOOL_ALLOC_DISP (-5501)
Description |
The DISP parameter value for a spool data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_DBIO_ALLOC_DISP (-5511)
Description |
The DISP parameter value for a DBIO data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_NEED_VOLSER_LIST (-5512)
Description |
The volume serial list is required to allocate a DBIO data set. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_TERM_ID (-5521)
Description |
The Terminal ID value for a terminal data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_TERM_ALLOC_DISP (-5522)
Description |
The DISP parameter value for a terminal data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_STRNAME (-5531)
Description |
The stream name for a STDIO data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_STDIO_ALLOC_DISP (-5532)
Description |
The DISP parameter value for a STDIO data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_MQNNAME (-5541)
Description |
The MQN node name for a MQNIO data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_MQNIO_ALLOC_DISP (-5542)
Description |
The DISP parameter value for a MQNIO data set is incorrect. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_DYNINFO_IO_FAILURE (-5551)
Description |
A problem occurred while using a file by dynamically allocating a data set. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_RDB_INVALID_ALLOC_INFO (-5601)
Description |
An invalid information has been entered when allocating a data set. |
Action |
This is an internal error code for library operation. |
Note |
DSALC_ERR_ALREADY_IN_CRITICAL (-5901)
Description |
An internal error (Already In Critical) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_NOT_IN_CRITICAL (-5902)
Description |
An internal error (Not In Critical) occurred in the allocator library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOG_FILE_OPEN (-5903)
Description |
Failed to open a data set allocator log file. |
Action |
Check for access rights for data set allocator log files or directories. |
Note |
DSALC_ERR_LOG_FILE_WRITE (-5904)
Description |
Failed to write to a data set allocator log file. |
Action |
Check for access rights for data set allocator log files or directories. |
Note |
DSALC_ERR_LOG_OPEN_ALREADY (-5905)
Description |
An allocator library usage error (Log Open Already) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOG_NOT_OPEN_YET (-5906)
Description |
An allocator library usage error (Log Not Open Yet) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOG_FILE_WRLCK (-5907)
Description |
An allocator library usage error (Log File Wrlck) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOG_FILE_UNLCK (-5908)
Description |
An allocator library usage error (Log File Unlck) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_INVALID_LOG_FD (-5909)
Description |
An allocator library usage error (Invalid Log FD) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOG_FILE_CLOSE (-5910)
Description |
An allocator library usage error (Log File Close) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_LOG_FILE_LSEEK (-5911)
Description |
An allocator library usage error (Log File LSEEK) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSALC_ERR_SYSTEM_LSTAT (-5991)
Description |
Failed to call the lstat() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_OPENDIR (-5992)
Description |
Failed to call the opendir() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_MKDIR (-5993)
Description |
Failed to call the mkdir() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_RMDIR (-5994)
Description |
Failed to call the rmdir() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_FOPEN (-5995)
Description |
Failed to call the fopen() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_OPEN (-5996)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_UNLINK (-5997)
Description |
Failed to call the unlink() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_SIGNAL(-5998)
Description |
Failed to call the signal() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
DSALC_ERR_SYSTEM_POPEN (-5999)
Description |
Failed to call the popen() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
8. VOLM (-6000)
The VOLM module is responsible for volume information inquiries and VTOC management. This section lists the error codes that can occur in the VOLM module, descriptions of errors and suggested corrective actions.
VOLM_ERR_INVALID_REQUEST (-6001)
Description |
An invalid parameter has been passed when using the VOLM library API directly. |
Action |
Pass a correct parameter for the job to perform when using the API directly. Otherwise, contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_MEMORY_ALLOC (-6002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
VOLM_ERR_BUFFER_OVERFLOW (-6003)
Description |
Insufficient buffer space is allocated for calling a data inquiry function. |
Action |
Allocate sufficient buffer space. |
Note |
VOLM_ERR_ELEMENT_NOT_FOUND (-6004)
Description |
The VTOC information of a data set is not found. |
Action |
Check whether the data set exists on the volume. |
Note |
VOLM_ERR_NOT_IMPLEMENTED (-6009)
Description |
An internal error (Not Implemented) occurred in the VOLM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_NOT_INITIALIZED (-6010)
Description |
An internal error (Not Initialized) occurred in the VOLM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_TABLE_NOT_FOUND (-6011)
Description |
The OFM_BASE_VTOC table is not found in the OpenFrame system database. |
Action |
Check if the OFM_BASE_VTOC table has been created. If necessary, use the baseinit program to recreate the system table. |
Note |
VOLM_ERR_ALREADY_EXIST_TABLE (-6012)
Description |
An attempt was made to recreate the OFM_BASE_VTOC table when it already exists in the OpenFrame system database. |
Action |
Check if the OFM_BASE_VTOC table has been created. If necessary, use the baseinit program to recreate the system table. |
Note |
VOLM_ERR_DUPLICATE_RECORD (-6013)
Description |
A duplicate volume with the same serial already exists in the system. |
Action |
Create another volume with a unique serial. |
Note |
VOLM_ERR_TABLESPACE_NOT_DEFINED (-6014)
Description |
The tablespace does not exist in the system database. |
Action |
Create a tablespace with the same name as that of the volume to create in the database. |
Note |
VOLM_ERR_GROUP_NOT_DEFINED (-6101)
Description |
The specified esoteric unit name has not been registered in the system. |
Action |
Run the list device command of volmgr or OFManager to check if the name actually exists, and if not, register the name. |
Note |
VOLM_ERR_GROUP_CONFIGURATION (-6102)
Description |
The esoteric information set in the system is not valid. |
Action |
Run the list device command of volmgr to identify the problem and correct it. |
Note |
VOLM_ERR_DEVICE_CONFIGURATION (-6103)
Description |
The device information set in the system is not valid. |
Action |
Run the list device command of volmgr to identify the problem and correct it. |
Note |
VOLM_ERR_UNKNOWN_DEVICE_TYPE (-6104)
Description |
The device type passed as parameter is an unknown type in the system. |
Action |
Check whether the device type to pass has been correctly specified. If the error persists even though the device type has been correctly specified, contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_DEVICE_NOT_DEFINED (-6105)
Description |
The device number used in JCL has not been defined in the system. |
Action |
Check whether the device number to pass has been correctly specified. If necessary, use volmgr to redefine the device number. |
Note |
VOLM_ERR_TAPE_DEVICE_NOT_SUPPORTED (-6106)
Description |
A tape type device is used. |
Action |
Change the device type. |
Note |
Starting from OpenFrame 7.1, tape type devices are not supported. |
VOLM_ERR_NO_DEFAULT_VOLSER (-6201)
Description |
The default volume serial number has not been registered in the system. |
Action |
Register the default volume serial number to the DEFAULT_VOLSER key, in the DATASET_DEFAULT section of the ds subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
VOLM_ERR_DEF_VOLSER_CONFIG (-6202)
Description |
The default volume serial number has been incorrectly set. |
Action |
Correct the incorrect number set to the DEFAULT_VOLSER key, in the DATASET_DEFAULT section of the ds subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
VOLM_ERR_VOLUME_CONFIGURATION (-6203)
Description |
The volume information set in the system is incorrect. |
Action |
Run the volmgr list command to find and correct the information. |
Note |
VOLM_ERR_VOLUME_NOT_DEFINED (-6204)
Description |
The volume serial number used in JCL has not been defined in the system. |
Action |
Run volmgr to define the volume. |
Note |
VOLM_ERR_VOLUME_IS_NOT_EMPTY (-6205)
Description |
A data set already exists in the volume. |
Action |
Delete the data set from the volume. |
Note |
VOLM_ERR_NO_PRIMARY_VOLUME (-6301)
Description |
There is no primary volume serial number corresponding to the specified device name. |
Action |
Register one or more volume serial number for the device. |
Note |
VOLM_ERR_NO_AMPLE_VOLUME (-6302)
Description |
Unable to find any volume with sufficient disk space, from the volume serial numbers list. |
Action |
Enlarge the disk space linked to each volume serial number or register a new volume serial number. |
Note |
VOLM_ERR_VOLUME_NOT_FOUND (-6303)
Description |
The specified volume information is not found. |
Action |
Check whether the specified volume actually exists in the system. |
Note |
VOLM_ERR_MAX_DEVICE_NUMBER (-6304)
Description |
The maximum allowable device number that can be defined in OpenFrame is exceeded. |
Action |
Define only the necessary number of devices. |
Note |
Up to 1,024 devices can be defined currently in OpenFrame. |
VOLM_ERR_INVALID_FILTER_KEY (-6401)
Description |
An invalid filter key is used. |
Action |
Check the validity of the filter key. |
Note |
VOLM_ERR_VTOC_OPEN_ALREADY (-6501)
Description |
An internal error (VTOC Open Already) occurred in the VOLM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_VTOC_NOT_OPEN_YET (-6502)
Description |
An internal error (VTOC Not Open Yet) occurred in the VOLM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_VTOC_OPEN_MODE (-6503)
Description |
An internal error (VTOC Open Mode) occurred in the VOLM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_INVALID_VTOC_FD (-6504)
Description |
An internal error (Invalid VTOC FD) occurred in the VOLM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_VTOC_CORRUPTED (-6505)
Description |
The VTOC table has been corrupted. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_VTOC_IO_FAILURE (-6506)
Description |
An error occurred during I/O of the VTOC information. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_TPOS_FILE_NOT_FOUND (-6507)
Description |
The file containing the information about the tape device’s location is not found. |
Action |
Contact TmaxSoft Technical Support. |
Note |
VOLM_ERR_ODBC (-6601)
Description |
Failed to call the ODBC-related API function. |
Action |
Check SQLSTATE and the native error message. |
Note |
VOLM_ERR_FAIL_OVER_RECONNECTED (-6602)
Description |
The DBMS server connection within the VOLM library has been ended, but another connection is made to the server instance with the same DNS name. |
Action |
Contact the DBMS server administrator, even through this situation is intended rather than an error. |
Note |
VOLM_ERR_SYSTEM_LSTAT (-6901)
Description |
Failed to call the lstat() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_CREAT (-6902)
Description |
Failed to call the creat() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_UNLINK (-6903)
Description |
Failed to call the unlink() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_OPEN (-6904)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_FCNTL (-6905)
Description |
Failed to call the fcntl() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_CLOSE (-6906)
Description |
Failed to call the close() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_READ (-6907)
Description |
Failed to call the read() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_WRITE (-6908)
Description |
Failed to call the write() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_LSEEK (-6909)
Description |
Failed to call the lseek() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
VOLM_ERR_SYSTEM_OPENDIR (-6910)
Description |
Failed to call the opendir() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
9. LOCKM (-7000)
The LOCKM module is a Lock server client module. This section lists the error codes that can occur in the LOCKM module, descriptions of errors and suggested corrective actions.
LOCKM_ERR_INTERRUPTED (-7007)
Description |
A job waiting for a lock is stopped with the STOP command or forcefully terminated. |
Action |
Check the status of the job waiting for a lock. |
Note |
LOCKM_ERR_INVALID_REQUEST (-7011)
Description |
An invalid parameter is used to call a function or Tmax service. |
Action |
Restart the ofrlmsvr and ofrlmwrk servers, or check if the node name has been correctly specified. |
Note |
LOCKM_ERR_INTERNAL_ERROR (-7013)
Description |
An internal error occurred during the library operation. |
Action |
Contact TmaxSoft Technical Support with the error logs. |
Note |
LOCKM_ERR_GET_LIST_IS_NULL (-7023)
Description |
The lock list is empty. |
Action |
If determined as an faulty operation, contact TmaxSoft Technical Support with the error logs. |
Note |
LOCKM_ERR_NODENAME_LENGTH_FAILURE (-7024)
Description |
The node name exceeds 64 bytes. |
Action |
Adjust the length of the node name not to exceed 64 bytes. |
Note |
LOCKM_ERR_LOCK_WAIT_TIMEOUT (-7030)
Description |
A timeout occurred while waiting for a lock. |
Action |
Increase the timeout period or modify the job settings not to allow concurrent access to an already locked data set. |
Note |
LOCKM_ERR_ALREADY_LOCKED (-7032)
Description |
The process for which a lock request has been made is already locked by another application. |
Action |
Identify the application that made the lock request for the data set through tjesmgr or OpenFrame Manager, and forcefully release the lock if necessary. |
Note |
LOCKM_ERR_MEMORY_ALLOC (-7041)
Description |
Failed to allocate system memory. |
Action |
Check if the system has sufficient available memory. |
Note |
LOCKM_ERR_NOTHING_CLEARED (-7101)
Description |
Unable to remove the lock list because the list does not exist. |
Action |
If determined as an faulty operation, contact TmaxSoft Technical Support with the error logs. |
Note |
LOCKM_ERR_LOCKMCLI_TPCALL_FAIL (-7200)
Description |
Failed to call the tpcall() function for LHSVR in the library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_LOCKMCLI_TPGETRPLY_FAIL (-7202)
Description |
Failed to call the tpgetrply() function for LHSVR in the library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_ALLOC_HANDLE_ERROR (-7301)
Description |
Failed to obtain the ODBC handle by calling the SQLAllocHandle() function. |
Action |
Check the ODBC driver settings for the DBMS, or contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_SET_ENV_ERROR (-7302)
Description |
Failed to configure ODBC by calling the SQLSetEnvAttr() function. |
Action |
Check the ODBC driver settings for the DBMS, or contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_CONNECT_ERROR (-7303)
Description |
Failed to connect to ODBC by calling the SQLConnect() function. |
Action |
Check the ODBC driver settings for the DBMS, or contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_SET_CONNECT_ERROR (-7304)
Description |
Failed to configure the ODBC connection by calling the SQLSetConnectAttr() function. |
Action |
Check the ODBC driver settings for the DBMS, or contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_BIND_PARAMETER_ERROR (-7305)
Description |
Failed to bind SQL parameters by calling the SQLBindParameter() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_EXEC_DIRECT_ERROR (-7306)
Description |
Failed to execute an SQL statement by calling the SQLExecDirect() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_DISCONNECT_ERROR (-7307)
Description |
Failed to end the ODBC connection by calling the SQLDisconnect() function. |
Action |
Check the DBMS connection status or contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_FREE_HANDLE_ERROR (-7308)
Description |
Failed to free the ODBC handle by calling the SQLFreeHandle() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_PREPARE_ERROR (-7309)
Description |
Failed to prepare an SQL statement by calling the SQLPrepare() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_BIND_COL_ERROR (-7310)
Description |
Failed to allocate a variable for the record to fetch by calling the SQLBindCol() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_EXECUTE_ERROR (-7311)
Description |
Failed to execute a prepared SQL statement by calling the SQLExecute() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_SQL_FETCH_ERROR (-7312)
Description |
Failed to fetch a record by calling the SQLFetch() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_INVALID_LOCK_TYPE_ERROR (-7313)
Description |
The requested lock type is invalid. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_DEADLOCK (-7314)
Description |
The lock request has encountered a deadlock. |
Action |
Identify the information in deadlock through tjesmgr or OpenFrame Manager, and forcefully release the deadlocks. |
Note |
LOCKM_ERR_INVALID_PARM (-7315)
Description |
An invalid parameter has been identified during a lock. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_INVALID_LOCK_HANDLE (-7316)
Description |
An error occurred while retrieving the lock handle during a lock. |
Action |
Contact TmaxSoft Technical Support with the information about the program and data set that requested a lock. |
Note |
LOCKM_ERR_DO_NOT_OWN_LOCK_HANDLE (-7317)
Description |
The process that requested a lock does not own the lock handle. |
Action |
Contact TmaxSoft Technical Support with the information about the program and data set that requested a lock. |
Note |
LOCKM_ERR_INVALID_RETURN (-7318)
Description |
An error occurred during a lock request. |
Action |
Contact TmaxSoft Technical Support with the information about the program and data set that requested a lock. |
Note |
LOCKM_ERR_SQL_NO_DATA (-7319)
Description |
An internal error occurred during a lock request. |
Action |
Contact TmaxSoft Technical Support with the information about the program and data set that requested a lock. |
Note |
LOCKM_ERR_SQL_CLOSE_CURSOR (-7320)
Description |
Failed to close a cursor by using the SQLCloseCursor() function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
LOCKM_ERR_ODBC (-7401)
Description |
Failed to call an ODBC-related API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
LOCKM_ERR_FAIL_OVER_RECONNECTED (-7402)
Description |
The DBMS server connection within the library has been ended, but a new connection is established to the server instance with the same DNS name. |
Action |
Contact the DBMS server administrator, even through this situation is intended rather than an error. |
Note |
10. PGMDD (-8000)
The PGMDD module is a module that queries the assigned data set with the DD name. This section lists the error codes that can occur in the PGMDD module, descriptions of errors and suggested corrective actions.
PGMDD_ERR_INVALID_REQUEST (-8001)
Description |
An invalid parameter has been specified for running the job. |
Action |
Specify an appropriate parameter for the job. |
Note |
PGMDD_ERR_MEMORY_ALLOC (-8002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
PGMDD_ERR_NOT_INITIALIZED (-8003)
Description |
The PGMDD library function is used directly without calling the initialization function. |
Action |
Call the initialization function before using the PGMDD library function. |
Note |
PGMDD_ERR_BUFFER_OVERFLOW (-8004)
Description |
The buffer size provided for the information query function is insufficient. |
Action |
Provide a correctly calculated buffer size to store the information. |
Note |
PGMDD_ERR_NOT_IMPLEMENTED (-8009)
Description |
An internal error (Not Implemented) occurred in the PGMDD library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_INVALID_DDNAME (-8201)
Description |
An invalid DD name has been specified. |
Action |
Check whether the DD name has been correctly specified and retry. |
Note |
PGMDD_ERR_INVALID_HANDLE (-8202)
Description |
A PGMDD library usage error (Invalid Handle) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_DD_NOT_FOUND (-8203)
Description |
The DD specified by the user has not been allocated. |
Action |
Check whether the DD has been specified in the JCL. |
Note |
PGMDD_ERR_GETENV_FORMAT (-8204)
Description |
An internal error (Getenv Format) occurred in the PGMDD library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_DUPLICATE_HEADER (-8205)
Description |
A PGMDD library usage error (Duplicate Header) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_GETENV_HANDLE (-8207)
Description |
An internal error (Getenv Handle) occurred in the PGMDD library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_GETENV_PID (-8208)
Description |
An internal error (Getenv PID) occurred in the PGMDD library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_GETENV_HOSTNAME (-8209)
Description |
An internal error (Getenv hostname) occurred in the PGMDD library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_GETENV_STEPSEQ (-8210)
Description |
An internal error (Getenv STEPSEQ) occurred in the PGMDD library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_SELECT_DD (-8211)
Description |
Failed to retrieve the data set allocation information from the database. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_SELECT_DD (-8212)
Description |
Failed to save the data set allocation information to the shared memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
PGMDD_ERR_SYSTEM_PUTENV (-8901)
Description |
Failed to call the putenv() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
11. AMSX (-10000)
The AMSX module is responsible for data set allocation and management. This section lists the error codes that can occur in the AMSX module, descriptions of errors and suggested corrective actions.
AMSX_ERR_DUPLICATE_RECORD (-10001)
Description |
A duplicate catalog entry with the same name already exists in the catalog. |
Action |
Check whether the entry to register has already been cataloged, and change the name of the entry to register. |
Note |
AMSX_ERR_NOT_FOUND (-10002)
Description |
The catalog entry to search for is not found. |
Action |
Check whether the entry to search for has been cataloged, and correctly specify the entry name. |
Note |
AMSX_ERR_MEMORY_ALLOC (-10003)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
AMSX_ERR_INTERNAL (-10004)
Description |
An internal error occurred in the AMSX library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_NOT_IMPLEMENTED (-10005)
Description |
An internal error (Not Implemented) occurred in the AMSX library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_NO_RECORD (-10006)
Description |
The specified data set is empty. |
Action |
Specify a data set containing records. |
Note |
AMSX_ERR_INVALID_INPUT_PARAM (-10101)
Description |
The input value passed as parameter is invalid. |
Action |
Specify the input value correctly when running the application. |
Note |
AMSX_ERR_INVALID_ALLOC_PARAM (-10102)
Description |
The allocation entry passed as parameter is invalid. |
Action |
Specify the allocation entry correctly when running the application. |
Note |
AMSX_ERR_INVALID_FSPEC_TYPE (-10103)
Description |
The file type passed as parameter is invalid. |
Action |
Specify the file type correctly when running the application. |
Note |
AMSX_ERR_INVALID_CATALOG_NAME (-10104)
Description |
The catalog name passed as parameter is invalid. |
Action |
Specify the catalog name correctly when running the application. |
Note |
AMSX_ERR_INVALID_ENTRY_NAME (-10105)
Description |
The entry name passed as parameter is invalid. |
Action |
Specify the entry name correctly when running the application. |
Note |
AMSX_ERR_INVALID_ENTRY_TYPE (-10106)
Description |
The entry type passed as parameter is invalid. |
Action |
Specify the entry type correctly when running the application. |
Note |
AMSX_ERR_INVALID_MEMBER_NAME (-10107)
Description |
The member name passed as parameter is invalid. |
Action |
Specify the member name correctly when running the application. |
Note |
AMSX_ERR_INVALID_FILE_PATH (-10108)
Description |
The file path passed as parameter is invalid. |
Action |
Specify the file path correctly when running the application. |
Note |
AMSX_ERR_INVALID_DATASET_NAME (-10109)
Description |
The data set name passed as parameter is invalid. |
Action |
Specify the data set name correctly when running the application. |
Note |
AMSX_ERR_INVALID_DCB_TYPE (-10110)
Description |
An internal error (Invalid DCB Type) occurred in the AMSX library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_INVALID_PORTABLE_DS (-10111)
Description |
The data set type specified when executing IDCAMS Import is not a portable data set. |
Action |
The data set type for executing IDCAMS Import must be a portable data set created by executing IDCAMS Export. |
Note |
Refer to "2.2. IDCAMS" in OpenFrame Utility Reference Guide. |
AMSX_ERR_INVALID_LRECL (-10112)
Description |
The record size of a data set to perform copy does not match with that of copy target. |
Action |
Check the size of the record to be copied and specify the record size of the target data set. |
Note |
AMSX_ERR_INVALID_VOLUME_SERIAL (-10113)
Description |
The volume serial number passed as parameter is invalid. |
Action |
Specify the volume serial number correctly when running the application. |
Note |
AMSX_ERR_INVALID_VSAMTYPE (-10114)
Description |
An internal error (Invalid VSAM Type) occurred in the AMSX library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_INVALID_KEY_LENGTH (-10115)
Description |
The key length of a VSAM passed as parameter is invalid. |
Action |
Specify a correct key length for VSAM. |
Note |
AMSX_ERR_NOT_INITIALIZED (-10201)
Description |
The AMSX library API is directly used without the initialization function. |
Action |
Modify the source code that Descriptiond the error, to call the initialization function before calling the AMSX library API. |
Note |
AMSX_ERR_DUPLICATE_DATASET (-10202)
Description |
An internal error (Duplicate dataset) occurred in the AMSX library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_ENTRY_TYPE_MISMATCH (-10203)
Description |
An internal error (Entry Type Mismatch) occurred in the AMSX library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_BUFER_OVERFLOW (-10204)
Description |
The size of the buffer passed to execute BLDL is not sufficient to save actual data. |
Action |
Contact TmaxSoft Technical Support. |
Note |
AMSX_ERR_LOGICAL_ERROR (-10205)
Description |
A logical error occurred while executing a command requested from the library. |
Action |
Retrieve the displayed logs and contact TmaxSoft Technical Support. |
Note |
12. SMS (-11000)
SMS is a module which provides SMS and ACS functions. This section lists the error codes that can occur in the SMS module, descriptions of errors and suggested corrective actions.
SMS_ERR_INVALID_REQUEST (-11001)
Description |
An invalid parameter has been passed for the job to perform. |
Action |
Specify a valid parameter for the job. |
Note |
SMS_ERR_MEMORY_ALLOC (-11002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
SMS_ERR_NOT_IMPLEMENTED (-11009)
Description |
An internal error (Not Implemented) occurred in the SMS library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SMS_ERR_NULL_CLASS_NAME (-11101)
Description |
An SMS library usage error (Null Class Name) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SMS_ERR_CLASS_NOT_FOUND (-11102)
Description |
The SMS class specified in the JCL is not found in the system. |
Action |
Add the SMS class as a configuration value. |
Note |
For more information about the sms subject in OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SMS_ERR_INVALID_CLASS_NAME (-11103)
Description |
The SMS class name specified in the JCL is incorrect. |
Action |
Check the JCL to determine if the SMS class name has been correctly specified. |
Note |
An SMS class name can be up to 8 bytes long, with alphanumeric characters (A-Z, 0-9). |
SMS_ERR_INVALID_SMS_CONFIG (-11104)
Description |
The values set to the sms subject to register SMS classes are invalid. |
Action |
Correct any invalid values related to the sms subject under OpenFrame Configuration. |
Note |
For more information about the sms subject in OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SMS_ERR_VOLUME_NOT_FOUND (-11105)
Description |
The volume serial number assigned to the storage class is not found in the system. |
Action |
Use a volume serial number registered in OpenFrame, or register a new volume serial number. |
Note |
For information about how to register a volume, refer to the description for volmgr in OpenFrame Tool Reference Guide. |
SMS_ERR_TOO_MANY_VOLUMES (-11106)
Description |
Too many volume serial numbers have been assigned to a single storage class. The maximum volume serial number that can be assigned to one storage class is 4096 bytes. |
Action |
Assign volume serial numbers to a single storage class only as many as necessary. Correct the settings related to the sms subject, under OpenFrame Configuration. |
Note |
For more information about the sms subject in OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SMS_ERR_DSNAME_IS_NULL (-11201)
Description |
An SMS library usage error (Dsname is Null) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SMS_ERR_DEFAULT_MGMTCLAS (-11202)
Description |
The default management class name specified to the DEFAULT_MGMTCLAS key is invalid, in the DATASET_DEFAULT section of the ds subject under OpenFrame Configuration. |
Action |
Correct the value specified as the default management class. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SMS_ERR_DEFAULT_STORCLAS (-11203)
Description |
The default management class name specified to the DEFAULT_STORCLAS key is invalid, in the DATASET_DEFAULT section of the ds subject under OpenFrame Configuration. |
Action |
Correct the value specified as the default storage class. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SMS_ERR_ACS_CONFIGURATION (-11204)
Description |
Items in the acs subject under OpenFrame Configuration are incorrectly set. |
Action |
Correct the settings of the items in the acs subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
13. DSCOM (-12000)
The DSCOM module is a data set common library module. This section lists the error codes that can occur in the DSCOM module, descriptions of errors and suggested corrective actions.
DSCOM_ERR_INVALID_REQUEST (-12001)
Description |
An invalid parameter has been passed for the job to perform. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_MEMORY_ALLOC (-12002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
DSCOM_ERR_INTERNAL (-12003)
Description |
An internal error occurred in the DSCOM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_NOT_IMPLEMENTED (-12009)
Description |
An internal error (Not Implemented) occurred in the DSCOM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_INVALID_LANG (-12010)
Description |
An invalid data is found when converting a field data. |
Action |
Check whether the data field of the user program has been properly defined, as well as the compiled binary file contains no error. |
Note |
DSCOM_ERR_INVALID_DSNAME (-12101)
Description |
The data set name is invalid. |
Action |
Check the data set name. |
Note |
DSCOM_ERR_INVALID_MEMBER (-12102)
Description |
The member name is invalid. |
Action |
Check the member name. |
Note |
DSCOM_ERR_INVALID_GENERATION (-12103)
Description |
The GDS name is invalid. |
Action |
Check the GDS name. |
Note |
DSCOM_ERR_DSNAME_LENGTH (-12105)
Description |
The length of the data set name is invalid. |
Action |
Check the length of the data set name. |
Note |
DSCOM_ERR_MEMBER_LENGTH (-12106)
Description |
The length of the member name is invalid. |
Action |
Check the length of the member name. |
Note |
DSCOM_ERR_GENERATION_LENGTH (-12107)
Description |
The length of the GDS name is invalid. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_INVALID_FILTER_KEY (-12108)
Description |
The wildcard requested for a data set name search has been incorrectly specified. |
Action |
Check whether the data set name has been specified according to the wildcard search rules. |
Note |
DSCOM_ERR_INVALID_PARAM (-12201)
Description |
The parameter value is invalid. |
Action |
Check the parameter value. |
Note |
DSCOM_ERR_INVALID_ODO_COUNT (-12202)
Description |
The value in the ODO (OCCURS DEPENDING ON) field is invalid. |
Action |
Check the value in the ODO field. |
Note |
DSCOM_ERR_INVALID_SCHEMA (-12203)
Description |
An invalid schema file has been used. |
Action |
Check the schema file. |
Note |
DSCOM_ERR_INVALID_CUSTOM (-12204)
Description |
An invalid user CPM file has been used. |
Action |
Check the CPM file. |
Note |
DSCOM_ERR_INVALID_SACEE (-12207)
Description |
The user authentication information is invalid. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_INVALID_COND (-12208)
Description |
The schema file contains an invalid conditional statement. |
Action |
Check if the field name specified to the conditional statement in the schema file is correct. |
Note |
DSCOM_ERR_SYSTEM_POPEN (-12901)
Description |
An error occurred from the popen() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_FOPEN (-12902)
Description |
An error occurred from the fopen() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_FREAD (-12903)
Description |
An error occurred from the fread() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_FWRITE (-12904)
Description |
An error occurred from the fwrite() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_STRTOL (-12905)
Description |
An error occurred from the strtol() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_PUTENV (-12906)
Description |
An error occurred from the putenv() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_STAT (-12907)
Description |
An error occurred from the stat() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_UTIME (-12908)
Description |
An error occurred from the utime() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_CHMOD (-12909)
Description |
An error occurred from the chmod() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_UNLINK (-12910)
Description |
An error occurred from the unlink() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_OPENDIR (-12911)
Description |
An error occurred from the opendir() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
DSCOM_ERR_SYSTEM_CLOSEDIR (-12912)
Description |
An error occurred from the closedir() system call function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
14. CPMLIB (-15000)
The CPMLIB module is responsible for converting code pages. This section lists the error codes that can occur in the CPMLIB module, descriptions of errors and suggested corrective actions.
CPMNAME_IS_NULL (-15000)
Description |
The cpm name parameter, among the internal function arguments, is set to NULL. |
Action |
Check whether the cpm name has been correctly specified, and if the error persists, contact the system administrator. |
Note |
NOT_SET_CPMDIR (-15001)
Description |
The CPMDIR environment variable is NULL. |
Action |
Specify the $CPMDIR environment variable. |
Note |
CPM_OPEN_ERROR (-15002)
Description |
An error occurred while opening the cpm file. |
Action |
Check whether the file is found in the specified directory. |
Note |
CPM_READ_ERROR (-15003)
Description |
An error occurred while reading the cpm file. |
Action |
Check whether the file has a correct format for the specified directory. |
Note |
CPM_WRITE_ERROR (-15004)
Description |
An error occurred while writing to a cpm file. |
Action |
Contact the system administrator. |
Note |
UCMNAME_IS_NULL (-15005)
Description |
The ucm name parameter, among the internal function arguments, is set to NULL. |
Action |
Check whether the ucm name has been correctly specified, and if the error persists, contact the system administrator. |
Note |
UCM_OPEN_ERROR (-15006)
Description |
An error occurred while opening the ucm file. |
Action |
Check whether the file is found in the specified directory. |
Note |
UCM_READ_ERROR (-15007)
Description |
An error occurred while reading the ucm file. |
Action |
Check whether the file has a correct format for the specified directory. |
Note |
UCM_WRITE_ERROR (-15008)
Description |
An error occurred while writing to a ucm file. |
Action |
Contact the system administrator. |
Note |
CPMMAP_IS_NULL (-15009)
Description |
The argument passed to an internal function is NULL. |
Action |
Contact the system administrator. |
Note |
CPMLIB_ERR_CPM_CONV_ERROR (-15010)
Description |
An error occurred during the cpm conversion. |
Action |
Check whether the cpm file in use or the data to be convert is valid. |
Note |
CPMLIB_ERR_USRMAP_OPEN_ERROR (-15011)
Description |
An error occurred while opening a user mapping file. |
Action |
Check whether the user mapping file to use is found with a correct name in a correct location. |
Note |
CPMLIB_ERR_USRMAP_INVALID_FORMAT_ERROR (-15012)
Description |
The format of a user mapping file is invalid. |
Action |
Check whether the user mapping file to use has a correct format. |
Note |
15. SAF (-17000)
The SAF module is responsible for OpenFrame system security. This section lists the error codes that can occur in the SAF module, descriptions of errors and suggested corrective actions.
SAF_ERR_MEMORY_ALLOC (-17003)
Description |
Failed to allocate memory. |
Action |
Check whether the system has sufficient available memory. |
Note |
SAF_ERR_INTERNAL (-17004)
Description |
Failed to call the Tmax API. |
Action |
Check whether the Tmax configuration is correct. |
Note |
SAF_ERR_INVALID_REQUEST (-17005)
Description |
An invalid parameter has been used to call a function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAF_ERR_NOT_IMPLEMENTED (-17006)
Description |
TACF Manager is used to add/change/delete/find groups or users when the OS authentication has been enabled. |
Action |
Use the functions provided by the OS, TACF Manager. |
Note |
SAF_ERR_NOT_INITIALIZED (-17007)
Description |
The SAF functions are used without the TACF module having been initialized. |
Action |
Perform the following to ensure that TACF initialization has been successfully completed.
|
Note |
For more information about the ofsys and tacf subjects in OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SAF_ERR_AUTH_CONFIGURATION (-17008)
Description |
The VALUE of both OS_AUTH and TACF_AUTH keys are set to NO, in the AUTH_METHOD section of the saf subject, under OpenFrame Configuration. |
Action |
Set one of the two keys to YES, depending on whether the OS or TACF authentication method is used. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SAF_ERR_GROUPNAME_TOO_LONG (-17009)
Description |
The length of a group name exceeds 8 bytes. |
Action |
Shorten the name not to exceed 8 bytes. |
Note |
SAF_ERR_TACF_NOT_ACTIVE (-17010)
Description |
The TACF functions are used without the TACF authentication method having been enabled. |
Action |
Set the VALUE of the TACF_AUTH key to YES, in the AUTH_METHOD section of the saf subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SAF_ERR_DISCONNECTED (-17011)
Description |
Connection to the database has been lost. |
Action |
Check the database connection status. |
Note |
SAF_ERR_OFCOM_CONFIGURATION (-17012)
Description |
The VALUE of the DATA_DIR key is empty, in the DIRECTORY section of the ofsys subject under OpenFrame Configuration. |
Action |
Check the configuration file. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SAF_ERR_ELEMENT_NOT_FOUND (-17014)
Description |
Data caching has not been implemented in memory. However, this error code is not delivered to the user. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAF_ERR_DUPLICATE_ELEMENT (-17015)
Description |
An attempt was made to register a duplicate data that had been already cached in memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAF_ERR_DUPLICATE_GROUP (-17101)
Description |
An attempt was made to add a duplicate group that already exists. |
Action |
Change the name of the group to add. |
Note |
SAF_ERR_GROUP_NOT_FOUND (-17102)
Description |
The group profile of a group is not found. |
Action |
Check whether the group profile exists. If no profile exists, request that the security administrator create the group profile. |
Note |
SAF_ERR_DUPLICATE_USER (-17103)
Description |
An attempt was made to add a duplicate user that already exists. |
Action |
Change the user ID to add. |
Note |
SAF_ERR_USER_NOT_FOUND (-17104)
Description |
The user profile of a user is not found. |
Action |
Check whether the user profile exists. If no profile exists, request that the security administrator create the user profile. |
Note |
SAF_ERR_USER_REVOKED (-17105)
Description |
An attempt was made to log in to the system as a user in REVOKE status. |
Action |
Contact the security administrator. |
Note |
SAF_ERR_CLASS_NOT_FOUND (-17109)
Description |
The class profile is not found. |
Action |
Check whether the class profile exists.. If no profile exists, request that the security administrator create the class profile. |
Note |
SAF_ERR_DUPLICATE_PROFILE (-17110)
Description |
An attempt was made to add a duplicate data set or general resource that already exists. |
Action |
Change the name of the data set or general resource to add. |
Note |
SAF_ERR_PROFILE_NOT_FOUND (-17111)
Description |
The profile of a data set or general resource is not found. |
Action |
Check whether the data set or general resource profile exists. If it doesn’t exist, request that the security administrator create it. |
Note |
SAF_ERR_DUPLICATE_MEMBER (-17113)
Description |
An attempt was made to add a duplicate member that already exists in the group resource. |
Action |
Delete the duplicate member and retry. |
Note |
SAF_ERR_DUPLICATE_ACCESS_LIST (-17114)
Description |
An attempt was made to add a duplicate access permission list that already exists. |
Action |
Check whether the access permission list to add is correct. |
Note |
SAF_ERR_VERIFICATION_FAILURE (-17201)
Description |
Failed to authenticate a user. |
Action |
Check whether the ID and password of the user are correct. |
Note |
SAF_ERR_NOT_AUTHORIZED (-17202)
Description |
There is no sufficient access rights for the data set or general resource. |
Action |
Request that the security administrator grant access to the data set or general resource. |
Note |
SAF_ERR_GROUP_NOT_CONNECTED (-17203)
Description |
An attempt was made to connect a user to a specific group that does not exist. |
Action |
Check whether the group profile exists. |
Note |
SAF_ERR_OWNER_NOT_FOUND (-17204)
Description |
The user or group to specify as OWNER is not found. |
Action |
Check whether the profile of the user or group exists. |
Note |
SAF_ERR_NOTIFY_NOT_FOUND (-17205)
Description |
The user or group to specify as NOTIFY is not found. |
Action |
Check whether the profile of the user or group exists. |
Note |
SAF_ERR_SUPGROUP_NOT_FOUND (-17208)
Description |
The profile of the group to specify as a superior group is not found. |
Action |
Check if the specified superior group profile exists. If it does not exist, request a new registration from the security administrator. |
Note |
SAF_ERR_SUPGROUP_AND_OWNER (-17209)
Description |
The name of the OWNER group is different from that of the superior group, when both groups have been specified. |
Action |
Specify the same name for both the OWNER group and the superior group. |
Note |
SAF_ERR_DFTGROUP_NOT_FOUND (-17210)
Description |
The profile of the default group is not found. |
Action |
Check the name of the default group. |
Note |
SAF_ERR_NER_PASSWD_REQUIRED (-17211)
Description |
The current password has expired. |
Action |
Change the password. |
Note |
Refer to the information about password change interval in OpenFrame TACF Administrator’s Guide. |
SAF_ERR_LOGIN_NOT_ALLOWED (-17212)
Description |
An attempt was made to log in the system outside the specified days or hours. |
Action |
Check the days and hours specified in the USER profile. |
Note |
Refer to the information about WDAY and WTIME from "2.3 USER Profile" in OpenFrame TACF Administrator’s Guide. |
SAF_ERR_PASSWORD_INCORRECT (-17213)
Description |
The current password specified with the PASSWORD command is incorrect. |
Action |
Check the current password. |
Note |
Refer to the information about password change interval in OpenFrame TACF Administrator’s Guide. |
SAF_ERR_SUSPENDED_USER (-17214)
Description |
A locked user account attempted to access the system. |
Action |
Wait until the account is unlocked and retry. |
Note |
Refer to the description for the "ACCOUNTLOCK status" from "Chapter 2. User Management" in OpenFrame TACF Administrator’s Guide. |
SAF_ERR_LOCK_FILE_OPEN (-17801)
Description |
Failed to open a locked file that is internally managed in TACF. |
Action |
Check whether the system administrator has permissions to READ and WRITE to the $OPENFRAME_HOME/data directory. |
Note |
SAF_ERR_LOCK_FILE_LOCK (-17802)
Description |
Failed to lock a file. |
Action |
Contact the system administrator. |
Note |
SAF_ERR_LOG_FILE_OPEN (-17803)
Description |
Failed to generate a TACF log file. |
Action |
Check whether sufficient access rights for the log generation directory are specified in the configuration file. |
Note |
SAF_ERR_LOG_FILE_WRITE (-17804)
Description |
Failed to write to a TACF log file. |
Action |
Check whether there are sufficient access rights for the file and available disk space. |
Note |
SAF_ERR_GETGR_SYSTEM_CALL (-17901)
Description |
Failed to call the getgrgid() system function. |
Action |
Check whether the system administrator has the root authority for the operating system. |
Note |
SAF_ERR_CRYPT_SYSTEM_CALL (-17903)
Description |
Failed to call the crypt() system function. |
Action |
Check whether the system administrator has the root authority for the operating system. |
Note |
SAF_ERR_SETSP_SYSTEM_CALL (-17904)
Description |
Failed to call the setpwdb() system function. |
Action |
Check whether the system administrator has the root authority for the operating system. |
Note |
SAF_ERR_ENDSP_SYSTEM_CALL (-17905)
Description |
Failed to call the endpwdb() system function. |
Action |
Check whether the system administrator has the root authority for the operating system. |
Note |
16. OFCOM (-22000)
The OFCOM module is an OpenFrame common library module. This section lists the error codes that can occur in the OFCOM module, descriptions of errors and suggested corrective actions.
OFCOM_ERR_INVALID_REQUEST (-22001)
Description |
An invalid parameter has been passed for the job to perform. |
Action |
Specify a valid parameter for the job. |
Note |
OFCOM_ERR_MEMORY_ALLOC (-22002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
OFCOM_ERR_BUFFER_OVERFLOW (-22003)
Description |
The provided buffer is too small for the data. |
Action |
Allocate sufficient buffer space for the data. |
Note |
OFCOM_ERR_VALUE_NOT_FOUND (-22004)
Description |
The specified value in the configuration file is not found. |
Action |
Check whether the specified value exists in the configuration file. |
Note |
OFCOM_ERR_PATHNAME_LENGTH (-22005)
Description |
The length of a path name exceeds the specified length. |
Action |
Ensure that the path name does not exceed the specified length. |
Note |
OFCOM_ERR_FILE_NOT_FOUND (-22006)
Description |
The specified file is not found. |
Action |
Check whether the file name is correct. |
Note |
OFCOM_ERR_DIRECTORY_NOT_FOUND (-22007)
Description |
The specified directory is not found. |
Action |
Check whether the directory name is correct. |
Note |
OFCOM_ERR_NOT_IMPLEMENTED (-22009)
Description |
An internal error (Not Implemented) occurred in the OFCOM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_INTERNAL_ERROR (-22010)
Description |
An internal error occurred in the OFCOM library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_NOT_FOUND (-22011)
Description |
Failed to retrieve the requested value because of an OFCOM library internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_KEY_NOT_FOUND (-22012)
Description |
Failed to retrieve the requested configuration value. |
Action |
Refer to OpenFrame Configuration Guide to check whether the configuration value to search for is valid. |
Note |
OFCOM_ERR_NOT_INITIALIZED (-22013)
Description |
The OFCOM library has not been initialized. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_DUPLICATE_RECORD (-22014)
Description |
A duplicate configuration or error value has been added. |
Action |
Check the value to add, or use the import command by referring to OpenFrame Tool Reference Guide. |
Note |
OFCOM_ERR_SECTION_NOT_FOUND (-22015)
Description |
Failed to retrieve the requested configuration value. |
Action |
Refer to OpenFrame Configuration Guide to check whether the requested configuration value is valid. |
Note |
OFCOM_ERR_SHM_INIT (-22101)
Description |
Failed to initialize the shared memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SHM_OPEN (-22102)
Description |
Failed to access the shared memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SHM_CLOSE (-22103)
Description |
Failed to free up the shared memory after it had been used. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SHM_ATTACH (-22104)
Description |
Failed to attach the process to the shared memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SHM_DETACH (-22105)
Description |
Failed to detach the process from the shared memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SHM_STAT (-22106)
Description |
Unable to retrieve the status information of the shared memory. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SHM_EXIST (-22107)
Description |
The shared memory to create already exists. |
Action |
Delete the existing shared memory. |
Note |
Refer to ipcs and ipcrm in Unix Manual Page. |
OFCOM_ERR_ODBC (-22110)
Description |
Failed to call ODBC-related API functions. |
Action |
Check SQLSTATE and native error message. |
Note |
OFCOM_ERR_FAIL_OVER_RECONNECTED (-22111)
Description |
Reconnection occurred after an interrupted database connection. |
Action |
The operation is not affected. For detailed information, refer to the server logs. |
Note |
OFCOM_ERR_ENV_OPENFRAME_HOME (-22201)
Description |
The OPENFRAME_HOME environment variable is not found. |
Action |
Define and export the OPENFRAME_HOME environment variable. |
Note |
OFCOM_ERR_OPEN_CONF_FILE (-22202)
Description |
Unable to open the specified configuration file. |
Action |
Check whether the name of the file is correct. Create a new configuration file. |
Note |
OFCOM_ERR_MAX_CONF_FILE (-22204)
Description |
The number of configuration files exceeds the maximum allowable number. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Currently, up to 256 configuration files can be created. |
OFCOM_ERR_WRONG_CONFIGURATION (-22205)
Description |
The configuration file contains an incorrect syntax. |
Action |
Correct the syntax in the configuration file. |
Note |
OFCOM_ERR_INVALID_CONF_VALUE (-22206)
Description |
An invalid configuration value is found. |
Action |
Specify a valid value in OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
OFCOM_ERR_CONF_TABLE_IS_EMPTY (-22207)
Description |
The configuration table in the database is empty. |
Action |
Retrieve the OpenFrame configuration values to the database. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
OFCOM_ERR_CONF_CACHE (-22208)
Description |
An error occurred in TCache. |
Action |
Check the TCache logs and refer to the relevant information in the TCache manual. |
Note |
OFCOM_ERR_INVALID_NODENAME_ENVVAR (-22211)
Description |
The OPENFRAME_NODENAME environment variable has incorrectly specified or not been specified. |
Action |
Specify a correct node name to the environment variable. The same restrictions as the Tmax node naming rules apply. |
Note |
OFCOM_ERR_UNLINK_FAILURE (-22301)
Description |
Failed to delete an external RC file. |
Action |
Check whether there are sufficient permissions for the directory or file. |
Note |
OFCOM_ERR_OPEN_EXTRC_FILE (-22302)
Description |
Failed to open an external RC file. |
Action |
Check whether there are sufficient permissions for the directory or file. |
Note |
OFCOM_ERR_LOCK_FAILURE (-22401)
Description |
Failed to open and lock a file. |
Action |
Check whether there are sufficient permissions for the directory or file. |
Note |
OFCOM_ERR_UNLOCK_FAILURE (-22402)
Description |
Failed to unlock or close a file. |
Action |
Check whether there are sufficient permissions for the directory or file. |
Note |
OFCOM_ERR_STATVFS_CALL (-22503)
Description |
Failed to call the statvfs() system function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_FOPEN_CALL (-22504)
Description |
Failed to open the error code file. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_OPENDIR_CALL (-22505)
Description |
Failed to call the opendir() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_INVALID_PARAMETER (-22601)
Description |
An invalid input parameter has been entered when analyzing parameters. |
Action |
Check the validity of the input parameter. |
Note |
OFCOM_ERR_PAREN_MISMATCHED (-22602)
Description |
Parentheses do not match when analysing parameters. |
Action |
Check whether the parentheses of the input parameter match. |
Note |
OFCOM_ERR_INVALID_POS (-22611)
Description |
An invalid value has been specified as a sub-parameter position, during a parameter tree analysis. The position value must be a number type string ("@n") starting from 1. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_QUERY_LEVEL (-22612)
Description |
A path step specified to obtain a sub-parameter in a specific path exceeds 16 steps, during a parameter tree analysis. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_EXALT_FOUND (-22613)
Description |
Exclusive parameters have been specified concurrently even if they cannot, during a parameter tree analysis. |
Action |
Check the syntax of the input parameters and correct it. |
Note |
OFCOM_ERR_SUB_NOT_ALLOWED (-22614)
Description |
A sub-parameter has been specified for a parameter that cannot have a sub-parameter, during a parameter tree analysis. |
Action |
Check the syntax of the input parameters and correct it. |
Note |
OFCOM_ERR_SUB_ONE_ALLOWED (-22615)
Description |
Multiple sub-parameters have been specified for a parameter that can have only one sub-parameter, during a parameter tree analysis. |
Action |
Check the syntax of the input parameters and correct it. |
Note |
OFCOM_ERR_SUB_ONE_REQUIRED (-22616)
Description |
No sub-parameter has been specified for a parameter that must have one sub-parameter, during a parameter tree analysis. |
Action |
Check the syntax of the input parameters and correct it. |
Note |
OFCOM_ERR_SUB_REQUIRED (-22617)
Description |
No sub-parameter has been specified for a parameter that must have one or more sub-parameter, during a parameter tree analysis. |
Action |
Check the syntax of the input parameters and correct it. |
Note |
OFCOM_ERR_DUPLICATE_ERRNO (-22701)
Description |
A duplicate error code already exists. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_INVALID_FORMAT (-22702)
Description |
The error format is invalid. |
Action |
Contact TmaxSoft Technical Support. |
Note |
OFCOM_ERR_LOG_FILE_OPEN (-22801)
Description |
A problem occurred while opening a log file to write logs. |
Action |
Contact TmaxSoft Technical Support(Refer to the displayed error message). |
Note |
OFCOM_ERR_LOG_FILE_CLOSE (-22802)
Description |
A problem occurred while closing a log file after writing logs. |
Action |
Contact TmaxSoft Technical Support(Refer to the displayed error message). |
Note |
OFCOM_ERR_LOG_FILE_WRLCK (-22803)
Description |
A problem occurred while locking a log file to write logs. |
Action |
Contact TmaxSoft Technical Support(Refer to the displayed error message). |
Note |
OFCOM_ERR_LOG_FILE_UNLCK (-22804)
Description |
A problem occurred while unlocking a log file after writing logs. |
Action |
Contact TmaxSoft Technical Support(Refer to the displayed error message). |
Note |
OFCOM_ERR_LOG_FILE_LSEEK (-22805)
Description |
A problem occurred while finding the location to write a record in a log file. |
Action |
Contact TmaxSoft Technical Support(Refer to the displayed error message). |
Note |
OFCOM_ERR_LOG_FILE_WRITE (-22806)
Description |
A problem occurred while writing a record by using the the write() function in a log file. |
Action |
Contact TmaxSoft Technical Support(Refer to the displayed error message). |
Note |
OFCOM_ERR_MAX_PACKED_BYTES (-22811)
Description |
The number of bytes passed to the Packed Decimal conversion function exceeds the maximum allowable value. |
Action |
Specify a smaller number of bytes for Packed Decimal than the maximum allowable value (10 bytes). |
Note |
OFCOM_ERR_MAX_ZONED_BYTES (-22812)
Description |
The number of bytes passed to the Zoned Decimal conversion function exceeds the maximum allowable value. |
Action |
Specify a smaller number of bytes for Zoned Decimal than the maximum allowable value (18 bytes). |
Note |
OFCOM_ERR_MAX_BCD_DIGITS (-22813)
Description |
The number of digits passed to the Binary Coded Decimal conversion function exceeds the maximum allowable value. |
Action |
Specify a smaller number of digits than the maximum allowable value (18 digits). |
Note |
OFCOM_ERR_BCD_CONVERSION (-22814)
Description |
An error occurred while executing the Binary Coded Decimal conversion function. |
Action |
Check the value in the BCD buffer that has been passed to the conversion function. |
Note |
OFCOM_ERR_BCD_CONVERSION_WARNING (-22815)
Description |
An error occurred while executing the Binary Coded Decimal conversion function. |
Action |
Check the value in the BCD buffer that has been passed to the conversion function. |
Note |
OFCOM_ERR_SYSTEM_OPEN (-22901)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
OFCOM_ERR_SYSTEM_READ (-22902)
Description |
Failed to call the read() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed error message. |
17. SAFX (-23000)
SAFX is a module which provides an interface between SAF, which is the OpenFrame system security module, and the authentication server. This section lists the error codes that can occur in the SAFX module, descriptions of errors and suggested corrective actions.
SAFX_ERR_INVALID_REQUEST (-23005)
Description |
An invalid input parameter has been used to call a function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAFX_ERR_NOT_INITIALIZED (-23007)
Description |
The SAF functions are used without the TACF module having been successfully initialized. |
Action |
Perform the following to ensure that TACF initialization has been successfully completed.
|
Note |
For more information about the ofsys subject in OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
SAFX_ERR_MAX_ACEE_COUNT (-23009)
Description |
The number of concurrent users in the system exceeds the maximum allowed count, which is 32,768. |
Action |
Reduce the number of concurrent users in the system, and if the error persists, restart the TACF server. |
Note |
SAFX_ERR_INVALID_TOKEN (-23010)
Description |
An invalid token has been received from a client. |
Action |
Contact TmaxSoft Technical Support. |
Note |
18. SAFO (-24000)
SAFO is a module that provides an interface between SAF, OpenFrame system security and OpenFrame online products. This section lists the error codes that can occur in the SAFO module, descriptions of errors and suggested corrective actions.
SAFO_ERR_MEMORY_ALLOC (-24003)
Description |
Failed to allocate system memory. |
Action |
Check if the system has sufficient available memory. |
Note |
SAFO_ERR_INVALID_REQUEST (-24005)
Description |
An invalid function input parameter has been used to call the function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAFO_ERR_NOT_INITIALIZED (-24007)
Description |
The SAF functions are used without the TACF module having been successfully initialized. |
Action |
Perform the following to ensure that TACF initialization has been successfully completed.
|
Note |
For more information about the ofsys and tacf subjects in OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
19. SAF BAT (-26000)
SAF BAT is a module that provides an interface between SAF, which is the OpenFrame system security module, and batch products. This section lists the error codes that can occur in the SAF BAT module, descriptions of errors and suggested corrective actions.
SAF_BATCH_ERR_INVALID_REQUEST (-26005)
Description |
An internally invalid input parameter has been used to call a function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAF_BATCH_ERR_V_NOT_PREPARED (-26101)
Description |
The initialization process has not been performed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SAF_BATCH_ERR_V_NOT_CREATED (-26102)
Description |
TACF has not been initialized. |
Action |
Contact TmaxSoft Technical Support. |
Note |
20. MEMM (-27000)
The MEMM module is responsible for dynamic memory allocation and its management. This section lists the error codes that can occur in the MEMM module, descriptions of errors and suggested corrective actions.
SHM_OPEN (-27001)
Description |
The shmget() or shmat() system call failed while opening the shared memory. |
Action |
Check whether the shared memory key is valid. |
Note |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
SHM_ATTACH (-27002)
Description |
The shmat() system call failed. |
Action |
Check whether the shared memory created with the given key can be attached to the process. |
Note |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
SHM_GET (-27003)
Description |
The shmget() system call failed. |
Action |
Check whether the shared memory key is valid. |
Note |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
SHM_CTL (-27004)
Description |
The shmctl() system call failed. |
Action |
Check whether the shared memory key is valid. |
Note |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
SHM_ALREADY_INIT (-27005)
Description |
The shared memory has been already initialized. |
Action |
Check whether the same shared memory has been initialized previously. |
Note |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
SHM_NOTFND (-27006)
Description |
The ID corresponding to the shared memory is not found. |
Action |
Check whether the requested ID is valid. |
Note |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
MEMORY_ALLOCATION (-27007)
Description |
Failed to allocate system memory. |
Action |
Check if there is any problem with the memory allocation process. |
Note |
21. TLIC (-28000)
The TLIC module is responsible for checking the OpenFrame license. This section lists the error codes that can occur in the TLIC module, descriptions of errors and suggested corrective actions.
TLIC_ERR_MEMORY_ALLOC (-28003)
Description |
Failed to allocate system memory. |
Action |
Check whether the system has sufficient available memory. |
Note |
TLIC_ERR_INVALID_REQUEST (-28004)
Description |
An invalid function input parameter has been used to call the function. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TLIC_ERR_INTERNAL_ERROR (-28005)
Description |
Failed to call the system() function. |
Action |
Contact the system administrator. |
Note |
TLIC_ERR_NOT_IMPELMENTED (-28006)
Description |
An attempt was made to retrieve the HostID from Microsoft Windows. |
Action |
Implement the program from Unix. |
Note |
TLIC_ERR_FILE_OPEN_FAILURE (-28010)
Description |
Failed to open the license file. |
Action |
To generate the license file, check whether there are sufficient permissions to write to the directory. To check the license file, check if the license file exists in $OPENFRAME_HOME/license. |
Note |
TLIC_ERR_FILE_WRITE_FAILURE (-28011)
Description |
There are insufficient permissions to write to the directory in which to generate the license file. |
Action |
Grant the write permission to the directory. |
Note |
TLIC_ERR_FILE_READ_FAILURE (-28012)
Description |
The license file is not found. |
Action |
Check if the path correctly points to the license file. |
Note |
TLIC_ERR_INVALID_MAGIC_NUMBER (-28020)
Description |
An internal value used to generate the OpenFrame license file is invalid. |
Action |
Contact the license issuer. |
Note |
TLIC_ERR_INVALID_CHECK_SUM (-28021)
Description |
The license file is invalid. |
Action |
Get a reissued license. |
Note |
TLIC_ERR_HOSTNAME_MISMATCH (-28023)
Description |
OpenFrame is used in a host whose name does not match with that of the permitted host. |
Action |
Get a reissued license with the correct host name. |
Note |
TLIC_ERR_HOSTID_MISMATCH (-28024)
Description |
OpenFrame is used in a host whose ID does not match with that of the permitted host. |
Action |
Get a reissued license with the correct host ID. |
Note |
TLIC_ERR_LNCPU_MISMATCH (-28025)
Description |
The number of CPUs does not match with the permitted number. |
Action |
Get a reissued license with the correct number of CPUs. |
Note |
TLIC_ERR_LICENSE_EXPIRED (-28026)
Description |
A demo license has expired. |
Action |
Get a reissued demo license. |
Note |
TLIC_ERR_PRODUCT_MISMATCH (-28027)
Description |
The issued license does not match with the product. |
Action |
Check whether the issued license matches with the product to use. |
Note |
22. TTREE (-29000)
TTREE is a TTREE type of memory management module. This section lists the error codes that can occur in the TTREE module, descriptions of errors and suggested corrective actions.
ALLOC (-29001)
Description |
An error occurred during memory allocation. |
Action |
Increase the size of shared memory. |
Note |
INVREQ (-29002)
Description |
An invalid request has been made. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
NOTFND (-29003)
Description |
No item is found with the specified key. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
DUPLICATED (-29004)
Description |
A duplicate key of the item to add already exists. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
KEY_LENGERR (-29005)
Description |
The length of the key buffer to receive is shorter than the actual key length. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
DATA_LENGERR (-29006)
Description |
The length of the data buffer to receive is shorter than the actual data length. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
DELETED (-29007)
Description |
The item to delete has been already deleted. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
INVMEMMID (-29008)
Description |
The ID of the MEMM module is invalid. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
ITEM_ENQBUSY (-29009)
Description |
The item cannot be accessed because it has been already locked. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
INTERNAL (-29011)
Description |
An internal error occurred in the module. |
Action |
The exception error code is important for diagnosing internal system errors. Thus, when an error occurs, contact the system administrator by referring to the details of the circumstances and error messages described in the log. |
Note |
23. SVRCOM (-32000)
The SVRCOM module is the Tmax Server common library module. This section lists the error codes that can occur in the SVRCOM module, descriptions of errors and suggested corrective actions.
SVRCOM_ERR_INTERNAL (-32001)
Description |
An internal SVRCOM error occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_INVALID_PARAM (-32002)
Description |
An invalid parameter has been specified to call the libsvrcom() function. This error basically cannot be raised, because the library is currently not available for external use. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_INVALID_CONFIG (-32003)
Description |
There is a problem in the OpenFrame configuration. |
Action |
Check the displayed messages in the server ulog to identify the problem and then try to fix it. After the problem is fixed, restart OpenFrame. |
Note |
SVRCOM_ERR_INVALID_LENGTH (-32004)
Description |
The buffer size passed as parameter to call libsvrcom() is not sufficient. This error often occurs while processing the svrcom_fbget() function call. This error basically cannot be raised, because the library is currently not available for external use. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_DATASET_EXIST (-32010)
Description |
A file already exists in the specified path for the DSLOAD service. |
Action |
Check the path specified by the dsload program or OFManager. |
Note |
SVRCOM_ERR_SVR_STARTED (-32101)
Description |
There is a problem related to an OpenFrame server coding standard. This error may occur when the SVRCOM library has been notified more than twice that Tmax server has been started. This error basically cannot be raised, because the library is currently not available for external use. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_SVR_NOT_STARTED (-32102)
Description |
There is a problem related to an OpenFrame server coding standard. This error may occur when successor jobs are set to run without notifying the SVRCOM library that Tmax server has started. This error basically cannot be raised, because the library is currently not available for external use. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_SVC_STARTED (-32111)
Description |
There is a problem related to an OpenFrame server coding standard. This error may occur when the SVRCOM library has been notified more than twice that the Tmax service has been started. It is likely that the existing server has not been terminated. This error basically cannot be raised, because the library is currently not available for external use. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_SVC_NOT_STARTED (-32112)
Description |
There is a problem related to the OpenFrame server coding standard. This error may occur when successor jobs are set to run without notifying the SVRCOM library that the Tmax service has been started. There is a high possibility that the existing server has not been terminated. This error basically cannot be raised, because the library is currently not available for external use. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SVRCOM_ERR_SYSTEM (-32201)
Description |
Failed to call a Unix function used in libsvrcom(). |
Action |
Check the error message log of the module and if it is a problem related to the Unix system, correct it. This error may be related to configuration settings for access authority, path, insufficient temporary space or swap space. |
Note |
SVRCOM_ERR_TPALLOC (-32300)
Description |
Failed to call the tpalloc() function to create Tmax buffers. |
Action |
Check the error log of the module and then contact the system administrator. |
Note |
Refer to the error message generated while processing the tpalloc() or fballoc() call, which are described in Tmax Reference Guide. |
SVRCOM_ERR_TPFREE (-32301)
Description |
Failed to call the tpfree() function to deallocate Tmax buffers. |
Action |
Check the error log of the module and then contact the system administrator. |
Note |
Refer to the error message generated while processing the tpfree() or fbfree() call, which are described in Tmax Reference Guide. |
SVRCOM_ERR_TPCALL (-32302)
Description |
Failed to call the Tmax tpcall() function. |
Action |
Check the error log of the module to determine whether the service successfully returned TPFAIL or has been abnormally terminated. |
Note |
Refer to the errors that occur while processing the tpcall() call, which is described in Tmax Reference Guide. |
SVRCOM_ERR_TPGETMYNODE (-32305)
Description |
Failed to call the Tmax tpgetmynode() function. |
Action |
Check the error log of the module and then contact the system administrator. |
Note |
Refer to Tmax Reference Guide. |
SVRCOM_ERR_FBPUT (-32310)
Description |
Failed to call the fbput() function to add a new field in the Tmax field buffer. |
Action |
Check the error log of the module and then contact the system administrator. |
Note |
Refer to Tmax FDL Reference Guide. |
SVRCOM_ERR_FBGET (-32311)
Description |
Failed to call the fbget() function to get the field value from the Tmax field buffer. |
Action |
Check the error log of the module and then contact the system administrator. |
Note |
Refer to Tmax FDL Reference Guide. |
SVRCOM_ERR_FBGETLEN (-32312)
Description |
Failed to call the fbgetlen() function to get the field length from the Tmax field buffer. |
Action |
Check the error log of the module and then contact the system administrator. |
Note |
Refer to Tmax FDL Reference Guide. |
SVRCOM_ERR_FIELD_NOT_FOUND (-32313)
Description |
The Tmax field key has not been defined in the ofb.fdl file. |
Action |
Check whether the FDLFILE contains the correct path to the ofb.fdl file and whether there are abnormal changes within the ofb.fdl file. If the file has been changed unexpectedly, reinstall the previous ofb.fdl file. |
Note |
Refer to OpenFrame Installation Guide and Tmax FDL Reference Guide. |
SVRCOM_ERR_FBNOENT (-32314)
Description |
The Tmax field key does not exist in the specified field buffer. |
Action |
If the field is not mandatory, this error message is returned as additional information. If the error causes the server to exit abnormally, it means that the Tmax server or client does not follow the API rules that the service expects. Request that the developer change the program. |
Note |
SVRCOM_ERR_TSAM_CONNECT (-32400)
Description |
Unable to connect to TSAM. |
Action |
Analyze the ulog of the server to identify the cause. This error may occur while using a DSIO or TSAM module. |
Note |
Refer to OpenFrame Data Set Guide. |
SVRCOM_ERR_TSAM_TXSTART (-32401)
Description |
Unable to start a TSAM transaction. |
Action |
Analyze the ulog of the server to identify the cause. This error may occur because of disconnection from TSAM. |
Note |
Refer to OpenFrame Data Set Guide. |
SVRCOM_ERR_TSAM_TXEND (-32410)
Description |
Unable to end a TSAM transaction. |
Action |
Analyze the ulog of the server to identify the cause. This error may occur because of disconnection from TSAM. |
Note |
Refer to OpenFrame Data Set Guide. |
SVRCOM_ERR_TSAM_TXCOMMIT (-32411)
Description |
Unable to commit a TSAM transaction. |
Action |
Analyze the ulog of the server to identify the cause. This error may occur because of disconnection from TSAM. |
Note |
Refer to OpenFrame Data Set Guide. |
SVRCOM_ERR_TSAM_TXROLL (-32412)
Description |
Unable to roll back a TSAM transaction. |
Action |
Analyze the ulog of the server to identify the cause. This error may occur because of disconnection from TSAM. |
Note |
Refer to OpenFrame Data Set Guide. |
SVRCOM_ERR_SYSTEM_STAT (-32991)
Description |
The stat() system function failed. |
Action |
Contact TmaxSoft Technical Support with the related server logs. |
Note |
SVRCOM_ERR_SYSTEM_FOPEN (-32992)
Description |
The fopen() system function failed. |
Action |
Contact TmaxSoft Technical Support with the related server logs. |
Note |
SVRCOM_ERR_SYSTEM_OPEN (-32993)
Description |
The open() system function failed. |
Action |
Contact TmaxSoft Technical Support with the related server logs. |
Note |
SVRCOM_ERR_SYSTEM_WRITE (-32994)
Description |
The write() system function failed. |
Action |
Contact TmaxSoft Technical Support with the related server logs. |
Note |
SVRCOM_ERR_SYSTEM_READ (-32995)
Description |
The read() system function failed. |
Action |
Contact TmaxSoft Technical Support with the related server logs. |
Note |
SVRCOM_ERR_SYSTEM_CLOSE (-32996)
Description |
The close() system function failed. |
Action |
Contact TmaxSoft Technical Support with the related server logs. |
Note |
24. CONSOLE (-34000)
The Console module is responsible for OpenFrame’s console function. This section lists the error codes that can occur in the Console module, descriptions of errors and suggested corrective actions.
CONSOLE_MALLOC_ERROR (-34010)
Description |
Failed to allocate system memory. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
Refer to the description for malloc() in the Unix Manual Page. |
CONSOLE_INVALID_REQUEST (-34011)
Description |
There is a problem with the data format of the console client (tconmgr or concli library). |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_INVALID_COMMAND (-34012)
Description |
An invalid value for the command server has been entered. |
Action |
Refer to the command types specified to the keys in the COMMAND section, from the console subject under OpenFrame Configuration, and contact TmaxSoft Technical Support. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
CONSOLE_INTERNAL_ERROR (-34014)
Description |
An internal error occurred. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_MSG_LEN_OVERFLOW (-34015)
Description |
The message length exceeds the maximum value of 4,096 bytes. |
Action |
Modify the application program to divide the message to send. |
Note |
CONSOLE_MSG_EMPTY (-34016)
Description |
An empty message has been sent while performing the DISPLAY command. |
Action |
Check the application. |
Note |
CONSOLE_INVALID_RECV_BUFFER (-34017)
Description |
There is a problem with the buffer while receiving a message via the ACCEPT command. |
Action |
Check the application. |
Note |
CONSOLE_CONFIG_ERROR (-34018)
Description |
There is a problem with an OpenFrame configuration file. |
Action |
Check the configuration settings in the sections of the ofsys or console subjects under OpenFrame Configuration, by referring the ofrcmsvr logs. |
Note |
For more information about the ofsys and console subjects under OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
CONSOLE_NOT_IN_CLI_LIST (-34021)
Description |
The ID of the client connecting to the console or command server is not found. |
Action |
Contact TmaxSoft Technical Support. |
Note |
CONSOLE_FILE_IO_ERROR (-34041)
Description |
Failed to call a Unix system function for file I/O. |
Action |
Refer to the ofrcmsvr logs. |
Note |
Refer to the description for open() and write() in the Unix Manual Page. |
CONSOLE_INVALID_FILE_DATA (-34042)
Description |
There is a problem with the console message file (CONSOLE_MSG_YYYYMMDD) data. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_INVALID_PARAM (-34051)
Description |
An invalid parameter has been entered in an internal program of the console. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPALLOC (-34052)
Description |
Failed to allocate Tmax memory from the console. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPGETCLID (-34053)
Description |
The Tmax API tpgetclid() failed from the console. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_DUPLICATE_CLID (-34054)
Description |
A duplicate client ID attempted to access the console server. This error occurs when a client ID has not been removed from the console server after an abnormal console shutdown. |
Action |
Restart the console server. |
Note |
CONSOLE_ERR_CLI_LIST_LOOKUP (-34055)
Description |
The client ID is not found in the console. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_INVALID_CLID (-34056)
Description |
An invalid client ID has been received from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_EMPTY_CLI_LIST (-34057)
Description |
The client list to delete from the console server is not found. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_CLID_NOT_FOUND (-34058)
Description |
The client ID to delete from the console server is not found. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_FBPUT (-34059)
Description |
The Tmax API fbput() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_SENDTOCLI (-34060)
Description |
The Tmax API tpsendtocli() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPCALL (-34061)
Description |
The Tmax API tpcall() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPSTART (-34062)
Description |
The Tmax API tpstart() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPSETUNSOL_FLAG (-34063)
Description |
The Tmax API tpsetunsol_flag() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPSETUNSOL (-34064)
Description |
The Tmax API tpsetunsol() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPRELAY (-34065)
Description |
The Tmax API tprelay() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_FBGET (-34066)
Description |
The Tmax API fbget() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPREALLOC (-34067)
Description |
The Tmax API tprealloc() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_NEED_RECOVERY (-34068)
Description |
An invalid token is found in the console, or the console server has been abnormally shut down. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPREGCB (-34069)
Description |
The Tmax API tpregcb() failed from the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_MSG_NOT_FOUND (-34070)
Description |
No message is found in the console or console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_MSG_MAX_COUNT (-34071)
Description |
The number of EXEC CICS WRITE OPERATOR CRITICAL commands to process in a COBOL application run from OpenFrame/OSC exceeds the maximum allowed count. |
Action |
Modify the value specified to the CRITICAL_MSG_MAX_COUNT key, in the CONSOLE section of the console subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
CONSOLE_ERR_INVALID_USER (-34072)
Description |
The client’s user information to delete from the console server is invalid. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_USER_NOT_FOUND (-34073)
Description |
The client with the user name to delete from the console server is not found. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_CLI_LIST_LOOKUP_BY_USER (-34074)
Description |
The client with the user name to search for is not found in the client list of the console server. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_TPGOTSIG (-34075)
Description |
A TPGOTSIG error occurred when the Tmax API tpcall() failed. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_NOT_SUPPORT (-34080)
Description |
The command type is not supported. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
CONSOLE_ERR_EXEC_COMMAND (-34081)
Description |
The command server failed to process a PGM command. |
Action |
Contact TmaxSoft Technical Support with the client and ofrcmsvr logs. |
Note |
25. SPIO (-36000)
The SPIO module is responsible for Spool data set management and I/O to the data set. This section lists the error codes that can occur in the SPIO module, descriptions of errors and suggested corrective actions.
SPIO_ERR_INVALID_REQUEST (-36001)
Description |
An SPIO library usage error (Invalid Request) occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SPIO_ERR_MEMORY_ALLOC (-36002)
Description |
Failed to allocate system memory. |
Action |
Contact the system administrator. |
Note |
SPIO_ERR_INTERNAL (-36003)
Description |
An internal error occurred in the SPIO library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SPIO_ERR_NOT_IMPLEMENTED (-36004)
Description |
A non-implemented function was called. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SPIO_ERR_NOT_ALLOWED (-36005)
Description |
An non-permitted mode is used. |
Action |
Check the error message. |
Note |
SPIO_ERR_END_OF_FILE (-36006)
Description |
The end of a file has been reached. |
Action |
Check the processing structure of the application. |
Note |
SPIO_ERR_MAX_FILES (-36101)
Description |
The maximum number of files that can be opened has been exceeded. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SPIO_ERR_INVALID_FD (-36102)
Description |
An invalid FD has been given. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SPIO_ERR_GET_RDW_FAIL (-36201)
Description |
The RDW information of a variable type data set is invalid. |
Action |
Check the error message. |
Note |
SPIO_ERR_PUT_RDW_FAIL (-36202)
Description |
The RDW information of a variable type data set is invalid. |
Action |
Check the error message. |
Note |
SPIO_ERR_INVALID_BUF_SIZE (-36203)
Description |
The record buffer size specified in an application program does not match with the actual data set length. |
Action |
Check the application program and the length of the data set. |
Note |
SPIO_ERR_SIZE_LIMIT_OVER (-36204)
Description |
The file size exceeds the maximum allowable value. |
Action |
Check the size of the file. |
Note |
SPIO_ERR_SYSTEM_OPEN (-36901)
Description |
Failed to call the open() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed system error message. |
SPIO_ERR_SYSTEM_READ (-36902)
Description |
Failed to call the read() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed system error message. |
SPIO_ERR_SYSTEM_WRITE (-36903)
Description |
Failed to call the write() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed system error message. |
SPIO_ERR_SYSTEM_CLOSE (-36904)
Description |
Failed to call the close() system function. |
Action |
Contact the system administrator. |
Note |
Refer to the displayed system error message. |
26. SMF (-93000)
The SMF module manages the OpenFrame SMF log. This section lists the error codes that can occur in the SMF module, descriptions of errors and suggested corrective actions.
SMF_ERR_INVALID_PARAM (-93001)
Description |
An invalid argument has been passed to an SMF service or library. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SMF_ERR_INTERNAL (-93002)
Description |
An internal SMFerror occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SMF_ERR_SYSTEM (-93003)
Description |
Failed to call a Unix system. |
Action |
Refer to the error logs of the module and check the system status. |
Note |
SMF_ERR_WRITE_LENGTH (-93100)
Description |
An invalid record length has been specified when writing to a data set in SMF. |
Action |
This error code is not currently used. |
Note |
SMF_ERR_DSN_NOMATCH (-93200)
Description |
The SMF data corresponding to the specified name is not found. |
Action |
Check the data set name again. The list of SMF data sets can be found using the smfmgr STATUS command. |
Note |
SMF_ERR_DS_INVALID_STATUS (-93210)
Description |
The SMF data set status is abnormal. |
Action |
Contact TmaxSoft Technical Support. |
Note |
SMF_ERR_DS_NOT_AVAILABLE (-93220)
Description |
There are are no more available SMF data sets. |
Action |
Check the data set status through smfmgr and secure an available data set. (use the DUMP function of IFSMFD.) |
Note |
SMF_ERR_TPALLOC (-93700)
Description |
Failed to call the Tmax tpalloc() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to the errors generated in tpalloc() or fballoc() in Tmax Reference Guide. |
SMF_ERR_TPCALL (-93702)
Description |
Failed to call the Tmax tpcall() function. |
Action |
Check the error logs of the module to determine whether the service that had generated the error returned TPFAIL normally or failed. |
Note |
Refer to the errors generated in tpcall() in Tmax Reference Guide. |
SMF_ERR_TPACALL (-93703)
Description |
Failed to call the Tmax tpacall() function. |
Action |
Check the error logs of the module to determine whether the service that had generated the error returned TPFAIL normally or failed. |
Note |
Refer to the errors generated in tpacall() in Tmax Reference Guide. |
SMF_ERR_FBPUT (-93710)
Description |
Failed to call the Tmax fbput() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax FDL Reference Guide. |
SMF_ERR_FBGET (-93711)
Description |
Failed to call the Tmax fbget() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax FDL Reference Guide. |
SMF_ERR_VERSION_MISMATCH (-93900)
Description |
The SMFINFO used in SMF is no longer compatible because of a version change. |
Action |
Restore the ofrsmlog and dump all SMF data sets through IFASFDP. Then, update SMF with the new version and initialize SMF. |
Note |