Table 22. Intervention Required Conditions relating to a Virtual Tape Server in the Library (continued)

 

 

 

 

 

Intervention Required Condition

Resolution Actions

 

 

 

 

 

 

Message

1. Contact your service representative.

 

 

 

 

 

Mount of logical volume xxxxxx failed because

2. Locate the physical volume and insert it into the

 

 

physical volume yyyyyy is not in the library. (rc=rrrr)

library.

 

 

(VTS z)

 

 

 

Probable Cause

 

 

 

To satisfy a logical volume mount request, the logical

 

 

 

volume must be recalled from a physical volume. At the

 

 

 

time the logical volume mount request was processed,

 

 

 

the physical volume required could not be found in the

 

 

 

library manager inventory.

 

 

 

 

 

 

 

Message

1. Contact your System Administrator

 

 

 

 

 

Mount of logical volume xxxxxx located on physical

2. For Dual Library Manager systems containing a VTS,

 

 

this intervention may be the result of a Library

 

 

volume yyyyyy failed. (rc=rrrr) (VTS z)

 

 

Manager switchover. When a Library Manager

 

 

 

 

 

Probable Cause

switchover occurs, queued or in-progress logical

 

 

To satisfy a logical volume mount request, the logical

mounts are not completed. This results in the VTS

 

 

asking the Library Manager to post this intervention. If

 

 

volume must be recalled from a physical volume. The

this is the case, clear the intervention and re-drive the

 

 

mount of the physical volume could not be completed and

mount from the host.

 

 

the VTS subsystem could not determine the exact reason

 

 

 

for the failure.

 

 

 

 

 

 

Message

1. This Intervention Required noti®cation will be given for

 

Stacked volume xxxxxx is in Read-Only status with a

the ®rst volume to be placed in read-only status within

 

a 24 hour period. Your service representative should

 

reason code of yyyyy. (VTS z)

 

only be contacted after your system administrator has

 

 

 

Probable Cause

been noti®ed as described in messagesLogical

 

volume xxxxxx was not fully recovered from damaged

 

 

 

During a prior read or write operation with the volume

stacked volume yyyyyy. (VTS z) and A damaged

 

(recall of a logical volume, copying of a virtual volume, or

stacked volume xxxxxx has been ejected to the

 

routine reclamation of a stacked volume), a permanent

convenience I/O station. (VTS z), and it is necessary

 

media error was detected by the VTS, or an excessive

to recover a damaged logical volume.

 

number of temporary media errors have occurred. The

 

 

volume is placed in read-only status to prevent further

 

 

writing of customer data. Customer data already on the

 

 

volume remains accessible.

 

 

 

 

 

Message

1. This message should be considered informational

 

 

 

Stacked Volume xxxxxx is unavailable with a reason

since the subsequent processing of read-only status

 

volumes may result in transparent recovery. Your

 

code of yyyyy. (VTS z)

 

service representative should be contacted only when

 

 

 

Probable Cause

recovery of a logical volume is necessary after having

 

received the message Logical volume xxxxxx was not

 

 

 

During the reclamation process, a stacked volume was

fully recovered from damaged stacked volume yyyyyy.

 

made unavailable. The volume will subsequently be

(VTZ z).

 

placed in read-only status.

 

 

 

 

 

 

Chapter 8. Problem Determination Procedures 301

Page 323
Image 323
IBM Magstar 3494 Mount of logical volume xxxxxx failed because, Physical volume yyyyyy is not in the library. rc=rrrr