Operator Messages Manual

Chapter 67 ODP (Optical Disk Process) Messages

This chapter describes the operator messages that are generated by the optical disk process (ODP). The subsystem ID displayed by these messages includes ODP as the subsystem name. These messages are typically related to hardware malfunctions or important changes in the state of a component of the reporting subsystem. The messages in this section apply to systems running D-series RVUs only.

NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.


501

{ $device | $volume } BAD DIRECTORY FILE ERROR SECTION: { DIRECTORY FILE HAS BEEN MODIFIED } { CREATION DATE HAS CHANGED }

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process has detected a bad directory file while attempting to bring a volume up (without the COLD option). One of the following has occurred:

  • The directory file has been modified since the last time the volume was brought down.

  • The directory file has a different creation date from the creation date recorded in the recovery file.

Effect  The volume is left down.

Recovery  Bring the volume back up with the COLD option of the Peripheral Utility Program (PUP) UP command.



502

$device BAD FILE LABEL ON $volume ERROR SECTION: { BAD COUNT | ILLEGAL LABEL ADDRESS }

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process has detected an inconsistency between information on a file label and information in the magnetic-disk directory file for a volume. Inconsistent information may be the result of a bad count on the directory read or an illegal file-label address.

Effect  If this error occurs during a file-open operation, file-system error 157 is returned to the calling process and the file is not opened. If this error occurs when a volume is being brought up, the volume is not brought up, but the directory rebuild continues.

Recovery  Bring down the specified volume, purge its old directory file, and bring the volume up using the Peripheral Utility Program (PUP) UP, COLD command to rebuild the file. See Appendix B, for information about the specified error.



503

{ $device | $volume } BAD RECOVERY FILE ERROR SECTION: { INCORRECT FREE SECTOR BOUNDS } { INCORRECT LOGICAL DEVICE NUMBER } { INCORRECT VOLUME STRUCTURE } { INCONSISTENT WITH HARDWARE: CAUSE nn }

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

nn

is a text description of the reason for the hardware inconsistency.

Cause  The optical disk process (ODP) has detected an inconsistency between information in the recovery file and other hardware or software information. Inconsistent information may result from one of the following:

  • Inconsistent logical device numbers (implying that a new SYSGEN has occurred)

  • An incorrect volume structure (possibly resulting from an internal error)

  • Incorrect values in the recovery file for the lower and upper bounds of unwritten sectors on a specific volume

  • A hardware inconsistency. Cartridges may have been manually moved while the optical disk process (ODP) was down.

Effect  If the error occurs while the entire ODP is being brought up, it is not brought up. If the error occurs while a volume is being mounted into a drive, the volume is brought down.

Recovery  Bring up the ODP or volume with the COLD and SUBVOL options of the PUP UP command.



504

BAD VOLUME LABEL ON $volume ERROR SECTION: { TIMESTAMP } { ILLEGAL LABEL ADDRESS } { INVALID DATA }

$volume

is the name of an optical disk volume.

Cause  The optical disk process (ODP) has detected an inconsistency between information on a volume label and the information in the magnetic-disk directory file for that volume. Inconsistent information may result from one of the following:

  • An inconsistent timestamp on the front and rear volume label

  • An illegal volume label address

  • Invalid data (such as an inconsistent volume ID or volume version)

Effect  If this error occurs while a volume is being brought up, the volume is not brought up and cannot be used. If this error occurs while a volume is being mounted onto a drive, the volume is brought down and all files are closed.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



505

$device CARTRIDGE { HAS BEEN | CAN BE } REMOVED FROM CELL #num

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  A cartridge is in the carrier, ready to be removed.

Effect  The Peripheral Utility Program (PUP) EJECT operation is finished.

Recovery  Remove the cartridge.



506

$device CARTRIDGE HAS BEEN INSERTED INTO CELL #num

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  A new cartridge was inserted into a storage cell.

Effect  The volumes on the inserted cartridge are accessible to user processes after you issue a Peripheral Utility Program (PUP) UP, COLD command for each volume.

Recovery  Informational message only; no corrective action is needed.



