Subject: RE: Using Virtual Tape with Shared Power Queues
From: Frank M. Ramaekers (FRamaekers@ailife.com)
Date: Wed Nov 11 2009 - 15:41:04 EST
I think the IJSYSRS.SYSLIB is shared, not the SVA. In any case, you can populate the SVA from different libraries (in each system), by using a different LIBDEF. Although, I don't know when this ($IJBVTAP) get's loaded. Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 ________________________________ From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Rbotsis@aol.com Sent: Wednesday, November 11, 2009 2:23 PM To: VSE Discussion List Subject: Re: Using Virtual Tape with Shared Power Queues Something isn't right here. How can you have ONE SVA with 2 different LPAR's? Hi Gustavo, That is the solution that I'm working on right now, the issue I'm currently having is the $IJBVTAP is in the SVA and is loaded for IJSYSRS.SYSLIB which is also shared between the 2 systems. Anyway what is currently working for me is running a job that has a VTAPE START not a VTAPE STOP like Kevin suggested yesterday, the TAPESRVR job stays up until a VTAPE STOP is run for the original virtual address. It ain't pretty, but it works. Louie Callari ________________________________ From: Gustavo Torres <clgtorres@gmail.com> To: VSE Discussion List <vse-l@Lehigh.EDU> Sent: Wed, November 11, 2009 1:59:27 PM Subject: Re: Using Virtual Tape with Shared Power Queues You can do it this way: Submit one TAPE Server JCL to each system with diferent JNMs including your SYSIDs. Zap $IJBVTAP on each system in order to release the corresponding JCL. On Wed, Nov 11, 2009 at 12:59 PM, Louis Callari <louis.callari@yahoo.com> wrote: I did find PRELEASE RDR,TAPESRVR at location 21CB in phase $IJBVTAP I'll start there and see what happens. _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at PrivacyAct@ailife.com.
This archive was generated by hypermail 2b25 : Sun Nov 22 2009 - 16:20:07 EST