Re: a cautionary tale

2006-10-10 Thread Nick Laflamme
David Kreuter wrote: Cynic that I am I still think dumb luck played a part here; the linux admin thinks otherwise. In any case linux on the mainframe under z/VM continues to astound and delight. Deleting devices so a guest can't see them seems analogous to me to a power supply failing on a

Re: a cautionary tale

2006-10-10 Thread David Kreuter
Title: RE: [IBMVM] a cautionary tale no not really, the LPAR that the dynamic I/O was issued from sends the command to the processor controller, which updates the HSA. The LPAR used is just the interface to the really real I/O stored up there somewhere. Yes I agree it was like a power supply

Re: a cautionary tale

2006-10-06 Thread Mark Pace, Mainline Information System
I converted from z/VM 5.1 to z/VM 5.2 Tuesday. Now my DFSMS RMM mounts are not working properly. I have both 3490 3590 drives in a 3494 ATL. In the RMM config I have the drives listed 580 - 581 3490 tapes 590 - 592 3590 tapes If I try to mount a tape, rmmastr will connect the first

DFSMS RMM - was, accidentally, Re: a cautionary tale

2006-10-06 Thread Mark Pace, Mainline Information System
Where are you doing the mounts from? Is this via the DFSMSRM command or via VGS for a VSE guest? Since you have two libraries, did you tell RMS and VGS about both libraries, and are you selecting the library on the mount command? I'm using DFSMSRM mount commands from my VM user id. I only have

DFSMS RMM - was, accidentally, Re: a cautionary tale

2006-10-06 Thread Les Geer (607-429-3580)
I'm using DFSMSRM mount commands from my VM user id. I only have 1 library with multiple drive types. 1 Frame has a 3490 C2A drive, the other frame as 3 - 3590 drives. Hmm, okay, well the problem here is you have one library with two different drive types and specific volumes for each. When