Re: Mainframe population

2006-07-22 Thread Howard Rifkind
NYC is a good bet for Wall Stree firms and banks using mainframes but the mainframes sure aren't in NYC. Most have move and consolidated in various sub of NYC, like NJ. Several have moved the physical operations overseas. Rent is just to high in NYC to house computer rooms any longer.

Re: Info-zip on Z/OS 1.6 and up

2006-07-22 Thread Edward Jaffe
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

Re: Program Call (PC) routine in AMODE(64)

2006-07-22 Thread Peter Relson
It is true that bit ETDEAM was defined in z/OS 1.5 but unfortunately it appears that the function doesn't actually work until z/OS 1.8. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive

Re: Program Call (PC) routine in AMODE(64)

2006-07-22 Thread Jeffrey D. Smith
=== -Original Message- From: Peter Relson [EMAIL PROTECTED] Sent: 7/22/2006 10:29 AM To: IBM-MAIN@BAMA.UA.EDU IBM-MAIN@BAMA.UA.EDU Subject: Re: Program Call (PC) routine in AMODE(64) It is true that bit ETDEAM was defined in z/OS 1.5 but

Re: Info-zip on Z/OS 1.6 and up

2006-07-22 Thread Eric N. Bielefeld
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

Re: Info-zip on Z/OS 1.6 and up

2006-07-22 Thread Gerhard Postpischil
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