509

$device DRIVE-{0 | 1 | 2 | 3 } HAS BEEN DOWNED BY { ODP | NON-ODP }

$device

is the name of the entire optical storage unit.

Cause  The specified drive has been brought down by the optical disk process (ODP) or another process—most likely the Peripheral Utility Program (PUP).

Effect  The operation is finished.

Recovery  If a PUP DOWN command caused this message, it is an informational message only; no corrective action is needed. If a PUP DOWN command did not cause this message, contact your service providerand provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



510

$device DRIVE-{0 | 1 | 2 | 3 } HAS BEEN UPPED BY { ODP | NON-ODP }

$device

is the name of the entire optical storage unit.

Cause  The specified drive has been brought up by the optical disk process or another process—most likely the Peripheral Utility Program (PUP).

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.



511

$device VOLUME $volume HAS THE SAME NAME AS AN UP VOLUME

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process (ODP) cannot bring the volume up because both names (original and alternate) in the volume are the same as that of a volume that is currently up.

Effect  The volume remains down.

Recovery  Use the Peripheral Utility Program (PUP) RENAME command to temporarily change the volume name.



512

$device FATAL CONTROLLER ERROR: { FIRMWARE FORCED LOCKSTEP FREEZE } { EPROM PARITY ERROR } { WCS PARITY ERROR } { DATA BUS MISCOMPARE } { ADDRESS BUS MISCOMPARE } { CONTROL LINE MISCOMPARE } CMD: command SECADDR: addr SECCNT: count

$device

is the name of the entire optical storage unit.

command

is the command issued to the controller.

addr

is a sector address.

count

is a sector count.

Cause  A fatal error has occurred on the controller.

Effect  The optical disk process (ODP) resets the controller, downloads the microcode, resets the small computer system interface (SCSI) bus, and retries the current request. If the error recurs, the ODP is brought down.

Recovery  Informational message only; no corrective action is needed unless the ODP is brought down. Contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



513

$device DRIVE-{ 0 | 1 | 2 | 3 } INTERRUPT TIMEOUT CMD: command SECADDR: addr SECCNT: count

$device

is the name of the entire optical storage unit.

command

is the command issued to the controller.

addr

is a sector address.

count

is a sector count.

Cause  The optical disk process (ODP) has issued an I/O command to the optical controller, but no interrupt has occurred.

Effect  The ODP attempts to reset the controller, download the microcode, and reset the small computer system interface (SCSI) bus. If successful, the ODP then retries the current request. If unsuccessful, the ODP switches to the other processor and retries the request. If the request fails again, the ODP is brought down.

Recovery  Informational message only; no corrective action is needed unless the ODP is brought down. Contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



514

$device I/O BUS ERROR: errnum

$device

is the name of the entire optical storage unit.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  An I/O bus error has occurred during a transfer on a channel controlled by the sender processor.

Effect  The operation is retried; if errnum is in the range 210 through 229, the operation can switch to the other processor.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



517

OSF $device HAS BEEN DOWNED BY { ODP | NON-ODP }

$device

is the name of the entire optical storage unit.

Cause  The Optical Storage Facility (OSF) has been brought down by the optical disk process (ODP) or another process—most likely the Peripheral Utility Program (PUP).

Effect  The operation is finished.

Recovery  If a PUP DOWN command caused this message, it is an informational message only; no corrective action is needed. If a PUP DOWN command did not cause this message, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



519

OSF $device HAS BEEN UPPED BY { ODP | NON-ODP }

$device

is the name of the entire optical storage unit.

Cause  The Optical Storage Facility (OSF) has been brought up by the optical disk process (ODP) or another process—most likely the Peripheral Utility Program (PUP).

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.



520

{ $device | $volume } UNABLE TO ALLOCATE MEMORY FOR INTERNAL TABLES

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  Not enough memory is available for the optical disk process (ODP) to allocate space for its internal tables. This message may appear when the ODP tried to bring up a volume or the entire ODP.

Effect  The ODP or volume remains down.

Recovery  You may need to add more system memory. Contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



