Generally, that would give you an 0C1. In my case it was a simple LOAD instruction. L R1,X'B4C'(0,0)
Chris Blaicher Technical Architect Syncsort, Inc. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Wednesday, August 19, 2020 4:16 PM To: [email protected] Subject: Re: Strange S0C4 on z15 [ External - This message originated Externally. Use proper judgement and caution with attachments, links, or responses. ] So I had an S0C4 one time - turned out the vendor had used an instruction that was not on the CEC (firmware) we were running. So maybe there is an instruction used on the z13 that the 15 does not have? Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Christopher Y. Blaicher Sent: Wednesday, August 19, 2020 12:12 PM To: [email protected] Subject: Strange S0C4 on z15 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 [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
