gtpm5m1nMessages (Online)

IPLA-IPLB

IPLA0005WNO 328X PRINTER IS OPERATIONAL -- RESTART CONTINUES

Explanation: In a TPF system generated with 3270 native console support, IPLA found all printers specified as eligible for the system receive only (RO) (see the ROCRS parameter on the SIP CRASTB macro) to be non-operational.

System Action: The system RO is marked as not valid in the line status table. All message issued during restart are sent to the system prime computer room agent set (PRC) and are not duplicated to the system RO.

User Response: When the TPF system reaches 1052 state, enter the ZACRS command to assign a system RO. Also, you may want to check the hardware configuration.

See TPF Operations for more information about the ZACRS command. See TPF Main Supervisor Reference for more information.

IPLA0050EVOLUME vol ON ccud - cccchhhhrr - ID xxxx FOUND IN location

Where:

vol
The volume serial number (VSN) or UNKNOWN.

ccud
The failing device address.

cccchhhhrr
The cylinder, head, record address.

xxxx
The record ID (in hexadecimal representation) in error.

location
One of the following:

ICR
Image Control Record

CTKx
X, I, or B

IPLB
 

KPTR
Keypoint pointer record

Explanation: This message tries to identify the reason for the DASD read error or record ID check failure.

System Action: If the location is not KPTR, the IPL procedure is ended with a storage dump. If KPTR is specified as the location, see message IPLA0055W for information about the action taken by the TPF system.

User Response: Do one of the following:

See TPF Main Supervisor Reference for more information about this error.

IPLA0051TPROGRAM CHECK IN IPLA

Explanation: Whenever the dump routine of the IPL program is called, the OLD PSW program is examined to determine whether a program check occurred. If so, this message and a dump is is sent to the console and the printer.

System Action: The IPL is ended. When the dump routine of the IPL program is entered, this message is sent if a program check was cause of the dump routine being entered.

User Response: Do the following:

  1. Have your system programmer review the system error dump.
  2. Take the necessary corrective action to correct the problem.
  3. IPL the TPF system again.

See TPF Main Supervisor Reference for more information.

IPLA0052EDEV ccud: START I/O FAILURE,CC=c DEV ccud: I/O ERROR

Where:

ccud
The device unit address.

c
2 or 3

Explanation: An input/output (I/O) error is when a condition code 1 is obtained or the interrupt contained an an error condition, in which case the subchannel status word (CSW) is appended by the IPLA0053E message.

The IPL program detected an error at SIO initiation time or the IPL program detected an error at the I/O interrupt time. The I/O error indicates that the condition code is 1.

System Action: The IPLA0053E and IPLA00503 messages may accompany the IPLA0052E message.

The IPL procedure is ended with a storage dump.

User Response: See your system programmer or your IBM service representative to determine the cause of the problem and to correct it. The IPLA0053E and IPLA0050E messages should be logged for them. In addition, the IPLA0050E, IPLA0052E, and IPLA0053E messages should be reviewed.

See TPF Main Supervisor Reference for more information.

IPLA0053EORIGINAL DEV/SUBCH STATUS xxyy

Where:

xx
The device status.

yy
The subchannel status.

Explanation: This message does one of the following:

System Action: The IPLA0050E message may accompany this message. The IPL procedure is ended with a storage dump.

User Response: See your system programmer or your IBM service representative to determine the cause of the problem and to correct it.

The SENSE data, if presented, indicates the reason for the unit error.

SENSE DATA NOT AVAILABLE

SENSE DATA ssssssss...ssssssss

Where:

ssssssss...ssssssss
The 24 byte sense data.
CU/DEV BUSY PERSISTENT

See TPF Main Supervisor Reference for more information.

IPLA0055WERROR READING KEYPOINT POINTER RECORD PSEUDO KEYPOINT POINTER RECORD USED

Explanation: On the initial TPF system IPL, keypoint pointer record #KEYPT does not exist in record ordinal 0 for the basic subsystem (BSS). A pseudo record is built in code for use by IPL. This should only occur on the first TPF system IPL. At any other time, the keypoint pointer record has been corrupted.

System Action: The TPF system IPL continues. A permanent keypoint pointer record is built during system restart and message CVZ60001A is displayed.

User Response: Do one of the following:

IPLA0056TUNABLE TO MAP KEYPOINT ORDINAL nn,nnn

Where:

nn,nnn
The decimal ordinal that could not be mapped.

Explanation: A keypoint ordinal found in the CTKX record could not be mapped to a FACE ordinal. The keypoint ordinal was zero, a negative value, or a value greater than the range mapped by the keypoint pointer record. The most likely cause is one of the following:

System Action: The TPF system IPL ends with a storage dump.

User Response: Do the following:

  1. If the ordinal displayed is zero or a negative value, examine CTKX and correct the error.
  2. If the ordinal is positive, examine CTKX:
    1. If CTKX is in error, correct the error.
    2. If CTKX is correct, make sure that the first processor that is IPLed has its keypoints in previously existing areas of the #KEYPT definition; also make sure that the ZKPTR command with the REPLACE parameter specified was entered in response to message CVZ60002A during system restart so that the keypoint record is updated.
  3. IPL the TPF system.

See message CVZ60002A for options when the permanent or corrected keypoint pointer record is built by system restart. See TPF Operations for more information about the ZKPTR command.

IPLB0001ASPECIFY SYSTEM PARAMETER (F B U VOL N)

Explanation: The TPF IPL program is requested multiple database function (MDBF) IPL types.

System Action: The IPL program follows your specification.

User Response: Use one of the following responses:

F
To initiate a FAST IPL. The IPL volume serial number (VSN) must match the VSN saved in keypoint M (CTKM) by the previous IPL. In other words, if the prime module was IPLed last time and it is still online, you can only use the F option when IPLing the prime module.

If you try using the F option to IPL the duplicate module, you will receive the IPLB0058E message.

If you must IPL a different VSN, use the U option and specify the multiple database function (MDBF) subsystems manually.

Use this option only after the MDBF configuration keypoint record (CTKM) was initialized by the IPLB and restart program. Therefore, the first time the TPF system is IPLed or when a fresh copy of CTKM is loaded, this option is rejected with an IPLB0077E message.

Note:
Do not specify F on a loader general file at IPL because it will cause ACPL to abort.

B
To include only the basic subsystem (BSS).

U
To define multiple subsystems.

VOL
The first two characters (they must be alphabetic) of the BSS volume label. Volume labels will be requested for all subsystems. The first two characters of all volume labels in a subsystem or BSS must be the same.

N
Fallback extent index, a decimal number greater than or equal to one and less than or equal to the maximum extent number.

See TPF Main Supervisor Reference for more information.

IPLB0002ITHE SYSTEM ID IS enterprise.complex id ON PROCESSOR num MODEL mod LOW CPU ADDRESS addr

Where:

enterprise
The name of your operations center or enterprise.

complex
The name of your loosely coupled complex or stand-alone TPF processor.

id
The TPF CPU identifier.

num
The two-character version code with the six-character CPU serial number.

mod
The CPU model number, for example, 3090.

addr
The lowest CPU address of the processor or processor partition on which the TPF system is running.

Explanation: This informational message displays the system ID, which consists of the:

System Action: The TPF system IPL is continued.

User Response: None.

IPLB0003TUNABLE TO READ FALLBACK EXTENT KEYPOINT POINTER RECORD IPL TERMINATED

Explanation: While trying to IPL the TPF system using keypoints from a fallback extent, an error occurred while reading the keypoint pointer record for the fallback extent.

System Action: The TPF system IPL ends with a storage dump.

User Response: Do the following:

  1. Make sure the correct fallback extent was requested and that it has had the system keypoints copied to it.
  2. Review the previous IPLB error messages to determine the cause of the read error.
  3. If the problem can be corrected, correct the error and re-IPL the TPF system using keypoints from the original fallback extent.
  4. If the problem cannot be corrected, IPL the TPF system using a different fallback extent, another module that can be IPLed, the duplicate of the prime system module, or the prime system module without using a fallback extent.

See TPF Main Supervisor Reference for more information about IPLing the TPF system.

IPLB0004ASPECIFY SS TO BE INCLUDED (CCUD/VOL E C T)

Explanation: The IPL program is requesting that you specify the next system action.

System Action: Depending on your specification, the IPL program includes a subsystem, cancels a subsystem, ends the IPL operation, or completes the multiple database function (MDBF) definition.

User Response: Use one of the following responses:

CCUD
To include another subsystem. CCUD is a three-to-four character hexadecimal subsystem IPL device unit address. CCUD must be the first parameter followed by a slash when other options are supplied.

E
To end MDBF definition and continue IPL processing. This cannot be used with CCUD.

C
To cancel a subsystem that was defined previously.

CCUD/C
To cancel a subsystem that is specified by CCUD.

CCUD/VOL
To specify the volume checking option for the subsystem. VOL must be the first two label characters in the subsystem volume label.

T
To end IPL processing with a dump. This cannot be used with CCUD.

Examples:

03E0
This response includes a subsystem whose IPL device is 03E0.

03E0/MA
This response includes a subsystem whose IPL device is 03E0 and applies volume label checking.

This example indicates that the first two characters of the volume label are MA, which do not match those defined in the volume label keypoint record V (CTKV).

C
This response cancels a subsystem that was included just before this message.

04C1/C
This response cancels a subsystem that was included prior to the last definition.

This example indicates that a subsystem whose IPL device unit address is 04C1 is to be canceled and removed from the MDBF configuration.

E
This response ends the MDBF definition.

T
This response ends the IPL.

See TPF Main Supervisor Reference for more information.

IPLB0005ATOD CLOCK IS NOT RUNNING, OPERATOR MUST PRESS TOD 'ENABLE SET KEY'

Explanation: On certain CPU models, the CPU time will not decrement if the time-of-day (TOD) clock is running. The TPF system is trying to set the TOD clock during IPL to ensure that the CPU timer is operational.

System Action: IPLB sets an arbitrary value now to get the clock running. Clock restart prompts you for the correct time later in the cycle-up process.

User Response: Press the TOD Enable Set key to start the TOD clock.

