Chapter 9 - Messages

In the message descriptions below, the variable parts of the message text are marked within < and > bracket pairs.

Note: Only those messages with assigned message numbers are listed in this chapter. Not all messages have been assigned numbers at this time.

Message Index

TCS000I SERIALLY REUSABLE MODULE <module name> USED MORE THAN ONCE BY THE SAME TASK

The serially reusable load module is being accessed recursively. See ABEND code SA06.

TCS001I MODULE <module name> LOAD COUNT EXCEEDS 32767

The module load count is already 32767. See ABEND code S906 reason code 04.

TCS002I MODULE <module name> USE COUNT EXCEEDS 32767

The module use count is already 32767. See ABEND code S906 reason code 08.

TCS003I MODULE <module name> NOT FOUND [IN DATA SET <data set name> [<path name>: <reason>] ]

The load module was not found or could not be loaded. See ABEND code S806 reason code 04.

TCS004I BLDL FOR MODULE <module name> FAILED, I/O ERROR

An I/O error occurred while accessing the module directory. See ABEND code S806 reason code 08.

TCS005I BLDL FOR MODULE <module name> FAILED, DCB IS NOT OPEN

The LINK(X), LOAD or XCTL(X) DCB is not open. See ABEND code S806 reason code 0C.

TCS007I MODULE <module name> NOT LOADED TO ADDR, DCB REQUIRED

The LOAD service was requested with the ADDR parameter but without the DCB parameter. See ABEND code S806 reason code 10.

TCS008I MODULE <module name> NOT FOUND IN LPA

The XCTL(X) service was requested from a type 2, 3 or 4 SVC, however the requested module was not found in the Link Pack Area. See ABEND code S806 reason code 14.

TCS009I MODULE <module name> NOT ACCESSED, IS ONLY LOADABLE

The LINK(X) or XCTL(X) service was requested for a module that was linked as “only loadable”. Modules marked as “only loadable” may only be accessed via the LOAD service. See ABEND code S406.

TCS010I MODULE <module name> NOT LOADED, INVALID PARAMETER LIST

The LOAD service was requested with the EOM parameter but without the GLOBAL parameter or the ADDR parameter was specified with the GLOBAL or LOADPT parameters. See ABEND code S206 reason code 04.

TCS011I FETCH FAILED FOR MODULE <module name>: <reason>
TCS011I FETCH FAILED FOR MODULE <module name> FROM <dsn> PATH <path>

An error occurred while starting execution of a job step program or while attempting to load a module. See ABEND code S106.

TCS012I INVALID SYNCH(X) PARAMETER LIST

An unauthorized caller of the SYNCH(X) service specified the STATE, KEYADDR, KEYMASK or XMENV parameters or the XMENV parameter length was invalid. See ABEND code S206 reason code 10 or 1C.

TCS013I MODULE <module name> NOT LOADED TO GLOBAL, NOT IN APF LIBRARY

The LOAD service was requested with the GLOBAL parameter but the library containing the module was not APF authorized. See ABEND code S306 reason code 04.

TCS014I MODULE <module name> NOT LOADED TO GLOBAL, CALLER IS NOT AUTHORIZED

The LOAD service was requested with the GLOBAL parameter by an unauthorized caller. See ABEND code S206 reason code 08.

TCS015I MODULE <module name> NOT LOADED TO GLOBAL, NOT REENTRANT

The LOAD service was requested with the GLOBAL parameter but the module was not marked RENT. See ABEND code S306 reason code 08.

TCS017I MODULE <module name> NOT LOADED TO GLOBAL, ALREADY LOADED TO A DIFFERENT SUBPOOL

The LOAD service was requested with the GLOBAL parameter but the module was already loaded to private storage. See ABEND code SD06 reason code 04.

TCS018I MODULE <module name> NOT LOADED TO ADDR, CALLER IS NOT AUTHORIZED

The LOAD service was requested with the ADDR parameter by an unauthorized caller. See ABEND code S206 reason code 0C.

TCS019I MODULE <module name> NOT ACCESSED, NOT IN APF LIBRARY

The LINK(X), LOAD or XCTL(X) service was requested by an authorized caller, however the module is not in an APF authorized library. See ABEND code S206 reason code 0C.

TCS021I BLDL FOR MODULE <module name> FAILED, DCB IS INVALID

The LINK(X), LOAD or XCTL(X) DCB is not a valid or is not DSORG=PO. See ABEND code S806 reason code 1C.