521

{ $device | $volume } SOFTWARE ERROR ON: { ADC IN USE } { ADC NOT IN USE } { DEMOUNT ERROR } { NO CARTRIDGE IN CELL } { CARTRIDGE IN OTHER DRIVE } { ILLEGAL VOLUME LABEL } { INTERNAL TABLE }

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process (ODP) has detected internal errors on one of the following:

  • A drive

  • A cartridge location

  • Automatic Disk Changer (ADC) usage

  • An ODP internal table

Effect  File-system error 157 has been returned to the calling process, and the operation is aborted.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



522

$device PROCESS SWITCH BEGUN

$device

is the name of the entire optical storage unit.

Cause  A processor switch has occurred.

Effect  The backup processor attempts to take control of the controller. If the takeover is successful, this message is followed by ODP message 545 (a processor switch was initiated and ended normally). If the takeover is unsuccessful, this message is followed by ODP message 544 (a processor switch was initiated, but the ODP encountered an error). This message should be preceded by other messages (I/O error and I/O retry fail).

Recovery  Informational message only; no corrective action is needed.



523

$device MICROCODE FILE $system.sysnn.{ m3219 | m3220 } LOADED SUCCESSFULLY

$device

is the name of the entire optical storage unit.

nn

is the number of the system affected.

Cause  The microcode was successfully downloaded after the controller was reset.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.



524

$device MICROCODE FILE $system.sysnn.{ m3219 | m3220 } LOADING FAILURE

$device

is the name of the entire optical storage unit.

nn

is the number of the system affected.

Cause  The controller was reset and an error occurred when the microcode was being downloaded.

Effect  If this error occurs while the optical disk process (ODP) is being brought up, it is not brought up. If this error occurs after one of the following ODP messages is returned, the ODP is brought down:

512A fatal controller error has occurred.
513The ODP has issued an I/O command to the optical controller, but no interrupt has occurred.
518The ODP has been powered on or off.

Recovery  If this error occurs while the ODP is being brought up, contact the Global Mission Critical Solution Center (GMCSC).

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



525

$volume UNABLE TO{CLOSE | CREATE | OPEN | READ | WRITE} THE FILE DIRECTORY $volume.subvol.ZZDInnnn ERROR: errnum

$volume

is the name of an optical disk volume.

subvol

is the name of the subvolume affected.

nnnn

is the number of the file directory affected.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The ODP has failed to close, create, open, read, or write the magnetic-disk directory file for a volume.

Effect  The volume remains down.

Recovery  Specify the correct subvolume or see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



526

UNABLE TO { READ | WRITE } THE FILE LABEL ON $volume ERROR: errnum

$volume

is the name of an optical disk volume.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The ODP has failed to read or write the file label on the optical disk volume.

Effect  The operation is aborted.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



527

$device UNABLE TO { CLOSE | OPEN | READ | WRITE } THE RECOVERY FILE $volume.subvol.ZZREnnnn ERROR: errnum

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

subvol

is the name of the subvolume affected.

nnnn

is the name of the recovery file affected.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The optical disk process (ODP) was being brought up, but it failed to close, open, read, or write the magnetic-disk recovery file.

Effect  The ODP remains down.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



528

$device UNABLE TO { OPEN | READ } THE MICROCODE FILE $system.sysnn.{ m3219 | m3220 } ERROR: errnum

$device

is the name of the entire optical storage unit.

nn

is the name of the system affected.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The ODP could not open or read the microcode file.

Effect  The optical disk process (ODP) is left down or is brought down.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



529

UNABLE TO { READ | WRITE } THE VOLUME LABEL ON $volume ERROR: errnum

$volume

is the name of an optical disk volume.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The ODP has failed to read or write the volume label on the optical disk.

Effect  The volume remains down.

Recovery  See the Guardian Procedure Errors and Messages Manual for recovery actions for the file-system error number indicated by errnum.



530

UNABLE TO INITIALIZE THE OSF $device ERROR: errnum

$device

is the name of the entire optical storage unit.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The ODP could not initialize the Optical Storage Facility (OSF).