See TPF Main Supervisor Reference for more information.

IPLB0006TTOD CLOCK IS NOT OPERATIONAL, IPL TERMINATED

Explanation: An attempt to issue a Set Clock instruction indicates that the time-of-day (TOD) clock is in the Not Operational state.

System Action: The IPL is ended with a disabled wait PSW.

User Response: See your IBM service representative to determine the cause of the TOD clock failure.

See TPF Main Supervisor Reference for more information.

IPLB0007IIPL STARTED ON DEV ccud VOL vol

Where:

ccud
The device unit address.

vol
The volume label.

Explanation: This message informs a subsystem (including a basic subsystem (BSS)) that IPL has started at the device indicated in the message with the volume label referenced in the message.

System Action: The TPF IPL program uses the device as the source of the subsystem keypoint records.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0008TUNABLE TO MAP KEYPOINT ORDINAL nn,nnn - IPL TERMINATED

Where:

nn,nnn
The decimal ordinal that could not be mapped.

Explanation: A keypoint ordinal that was found in the CTKX record could not be mapped to a FACE ordinal because the keypoint ordinal was zero, a negative value, or a value greater than the range mapped by the keypoint pointer record. The most likely cause is one of the following:

System Action: The TPF system IPL ends with a storage dump.

User Response: Do the following:

  1. If the ordinal displayed is zero or a negative value, examine and correct CTKX.
  2. If the ordinal is positive, examine CTKX:
    1. If CTKX is in error, correct the error.
    2. If CTKX is correct, make sure that the first processor IPLed has its keypoints in previously existing areas of the #KEYPT definition; also make sure that the ZKPTR command with the REPLACE parameter specified was entered in response to message CVZ60002A during system restart so that the keypoint record is updated.
  3. IPL the TPF system.

See message CVZ60002A for options when the permanent or corrected keypoint pointer record is built by system restart. See TPF Operations for more information about the ZKPTR command.

IPLB0009TUNABLE TO MAP BSS KEYPOINT ORDINAL nn,nnn - IPL TERMINATED

Where:

nn,nnn
The decimal ordinal that could not be mapped.

Explanation: A keypoint ordinal that was found in the CTKX record could not be mapped to a FACE ordinal because the keypoint ordinal was either zero, a negative value, or a value greater than the range mapped by the keypoint pointer record. The most likely cause is one of the following:

System Action: The TPF system IPL ends with a storage dump.

User Response: Do the following:

  1. If the ordinal displayed is zero or a negative value, examine and correct CTKX.
  2. If the ordinal is positive, examine CTKX:
    1. If CTKX is in error, correct the error.
    2. If CTKX is correct, make sure that the first processor IPLed has its keypoints in previously existing areas of the #KEYPT definition; also make sure that the ZKPTR command with the REPLACE parameter specified was entered in response to message CVZ60002A during system restart so that the keypoint record is updated.
  3. IPL the TPF system.

See message CVZ60002A for options when the permanent or corrected keypoint pointer record is built by system restart. See TPF Operations for more information about the ZKPTR command.

IPLB0010ISUBSYSTEM CANCEL ACCEPTED

Explanation: A request to cancel a subsystem was preformed successfully.

System Action: The subsystem is removed from the multiple database function (MDBF) configuration.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0011EVFA IS BEING REINITIALIZED DUE TO STORAGE CONFIGURATION CHANGE

Explanation: IPLB marked virtual file access (VFA) for reinitialization for one of the following reasons:

System Action: VFA is reinitialized and any data is lost.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0013EUNABLE TO MAP SS KEYPOINT ORDINAL nn,nnn - SS PURGED

Where:

nn,nnn
The decimal ordinal that could not be mapped.

Explanation: A keypoint ordinal that was found in the CTKX record could not be mapped to a FACE ordinal because the keypoint ordinal was either zero, a negative value, or a value greater than the range mapped by the keypoint pointer record. The most likely cause is one of the following:

System Action: The subsystem is not included in the multiple database function (MDBF) configuration.

For a TPF system IPL that you initiated, the next definition is initiated with message IPLB0004A or message IPLB0009T.

For the software-initiated TPF system IPL, the next subsystem is obtained from the MDBF configuration keypoint record.

User Response: Do the following:

  1. If the ordinal displayed is zero or a negative value, examine and correct CTKX.
  2. If the ordinal is positive, examine CTKX:
    1. If CTKX is in error, correct the error.
    2. If CTKX is correct, make sure that the first processor IPLed has its keypoints in previously existing areas of the #KEYPT definition; also make sure that the ZKPTR command with the REPLACE parameter specified was entered in response to message CVZ60002A during system restart so that the keypoint record is updated.
  3. IPL the TPF system.

See message CVZ60002A for options when the permanent or corrected keypoint pointer record is built by system restart. See TPF Operations for more information about the ZKPTR command.

IPLB0014WDUPLICATE VSN vvvvvv FOUND ON DASD CCUD ccud

Where:

vvvvvv
The volume serial number (VSN).

ccud
The device unit address.

Explanation: The IPL disk roll call detected two or more devices with the same volume serial number (VSN). This message is issued once for each duplicate volume.

System Action: This message is always followed by the IPLB0015A message.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0015ASPECIFY CCUD OR NONE FOR VSN vvvvvv

Where:

vvvvvv
The volume serial number (VSN).

Explanation: This message is always preceded by two or more IPLB0014W messages. This message allows you to select which of the duplicate volumes the IPL will use.

System Action: The IPL waits for a reply.

User Response: Do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0016IDASD ccud WILL BE USED FOR VSN vvvvvv

Where:

ccud
The device unit address.

vvvvvv
The volume serial number (VSN).

Explanation: This is the normal response to the IPLB0015A message.

System Action: The IPL proceeds by using the specified volume. The duplicate volumes is ignored.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0017EIPL VOLUME DUPLICATED, ENTER ccud OR RE-IPL TO CHANGE VOLUME

Where:

ccud
The initial program load (IPL) device unit address.

Explanation: This message follows the IPLB0015A message when the IPL volume is duplicated. Only the IPL volume device address indicated in the message is accepted in this case. You must IPL the TPF system again to switch to one of the other duplicate IPL volumes.

System Action: The TPF system issues another IPLB0015A message and waits for a reply.

User Response: Do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0017TDEVICE device, SUBSYSTEM ID ssid INVALID

Where:

device
The device address.

ssid
The subsystem ID.

Explanation: IPLB (IB04) detected a subsystem ID that is less than 1 or greater than 255.

System Action: None.

User Response: Assign a valid subsystem number that ranges from 1 to 255.

See TPF Main Supervisor Reference for more information.

IPLB0018WERROR READING KEYPOINT POINTER RECORD PSEUDO KEYPOINT POINTER RECORD USED

Explanation: On the initial TPF system IPL, no #KEYPT keypoint pointer record exists in ordinal 0 of the subsystem being processed. A pseudo record is built in code for use by IPLB. This should only occur on the first system IPL. At any other time, the keypoint pointer record has been corrupted.

System Action: The TPF system IPL continues. A permanent keypoint pointer record will be built during system restart.

User Response: Do one of the following:

IPLB0020ICONFIGURATION NOT SAME AS CTKM

Explanation: During this software (FAST) IPL, the TPF system configuration is not the same as that reported in CTKM (for the previous IPL).

System Action: The IPLB0027A message is issued. This message prompts you to continue, end, or IPL the TPF system again.

User Response: Do the following:

  1. Review the subsystem configuration report and verify that this configuration is keypointable.
  2. Determine why a subsystem was purged during this IPL.

See TPF Main Supervisor Reference for more information.

IPLB0021AVFA ACTIVE SPECIFY SYSTEM PARAMETER (F OR B)

Explanation: When virtual file access (VFA) is active in the TPF system, the system must be IPLed with the same configuration as it had on the previous IPL (F) or IPLed as a basic subsystem (BSS) only configuration (B). This is to avoid corruption of the VFA area.

System Action: IPL program follows your specification.

User Response: Use one of the following responses:

F
To initiate a FAST IPL. The IPL volume serial number (VSN) must match the VSN saved in keypoint M (CTKM) by a previous IPL. In other words, if the prime module was IPLed last time and it is still online, you can only use the F option when IPLing the prime module.

If you try using the F option to IPL the duplicate module, you will receive the IPLB0058E message.

If you must IPL a different VSN, do the following:

  1. Perform an IPL by using the CLEAR option (hardware). The IPLB0001A message displays.
  2. Select the U option to include the multiple database function (MDBF) subsystems.

B
To include only the basic subsystem (BSS).
Note:
If you perform a hard IPL with the CLEAR option, you will be able to specify the subsystems again (F, B, U, VOL, and N). When virtual file access (VFA) is active, the TPF system only prompts for the F or B options (for the same configuration or BSS only) to preserve the integrity of VFA. To include additional subsystems, memory must be cleared to force a rebuild of VFA.
See TPF Main Supervisor Reference for more information.

IPLB0022AWARNING MSG HAS BEEN SENT FOR THE FOLLOWING SUBSYSTEMS -- addr -- SPECIFY U TO CONTINUE, T TO TERMINATE OR CCUD TO BE PURGED

Where:

addr
The IPL address of the subsystems for which a warning message was sent.

Explanation: This message lists the IPL device unit address of all subsystems for which warning messages were sent.

System Action: Depends on your response.

User Response: Use one of the following responses:

U
To continue.

T
To end with a storage dump.

CCUD
To cancel a subsystem, where CCUD is the subsystem IPL device unit address.

See TPF Main Supervisor Reference for more information.

IPLB0023ISS IPL CCUD: ccud VOL vol,ss PURGED

Where:

ccud
The device unit address.

vol
The volume label of the subsystem IPL device.

ss
The two character online module volume label.

Explanation: A subsystem was internally purged from the multiple database function (MDBF) configuration due to a failure:

System Action: The IPL procedure is continued with the remaining subsystems.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0024ISUBSYSTEM CONFIGURATION REPORT

Explanation: This message reports subsystem configurations by providing the following information:

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0025ISUBSYSTEM USER CONFIGURATION REPORT

