The POSTing code has a partner started task (that it is trying to POST). If the partner STC has gone away, then the problem is whatever made the STC go away, not the POST failing; the POST failing is just an inevitable symptom. If the STC is still there, we put the error code where the STC will find it (albeit eventually, not as the result of a POST) and log it where it logs things. I'm pretty happy with that design.
The POSTing code is running sometimes as an SRB and sometimes with locks held, so the options for logging things directly are limited. Not nonexistent, but limited. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Seymour J Metz Sent: Wednesday, October 10, 2018 11:18 AM To: [email protected] Subject: Re: Cross-memory POST ERRET and return codes You might want to create, e.g., a dump, a logrec record, a trace record. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