Effect  The OSF remains down.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



531

UNABLE TO OBTAIN CELL STATUS OF THE OSF $device ERROR: errnum USING DRIVE - { 0 | 1 | 2 | 3 }

$device

is the name of the entire optical storage unit.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The optical disk process (ODP) cannot obtain the cell status of $device when the optical storage unit is being brought up or during a processor switch recovery.

Effect  The ODP is brought down.

Recovery  See Appendix B, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.



532

UNABLE TO { DEMOUNT | EJECT | FLIP | INSERT | MOUNT } A CARTRIDGE ON $device ERROR: errnum

$device

is the name of the entire optical storage unit.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The ODP has failed to demount, eject, flip, insert, or mount a cartridge. The Automatic Disk Changer (ADC) has malfunctioned, or errors have occurred in the ODP internal tables.

Effect  The operation is aborted, and the ADC cannot be used until the ODP is brought up again.

Recovery  Bring down the entire ODP with the Peripheral Utility Program (PUP) DOWN command, then back up using the COLD and SUBVOL options of the PUP UP command. If this action does not clear the problem, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



534

$ device VOLUME $volume HAS BEEN DOWNED BY { ODP | NON-ODP }

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  A volume has been brought down by the optical disk process (ODP) or another process—most likely the Peripheral Utility Program (PUP).

Effect  The volume is inaccessible to user processes.

Recovery  Informational message only; no corrective action is needed.



535

$ device VOLUME $volume IS FULL

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  There is no space available on the specified volume.

Effect  The optical disk process (ODP) cannot write data to the volume.

Recovery  Use a different volume.



536

$ device VOLUME $volume HAS BEEN UPPED BY { ODP | NON-ODP }

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  A volume has been brought up by the optical disk process (ODP) or another process—most likely the Peripheral Utility Program (PUP).

Effect  The volume can be accessed by user processes.

Recovery  Informational message only; no corrective action is needed.



537

$device CARTRIDGE HAS BEEN DETECTED IN CELL #num

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  This message is sent after a Peripheral Utility Program (PUP) UP, COLD command is issued. After a PUP UP, COLD operation, any cartridges already present are considered to be newly inserted cartridges.

Effect  The cartridge and its current location are noted in the recovery file.

Recovery  Informational message only; no corrective action is needed.



538

$device UNABLE TO FIND EXPECTED CARTRIDGE IN CELL #num

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  The optical disk process (ODP) $device is being brought up with the WARM option in the Peripheral Utility Program (PUP) UP command. The recovery file states that a cartridge is in cell #num but the cell is empty. A cartridge has been physically moved without updating the recovery file.

Effect  If the ! option is used, recovery-file entries for the cartridge are cleared and ODP message 556 (the ODP brought up a volume using the ! option) is generated. If the ! option is not used, the PUP UP operation fails with file-system error 15.

Recovery   To recover from this error, do one of the following:

  • Put the missing cartridge back into its cell.

  • Issue a PUP UP ! command for $device. The optical disk process assumes that any missing cartridges have been ejected and allows UP processing for other cartridges to continue without causing the entire UP operation to fail.

  • Issue a PUP UP, COLD command for $device to rebuild the recovery file. Volumes must be brought up using the COLD option in the PUP UP command in order to be accessible, but their directory files do not have to be rebuilt.



539

$device ADC OPERATIONS HAVE BEEN ENABLED

$device

is the name of the entire optical storage unit.

Cause  A Peripheral Utility Program (PUP) UP command has been issued for a drive, instructing the software that it can use the Automatic Disk Changer (ADC) again.

Effect  The ADC operation is enabled.

Recovery  Informational message only; no corrective action is needed.



540

$device ADC OPERATIONS HAVE BEEN DISABLED

$device

is the name of the entire optical storage unit.

Cause  The optical disk process (ODP) cannot locate a cartridge after a disk change operation. The ODP issues a message indicating that the automatic disk changer (ADC) should not be used.

Effect  The ADC operation is disabled.

Recovery  If the optical disk process (ODP) is not brought down, this is an informational message only; no corrective action is needed. If the ODP is brought down, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