Explanation: This message reports the multiple database function (MDBF) subsystem user configurations. For each defined subsystem user, an assigned subsystem user ordinal number, the subsystem user name, the parent subsystem name, and the status of the subsystem are reported.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0026TVOLUME vol ON ccud IS IPL VOLUME: NOT FOUND IN KEYPOINT 0

Where:

vol
The volume label.

ccud
The subsystem IPL device unit address.

Explanation: This message indicates the failure of the disk roll call phase to identify the subsystem IPL device.

System Action: The IPL procedure is ended with a storage dump.

User Response: Do the following:

  1. Verify that the correct device is being IPLed.
  2. Have your system programmer verify that the IPL device is defined in keypoint 0.

See TPF Main Supervisor Reference for more information.

IPLB0026IVOLUME vol ON ccud IS IPL VOLUME: SYSTEM PRIME

Where:

vol
The volume label.

ccud
The subsystem IPL device unit address.

Explanation: This message indicates the subsystem IPL device status at the disk roll call phase.

System Action: IPL processing is continued.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0026IVOLUME vol ON ccud IS IPL VOLUME: SYSTEM PRIME DUPLICATE

Where:

vol
The volume label.

ccud
The subsystem IPL device unit address.

Explanation: This message indicates the subsystem IPL device status at the disk roll call phase.

System Action: IPL processing is continued.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0026IVOLUME vol ON ccud IS IPL VOLUME: NEITHER SYSTEM PRIME NOR DUP

Where:

vol
The volume label.

ccud
The subsystem IPL device unit address.

Explanation: This message indicates the subsystem IPL device status at the disk roll call phase.

System Action: IPL processing is continued.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0026IVOLUME vol ON ccud IS IPL VOLUME: LOADER GENERAL FILE

Where:

vol
The volume label.

ccud
The subsystem IPL device unit address.

Explanation: This message indicates the subsystem IPL device status at the disk roll call phase.

System Action: IPL processing is continued.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0026IVOLUME vol ON ccud IS IPL VOLUME: NOT FOUND IN KEYPOINT V

Where:

vol
The volume label.

ccud
The subsystem IPL device unit address.

Explanation: This message indicates the subsystem IPL device status at the disk roll call phase.

System Action: One of the following occurs:

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0027ASPECIFY U TO CONTINUE, T TO TERMINATE, ... OR RE-IPL

Explanation: This message is issued for one of the following reasons:

Also see the IPLB0020I message.

System Action: Depends on your response.

User Response: Use one of the following responses:

U
To continue.

T
To end with a storage dump.

Re-IPL
If a storage dump is not required.

See TPF Main Supervisor Reference for more information.

IPLB0028TINSUFFICIENT STORAGE FOR DISK ROLL CALL

Explanation: IPL was unable to complete because insufficient storage was available. Since this message occurs early in the IPL process, there is probably a substantial mismatch between the storage required for IPL and the amount of storage available.

System Action: A system error is issued to the system printer and then the TPF system goes into a disabled wait state.

User Response: Do the following:

  1. Save the IPL dump for later problem determination. After saving the dump, you can create more storage for use during IPL.

    IPL cannot use storage that is being used for virtual file access (VFA) buffers and system tables that survive across an IPL. You should retry the IPL by using the hardware console. An IPL from the hardware console throws away tables that have a correct image on DASD, freeing this memory for IPL. No data is lost on a hardware IPL. If the hardware IPL also ends in the IPLB0028T message, then you should retry the hardware. IPL the TPF system by using the CLEAR STORAGE option on the hardware console.

    Note:
    If the CLEAR STORAGE option is used and VFA has delay file pending buffers, then the contents of the buffers is lost.
  2. Have your system programmer determine the cause of the error and correct it.

IPLB0029ARDY A PRINTER FOR DUMP

Explanation: The IPL program requires the system printer to be ready for the dump.

System Action: The dump is resumed when the printer ready signal is received.

User Response: Make the system printer ready.

See TPF Main Supervisor Reference for more information.

IPLB0030TIPL DUMP ENDED

Explanation: The IPL completed a dumping storage to the system printer.

System Action: The TPF system is set to a disabled wait state.

User Response: Have your system programmer determine the cause of the error and correct it.

IPLB0031IIPL PROGRAM CALLING CTIN

Explanation: This message is sent to notify you when the IPL program completes the IPL functions.

System Action: System control is given to the nucleus initialization program.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0032INO 328X PRINTER IS OPERATIONAL -- RESTART CONTINUES

Explanation: In a TPF system generated with 3270 native console support, IPLB found all printers specified as eligible for the system receive-only (RO) (see the ROCRS parameter on the SIP CRASTB macro) to be non-operational.

System Action: The system RO is marked as not valid in the line status table. All message issued during restart are sent to the system prime computer room agent set (PRC) and are not duplicated to the system RO.

User Response: When the TPF system reaches 1052 state, enter the ZACRS command to assign a system RO. In addition, you should check the hardware configuration.

See TPF Main Supervisor Reference for more information.

IPLB0033AREAD FAILURE ON SYSTEM CONSOLE -- IPL CONTINUING ON THIS DEVICE

Explanation: After sending a message to the system console, which requires a response, IPLB is not able to read data from it successfully.

System Action: IPLB forces selection of an alternate console (as specified in the PRCRS parameter on the SIP CRASTB macro) to which it will send the IPLB0033A message. IPL is continued on the new console.

User Response: Respond to the original message on the new console and check the hardware configuration to determine the cause of the console failure.

See TPF Main Supervisor Reference for more information.

IPLB0034WDURING LOAD OF CORE IMAGE RESTART AREA, DUPLICATE MODULES WERE USED.

Explanation: Loading of the core image restart area (CIMR) was completed by using the duplicate of the prime modules for a CIMR. An error condition with the prime module copy was detected and the load continued with the duplicate module for this CIMR.

System Action: The IPL is completed.

User Response: This message is followed by the IPLB0027A message to continue or end the IPL.

The IPLB0086E message was previously displayed to the console stating the error condition, volume number, device and record address. The record that failed should be checked and corrected as necessary.

See TPF Main Supervisor Reference for more information.

IPLB0035TLOGIC ERROR -- FIELD INVALID IN I/O WKBLOCK: OPERATION TYPE

Explanation: The IPL program does not recognize a value in the operation type field of an input/output (I/O) block.

System Action: The dump routine is invoked by the IPLB and the IPL is ended.

User Response: IPL the TPF system again. If you cannot IPL the TPF system, see your system programmer for more information. Save the console and the dump because your IBM service representative may request this information.

See TPF Main Supervisor Reference for more information.

IPLB0036ASPECIFY OPTION (C: CANCEL R: REPLACE)

Explanation: This form of the IPLB0036A message is issued after the IPLB0041W message is sent. You must cancel the assignment or override the current assignment.

System Action: If C (Cancel) is specified, the IPLB0040A message displays.

If R (Replace) is specified, the TPF CPU ID X is given to the IPLed processor at the end of restart, and the loosely coupled processor status keypoint (CTKI) is updated to reflect the status.

User Response: Use one of the following responses:

C
To cancel and reassign to the TPF CPU ID.

R
To override the current assignment.
Note:
The processor being replaced must be manually inoperative.

See TPF Main Supervisor Reference for more information.

IPLB0036ASPECIFY OPTION (C: CANCEL B: BYPASS)

Explanation: This form of the IPLB0036A message is issued after the IPLB0042W message is sent. You must cancel the assignment or override the current assignment.

System Action: If C (Cancel) is specified, the IPLB0040A message displays.

If B (Bypass) is specified, the TPF CPU ID X is given to the IPLed processor at the end of restart, and the loosely coupled processor status keypoint (CTKI) is updated to reflect the status.

User Response: Use one of the following responses:

C
To cancel and reassign to TPF CPU id.

B
To override the current assignment.
Note:
The processor being bypassed must be manually inoperative.

See TPF Main Supervisor Reference for more information.

IPLB0038IKEYPOINT INDICATES THIS IS NOT THE FIRST PROCESSOR TO BE IPLED IN A L/C COMPLEX.

Explanation: Keypoint I indicates there is another processor active in the loosely coupled complex. This message is always accompanied by the IPLB0147A message. See the IPLB0147A message for a further explanation of this message.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0039ITHE IPL BYPASS FUNCTION HAS BEEN INVOKED. THIS WILL DESTROY THE L/C COMPLEX.

Explanation: You replied with a D to the IPLB0147A message. This message is always accompanied by the IPLB0048A message. Refer to the IPLB0048A message for a further explanation of this message.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0040ASPECIFY TPF CPU ID

Explanation: The TPF IPL program requested that you assign a CPU ID to the IPLed processor to couple into the loosely coupled complex.

System Action: Based on the processor status and the specified TPF CPU ID, one of the following messages displays:

User Response: Refer to each message section for I, E type messages.

See TPF Main Supervisor Reference for more information.

IPLB0041WTPF CPU ID x ACTIVE ON PROCESSOR serial

Where:

x
A TPF CPU ID.

serial
The CPU machine serial number.

Explanation: The IPL program determined that the TPF CPU ID referenced in the message was assigned to an active loosely coupled processor whose CPU machine serial number is as indicated in this message.

System Action: A message displays prompting you to:

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0042WTPF CPU ID x RESERVED BY PROCESSOR serial SPECIFY OPTION (C: CANCEL B: BYPASS)

Where:

x
A TPF CPU ID.

serial
A CPU machine serial number.

Explanation: The TPF CPU ID referenced in the message was assigned to a loosely coupled inactive processor whose machine serial number is as referenced in this message.

System Action: A message displays prompting you to cancel or override the current assignment.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0043ITPF CPU ID x ERRONEOUSLY ACTIVE: ASSIGNED TO -- serial

Where:

x
A TPF CPU ID.

serial
A CPU machine serial number.

Explanation: The IPL program detected a condition that the loosely coupled processor status keypoint record (CTKI) contains a processor status entry that is not valid for the TPF CPU ID referenced in the message. There is no physical processor coupled to the ID, however, the active indicator is on erroneously.