TCS022I MODULE <module name> NOT LOADED TO ADDR, INVALID STORAGE ADDRESS

The LOAD service was requested with an invalid ADDR parameter value. See ABEND code S206 reason code 18.

TCS027I MODULE <module name> NOT ACCESSED, UNCONTAMINATED COPY NOT FOUND

The LINK(X), LOAD or XCTL(X) service was requested by an authorized caller, however the module was not marked as RENT and it was previously loaded by an unauthorized requester. See ABEND code S306 reason code 24.

TCS029I MODULE NOT ACCESSED, INVALID PARAMETER LIST

An attempt to invoke the LINK(X), LOAD, SYNCH(X) or XCTL(X) service failed because the parameter list was not accessible or was invalid. See ABEND code S206.

TCS030I XCTL TO MODULE <module name> FAILED, LINKAGE STACK NOT RESTORED

The XCTL(X) service was requested but the linkage stack was not restored. See ABEND code S906 reason code 0C.

TEA007I STATIC SYSTEM SYMBOLS:

This message is displayed in response to a DISPLAY SYMBOLS operator console command. The message is followed by a list of the static system symbols and their values.

TEA888I UTC DATE=<date>,CLOCK=<time> LOCAL DATE=<date>,CLOCK=<time>

The CLOCK parameter of the LOADxx.ini configuration file was specified. This message lists the altered date and time.

TEC015I A37-04 <ddname>, DCB IS NOT OPEN

The EOV or FEOV service was called for a DCB that was not open. See ABEND code SA37.

TEC020I 001-<reason code>,<ddname>,<reason>

An I/O error occurred. See ABEND code S001.

TEC024I 337-<reason code>,<ddname>,NO EODAD

An GET or READ was attempted after the last record of a data set was accessed or the FEOV service was called on the last data set in a concatenation but no End Of Data Exit Address (EODAD) was set in the DCB or DCBE. See ABEND code S337.

TEC025I 437-<reason code> <ddname>, <reason>

The EOV or FEOV service was called for an invalid DCB. See ABEND code S437.

TEC030I B37-04,<ddname>,DISK SPACE EXHAUSTED

An output operation was attempted on a disk data set but the file system is full. See ABEND code SB37.

TEC036I 002-<reason code>,<ddname>,<reason>

An I/O error occurred. See ABEND code S002.

TEC130I <ddname> DD STATEMENT MISSING

An attempt was made to open a DCB or ACB but there was no DD statement for the DDNAME in the DCB or ACB.

TEC138I 020-<reason code>,<ddname>,<reason>

The OPEN service failed for a DCB. See ABEND code S020.

TEC141I 013-<reason code>,<ddname>,<reason>

The OPEN service failed for a DCB. See ABEND code S013.

TEC142I 113-2C,<ddname>,DCB CANNOT BE USED TO OPEN A VSAM DATA SET

The OPEN service failed for a DCB. The DD statement refers to a VSAM file but a DCB was used instead of an ACB. See ABEND code S113.

TEC143I 213-<reason code>,<ddname>,<reason>

The OPEN service failed for a DCB. See ABEND code S213.

TEC150I 913-70,<ddname>,DCB=DSORG=PO REQUIRED FOR LOAD LIBRARY

An OPEN for a non-BPAM DCB was attempted for a simulated partitioned data set with FILEDATA(BINDER). See ABEND code S913.

TEC153I C13-10,<ddname>,OUTPUT DATA SETS CANNOT BE CONCATENATED

An OPEN for OUTPUT was attempted for a concatenated data set. See ABEND code SC13.

TEC155I 240-<reason code>,<ddname>,<reason>

The attempt to invoke the RDJFCB service failed because the JFCB or ARL entry in the DCB EXLST could not be accessed. See ABEND code S240.

TEC161I <code1>-<code2>,<ddname>,<reason>

The OPEN service failed for an ACB. One of the following error codes are associated with the message:

004-088

Either the data or index component file could not be opened. This message is preceded by the workstation file name and an explanation of the problem. The ACBERFLG field is set to X'84'.

016-002

MACRF=RLS was specified in the ACB. Record level sharing is not supported. The ACBERFLG field is set to X'A9'.

020-052

The request to allocate virtual storage for the buffers failed. The BUFND, BUFNI or BUFSP values may be too large. The ACBERFLG field is set to X'88'.

020-053

