Obvious question: was R13 ever set to a valid working storage address? Rupert
On 14 Jul 2017 21:09, "Richard Craven" <[email protected]> wrote: > This has me stumped (although that may not be too hard to do). > > I'm debugging an assembly program that has an EXEC CICS READ UPDATE... > Something is wrong with the READ request, and the HANDLE ABEND label is > taken. > > I GTF'd the call and ABEND label. As per documentation, R0-R14 look like > they are being returned intact from the call (the BASR), except R13 which > has been zeroed! This held the address of working storage (DFHEISTG) going > in to the READ. Now I don't have any base from which to read error fields, > etc. > I don't have a lot of CICS experience. Is there a known CICS condition > that causes R13 to be zeroed when a particular API error occurs? > > ---------------------------------------------------------------------- > 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
