OpenFrame/Batch Error Codes
This chapter describes the scope of error codes and individual errors associated with OpenFrame/Batch.
1. Overview
The following is an overview of the scope of error codes and associated modules in OpenFrame/Batch (hereafter Batch).
| Error Code Base | Module | Description |
|---|---|---|
-9000 |
Manages batch jobs. |
|
-13000 |
Manages creation/deletion/backup/recovery of spool. |
|
-16000 |
Processes JES commands. |
|
-92000 |
Manages TSO commands and command procedures. |
2. TJES (-9000)
The TJES module is responsible for managing Batch JOBs. This section lists the error codes that can occur in the TJES module, descriptions of errors and suggested corrective actions.
TJES_ERR_NOT_INITIALIZED (-9001)
Description |
The TJES library is used without having been initialized. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_NOT_CONNECTED (-9002)
Description |
An attempt was made to use a TSAM data set without being connected to TSAM. |
Action |
Check if TSAM is available. If no problem is found, contact TmaxSoft Technical Support. |
Note |
Refer to OpenFrame Data Set Guide. |
TJES_ERR_TX_NOT_STARTED (-9003)
Description |
An attempt was made to use the TSAM record I/O API without having started a TSAM transaction. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_TX_STARTED (-9004)
Description |
A repeated attempt was made to start a TSAM transaction that has already started. TJES can use a TSAM transaction only once. |
Action |
This error code is internally used as an additional information. |
Note |
TJES_ERR_TX_NOT_COMMITED (-9005)
Description |
A TSAM transaction was closed without being committed or rolled back. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_DS_NOT_ALLOC (-9010)
Description |
A data set used in TJES has not been allocated. |
Action |
Check whether the TJES system data set exists and verify the catalog information. |
Note |
TJES_ERR_DATA_NOT_FOUND (-9020)
Description |
The TJES entry to search for is not found in the system table. |
Action |
Check the TJES entry to search for in the system table. |
Note |
TJES_ERR_EOF (-9021)
Description |
The end of a file has been reached during sequential reading of an internal information used in TJES. |
Action |
This error code is internally used as an additional information. |
Note |
TJES_ERR_FILE_NOT_FOUND (-9030)
Description |
An internal file used in TJES such as spool is not found. |
Action |
Check the status of the disk in which the spool exists and check access permissions for the disk. |
Note |
TJES_ERR_TRY_AGAIN (-9040)
Description |
There is a failure implementing the TJES two-phase commit protocol logic. This error is not transmitted to external clients. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_RDB_DEPEND (-9050)
Description |
Failed to call an ODBC API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
TJES_ERR_PREPARE (-9051)
Description |
Failed to call SQLPrepare(), an ODBC-standard API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
TJES_ERR_EXECUTE (-9052)
Description |
Failed to call SQLExecute(), an ODBC-standard API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
TJES_ERR_BINDPARAM (-9053)
Description |
Failed to call SQLBindParameter(), an ODBC-standard API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
TJES_ERR_FETCH (-9054)
Description |
Failed to call SQLFetch(), an ODBC-standard API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
TJES_ERR_ODBC (-9060)
Description |
Failed to call an ODBC API function. |
Action |
Check the SQLSTATE and native error message. |
Note |
TJES_ERR_FAIL_OVER_RECONNECTED (-9061)
Description |
The DBMS server connected from the TJES library has been shut down, but a new connection is made 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 |
TJES_ERR_DUPLICATE_RECORD (-9062)
Description |
A duplicate TJES entry already exists in the system table. |
Action |
Ensure that there is no duplication. |
Note |
TJES_ERR_INVALID_JOBID (-9100)
Description |
The JOBID does not conform to the required format. The format of a JOBID is JOBnnnnn (where 0<n<9). |
Action |
Check whether the JOBID has been incorrectly defined when implementing tjesmgr. |
Note |
TJES_ERR_INVALID_JOBCLASS (-9101)
Description |
An invalid JOB CLASS has been specified. A valid JOB CLASS contains only alphanumeric characters. |
Action |
Check whether the JOB CLASS has been incorrectly specified in the JCL. |
Note |
TJES_ERR_INVALID_FLAG (-9102)
Description |
A function has an invalid flag set. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_INVALID_FD (-9103)
Description |
A required file hasn’t been opened at a certain point. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_INVALID_TOKEN (-9104)
Description |
a token used to update a data set is invalid. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_INVALID_POINTER (-9105)
Description |
A pointer that must not be null is set to null. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_INVALID_STATUS (-9106)
Description |
The JOB is in an unexpected state. For example, REMOVE can only be used for a JOB in DONE, ERROR, STOP or FLUSH state. |
Action |
Check whether the API can be called in the current job state. |
Note |
Refer to OpenFrame TJES Guide. |
TJES_ERR_INVALID_LICENSE (-9107)
Description |
The TJES license is invalid. |
Action |
Check the Batch license and then request a reissued license if necessary. |
Note |
TJES_ERR_INVALID_PARAM (-9108)
Description |
an invalid parameter has been passed when calling a function or service. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_INVALID_CONFIG (-9109)
Description |
A configuration value retrieved from a configuration file contains an invalid format or content. |
Action |
Check the configuration set in the sections of the tjes subject, under OpenFrame Configuration. |
Note |
For more information about the individual setting items of the tjes subject, refer to OpenFrame Configuration Guide. |
TJES_ERR_INVALID_LENGTH (-9110)
Description |
the length of a parameter exceeds the maximum parameter length defined in the data set definition. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_INVALID_INPUT (-9111)
Description |
A invalid input argument has been passed when calling a function or service. This is a TJES internal error. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_DUPLICATE_JOBNAME (-9200)
Description |
The JOBNAME is duplicated while scheduling a job. This error code is provided as an additional information. |
Action |
Check whether the VALUE of the DUPL_JOBNAME key has been specified as intended, in the SCHEDULING section of the tjes subject, under OpenFrame Configuration. If the VALUE has been modified, RELOAD must be executed through the ofconfig tool. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
TJES_ERR_JOB_NOT_FOUND (-9201)
Description |
No job meeting the specified conditions is found. This error code is provided as an additional information. |
Action |
Check whether the job exists. |
Note |
TJES_ERR_RUNNER_NOT_FOUND (-9210)
Description |
No runner meeting the specified conditions is found. |
Action |
Use the PSJCLRUN command of tjesmgr or the runner information in OpenFrame Manager, to check whether the runner’s index is available for use, or there is any runner that satisfies the conditions. |
Note |
TJES_ERR_RUNNER_NOT_READY (-9211)
Description |
The runner to assign a job is not in the active state. |
Action |
Use the PSJCLRUN command of tjesmgr or the runner information in OpenFrame Manager, to check the runner’s state. |
Note |
TJES_ERR_CLASS_NOT_FOUND (-9212)
Description |
The runner to assign a job is not compatible with the job class. This error may occur if a user modifies the job class or the runner class in between the scheduling of the job and the assignment of the job to the runner by OBMJINITRUN. |
Action |
Check the job class and the runner class. |
Note |
Refer to the information about the job scheduling policy in OpenFrame TJES Guide. |
TJES_ERR_NODE_NOT_BOOTED (-9220)
Description |
Unable to assign a job to a specific runner because the node contains the runner has not been started. This error may occur if a user closes the node in between the scheduling of the job and the assignment of the job to the runner by OBMJINITRUN. |
Action |
Check the node’s status by using the NODEST command of tjesmgr. |
Note |
"OpenFrame TJES 안내서"를 Note한다. |
TJES_ERR_NODE_MISMATCH (-9221)
Description |
The node name of the server processing the TJES service does not match with the expected node name. This error may occur in services that provides node-name based routing. |
Action |
Check the NODE, SERVICE and ROUTING sections in the Tmax configuration. |
Note |
Refer to Tmax Administrator’s Guide. |
TJES_ERR_NODE_NOT_FOUND (-9222)
Description |
A request has been reported from the obmjinit server to a node that the obmjschd server does not recognize. This is a TJES internal error. |
Action |
Check whether the Tmax configuration has been correctly defined for every node, since the obmjschd server monitors the nodes through Tmax configuration. |
Note |
Refer to Tmax Administrator’s Guide. |
TJES_ERR_DOMAIN_MISMATCH (-9223)
Description |
The domain name of the server processing the TJES service does not match with the expected domain name. |
Action |
Check the NODE section in the Tmax configuration. |
Note |
Refer to Tmax Administrator’s Guide. |
TJES_ERR_JOBQ_FULL (-9300)
Description |
No more JOBID can be assigned to a new job because there are no more JOBIDs remaining in the specified range. (TJES issues a unique JOBID for every incoming job in the specified range.) |
Action |
Delete an unused job from the job queue or remove jobs through spool backup and return the JOBID resource to TJES. |
Note |
Refer to OpenFrame TJES Guide. |
TJES_ERR_INTERNAL (-9301)
Description |
A TJES internal error occurred. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_RESOURCE_LIMIT (-9302)
Description |
On or more resources used in TJES have reached the limit. |
Action |
Check the TJES resource constraints. |
Note |
TJES_ERR_OUTPUTQ_FULL (-9304)
Description |
No more OUTPUTID can be assigned to a new output because there are no more OUTPUTIDs remaining in the specified range. (TJES issues a unique OUTPUTID for every output in the specified range.) |
Action |
Delete an unused output and return the OUTPUTID resource to TJES. |
Note |
Refer to OpenFrame TJES Guide. |
TJES_ERR_CREATE_FILE (-9305)
Description |
Failed to create a data file with the hdr extension. |
Action |
If there is an issue in the Unix system, correct it. There may be some problems related to access permissions, path, temporary space or swap space. |
Note |
TJES_ERR_COPY_ERROR (-9306)
Description |
Failed to write an output file. |
Action |
If there is an issue in the Unix system, correct it. There may be some problems related to access permissions, path, temporary space or swap space. |
Note |
TJES_ERR_UNLINK (-9307)
Description |
Failed to remove an output file. |
Action |
If there is an issue in the Unix system, correct it. There may be some problems related to access permissions or the path. |
Note |
TJES_ERR_JOBG_DELETED (-9400)
Description |
The job group has been deleted. (for XSP only) |
Action |
This error code is internally used as an additional information. |
Note |
TJES_ERR_JOBG_NOT_DELETED (-9401)
Description |
The job group has not been deleted. (for XSP only) |
Action |
This error code is internally used as an additional information. |
Note |
TJES_ERR_JOBG_DUPLICATED (-9402)
Description |
A duplicate job group with the same name already exists. (for XSP only) |
Action |
Use a different name for the job group. |
Note |
TJES_ERR_JOBG_NOT_FOUND (-9403)
Description |
The job group with the specified name is not found. (for XSP only) |
Action |
Check the job group name. |
Note |
TJES_ERR_SYSTEM (-9500)
Description |
Failed to call a Unix system function. |
Action |
Check the error message log of the module. If there is an issue in the Unix system, correct it. There may be some problems related to access permissions, path, temporary space or swap space. |
Note |
TJES_ERR_JOB_TIME_OVER (-9550)
Description |
The CPU time limit exceeded the TIME parameter value specified in the JOB statement, during the execution of the JOB. |
Action |
Contact the system administrator. This situation is intended rather than an error. |
Note |
TJES_ERR_EXEC_TIME_OVER (-9551)
Description |
The CPU time limit exceeded the TIME parameter value specified in the EXEC statement, during the execution of the JOB STEP. |
Action |
Contact the system administrator. This situation is intended rather than an error. |
Note |
TJES_ERR_NET_NOT_FOUND (-9610)
Description |
The JOBNET with the specified name is not found. (for VOS3 only) |
Action |
Check the JOBNET name. |
Note |
TJES_ERR_NETVER_MISMATCH (-9611)
Description |
The version of the JOBNET_INFO file does not match with that of the JOBNET_INFO to be used in TJES. |
Action |
Check the patch history. If necessary, use tjesinit to initialize the JOBNET information so that the versions match. |
Note |
TJES_ERR_NETJOB_NOT_FOUND (-9620)
Description |
The job with the specified name is not found in JOBNET. (for VOS3 only) |
Action |
Check the job name and whether the NET statement exists in the job. |
Note |
TJES_ERR_NETJOB_FULL (-9621)
Description |
The number of jobs assigned to a given JOBNET exceeded the limit and no more jobs can be added. (for VOS3 only) |
Action |
Split the JOBNET into two or more JOBNETs and connect them using the NETREL properties. |
Note |
TJES_ERR_NETJOB_DUPLICATED (-9622)
Description |
The job with the specified name already exists in the JOBNET. A duplicate job with the same name cannot be submitted. (Only for VOS3) |
Action |
Delete the job in JOBNET and submit the job again, if necessary. |
Note |
TJES_ERR_TPALLOC (-9700)
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 from the tpalloc() or fballoc() function, which are described in Tmax Reference Guide. |
TJES_ERR_TPFREE (-9701)
Description |
Failed to call the Tmax tpfree() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to the errors generated from the tpfree() or fbfree() function, which are described in Tmax Reference Guide. |
TJES_ERR_TPCALL (-9702)
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 generated from the tpcall() function, which is described in Tmax Reference Guide. |
TJES_ERR_TPREGCB (-9703)
Description |
Failed to call the Tmax tpregcb() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax Reference Guide. |
TJES_ERR_TPSCHEDULE (-9704)
Description |
Failed to call the Tmax tpschedule() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax Reference Guide. |
TJES_ERR_TPGETMYNODE (-9705)
Description |
Failed to call the Tmax tpgetmynode() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax Reference Guide. |
TJES_ERR_TMADMIN (-9706)
Description |
Failed to call the Tmax tmadmin() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax Reference Guide. |
TJES_ERR_TPGETACTIVESVR (-9707)
Description |
Failed to call the Tmax tpgetactivesvr() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax Reference Guide. |
TJES_ERR_TPACALL (-9708)
Description |
Failed to call the Tmax tpacall() 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 generated from the tpacall() function, which is described in Tmax Reference Guide. |
TJES_ERR_TPREALLOC (-9709)
Description |
Failed to call the Tmax tprealloc() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to the errors generated from the tprealloc() or fbrealloc() function, which are described in Tmax Reference Guide. |
TJES_ERR_FBPUT (-9710)
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. |
TJES_ERR_FBGET (-9711)
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. |
TJES_ERR_FBGETLEN (-9712)
Description |
Failed to call the Tmax fbgetlen() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module.. |
Note |
Refer to Tmax FDL Reference Guide. |
TJES_ERR_RCVBUF_NULL (-9713)
Description |
A Tmax service receives the TPSVCINFO struct to process a client’s request. Here, the buffer data requested by the client must be found in TPSVCINFO→DATA. This error occurs when this data does not exist. |
Action |
Check first whether the client’s request is valid, and then contact TmaxSoft Technical Support. |
Note |
Refer to Tmax Application Development Guide. |
TJES_ERR_TPSENDTOCLI (-9714)
Description |
Failed to call the Tmax tpsendtocli() function. |
Action |
Contact TmaxSoft Technical Support with the error log of the module. |
Note |
Refer to Tmax Reference Guide. |
TJES_ERR_JCL_PATH (-9800)
Description |
The JCL file path defined in the job submitted is not accessible. This error occurs when the JCL file does not exist, or the user does not have sufficient access rights for the file, or the JCL path that can be accessed only locally is transmitted via the obmjmsvr server in another node. |
Action |
Check whether the JCL file exists, sufficient access rights for the file have been granted, and the file can be accessed from every node. |
Note |
TJES_ERR_JCL_SYNTAX (-9801)
Description |
An error is detected in a submitted JCL statement. |
Action |
Revise the JCL and then resubmit it. |
Note |
TJES_ERR_NO_SUBM_TOKEN (-9900)
Description |
A TACF token has not been submitted with a request. |
Action |
Check the JCL path and the user who submitted the JCL. |
Note |
TJES_ERR_NO_SUBM_ACCOUNT (-9901)
Description |
The TACF token of the user who submitted a job is invalid. This error may occur when the ofrsasvr server was restarted. |
Action |
Log in to the system again to get a valid TACF token and then submit a job. |
Note |
TJES_ERR_NO_EXEC_ACCOUNT (-9902)
Description |
A TACF token cannot be generated with the user ID defined in a submitted JCL. |
Action |
Check whether the user ID and password defined in the JCL are valid. |
Note |
TJES_ERR_SURROGATE_DENIED (-9903)
Description |
A surrogate user who submitted a job under the user ID without specifying the password in the JCL has no surrogate authority. |
Action |
Ensure that the job is submitted by a submitter with surrogate authority, or grant the authority to the submitter who failed to submit the job. |
Note |
Refer to OpenFrame TACF Administrator’s Guide. |
TJES_ERR_ELEM_IS_NULL (-9950)
Description |
No element is found in obmjtimr. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TJES_ERR_DUP_ELEM (-9951)
Description |
Failed to delete duplicate elements in obmjtimr. |
Action |
Contact TmaxSoft Technical Support. |
Note |
3. SPOOL (-13000)
The SPOOL module is responsible for creating, deleting, backing up, and recovering SPOOL data sets. This section lists the error codes that can occur in the SPOOL module, descriptions of errors and suggested corrective actions.
SPOOL_ERR_MALLOC (-13001)
Description |
Failed to allocate system memory. |
Action |
Check whether the system has sufficient available memory, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_SYSTEM (-13002)
Description |
Failed to call the system() function. |
Action |
Check whether too many processes are running at once. |
Note |
SPOOL_ERR_OPEN (-13011)
Description |
Failed to open a file. |
Action |
Check whether the file exists, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_READ (-13012)
Description |
Failed to read a file. |
Action |
Check access rights for the file, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_WRITE (-13013)
Description |
Failed to write a file. |
Action |
Check access rights for the file, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_UNLINK (-13014)
Description |
Failed to delete a file. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_LOCK (-13015)
Description |
Failed to lock a file. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_UNLOCK (-13016)
Description |
Failed to unlock a file. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_LSEEK (-13017)
Description |
Failed to call the lseek() system function. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_STAT (-13018)
Description |
Failed to call the stat() system function. |
Action |
Check whether the file or directory exists, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_CHMOD (-13019)
Description |
Failed to call the chmod() system function. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_OPEN_DIRECTORY (-13021)
Description |
Failed to open a directory. |
Action |
Check whether the directory exists, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_MAKE_DIRECTORY (-13022)
Description |
Failed to create a directory. |
Action |
Check whether a file with the same name exists, and refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_REMOVE_DIRECTORY (-13023)
Description |
Failed to delete a directory. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_GET_WORKING_DIR (-13024)
Description |
Failed to get the current working directory. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_CHANGE_WORKING_DIR (-13025)
Description |
Failed to change the working directory. |
Action |
Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_ERR_BUFLEN (-13101)
Description |
The buffer length has been set below specification. |
Action |
Patching is needed. |
Note |
SPOOL_ERR_SYSOUT_LIMIT (-13102)
Description |
The number of spool data sets exceeded 512. |
Action |
Adjust the number of SYSOUT in the JCL. |
Note |
SPOOL_ERR_INVALID_INPUT (-13103)
Description |
The input parameter value for the API is null. |
Action |
Check whether a memory failure occurred in the process. Refer to the error log to determine the cause and take the necessary action. |
Note |
SPOOL_INVALID_CONFIG (-13104)
Description |
Failed to retrieve data from OpenFrame Configuration. |
Action |
Check the logs to verify whether the relevant items have been correctly set under OpenFrame Configuration. |
Note |
4. MVSSYS (-16000)
The MVSSYS module is responsible for processing JES commands. This section lists the error codes that can occur in the MVSSYS module, descriptions of errors and suggested corrective actions.
MVSSYS_ERR_INVALID_COMMAND (-16001)
Description |
The syntax format of a MVS system command parameter is not valid. |
Action |
Check the specified MVS system command parameter. |
Note |
MVS system command syntax is as follows:
|
MVSSYS_ERR_EXECUTE_FAILURE (-16002)
Description |
The MVS system command has not been successfully executed. |
Action |
Check the error logs for the MVS system commands. |
Note |
MVSSYS_ERR_CMD_NOT_SUPPORTED (-16003)
Description |
The MVS system command has been specified with an unsupported or incorrect format |
Action |
Check the MVS system command. |
Note |
|
5. TSO (-92000)
The Time Sharing Option (TSO) module is responsible for various jobs such as terminal I/O, data sets management and COBOL programs execution performed by the user through TSO commands and command procedure statements. This section lists the error codes that can occur in the TSO module, descriptions of errors and suggested corrective actions.
TSO_ERR_INVALID_REQUEST (-92001)
Description |
An invalid parameter has been passed when using an API of the TSO library directly. |
Action |
Specify a valid parameter for the job to perform when using an API directly. Otherwise, refer to the error message and contact TmaxSoft Technical Support. |
Note |
TSO_ERR_MEMORY_ALLOC (-92002)
Description |
Failed to allocate system memory. |
Action |
Refer to the error message and contact the system administrator. |
Note |
TSO_ERR_INTERNAL (-92003)
Description |
An internal error occurred in the TSO module. |
Action |
Refer to the error message and contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_IMPLEMENTED (-92004)
Description |
A currently unsupported function was used. |
Action |
Modify the CLIST so that the unsupported function is not used. If unable to modify the CLIST, contact TmaxSoft Technical Support. |
Note |
TSO_ERR_MAX_TSOID (-92005)
Description |
The number of TSO users exceeded the VALUE of the MAX_TSO_COUNT key, in the TSOMGR section of the tso subject under OpenFrame Configuration. |
Action |
Modify the VALUE of the MAX_TSO_COUNT key, in the TSOMGR section of the tso subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
TSO_ERR_NOT_DEFINED_SPOOLPATH (-92006)
Description |
The SPOOL path has not been defined. |
Action |
Contact the system administrator. |
Note |
TSO_ERR_NOT_DEFINED_SYSMSGPATH (-92007)
Description |
The SYSMSG path has not been defined. |
Action |
Contact the system administrator. |
Note |
TSO_ERR_NOT_FOUND_ENTRY (-92008)
Description |
The entry to search for is not found. |
Action |
Contact the system administrator. |
Note |
TSO_ERR_NOT_SUPPORTED (-92009)
Description |
A currently unsupported function was used or the command has been specified with an invalid format. |
Action |
Modify the CLIST so that the unsupported function is not used. If unable to modify the CLIST, contact TmaxSoft Technical Support. |
Note |
TSO_ERR_INVALID_MAP_VERSION (-92010)
Description |
The version of the MAP file in use is invalid. |
Action |
Recompile the MAP file. |
Note |
TSO_ERR_USERID_NOT_DEFINED (-92011)
Description |
The user ID has not been defined. |
Action |
Contact the system administrator. |
Note |
TSO_ERR_PASSWORD_NOT_DEFINED (-92012)
Description |
The password of the user ID has not been defined. |
Action |
Contact the system administrator. |
Note |
TSO_ERR_NOT_LOGON (-92013)
Description |
The user has not logged into the system. |
Action |
Log into the TSO system in a valid way. |
Note |
TSO_ERR_REQUIRE_USERID (-92014)
Description |
An attempt was made to log in without entering the user ID on the login screen of the system. |
Action |
Enter the user ID correctly on the login screen to log into the system. |
Note |
TSO_ERR_REQUIRE_PASSWD (-92015)
Description |
An attempt was made to log in without entering the password on the login screen of the system. |
Action |
Enter the password correctly on the login screen to log into the system. |
Note |
TSO_ERR_WRONG_USERID_PASSWD (-92017)
Description |
An attempt was made to log in by entering an incorrect password on the login screen of the system. |
Action |
Enter a correct password on the login screen to log into the system. |
Note |
TSO_ERR_LOGOUT (-92018)
Description |
The user has logged out. |
Action |
If the logout process has not been performed correctly through the TSO command, contact TmaxSoft Technical Support. |
Note |
TSO_ERR_SCREEN_READY (-92019)
Description |
The specified function key has returned to its original position to display the Ready screen. |
Action |
If the Ready screen is not displayed in a valid way through the TSO command, contact TmaxSoft Technical Support. |
Note |
TSO_ERR_MAX_JCLPATH_COUNT (-92021)
Description |
Too many JCL file paths have been specified. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_JCLPATH_NOT_FOUND (-92022)
Description |
Unable to access the JCL file path. This error occurs either because the JCL file does not exist or there is no access right for the file. |
Action |
Check whether the JCL file exist and access rights have been granted. |
Note |
TSO_ERR_INVALID_DSNAME (-92031)
Description |
The data set name is invalid. |
Action |
Check whether the data set name has been correctly specified. |
Note |
TSO_ERR_DSHANDLE_NOT_FOUND (-92032)
Description |
The DS handle specified as parameter is not found. |
Action |
Check if the DS handle is correctly passed when calling an API function. |
Note |
TSO_ERR_OCENT_NOT_FOUND (-92033)
Description |
The output control entry is not found. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_INVALID_DD_HANDLE (-92034)
Description |
The DD handle specified as parameter is not found. |
Action |
Check if the DD handle is correctly passed when calling an API function. |
Note |
TSO_ERR_DUPLICATE_DD (-92035)
Description |
A duplicate DD entry with the same name exists in the JCL or CLIST. |
Action |
Check the DD name. |
Note |
TSO_ERR_CANCEL_EXPECTED_JOBID (-92041)
Description |
When a duplicate job with the same JOBNAME exists in the system, the job has been performed without JOBID while executing the TSO CANCEL command with the JOBNAME specified as a parameter. |
Action |
Enter the JOBID when executing the TSO CANCEL command. |
Note |
TSO_ERR_NOT_SHARED_OBJECT (-92042)
Description |
The file to call is not a dynamic library. |
Action |
Check whether a correct file has been specified. |
Note |
TSO_ERR_INFINITE_CALL (-92043)
Description |
A COBOL application repeatedly calls the IPF subroutine. |
Action |
Check the application behavior or contact the system administrator. |
Note |
TSO_ERR_SYSCALL_OPEN (-92051)
Description |
Failed to call the fopen() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_SYSCALL_LOCKF (-92052)
Description |
Failed to call the lockf() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_SYSCALL_OPENDIR (-92053)
Description |
Failed to call the opendir() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_SYSCALL_PUTENV (-92054)
Description |
Failed to call the putenv() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_SYSCALL_MALLOC (-92055)
Description |
Failed to call the calloc() or malloc() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_SYSCALL_STAT (-92056)
Description |
Failed to call the stat() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_SYSCALL_MKSTEMP (-92057)
Description |
Failed to call the mkstemp() system function. |
Action |
Refer to the displayed error message and contact the system administrator. |
Note |
TSO_ERR_NOT_FOUND_TSOID (-92061)
Description |
Unable to find the TSO ID in the TSO system. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_FOUND_CLNTID (-92062)
Description |
Unable to find the client ID in the TSO system. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_FOUND_TSOSEQ (-92063)
Description |
Unable to find the TSO sequence in the TSO system. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_FOUND_RUNPID (-92064)
Description |
Unable to find the process ID in the TSO system. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_FOUND_CLNTLU (-92065)
Description |
Unable to find the client LU in the TSO system. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_FOUND_MAPFILE (-92067)
Description |
Unable to access the path to the TSO MAP file. |
Action |
Check whether the TSO MAP file exists. |
Note |
TSO_ERR_NOT_FOUND_JOBID (-92068)
Description |
Unable to find the job ID in the TSO system. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_NOT_FOUND_PROCFILE (-92069)
Description |
Unable to find the default procedure in the TSO system. |
Action |
Specify a correct procedure to the VALUE of the DEFAULT_PROC key, in the TSOMGR section of the tso subject under OpenFrame Configuration. |
Note |
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide. |
TSO_ERR_NOT_INITIALIZED (-92071)
Description |
The TSO system has not been initialized. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_INVALID_CONFIG (-92093)
Description |
OpenFrame configuration values have not been retrieved correctly. |
Action |
Check the configuration values and correct the error. |
Note |
TSO_ERR_INVALID_PARAM (-92095)
Description |
The parameter is invalid. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPALLOC (-92300)
Description |
The tpalloc() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPFREE (-92301)
Description |
The tpfree() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPCALL (-92302)
Description |
The tpcall() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPREGCB (-92303)
Description |
The tpregcb() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPSCHEDULE (-92304)
Description |
The tpschedule() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPGETMYNODE (-92305)
Description |
The tpgetmynode() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TMADMIN (-92306)
Description |
The tmadmin() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPGETACTIVESVR (-92307)
Description |
The tpgetactivesvr() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPACALL (-92308)
Description |
The tpacall() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPREALLOC (-92309)
Description |
The tprealloc() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_TPRELAY (-92310)
Description |
The tprelay() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FBPUT (-92320)
Description |
The fbput() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FBGET (-92321)
Description |
The fbget() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FBGETLEN (-92322)
Description |
The fbgetlen() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_SYSTEM (-92500)
Description |
The system() function failed. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FTP_PARSING_ERROR (-92600)
Description |
The TSO FTP command has been incorrectly parsed. |
Action |
Check the syntax of the TSO FTP command and correct the error. |
Note |
TSO_ERR_FTP_TRANSALTE_EROR (-92601)
Description |
The header of the TSO FTP command has been processed incorrectly. |
Action |
Check the log message and contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FTP_EXEC_ERROR (-92602)
Description |
The TSO FTP command has been executed incorrectly. |
Action |
Check the log message and contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FTP_RECV_COPY_ERROR (-92603)
Description |
The files transferred through the TSO FTP command have been processed incorrectly. |
Action |
Check the log message and contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FTP_RECV_INVALI_LRECL (-92604)
Description |
The record length of a file received through the TSO FTP command is invalid. |
Action |
Check the length of both the received file and data set to bring them to match each other. |
Note |
TSO_ERR_FTP_UNSUPPORTED_CMD (-92605)
Description |
An FTP command that is not supported in TSO has been specified. |
Action |
If the command is needed to be supported, contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FTP_NOT_NONVSAM (-92606)
Description |
A data set that is not supported by the TSO FTP command is used. |
Action |
Contact TmaxSoft Technical Support. |
Note |
TSO_ERR_FTP_ACCNT_ERROR (-92607)
Description |
The user name and password required for processing the TSO FTP command have not been specified. |
Action |
Specify the user name and password. |
Note |