VTAPE USS (NFS) Recall attempts fail from one LPAR and not the other LPAR in the SYSPLEX.

book

Article ID: 220374

calendar_today

Updated On:

Products

CA Vtape Virtual Tape System

Issue/Introduction

When a CA VTAPE USS (NFS) recall attempt is made from one of our LPARs (Vtape RecallServer = CLIENT), we are receiving the following message:

IEC145I 413-08,IFG0194K,$RECALL,RECALL,TAPE#,04F7,, 
FDRABR.xxxxxxxx.yyyyyyyy                                        
FDR324** DDNAME=TAPE#    IS MISSING OR IN ERROR REASON=U - OPEN

When the recall is attempted from the other LPAR (Vtape RecallServer = SERVER), the file is recalled and everything works.

Cause

The Client Vtape (RecallServer = CLIENT) in a Vtape complex does not have the USS mounts defined (or shared) between the Vtapes in the complex.  

Environment

Release : 12.6

Component : CA VTAPE

Resolution

The Client Vtape (RecallServer = CLIENT) in the CA Vtape Complex (that is, Vtapes sharing the same Global VCAT) needs to use the same USS definitions as used by the Server Vtape (RecallServer = SERVER), even though the Client Vtape will not actually perform the Recalls.  Also, the Client Vtape should have the settings MAXDRIVES=0 and MAXUSS=0 so that it will function as a Client.

Additional Information

USS Mount Points in a CA Vtape Complex:


https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-vtape-virtual-tape-system/12-6/configuring/the-backstore-engine/uss-backstore/uss-mount-points-in-a-ca-vtape-complex.html