Re: DFSMSRM Errors in RMSMASTR
I just looked and none of these APARs are listed in the upgrade/setup. I have just installed DFSMS VM 221 on z/VM 5.3 The "ADDSERV" says this is at ESO0702, and the VMFINO only list apars from 1993. Do I need these APARs for 5.3. 10 00/08/15 VM62522 UM29738 0008 HIPER DFSMS MOVE IN CSE CLUSTER 9. 99/04/15 VM62133 UM29280 9903 THE FSMRMVST MODULE, FIRSTE 8. 99/04/15 VM62089 UM29248 9903 SEVERAL PROBLEMS WITHIN THE 7 98/07/31 VM61781 UM28993 9807 HIPER VGS FSMRMVGS TERRIBLE 6. 96/10/21 VM60753 UM28457 9709 DFSMS PART HANDLER FSMBDMLD 5 95/01/20 VM59034 UM26933 9501 MSFSMBAC2006E RSN3740 4 94/03/28 VM57835 UM25767 9404 MINIDISK MOVE PROCESSING IN 3 94/03/18 VM57630 UM25767 9404 MSFSMZCG3039E DFSMS NOT 2 93/07/22 VM55830 UM24457 9404 ENHANCEMENTS TO RMS FUNCTION 1. 93/03/29 VM55497 UM24117 9404 HIPER ML1 FILES ERASED WHEN End of Upgrade DFSMSVM221 , Subset SMS221 , as of 2006/07/04. Rate this page Please take a moment to complete this form to help us better serve you. This material provides me with the information I need. Strongly Agree Agree Neutral Disagree Strongly Disagree The language of this material is easy to understand. Strongly Agree Agree Neutral Disagree Strongly Disagree Did the information help you to achieve your goal? Yes No Don't know Please provide us with comments to help improve this page: Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site. Input the verification number to submit feedback: Verification number: 32647 Document information Product categories: Software Operating System z/OS family IBM Group: IBM Server Group Modified date: 2005-01-05 Translate My Page Select language Return to English Brazilian Portuguese French German Italian Japanese Korean Spanish Simplified Chinese Traditional Chinese Rate this page Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site. "Les Geer (607-429-3580)" [EMAIL PROTECTED]Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/12/2007 01:28 PM EST Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To "IBMVM@LISTSERV.UARK.EDU" IBMVM@LISTSERV.UARK.EDU cc bcc Subject Re: DFSMSRM Errors in RMSMASTR That would be scratch0 I believe. I've been trying some stuff thismorning after reading your note. I disassociated the drive from thescratch pool and when I re-started the RMSMASTR machine, there were nosense errors. I was able to manually mount a tape which was volspecific.After re-associating the drive to the scratch0 pool, I once again gotthe errors on initialization of RMSMASTR.Which APAR(s) should I be applying to bring DFSMS/VM current?The APARs which allow RMS to issue a query device without attachingthe device are VM64062 and VM64206 for RMS, and VM64157 for CP.However, none of this service in my belief will help solve theI/O errors you are receiving. If you associate a device with aparticular scratch pool, and there are volumes in this pool, theI/O error seems strange. You should ask the CE about this. Of coursethey will point to the software. So if you obtain a trsource trace ofthe I/O error we can tell you exactly what I/O is failing and what theerror is.Best Regards,Les GeerIBM z/VM and Linux Development__ This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
Les, What APAR or APARs would that be? Jim -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580) Sent: Tuesday, December 11, 2007 5:10 PM To: IBMVM@LISTSERV.UARK.EDU Subject: DFSMSRM Errors in RMSMASTR BTW, if you order latest DFSMS service, which removes the need by RMS to attach the drive to issue the query drive command, there is corresponding CP service required. Best Regards, Les Geer IBM z/VM and Linux Development This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: DFSMSRM Errors in RMSMASTR
Les, That would be scratch0 I believe. I've been trying some stuff this morning after reading your note. I disassociated the drive from the scratch pool and when I re-started the RMSMASTR machine, there were no sense errors. I was able to manually mount a tape which was volspecific. After re-associating the drive to the scratch0 pool, I once again got the errors on initialization of RMSMASTR. Which APAR(s) should I be applying to bring DFSMS/VM current? Thanks, Dave -Original Message- From: Les Geer (607-429-3580) [EMAIL PROTECTED] Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DFSMSRM Errors in RMSMASTR Date: Tue, 11 Dec 2007 21:36:05 -0500 What was the category the device was assigned to in the previous query? Best Regards, Les Geer IBM z/VM and Linux Development I have 4 tapes assigned to the category scratch0 and 2 assigned to volspecific: FSMBCJ2182I SCRATCH0 VM 3592 300GB FSMBCJ2182I SCRATCH0 VM0001 3592 300GB FSMBCJ2182I SCRATCH0 VM0002 3592 300GB FSMBCJ2182I SCRATCH0 VM0003 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0004 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0005 3592 300GB Dave Keeton Systems Programmer Enterprise Systems Oregon State Data Center (503) 373-0832 email: [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
That would be scratch0 I believe. I've been trying some stuff this morning after reading your note. I disassociated the drive from the scratch pool and when I re-started the RMSMASTR machine, there were no sense errors. I was able to manually mount a tape which was volspecific. After re-associating the drive to the scratch0 pool, I once again got the errors on initialization of RMSMASTR. Which APAR(s) should I be applying to bring DFSMS/VM current? The APARs which allow RMS to issue a query device without attaching the device are VM64062 and VM64206 for RMS, and VM64157 for CP. However, none of this service in my belief will help solve the I/O errors you are receiving. If you associate a device with a particular scratch pool, and there are volumes in this pool, the I/O error seems strange. You should ask the CE about this. Of course they will point to the software. So if you obtain a trsource trace of the I/O error we can tell you exactly what I/O is failing and what the error is. Best Regards, Les Geer IBM z/VM and Linux Development
Re: DFSMSRM Errors in RMSMASTR
Those errors sound like something I once had. The errors were inconsistant and somewhat random. I spent weeks writing error recovery routines for my program and was pretty much at my witts end. Then I switched the cable to a different card and PRESTO the errors went to the z/OS LPAR.. Maybe not your problem, but if you have a spare cable and can try switching them it may be worth the effort. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Dave Keeton Sent: Wednesday, December 12, 2007 10:17 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DFSMSRM Errors in RMSMASTR Les, That would be scratch0 I believe. I've been trying some stuff this morning after reading your note. I disassociated the drive from the scratch pool and when I re-started the RMSMASTR machine, there were no sense errors. I was able to manually mount a tape which was volspecific. After re-associating the drive to the scratch0 pool, I once again got the errors on initialization of RMSMASTR. Which APAR(s) should I be applying to bring DFSMS/VM current? Thanks, Dave -Original Message- From: Les Geer (607-429-3580) [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU mailto:The%20IBM%20z/[EMAIL PROTECTED] e To: IBMVM@LISTSERV.UARK.EDU mailto:IBMVM@LISTSERV.UARK.EDU Subject: Re: DFSMSRM Errors in RMSMASTR Date: Tue, 11 Dec 2007 21:36:05 -0500 What was the category the device was assigned to in the previous query? Best Regards, Les Geer IBM z/VM and Linux Development I have 4 tapes assigned to the category scratch0 and 2 assigned to volspecific: FSMBCJ2182I SCRATCH0 VM 3592 300GB FSMBCJ2182I SCRATCH0 VM0001 3592 300GB FSMBCJ2182I SCRATCH0 VM0002 3592 300GB FSMBCJ2182I SCRATCH0 VM0003 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0004 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0005 3592 300GB Dave Keeton Systems Programmer Enterprise Systems Oregon State Data Center (503) 373-0832 email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
My MVS counterpart, 20+ years ago, would ask me to run with a piece of equipment on VM if it was suspect on MVS because, at that time MVS error recovery was so much better than VM's that it was harder to tell if there was a hardware error on something connected to MVS. It would just recover, but VM would let you know, sometimes with a CP abend. Jim Huegel, Thomas wrote: This is a multi-part message in MIME format. --_=_NextPart_001_01C83CF7.6333BE72 Content-Type: text/plain;charset=utf-8 X-EC0D2A8E-5CB7-4969-9C36-46D859D137BE-PartID: C2F4CFB4-5DC5-4C0B-BD01-766418D2226B Those errors sound like something I once had. The errors were inconsistant and somewhat random. I spent weeks writing error recovery routines for my program and was pretty much at my witts end. Then I switched the cable to a different card and PRESTO the errors went to the z/OS LPAR.. Maybe not your problem, but if you have a spare cable and can try switching them it may be worth the effort. -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
The APARs which allow RMS to issue a query device without attaching the device are VM64062 and VM64206 for RMS, and VM64157 for CP. However, none of this service in my belief will help solve the I/O errors you are receiving. If you associate a device with a particular scratch pool, and there are volumes in this pool, the I/O error seems strange. You should ask the CE about this. Of course they will point to the software. So if you obtain a trsource trace of the I/O error we can tell you exactly what I/O is failing and what the error is. Thanks for the APAR info, Les! Having never done a trace before, I'm not sure how to proceed. Should I use the TRACE command? You mention 'trsource', which I see on the z/VM Downloads page, but I'm not sure if that's what I need or not. Please advise, Dave
Re: DFSMSRM Errors in RMSMASTR
Dave, What level of z/VM are you running ... your DFSMS/VM software appears to be back level. With the current SDO for DFSMS/VM installed, a DFSMSRM QUERY LIBRARY DEVICE command will not generate a CP ATTACH/DETACH sequence for the device on the RMSMASTR virtual machine. I also see the device you are working with is a 3592 (the most recent hardware from IBM), so these error may go away by upgrading your DFSMS/VM software. JR JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
We're running z/VM 5.2 and DFSMS/VM that came with the SDO. Sounds like maybe I'm behind on fixes? -Original Message- From: Imler, Steven J [EMAIL PROTECTED] Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DFSMSRM Errors in RMSMASTR Date: Tue, 11 Dec 2007 14:36:56 -0500 Dave, What level of z/VM are you running ... your DFSMS/VM software appears to be back level. With the current SDO for DFSMS/VM installed, a DFSMSRM QUERY LIBRARY DEVICE command will not generate a CP ATTACH/DETACH sequence for the device on the RMSMASTR virtual machine. I also see the device you are working with is a 3592 (the most recent hardware from IBM), so these error may go away by upgrading your DFSMS/VM software. JR JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] Dave Keeton Systems Programmer Enterprise Systems Oregon State Data Center (503) 373-0832 email: [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
Yeah, I suppose doing a demount before mounting the tape probably doesn't make any sense. First, I restarted the RMSMASTR machine. Here's what it said after the PROFILE EXEC ran: FSMBBV3053I All DFSMS local APPC/VM resources initialized FSMRMBLC== Diag 254 is available TAPE 4116 ATTACHED TO RMSMASTR 4116 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 4116, library = FSMBAC2019E Sense Data = 804004272030202364C44340404040404034001213902004E82 05D8F2011 TAPE 4116 DETACHED BY RMSMASTR FSMBBD2241W Device 4116 could not be initialized Then I tried to mount a tape from the DFSMS machine: dfsmsrm mount vol vm DGTUIR2026I DFSMS request 12 accepted for processing Ready; T=0.01/0.01 15:26:16 15:26:17 * MSG FROM RMSMASTR:FSMBAD2006E Library I/O error; reason code = 3800, request identifier = 12, device = 4116, library = TLLIB01 The line about Sense Data make no sense to me... Dave -Original Message- From: Les Geer (607-429-3580) [EMAIL PROTECTED] Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU Subject: DFSMSRM Errors in RMSMASTR Date: Tue, 11 Dec 2007 17:09:57 -0500 Well, you queried the drive, and the response was no tape mounted. Next you issued a demount to the drive which received the I/O error, probably because there was nothing to demount. Try mounting a tape then see if the demount is successful. BTW, if you order latest DFSMS service, which removes the need by RMS to attach the drive to issue the query drive command, there is corresponding CP service required. Best Regards, Les Geer IBM z/VM and Linux Development Yesterday I was getting pretty excited because I actually got VM talking to our tape library. I was able to see the volumes that were assigned to me and assign them to a scratch category. I even mounted a tape, invoked DDR and dumped a MOD3 and a MOD9 to the tape. Then, later that day, I started having problems. Now when I start up the RMSMASTR machine, I get errors about not being able to talk to the drive. I've tried varying off and on the chpid, path and device address, but that didn't seem to help. The IBM technician said that the drive looks fine. This morning I tried going through the DFSMS/VM Customization manual and testing the RMSMASTR. Here's what I'm getting: dfsmsrm q lib dev 4116 RMSMASTR: FSMEIF1211I DFSMS RM QUERY LIBRARY with NOWAIT received from user DFSM S, request identifier = 15 DGTUIR2026I DFSMS request 15 accepted for processing Ready; T=0.01/0.01 12:17:18 RMSMASTR: TAPE 4116 ATTACHED TO RMSMASTR 4116 RMSMASTR: TAPE 4116 DETACHED BY RMSMASTR 12:17:18 * MSG FROM RMSMASTR:FSMBCI2200I Device 4116: Device Type = 3592, Library Name = TLLIB01, VLABEL = N/A, Mounted Category = NONE, Assigned Category = SCRATCH0 dfsmsrm demount rdev 4116 RMSMASTR: FSMEIF1211I DFSMS RM DEMOUNT with NOWAIT received from user DFSMS, request identifier = 18 DGTUIR2026I DFSMS request 18 accepted for processing Ready; T=0.01/0.01 12:17:47 RMSMASTR: TAPE 4116 ATTACHED TO RMSMASTR 4116 RMSMASTR: TAPE 4116 DETACHED BY RMSMASTR RMSMASTR: FSMBAC2006E Library I/O error; reason code = 3800, request identifier= 18, device = 4116, library = TLLIB01 RMSMASTR: FSMBAC2019E Sense Data = 804004272030202364C44340404040404034001213902004E8205D8F2011 12:17:47 * MSG FROM RMSMASTR:FSMBAD2006E Library I/O error; reason code = 3800, request identifier = 18, device = 4116, library = TLLIB01 Has anyone seen this before or have any insight as to what might be going on? Dave Keeton Systems Programmer Enterprise Systems Oregon State Data Center (503) 373-0832 email: [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
During initialization, RMS does a demount to each drive it can access. However now that I think about this, there is a different error that comes back which RMS intercepts indicating there is no volume mounted. An error that is not reflected like this sense is. I recently worked on a similar problem, which turned out to be the drive somehow had been assigned as an autoloader for a particular scratch tape. Did the query you previously showed indicate the device was assigned category SCRATCH0? Do you have any tapes in this category? Best Regards, Les Geer IBM z/VM and Linux Development Yeah, I suppose doing a demount before mounting the tape probably doesn't make any sense. First, I restarted the RMSMASTR machine. Here's what it said after the PROFILE EXEC ran: FSMBBV3053I All DFSMS local APPC/VM resources initialized FSMRMBLC== Diag 254 is available TAPE 4116 ATTACHED TO RMSMASTR 4116 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 4116, library = FSMBAC2019E Sense Data = 804004272030202364C44340404040404034001213902004E82 05D8F2011 TAPE 4116 DETACHED BY RMSMASTR FSMBBD2241W Device 4116 could not be initialized Then I tried to mount a tape from the DFSMS machine: dfsmsrm mount vol vm DGTUIR2026I DFSMS request 12 accepted for processing Ready; T=0.01/0.01 15:26:16 15:26:17 * MSG FROM RMSMASTR:FSMBAD2006E Library I/O error; reason code = 3800, request identifier = 12, device = 4116, library = TLLIB01 The line about Sense Data make no sense to me...
Re: DFSMSRM Errors in RMSMASTR
I have 4 tapes assigned to the category scratch0 and 2 assigned to volspecific: FSMBCJ2182I SCRATCH0 VM 3592 300GB FSMBCJ2182I SCRATCH0 VM0001 3592 300GB FSMBCJ2182I SCRATCH0 VM0002 3592 300GB FSMBCJ2182I SCRATCH0 VM0003 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0004 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0005 3592 300GB -Original Message- From: Les Geer (607-429-3580) [EMAIL PROTECTED] Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DFSMSRM Errors in RMSMASTR Date: Tue, 11 Dec 2007 18:28:02 -0500 During initialization, RMS does a demount to each drive it can access. However now that I think about this, there is a different error that comes back which RMS intercepts indicating there is no volume mounted. An error that is not reflected like this sense is. I recently worked on a similar problem, which turned out to be the drive somehow had been assigned as an autoloader for a particular scratch tape. Did the query you previously showed indicate the device was assigned category SCRATCH0? Do you have any tapes in this category? Best Regards, Les Geer IBM z/VM and Linux Development Yeah, I suppose doing a demount before mounting the tape probably doesn't make any sense. First, I restarted the RMSMASTR machine. Here's what it said after the PROFILE EXEC ran: FSMBBV3053I All DFSMS local APPC/VM resources initialized FSMRMBLC== Diag 254 is available TAPE 4116 ATTACHED TO RMSMASTR 4116 FSMBAC2006E Library I/O error; reason code = 3800, request identifier = 0, devic e = 4116, library = FSMBAC2019E Sense Data = 804004272030202364C44340404040404034001213902004E82 05D8F2011 TAPE 4116 DETACHED BY RMSMASTR FSMBBD2241W Device 4116 could not be initialized Then I tried to mount a tape from the DFSMS machine: dfsmsrm mount vol vm DGTUIR2026I DFSMS request 12 accepted for processing Ready; T=0.01/0.01 15:26:16 15:26:17 * MSG FROM RMSMASTR:FSMBAD2006E Library I/O error; reason code = 3800, request identifier = 12, device = 4116, library = TLLIB01 The line about Sense Data make no sense to me... Dave Keeton Systems Programmer Enterprise Systems Oregon State Data Center (503) 373-0832 email: [EMAIL PROTECTED]
Re: DFSMSRM Errors in RMSMASTR
What was the category the device was assigned to in the previous query? Best Regards, Les Geer IBM z/VM and Linux Development I have 4 tapes assigned to the category scratch0 and 2 assigned to volspecific: FSMBCJ2182I SCRATCH0 VM 3592 300GB FSMBCJ2182I SCRATCH0 VM0001 3592 300GB FSMBCJ2182I SCRATCH0 VM0002 3592 300GB FSMBCJ2182I SCRATCH0 VM0003 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0004 3592 300GB FSMBCJ2182I VOLSPECIFIC VM0005 3592 300GB
