Some Scratch Mounts Going To Incorrect VTSS

(Doc ID 1637511.1)

Last updated on MARCH 21, 2014

Applies to:

Sun StorageTek Enterprise Library Software (ELS) - Version 7.0 and later
IBM z/OS on System z

Symptoms

Some scratch VTV mounts are being allocated to VTDs in the wrong VTSS.

Changes

The environment contained a VSM5 with 9840D RTDs and media.  Then a VSM6 with attached T10K RTDs was added.  Once the VSM6 was installed, migrations were to be directed toward it and the T10K RTDs and only recalls would go to the VSM5/9840D RTDs. 

The customer was migrating from VSM5s to VSM6s. They shared the same MGMTCLAS. When they replaced the 9840 drives with T10Ks attached to the VSM6s, then allocation of Scratch VTVs only went to the VSM5s.

The problem was that the STORCLAS did not have a MEDIA parameter, it only had a MVCPOOL parm. Even though the MVCPOOL parm pointed to the T10K media, MVCPOOL parm is not used in the VTSS selection criteria. Therefore, VTCS was selecting VTSSs via the Default 9840 MEDIA. When the 9840s were replaced it eliminated the VSM6s from being selected, and Default Media processing only included VTSSs that had 9840 attached, in this case the VSM5.

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms