> The fast POST example is unfortunately based on System 370 instructions.
Why is that a problem? Wouldn't something like PLO be overkill? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Charles Mills <[email protected]> Sent: Friday, June 22, 2018 5:16 PM To: [email protected] Subject: Re: Eternal WAIT on un-waited ECB Examples are actually in Authorized Assembler Services Guide. The fast POST example is unfortunately based on System 370 instructions. I would say "clear the ECB sometime before either the WAIT or the POST is possible." Keep in mind that in some situations the POST might happen before the WAIT. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Christopher Y. Blaicher Sent: Friday, June 22, 2018 1:07 PM To: [email protected] Subject: Re: Eternal WAIT on un-waited ECB At the start of everything, you should clear the ECB. Immediately after the WAIT you should clear it. OK, first pick up the value in the ECB in case it has significance and then clear it. You should also look at the FAST POST and FAST WAIT examples in Appendix A of the POP manual. They can save substantial CPU time if you do this often. Chris Blaicher Technical Architect Syncsort, Inc. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Smith Sent: Friday, June 22, 2018 3:15 PM To: [email protected] Subject: Eternal WAIT on un-waited ECB I have a bad situation where a program is hanging forever in a wait. The ECB shows x'30ABFC50'. The lower 3 bytes are the address of my PRB, and I read somewhere that x'30' means it was un-waited (something like undead, I guess). This happens after some turmoil, and it's probable, not yet certain, the ECB looked like that when I waited on it. This is actually a VSAM CHECK after an asynchronous POINT. Looking at the S122 dump, the RPLACTIV flag is on, RPLFDBK is all 0. My question is, would clearing the ECB before the asynch. request fix this? I believe I ought to anyway, but my question is if this could cause the hang? I have no way to re-create the situation. Unfortunately, my customers evidently do. -- sas ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