System Action: The condition is cleared by the IPL program and the specified TPF CPU ID is assigned to the IPLed processor. The new status is reflected in the CTKI at restart time.

User Response: Have your system programmer check the processor DEACTIVATION procedure when the CPU with the machine serial number referenced in the message was removed from the loosely coupled complex. From another active loosely coupled processor, the current TPF CPU ID assignments must be verified.

See TPF Main Supervisor Reference for more information.

IPLB0044ITPF CPU ID x COUPLING PROCEEDING ON PROCESSOR serial MODEL model CPA cpa

Where:

x
A TPF CPU ID.

serial
A CPU machine serial number.

model
A four character CPU model number.

cpa
The CPU address (for example CPU A in a loosely coupled complex).

Explanation: When the IPL program continues the processing, this message displays indicating the TPF system coupling intention. The final decision is made during the restart phase. If coupled successfully, the TPF CPU ID referenced in the message is coupled to the IPLed CPU (the machine serial number and the CPU model referenced in the message).

System Action: IPL processing is continued.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0045ICPU ID x OPERATION TO BE CONTINUED ON PROCESSOR serial MODEL--model

Where:

x
A TPF CPU ID

serial
A CPU machine serial number.

model
A four character CPU model number.

Explanation: The IPLed CPU was coupled to the loosely coupled complex. The same TPF CPU ID is assigned automatically to the IPLed CPU (the machine serial number referenced and the CPU model referenced in the message). The loosely coupled processor status keypoint record read by the IPL program indicates that this CPU machine serial number is coupled to the TPF CPU ID referenced in this message in the record.

System Action: Normal coupling is continued with the IPLB0044I message.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0046ITPF CPU ID x OPERATION TO BE RESUMED ON PROCESSOR serial MODEL model

Where:

x
A TPF CPU ID.

serial
A CPU machine serial number.

model
A four character CPU model number.

Explanation: The IPLed CPU with the machine serial number and CPU model referenced in this message is to be reactivated with a TPF CPU ID referenced in this message. The CPU was deactivated and removed from the loosely coupled complex previously but the TPF CPU ID was reserved for this processor.

System Action: Normal coupling is continued with the IPLB0044I message.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0048ASPECIFY THE WORD BYPASS TO CONTINUE OR T TO TERMINATE

Explanation: You replied D to the IPLB0147A message. This message double checks the accuracy of that reply. It ensures that you are aware that the loosely coupled complex will be destroyed.

System Action: IPL program follows your specification.

User Response: Use one of the following responses:

BYPASS
To continue destruction IPL.

T
To end the IPL.

See TPF Main Supervisor Reference for more information.

IPLB0049TUNABLE TO READ KEYPOINT I

Explanation: The TPF IPL program failed to read the loosely coupled processor status keypoint record (CTKI).

System Action: IPL processing is ended with a storage dump.

User Response: Review the previous IPLB error messages, which indicate the type of errors.

If this is a software error, do the following:

  1. Load keypoint I again with the correct record ID (CK).
  2. IPL the TPF system again.

See your system programmer or IBM service representative if this message is accompanied by the IPLBB004E message.

The pack may be remounted at another device or the basic subsystem (BSS) IPL device selected again. In this case, you must IPL the TPF system again.

See TPF Main Supervisor Reference for more information.

IPLB0050TUNABLE TO READ BSS VOL

Explanation: A hardware error was detected when the IPL program read the basic subsystem (BSS) IPL device volume label.

System Action: IPL is ended with a storage dump.

User Response: Review the previous IPLB error messages, which indicate the type of errors.

See your system programmer or IBM service representative to determine the source of the hardware error.

The pack may be remounted on another device or the basic subsystem (BSS) IPL device selected again. In this case, you must IPL the TPF system again.

See TPF Main Supervisor Reference for more information.

IPLB0051EUNABLE TO READ SS VOL. SPECIFY RETRY DEV

Explanation: A hardware error was detected when the IPL program read the subsystem IPL device volume label.

System Action: The IPLB0004A message is sent following this message.

User Response: Review the previous IPLB error messages, which indicate the type of errors.

If the multiple database function (MDBF) IPL can be continued without the subsystem, the next subsystem can be defined by the IPLB0004A message.

See your system programmer or IBM service representative to determine the source of the error.

The pack may be remounted at another device or the subsystem IPL device selected again at the next IPLB0004A message.

See TPF Main Supervisor Reference for more information.

IPLB0052TBSS IPL VOLUME VOL UNMATCH. ccud vol volser

Where:

ccud
The basic subsystem (BSS) device unit address.

vol
The two alphabetic characters of the CTKV volume label.

volser
The IPL device volume serial number (VSN).

Explanation: The two characters of the BSS IPL device volume label do not match the characters in the CTKV label.

System Action: The IPL is ended with a storage dump.

User Response: Verify that the BSS IPL device address was specified correctly.

If the BSS IPL device was specified correctly, see your system programmer to correct CTKV. A bypass volume label checking option can be used if the BSS can be included. The message displays the two volume labels that should be checked.

See TPF Main Supervisor Reference for more information.

IPLB0053ESS IPL VOLUME VOL UNMATCH. ccud vol volser

Where:

ccud
The subsystem IPL device unit address.

vol
The two character alpha portion of the volume label specified in keypoint V (CTKV).

volser
The subsystem IPL device volume label.

Explanation: The first two characters in the subsystem device volume label do not match those in keypoint record V (CTKV).

System Action: The subsystem is not included or purged from the MDBF configuration.

If the IPL was software initiated, the processing is continued.

If you initiated the IPL, the IPLB0004A message displays.

User Response: Verify whether the specified subsystem IPL device address was correct or not.

If the SS IPL device was specified correctly, have your system programmer to correct keypoint V.

A bypass volume label checking option can be used if the subsystem can be included.

The message indicates two volume labels to be checked.

See TPF Main Supervisor Reference for more information.

IPLB0054ESS IPL DEV ccud1 PREVIOUSLY DEFINED AT DEV ccud2: IGNORED

Where:

ccud1
The IPL device unit address.

ccud2
The device unit address.

Explanation: A subsystem where the IPL device on the address referenced in the message has the same volume label as another subsystem that was defined previously. The same volume label was found at device unit address referenced in this message.

System Action: The current subsystem for which the IPL device unit address referenced in the message is not included in the MDBF configuration. The next MDBF definition is initiated with the IPLB0004A or IPLB0009A messages.

User Response: Correct the duplicate volume label condition.

To include both subsystems, the volume label on one of the packs must be changed. If the volume label is changed, the alphabetic portion must be changed in keypoint record V or the Bypass Vol Label option is required on the next IPL.

See TPF Main Supervisor Reference for more information.

IPLB0055TUNABLE TO READ BSS KEYPOINT RECORDS. IPL TERMINATED.

Explanation: IPLB failed to read the basic subsystem (BSS) keypoint records due to hardware or software errors.

System Action: The IPL procedure is ended with a storage dump.

User Response: Review the previous IPLB error messages, which indicate the type of errors.

If this is a software error, do the following:

  1. Load the keypoint records again with the correct record ID (CK) or, if applicable, another fallback keypoint extent can be retried to bring the TPF system to check the problem.
  2. Mount the pack again at other devices or reselect the BSS IPL device.
  3. IPL the TPF system.

See your system programmer or IBM service representative, especially if this message is accompanied with the IPLBB004E message.

See TPF Main Supervisor Reference for more information.

IPLB0056EUNABLE TO READ SS KEYPOINT RECORDS. SS IS PURGED.

Explanation: IPLB failed to read the subsystem keypoint records due to hardware or software error reasons.

System Action: The subsystem is not included in the multiple database function (MDBF) configuration. The next definition is initiated with the IPLB0004A message or the IPLB0009A message for an IPL you initiated.

For the software-initiated IPL, the subsystem is excluded from the MDBF configuration and the next subsystem is obtained from the MDBF configuration keypoint record.

User Response: Review the previous IPLB error messages, which indicate the type of errors.

If a software error, the subsystem keypoint records must be loaded again with the correct record ID (CK).

If you initiated the IPL, the pack may be mounted on another device followed by another IPL.

If retry at another device is necessary for the software-initiated IPL, IPL and define each subsystem.

See your system programmer or IBM service representative, especially if this message is accompanied by the IPLB0004A message.

See TPF Main Supervisor Reference for more information.

IPLB0058EEXPECTED VOL volser1 ON DEV ccud, FOUND volser2

Where:

volser1
The volume label expected.

ccud
The device unit address.

volser2
The volume label found on device unit address.

Explanation: A software-initiated or FAST IPL detected that the volume label referenced in the message was found on the subsystem IPL device referenced in this message. According to keypoint M (CTKM) the TPF system expected to find volume volser1 at this address.

System Action: If this is the basic subsystem (BSS) IPL volume, an IPL dump is taken and the IPL is ended with a disabled wait PSW.

If this is a multiple database function (MDBF) subsystem IPL volume, the subsystem is purged from the MDBF configuration and the IPL is continued with the next subsystem.

User Response: You must IPL the TPF system to include the missing subsystem.

Review the previous IPL log and deactivation history. If the IPL was due to an irrecoverable error, review the system error dump to be sure that keypoint M (CTKM) is valid. (keypoint M is defined by the MK0CK data macro.)

If the IPL was due to an explicit FAST IPL, then either the previous subsystem deactivation was not completed properly or the status of the BSS prime module changed since the previous IPL. This affects the CTKM that saves the address of the IPL device used. For example, if you take the prime module offline, CTKM shows the duplicate module as the IPL device. If you bring the prime module back online, CTKM shows the prime module as the IPL device, even though it was not necessarily the IPL device used. Therefore, when using the FAST IPL option, IPL the BSS prime module if it was online when the TPF system went down.

If you must IPL a different volume serial number (VSN) than that saved in Keypoint M (CTKM) by the previous IPL, do the following:

  1. IPL the TPF system by using the CLEAR option (hardware). The IPLB0001A message displays.
  2. Select the U option to include the MDBF subsystems.

See TPF Main Supervisor Reference for more information.

