Have you experienced problems with VMTAPE when RMS or HSC was not started?

Products

• Mainframe VM Product Manager
• VM:Manager Suite for Linux on Mainframe
• VM:Manager Suite for z/VM
• VM SUITE
• VM:Tape for z/VM

Issue/Introduction

Description:

If you have VTS or Silo drives that are managed by RMS or HSC, and often find that VMTAPE and RMS/HSC are not talking, you may have experienced this situation. VMTAPE may think that the drives are NON-ARM and you are not able to get mounts to occur. If so, you might want to either add the record below to the PROFILE VMTAPE file, or, create one if it doesn't exist.

Solution:

Add this record to PROFILE VMTAPE on VMTAPE's 191 disk:

'PROCESS CALL RMS START' 
or
'PROCESS CALL HSC START'

If you do not have a PROFILE VMTAPE, review Technical Document TEC482433, "Have you heard about PROFILE VMTAPE? What it is and how it can be used".

Of course, the most important step is to make sure when you bring up VMTAPE, that RMS/HSC is up and running. In your AUTOLOG sequence, RMS/HSC should be autologged before VMTAPE and you may want to have a 'wait' of a few seconds between RMS/HSC and VMTAPE being started.

Environment

Release:
Component: VMT