I just realized you mentioned the target category specified on the mount command was VOLSPECIFIC. Check out PMH 84921,004,000 as this is a known problem being worked. Check with your CE on a timeframe when the fix will be available.
Best Regards, Les Geer IBM z/VM and Linux Development >You are referring to the z/VM530 documentation, aren't you ? > >With or without target parameter in the MOUNT cmd, the targetcat is not >changed under z/VM440 when asking for a scratch in P2P. Did the test with >z/VM530, no change. > >This hardware situation is a major regression. >We could not live if the problem was similar with MVS. We mount thousands >VTS tapes a day. > > >>> I suppose you would be aware of our peer-to-peer problem. >>> >>> When we got a 2nd 3494 in 2004, we decided to make them talk each other >>> as P2P mode. This situation revealed a major problem related to the tar= >get >>> category. In basic mode, asking to mount a scratch through vmtape, rmsma= >str >>> changed the category from scratch to volspecific. No more true in P2P (f= >or >>> us). >>> We have upgraded our 3494, we have opened PMR, we have asked the IBM >>> hardware their advice with no result. We even asked the dfsms doc to be >>> changed related the p2p part to make it clearer. >>> >>> We had to developp something to change the categories according to what >>> has been mounted during the day. I would really like to know if someone = >is >>> in the same situation >>> >> >> I was under the impression with more recent PtP microcode levels the >> restriction on a mount that a target category could not be specified >> was removed. >> >> >> Best Regards, >> Les Geer >> IBM z/VM and Linux Development >>