IPLB0059TINSUFFICIENT STORAGE FOR KEYPOINT RECORDS LOADING

Explanation: During a loading of subsystem keypoint records, the available remaining storage is insufficient for continued processing.

System Action: The IPL procedure is ended with a storage dump.

User Response: Do the following:

  1. Decrease the number of subsystems to be included in the re-IPL.
  2. IPL the TPF system again.

Have your system programmer check the valid number of maximum allowable subsystems in the MDBF configuration keypoint record (CTKM) and storage requirements for each subsystem.

See TPF Main Supervisor Reference for more information.

IPLB0060ECANCEL SS INVALID CCUD

Explanation: The subsystem IPL device unit address was not valid.

System Action: The IPLB0004A or IPLB0009A message displays requesting further action by you.

User Response: Reply cancel with a valid subsystem IPL device unit address.

See TPF Main Supervisor Reference for more information.

IPLB0061EMAX SS EXCEEDED

Explanation: The number of subsystems you defined exceeded the maximum allowed.

System Action: The definition that exceeded the maximum allowable subsystem number is not included. The IPL program internally generated an End Of Definition.

User Response: Check the validity of the maximum allowable number of subsystems in the multiple database function (MDBF) configuration keypoint record.

See TPF Main Supervisor Reference for more information.

IPLB0062WSUBSYSTEM ccud status

Where:

ccud
The subsystem IPL device unit address.

status
One of the following:

Explanation: This error message informs you of the status of the subsystem.

System Action: Based on the status of the subsystem:

PURGED
The subsystem was purged and the IPL process is continued without the subsystem included.

WARNED
You must take action if the IPL continues as is.

UNACCEPTABLE
The subsystem is purged.

User Response: Correct the status of the subsystem by fixing the problem reported by a previous error message.

See TPF Main Supervisor Reference for more information.

IPLB0063WSTATUS TRACK INITIALIZATION FAILED ON DEVICE ccud

Where:

ccud
The device address.

Explanation: A 3990 Record Cache Subsystem (RCS) device could not be brought online because an unrecoverable error occurred while trying to re-initialize the RCS subsystem global status information.

If, during IPL, the attached RCS DASD configuration changed or if the RCS controller was unable to determine the subsystem status, the TPF system issues a diagnostic control channel command word (CCW) command to re-establish the global subsystem status information in order to bring the affected devices online to the TPF system. This message is issued when the diagnostic control CCW command recovery operation fails the affected device.

System Action: The device remains offline to the TPF system.

User Response: Do the following:

  1. Make sure the attached 3990 RCS devices are properly configured.
  2. Try to bring the device online by using the TPF DASD mount procedures after the problem is corrected.

See TPF Main Supervisor Reference for more information.

IPLB0064TSERVICE PROCESSOR FAILED.

Explanation: The service processor was not operational.

System Action: The IPL procedure is ended with a storage dump.

User Response: See your IBM service representative to determine why the service processor is not operational.

IPLB0065TIPL LOGIC ERROR -- CC2 FROM SERVICE PROCESSOR REQUEST.

Explanation: A service processor request is initiated while a prior request is pending. Since IPL processes service processor requests sequentially, this is a logic error.

System Action: The IPL procedure is ended with a storage dump.

User Response: IPL the TPF system again. If the problem continues, see your system programmer for more information. Save the console and the dump because your IBM service representative may request this information.

IPLB0066IIPL WAITING FOR RESPONSE FROM SERVICE PROCESSOR.

Explanation: This is a reminder that the IPL is not hung but is waiting for a response to a service processor request.

System Action: This message is repeated every 5 seconds until the service processor responds.

User Response: If the IPL does not proceed beyond this message in a reasonable amount of time, IPL the TPF system again.

If the problem occurs repeatedly, see your IBM service representative to determine whether there is a problem with the service processor.

IPLB0067TIPL LOGIC ERROR -- UNEXPECTED EXTERNAL INTERRUPT.

Explanation: An unexpected external interrupt was received.

System Action: The IPL procedure is ended with a storage dump.

User Response: Check the dump to determine the cause of the external interrupt.

IPLB0068TSERVICE PROCESSOR ERROR. RETURN CODE IS retcode

Where:

retcode
The return code.

Explanation: An error return code was returned from the service processor.

System Action: The IPL procedure is ended with a storage dump.

User Response: See your IBM service representative to determine why the service processor returned the error return code.

IPLB0071WLOCKING NOT AVAILABLE ON ANY CUS

Explanation: In a loosely coupled environment, IPL detected that no TPF online modules were accessed through control units, which have the limited lock facility (LLF) RPQs installed.

System Action: IPL processing is continued in uniprocessor mode.

User Response: If loosely coupled processing is not intended, no actions are required. If loosely coupled processing is intended, your system programmer and IBM service representative should be consulted.

Channel-control unit connections should be checked and keypoint record 0 (CTK0) should be verified.

See TPF Main Supervisor Reference for more information.

IPLB0072WLOCKING MISSING WITH CU ccud

Where:

ccud
The online module device unit address.

Explanation: In a loosely coupled TPF system, an online online module at the address referenced in the message was accessed without the limited lock facility (LLF).

System Action: The IPL procedure is continued as uniprocessor mode.

User Response: If loosely coupled processing is not intended, no actions are required.

If loosely coupled processing is intended, your system programmer or IBM service representative should be consulted to verify the interface and the data of keypoint record 0 (CTK0).

See TPF Main Supervisor Reference for more information.

IPLB0073EI/O ERROR ON READING LLF AT ccud

Where:

ccud
The online module device unit address.

Explanation: A hardware error was detected at the limited lock facility (LLF) RPQ when accessing a TPF online module at the address referenced in the message.

System Action: The IPL procedure is continued as uniprocessor mode.

User Response: See your system programmer or IBM service representative to check the error status that was reported by the preceding IPLBB004E message.

See TPF Main Supervisor Reference for more information.

IPLB0074TINCONSISTENT INTERFACE IDS: DEV ccud1 ID xx VS DEV ccud2 ID yy

Where:

ccud1
The device unit address.

xx
The interface ID.

ccud2
The device unit address.

yy
The interface ID.

Explanation: The IPL program detected two different interface IDs -- ID xx at device ccud1 and ID yy at device ccud2.

System Action: The IPL processing is ended with a storage dump.

User Response: Do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0076EINVALID TPF CPUID

Explanation: In a loosely coupled TPF system, the assigned CPU ID is not found in a keypoint record I.

System Action: The IPLB0040A message is issued again.

User Response: A valid CPU ID must be assigned to the IPLed CPU.

See TPF Main Supervisor Reference for more information.

IPLB0077ECTKM UNQUALIFIED -- IPLED BSS ONLY

Explanation: You performed a FAST IPL or TPF software IPL before the multiple database function (MDBF) configuration keypoint record was initialized.

System Action: The IPL processing is continued with only a basic subsystem (BSS).

User Response: To initialize the MDBF configuration keypoint record, define define a MDBF subsystem configuration at the first IPL time after TPF system generation or after a fresh keypoint M is loaded.

See TPF Main Supervisor Reference for more information.

IPLB0078TOTHER PROCESSOR ACTIVE. UNIPROCESSING FAILED

Explanation: Another processor is active so the uniprocessing failed.

System Action: A system error is issued and a dump is sent to the system printer. Then, the TPF system goes into a disabled wait state.

User Response: Do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0079WCU ccud SUBSYSTEM STORAGE INIT TIMEOUT, CACHING DEACTIVATED

Where:

ccud
The address of the failing control unit.

Explanation: A caching control failed to initialize properly. All devices on the control unit are placed in DIRECT (uncaching) mode.

System Action: The TPF system uses the modules in DIRECT mode.

User Response: Check the failing control unit for hardware problems. If necessary, copy the modules from the failing control unit to a functional caching control unit.

See specific diagnostics for the failing control unit in the applicable control unit description manual.

See TPF Main Supervisor Reference for more information.

IPLB0080WZBUFC ALLOCATE IMPLEMNT RC FUNCTION PENDING

Explanation: A prior ZBUFC command was entered to implement pending cache allocation changes for all 3880 Record Cache Control Units but the operation did not complete on the requesting TPF processor.

System Action: No action is performed. The record cache allocations remain the same as they were at the time the requesting TPF processor went down.

User Response: Enter another ZBUFC ALLOCATE command with the IMPLEMENT parameter specified after 1052 state to complete the cache allocation changes. Use either the new (target) or old (current) allocation ratio values.

See TPF Operations for more information about the ZBUFC ALLOCATE command. See TPF Main Supervisor Reference for more information.

IPLB0081EVOL SER RANGES DEFINED IN CTKV OVERLAP

Explanation: This message is issued when the IPL program detects that the volume serial number (VSN) ranges defined in keypoint record V for the different device types overlap.

System Action: If processing is for the basic subsystem (BSS), the IPL procedure is ended with a storage dump.

If processing is for a subsystem, the subsystem is purged and the IPLB0023I message is issued.

User Response: Have your system programmer correct the keypoint record.

See TPF Main Supervisor Reference for more information.

IPLB0082xVOL volser, MODULE mod, DUPLICATE REAL TIME PACKS ccud1 AND ccud2

Where:

x
T, if a basic subsystem (BSS) or E, if a subsystem.

volser
The volume label (six characters).

mod
The symbolic module number.

ccud1
The device unit address.

ccud2
The device unit address.

Explanation: IPL program detected a TPF pack that has the volume label referenced in the message at the second address referenced in the message. The same volume label was found previously at the first address referenced in the message.

System Action: If the volume label is of the BSS, the IPL procedure is ended with a storage dump.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0085TNO DISK ADDRS IN KPT 0: CANNOT START ROLL CALL

Explanation: The DASD configuration keypoint record CTK0 is not valid.

System Action: The IPL procedure is ended with a storage dump.

User Response: Have your system programmer load a correct keypoint record 0.

See TPF Main Supervisor Reference for more information.

IPLB0086EVOLUME volser ON CCUD -- cccchhhhrr -- error IN rtype CHAIN

Where:

