gtpm5m2jMessages (Online)

TCTL-TRCC

TCTL0001Ename tapename address CCcode CCW-command CSW-word SNS-dat

Where:

name
Subsystem user name or Basic subsystem (BSS) name.

tapename
Symbolic tape name (for example, RTL).

address
The device address.
Note:
Where two paths are defined for the drive, the address given is that used for the failing operation.

code
SIO condition code. When a deferred SIOF condition code occurs the deferred condition code is given.

command
The channel command that was not successful.
Note:
When a data chained channel program specified through the TDCTC macro fails, the operation code given is that of the first CCW in the chain.

word
Channel status word. This is the CSW associated with the error.
Note:
For SIO condition code 3 (not operational), the CSW is not meaningful and is not included in the message.

data
Sense data. The sense data is only included in the message for unit-check conditions. The number of sense bytes displayed is dependent on the device type. There are 24 bytes displayed for the IBM 3400 series tape drives.

If an input/output (I/O) error prevents the successful sensing of the device, the UNABLE word is displayed in place of the sense data.

Explanation: None.

System Action: None.

User Response: None.

TERM0000EINVALID INPUT

Explanation: The ZTERM command was entered an input that is not valid.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTERM command.

TERM0001EINVALID LNIATA

Explanation: The ZTERM command was entered with an address that is not valid.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTERM command.

TFTP0001ETFTP DETECTED AN ERROR ON LINE line OF CONFIGURATION FILE file: desc

Where:

line
The line number in the Trivial File Transfer Protocol (TFTP) configuration file where the error was detected.

file
The name of the TFTP configuration file (/etc/tftp.conf).

desc
A description of why the line is not valid.

Explanation: The TFTP server attempted to configure itself using the directives in the configuration file, but found a directive that is not valid on the line specified in the message.

System Action: The TFTP server ignores the directive. If no valid directive is found, the TFTP server uses the default value.

User Response: Edit the configuration file and correct the directive that is not valid.

See TPF Transmission Control Protocol/Internet Protocol for more information about the TFTP configuration file.

TFTP0002ETFTP WAS UNABLE TO ACCESS CONFIGURATION FILE file: desc

Where:

file
The name of the Trivial File Transfer Protocol (TFTP) configuration file (/etc/tftp.conf).

desc
A description of the error that was found.

Explanation: The TFTP server attempted to configure itself, but was unable to access the configuration file. This will happen, for example, if TFTP is not authorized to read the configuration file.

System Action: The TFTP server continues to use the default configuration. The default settings deny access to all files, so the transfer is denied.

User Response: Ensure the configuration file is available and that the TFTP server is authorized to read the file.

See TPF Transmission Control Protocol/Internet Protocol for more information about the TFTP configuration file.

TMSL0002IEXISTING TIME-SLICE NAMES value name

Where:

value
ON FILE or IN CORE.

name
The time-slice name found in the time-slice name table. Additional time-slice names may follow.

Explanation: This is the normal response to the ZTMSL command with the DISPLAY parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTMSL command and for an example of the informational display.

TMSL0003ITIME SLICE ATTRIBUTES FOR NAME name value

Where:

name
The time-slice name.

value
ON FILE or IN CORE.

Explanation: This is the normal response to the ZTMSL command with the DISPLAY parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTMSL command and for an example of the informational display.

TMSL0004INEW TIME SLICE ATTRIBUTES FOR NAME name value

Where:

name
The time-slice name.

value
ON FILE or IN CORE.

Explanation: This is the normal response to the ZTMSL command with the ADD parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTMSL command.

TMSL0005IOLD TIME SLICE ATTRIBUTES FOR NAME name value

Where:

name
The time-slice name.

value
ON FILE or IN CORE.

Explanation: This is the normal response to the ZTMSL command with the CHANGE parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTMSL command and for an example of the informational display.

TMSL0006EERROR READING OR WRITING TIME-SLICE NAME RECORD

Explanation: The time-slice name table (file copy) cannot be read or written to file.

System Action: The ZTMSL command is rejected. A system error dump is issued.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Correct the error.
  3. Ensure that the file copy contains the appropriate time-slice names and attributes.

See TPF Operations for more information about the ZTMSL command.

TMSL0007EPARAMETER SPECIFIED IS NOT VALID

Explanation: The ZTMSL command was not specified with the correct positional parameters and keywords.

System Action: The ZTMSL command is rejected.

User Response: Do the following:

  1. Determine the correct format of the ZTMSL command.
  2. Enter the ZTMSL command again by using the correct format.

See TPF Operations for more information about the ZTMSL command.

TMSL0008EVALUE OUT OF RANGE

