vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3
We have a mapping / presentation issue on a new vmax450AF where effectively the volser is obscured to the z/os by the legend
*ntfnd
A similar command against our production VMAX40K from same mainframe reveals valid EMC volser identities for some GK devices.
Here's the output firstly showing new test SSID 4100 on a VMAX450FX dedicated to z/os
First of all, if I try to bring 4100 online I get the same I/O error as previously:
V 4100,ONLINE
IEF503I UNIT 4100 I/O ERROR
And the explanation for this error as I’ve mentioned before suggests there may be a problem with the volser. That’s a z/OS command by the way and the V is for VARY.
When I try an EMC display command I now get this: ...(note this is the 5977 VMAX450AF)
Jasonc...thank you ...yes its worked! And given a volser of the SSID eg. XX4000 (for dev 4000).
Marked your original reply as correct. A different process to our past opex with VMAX and VMAX40k though....so we'd really appreciate a link if we've missed something in the documentation.
PedalHarder
4 Apprentice
•
465 Posts
4599
0
Posted July 2nd, 2017 22:00
Unlike Previous VMEX generations, the VMAX3 does not have labeled volumes initially. Run ICKDSF to format your volumes and they will come online.