0101: you did not show the rest of the expansion or the registers at the
time of the error, or what the contents of the parameter area was.
This is basic diagnosis upon reading the reason for an abend that
indicates that the problem is that reserved fields in a parameter area are
non-zero.
It was primary mode I did a SAC 0
Right before the VSMLOC
> On Aug 8, 2017, at 3:01 AM, Binyamin Dissen
> wrote:
>
> On Mon, 7 Aug 2017 21:30:08 -0400 Jim Mulder wrote:
>
> :>It should not be possible to get a 052 abend from VSMLOC,
>
rrect PC number to be loaded?
:>Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
:>Poughkeepsie NY
:>
:>> From: Binyamin Dissen <bdis...@dissensoftware.com>
:>> To: IBM-MAIN@LISTSERV.UA.EDU
:>> Date: 08/08/2017 04:16 AM
:>> Subject: Re: Variou
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 08/08/2017 04:16 AM
> Subject: Re: Various 052 abends with LINKAGE=SYSTEM calls in SRB
> Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
>
> On Mon, 7 Aug 2017 21:30:08 -0400 Jim Mulder <d10j...@us.ibm.com> wrot
On Mon, 7 Aug 2017 21:30:08 -0400 Jim Mulder wrote:
:>It should not be possible to get a 052 abend from VSMLOC,
:>unless some rogue code on your system has messed with the
:>System Function Table so that the wrong PC number is being issued,
:>or some rogue code on your
Thanks that's what I thought
> On Aug 7, 2017, at 9:30 PM, Jim Mulder wrote:
>
>It should not be possible to get a 052 abend from VSMLOC,
> unless some rogue code on your system has messed with the
> System Function Table so that the wrong PC number is being issued,
>
It should not be possible to get a 052 abend from VSMLOC,
unless some rogue code on your system has messed with the
System Function Table so that the wrong PC number is being issued,
or some rogue code on your system has messes with the Entry Table Entry
for the VSMLOC PC so that something