541

UNABLE TO UP THE OSF $device ERROR: errnum

$device

is the name of the entire optical storage unit.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  An attempt to bring up ODP failed because of an error.

Effect  The ODP remains down.

Recovery  A number of hardware or software conditions could cause this message, depending on the error received. Look for obvious hardware problems, such as loose cable connections, a lack of power, or the wrong controller. Check the Tandem Maintenance and Diagnostic System (TMDS) log for related errors or messages and try to determine whether the error is hardware-related or software-related.

If you are unable to determine the cause of the error or to bring up the ODP, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



542

$device CARTRIDGE HAS BEEN DETECTED IN DRIVE: #num

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  After a PUP UP, COLD command, the optical disk process (ODP) detected a cartridge in the specified drive.

Effect   The cartridge is available for use.

Recovery  Informational message only; no corrective action is needed.



543

$device UNABLE TO FIND CARTRIDGE IN DRIVE #num

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  The optical disk process (ODP) is being brought up with the WARM option in the Peripheral Utility Program (PUP) UP command. The recovery file states that a cartridge is in drive #num, but the drive is empty. A cartridge has been physically moved without updating the recovery file.

Effect  If the ! option is used, recovery-file entries for the cartridge are cleared and ODP message 556 (the ODP brought up a volume using the ! option) is generated. If the ! option is not used, the PUP UP operation fails with file-system error 15.

Recovery  See Appendix B, for information on the specified error. To recover from this error, do one of the following:

  • Put the missing cartridge back into its cell.

  • Issue a PUP UP ! command for $device. The ODP assumes that any missing cartridges have been ejected and allows UP processing for other cartridges to continue without causing the entire UP operation to fail.

  • Issue a PUP UP, COLD command for $device to rebuild the recovery file. Volumes must be brought up using the COLD option in the PUP UP command to be accessible, but their directory files do not have to be rebuilt.



544

$device PROCESS SWITCH ENDED WITH ERROR errnum

$device

is the name of the entire optical storage unit.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  A processor switch was initiated, but the ODP encountered an error.

Effect  The ODP is brought down.

Recovery  Try to bring up the ODP using the Peripheral Utility Program (PUP) UP command. If you are unable to bring it up, check the Tandem Maintenance and Diagnostic System (TMDS) log for related errors or messages and try to determine whether the error is hardware-related or software-related.

If you are unable to determine the cause of the error, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



545

$device PROCESS SWITCH FINISHED

$device

is the name of the entire optical storage unit.

Cause  A processor switch was initiated and ended normally. This error is preceded by optical disk process (ODP) message 522 (a processor switch has occurred).

Effect  The backup processor becomes the primary processor.

Recovery  Informational message only; no corrective action is needed.



546

$device VOLUME $volume BAD FILE LABEL DATA AT SECTOR addr

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

addr

contains a sector address.

Cause  This message can appear after issuing a Peripheral Utility Program (PUP) UP, COLD command. It can be caused by an invalid sector count in a file-label trailer record, by an invalid file label, by a bad file-label trailer record version, or by other file-label problems.

Effect  The PUP UP, COLD operation for a specific volume is abandoned because it is likely that user data has been encountered, or an optical disk process (ODP) internal error has created the appearance of bad data. If the ! option is used, the volume comes up in permanent read-only mode.

Recovery  Use the PUP UP command with the ! option to try to bring up each volume individually. If the volume cannot be brought up or if you need to write to the volume, contact your service provider and provide all relevant information ad follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



547

$device CARTRIDGE ONCE IN CELL #num HAS BEEN LOST

$device

is the name of the entire optical storage unit.

num

contains the cell number where the cartridge has been detected.

Cause  After a Peripheral Utility Program (PUP) UP, WARM command, a cartridge could not be located in its designated cell or in a drive if the recovery file said it was there. The ! option is being used, so the cartridge is removed from the recovery file just as it would be removed after a PUP EJECT command. It is possible that the cartridge is still in the jukebox, in another drive. If so, it is added back to the recovery file just as it would be added if the cartridge were inserted into the jukebox.

