Just off the top of my head from having a similar issue a few
years ago, you may need to be watching two ECBs (EVENTS). But I'm
not sure that the STIMERM won't cause a squawk when you have the
task end.
And I think you will have to pass the address of the ECB you will
POST for termination to the Attached task. Otherwise, you might
be able to do a CALLRTM to terminate the subtask. Now, the
subtask will need an error recovery routine to hide the fact that
you just term'ed it.
Here is what the macro contains relative to this:
THE STIMERM MACRO ALLOWS THE ISSUER TO SET, TEST OR CANCEL
UP TO 16 REAL TIME INTERVALS. AT THE TIME THE INTERVAL IS
ESTABLISHED, THE CALLER MAY OPTIONALLY SPECIFY AN EXIT ROUTINE
TO BE GIVEN CONTROL ASYNCHRONOUSLY AFTER THE TIME INTERVAL
EXPIRES OR THAT EXECUTION OF THE CURRENT TASK IS TO BE
SUSPENDED.
AN ERROR EXIT MAY ALSO BE SPECIFIED WHICH MAY BE GIVEN CONTROL
IF THE STIMERM FUNCTION CANNOT BE PERFORMED.
Steve Thompson
On 11/13/2023 7:37 PM, Paul Schuster wrote:
How to handle this situation: task ‘A’ attaches a subtask, task ‘B’.
The ‘B’ task issues a STIMERM WAIT=YES
Task ‘A’ terminates, but gets the A03 abend since task ‘B’ still active.
How can task ‘A’ communicate to the subtask ‘B’ that it (task ‘B’) needs to
terminate? Task ‘B’ is in the STIMERM wait, so it can’t do anything.
I didn’t see this scenario documented in the Assembler Services Guide or the
Assembler Services References.
Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Regards, Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
