johncampbell1
3 Silver

vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3

Jump to solution

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)


F EMCSCF,DEV,DIS,DEV(4100-410F),VOL

SCF0350I 4100(*ntfnd) OFFLINE    EMC-00029700xxxx-4100-000032-41-00

SCF0350I 4101(*ntfnd) OFFLINE    EMC-00029700xxxx-4100-000036-41-01




................and so on

That *ntfnd is I suspect at the root of this problem. If I issue the same command against the 40k gatekeepers I see valid volsers as assigned by EMC:

F EMCSCF,DEV,DIS,DEV(2100-210F),VOL

SCF0350I 2100(SYM57D) OFFLINE    EMC-00029570yyyy-2100-001598-21-00

SCF0350I 2101(SYM57E) OFFLINE    EMC-00029570yyyy-2100-001599-21-01


......and so on

So, whey are these devs marked as"* ntfnd" on the new VMAX450FX and whilst the set on the 5876 vmax40k shows volser's (SYM57D, SYM57E) ?

0 Kudos
1 Solution

Accepted Solutions
PedalHarder
3 Zinc

Re: vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3

Jump to solution

Unlike Previous VMEX generations, the VMAX3 does not have labeled volumes initially. Run ICKDSF to format your volumes and they will come online.

View solution in original post

0 Kudos
4 Replies
PedalHarder
3 Zinc

Re: vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3

Jump to solution

Unlike Previous VMEX generations, the VMAX3 does not have labeled volumes initially. Run ICKDSF to format your volumes and they will come online.

View solution in original post

0 Kudos
johncampbell1
3 Silver

Re: vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3

Jump to solution

Jasonc....thanks for the tip...we'll check it out and report back asap. May i ask where this is documented?

John

0 Kudos
johncampbell1
3 Silver

Re: vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3

Jump to solution

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.

Thanks again , John.

0 Kudos
PedalHarder
3 Zinc

Re: vmax3 vmax40 differences to z/os 1.13: volser *ntfnd on vmax3

Jump to solution

In the Thin Device section of the VMAX 3 Family Product Guide there is an entry related to Thin CKD that describes the INIT requirement.

0 Kudos