The request to allocate virtual storage for the control blocks failed. The ACBERFLG field is set to X'88'.

020-093

The request to allocate virtual storage for the DEB failed. The ACBERFLG field is set to X'88'.

032-003

The VSAM catalog information file does not exist. The ACBERFLG field is set to X'94'.

036-003

An I/O error was encountered while reading the catalog information file. This message is preceded by the workstation file name and an explanation of the problem. The ACBERFLG field is set to X'90'.

040-002

MACRF=OUT is not supported. The ACBERFLG field is set to X'98'.

041-151

The BUFSP value is too small. The ACBERFLG field is set to X'84'.

044-002

MACRF=UBF was specified with MACRF=ADR or MACRF=KEY. The ACBERFLG field is set to X'A0'.

047-002

MACRF=ICI was specified for a KSDS or VRRDS. The ACBERFLG field is set to X'A0'.

049-002

MACRF=ICI was specified for an empty data set. The ACBERFLG field is set to X'E0'.

054-002

MACRF=KEY was specified for an ESDS or LDS. The ACBERFLG field is set to X'A0'.

072-002

MACRF=IN was specified for an empty data set. The ACBERFLG field is set to X'A0'.

074-088

The data or index component file size does not match the information in the catalog file. The files may have been moved separately. The ACBERFLG field is set to X'BE'.

076-002

The DD statement refers to a non-VSAM file. An ACB can only be used with VSAM files. The ACBERFLG field is set to X'BC'.

079-002

The EXLST is invalid. The ACBERFLG field is set to X'BD'.

080-002

The STRNO is greater than 1 but the VSAM file is empty. The ACBERFLG field is set to X'A0'.

136-002

MACRF=LSR or MACRF=GSR was specified with MACRF=RST. The ACBERFLG field is set to X'A0'.

140-002

MACRF=LSR or MACRF=GSR was specified with MACRF=ICI. The ACBERFLG field is set to X'A0'.

144-002

MACRF=LSR or MACRF=GSR was specified with MACRF=UBF. The ACBERFLG field is set to X'A0'.

148-002

MACRF=GSR is not supported. The ACBERFLG field is set to X'CC'.

152-002

MACRF=LSR or MACRF=GSR was specified but the data set is empty. The ACBERFLG field is set to X'D4'.

231-053

There are more than 4096 open ACBs. The ACBERFLG field is set to X'E7'.

TEC190I <ddname>, DCB RESIDES ABOVE 16MB

The OPEN or RDJFCB service was called with a DCB address above 16 Megabytes.

TEC191I 50D-<reason code> INVALID PARAMETER LIST SUPPLIED TO {OPEN | RDJFCB} MACRO, ADDRESS=<address>

The OPEN or RDJFCB service was called with an invalid parameter list. See ABEND code S50D.

TEC290I <ddname>, DCB RESIDES ABOVE 16MB

The CLOSE service was called with a DCB address above 16 Megabytes.

TEC291I 50D-<reason code> INVALID PARAMETER LIST SUPPLIED TO CLOSE MACRO, ADDRESS=<address>

The CLOSE service was called with an invalid parameter list. See ABEND code S50D.

TEC908I 112-<reason code>,<reason>

The BLDL or FIND service was called with an invalid parameter list. See ABEND code S112.

TEE019I <command> REJECTED, QUOTE(S) MISSING

The operator console command contains unbalanced quotes.

TEE112I NO OUTSTANDING REPLIES OR RETAINED MESSAGES
TEE112I OUTSTANDING REPLIES AND RETAINED MESSAGES:
{<reply-id> | *} <message>

This message is displayed in response to a DISPLAY R operator console command. The first version of the message is displayed if there are no outstanding WTORs or action messages, otherwise the second version is displayed, followed by a list of the messages.

TEE153I <command> REJECTED, MORE THAN 126 CHARACTERS

The operator console command is too long.

TEE298I <command> REJECTED, INVALID CHARACTER: <character>

The operator console command contains an invalid character.

TEE309I <command> REJECTED, INVALID KEYWORD: <keyword>

The operator console command contains an invalid keyword.

TEE311I <command> REJECTED, PARAMETER MISSING

The operator console command does not include a required parameter.

TEE328I <command> ABORTED, OUT OF STORAGE

The operator console command could not be processed because the required storage was not available.

TEE341I <job name> NOT ACTIVE

The job referenced by the operator console command does not exist.

TEE342I <command> REJECTED, TASK BUSY

