gtpm5m1u | Messages (Online) |
MEAS0001I | STARTING |
Explanation: This is the normal response to a command starting data collection.
System Action: None.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0002I | TERMINATION REQUESTED |
Explanation: A command was entered to stop data collection. Data collection stops at the end of the current sampling mode period and at the end of the current continuous mode interval.
System Action: None.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0003I | TERMINATED |
Explanation: This is the normal response when data collection finishes successfully.
System Action: None.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0004I | STARTING (NO COMPLEXWIDE DATA WILL BE COLLECTED) |
Explanation: This is the normal response to a command starting data collection on a CPU excluded from collecting complex-wide data.
System Action: None.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0005I | TERMINATED (NO COMPLEXWIDE DATA WAS COLLECTED) |
Explanation: This is the normal response when data collection finishes successfully on a CPU excluded from collecting complex-wide data.
System Action: None.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0006I | NOT ACTIVE |
Explanation: A command specified that data collection was to be stopped even though it was not active.
System Action: None.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0007I | ALREADY ACTIVE |
Explanation: There was an attempt to start data collection when it was already active. In addition, an incorrectly spelled ZMEAS END command can generate this message.
System Action: None.
User Response: Do one of the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0008I | TERMINATION ALREADY IN PROGRESS |
Explanation: A command was entered to stop data collection even though the terminate condition already exists.
System Action: None.
User Response: Do one of the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0009E | SAMPLING PERIOD MUST BE 3 SEC GT THE SUM OF INTERVALS |
Explanation: A command specifying a sampling mode request has the sum of the interval plus three seconds greater than or equal to the cycle time. To start collection in this situation, increase the cycle time or decrease the interval time.
System Action: None.
User Response: Correct the command input.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0010E | INVALID COLLECTOR NAME - MUST BE S, F, M, OR P |
Explanation: A program collector code that is not valid was found in the sampling mode or continuous mode request. The only collectors activated are:
System Action: None.
User Response: Enter the command again by using the correct format.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0011E | INVALID TIME PERIOD SPECIFIED |
Explanation: A time field in the input message contained a non-numeric character or a zero.
System Action: None.
User Response: Enter the command again and specify valid time parameters.
MEAS0012E | MORE THAN 'INTVL' PERIODS IN THE LIFE OF DATA COLLECTION |
Explanation: The number of sampling periods specified (indirectly) in the ZMEAS sampling mode message must not exceed the limit set by the INTVL parameter of the system initialization program (SIP) DATACO macro.
System Action: None.
User Response: Indicate fewer sampling periods by specifying a shorter duration for the life of data collection in the sampling mode or a longer duration for each sampling period.
The format of the relevant part of the ZMEAS sampling mode message is /mmss/ where mm indicates the duration in minutes and ss is the duration in seconds. Decrease mm to specify a shorter duration for the life of data collection in sampling mode. Increase ss to specify a longer duration for each sampling period.
The number of sampling periods is calculated by converting the minutes (mm) in the life of data collection to seconds (mm *60) and dividing by the seconds (ss) in each sampling period. The number of sampling periods may not exceed the INTVL limit.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0013E | DUPLICATE COLLECTORS SPECIFIED |
Explanation: A collector mode (S, F, P, or M) was duplicated in a command specifying sampling mode.
System Action: None.
User Response: To start collection, submit the request again with unduplicated collector modes.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0014I | I/O ERROR READING CTKA |
Explanation: An input/output (I/O) error occurred when the driver segment attempted to read CTKA.
System Action: Collection is continued.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0015I | I/O ERROR READING RCIT |
Explanation: An input/output (I/O) error occurred when the driver segment tried to read an RCIT record.
System Action: Collection is continued.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0016I | I/O ERROR READING UAT |
Explanation: An input/output (I/O) error occurred when the driver segment tried to read a UAT record.
System Action: Collection is continued.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0017I | I/O ERROR READING CTKI |
Explanation: An input/output (I/O) error occurred when the driver segment tried to read CTKI.
System Action: Collection is continued.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0018E | SYSTEM IN 1052/UTIL STATE OR CYCLING |
Explanation: An attempt was made to start data collection when the TPF systemwas in 1052 state, in utility (UTIL) state, or during cycling.
System Action: Collection is aborted.
User Response: Do the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0019E | MOUNT RTC TAPE AND REISSUE ZMEAS |
Explanation: This message is displayed when an attempt is made to start data collection before the RTC tape is mounted.
System Action: None.
User Response: Do the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0020E | INVALID INPUT MESSAGE |
Explanation: An incorrect message to start or stop data collection was entered.
System Action: None.
User Response: Enter the command again and specify a valid tertiary action code (that is, S, I, V, or END) to start or stop data collection.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance. Also see TPF Operations for more information about the correct format for the commands.
MEAS0021E | DESIGNATED CPU NOT SYSGENED |
Explanation: A request to start data collection was rejected because the CPU designated to collect exclusively complex-wide data was not generated into the TPF system. This prevents the CPU from collecting any data. Data collection starts only when it is reasonable to expect complex-wide data to be collected somewhere in the sysplex.
System Action: None.
User Response: Select another CPU for data collection. The one selected is not defined to the TPF system.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0022E | DESIGNATED CPU NOT ACTIVE |
Explanation: The request to start data collection is rejected because the CPU designated to collect exclusively complex-wide data is not active. This prevents it from collecting any data. Data collection starts only when it is reasonable to expect complex-wide data to be collected somewhere in the sysplex.
System Action: None.
User Response: Do one of the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0023E | BSS CYCLING ON DESIGNATED CPU |
Explanation: The request to start data collection is rejected because the basic subsystem (BSS) is cycling on the CPU designated to collect exclusively complex-wide data. This prevents it from collecting any data. Data collection starts only when it is reasonable to expect complex-wide data to be collected somewhere in the sysplex.
System Action: None.
User Response: Do the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0024E | BSS BELOW CRAS STATE ON DESIGNATED CPU |
Explanation: The request to start data collection is rejected because the basic subsystem (BSS) on the CPU designated to collect exclusively complex-wide data is below the computer room agent set (CRAS) state. This prevents it from collecting any data. Data collection starts only when it is reasonable to expect complex-wide data to be collected somewhere in the sysplex.
System Action: None.
User Response: Cycle the TPF system to the appropriate state (probably NORM state) by entering the ZCYCL command.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0025I | RTC TAPE NOT USABLE |
Explanation: Data collection detected an error with the RTC tape.
System Action: Data collection is ended. Data on the tape should be considered unusable.
User Response: None.
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0026I | RTC TAPE TOO SLOW |
Explanation: The RTC tape queue threshold was reached.
System Action: An attempt is made to collect the end-of-episode records. The RTC tape probably can be reduced.
User Response: Do one of the following:
See TPF Operations and TPF System Performance and Measurement Reference for more information about system performance.
MEAS0027E | INVALID SKIP SPECIFIED |
Explanation: The skip value specified on the ZMEAS command is not valid because a non-numeric value was specified.
System Action: None.
User Response: Enter the ZMEAS command again and specify a skip value between 0 and 9999. If you do not specify a skip value, the default value is 99.
See TPF Operations for more information about system performance operations and TPF System Generation for more information about the skip value.
MEAS0028I | DATA COLLECTION HAS BEEN RESET |
Explanation: The ZMEAS RESET command has completed.
System Action: The TPF 4.1 system assumes that data collection failed and clears any residual data collection status that may otherwise prevent data collectionfrom running again.
The TPF system does the following:
User Response: None.
See TPF Operations for information about the unusual conditions for which the ZMEAS RESET command is intended.
MEAS0029I | cccc CURRENT pppp PREVIOUS oooo ORIGINAL TAPE THRESHOLDS |
Where:
Explanation: The ZMEAS Q command has completed. It is used to display and alter the RTC tape queue threshold. The RTC tape is the Data Collection/Reduction tape. When the length of the RTC tape queue reaches this threshold, Data Collection quiesces.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMEAS Q command.
MEAS0030I | ALREADY STARTING |
Explanation: The ZMEAS command was entered to start data collection when it was started already.
System Action: None.
User Response: Do one of the following:
See TPF Operations for more information about the ZMEAS and ZMEAS END commands. See TPF System Performance and Measurement Reference for more information about system performance.
MIGR0001I | CTKI CONVERSION COMPLETED, SUBSYSTEM STATE TABLE HAS BEEN MOVED FROM CTKI TO FIXED FILE RECORD TYPE #CN1ST |
Explanation: This is a normal response to the ZMIGR command with the CTKI and CONVERT parameters specified.
System Action: The subsystem state table has been moved from IC0SST in CTKI to fixed file record type #CN1ST.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0002I | CTKI FALLBACK COMPLETED, SUBSYSTEM STATE TABLE HAS BEEN MOVED FROM FIXED FILE RECORD TYPE #CN1ST TO CTKI |
Explanation: This is a normal response to the ZMIGR command with the CTKI and FALLBACK parameters specified.
System Action: The subsystem state table has moved from fixed file record type #CN1ST to IC0SST in CTKI.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0003I | CTKI IS NOT CONVERTED, SUBSYSTEM STATE TABLE IS RESIDENT IN CTKI |
Explanation: This is a normal response to the ZMIGR command with the CTKI and STATUS parameters specified.
System Action: The current location of the subsystem state table is displayed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0004I | CTKI IS CONVERTED, SUBSYSTEM STATE TABLE IS RESIDENT IN FIXED FILE RECORD TYPE #CN1ST |
Explanation: This is a normal response to the ZMIGR command with the CTKI and STATUS parameters specified.
System Action: The current location of the subsystem state table is displayed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0005T | PARAMETER IS NOT VALID |
Explanation: The ZMIGR command was entered with an incorrect or missing parameter.
System Action: The ZMIGR command help message is displayed.
User Response: Enter the ZMIGR command with the correct parameters specified.
See TPF Operations for more information about the ZMIGR command.
MIGR0006T | UNABLE TO CONVERT DUE TO UNMIGRATED PROCESSORS |
Explanation: The ZMIGR command was entered with the CONVERT parameter specified, but all the processors in the loosely coupled complex are not migrated to 32-way loosely coupled processor support. All processors in the loosely coupled complex must be migrated to 32-way loosely coupled processor support before this command is entered.
System Action: Data remains in the unconverted format and the entry control block (ECB) exits.
User Response: Do the following:
See TPF Operations for more information about the ZMIGR command.
MIGR0007W | CTKI IS ALREADY IN REQUESTED STATE |
Explanation: One of the following occurred:
System Action: Data format is unchanged and the entry control block (ECB) exits.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0008T | CONVERSION NOT ALLOWED WITH MORE THAN 8 PROCESSORS |
Explanation: The ZMIGR command was entered with the CONVERT or FALLBACK parameter specified in a loosely coupled complex with more than eight processors generated. This is not allowed because processor data beyond the eighth processor would be lost.
System Action: Data format is unchanged and the entry control block (ECB) exits.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0009I | record CONVERSION COMPLETED |
Where:
Explanation: This is the normal response to the ZMIGR command with the KEYPOINT and CONVERT parameters specified. The keypoint control record for the specified record type was converted to 32-way loosely coupled format.
System Action: Conversion continues with the next record type.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0010I | KEYPOINT function REQUEST COMPLETED |
Where:
Explanation: This is the normal response to the ZMIGR command with the KEYPOINT parameter specified. All keypoint records are processed.
System Action: The function specified in the ZMIGR command is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0011I | record FALLBACK COMPLETED |
Where:
Explanation: This is the normal response to the ZMIGR command with the KEYPOINT and FALLBACK parameters specified. Fallback is completed for the keypoint control record of the specified record type.
System Action: FALLBACK parameter processing continues with the next record type.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0012T | ZMIGR KEYPOINT - ACTION NOT SUPPORTED |
Explanation: The ZMIGR command was entered with the KEYPOINT parameter and a second parameter specified, but the second parameter specified is not a support function.
System Action: The command ends with no action taken.
User Response: Enter the ZMIGR command again with the correct parameters specified.
See TPF Operations for more information about the ZMIGR command.
MIGR0013I | record CONVERTED |
Where:
Explanation: This is the normal response to the ZMIGR command with the KEYPOINT and STATUS parameters specified. The control record for the specified record type is in 32-way loosely coupled processor format.
System Action: The status request continues.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0014I | record NOT CONVERTED |
Where:
Explanation: This is the normal response to the ZMIGR command with the KEYPOINT and STATUS parameters specified. The control record for the specified record type is not in 32-way loosely coupled processor format.
System Action: The status request continues.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0015T | ZMIGR KEYPOINT - ACTION INDEX NOT VALID |
Explanation: The ZMIGR command was entered with the KEYPOINT parameter and a second parameter specified, but the second parameter's internal index value is not valid.
System Action: A 00510C system error with a SNAPC dump is started. The command ends with no action taken.
User Response: Do the following:
See TPF Operations for more information about the ZMIGR command.
MIGR0016W | record IS ALREADY IN THE REQUESTED STATE |
Where:
Explanation: One of the following occurred:
System Action: The CONVERT or FALLBACK parameter request continues.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0017T | ZMIGR KEYPOINT - TOO MANY PARAMETERS |
Explanation: The ZMIGR command was entered with the KEYPOINT parameter and more than one additional parameter specified. There can be only one parameter following the KEYPOINT parameter.
System Action: The command ends with no action taken.
User Response: Enter the ZMIGR command correctly.
See TPF Operations for more information about the ZMIGR command.
MIGR0018T | UNABLE TO CONVERT, RECORD ID OF #CN1ST ORDINAL nn INDICATES AN UNEXPECTED STATE |
Where:
Explanation: While processing a ZMIGR command with the CTKI parameter and the CONVERT or FALLBACK parameter specified, a #CN1ST ordinal was found in an unexpected state. One of the following occurred:
System Action: One of the following occurs:
User Response: This error can occur if conversion indicator IC032LC does not reflect the current state of the data. Verify that the correct version of keypoint I (CTKI) is loaded and that IC032LC is set as expected. This flag is set by the ZMIGR command or by the CTKI32LC parameter of the CONFIG macro during system initialization package (SIP) processing of a new CTKI.
See TPF Operations for more information about the ZMIGR command. See TPF System Generation for more information about SIP and the CONFIG macro.
MIGR0019I | #CN1ST ORDINALS HAVE BEEN INITIALIZED |
Explanation: This is a normal response when the following occurs:
System Action: TPF system restart initializes the new #CN1ST ordinals and continues.
User Response: None. Because the system has been initialized and is now using the #CN1ST ordinals, you do not need to enter the ZMIGR command with the CTKI and CONVERT parameters specified.
See TPF Operations for more information about the ZMIGR command.
MIGR0020T | REQUEST REJECTED, ZMIGR CTKI IS VALID IN THE BSS ONLY |
Explanation: The ZMIGR command was entered with the CTKI parameter specified from a multiple database function (MDBF) subsystem other than the basic subsystem (BSS). CTKI requests are only allowed in the basic subsystem because subsystem state table record type #CN1ST is resident in the basic subsystem.
System Action: The ZMIGR command ends and the entry control block (ECB) exits.
User Response: Enter the ZMIGR command with the CTKI parameter specified from the basic subsystem.
See TPF Operations for more information about the ZMIGR command.
MIGR0021I | 32-WAY LC MIGRATION STATUS PROCESSOR procid STATUS status |
Where:
Explanation: This is a normal response to the ZMIGR command with the PROCESSOR and STATUS parameters specified. The 32-way loosely coupled processor support migration status for each processor is listed.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0022W | record READ ERROR |
Where:
Explanation: The ZMIGR command uses the read function of the ZIMAG command to read the keypoint control record. This function reported an error while reading the record. There is an accompanying IMAG message that explains the error.
System Action: No action is taken on the record that was read in error and the command continues with the next record.
User Response: Do one of the following:
See TPF Operations for more information about the ZMIGR and ZIMAG commands.
MIGR0023W | record FILE ERROR |
Where:
Explanation: The ZMIGR command uses the write function of the ZIMAG command to read the keypoint control record. This function reported an error while filing the record. There is an accompanying IMAG message that explains the error.
System Action: No action is taken on the record filed in error and the command continues with the next record.
User Response: Do the following:
Records that were previously processed will be reported and records that were not processed will be updated.
See TPF Operations for more information about the ZMIGR and ZIMAG commands.
MIGR0025T | REQUEST REJECTED, ZMIGR MPIF IS VALID IN THE BSS ONLY |
Explanation: The ZMIGR command was entered with the MPIF parameter specified from a multiple database function (MDBF) subsystem other than the basic subsystem (BSS). MPIF requests are only allowed in the basic subsystem because subsystem state table record type #CN1ST is resident in the basic subsystem.
System Action: The ZMIGR command ends and the entry control block (ECB) exits.
User Response: Enter the ZMIGR command with the MPIF parameter specified from the basic subsystem.
See TPF Operations for more information about the ZMIGR command.
MIGR0030I | RECOUP CONVERSION COMPLETED |
Explanation: This is a normal response to the ZMIGR command with the RECOUP and CONVERT parameters specified. The 1052 FC33 record has been moved to its location for 32-way loosely coupled processor support and the migration indicator is set to converted.
System Action: The conversion is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0031I | RECOUP CONVERSION FALLBACK COMPLETED |
Explanation: This is a normal response to the ZMIGR command with the RECOUP and FALLBACK parameters specified. The 1052 FC33 record has been returned to the location it had before conversion to 32-way loosely coupled processor support, and the migration indicator is set to not converted. This message only occurs when a processor in a loosely coupled complex falls back from 32-way loosely coupled processor support to a previous level of support.
System Action: Fallback processing is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0032I | RECOUP MIGRATION STATUS - RECOUP CONVERSION COMPLETED |
Explanation: This is a normal response to the ZMIGR command with the RECOUP and STATUS parameters specified. The 1052 FC33 record has been moved to the location for 32-way loosely coupled processor support.
System Action: The status request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0033I | RECOUP MIGRATION STATUS - RECOUP CONVERSION NOT COMPLETED |
Explanation: This is a normal response to the ZMIGR command with the RECOUP and STATUS parameters specified. The 1052 FC33 record is not in the fixed record ordinal location for 32-way loosely coupled processor support.
System Action: The status request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0034E | RECOUP CONVERSION HAS ALREADY COMPLETED |
Explanation: The ZMIGR command was entered with the RECOUP and CONVERT parameters specified, but the 1052 FC33 record had already been moved to the fixed record ordinal location for 32-way loosely coupled processor support.
System Action: The ZMIGR command is rejected.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0035E | RECOUP CONVERSION FALLBACK HAS ALREADY COMPLETED |
Explanation: The ZMIGR command was entered with the RECOUP and FALLBACK parameters specified, but the 1052 FC33 record is not in the location for 32-way loosely coupled processor support. Fallback processing had already been requested.
System Action: The ZMIGR command is rejected.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0036I | ALL NEW FC33 RECORDS INITIALIZED |
Explanation: This is the normal response to the ZMIGR command with the RECOUP and INIT parameters specified. All new FC33 records are initialized.
System Action: The initialization request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0037E | NEW FC33 RECORDS ALREADY INITIALIZED |
Explanation: The ZMIGR command was entered with the RECOUP and INIT parameters specified. All new FC33 records had been previously initialized.
System Action: The initialization request is rejected.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0038E | FACS ERROR ON FC33, ORDINAL yyy |
Where:
Explanation: The ZMIGR command was entered with the RECOUP parameter specified, but an error occurred while calculating the file address for the FC33 record.
System Action: The ZMIGR command is ended.
User Response: Do the following:
See TPF Operations for more information about the ZMIGR command.
MIGR0039E | FIND ERROR ON FC33, ORDINAL yyy |
Where:
Explanation: The ZMIGR command was entered with the RECOUP parameter specified, but a find error occurred while accessing the FC33 record.
System Action: The ZMIGR command is ended.
User Response: Do the following:
See TPF Operations for more information about the ZMIGR command.
MIGR0040I | CTKC CONVERSION COMPLETED |
Explanation: The ZMIGR command was entered with the CTKC and CONVERT parameters specified. Keypoint C (CTKC) has been converted to 32-way loosely coupled format.
System Action: The conversion request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0041I | CTKC FALLBACK COMPLETED |
Explanation: The ZMIGR command was entered with the CTKC and FALLBACK parameters specified. Keypoint C (CTKC) has been returned to the format it had before conversion to 32-way loosely coupled format.
System Action: The fallback request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0042I | CTKC IS NOT CONVERTED |
Explanation: This is a normal response to the ZMIGR command with the CTKC and STATUS parameters specified. Keypoint C (CTKC) is not in 32-way loosely coupled format.
System Action: The status request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0043I | CTKC IS CONVERTED |
Explanation: This is a normal response to the ZMIGR command with the CTKC and STATUS parameters specified. Keypoint C (CTKC) is in 32-way loosely coupled format.
System Action: The status request is completed.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0044W | CTKC ALREADY IN REQUESTED STATE |
Explanation: One of the following occurred:
System Action: CTKC is unchanged and the entry control block (ECB) ends.
User Response: None.
See TPF Operations for more information about the ZMIGR command.
MIGR0045T | REQUEST REJECTED, ZMIGR CTKC IS VALID IN THE BSS ONLY |
Explanation: The ZMIGR command was entered with the CTKC parameter specified from multiple database function (MDBF) subsystem other than the basic subsystem (BSS). The CTKC parameter can only be entered when in the BSS.
System Action: The ZMIGR command is terminated and the entry control block (ECB) ends.
User Response: Enter the ZMIGR command with the CTKC parameter specified from the BSS.
See TPF Operations for more information about the ZMIGR command.
MODE0003E | FARFm DISPENSING MODE NOT ALLOWED WITHIN STAGE FARFs |
Where:
Explanation: The parameter for the ZMODE command was a valid file address reference format (FARF) addressing mode or a display request but it was not valid for the current FARF migration stage.
System Action: None.
User Response: Enter the ZMODE command again and specify a valid parameter for the current FARF migration stage.
See TPF Operations for more information about the ZMODE command.
MODE0004I | CURRENT DISPENSING MODE IS ALREADY FARFm |
Where:
Explanation: The dispensing mode specified is currently in effect.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMODE command.
MODE0005E | CANNOT ACTIVATE FARF6 DURING RESTART |
Explanation: The ZMODE command was entered to dispense FARF6 addresses while the TPF system was in restart. FARF6 address dispensing cannot be activated during restart.
System Action: The command is rejected.
User Response: Enter the ZMODE command again after the TPF system completes restart processing.
See TPF Operations for more information about the ZMODE command.
MODE0006E | CANNOT ACTIVATE FARF6 UNTIL CTK9 CONVERSION IS COMPLETE |
Explanation: The ZMODE command was entered to activate FARF6 addressing, but conversion to 32-way loosely coupled pool support format is not completed.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMODE and ZPMIG commands. See TPF Migration Guide: Program Update Tapes for more information about converting the entire complex to 32-way loosely coupled pool support format.
MODE0007E | FARF6 ADDRESSING IS ALREADY ACTIVE ON THIS PROCESSOR |
Explanation: The ZMODE command was entered to activate FARF6 addressing, but FARF6 addressing is already active.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMODE command.
MODE0008E | REQUEST INCOMPLETE -- ERROR err KEYPOINT 9 |
Where:
Explanation: The ZMODE command was entered to activate FARF6 addressing, but an error when retrieving or filing keypoint 9 (CTK9) occurred during processing.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMODE command.
MODE0009I | IN STAGE FARFs, DISPENSING MODE IS FARFm FARF6 ADDRESSING IS status |
Where:
Explanation: This is the normal response to the ZMODE command. This message displays the file address reference format (FARF) migration stage that is currently active and the FARF dispensing mode. In the FARF3 migration stage, dispensing is either in FARF3 or FARF4 formatted addresses. In the FARF4 migration stage, dispensing is either in FARF4 or FARF5 formatted addresses. An indication that FARF6 addressing is available means that the TPF system is ready to support FARF6 8-byte file addresses. This does not mean that FARF6 addresses are being used.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMODE command.
MODE0010E | VALID ZMODE PARAMETER IS 3, 4, 5, 6, OR D |
Explanation: The ZMODE command was entered with a parameter that is not valid. The parameter must be a valid file address reference format (FARF) addressing mode (3, 4, 5, or 6) or a display request (D).
System Action: None.
User Response: Enter the ZMODE command again and specify a valid parameter.
See TPF Operations for more information about the ZMODE command.
MODE0011I | SYSTC BIT SB8BFAD SET ON ALL I-STREAMS |
Explanation: This is a normal response to the ZMODE command with the 6 parameter specified to activate FARF6 addressing. This message indicates that the correct system bits were set for a processor in the complex. When FARF6 addressing is activated, this message is displayed on each processor in the complex.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMODE command.
MODE0012I | KEYPOINT 9 UPDATED |
Explanation: This is a normal response to the ZMODE command with the 6 parameter specified to activate FARF6 addressing. This message indicates that keypoint 9 (CTK9) was successfully updated with information indicating that FARF6 addressing is active.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMODE command.
MPIF0001I | PATH PARAMETERS DEFINED |
Explanation: This is the normal response to the ZMPIF DEFINE PATH command. The message is followed by a display of the defined path parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DEFINE PATH command.
MPIF0004I | SYSTEM PARAMETERS SET |
Explanation: This is the normal response to the ZMPIF SET command. This message is followed by a display of the system parameters and their settings.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF SET command.
MPIF0005I | COMPLEX PARAMETERS SET |
Explanation: This is the normal response to the ZMPIF SET command with the COMPLEX parameter specified. This message is followed by a display of the complex parameters and their settings.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF SET command.
MPIF0006I | CLASS PARAMETERS SET |
Explanation: This is the normal response to the ZMPIF SET command. This message is followed by a display of the class parameters and their settings.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF SET command.
MPIF0010I | TRACE STARTED |
Explanation: This is the normal response to the ZMPIF TRACE command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0011I | MSRB TRACE TABLE WILL NOT BE LOGGED TO TAPE |
Explanation: This is the normal response to the ZMPIF TRACE command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0012I | TRACE STOPPED |
Explanation: This is the normal response to the ZMPIF TRACE command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0013I | MSRB DISPLAY |
Explanation: This is the normal response to the ZMPIF TRACE command. This message is followed by a display of the MSRB trace table.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0014I | ACTIVE CONNECTION PARAMETERS |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the active connection parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0015I | ACTIVE PATH PARAMETERS |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the active path parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0016I | STATUS INFORMATION |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the status information.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0017I | ACTIVITY INFORMATION |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the activity information.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0018I | DEVICE PARAMETERS DEFINED |
Explanation: This is the normal response to the ZMPIF DEFINE command with the DEVICE parameter specified. This message is followed by a display of the defined device parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DEFINE command.
MPIF0019I | ACTIVE DEVICE PARAMETERS |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the active device parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0026I | DEVICE PURGED |
Explanation: This is the normal response to the ZMPIF STOP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0026I | PATH(S) PURGED |
Explanation: This is the normal response to the ZMPIF STOP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0027I | PATH(S) QUIESCING |
Explanation: This is the normal response to the ZMPIF STOP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0028I | DEVICE STARTED |
Explanation: This is the normal response to the ZMPIF START command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF START command.
MPIF0028I | DEVICE STOPPED |
Explanation: This is the normal response to the ZMPIF STOP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0028I | PATH(S) STARTED |
Explanation: This is the normal response to the ZMPIF START command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF START command.
MPIF0030I | ACTIVE SYSTEM PARAMETERS |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the active system parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0031I | ACTIVE COMPLEX PARAMETERS |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the active complex parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0032I | ACTIVE CLASS PARAMETERS |
Explanation: This is the normal response to the ZMPIF DISPLAY command. This message is followed by a display of the active class parameters.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0034W | PATH(S) ALREADY STARTED -- WILL CONTINUE WITH PRIMING OF LINKS |
Explanation: The paths associated with the given request are already in started status.
System Action: Processing is continued with priming of the device links. Paths in the process of being stopped, that is in QUIESCE state, are unaffected and will eventually be stopped.
User Response: None.
See TPF Operations for more information about the ZMPIF START command.
MPIF0035A | DEVICE ALREADY STARTED |
Explanation: The requested device was already started.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF START command.
MPIF0036E | INVALID INPUT FORMAT |
Explanation: The format of the ZMPIF TRACE command is not valid. For example, a parameter is spelled incorrectly or there were characters specified that are not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF commands.
MPIF0037E | TRACE BLOCK - INVALID LENGTH |
Explanation: The length of the trace block is not valid. For example, the length may be greater than 4 KB.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0038E | SUBCHANNEL NOT FOUND IN CCWA |
Explanation: The subchannel pair specified in the command was not found in the Multi-Processor Interconnect Facility (MPIF) hardware table (HDREC).
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF commands.
MPIF0040E | TERMINATED PATH |
Explanation: The path specified in the command was marked as ended in the channel command word area (CCWA).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0041E | INVALID SUBCHANNEL |
Explanation: The subchannel specified in the command is not in the channel command word area (CCWA).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0042I | SUBCHANNELS NOT FOUND |
Explanation: No entries were found in the trace table for the subchannels specified in the command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0043E | INVALID MPIF COMMAND |
Explanation: The trace block types specified in the command do not match the following trace block types, which are recognized by the TPF system:
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0044E | MPIF TRACE POINTER ERROR |
Explanation: There is no trace table defined in the TPF system. For example, the address of the trace table is zero.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0045E | SUBCHANNEL ERROR |
Explanation: The channel command word (CCW) indicator or channel command in the trace table is in error.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF commands.
MPIF0046E | INVALID LNIATA FOR PRINTER |
Explanation: The line number, interchange address, and terminal address (LNIATA) specified is not in the terminal address table (WGTA) or is not a printer.
System Action: The command is rejected.
User Response: Enter the command again and specify a correct printer LNIATA.
See TPF Operations for more information about the ZMPIF commands.
MPIF0047E | INVALID SUBCHANNEL RANGE |
Explanation: The subchannel range specified was not found in the channel command word area (CCWA) table.
System Action: The command is rejected.
User Response: Enter the command again and specify a subchannel range that is valid for your configuration.
See TPF Operations for more information about the ZMPIF commands.
MPIF0051A | SYNTAX ERROR |
Explanation: The command has a syntax error.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF command.
MPIF0052A | xxxxx PARAMETER INVALID |
Where:
Explanation: A command was entered and the parameter referenced in the message has an incorrect value. A CLASS parameter condition that is not valid can indicate that no path classes were defined.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF command.
MPIF0053A | TOO MANY PARAMETERS |
Explanation: A DISPLAY command was entered with too many parameters.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF DISPLAY command.
MPIF0054A | NO INFORMATION IS AVAILABLE FOR DISPLAY |
Explanation: The paths or devices associated with the request were not defined to the TPF system in the path definition record (PDR) (CB9PD) or the Multi-Processor Interconnect Facility (MPIF) hardware table definition record (HDREC), respectively. No parameters were defined through the ZMPIF SET command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF SET or ZMPIF DEFINE PATH command.
MPIF0056E | MPIF USER NAME NOT FOUND IN RFND |
Explanation: The specified user name was not found in the resident function name directory (DCTRNF).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0057E | PATH NAME NOT FOUND IN PDT |
Explanation: The specified path name was not found in the path definition table (DCTPDT).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0058E | GENERIC NAME NOT FOUND IN CWA |
Explanation: The specified generic device name was not found in the 3088 CWA table (DCTCWA).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0059E | NUMBER OF PATHS IN TRACE REQUEST EXCEEDS MAXIMUM |
Explanation: The format of the command is not valid.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0062E | NO PATHS DEFINED IN PDT |
Explanation: No paths are defined in the path definition table (DCTPDT).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0063E | NO CONNECTIONS FOUND IN CDB |
Explanation: No connections are defined in the connection definition block table (DCTCDB).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0064E | NO CCW ENTRIES FOUND IN CWA |
Explanation: No devices are defined in the Multi-Processor Interconnect Facility (MPIF) hardware table (HDREC).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0065E | NO USER NAMES FOUND IN RFND |
Explanation: No MPIF user names were found in the resident function name directory (DCTRFN).
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0066W | MSRB TRACE WILL BE STOPPED BECAUSE OF SHORTAGE OF 4K BLOCKS |
Explanation: In the CBQ3 segment, while dumping the in core MSRB trace table to tape, it was discovered that the number of 4K blocks available has fallen below the input list shutdown level.
System Action: MSRB trace is stopped. The PDT entries are cleaned up.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0069I | DEVICE DELETED |
Explanation: This is the normal response to the ZMPIF DELETE command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DELETE command.
MPIF0069I | PATH DELETED |
Explanation: This is the normal response to the ZMPIF DELETE command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZMPIF DELETE command.
MPIF0070A | UNABLE TO STOP DEVICE, PATH(S) NOT STOPPED |
Explanation: The device was not stopped since one or more paths were found to be using the device. All paths using a device must first be stopped before the device can be stopped unless the PURGE option is specified on the ZMPIF STOP DEVICE command.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0072A | DEVICE NOT DEFINED |
Explanation: The named device (generic device name) was not found in the MPIF CWA table (DCTCWA).
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF START and ZMPIF STOP commands.
MPIF0072A | PATH(S) NOT DEFINED |
Explanation: The paths associated with the given request are not defined to the TPF system.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF START and ZMPIF STOP commands.
MPIF0073A | UNABLE TO STOP, PATH(S) PROTECTED |
Explanation: A request to stop a specific path was not satisfied or a request to stop more than one path was not completely satisfied. The last path of a protected class of paths will never be stopped by Multi-Processor Interconnect Facility (MPIF). This message, thus, indicates that the last path of one or more protected path classes was not stopped. Any non-protected paths were stopped.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0074A | xxxxxx DEVICE ALREADY STOPPED OR QUIESCING |
Where:
Explanation: The device or path you requested (by entering the ZMPIF STOP command) is already in stopped status or is in the process of being stopped.
System Action: The ZMPIF STOP command is not processed.
User Response: None.
See TPF Operations for more information about the ZMPIF STOP command.
MPIF0078A | PDR RECORDS ARE FULL |
Explanation: The Multi-Processor Interconnect Facility (MPIF) Path Definition Records (CB9PD) are full.
System Action: The command is rejected.
User Response: Have your system programmer allocate more records for the PDR record type.
See TPF Operations for more information about the ZMPIF DEFINE PATH command.
MPIF0079A | HDW RECORDS ARE FULL |
Explanation: The Multi-Processor Interconnect Facility (MPIF) hardware definition records (HDRECs) are full.
System Action: The command is rejected.
User Response: Have your system programmer allocate more records for this record type.
See TPF Operations for more information about the ZMPIF DEFINE DEVICE command.
MPIF0080A | UNABLE TO DELETE, PATH|DEVICE NOT STOPPED |
Explanation: A path or device must be inactive or stopped to be deleted.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZMPIF DELETE command.
MPIF0084W | TRACE ALREADY ACTIVE |
Explanation: Trace is already active and the command entered was to start trace.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0085W | TRACE NOT ACTIVE |
Explanation: Trace is already not active and the command entered was to stop trace.
System Action: The command is rejected.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0086E | ERROR OCCURRED WHEN WRITING MSRB TRACE BLOCK TO TAPE |
Explanation: An error occurred when Multi-Processor Interconnect Facility (MPIF) was trying to write a trace record to the real-time tape.
System Action: The MSRB trace is stopped.
User Response: None.
See TPF Operations for more information about the ZMPIF TRACE command.
MPIF0090E | MESSAGE IS NOT VALID AT THIS TIME |
Explanation: A ZMPIF KPE REP or ZMPIF KPE BYPASS command was entered but was not expected by the Multi-Processor Interconnect Facility (MPIF) restart program.
System Action: The command is ignored.
User Response: The command should not be repeated. The ZMPIF KPE command is valid only after MPIF restart has requested it. See the CBR20006A message for more information.
See TPF Operations for more information about the ZMPIF KPE command.
MPIF0091E | VALID RESPONSES ARE ZMPIF KPE REP OR ZMPIF KPE BYPASS REENTER MESSAGE |
Explanation: A response to a CBR20006A message was not a ZMPIF KPE REP or ZMPIF KPE BYPASS command.
System Action: The command is ignored.
User Response: Enter the correct command.
See TPF Operations for more information about the ZMPIF KPE command.
MPIF0092E | MESSAGE IS NOT VALID AT THIS TIME |
Explanation: A ZMPIF PDR|HDW INIT or ZMPIF PDR|HDW BYPASS command was entered but was not expected by the Multi-Processor Interconnect Facility (MPIF) restart program.
System Action: The command is ignored.
User Response: The command should not be repeated. The ZMPIF PDR|HDW commands are valid only after MPIF restart had requested them. See the CBR00101W command.
See TPF Operations for more information about the ZMPIF PDR and ZMPIF HDW commands.
MPIF0093E | VALID RESPONSES ARE ZMPIF PDR|HDW INIT OR ZMPIF PDR BYPASS REENTER MESSAGE |
Explanation: A response to the CBR00101W message was not the ZMPIF PDR|HDW INIT or ZMPIF PDR|HDW BYPASS commands.
System Action: The command is ignored.
User Response: Enter the correct command.
See TPF Operations for more information about the ZMPIF PDR and ZMPIF HDW commands.