Effect  The drive is brought up without the missing cartridge.

Recovery  If the cartridge has been removed from the jukebox manually (during maintenance, for example), find the cartridge, reinsert it, and bring up the volumes using the PUP UP command. If you cannot locate the cartridge, there may be a sensor malfunction within the jukebox. Contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



548

$device MOUTH OPEN - ADC SUSPENDED UNTIL CLOSED

$device

is the name of the entire optical storage unit.

Cause  The optical disk process (ODP) has detected a condition that may be caused by the disk I/O slot being left open for an extended period. This message is valid only for the 5410 optical disk storage subsystem.

Effect  The ODP continues to issue this error message until the slot is closed. If the slot is closed, the ODP returns to normal operation.

Recovery  Check the disk I/O slot to ensure that nothing is preventing the shutter from closing. Remove any object that is preventing the shutter from closing and press the IN button to close the shutter.



549

$device THERE ARE INSERTIONS STILL PENDING

$device

is the name of the entire optical storage unit.

Cause  A load is pending for multiple cartridges.

Effect  The optical disk process (ODP) has transported multiple cartridges to storage cells.

Recovery  Informational message only; no corrective action is needed. If this message occurs frequently, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



550

$device CARTRIDGES AWAIT REMOVAL

$device

is the name of the entire optical storage unit.

Cause  Multiple cartridges are ready to be removed. This message is valid only for the 5410 optical disk storage subsystem.

Effect  The OUT indicator for the operator panel on the 5410 optical disk storage subsystem lights, prompting you to remove the cartridges that are prepared for ejection.

Recovery  Press the OUT button for the operator panel on the 5410 optical disk storage subsystem and remove each prepared cartridge. See Section 3 of the 5410, 5411, and 5420 Optical Disk Subsystem Manual for information about removing cartridges.



551

$device A CARTRIDGE AWAITS REMOVAL

$device

is the name of the entire optical storage unit.

Cause  A single cartridge is ready to be removed.

Effect  On the 5411 and 5420 optical disk storage subsystems, the cartridge is delivered to the disk I/O slot. On the 5410 optical disk storage subsystem, the OUT indicator on the operator panel lights, prompting you to remove the cartridge.

Recovery  On the 5411 and 5420 optical disk storage subsystems, remove the cartridge from the disk I/O slot. On the 5410 optical disk storage subsystem, press the OUT button and remove the cartridge. See Section 3 of the 5410, 5411, and 5420 Optical Disk Subsystem Manual for information about removing cartridges. If this message appears frequently, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



552

$device VOLUME $volume SECTOR addr HAS BEEN WRITTEN. NO LOWER FREE SECTOR CAN BE ESTABLISHED

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

addr

contains a sector address.

Cause  During a Peripheral Utility Program (PUP) UP, COLD command, a value for the lower free sector bound for a volume is calculated, but there is data at that disk address. This message indicates that data has been written to a volume without a corresponding file label to point to it.

Effect  If the ! option is used, the volume is brought up in permanent read-only mode. If the ! option is not used, the volume remains down and file-system error 157 is returned.

Recovery  Try to bring up the volume using the PUP UP command with the ! option. If you are unable to bring up the volume, or if you want to write to the volume, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



553

$device VOLUME $volume IS WRITE PROTECTED

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process (ODP) attempted to write to a volume on a write-protected cartridge.

Effect  The write is rejected with file-system error 134. All files open for write access on either volume of the cartridge are closed.

Recovery  To write to either volume, you must remove write protection from the cartridge. See Section 3 of the 5410, 5411, and 5420 Optical Disk Subsystem Manual. See Appendix B, for information on the specified error.



554

$device VOLUME $volume HAS NO MORE ALTERNATE SECTORS

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process (ODP) has attempted to write to a volume whose supply of alternate sectors is exhausted.

Effect  The write is rejected with file-system error 134. All files open for write access on the volume are closed.

Recovery  Reset the volume’s access mode to RW using a Peripheral Utility Program (PUP) ALTER command and retry writing to the volume. See Appendix B, for information on the specified error.



