Re: DDR to standard labeled tapes
I know you can do that as a crude FSF file, but you can't BSF without CMS. A CP command to FSF would be much faster and cleaner than multiple IPL's. CP already provides REWIND, so a command to do FSF and BSF isn't much of a stretch. Maybe I'll write an IPL'able utility that will issue FSF and BSF commands to a tape drive. I'll IPL that whenever I need to re-position my main tape drive. g Brian Nielsen On Thu, 8 Jun 2006 15:30:11 -0700, Schuh, Richard [EMAIL PROTECTED] wrote : You do not have to use CMS. IPL commands will work just like loading fro m the HMC. IPL 181 Read VOL1 label; Get a message IPL 181 Read HDR1; Get a message IPL 181 Read HDR2 and get a message IPL 181 Cross the tape mark and get a message IPL 181 And you are there If your tape just has a VOL1 without the HDR records, you shorten the process by 2 IPL commands. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Thursday, June 08, 2006 3:21 PM To:IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes That was my point, 2nd level you have to use CMS to do the tape poisitoning, there is not a CP command. If you're logged onto a userid = that doesn't normally have access to CMS (ex. a z/OS guest) there is ext r= a work to do to get CMS running (such as linking the MAINT 190 disk) just t= o position the tape. If the z/OS guest already uses address 190 it's even = more extra work. (Not to mention the error messages when you IPL CMS if = you don't also have a 191 or 19E disk.) CP provides only a REWIND command. How hard would a FSF/BSF type comman d= be? Brian Nielsen On Thu, 8 Jun 2006 17:38:07 -0400, carlos martinez [EMAIL PROTECTED] = wrote: But from second level cms: Tape FSF N CP term con 3270 Cp IPL CL LOADPARM CUU -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, June 08, 2006 5:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes How about TAPE FSF ( VDEV is 181 as a default) TAPE is a CMS command, not a CP command. = ===
Re: DDR to standard labeled tapes
You can manually BSF all the way to load point - it was called a Rewind button in the olden days :). I think there is a different name on the button nowadays; however, I can't be sure because the machine room is over 1000 miles away. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Friday, June 09, 2006 7:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject:Re: DDR to standard labeled tapes I know you can do that as a crude FSF file, but you can't BSF without CMS. A CP command to FSF would be much faster and cleaner than multiple = IPL's. CP already provides REWIND, so a command to do FSF and BSF isn't much of = a stretch. Maybe I'll write an IPL'able utility that will issue FSF and BSF commands= to a tape drive. I'll IPL that whenever I need to re-position my main = tape drive. g Brian Nielsen On Thu, 8 Jun 2006 15:30:11 -0700, Schuh, Richard [EMAIL PROTECTED] wrote= : You do not have to use CMS. IPL commands will work just like loading fro= m the HMC. IPL 181 Read VOL1 label; Get a message IPL 181 Read HDR1; Get a message IPL 181 Read HDR2 and get a message IPL 181 Cross the tape mark and get a message IPL 181 And you are there If your tape just has a VOL1 without the HDR records, you shorten the = process by 2 IPL commands. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] = On Behalf Of Brian Nielsen Sent: Thursday, June 08, 2006 3:21 PM To:IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes That was my point, 2nd level you have to use CMS to do the tape poisitoning, there is not a CP command. If you're logged onto a userid = = that doesn't normally have access to CMS (ex. a z/OS guest) there is ext= r= a work to do to get CMS running (such as linking the MAINT 190 disk) just = t= o position the tape. If the z/OS guest already uses address 190 it's even= = more extra work. (Not to mention the error messages when you IPL CMS if= = you don't also have a 191 or 19E disk.) CP provides only a REWIND command. How hard would a FSF/BSF type comman= d= be? Brian Nielsen On Thu, 8 Jun 2006 17:38:07 -0400, carlos martinez [EMAIL PROTECTED]= = wrote: But from second level cms: Tape FSF N CP term con 3270 Cp IPL CL LOADPARM CUU -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On= Behalf Of David Boyes Sent: Thursday, June 08, 2006 5:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes How about TAPE FSF ( VDEV is 181 as a default) TAPE is a CMS command, not a CP command. = == ===
Re: DDR to standard labeled tapes
On Friday, 06/09/2006 at 08:48 MST, Schuh, Richard [EMAIL PROTECTED] wrote: I never saw the problem on a 3088 - we had a 9088 that apparently did the right thing when it received the IPL reset signal :) In any event, this applies to anything that causes an interrupt when the stand-alone program has been ipled and is waiting for the console interrupt. In the Dark Ages (stone knives and bear skins), CTCs were problematic for SA programs because the interrupts are generated by the system on the *other* end. The various SA programs that still depend on an I/O interrupt in addition to, or instead of, LOADPARM were changed in the Middle Ages (represented by the invention of Sense ID) to examine more closely the cyberDNS of interrupting device. 3088s exacerbated the problem because it was so easy to fully interconnect the attached systems. Or someone decided that *now* would be good time to ENABLE one of the adapters. :-) For a 3088/CTC, the channel reset only affects *this* system's I/O status. The other side can still restart the link and annoy your SA program. If you find an SA program that gets confused by random interrupts and cannot be overridden by LOADPARM, you should probably call it in. With the XA I/O architecture there are all kinds of interrupts that can come in that have nothing to do with a tape was mounted or somebody flipped the test/normal switch on the 3278 or Attention was pressed on the 3215. Alan Altmark z/VM Development IBM Endicott
Re: DDR to standard labeled tapes
Watch that dark ages stuff, Chuckie. By the time I saw that problem, I was no longer keying on an 029 or maybe 026. I had graduated to a 3278 or 3279, altho I did then and still do carry 5081 cards in my pocket. Jim At 01:31 PM 6/9/2006, you wrote: In the Dark Ages (stone knives and bear skins), CTCs were problematic for SA programs because the interrupts are generated by the system on the *other* end. The various SA programs that still depend on an I/O interrupt in addition to, or instead of, LOADPARM were changed in the Middle Ages (represented by the invention of Sense ID) to examine more closely the cyberDNS of interrupting device. 3088s exacerbated the problem because it was so easy to fully interconnect the attached systems. Or someone decided that *now* would be good time to ENABLE one of the adapters. :-) For a 3088/CTC, the channel reset only affects *this* system's I/O status. The other side can still restart the link and annoy your SA program. If you find an SA program that gets confused by random interrupts and cannot be overridden by LOADPARM, you should probably call it in. With the XA I/O architecture there are all kinds of interrupts that can come in that have nothing to do with a tape was mounted or somebody flipped the test/normal switch on the 3278 or Attention was pressed on the 3215. Alan Altmark z/VM Development IBM Endicott Jim Bohnsack Cornell Univ. (607) 255-1760
Re: DDR to standard labeled tapes
Never ran into that with a 3088, but I certainly did back with a 3705. We ended up having that Ctrlr on a channel switch which we had to disable when booting. Early during an HPO release (4.somethng IIRC), we even saw it interfere with a CP IPL until we worked with a Standalone Dump and Level II for a PTF. Jim Bohnsack wrote: Another gotcha that I discovered about 20 years ago on a system that had a 3088 connected to it, is that some other types of equipment, in this case, 3088's can confuse a SA program into thinking that it is getting 3270 attn interrupts. I was not, very dependable, able to ipl a SA tape unless I would first disable the channel adapter on the 3088. I don't know what other kind of equipment can generate fake 3270 interrupts. Maybe nothing, but it can be frustrating if you are pretty sure that you're ipled a real program from the tape, but the program thinks that the interrupt it got is from the address it wants to talk to and it's something out on the machine room floor.
Re: DDR to standard labeled tapes
You must be a kid if you don't know what 5081 cards are or am I the only one on the list who does? Jim At 03:11 PM 6/9/2006, you wrote: John, carry 5081 cards in my pocket Wow! 5,081 cards in your pocket!? Must be really small cards or really big pockets! Talk about playing with a full deck! :-) Ah, it's Friday, isn't it? Mike Walter Jim Bohnsack [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/09/2006 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: DDR to standard labeled tapes Watch that dark ages stuff, Chuckie. By the time I saw that problem, I was no longer keying on an 029 or maybe 026. I had graduated to a 3278 or 3279, altho I did then and still do carry 5081 cards in my pocket. Jim At 01:31 PM 6/9/2006, you wrote: In the Dark Ages (stone knives and bear skins), CTCs were problematic for SA programs because the interrupts are generated by the system on the *other* end. The various SA programs that still depend on an I/O interrupt in addition to, or instead of, LOADPARM were changed in the Middle Ages (represented by the invention of Sense ID) to examine more closely the cyberDNS of interrupting device. 3088s exacerbated the problem because it was so easy to fully interconnect the attached systems. Or someone decided that *now* would be good time to ENABLE one of the adapters. :-) For a 3088/CTC, the channel reset only affects *this* system's I/O status. The other side can still restart the link and annoy your SA program. If you find an SA program that gets confused by random interrupts and cannot be overridden by LOADPARM, you should probably call it in. With the XA I/O architecture there are all kinds of interrupts that can come in that have nothing to do with a tape was mounted or somebody flipped the test/normal switch on the 3278 or Attention was pressed on the 3215. Alan Altmark z/VM Development IBM Endicott Jim Bohnsack Cornell Univ. (607) 255-1760 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. Jim Bohnsack Cornell Univ. (607) 255-1760
Re: DDR to standard labeled tapes
I lost my last 5081 years ago, at the same time my -0 of the 360 reference card, yellow instead if green, disappeared from my desk drawer. We weren't issued desk keys because everyone is a professional and can be trusted. That -0 was considered a relic as we were on VM R3, going to R4, at the time. It was just before SP, and Jim Brergsten's famous vulture T-shirt (VM SP is waiting for you) Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Friday, June 09, 2006 12:12 PM To: IBMVM@LISTSERV.UARK.EDU Subject:Re: DDR to standard labeled tapes John, carry 5081 cards in my pocket Wow! 5,081 cards in your pocket!? Must be really small cards or really big pockets! Talk about playing with a full deck! :-) Ah, it's Friday, isn't it? Mike Walter Jim Bohnsack [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/09/2006 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: DDR to standard labeled tapes Watch that dark ages stuff, Chuckie. By the time I saw that problem, I was no longer keying on an 029 or maybe 026. I had graduated to a 3278 or 3279, altho I did then and still do carry 5081 cards in my pocket. Jim At 01:31 PM 6/9/2006, you wrote: In the Dark Ages (stone knives and bear skins), CTCs were problematic for SA programs because the interrupts are generated by the system on the *other* end. The various SA programs that still depend on an I/O interrupt in addition to, or instead of, LOADPARM were changed in the Middle Ages (represented by the invention of Sense ID) to examine more closely the cyberDNS of interrupting device. 3088s exacerbated the problem because it was so easy to fully interconnect the attached systems. Or someone decided that *now* would be good time to ENABLE one of the adapters. :-) For a 3088/CTC, the channel reset only affects *this* system's I/O status. The other side can still restart the link and annoy your SA program. If you find an SA program that gets confused by random interrupts and cannot be overridden by LOADPARM, you should probably call it in. With the XA I/O architecture there are all kinds of interrupts that can come in that have nothing to do with a tape was mounted or somebody flipped the test/normal switch on the 3278 or Attention was pressed on the 3215. Alan Altmark z/VM Development IBM Endicott Jim Bohnsack Cornell Univ. (607) 255-1760 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: DDR to standard labeled tapes
Thanks for the journey down memory lane... I thought my first keypunch was an IBM Model 26 keypunch (the rounded battleship gray ones), but that actually came later. My first exposure to a keypunch was during a Data Processing 101 course in college, c. 1969. Apparently I started on a model 29, then a model 129, then (good old real-life business, maybe in the Marines - can't remember for sure) used a model 26 for a bit. It all came rushing back after visiting: http://www.columbia.edu/acis/history/026.html and http://www.columbia.edu/acis/history/029.html My first computer use was writing FORTRAN on an IBM 360 Model 20 (I think), and I drooled at thought of all that power in an IBM 360 Model 45. :-) Mike Jim Bohnsack [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/09/2006 02:54 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: DDR to standard labeled tapes You must be a kid if you don't know what 5081 cards are or am I the only one on the list who does? Jim At 03:11 PM 6/9/2006, you wrote: John, carry 5081 cards in my pocket Wow! 5,081 cards in your pocket!? Must be really small cards or really big pockets! Talk about playing with a full deck! :-) Ah, it's Friday, isn't it? Mike Walter Jim Bohnsack [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/09/2006 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: DDR to standard labeled tapes Watch that dark ages stuff, Chuckie. By the time I saw that problem, I was no longer keying on an 029 or maybe 026. I had graduated to a 3278 or 3279, altho I did then and still do carry 5081 cards in my pocket. Jim At 01:31 PM 6/9/2006, you wrote: In the Dark Ages (stone knives and bear skins), CTCs were problematic for SA programs because the interrupts are generated by the system on the *other* end. The various SA programs that still depend on an I/O interrupt in addition to, or instead of, LOADPARM were changed in the Middle Ages (represented by the invention of Sense ID) to examine more closely the cyberDNS of interrupting device. 3088s exacerbated the problem because it was so easy to fully interconnect the attached systems. Or someone decided that *now* would be good time to ENABLE one of the adapters. :-) For a 3088/CTC, the channel reset only affects *this* system's I/O status. The other side can still restart the link and annoy your SA program. If you find an SA program that gets confused by random interrupts and cannot be overridden by LOADPARM, you should probably call it in. With the XA I/O architecture there are all kinds of interrupts that can come in that have nothing to do with a tape was mounted or somebody flipped the test/normal switch on the 3278 or Attention was pressed on the 3215. Alan Altmark z/VM Development IBM Endicott Jim Bohnsack Cornell Univ. (607) 255-1760 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. Jim Bohnsack Cornell Univ. (607) 255-1760 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: DDR to standard labeled tapes
On: Fri, Jun 09, 2006 at 03:54:45PM -0400,Jim Bohnsack Wrote: } You must be a kid if you don't know what 5081 cards are or am I the only } one on the list who does? I remember them. I tossed a full box of them in my last cross country move in 1997. -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67 Canines:Val, Red Shasta (RIP),Red, Zero Casey, Siberians Owner:Chinook-L Atlanta Siberian Husky Rescue. www.panix.com/~richgr/ Asst Owner:Sibernet-L
Re: DDR to standard labeled tapes
I call this Psuedo-standard labels because of the lack of HDR1, EOF1, EOV labels. This has worked well enough for at least 12 years of successful Disaster Recovery exercises. The only problem I have hit is remembering t o IPL the tape drive twice to get to my standalone DDR program that leads m y sysres backup. With 3590 tapes and being able to stack multiple backups on a single tape it would be nice if DDR understood REAL standard labels. /Tom Kern On Wed, 7 Jun 2006 16:28:35 -0400, George Haddad [EMAIL PROTECTED] wrote: I would like to DDR DUMP to standard label (3480-XF) tapes. For reasons I won't go into here, I plan to manually define the extents to be dumped to each tape, so DDR's multi-volume tape handling is not an issue. So is there any more to it than writing a VOL1 hdr, starting at the load point, then doing the DDR dump with a SKIP 1 on OUTPUT? For example, in a CMS environment, would this be correct ? 1) Write a VOL1 label to the tape TAPE WVOL1 volser userid (XF TAPE WTM 2 2) Boot a Standalone DDR 3) Mount the tape labeled in Step 1 4) DDR dump: INPUT 3390 volser OUTPUT 3480 (SKIP 1 MODE XF SYSPRINT CONS DUMP start-cyl TO end-cyl Is the WTM needed after the WVOL1 to mark the end-of-tape? Does writing a VOL1 header w/o HDR1 cause any problems? Is it really this straightforward? Any gotchas I should be aware of (other than multi-tape DDR dumps, which as I said, won't be an issue in my case)? =
Re: DDR to standard labeled tapes
I tell the DR vendor assistant to IPL device that I have my initial sysres backup tape loaded on. I run ONE standalone DDR to restore MY sysr es and then IPL my sysres to restore the rest of the system. Our MVS people use the vendor's floor system to load a PDS of job control information and th en modify and submit jobs to do their restores. My initial standalone DDR ta kes less time than their load and setup of their first job. I considered load ing my programs into the vendor's floor VM system, but thought that modifying the directory to include my DR service virtual machines would probably ta ke just as long as the DDR of my sysres that already has the servers defined , the minidisk with all the programs and the tape catalog of all the backup s I need to restore. /Tom Kern On Thu, 8 Jun 2006 12:27:49 -0500, Steve Gentry [EMAIL PROTECTED] wrote: How do you IPL the tape? Bare metal or 2nd level? Steve G. Thomas Kern [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/08/2006 10:52 AM I call this Psuedo-standard labels because of the lack of HDR1, EOF1, EO V labels. This has worked well enough for at least 12 years of successful Disaster Recovery exercises. The only problem I have hit is remembering to IPL the tape drive twice to get to my standalone DDR program that leads my sysres backup.
Re: DDR to standard labeled tapes
It doesn't really matter, other than how the ipl failure message is displayed. On bare metal, at least on our 9672 vintage machine (7060-H55), ipling on bare metal will make the HMC screen turn red. On 2nd level, you see the IPL unit failure message on the screen. Our D/R dumps are done on MVS using ADRDSSU, so I end up ipling 5 times to get to the S/A ICKDSF and then another 7 times to get to the S/A ADRDSSU program. The ipl failures are the VOL label, the HDR labels, I guess the EOF label. Jim At 01:27 PM 6/8/2006, you wrote: This is a multipart message in MIME format. --=_alternative 005FEE6405257187_= Content-Type: text/plain; charset=us-ascii How do you IPL the tape? Bare metal or 2nd level? Steve G. Thomas Kern [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/08/2006 10:52 AM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: DDR to standard labeled tapes I call this Psuedo-standard labels because of the lack of HDR1, EOF1, EOV labels. This has worked well enough for at least 12 years of successful Disaster Recovery exercises. The only problem I have hit is remembering t o IPL the tape drive twice to get to my standalone DDR program that leads m y sysres backup. With 3590 tapes and being able to stack multiple backups on a single tape it would be nice if DDR understood REAL standard labels. /Tom Kern On Wed, 7 Jun 2006 16:28:35 -0400, George Haddad [EMAIL PROTECTED] wrote: I would like to DDR DUMP to standard label (3480-XF) tapes. For reasons I won't go into here, I plan to manually define the extents to be dumped to each tape, so DDR's multi-volume tape handling is not an issue. So is there any more to it than writing a VOL1 hdr, starting at the load point, then doing the DDR dump with a SKIP 1 on OUTPUT? For example, in a CMS environment, would this be correct ? 1) Write a VOL1 label to the tape TAPE WVOL1 volser userid (XF TAPE WTM 2 2) Boot a Standalone DDR 3) Mount the tape labeled in Step 1 4) DDR dump: INPUT 3390 volser OUTPUT 3480 (SKIP 1 MODE XF SYSPRINT CONS DUMP start-cyl TO end-cyl Is the WTM needed after the WVOL1 to mark the end-of-tape? Does writing a VOL1 header w/o HDR1 cause any problems? Is it really this straightforward? Any gotchas I should be aware of (other than multi-tape DDR dumps, which as I said, won't be an issue in my case)? = --=_alternative 005FEE6405257187_= Content-Type: text/html; charset=us-ascii brfont size=2 face=sans-serifHow do you IPL the tape? nbsp;Bare metal or 2nd level?/font brfont size=2 face=sans-serifSteve G./font br br br table width=100% tr valign=top td tdfont size=1 face=sans-serifbThomas Kern lt;[EMAIL PROTECTED]gt;/b/font brfont size=1 face=sans-serifSent by: The IBM z/VM Operating System lt;IBMVM@LISTSERV.UARK.EDUgt;/font pfont size=1 face=sans-serif06/08/2006 10:52 AM/font brfont size=1 face=sans-serifPlease respond to The IBM z/VM Operating System/font br tdfont size=1 face=Arialnbsp; nbsp; nbsp; nbsp; /font brfont size=1 face=sans-serifnbsp; nbsp; nbsp; nbsp; To: nbsp; nbsp; nbsp; nbsp;IBMVM@LISTSERV.UARK.EDU/font brfont size=1 face=sans-serifnbsp; nbsp; nbsp; nbsp; cc: nbsp; nbsp; nbsp; nbsp;/font brfont size=1 face=sans-serifnbsp; nbsp; nbsp; nbsp; Subject: nbsp; nbsp; nbsp; nbsp;Re: DDR to standard labeled tapes/font/table br br brfont size=2 face=Courier NewI call this Psuedo-standard labels because of the lack of HDR1, EOF1, EOVbr br labels. This has worked well enough for at least 12 years of successfulbr Disaster Recovery exercises. The only problem I have hit is remembering tbr obr IPL the tape drive twice to get to my standalone DDR program that leads mbr ybr sysres backup. br br With 3590 tapes and being able to stack multiple backups on a single tapebr itbr would be nice if DDR understood REAL standard labels.br br /Tom Kernbr br On Wed, 7 Jun 2006 16:28:35 -0400, George Haddad lt;[EMAIL PROTECTED]gt; wrote:br br gt;I would like to DDR DUMP to standard label (3480-XF) tapes.br gt;For reasons I won't go into here, I plan to quot;manuallyquot; define thebr gt;extents to be dumped to each tape, so DDR's multi-volume tape handlingbr gt;is not an issue.br gt;So is there any more to it than writing a VOL1 hdr, starting at the loadbr br gt;point, nbsp;then doing the DDR dump with a SKIP 1 on OUTPUT?br gt;br gt;For example, in a CMS environment, would this be correct ?br gt;br gt;1) Write a VOL1 label to the tapebr gt; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;TAPE WVOL1 volser userid (XFbr gt; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;TAPE WTM 2br gt;br gt;2) nbsp;Boot a Standalone DDRbr gt;br gt;3) Mount the tape labeled in Step 1br gt;br gt;4) nbsp;DDR dump:br gt; nbsp; nbsp; nbsp; nbsp; INPUT 3390 volserbr
Re: DDR to standard labeled tapes
And of course if you're running 2nd level you can use CMS to forward spac e the tape to the appropriate location before you IPL it. It's faster and you won't see any IPL failure messages. Too bad CP only provides command to REWIND the tape to the load point and none to forward/backward space a tape. Brian Nielsen On Thu, 8 Jun 2006 13:12:45 -0400, Jim Bohnsack [EMAIL PROTECTED] wrot e: It doesn't really matter, other than how the ipl failure message is displayed. On bare metal, at least on our 9672 vintage machine (7060- H55), ipling on bare metal will make the HMC screen turn red. On 2nd level, y ou see the IPL unit failure message on the screen. Our D/R dumps are done on MVS using ADRDSSU, so I end up ipling 5 times to get to the S/A ICKDSF a nd then another 7 times to get to the S/A ADRDSSU program. The ipl failure s are the VOL label, the HDR labels, I guess the EOF label. Jim
Re: DDR to standard labeled tapes
So IPLing the tape 5 times (or 7 times) is a cumbersome way of doing a FSF. What happens when you IPL a HDR1, you get some kind of error right? The tape at that point has positioned itself at the next file and you do the process over again. We've been trying to decide if we want to use STD Labels on our SYSRES back up tape. IPL'ing a tape 2nd level is really not an issue because you have an FSF command available. But when IPL'ing from the HMC a.k.a. bare metal then you don't have an FSF command. To deal with that situation, you just IPL the tape x-number of times until you get to the file you need, right? Steve G. Jim Bohnsack [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/08/2006 12:12 PM Please respond to The IBM z/VM Operating System To:IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: DDR to standard labeled tapes It doesn't really matter, other than how the ipl failure message is displayed. On bare metal, at least on our 9672 vintage machine (7060-H55), ipling on bare metal will make the HMC screen turn red. On 2nd level, you see the IPL unit failure message on the screen. Our D/R dumps are done on MVS using ADRDSSU, so I end up ipling 5 times to get to the S/A ICKDSF and then another 7 times to get to the S/A ADRDSSU program. The ipl failures are the VOL label, the HDR labels, I guess the EOF label. Jim At 01:27 PM 6/8/2006, you wrote: This is a multipart message in MIME format. --=_alternative 005FEE6405257187_= Content-Type: text/plain; charset=us-ascii How do you IPL the tape? Bare metal or 2nd level? Steve G. Thomas Kern [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/08/2006 10:52 AM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: DDR to standard labeled tapes I call this Psuedo-standard labels because of the lack of HDR1, EOF1, EOV labels. This has worked well enough for at least 12 years of successful Disaster Recovery exercises. The only problem I have hit is remembering t o IPL the tape drive twice to get to my standalone DDR program that leads m y sysres backup. With 3590 tapes and being able to stack multiple backups on a single tape it would be nice if DDR understood REAL standard labels. /Tom Kern On Wed, 7 Jun 2006 16:28:35 -0400, George Haddad [EMAIL PROTECTED] wrote: I would like to DDR DUMP to standard label (3480-XF) tapes. For reasons I won't go into here, I plan to manually define the extents to be dumped to each tape, so DDR's multi-volume tape handling is not an issue. So is there any more to it than writing a VOL1 hdr, starting at the load point, then doing the DDR dump with a SKIP 1 on OUTPUT? For example, in a CMS environment, would this be correct ? 1) Write a VOL1 label to the tape TAPE WVOL1 volser userid (XF TAPE WTM 2 2) Boot a Standalone DDR 3) Mount the tape labeled in Step 1 4) DDR dump: INPUT 3390 volser OUTPUT 3480 (SKIP 1 MODE XF SYSPRINT CONS DUMP start-cyl TO end-cyl Is the WTM needed after the WVOL1 to mark the end-of-tape? Does writing a VOL1 header w/o HDR1 cause any problems? Is it really this straightforward? Any gotchas I should be aware of (other than multi-tape DDR dumps, which as I said, won't be an issue in my case)? = --=_alternative 005FEE6405257187_= Content-Type: text/html; charset=us-ascii brfont size=2 face=sans-serifHow do you IPL the tape? nbsp;Bare metal or 2nd level?/font brfont size=2 face=sans-serifSteve G./font br br br table width=100% tr valign=top td tdfont size=1 face=sans-serifbThomas Kern lt;[EMAIL PROTECTED]gt;/b/font brfont size=1 face=sans-serifSent by: The IBM z/VM Operating System lt;IBMVM@LISTSERV.UARK.EDUgt;/font pfont size=1 face=sans-serif06/08/2006 10:52 AM/font brfont size=1 face=sans-serifPlease respond to The IBM z/VM Operating System/font br tdfont size=1 face=Arialnbsp; nbsp; nbsp; nbsp; /font brfont size=1 face=sans-serifnbsp; nbsp; nbsp; nbsp; To: nbsp; nbsp; nbsp; nbsp;IBMVM@LISTSERV.UARK.EDU/font brfont size=1 face=sans-serifnbsp; nbsp; nbsp; nbsp; cc: nbsp; nbsp; nbsp; nbsp;/font brfont size=1 face=sans-serifnbsp; nbsp; nbsp; nbsp; Subject: nbsp; nbsp; nbsp; nbsp;Re: DDR to standard labeled tapes/font/table br br brfont size=2 face=Courier NewI call this Psuedo-standard labels because of the lack of HDR1, EOF1, EOVbr br labels. This has worked well enough for at least 12 years of successfulbr Disaster Recovery exercises. The only problem I have hit is remembering tbr obr IPL the tape drive twice to get to my standalone DDR program that leads mbr ybr sysres backup. br br With 3590 tapes and being able to stack multiple backups on a single tapebr itbr would be nice if DDR understood REAL standard labels.br br /Tom Kernbr br On Wed, 7 Jun 2006 16:28:35
Re: DDR to standard labeled tapes
How about TAPE FSF ( VDEV is 181 as a default) -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Thursday, June 08, 2006 4:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes And of course if you're running 2nd level you can use CMS to forward space the tape to the appropriate location before you IPL it. It's faster and you won't see any IPL failure messages. Too bad CP only provides command to REWIND the tape to the load point and none to forward/backward space a tape. Brian Nielsen On Thu, 8 Jun 2006 13:12:45 -0400, Jim Bohnsack [EMAIL PROTECTED] wrote: It doesn't really matter, other than how the ipl failure message is displayed. On bare metal, at least on our 9672 vintage machine (7060- H55), ipling on bare metal will make the HMC screen turn red. On 2nd level, you see the IPL unit failure message on the screen. Our D/R dumps are done on MVS using ADRDSSU, so I end up ipling 5 times to get to the S/A ICKDSF and then another 7 times to get to the S/A ADRDSSU program. The ipl failures are the VOL label, the HDR labels, I guess the EOF label. Jim
Re: DDR to standard labeled tapes
How about TAPE FSF ( VDEV is 181 as a default) TAPE is a CMS command, not a CP command.
Re: DDR to standard labeled tapes
But from second level cms: Tape FSF N CP term con 3270 Cp IPL CL LOADPARM CUU -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, June 08, 2006 5:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes How about TAPE FSF ( VDEV is 181 as a default) TAPE is a CMS command, not a CP command.
Re: DDR to standard labeled tapes
That was my point, 2nd level you have to use CMS to do the tape poisitoning, there is not a CP command. If you're logged onto a userid that doesn't normally have access to CMS (ex. a z/OS guest) there is extr a work to do to get CMS running (such as linking the MAINT 190 disk) just t o position the tape. If the z/OS guest already uses address 190 it's even more extra work. (Not to mention the error messages when you IPL CMS if you don't also have a 191 or 19E disk.) CP provides only a REWIND command. How hard would a FSF/BSF type command be? Brian Nielsen On Thu, 8 Jun 2006 17:38:07 -0400, carlos martinez [EMAIL PROTECTED] wrote: But from second level cms: Tape FSF N CP term con 3270 Cp IPL CL LOADPARM CUU -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, June 08, 2006 5:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes How about TAPE FSF ( VDEV is 181 as a default) TAPE is a CMS command, not a CP command.
Re: DDR to standard labeled tapes
You do not have to use CMS. IPL commands will work just like loading from the HMC. IPL 181 Read VOL1 label; Get a message IPL 181 Read HDR1; Get a message IPL 181 Read HDR2 and get a message IPL 181 Cross the tape mark and get a message IPL 181 And you are there If your tape just has a VOL1 without the HDR records, you shorten the process by 2 IPL commands. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Thursday, June 08, 2006 3:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject:Re: DDR to standard labeled tapes That was my point, 2nd level you have to use CMS to do the tape poisitoning, there is not a CP command. If you're logged onto a userid = that doesn't normally have access to CMS (ex. a z/OS guest) there is extr= a work to do to get CMS running (such as linking the MAINT 190 disk) just t= o position the tape. If the z/OS guest already uses address 190 it's even = more extra work. (Not to mention the error messages when you IPL CMS if = you don't also have a 191 or 19E disk.) CP provides only a REWIND command. How hard would a FSF/BSF type command= be? Brian Nielsen On Thu, 8 Jun 2006 17:38:07 -0400, carlos martinez [EMAIL PROTECTED] = wrote: But from second level cms: Tape FSF N CP term con 3270 Cp IPL CL LOADPARM CUU -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, June 08, 2006 5:34 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DDR to standard labeled tapes How about TAPE FSF ( VDEV is 181 as a default) TAPE is a CMS command, not a CP command.
Re: DDR to standard labeled tapes
Ipling a HDR1 gives you an IPL Unit Error. That's most of what I see. There is one other ipl error message that you see once in a while, but any error comes back right away. If you really do hit something you want, there is no error message and then you start giving the program some attn interrupts from the 3270 keyboard. In my case, ICKDSF takes a long time to load. ADRDSSU, at least enough of it to handle an attn interrupt, loads very quickly. The only FSF I know, and I have looked but not very hard for a CP FSF command, is CMS's TAPE FSF. Unless you know exactly how many files you want to pass, I think you're better off just ipling until you stop getting errors. Otherwise, it seems to me to be more of a hassle to I CMS in order to be able to enter TAPE FSF. Another gotcha that I discovered about 20 years ago on a system that had a 3088 connected to it, is that some other types of equipment, in this case, 3088's can confuse a SA program into thinking that it is getting 3270 attn interrupts. I was not, very dependable, able to ipl a SA tape unless I would first disable the channel adapter on the 3088. I don't know what other kind of equipment can generate fake 3270 interrupts. Maybe nothing, but it can be frustrating if you are pretty sure that you're ipled a real program from the tape, but the program thinks that the interrupt it got is from the address it wants to talk to and it's something out on the machine room floor. Jim At 05:42 PM 6/8/2006, you wrote: This is a multipart message in MIME format. --=_alternative 007745EA05257187_= Content-Type: text/plain; charset=us-ascii So IPLing the tape 5 times (or 7 times) is a cumbersome way of doing a FSF. What happens when you IPL a HDR1, you get some kind of error right? The tape at that point has positioned itself at the next file and you do the process over again. We've been trying to decide if we want to use STD Labels on our SYSRES back up tape. IPL'ing a tape 2nd level is really not an issue because you have an FSF command available. But when IPL'ing from the HMC a.k.a. bare metal then you don't have an FSF command. To deal with that situation, you just IPL the tape x-number of times until you get to the file you need, right? Steve G. Jim Bohnsack Cornell Univ. (607) 255-1760
