Hi

I quite don’t understand this but In my testing when I had WTO's the modify 
logic would work. I now decided to put a STIMER after the SELECT_LOOP

I.E. 

             STIMER   WAIT,DINTVL=LTINTVLL  WAIT A BIT     
LTINTVLL DC    CL8'00000001'


I just ran the code 6 times in a row and it worked with out the STIMER the code 
would work 1 out 5 times

thanks 
-----Original Message-----
From: Joseph Reichman <[email protected]> 
Sent: Monday, January 7, 2019 3:45 PM
To: 'IBM Mainframe Discussion List' <[email protected]>
Subject: RE: Concurrent Server Task Dispatch issue multitasking issue

The code bypassed the 1,000 limit size I had no choice but to  chop it up if 
you give me an e-mail I'll attach the program/code -----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Tony Harminc
Sent: Monday, January 7, 2019 3:33 PM
To: [email protected]
Subject: Re: Concurrent Server Task Dispatch issue multitasking issue

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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to