Joe, I know that you are writing a lot of assembler code in your spare time without access to debugging software like zXDC , so I would advise the following as a good investment of your time as working out errors in code just from dumps can be difficult:
(O) write yourself an internal trace tool that can dump out regs and named storage areas during runtime (maybe activated by special ddname or parameter). Make this code generic so that you can use it in all your projects. (O) insert trace points before and after major logic points and any internal or external calls. (O) consider improving your naming standards so that reading the code is easier and obvious typos appear more frequently. A good example is using something like "struct_field_name" for fields inside your own struct (O) consider working storage as a struct and apply the same rules as above (O) have a naming standard for constants (and this includes model list forms of macros that you prime parameter lists from) Hope this helps Rob Scott Rocket Software Sent from Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Joseph Reichman <reichman...@gmail.com> Sent: Monday, September 11, 2023 4:09:35 pm To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: Mysterious S0C4 pic 10 EXTERNAL EMAIL No it’s not the ESTAE but the code that populates the parameter list to it it when I comment that out Later on the BASR to pars works Is there some thing like setting a slip trap that might help me Thanks Joe Reichman On Mon, Sep 11, 2023 at 11:05 AM Tony Harminc <t...@harminc.net> wrote: > On Mon, 11 Sept 2023 at 09:33, Joseph Reichman <reichman...@gmail.com> > wrote: > > > I have the following lines of code which basically sets up the parameter > > list to an ESTAE and calls it > > > Later on when I populate Parse Parameter list and call IKJPARS I get a > > s0c4 pic 10 right after the BALR > > There's no BALR in the code snippets you've shown. I'll assume you mean > BASR. > > > When I comment out the code below (that sets up the ESTAE parameter > list) > > everything with PARS works great > > I check and double checked there is no storage overlay, I am just looking > > for guidance how to debug this > > Two basic approaches: Top Down and Bottom Up. Start at the bottom - > what is the failing address causing your PIC 10? Does it look > plausible for the AMODE you're in at the time? Which instruction > actually failed? Is the failing address (or a near or left-truncated > version of it) in a register? > > Etc... > > If that hasn't made the problem obvious, then you may have collected > enough information to work from the top down. If it's true that the > ESTAE is provoking the failure, then what does it change, i.e. how > could anything it does affect the result of calling IKJPARS? > > Etc... > > Tony H. > > ---------------------------------------------------------------------- > 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 ================================ Rocket Software, Inc. and subsidiaries ¦ 77 Fourth Avenue, Waltham MA 02451 ¦ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
