Re: use of 3494 library in a second level vm system
Any guest that will need to control the ATL needs that statement. So if you every run z/OS or VSE as a guest that would need that statement also. On Tue, Feb 9, 2010 at 4:34 PM, Barbara Andrews bandr...@e1b.org wrote: No, I didn't realize that statement had to the on the userid for the guest. I just had it on both the 1st level and 2nd level RMSMASTR id's. I'll give that a try. Thanks. On Tue, 9 Feb 2010 16:13:50 -0500, Ray Waters ray.wat...@opensolutions.com wrote: Did you add STDEVOPT LIBRARY CTL to your first level directory for the VM540 second level system guest? Ray Waters -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Barbara Andrews Sent: Tuesday, February 09, 2010 3:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: use of 3494 library in a second level vm system Is it possible to use a 3494 tape library in a second level VM system? We have a 1st level VM 5.2 system that I just recently installed DFSMS/VM on as RMSONLY. And I successfully tested use of 3590 tape drives that are in our 3494 library on our 1st level VM 5.2 system. I also have a second level VM 5.4 system installed and have DFSMS/VM installed on that as RMSONLY also. We would like to test out CA's VM:Tape, VM:Backup, and VM:Operator on this second level system (user vm54test). But I am unsure on how to use the 3494 library on the second level system. Our tape devices controlled by this library are c00-c05. I varied c00 offline in our z/OS system (in a separate LPAR) and online in VM 1st level (and left c01-c05 online in z/os and offline in z/VM 1st level) and then issued: att c00 vm54test c00 But when I try to start RMSMASTR on the second level vm54test system, I get: TAPE 0C00 ATTACHED TO RMSMASTR 0C00 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 0C00, library = FSMBAC2019E Sense Data = 804800C020302041C3804004E80 0BC361311 TAPE 0C00 DETACHED BY RMSMASTR Is there something else that needs to be done other than attaching the tape device to the second level system to get this to work? NOTICE: This e-mail is intended solely for the use of the individual to whom it is addressed and may contain information that is privileged, confidential or otherwise exempt from disclosure. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the original message at the listed email address. Thank You. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
use of 3494 library in a second level vm system
Is it possible to use a 3494 tape library in a second level VM system? We have a 1st level VM 5.2 system that I just recently installed DFSMS/VM on as RMSONLY. And I successfully tested use of 3590 tape drive s that are in our 3494 library on our 1st level VM 5.2 system. I also have a second level VM 5.4 system installed and have DFSMS/VM installed on that as RMSONLY also. We would like to test out CA's VM:Tape, VM:Backup, and VM:Operator on this second level system (user vm54test). But I am unsure on how to use the 3494 library on the second level system. Our tape devices controlled by this library are c00-c05. I varied c00 offline in our z/OS system (in a separate LPAR) and online in VM 1st level (and left c01-c05 online in z/os and offline in z/VM 1st level) and then issued: att c00 vm54test c00 But when I try to start RMSMASTR on the second level vm54test system, I get: TAPE 0C00 ATTACHED TO RMSMASTR 0C00 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 0C00, library = FSMBAC2019E Sense Data = 804800C020302041C3804004E80 0BC361311 TAPE 0C00 DETACHED BY RMSMASTR Is there something else that needs to be done other than attaching the tape device to the second level system to get this to work?
Re: use of 3494 library in a second level vm system
Did you put STDEVOPT LIBRARY CTL in the 2nd level system's directory entry? -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Barbara Andrews Sent: Tuesday, February 09, 2010 4:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: use of 3494 library in a second level vm system Is it possible to use a 3494 tape library in a second level VM system? We have a 1st level VM 5.2 system that I just recently installed DFSMS/VM on as RMSONLY. And I successfully tested use of 3590 tape drive= s that are in our 3494 library on our 1st level VM 5.2 system. I also have a second level VM 5.4 system installed and have DFSMS/VM= installed on that as RMSONLY also. We would like to test out CA's VM:Tape, VM:Backup, and VM:Operator on this second level system (user vm54test). But I am unsure on how to use the 3494 library on the second = level system. Our tape devices controlled by this library are c00-c05. = I varied c00 offline in our z/OS system (in a separate LPAR) and online in = VM 1st level (and left c01-c05 online in z/os and offline in z/VM 1st level) and then issued: att c00 vm54test c00 But when I try to start RMSMASTR on the second level vm54test system, I = get: TAPE 0C00 ATTACHED TO RMSMASTR 0C00 = FSMBAC2006E Library I/O error; reason code = 3800, request identifier == 0, devic e = 0C00, library == = FSMBAC2019E Sense Data = 804800C020302041C3804004E80 0BC361311 = = TAPE 0C00 DETACHED BY RMSMASTR Is there something else that needs to be done other than attaching the = tape device to the second level system to get this to work? =
Re: use of 3494 library in a second level vm system
Did you add STDEVOPT LIBRARY CTL to your first level directory for the VM540 second level system guest? Ray Waters -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Barbara Andrews Sent: Tuesday, February 09, 2010 3:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: use of 3494 library in a second level vm system Is it possible to use a 3494 tape library in a second level VM system? We have a 1st level VM 5.2 system that I just recently installed DFSMS/VM on as RMSONLY. And I successfully tested use of 3590 tape drives that are in our 3494 library on our 1st level VM 5.2 system. I also have a second level VM 5.4 system installed and have DFSMS/VM installed on that as RMSONLY also. We would like to test out CA's VM:Tape, VM:Backup, and VM:Operator on this second level system (user vm54test). But I am unsure on how to use the 3494 library on the second level system. Our tape devices controlled by this library are c00-c05. I varied c00 offline in our z/OS system (in a separate LPAR) and online in VM 1st level (and left c01-c05 online in z/os and offline in z/VM 1st level) and then issued: att c00 vm54test c00 But when I try to start RMSMASTR on the second level vm54test system, I get: TAPE 0C00 ATTACHED TO RMSMASTR 0C00 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 0C00, library = FSMBAC2019E Sense Data = 804800C020302041C3804004E80 0BC361311 TAPE 0C00 DETACHED BY RMSMASTR Is there something else that needs to be done other than attaching the tape device to the second level system to get this to work? NOTICE: This e-mail is intended solely for the use of the individual to whom it is addressed and may contain information that is privileged, confidential or otherwise exempt from disclosure. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the original message at the listed email address. Thank You.
Re: use of 3494 library in a second level vm system
No, I didn't realize that statement had to the on the userid for the guest. I just had it on both the 1st level and 2nd level RMSMASTR id's. I'll give that a try. Thanks. On Tue, 9 Feb 2010 16:13:50 -0500, Ray Waters ray.wat...@opensolutions.com wrote: Did you add STDEVOPT LIBRARY CTL to your first level directory for the VM540 second level system guest? Ray Waters -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Barbara Andrews Sent: Tuesday, February 09, 2010 3:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: use of 3494 library in a second level vm system Is it possible to use a 3494 tape library in a second level VM system? We have a 1st level VM 5.2 system that I just recently installed DFSMS/VM on as RMSONLY. And I successfully tested use of 3590 tape driv es that are in our 3494 library on our 1st level VM 5.2 system. I also have a second level VM 5.4 system installed and have DFSMS/V M installed on that as RMSONLY also. We would like to test out CA's VM:Tape, VM:Backup, and VM:Operator on this second level system (user vm54test). But I am unsure on how to use the 3494 library on the second level system. Our tape devices controlled by this library are c00-c05. I varied c00 offline in our z/OS system (in a separate LPAR) and online in VM 1st level (and left c01-c05 online in z/os and offline in z/VM 1st level) and then issued: att c00 vm54test c00 But when I try to start RMSMASTR on the second level vm54test system, I get: TAPE 0C00 ATTACHED TO RMSMASTR 0C00 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 0C00, library = FSMBAC2019E Sense Data = 804800C020302041C3804004E80 0BC361311 TAPE 0C00 DETACHED BY RMSMASTR Is there something else that needs to be done other than attaching the tape device to the second level system to get this to work? NOTICE: This e-mail is intended solely for the use of the individual to whom it is addressed and may contain information that is privileged, confidential or otherwise exempt from disclosure. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for deliverin g the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the original message at the listed email address. Thank You.