On Sun, 6 Jan 2019 at 15:29, Seymour J Metz <[email protected]> wrote: > Second, MODIFY is not the only type of CIB, If the COMM ECB is posted then > you need to process and delete the CIB, regardless of > type, and regardless of whether you recognize the text of a MODIFY. The types > I would expect to see are START, MODIFY and STOP. I > would do a WTO for any CIB my code didn't recognize, but you still need to > delete it.
I agree with you, of course, but I'm not sure that that's fundamental to the reported problem.The symptom for failing to delete the CIB would be that the next MODIFY (or STOP or anything else) command would get an IEE342I MODIFY REJECTED-TASK BUSY. (To say nothing of a hard loop.) Joe hasn't told us how his MODIFYs are mostly "not working", nor if all of them that he has issued are "valid" in that his code understands them. I am more suspicious of mixing async (are they really all async?) EZASMI calls with WAITs in the same maintask flow of control. Is there any reason for a Givesocket to be async? (For that matter is there any reason for Takesocket or indeed any of the worker task's socket calls to be async?) In the enlarged but still incomplete code snippet posted, the WAIT after the SELECTX is commented out. SELECTX isn't going to WAIT on the Comm ECB, so who does? Joe, if you want serious help with this, please post something that can actually be assembled and run. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