Explanation: The ZTMSL command was entered and one of the following errors occurred:

System Action: The ZTMSL command is rejected.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Correct the error.
  3. Enter the ZTMSL command again and specify a valid value.

See TPF Operations for more information about the ZTMSL command.

TMSL0009ETIME-SLICE NAME NOT FOUND value

Where:

value
ON FILE or IN CORE.

Explanation: The name specified does not exist in the time-slice name table.

System Action: The ZTMSL command is rejected.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZTMSL command again and specify a valid time slice name.

See TPF Operations for more information about the ZTMSL command.

TMSL0010ITIME-SLICE NAME name HAS BEEN REMOVED value

Where:

name
The time-slice name.

value
ON FILE or IN CORE.

Explanation: The time-slice name specified has been removed. If this operation was performed on the core copy of the time-slice name table, the entry that contains this name is set to NOT VALID. This entry cannot be used again until the next initial program load (IPL).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTMSL command.

TMSL0011ENO SPACE AVAILABLE IN THE TIME SLICE NAME TABLE value

Where:

value
ON FILE or IN CORE.

Explanation: The time-slice name table is full. You cannot add an additional time-slice name.

System Action: The ZTMSL command ends.

User Response: Do one of the following:

See TPF Operations for more information about the ZTMSL command.

TMSL0013ETIME-SLICE NAME ALREADY EXISTS value

Where:

value
ON FILE or IN CORE.

Explanation: The time-slice name specified on the ZTMSL command already exists.

System Action: The ZTMSL command is rejected.

User Response: Do the following:

  1. Determine whether the time-slice name specified is correct.
  2. Enter the ZTMSL command again and specify a valid time-slice name.

See TPF Operations for more information about the ZTMSL command.

TMSL0014ECORE COPY OPERATION NOT VALID DURING RESTART

Explanation: The ZTMSL command was entered with the CORE COPY parameter specified while the TPF system is in restart.

System Action: The ZTMSL command ends.

User Response: Do one of the following:

See TPF Operations for more information about the ZTMSL command.

TMSL0015ECOPY PARAMETER SPECIFIED IS NOT VALID

Explanation: The format of the ZTMSL command is not correct.

System Action: The ZTMSL command is rejected.

User Response: Do the following:

  1. Determine the correct format of the ZTMSL command.
  2. Enter the ZTMSL command again by using the correct format.

See TPF Operations for more information about the ZTMSL command.

TPLD0001ISTARTING LOAD TO IMAGE imagename FROM DDNAME name

Where:

imagename
A 5 to 8 character image name.

name
A 1 to 16 character alphanumeric data definition name of the input device (general data set (GDS), tape, virtual reader, or user-define device) that contains the program data.

Explanation: Auxiliary loader processing is starting for the image and data definition referenced in the message.

System Action: Processing is continued.

User Response: None.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0002Inamecode LOADED

Where:

name
The component name.

code
The version code.

Explanation: The specified component was loaded successfully.

System Action: Processing is continued.

User Response: None.

See TPF System Installation Support Reference for more information.

TPLD0003Inumber E-TYPE PROGRAMS LOADED

Where:

number
The number of E-type programs loaded.

Explanation: The specified number of E-type programs were loaded successfully.

System Action: Processing continues.

User Response: None.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0004ILOAD COMPLETE

Explanation: The auxiliary loader processing completed successfully.

System Action: None.

User Response: If the input file contained all of the necessary program components, you can now use the ZIMAG ENABLE command to enable the newly-loaded image to be used.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0099IZTPLD imagename name

Where:

imagename
A 5 to 8 character image name.

name
A 1 to 16 character alphanumeric data definition name of the input device (general data set (GDS), tape, virtual reader, or user-define device) that contains the program data.

Explanation: The help menu requested for the ZTPLD command is displayed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0101EREQUEST REJECTED - IMAGE imagename IS ENABLED

Where:

imagename
The image name.

Explanation: The image referenced in the message is enabled. Therefore, programs cannot be loaded to it.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0102EREQUEST REJECTED - IMAGE imagename IS NOT DEFINED

Where:

imagename
The image name.

Explanation: The ZTPLD command was entered with an image name specified that is not defined.

System Action: The ZTPLD command is rejected.

User Response: Enter the ZTPLD command again specifying the name of a defined image.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0103EREQUEST REJECTED -- DDNAME name CANNOT BE OPENED

Where:

name
A 1 to 16 character alphanumeric data definition name of the input device (general data set (GDS), tape, virtual reader, or user-define device) that contains the program data.

Explanation: The ZTPLD command was entered with a tape name, GDS name, virtual reader name, or user-defined media that cannot be opened.

