zOS V2.2, V2.3 and V2.4, all running on LPARs of a z15. It seems to be a machine issue, not a zOS issue.
This is NOT, repeat NOT, code in any Syncsort, now Precisely, product. Chris Blaicher Technical Architect Syncsort, Inc. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Beaver Sent: Wednesday, August 19, 2020 3:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Strange S0C4 on z15 [ External - This message originated Externally. Use proper judgement and caution with attachments, links, or responses. ] What was your zOS version and what is it now? Sent from my iPhone I promise you I can’t type or Spell on any smartphone > On Aug 19, 2020, at 14:21, Christopher Y. Blaicher <cblaic...@precisely.com> > wrote: > > We have a program that ran fine on a z13 that now gets an S0C4 on a z15. > On a z13 we could access data in the PSA in the 2048 to 4095 range without > going into key 0. The specific field is PSASVT. > To get to that data now, we have to do a MODESET to key zero. > Anyone else find this as a problem? Was it there with a z14? We jumped from > a z13 to a z15. > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