volser
The volume serial number (VSN) or UNKNOWN. (UNKNOWN may appear when an error occurs on the first restart record or a keypoint record prior to reading the IPL VSN or building the subsystem cross-reference table.)

cccchhhhrr
The cylinder, head, or record. Keypoints use a seven digit CCUD address while restart chains use a six digit CCUD address. (When reading a volume serial number (VSN) or verifying the limited lock facility (LLF), this field is zero.)

error
The error description, which can be one of the following:

rtype
The record type, which can be one of the following:

TPF
The control program load failure.

A P
The resident E-type program load failure.

ICDF
The ICDF program load failure.

ACPL
The ACPL program load failure.

FCTB
The FACE table load failure.

SIGT
The SIGT table load failure.

RIAT
The RIAT table load failure.

IPAT
The IPAT table load failure.

For single unchained records, the record type can be one of the following:

KEYPOINT
The keypoint record read failure.

RECORD #1
The first restart record read failure.

Explanation: This message tries to identify the reason for the DASD read error.

System Action: The IPL procedure is ended if the error occurred on a critical record (IPAT, ICDF, ACPL) or other basic subsystem (BSS) records (Keypoint records, resident E-type program, file address compute program (FACE) table).

In other cases, the IPL procedure is continued without subsystems that encountered the error.

User Response: See your system programmer or IBM service representative if the message is accompanied by the IPLBB004E message.

See TPF Main Supervisor Reference for more information.

IPLB0087TPROGRAM CHECK: PSW IS psw INTERRUPT CODE IS code

Where:

psw
The eight byte PSW.

code
The two byte interrupt code.

Explanation: Whenever the dump routine of the IPL program is called, the OLD PSW program is examined to determine whether a program check occurred. If so, this message displays.

System Action: The IPL is ended with a dump.

User Response: Do the following:

  1. Have your system programmer review the system error dump.
  2. Take the necessary corrective action.
  3. IPL the TPF system again.

See TPF Main Supervisor Reference for more information.

IPLB0088TCHANNEL CHECK THRESHOLD EXCEEDED. IPL TERMINATED.

Explanation: CIO alerted IPLB that the allowable limit of channel check errors was exceeded.

System Action: The IPL is ended with a dump.

User Response: The IPLB0088T message is usually preceded by input/output (I/O) error messages indicating the failing device and the nature of the error. If not, review the CIO I/O trace table in the IPL dump to determine the failing device. Then, try to IPL the TPF system again.

If the problem continues, see your system programmer or IBM service representative to correct the problem.

See TPF Main Supervisor Reference for more information.

IPLB0089WVSN DISCREPANCY ON THE FOLLOWING CHPIDS FOR ssss: CHPID cc -- VSN vvvvvv, CHPID cc -- VSN vvvvvv

Where:

ssss
The channel path IDs (CHPIDs).

cc
The CHIPD.

vvvvv
The volume serial number.

Explanation: IPLB tries to verify all paths to the real-time module with the symbolic device address (SDA) for the channel path IDs (CHPIDs) referenced in the message. This error message occurs when there is a discrepancy in the volume serial number (VSN) on two different channel paths. The message displays the CHPID and VSN from each path. The program assumes the first CHPID and VSN pair to be correct.

System Action: IPLB disables the channel path associated with the second CHPID and continues with the IPL.

User Response: This error indicates the presence of a cabling error, a switching error, or both. When the problem is corrected, enter the ZPATH command to bring the path back online.

See TPF Operations for more information about the ZPATH command. See TPF Main Supervisor Reference for more information.

IPLB0090EPRIMARY | DUPLICATE MODULE mod OFFLINE IN MFST | IS IN COPY STATE SS IPL DEV ADDR ccud, VOL volser

Where:

mod
The symbolic module number.

ccud
The subsystem IPL device unit address.

volser
The subsystem IPL device volume label.

Explanation: When IPL loads the core image restart area (CIMR), a copy state or offline condition for either the system primary module or duplicate module was detected from the module file status table (MFST).

System Action: If the module in error is duplicated, loading is continued from the duplicated module by the IPL program.

If the duplicated module is not available, or not configured, the IPL procedure is ended if a basic subsystem (BSS) or the subsystem is purged and the IPL is continued if non-BSS.

User Response: To IPL BSS or include a subsystem, at least the primary or prime duplicate module must be available.

See TPF Main Supervisor Reference for more information.

IPLB0091EKPT V DOES NOT CONTAIN ANY VOLUME SERIAL NUMBERS

Explanation: The basic subsystem (BSS) or a subsystem keypoint V (CTKV) does not contain an online module volume number.

System Action: If the condition was found for the BSS, the IPL procedure is ended with a storage dump.

If the condition is for a subsystem, the subsystem is purged and the IPLB0023I message displays.

User Response: Have your system programmer load the correct keypoint V.

See TPF Main Supervisor Reference for more information.

IPLB0092EIPL DEVICE ccud IS IN COPY STATE (SYSTEM PRIME | SYSTEM PRIME DUPLICATE)

Where:

ccud
The subsystem IPL device unit address.

Explanation: Keypoint 6 indicates that the IPL volume (either the prime or prime duplicate) is in dup-update copy state. The indicator in keypoint 6 (CTK6) is set by the ZMCPY UP command.

System Action: The IPL continues on the duplicate module, if available. If the duplicate module is not available, the IPL is ended with a dump. If this is a multiple database function (MDBF) subsystem and the duplicate module is not available, the subsystem is purged and the basic subsystem (BSS) IPL is continued.

User Response: If the duplicate module is available, the IPL is continued and no response is necessary.

If the IPL is ended, the TPF system must be IPLed again after the problem is corrected.

Have your system programmer review the system error dump and the previous IPL log to determine the validity of CTK6 and the IPL volume.

If a ZMCPY UP copy was in progress, another volume should be used for the IPL (for example, the duplicate of the volume being IPLed). You can then enter a ZMCPY RESTART command to resume the ZMCPY UP copy.

See TPF Main Supervisor Reference for more information.

IPLB0093WCACHING CU ccud SUBSYSTEM STORAGE UNAVAILABLE, CACHING DEACTIVATED.

Where:

ccud
The control unit address.

Explanation: An attempt to make record cache subsystem storage available to the subsystem failed. The licensed internal code detected irrecoverable equipment checks or bit failures that cannot be corrected.

System Action: The TPF system may display sense data but continues the IPL.

User Response: See your system programmer or IBM service representative to solve the problem.

The device address identifies the failing storage director. The SENSE data, if presented, may indicate the reason for failure.

After the problem is corrected, do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0094WCACHING CU ccud UNABLE TO INITIALIZE CACHE, CACHING DEACTIVATED

Where:

ccud
The address of the failing control unit.

Explanation: In the channel command word (CCW) chain to initialize cache, either the CCW to initialize all interfaces or the CCW to deinitialize all interfaces failed.

System Action: The IPL is continued with the TPF system trying to place the failing storage director into DIRECT mode. The IPLB0096W message is issued.

User Response: See your system programmer or IBM service representative to solve the problem.

Check the data for the initialize CCW. If the data taken from keypoint 0 does not match the data in the initialized SD, then keypoint 0 could be in error. If the CCWs and data are valid, a licensed internal code or hardware problem could exist.

After the problem is corrected, do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0095WCACHING CU ccud HAS DIAGNOSTIC MODE SWITCH SET, CACHING DEACTIVATED.

Where:

ccud
The device address.

Explanation: As a result of a SENSE SUBSYSTEM STATUS command the DIAGNOSTIC MODE switch was detected as being set. This means the SD is not permitted to access the subsystem storage.

System Action: The IPL is continued.

User Response: Check the DIAGNOSTIC MODE switch. If the DIAGNOSTIC MODE switch is off, notify your system programmer or IBM service representative.

If the DIAGNOSTIC MODE switch is on, check with your system programmer and IBM service representative as to why and it may be returned to service.

After the problem is corrected, do one of the following:

See TPF Main Supervisor Reference for more information.

IPLB0096WACTIVATE CACHING FAILED FOR DEVICE ccud, VSN volser.

Where:

ccud
The device address.

volser
The volume serial number (VSN).

Explanation: This message is issued when a SET SUBSYSTEM MODE command to activate caching (place a device in RECORD ACCESS MODE) fails. It is also issued when a device is placed in DIRECT MODE.

System Action: The IPL is continued.

User Response: See your system programmer or IBM service representative to solve the problem.

Determine whether the failure was caused by a hardware problem that may have been reported in other error messages. The SD may need to be MLed again.

See TPF Main Supervisor Reference for more information.

IPLB0097WDEVICE ccud MAY HAVE NON-RETENTIVE DATA ENABLED, CANNOT DISABLE.

Where:

ccud
The device address.

Explanation: The channel command word (CCW) command to DISABLE NON-RETENTIVE DATA failed. The state of non-retentive data is unknown.

System Action: The TPF system continues.

User Response: See your system programmer or IBM service representative. The failing CCW may be accompanied by sense data. This data may be useful in analysis. However, the TPF system does not support non-retentive data, so this failure should not disrupt the operation of the TPF system.

See TPF Main Supervisor Reference for more information.

IPLB0098WDEVICE ccud MAY HAVE NON-RETENTIVE ACCESS ALLOWED, CANNOT DISALLOW.

Where:

ccud
The device address.

Explanation: The channel command word (CCW) command to DISALLOW NON-RETENTIVE ACCESS failed. The state of non-retentive access is unknown.

System Action: The TPF system continues.

User Response: See your system programmer or IBM service representative. The failing CCW may be accompanied by sense data. This data may be useful in analysis. However, the TPF system does not support non-retentive access, so this failure should not disrupt the operation of the TPF system.

See TPF Main Supervisor Reference for more information.

IPLB0099EINVALID RESPONSE

Explanation: This message notifies that your previous response was not valid.

System Action: Request is repeated.

User Response: Reply in the correct format

See TPF Main Supervisor Reference for more information.

IPLB0121xVOL volser, MODULE mod, mfunc mstat mavail

Where:

x
The severity code for the message, which is one of the following:

E
The error code.

W
The warning code.

volser
The volume label.

mod
The symbolic module number.