This message is preceded by other messages that provide further details about why the tape name, TDS name, VRDR name, or user-defined media cannot be opened.

System Action: The ZTPLD command is rejected.

User Response: Refer to the previous messages for more information about correcting this error.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0104EREQUEST REJECTED -- IPL AREA IN USE

Explanation: The initial program load (IPL) area defined to the specified image is in use by another enabled image.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0105EREQUEST REJECTED -- PROG AREA IN USE

Explanation: The program area defined to the specified image is in use by another enabled image.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0106EREQUEST ABORTED

Explanation: An error occurred during auxiliary loader processing.

System Action: Auxiliary load processing is ended.

User Response: This message is preceded by other messages that provide further details about the type of error that occurred. Refer to the explanation of those messages to determine the appropriate action.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0107EREQUEST REJECTED -- ADDRESS MISMATCH FOR THE FOLLOWING COMPONENTS name

Where:

name
The component name, which is one of the following:

Explanation: The address saved in the image control record for the listed areas does not match the address obtained online from FACS.

System Action: The auxiliary load processing is ended.

User Response: Do the following:

  1. Use the ZIMAG CLEAR and ZIMAG DEFINE commands to reinitialize
  2. Load all components.

Otherwise, correct the file address computer program (FACE) table (FCTB) and enter the request again.

See TPF Operations for more information about the ZTPLD, ZIMAG CLEAR, and ZIMAG DEFINE commands. See TPF System Installation Support Reference for more information.

TPLD0108EREQUEST REJECTED -- LOAD NOT FOR CORRECT SUBSYSTEM

Explanation: The input file was generated for a subsystem other than from where the ZTPLD command was entered.

System Action: Auxiliary load processing is ended.

User Response: Enter the ZTPLD command again from the correct subsystem.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0109EREQUEST ABORTED COMPONENT name IS TOO LARGE FOR TARGET IMAGE DEFINED SIZE - size1 ACTUAL SIZE - size2

Where:

name
The name of the CIMR component that is larger on the input file than that defined in the image CTKX record.

size1
The defined size of the component in the CTKX record.

size2
The actual size of the component on the input file.

Explanation: The load request was not processed because a component in the input file is larger than the area defined for the component in the image CTKX record.

System Action: The auxiliary load processing is ended.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0110WINVALID KEYPT keypoint FOR THIS SUBSYSTEM

Where:

keypoint
The name of the keypoint that resides only in the basic subsystem (BSS).

Explanation: The input file contains a BSS-only keypoint record, while the auxiliary loader is running for a non-BSS subsystem.

System Action: The keypoint record is ignored and processing is continued.

User Response: Do not include the specified keypoint in the input deck when running the offline job (TLDR) for a non-BSS subsystem.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0111EREQUEST ABORTED -- CTKX MUST BE LOADED FIRST

Explanation: One of the following errors occurred:

System Action: The auxiliary load processing is ended.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD and ZIMAG COPY commands. See TPF System Installation Support Reference for more information.

TPLD0114EREQUEST ABORTED -- EXPECTED ITEM NOT FOUND IN INPUT FILE PREMATURE EOF WHILE READING DDNAME name

Where:

name
A 1 to 16 character alphanumeric data definition name of the input device (general data set (GDS), tape, virtual reader, or user-define device) that contains the program data.

Explanation: The auxiliary loader expected to read additional records from the input file but the end of the input file occurred prematurely.

System Action: A system error dump is issued and load processing is ended.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0115WE-TYPE LOADER CONTROL RECORDS NOT AFFECTED BY LOAD

Explanation: This message is issued only when E-type programs are loaded by the auxiliary loader. The E-type loader control records were not cleared because the ELDR CLEAR option was not specified in the input deck when running the offline job (TLDR). This means that after the auxiliary loader has completed processing, the image may still contain E-type programs that were loaded previously with the E-type loader. These programs may now be obsolete because of E-type programs included in the input file for the auxiliary loader. However, these previous versions of programs are still available for processing.

System Action: Auxiliary load processing is continued.

User Response: Exercise caution with any programs that were loaded previously using the E-type loader. Ensure that there are no compatibility problems between the programs that were loaded previously (by entering the ZOLDR LOAD command) and the programs that are loaded now (by entering the ZTPLD command).

Otherwise, you can clear out the programs that were previously loaded by entering the ZOLDR CLEAR or ZOLDR DELETE commands, or by using the ELDR CLEAR option in the input deck for the offline job (TLDR).

See TPF Operations for more information about the ZTPLD and ZOLDR commands. See TPF System Installation Support Reference for more information.