555

$device VOLUME $volume FILE LABEL AT SECTOR addr INCONSISTENT WITH A PREVIOUS

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

addr

contains a sector address.

Cause  The optical disk process (ODP) has detected an inconsistency in file labels during a Peripheral Utility Program (PUP) UP, COLD command.

Effect  If the ! option is used, the UP, COLD operation continues. File-system error 10 or 11 is returned if no other error is encountered later in processing.

Recovery  If this message appears frequently, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



556

$device VOLUME $volume HAS BEEN UPPED BY { ODP | NON-ODP }; ERROR errnum TOLERATED

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

errnum

is the file-system error returned by the optical disk process (ODP).

Cause  The optical disk process (ODP) brought up a volume using the ! option and tolerable errors occurred, for which other ODP messages were generated.

Effect   The following file-system errors can be returned: 10, 11, 120, or 157. The volume is placed in read-only mode. For file-system errors 10, 11, or 120, the file-open mode can be altered for read and write access. For file-system error 157, read-only mode is permanent. The following table shows possible errors and the ODP messages they generate.

File-System ErrorODP Message Generated
10 and 11525 and 555
120515
157546 or 555

Recovery  Informational message only; no corrective action is needed. See Appendix B, for information on the specified error.



557

$device HAS BEEN RESET

$device

is the name of the entire optical storage unit.

Cause  The optical disk process (ODP) subsystem has been powered on or off. This message is valid only for the 5410 optical disk storage subsystem.

Effect  The ODP takes the appropriate recovery action. If unsuccessful, the optical disk storage subsystem is brought down.

Recovery  Informational message only; no corrective action is needed. If the ODP is brought down, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



558

$device VOLUME $volume RUNNING OUT OF ALTERNATE SECTORS

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  The optical disk process (ODP) has written to alternate sectors, and a warning threshold has been exceeded. It is possible that few alternate sectors remain available for use.

Effect  The ODP continues to operate normally.

Recovery  If this message appears frequently, the cartridge may be defective. Try cleaning the cartridge using the procedure described in the WOA-D11 Writable Optical Disk Cleaning Kit Manual. Use the Tandem Maintenance and Diagnostic System (TMDS) ODISK TEST command to analyze the optical media. See Section 6 of the 5410, 5411, and 5420 Optical Disk Subsystem Manual for more information.

If you are unable to determine the cause of the problem, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.



559

$device VOLUME$volume WILL BE REMOUNTED

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  A cartridge cannot be read.

Effect  The cartridge is demounted and remounted, if possible, on the same drive or on another drive.

Recovery  If this message appears infrequently, it is an informational message only; no corrective action is needed. If the message appears often, use the Tandem Maintenance and Diagnostic System (TMDS) ODISK TEST command to test the optical drive. See Section 6 of the 5410, 5411, and 5420 Optical Disk Subsystem Manual for more information.



560

$device DRIVE SIDE FOR VOLUME $volume HAS BEEN CORRECTED

$device

is the name of the entire optical storage unit.

$volume

is the name of an optical disk volume.

Cause  A cartridge has just been mounted or flipped and its volume label read. The optical disk process (ODP) has discovered that the incorrect volume is now mounted (UP) in the drive.

Effect  The ODP displays the name of the incorrect volume that is mounted and corrects the recovery file accordingly. The user request that caused the mount or flip in an attempt to access the other side of the cartridge is reexecuted.

Recovery  Informational message only; no corrective action is needed.



561

$device ERROR DURING INITIALIZATION

$device

is the name of the entire optical storage unit.

Cause  The optical disk process (ODP) detected an error during initialization. Such an error could result from a buffer that could not be locked, a segment that could not be allocated, or a configuration parameter that is incorrect or not allowed.

Effect  The ODP is not brought up.

Recovery  Reexamine the CONFTEXT configuration file or the Configuration Utility Program (COUP) commands that you used to configure the ODP. Correct any mistakes you made, and repeat the procedure. If you are unable to bring up the ODP, contact your service provider and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.