mfunc
The module function, which is one of the following:

mstat
The module status, which is one of the following:

mavail
The availability of the duplicate volume, which is one of the following:

Explanation: IPLB disk roll call is reporting the status of a volume that was listed in keypoint V but is now physically unavailable or was taken offline during the previous IPL.

System Action: If the message is accompanied by a severity code of E, the subsystem is marked unacceptable. If the basic subsystem (BSS) is marked unacceptable, the IPL is ended automatically with a storage dump.

If the message is accompanied by severity code of W and a previously online module is not found, you are prompted through the IPLB0022A message at the end of disk roll call to do one of the following:

User Response: Verify the volume status and respond accordingly.

See TPF Main Supervisor Reference for more information.

IPLB0130IFARF ADDRESSING STAGE a/b DISPENSE MODE FARFc

Where:

a/b
The File Address Reference Format (FARF) addresses supported by the file address compute program (FACE) table. This is either FARF3 to FARF4 or FARF4 to FARF5.

c
The FARF addresses being dispensed. This is 3, 4, or 5.

Explanation: This is an informational message that is issued during restart indicating the active stage and the current dispense mode.

System Action: None.

User Response: None.

See the TPF Migration Guide: Program Update Tapes for more information about FARF migration.

IPLB0147ASPECIFY: N -- NORMAL IPL, D -- L/C DESTRUCT IPL AND SELECT IMAGE T -- TERMINATE, I -- NORMAL IPL AND SELECT IMAGE

Explanation: Keypoint I indicates that there is another processor active in the loosely coupled complex. This IPL can be a normal IPL (join the complex), a destruction IPL (destroy the loosely coupled complex), or the IPL can be ended.

Note:
If the image selection is desired, it must be specified when this message is first issued. This message is issued again allowing you to select the IPL type.

System Action: The IPL program follows your specification.

User Response: Use one of the following responses:

N
For a normal IPL.

D
For destruction IPL.

T
To end the IPL.

I
To indicate you should be prompted for image selection.

See TPF Main Supervisor Reference for more information.

IPLB0150IONE ENABLED IMAGE -- IMAGE SELECTION BYPASSED

Explanation: An image selection request failed. Only one image is enabled. Therefore, no other selections are available.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0151IPROCESSING CONTINUES WITH IMAGE nnnnnnnn

Where:

nnnnnnnn
The image name.

Explanation: All subsystems identify the enabled image during a hard IPL.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB0154AVALID IMAGE SELECTIONS image [status] [status]
  ·
  ·
  ·
SPECIFY IMAGE NAME

Where:

image
The name of a valid (enabled) image for selection.

status
Status of the image. This may consist of none, one, or both of the following:

PRIMARY
This denotes the primary image.

ACTIVE
This denotes the last active image for this processor. This image is used when no image is explicitly specified.

Explanation: This message prompts you for an image selection and provides you with a list of enabled images that are available for selection.

Note:
The default selection (achieved by pressing ENTER) is the last active image for the processor (if there is one).

System Action: IPL of the specified image occurs.

User Response: Specify one of the image names listed. If one of the listed images is marked as ACTIVE, then that image will be used if no image is specified. If none of the images are marked as ACTIVE, then a selection must be made.

See TPF Main Supervisor Reference for more information.

IPLB0155TUNABLE TO READ BSS CTKX RECORD. IPL TERMINATED.

Explanation: IPLB failed to read CTKX while trying to IPL another image because of hardware or software error reasons.

System Action: The IPL is ended.

User Response: Load CTKX with the proper record ID (X'00ED').

See TPF Main Supervisor Reference for more information.

IPLB0156TUNABLE TO READ IPLA CHAIN. IPL TERMINATED.

Explanation: IPLB failed to read IPLA while trying to IPL another image because of hardware or software error reasons.

System Action: The IPL is ended.

User Response: Load IPLA.

See TPF Main Supervisor Reference for more information.

IPLB0157ASPECIFY: I -- IMAGE SELECTION, B -- BYPASS SELECTION

Explanation: This message prompts you to specify whether or not to prompt for image selection if there is more than one image enabled.

If I is specified, you are prompted for image selection for each subsystem.

Note:
If I is specified and only one image is enabled in the TPF system, you are not prompted for an image name because the single, enabled image is used for the IPL.
If the you press Enter, the TPF system uses option B as the default.

If option B is selected, and there is no active image for the processor but there is more than one enabled image, you are prompted to provide an image name.

System Action: None.

User Response: Enter one of the following responses:

I
To prompt for image selection.

B
To bypass image selection.

See TPF Main Supervisor Reference for more information.

IPLB0160WRCS STATE CHANGE PENDING REPORTED ON DEVICE ccud. OPERATION WILL BE RETRIED xx TIMES AT yy SECOND INTERVALS BEFORE BEING ABANDONED.

Where:

ccud
The device address.

xx
The number of times the failing operation will be retried before recovery is abandoned.

yy
The time interval in seconds between retries.

Explanation: The record cache subsystem (RCS) controller rejected the DASD input/output (I/O) operation while performing a cache recovery function.

A state change interrupt will be presented when the controller is ready to accept I/O requests.

The TPF system will retry the failed operation the number of times indicated in the message before continuing the initial program load (IPL).

System Action: If the operation is abandoned due to retries being exhausted before the state change interrupt is received, IPL will flag the device as a dummy in the device address volume serial number (DAVSN) table and continue without it.

User Response: See your system programmer or your IBM service representative to determine the cause of the state change pending condition and to correct it. If the TPF system cannot be brought up without the lost device, IPL the TPF system again after the controller resumes normal operations.

IPLB00A0TLOGIC ERROR -- ZERO DEVICE ADDRESS

Explanation: IB08 tried to do a DASD input/output (I/O) operation to address 000.

System Action: IPLB will dump and is ended.

User Response: Try to IPL the TPF system again. If the condition continues, see your system programmer for more information.

Verify the contents of the I/O request block (WB0WB) passed to IB08, especially the device address field.

See TPF Main Supervisor Reference for more information.

IPLB00A1TLOGIC ERROR -- BAD CHANNEL ADDRESS

Explanation: IB08 tried to do a DASD input/output (I/O) operation to a channel address that is not valid.

System Action: IPLB will dump and is ended.

User Response: IPL the TPF system again. If the condition continues, see your system programmer for more information.

Verify the contents of the I/O request block (WB0WB) passed to IB08, especially the device address field.

See TPF Main Supervisor Reference for more information.

IPLB00A2TLOGIC ERROR -- BAD CCW POINTER

Explanation: IB08 tried to do a DASD input/output (I/O) operation to the channel command word (CCW) string pointer that is not valid.

System Action: IPLB will dump and is ended.

User Response: IPL the TPF system again. If the condition continues, see your system programmer for more information. Verify. the contents of the I/O request block (WB0WB) passed to IB08, especially the CCW string pointer field.

See TPF Main Supervisor Reference for more information.

IPLB00A3TLOGIC ERROR -- 2 I/Os TO SAME DEVICE, ADDRESS = ccud

Where:

ccud
The device address.

Explanation: The IPLB DASD input/output (I/O) routine, IB08, only supports one I/O operation outstanding to any one device. An attempt was made to start a second I/O operation to the device referenced in the message while the first operation was active.

System Action: IPLB will dump and is ended.

User Response: IPL the TPF system again. This is a logic error. If the condition continues and there are no local modifications to IPLB, save the console and the IPL dump. Then, see your IBM service representative.

See TPF Main Supervisor Reference for more information.

IPLB00A4TLOGIC ERROR -- SIOSC STACK OVERFLOW

Explanation: An internal table in IB08 overflowed.

System Action: IPLB will dump and is ended.

User Response: IPL the TPF system again. If the condition continues and there are no local modifications to the IPLB from your operations center or enterprise, save the console and the dump because your IBM service representative may request this information.

See TPF Main Supervisor Reference for more information.

IPLB00A5WI/O ERROR -- SUBCHANNEL LOGOUT, ADDRESS = ccud, TYPE = type

Where:

ccud
The device address associated with the input/output (I/O) interrupt that signaled the channel logout.

type
One of the following:

ICC
If an interface control check was received.

CDC
If a channel data check was received.

CCC
If a channel control check was received.

Explanation: The hardware channel took a temporary or permanent failure. IPLB does not save the information from the logout. The CCUD referenced in the message is the I/O address associated with the channel failure. This address indicates the channel involved. The device portion of the address may or may not be related to the channel failure. The types of channel logout correspond to bit settings in the channel status word byte 5.

System Action: None.

User Response: If the IPL continues without further incident, you can ignore this message.

If this message appears several times, in conjunction with other DASD I/O errors, or if the IPL cannot continue, fallback to backup hardware occurs. The failing channel address and the type of logout are provided in the message. This should be given to your IBM service representative if fallback was necessary.

See TPF Main Supervisor Reference for more information. See 370/XA Principles of Operation for more information.

IPLB00A6TI/O ERROR -- UNIT CHECK ON SENSE OPERATION, ADDRESS = ccud

Where:

ccud
The device address.

Explanation: A sense operation was initiated following a unit check on an input/output (I/O) operation to the CCUD address referenced in the message. The sense operation resulted in a second unit check. This second check should not occur.

System Action: A dump is issued and is ended.

User Response: IPL the TPF system again.

If the TPF system is still unable to IPL, verify that the address referenced in the message is an address that should be accessed by the TPF system and that the device is in working order. IPL the TPF system again.

If the TPF system is still unable to IPL, see your system programmer for more information. This should be a hardware error. Normal diagnostic operations should be run for the device referenced in this the message.

See TPF Main Supervisor Reference for more information.

IPLB00A7TPOSSIBLE GEN ERROR -- NO STORAGE AVAILABLE TO CARVE I/O TABLES

Explanation: There was insufficient storage available for the input/output (I/O) tables in IB08. IPLB resides in the area reserved for working storage. Working storage may have been generated too small or the processor being IPLed may have too little main storage for the TPF system being IPLed.

System Action: A diagnostic dump is issued and, if possible, then is ended.

If there is very little main storage available on the TPF system, the IPL dump routine may fail.