TPLD0116EREQUEST ABORTED -- ERROR WRITING IHR

Explanation: A system error or an input/output (I/O) error occurred while trying to update the image history record, which contains information about components loaded in each image.

System Action: The auxiliary load processing is ended.

User Response: Do the following:

  1. Determine the cause of the system error or the I/O error.
  2. Correct the error.
  3. Enter the ZTPLD command again.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0117EREQUEST ABORTED -- ERROR WRITING RECORD TO rectype ORDINAL NUMBER ordnum

Where:

rectype
The FACS record type.

ordnum
The record ordinal number.

Explanation: A system error or an input/output (I/O) error occurred while trying to write a record at the specified file type and ordinal position.

System Action: The auxiliary load processing is ended.

User Response: Do the following:

  1. Determine the cause of the system error or the I/O error.
  2. Correct the error.
  3. Enter the ZTPLD command again.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0118EREQUEST ABORTED -- EXPECTED ITEM NOT FOUND IN INPUT FILE TLDR OUTPUT MAY HAVE BEEN CORRUPTED

Explanation: The auxiliary loader did not find an expected data item within the input file.

System Action: The OPR-07C system dump is issued and the load processing is ended.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0119EREQUEST ABORTED -- ERROR WRITING CTKX FOR IMAGE imagenum

Where:

imagenum
The image number.

Explanation: A system error or an input/output (I/O) error occurred while trying to update the CTKX record for the specified image number.

System Action: The auxiliary load processing is ended.

User Response: Do the following:

  1. Determine the cause of the system error or the I/O error.
  2. Correct the error.
  3. Enter the ZTPLD command again.

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0120WUNABLE TO CHECK IPAT COMPATIBILITY

Explanation: A system error or an input/output (I/O) error occurred while trying to retrieve the IPAT record for the target image to do IPAT compatibility checking.

Note:
This checking is only done when the input file for ZTPLD does not include IPAT and includes components that may depend upon the allocator (anything other than CP, CTKX, file address compute program (FACE) table (FCTB)).

System Action: Auxiliary load processing is continued.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD and ZIMAG COPY commands. See TPF System Installation Support Reference for more information.

TPLD0121EREQUEST ABORTED -- RECORD ID record1 FOUND IN INPUT FILE WHILE EXPECTING RECORD ID record2

Where:

record1
The actual record ID from the input file.

record2
The record ID that was expected.

Explanation: The auxiliary loader did not find an expected data item within the input file. The expected data item would have had the record ID specified in the message but a different record ID was found.

System Action: A system error dump is issued and load processing is ended.

User Response: Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0123WTIME STAMP MISMATCH DETECTED BETWEEN OFFLINE IPAT AND ONLINE PAT

Explanation: The time stamp in the online program allocation table (PAT) does not agree with the time stamp from the PAT in the input file, which was copied from the offline PAT. This means that the program allocation characteristics in the online system may not agree with those used while running the offline job (TLDR) that was used to prepare the auxiliary loader input file.

If the input file does not include any program components other than CP, CTKX, and FCTB, it is safe to continue load processing because these components are unaffected by a PAT mismatch.

System Action: Auxiliary load processing is continued.

User Response: Do the following:

  1. Determine the cause of the PAT mismatch.
  2. Do one of the following:

See TPF Operations for more information about the ZTPLD command. See TPF System Installation Support Reference for more information.

TPLD0124WADATA FILES WILL BE IGNORED

Explanation: The auxiliary loader attempted to load one or more real-time programs with ADATA files, however, these ADATA files could not be loaded because #APRGn records are not allocated.

System Action: The loader does not attempt to load ADATA files for any real-time programs.

User Response: To load real-time programs with ADATA files, do one of the following:

See TPF System Installation Support Reference for more information about loaders.

TPLD0125ELOADING ccccvv FOR PROCESSOR nn KEYPOINT CONTROL RECORDS NOT CONVERTED FOR 32-WAY LOOSELY COUPLED

Where:

ccccvv
The keypoint and version being loaded.

nn
The decimal processor ordinal for the keypoint being loaded.

Explanation: While loading keypoints, the auxiliary loader (ALDR) has detected a keypoint for processor ordinals 8 - 31. The keypoint control records have not been converted to 32-way loosely coupled format and only support processor ordinals 0 - 7. A loss of keypoint status would result if unconverted keypoint control records were filed.

System Action: Keypoint load processing is ended.

User Response: Enter the ZMIGR command to remove keypoints for processor ordinals 8 - 31 from the load until the keypoint control records have been migrated to 32-way loosely coupled format.

See TPF Operations for more information about the ZMIGR command.