The maximum number of outstanding MODIFY commands (as set by the QEDIT service) have already been accepted or there is an outstanding STOP command.

TEE600I REPLY TO <reply number> IS: <reply>

The REPLY operator console command was accepted.

TEE700I REPLY <reply number> IGNORED, REPLY IS TOO LONG

The length of the REPLY operator console command was too long for the WTOR.

TEE704I REPLY <reply number> IS NOT OUTSTANDING

The reply identifier of the REPLY operator console command does not match any outstanding WTOR. You can use the DISPLAY R command to list the outstanding WTORs.

TEF000I JOB <job number> SUBMITTED

The job execution program (j390) was started without the -scan command line parameter. A job number has been assigned to the job.

TEF142I <job name> <step name> - STEP WAS EXECUTED - COND CODE <return code>

The job step completed normally.

TEF201I <job name> <step name> - JOB TERMINATED BECAUSE OF CONDITION CODES

The job step completion code matched a test of the COND parameter of the JOB statement.

TEF202I <job name> <step name> - NOT RUN BECAUSE OF { CONDITION CODES | COND=ONLY }

The job step was not run because of the the COND parameter of the EXEC statement.

TEF212I <job name> <step name> <ddname> - DATA SET NOT FOUND [PATH=<path>]

One of the following errors occurred:

1. The data set could not be mapped to a path name. No PATH parameter was specified on the DD statement and a matching DSNMAP statement did not exist in the DSNMAPxx.ini configuration file.
2. The disposition for the data set on the DD statement was OLD or SHR but the file does not exist.

TEF236I ALLOCATIONS FOR <job name> [<step name>]

Data set allocation information follows.

TEF237I { DMY | TRM | <subsystem> } ALLOCATED TO DDNAME <ddname>

The data set has been allocated.

TEF252I <job name> <step name> <ddname> - DUPLICATE NAME ON DIRECT ACCESS VOLUME PATH=<path>

The disposition for the data set on the DD statement was NEW but the file already exists.

TEF272I <job name> <step name> - STEP WAS NOT EXECUTED

The job step was not run because the job failed.

TEF283I <data set name> NOT DELETED, DDNAME=<ddname> PATH=<path> REASON=<reason>

During unallocation, the data set could not be deleted.

TEF285I <data set name> { SYSIN | SYSOUT }, DDNAME=<ddname>

The SYSIN or SYSOUT data set has been unallocated.

TEF373I STEP <step name> - START <date/time>

Execution of the job step has started.

TEF374I STEP <step name> - STOP <date/time> [ USER <user instruction count> SYS <system instruction count> INIT <initialization instruction count> ]

Execution of the job step has ended.

TEF375I JOB <job name> - START <date/time>

Execution of the job has started.

TEF376I JOB <job name> - STOP <date/time>

Execution of the job has ended.

TEF401I <job name> - ENDED - TIME=<time>

Execution of the job has ended.

TEF403I <job name> - STARTED - TIME=<time>

Execution of the job has started.

TEF450I <job name> <step name> - ABEND <abend code> REASON=<reason code>

The job step abnormally terminated. The abend code is printed either as Sxxx where xxx is the system abend code in hexadecimal or as Udddd where dddd is the abend code in decimal. The reason code is printed as 8 hexadecimal digits.

TEF452I <job name> NOT RUN - JCL ERROR

The JCL file contains syntax errors.

TEF453I <job name> FAILED - JCL ERROR

The job failed due to data set allocation errors.

TEF602I EXCESSIVE NUMBER OF EXECUTE STATEMENTS

There are more than 255 EXEC statements in the JOB.

TEF605I UNIDENTIFIED OPERATION FIELD

The JCL statement could not be identified as a JOB, EXEC, DD or null statement.

TEF606I MISPLACED DD STATEMENT

The DD statement precedes the JOB statement or a non-JOBLIB DD statement precedes the first EXEC statement.

TEF607I JOB HAS NO STEPS

The JOB does not contain any EXEC statements.

TEF608I { NO | <count> } ERRORS FOUND IN <file name>

The JOB statement contained a TYPERUN=SCAN parameter or the job execution program (j390) was started with the -scan command line parameter or the JCL file contained syntax errors.

TEF617I NO NAME OF FIRST DD STATEMENT AFTER EXEC STATEMENT

The first DD statement following a EXEC statement does not contain a name in the label field.