User Response: See your system programmer for more information. Verify the size of the processor being IPLed. If this is a High Performance Option (HPO) system, verify the subsystem configuration. Each additional subsystem adds a large main storage requirement during IPL. This message implies a large mismatch between the available storage and the storage requirements.

If the TPF system being IPLed has the minimum main storage, 2 MB, then study the TPF system generation reports to determine the size of working storage reserved. Ensure that working storage is at least 521 K + (70 K for each subsystem generated). Verify the action of the memory in the processor being IPLed. A memory failure in the first 2 MB may produce this failure.

See TPF Main Supervisor Reference for more information.

IPLB00A9TLOGIC ERROR -- NO RETURN ADDRESS IN I/O BLOCK

Explanation: This is an interface error within IPLB code.

System Action: A dump is issued and then ended.

User Response: IPL the TPF system again. If the condition continues, see your system programmer for more information.

This is a logic error. IB08 was called with an input/output (I/O) request block (WB0WB) without a return address in the block. Verify the content of the I/O request block.

See TPF Main Supervisor Reference for more information.

IPLB00AATLOGIC ERROR -- CC=1 RETURN FROM SIOSC

Explanation: The IPL DASD input/output (I/O) initiator code issued an SIOSC and a condition code 1 was returned. Condition code 1 is not defined and a logic error is indicated when it is received.

System Action: The IPL operation is ended.

User Response: Have your system programmer determine why the SIOSC is returning an illegal condition code.

See TPF Main Supervisor Reference for more information.

IPLB00ABTLOGIC ERROR -- BAD WORKBLOCK ADDRESS RETURNED BY CIO

Explanation: The IPL DASD interrupt code expects the input/output (I/O) operation work block address is returned by CIO as a parameter. If the device address in the workblock does not match the device address in SYSIDA, it is assumed the workblock address is bad. This is logically not suppose to occur.

System Action: The IPL operation is ended.

User Response: Have your system programmer determine why a bad workblock address was passed to common I/O from IPL or passed to IPL from common I/O.

See TPF Main Supervisor Reference for more information.

IPLB00ACTLOGIC ERROR -- SOFTWARE MOUNT FAILED FOR THE IPL VOLUME

Explanation: The IPL DASD input/output (I/O) initiator code issued an MSDAC macro to software mount the IPL volume before initiating an I/O to the device. A nonzero return code (symbolic device address (SDA) does not exit or SDA is in use), was returned from the MSDAC macro. IPL does not continue if the IPL volume cannot be mounted.

System Action: The IPL operation is ended.

User Response: Verify the that DASD is online. If the DASD is online, have your system programmer determine why the mount is failing.

See TPF Main Supervisor Reference for more information.

IPLB00B1xI/O OPERATION ON DEVICE ccud COMPLETED status

Where:

x
The severity indicator, Action Code, which may be:

I
Informational

E
Error

ccud
The channel address of the device.

status
The status of the input/output (I/O) operation, which is one of the following:

Explanation: If the I/O operation completed abnormally, this message is always followed by a second message describing the cause of the failure. However, it is not normal for you to receive this notification when an input/output (I/O) operation is completed normally.

System Action: None.

User Response: Save the console and see your system programmer for more information.

See TPF Main Supervisor Reference for more information.

IPLB00B2EDEVICE IS NOT PRESENT, OR REQUIRES INTERVENTION

Explanation: IPLB received from DASD one of the various indications that a device is not installed, not powered on, or otherwise requires intervention. This was indicated as the result of an input/output (I/O) operation.

System Action: None.

User Response: This message is generally be followed by a message indicating what the TPF system was trying to do when it received this status. You respond to that message.

See TPF Main Supervisor Reference for more information.

IPLB00B3EI/O RETRY COUNT EXHAUSTED, DEVICE PERSISTENTLY BUSY

Explanation: The number of retries that IPLB attempts is limited following conditions that prevent input/output (I/O) from being initiated (for example, busy conditions). This number was reached.

System Action: None.

User Response: This message is generally followed by another message indicating what the TPF system was trying to do when it received this status. You should respond to that message. The device at the address specified by the preceding IPLBB1E message should be checked. If that device is shared with another processor or is on a control unit that is shared with other processors, then the level of activity outstanding to the device or control unit should be studied.

See TPF Main Supervisor Reference for more information.

IPLB00B4ESENSE DATA PRESENT: sense data SCSW=statword, CCW=cmdword, paddr=parm

Where:

sense data
24 or 32 bytes of sense data.

statword
The subchannel status word (CSW) stored at the time of the failure.

cmdword
The failing channel command word (CCW).

paddr
The address of the parameter pointed to by the failing CCW.

parm
The four bytes of data starting at the failing CCW parameter address.

Explanation: The sense data is for the device specified in the preceding IPLBB001E message.

System Action: None.

User Response: This message is generally followed by a message indicating what the TPF system was trying to do when it received this status. You should respond to that message. The type of error can be determined by looking at the publication for the control unit to which the device is attached.

See TPF Main Supervisor Reference for more information.

IPLB00B5ETIMEOUT WHILE WAITING FOR DEVICE TO RESPOND

Explanation: The DASD input/output (I/O) operations are timed in IPLB. If an I/O operation exceeds its time value, it is considered lost. I/O operations should not normally timeout.

System Action: None.

User Response: This message is generally followed by a message indicating what the TPF system was trying to do when it received this status. You should respond to that message.

This situation may be caused by lost interrupts, which are a normal, but very infrequent part of I/O operations. A re-IPL should not receive the same message if this message was caused by a lost interrupt. The device should be checked to determine why the operation did not complete in the time allotted.

See TPF Main Supervisor Reference for more information.

IPLB00B6ERECEIVED CHANNEL PROGRAM CHECK ON I/O OPERATION

Explanation: IPLB tried an input/output (I/O) operation that ended with a channel program check.

System Action: None.

User Response: This message is generally followed by a message indicating what the TPF system was trying to do when it received this status. You should respond to that message.

See TPF Main Supervisor Reference for more information.

IPLB00B7ETYPE OF ERROR UNKNOWN, IPLB LOGIC ERROR.

Explanation: The error code in the input/output (I/O) request block was not recognized by the DASD error print utility.

System Action: None.

User Response: This message is generally followed by a message indicating what the TPF system was trying to do when it received this status. You should respond to that message.

See TPF Main Supervisor Reference for more information.

IPLB00D1EUNABLE TO SIGP PROC ADDR = x: reason

Where:

x
The physical address of the I-stream being signalled.

reason
One of the following:

Explanation: IPLB was unable to issue the SIGP instruction to the specified target I-stream. This message is followed by the IPLBD003T message, which ends the IPL.

System Action: IPL continues to roll call all I-streams. The TPF system aborts the IPL after all I-streams were interrogated via SIGP.

User Response: Respond to the IPLBD003T message.

See TPF Main Supervisor Reference for more information.

IPLB00D2ITPF WILL USE xx OF THE yy AVAILABLE I-STREAMS

Where:

xx
The number of I-streams, which is displayed as a decimal number, that are available for application program use.

yy
The number of I-streams, which is displayed as a decimal number, that are physically installed and varied online through the hardware console.

Explanation: This message is for informational use only. It describes the tightly coupled configuration.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information.

IPLB00D3TIPL TERMINATED, CANNOT DETERMINE STATUS OF PROC ADDR x

Where:

x
The physical address of the failing I-stream.

Explanation: IPLB was unable to SIGP the specified I-stream.

System Action: The TPF system is dumped and the IPL is aborted.

User Response: Do the following:

  1. Perform a system reset from the hardware operator console.
  2. IPL the TPF system again. If the IPL fails the same way, IPL a backup processor. If there is no is no fallback processor, the I-stream identified in the message can be removed from the configuration by using the hardware console. The process of removing an I-stream through the hardware console may be too lengthy to use in a production environment. See 370/XA Principles of Operation for more information about the conditions under which each type of SIGP instruction failure can occur.

The IPLBD001E message specifies the error that occurred during the SIGP instruction.

See TPF Main Supervisor Reference for more information.

IPLB00S1TSTOR MANGT: DOUBLE OPEN OF STORAGE

Explanation: The storage management routine in IPLB was used incorrectly.

System Action: A dump is issued and is ended.

User Response: IPL the TPF system again. If the TPF system still cannot IPL, see your system programmer for more information.

See TPF Main Supervisor Reference for more information.

IPLB00S2TSTOR MANGT: GET/RELEASE WITHOUT AN OPEN

Explanation: The storage management routine in IPLB was used incorrectly.

System Action: A dump is issued and is ended.

User Response: IPL the TPF system again. If the TPF system still cannot IPL, see your system programmer for more information.

See TPF Main Supervisor Reference for more information.

IPLB00S3TSTOR MANGT: INVALID STORAGE RELEASE

Explanation: The storage management routine in IPLB was used incorrectly.

System Action: A dump is issued and is ended.

User Response: IPL the TPF system again. If the TPF system still cannot IPL, see your system programmer for more information.

See TPF Main Supervisor Reference for more information.

IPLB00S4TSTOR MANGT: INSUFFICIENT STORAGE AVAILABLE

Explanation: There was insufficient storage available for the input/output (I/O) request blocks (WB0WB) in IB04. IPLB resides in the area reserved for working storage but working storage may have been generated too small or the processor being IPLed may have too little main storage for the TPF system being IPLed.

System Action: A diagnostic dump is issued and, if possible, is then ended. If there is very little main storage available on the TPF system, the IPL dump routine may fail.

User Response: See your system programmer for more information. Verify the size of the processor being IPLed. If this an High Performance Option (HPO) system, verify the subsystem configuration. Each additional subsystem adds a large main storage requirement during IPL. This message implies a mismatch between the available storage and the storage requirements. If the TPF system being IPLed has the minimum main storage, 2 MB, then study the TPF system generation reports to determine the size of the working storage reserved. Ensure that working storage is at least 521 K + (70 K for subsystem generated). Verify the action of the memory in the processor being IPLed. A memory failure in the first 2 MB may produce this failure.

See TPF Main Supervisor Reference for more information.