TPLD0126EUNABLE TO LOAD ccccvv FOR PROCESSOR nn CTKX FOR IMAGE imagename ONLY SUPPORTS gg PROCESSORS

Where:

ccccvv
The keypoint and version being loaded.

nn
The decimal processor ordinal for the keypoint being loaded. Processor ordinal numbers start with 0.

imagename
The name of the TPF system image being loaded.

gg
The total number of processors supported by the version of keypoint X (CTKX) currently loaded on the TPF system image.

Explanation: The auxiliary loader tryed to load keypoints for processor nn to the keypoint staging area for the TPF system image imagename. When doing the load, the keypoint ordinals for the processor are obtained from the CTKX for this TPF system image. The CTKX was generated for a maximum of gg processors and does not contain keypoint ordinal number for processor nn.

System Action: Keypoint load processing is ended.

User Response: Include in the TPF system image a version of CTKX that was generated for all of the processors for which keypoints are being loaded.

TPRD0001Ename tapename devaddr CCcode CCW-command CSW-word SNS-data

Where:

name
The subsystem user (SSU) name or the basic subsystem (BSS) name.

tapename
The symbolic tape name (for example, RTL).

devaddr
The device address.
Note:
Where two paths are defined for the drive, the address given is that used for the failing operation.

code
The SIO condition code. When a deferred SIOF condition code occurs the deferred condition code is given.

command
The channel command that was not successful.
Note:
When a data chained channel program specified through the TDCTC macro fails, the operation code given is that of the first CCW in the chain.

word
The channel status word. This is the CSW associated with the error.
Note:
For the SIO condition code 3 (not operational), the CSW is not meaningful and is not included in the message.

data
The sense data. The sense data is only included in the message for unit-check conditions. The number of sense bytes displayed is dependent on the device type. There are 24 bytes displayed for the IBM 3400 series tape drives. If an input/output (I/O) error prevents the successful sensing of the device, the UNABLE word is displayed in place of the sense data.

Explanation: None.

System Action: None.

User Response: None.

TPXD0001ALOAD TAPE VOLUME volser INTO DRIVE devaddr MOUNTED AS tapename

Where:

volser
The volume serial label of the tape.

devaddr
The device address to use when mounting the tape.

tapename
The symbolic tape name.

Explanation: An application program has issued a TPFxd_open call and the tape referenced in the positioning string map was not found in the tape status table (TSTB).

System Action: Processing is suspended for the entry control block (ECB) that issued the TPFxd_open call until the request is satisfied or the timeout value indicated has elapsed.

User Response: Mount the tape for input on the device specified by using the tape name specified.

See the TPF C/C++ Language Support User's Guide for more information about the TPFxd_open C function.

TPXD0002Innnnnnnnnnn...nnnn

Where:

nnnnnnnnnnnn...nnnn
The text provided by either a TPFxd_open, TPFxd_nextVolume, or tape_access call if the requested tape could not be located in the time indicated.

Explanation: A TPFxd_open, TPFxd_nextVolume, or tape_access call was attempted and the required tape was not available in the time specified. A message that is provided with the function call is sent to the console.

System Action: A timeout error condition is returned to the application program and processing continues.

User Response: Do the following:

  1. Determine why the tape was not mounted in the time specified by the application program.
  2. Activate the application program that contains the TPFxd_open, TPFxd_nextVolume, or tape_access function calls again.

See the TPF C/C++ Language Support User's Guide for more information about the TPFxd_open, TPFxd_nextVolume, and tape_access C functions.

TRCC0001IECB CHECKING ACTIVATION COMPLETED

Explanation: ECB checking was activated successfully.

System Action: None.

User Response: None.

TRCC0002IECB CHECKING INACTIVATION COMPLETED

Explanation: ECB checking was inactivated successfully.

System Action: None.

User Response: None.

TRCC0003EPARAMETER INVALID

Explanation: The parameter is not valid. Valid parameters are:

System Action: None.

User Response: None.

TRCC0004WECB CHECKING ALREADY ACTIVE

Explanation: A request to activate ECB checking was rejected because ECB checking was already active.

System Action: None.

User Response: None.

TRCC0005WECB CHECKING ALREADY INACTIVE

Explanation: A request to inactivate ECB checking was rejected because ECB checking was already inactive.

System Action: None.

User Response: None.

TRCC0006IECB CHECKING ACTIVE

Explanation: This message is displayed in response to a request for ECB checking status.

System Action: None.

User Response: None.

TRCC0007IECB CHECKING INACTIVE

Explanation: This message is displayed in response to a request for ECB checking status.

System Action: None.

User Response: None.