TEF621I EXPECTED CONTINUATION NOT RECEIVED

A JCL statement ended in a comma but either there were no more JCL statements or the following statement was not recognized as a valid continuation of the previous statement.

TEF622I UNBALANCED { LEFT | RIGHT } PARENTHESIS IN THE PARAMETER FIELD

The parameter field of a JCL statement contains an unbalanced left or right parenthesis.

TEF630I UNIDENTIFIED KEYWORD <keyword> { ON THE <type> STATEMENT | IN THE <name> FIELD }

The JCL statement contains an invalid or unsupported keyword.

TEF635I JOBNAME MISSING ON THE JOB STATEMENT

The JOB statement does not contain a name in the label field.

TEF636I MISPLACED JOBLIB DD STATEMENT

The JOBLIB DD statement must follow the JOB statement and precede the first EXEC statement.

TEF637I EXCESSIVE ACCOUNT FIELD LENGTH

The account parameter of a JOB or EXEC statement is too long.

TEF640I EXCESSIVE NUMBER OF POSITIONAL PARAMETERS ON THE <type> STATEMENT

The JCL statement contains too many positional parameters.

TEF642I EXCESSIVE PARAMETER LENGTH IN THE PROGRAMMER NAME FIELD

The programmer name parameter of a JOB statement is too long.

TEF643I UNIDENTIFIED POSITIONAL PARAMETER <parameter> ON THE DD STATEMENT

The DD statement contains an invalid positional parameter.

TEW2000S <ddname> COULD NOT BE OPENED, <reason>

The linkage editor could not be invoked because one or more of the data set attributes was invalid.

TEW2001S DD STATEMENT FOR <ddname> IS MISSING.

The linkage editor could not be invoked because a DD statement for SYSLIN or SYSPRINT was not specified.

TGD101I SMS ALLOCATED TO DDNAME <ddname> DSN=<data set name> PATH=<path> DATACLAS(<data class>) MGMTCLAS(<management class>) STORCLAS(<storage class>)

A new data set has been allocated.

TGD103I SMS ALLOCATED TO DDNAME <ddname>

An existing data set has been allocated.

TGD104I <data set name> RETAINED, DDNAME=<ddname>

The data set has been unallocated.

TGD105I { <data set name> | FILE } DELETED, DDNAME=<ddname> [PATH=<path>]

The data set has been unallocated and deleted.

TGD106I <data set name> PASSED, DDNAME=<ddname>

The data set has been passed to a subsequent step.

TGD107I <data set name> ROLLED IN, DDNAME=<ddname>

The generation data set has been unallocated and added to the generation data group.

TGD108I <data set name> CATALOGED, DDNAME=<ddname>

The data set has been unallocated. The disposition specified that the data set was to be cataloged.

TGD308I DATA SET ALLOCATION REQUEST FAILED FOR DDNAME=<ddname> PATH=<path> REASON=<reason>

The disposition for the data set was NEW or MOD, however the file could not be opened during allocation.

TGD0790I DELETION OF FILE FAILED, DDNAME=<ddname> PATH=<path> REASON=<reason>

During unallocation, the file could not be deleted.

TGD1750I ATTEMPT TO OPEN FILE FAILED FOR DDNAME=<ddname> PATH=<path> REASON=<reason>

PATHOPTS=OCREAT was specified for the file, however the file could not be opened during allocation.

TLC000S <product name> {demonstration license | license for <licensee>} has expired!

The license for this product has expired.

TLC001W <product name> {demonstration license | license for <licensee>} expires in <number> days.

The license for this product expires soon.

TLC002I <product name> is licensed to <licensee>.

This message is displayed for your information.

TLC003S The computer clock is not set correctly!

The computer clock is not set to a reasonable value.

TLC004S <product name> license information is invalid!

The license information for this product is corrupted.

TLC005I Please contact <vendor>

Please contact the product vendor for help with your license.

TLC006S <product name> license information was not found in <path name>

The license information was not found or is corrupted.

TLC007S Could not access file <path name>

The required Tachyon License Control file was not found or is corrupted.

TLC008S Could not allocate <number> bytes of memory!

Virtual memory on your workstation is full.

TLC009S Computer "<computer name>" is not licensed for <product name>!

The license information indicates that the product is not licensed for this computer.

TLC010I <product name> - version <version> <copyright notice>

This message is displayed for your information.

TLC011I [Demonstration] License expires on <date> at <time>

This message is displayed for your information.