I agree that it is not advisable without coding HPRSESLM=DISABLED.-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Thursday, March 08, 2018 4:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VTAM communication z/OS 2.2 and z/OS 1.4 Tony, Based upon the note in the 1.10 migration, it would seem to indicate that using z/OS 2.2 EE to communicate with a z/OS 1.4 system would be inadvisable? Or just inadvisable without the ATCSTRxx HPRSESLM=DISABLED? Rob Schramm On Thu, Mar 8, 2018 at 3:16 PM Cieri, Anthony <aci...@seic.com> wrote: > > I did some more digging and it appears that the HPRSESLM VTAM > start option that I referred to earlier was introduced in z/OS V1.10. > We are a service Bureau shop and I recall having some issues when we > upgraded from z/OS V1.9 to V1.11. Those scars are what lead to my > first reply!!! I also found an old discussion in the archives at: > > > https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/6QggnT04 > hlw > > This discussion points to other document and tech notes for > back ground information. To avoid this particular issue, code > HPRSESLM=DISABLED in the ATCSTRxx member for the z/OS V2.2 VTAM. > > > HTH > Tony > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Rob Schramm > Sent: Thursday, March 08, 2018 10:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: VTAM communication z/OS 2.2 and z/OS 1.4 > > Tim, > > z/os 1.4 runs on a z13s mono-cpu with no accommodation other than > having all available maintenance applied. Multi-cpu's is a wait-state. > > I am most concerned with Tony's comments about EE over the years. The > chance of these ending up on separate CECs is very low. But I always > like to position for the unlikely. I want to conserve my efforts.. to > establish communication between the LPARs and pick the method that is > most likely to work coupled with having the best flexibility. But # 1 > priority is that it works. > > Rob Schramm > > > > On Thu, Mar 8, 2018 at 2:23 AM Timothy Sipples <sipp...@sg.ibm.com> wrote: > > > z/OS 1.4 and z/OS 2.2 are far enough apart that there was never a > > single IBM machine model that officially supported both releases. > > IBM supported running z/OS 1.4 up to the z9 models, and z/OS 2.2 > > starts with the z10 models. If you've got them both running on one > > CEC, it's lucky, and congratulations. Please make sure you're not > > running z/OS > > 1.4 in Bimodal Accommodation (ESA/390 31-bit mode), by the way, for > > at least two big reasons. > > > > With that background, I don't think you can or should assume a > > single CEC "forever," or even for very long. At least, it'd be > > prudent not to "wire in" such rigidity. If you're still nervous, you > > can set up both EE and CTCA connections. I recommend configuring EE > > (over a HiperSocket if on the same > > CEC) as primary/favored since the performance characteristics are > > likely to be better, but you can backstop EE with CTCA if you wish. > > > > EE officially debuted with OS/390 Version 2 Release 7 in early 1999, > > was backported to OS/390 Version 2 Release 6, and was circulating in > > earlier form before that. EE certainly wasn't fresh off the boat > > with z/OS 1.4, which reached End of Service in 2007, over 8 years > > after EE debuted. z/OS > > 1.4 is plenty new enough for these purposes. I recall plenty of EE > > adoption in z/OS 1.4 and prior. > > > > > > -------------------------------------------------------------------- > > -- > > ---------------------------------- > > Timothy Sipples > > IT Architect Executive, Industry Solutions, IBM Z & LinuxONE, > > Multi-Geography > > E-Mail: sipp...@sg.ibm.com > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > > -- > > Rob Schramm > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Rob Schramm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
