Joe,
If you have a bad address when you do the storage release, you
could be releasing storage zOS needs...hence the 0c4.
Why don't you put a DC X'00' just prior to the storage release,
after you have set the values for the storage release.
Set a SLIP for and oc1, get a dump, and look at the values. Compare
what you are setting for release to what you obtained.
If you can't do something like that, post your exit code so another
pair of eyeballs can have a look.
Sometimes the guy writing the code just can't see the error, and
another pair of eyes spots it right off.
Regards,
-- Dave Day
On 6/18/2025 2:39 PM, Joseph Reichman wrote:
Jon
Don’t know if you work for a vendor I don’t blame them
At the end of IKJEFLD3 I release working storage sp=0 restore regs and do a BR
14 all this without a abend
The abend is displayed on the console afterwards
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of Jon
Perryman <[email protected]>
Sent: Wednesday, June 18, 2025 3:32:56 PM
To: [email protected] <[email protected]>
Subject: Re: error in post logon exit IKJEFD3 878-18 from MSTJCL
On Wed, 18 Jun 2025 13:40:45 -0400, Joseph Reichman <[email protected]>
wrote:
Then I would of gotten a s0c4 ( was running key 0 )
While ikjefld3 was executing
What makes you think a S0C4 is guaranteed in your IKJEFLD3 with a bad address?
Since we haven't seen your code, we don't know how you are using the address.
You saw an S878 instead of S0C4 from storage release. There are many ways a
S0C4 will be hidden or avoided. One such way is through PC routines (in this
case STORAGE RELEASE). Rarely will you see a S0Cx abend from a PC routine
unless you look at a dump.
You just panicked every vendor. Screw up as much as you want in key 8 but you
NEVER allow storage overlays in key 0. Vendorss get blamed for someone else's
screwup.
----------------------------------------------------------------------
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
