Re: Info-zip on Z/OS 1.6 and up
The problem was due to the fact that there were several shadow volumes for the base volume and when I made the copy of the volume to xmit to the real system, I had accidentally left one of them off, so I ended up with some directory pointers in hte load library that were not pointing to the correct places. Very stupid mistake to have made on my part, I should have known better. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Brian Westerman wrote: ... In this case, it turned out to be that we were trying to take a DASD volume that was built under a Hercules (MVS 3.8) system and after conversion and transmitting, load and use it on a Z/OS system. Normally that is not a problem, but (apparently) when you use Shadow volumes, you can't built the image the same way, (you end up with the problem that we ran into). I wish you had just said that sooner! (Obviously, I know next to nothing about Hercules.) It might be worth consulting Jay Maynard about the issue you encountered. Emulation is *supposed* to be transparent! If there's an incompatibility, he'll probably want to know ... -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
I don't know anything about shadow volumes, but I bet that they need an indexed vtoc. The MVS 3.8 vtoc wouldn't support an indexed vtoc. Maybe that was the problem. Eric Bielefeld Sr. z/OS Systems Programmer Milwaukee Wisconsin 414-475-7434 - Original Message - From: Edward Jaffe [EMAIL PROTECTED] Brian Westerman wrote: ... In this case, it turned out to be that we were trying to take a DASD volume that was built under a Hercules (MVS 3.8) system and after conversion and transmitting, load and use it on a Z/OS system. Normally that is not a problem, but (apparently) when you use Shadow volumes, you can't built the image the same way, (you end up with the problem that we ran into). I wish you had just said that sooner! (Obviously, I know next to nothing about Hercules.) It might be worth consulting Jay Maynard about the issue you encountered. Emulation is *supposed* to be transparent! If there's an incompatibility, he'll probably want to know ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Eric N. Bielefeld wrote: I don't know anything about shadow volumes, but I bet that they need an indexed vtoc. The MVS 3.8 vtoc wouldn't support an indexed vtoc. Maybe that was the problem. That's a bet you would lose. Any volume produced or usable under MVS 3.8 is fully functional under later systems, although adding an index data set may improve performance. Going the other way is a little more problematic, as MVS 3.8 won't handle some data sets (e.g., PDSE, ICF catalogs, VSAM), and may need to have the indexed VTOC converted back to get format 5 DSCBs. Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Thanks, That was the original question. Most of our clients use PKZIP so (originally) it was a question of whether or not it was a problem with the INFO-ZIP software or the installation or the method of transfer. In this case, it turned out to be that we were trying to take a DASD volume that was built under a Hercules (MVS 3.8) system and after conversion and transmitting, load and use it on a Z/OS system. Normally that is not a problem, but (apparently) when you use Shadow volumes, you can't built the image the same way, (you end up with the problem that we ran into). (in retrospect) It would have probably saved a lot of time and effort to get new copies of INFO-ZIP, but there were a number of other datasets on that particular volume and the original XMIT format copy of INFO-ZIP that were also needed on the other end, so we thought things were safe. I have performed that type of transfer many times before, but never with volumes that were quite so heavily shadowed (there were 11 separate shadow files) In this case, saving time ended up costing more time. :( Some day, I hope there will be FTP for the Hercules based MVS system and this type of issue won't even be a bad memory any more. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
It is a feature of the emulated DASD support in Hercules. Chuck Arney illustro Systems International, LLC http://www.illustro.com Access 3270 data from anywhere with z/XML-Host Access 3270 apps from the web with z/Web-Host Access CMS minidisks from OS/390 or VSE with CMSACCess Voice: 972-296-6166 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Edward Jaffe Sent: Wednesday, July 19, 2006 12:47 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Info-zip on Z/OS 1.6 and up I have access to a Flex-ES system here. But, I'm not familiar with the base and shadow DASD concepts you mentioned. Is there any chance this is a Hercules feature? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Brian Westerman wrote: The emulated DASD has a BASE dasd image, and can have one or more SHADOW images of the same volumes. All changes made to the dasd occur in the shadow image, thus leaving the base dasd unchanged. You can select to merge the shadow image into the base, (thus making a new base) or deleting the shadow image, thus throwing away all of the changes to that volume at any time. It's a cool way to handle things, and it's not that much different than on a regular mainframe when you work with an Iceberg or some other similar device where you can accomplish the same type of operations. It makes backing up the dasd very quick as well since you only have to backup the shadow images (assuming you have copies of the base already), which is sort of like instant incremental backups. Are you talking about something specific to Flex/ES? In an earlier post, you mentioned the ADCD pre-packaged system from IBM. How is that relevant? Does IBM provide some specialized software support for Flex/ES, available with ADCD, that isn't available on ordinary systems? Can you kindly provide a URL to any documentation or other information that would help me understand what it is you're talking about? -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Brian Westerman wrote: The support is only available on the PC(s) that run Z/OS, not a real mainframe, this issue will not affect real mainframes (i.e. Z9), but there are a lot of us that have Flex-based systems that could run into this problem, that's why I posted the answer. I have access to a Flex-ES system here. But, I'm not familiar with the base and shadow DASD concepts you mentioned. Is there any chance this is a Hercules feature? It does however fianlly test that INFO-ZIP will run on Z/OS 1.6, and 1.7 which was not verified until now. I've been using Info-ZIP on z/OS 1.7 since late last year. Guess I should have mentioned that before now. Sorry. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
On Mon, 17 Jul 2006 00:42:55 -0500 Brian Westerman [EMAIL PROTECTED] wrote: :I got the source for Info-Zip and compiled it (which didn't fix anything) :but it did allow me to debug things and I found that the allocate was not :getting the only allowed zero return code. Further checking allowed me :to discover that there appears to be a problem with C routines under LE :when allocating a dataset if the module(s) in question are loaded from the :shadow copy of a linklist dataset and not the base copy. Changing ZIP to :be in the base allowed normal operation. I went back and tested with the :original module and it also works in that base configuration. :I don't see that this will be a problem for people using real dasd, just :the ADCD users (like me). :I tested zip on our 2066 under z/os V1.7 (with real dasd on a shark and :it functioned fine. I rebuilt the ADCD and included the module in the :base and it workd fine for both Z/os 1.6 and 1.7. When I rebuilt again :and left it off the base so that it would be loaded from the shadow copy :and again it fails. I am not sure what you mean by base and shadow, but if a linklist dataset is updated a F LLA,REFRESH command is required to pull in the new module. VLF commands may also be required. -- Binyamin Dissen [EMAIL PROTECTED] http://www.dissensoftware.com Director, Dissen Software, Bar Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Hi, The emulated DASD has a BASE dasd image, and can have one or more SHADOW images of the same volumes. All changes made to the dasd occur in the shadow image, thus leaving the base dasd unchanged. You can select to merge the shadow image into the base, (thus making a new base) or deleting the shadow image, thus throwing away all of the changes to that volume at any time. It's a cool way to handle things, and it's not that much different than on a regular mainframe when you work with an Iceberg or some other similar device where you can accomplish the same type of operations. It makes backing up the dasd very quick as well since you only have to backup the shadow images (assuming you have copies of the base already), which is sort of like instant incremental backups. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Info-zip on Z/OS 1.6 and up
Hi all, I got the source for Info-Zip and compiled it (which didn't fix anything) but it did allow me to debug things and I found that the allocate was not getting the only allowed zero return code. Further checking allowed me to discover that there appears to be a problem with C routines under LE when allocating a dataset if the module(s) in question are loaded from the shadow copy of a linklist dataset and not the base copy. Changing ZIP to be in the base allowed normal operation. I went back and tested with the original module and it also works in that base configuration. I don't see that this will be a problem for people using real dasd, just the ADCD users (like me). I tested zip on our 2066 under z/os V1.7 (with real dasd on a shark and it functioned fine. I rebuilt the ADCD and included the module in the base and it workd fine for both Z/os 1.6 and 1.7. When I rebuilt again and left it off the base so that it would be loaded from the shadow copy and again it fails. Hopefully this will help someone in the future if they run into the same problem on their ADCD system. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
info?zip on z/os 1.6 and up
Hi, Has anyone been successful in getting infozip to run on z/os 1.6 or higher. I keep getting the following when I try it on anything above a 1.5 system: The TEST.TXT file is just a small 1 track FB 80x800 text file. Translating to ASCII... zip warning: name not matched: TEST.TXT zip error: Nothing to do! (DD:OUT) The JCL in use: //ZIP EXEC PGM=ZIP,PARM='DD:OUT TEST.TXT -a' //OUT DD DSN=amp;OUTFILE,DISP=(NEW,PASS), //SPACE=(15000,(5000,5000),RLSE),UNIT=SYSALLDA, //LRECL=80,RECFM=FB,DSORG=PS //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //CEEDUMP DD SYSOUT=* Any suggestions? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Info-zip on Z/OS 1.6 and up
Hi, Sorry if this is a duplicate, but I'm not certain I posted correctly earlier. I wanted to ask if anyone is running INFO-ZIP under z/os V1.6 or higher. I am able to run it on 1.5 and 1.4 (and os/390 2.10) with no problems, but at 1.6 using the same JCL I get name not matched on the input dataset, whereas this works fine on the 1.5 system. I thought it might be an issue with LE (zip is a C program), but I assembled CEEUOPT with ALL31(off) and STACK(,,BELOW) and linked it into ZIP just in case but it still gets the same error: The JCL I use is: //STEP010 EXEC PGM=ZIP, // PARM='-a ''TEST.MYZIP.ZIP'' ''TEST.INPUT.TEXT''' //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* The messages we get are : Translating to ASCII... zip warning: name not matched: TEST.INPUT.TEXT zip error: Nothing to do! (TEST.MYZIP.ZIP) We have tried everything, the files exist, and it works fine on my 1.5 system, just not the test 1.6 or 1.7 systems. Thanks for your help. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
