Jeff, Does VSE run DYNAM/T?
If so, the OWNER ID in the DSN must have the Library ID in the first byte and the Scratch pool in the second byte. For example 30. Data Set: P.RLWSAVE1 Password: Type: TAPE Disk Filetype: Ngens: 0 Retention: 1 Owner ID: 30 Lock: NO My tapes would be in Library 3 CHG3490 and in SCRATCH0 or category 80. My LIBCONFG LIST: 1 CHH3490 2 CHH3590 3 CHG3490 4 CHG3590 DGTVCNTL DATA: RM_AUTO_LIBRARY CHH3490 B2114 WATERSR * AUTOMATED RM_AUTO_LIBRARY CHH3590 17759 WATERSR * AUTOMATED RM_AUTO_LIBRARY CHG3490 B1215 WATERSR * AUTOMATED RM_AUTO_LIBRARY CHG3590 12311 WATERSR * AUTOMATED Ray Waters -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Jeff Forte Sent: Wednesday, September 02, 2009 11:13 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Multiple VTS libraries - RMSMASTR & VGLIBSRV Yes, the two userids were recycled after the updates to the various config files. I don't know that all the drives had been attached/detached from RMSMASTR before I xautologed VGLIBSRV. I can sure try that to see if it helps. Jeff Forte On Wed, 2 Sep 2009 11:57:03 -0400, Ray Waters <ray.wat...@opensolutions.com> wrote: >Did you cycle RMSMASTR, VGLIBSRV? > >How I do it is(from MY VM ID): STOP_VGS I > >Then >CP FORCE RMSMASTR >CP FORCE VGLIBSTRV > >Next XAUTOLGO RMSMASTR >CP Q TAPE ATTACH RMSMASTR >Wait until all tapes have been attached/detached to/from RMSMASTR >Then: CP XAUTOLOG VGLIBSRV > >Ray Waters > >-----Original Message----- >From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Jeff Forte >Sent: Wednesday, September 02, 2009 10:49 AM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Multiple VTS libraries - RMSMASTR & VGLIBSRV > >We are trying to add an additional VTS library to one of our z/VM systems >running VSE guests. I have made the updates to the RMCONFIG DATA (Add the >new drives) and DGTVCNTL DATA (Add additional RM_AUTO_LIBRARY)in >VMSYS:DFSMS.CONTROL. On VGLIBSRV, I've updated the LIBCONFG LIST to >include the new library name and updated FSMRMVGC EXEC to add the >additional drives to the DRIVE_LIST_3490 variable. This seems to be the >only required updates, yet when the VSE guest submits their jobs, the >VGLIBSRV console shows the following - > >10:49:32.232091 New request type: QS CID=00000000 RID=VSE3SBX >10:49:32.267682 QS request complete. ID=0 RC=8 Reason=5026 >10:49:32.325331 New request type: MV CID=00000001 RID=VSE3SBX >10:49:32.326188 MV request complete. ID=0 RC=8 Reason=5026 > >That reason code says > >5026 Library not known The library name specified in a request is >not found in the VGS library configuration file LIBCONFG LIST A. Update or >correct this file and retry the request. > >With the one library defined, we have no issues at all with the drives >being attached to the VSE guest. Only when trying to define the new VTS. >Once all the data is migrated, we will delete the old addresses. > >What am I missing ?? > >Jeff Forte > >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. 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.
