Re: STIMERM EXIT question

2005-08-28 Thread Jim Mulder
IBM Mainframe Discussion List  wrote on 08/26/2005 
03:14:23 PM:

> In a recent note, Paul Schuster said:
> 
> > Date: Fri, 26 Aug 2005 13:25:04 -0500
> > 
> > Thank you.  A natural follow-on question is this: what about STIMERM's 
that
> > have been created with an ATTACH from other than the initiator TCB? 
More
> > exactly, a sub-task of your current running task?

  STIMER cleanup is done at task termination for every task, not just
the jobstep task.
 
> If the parent task terminates without DETACHing the child task,
> doesn't the child ABEND asynchronously?

  Yes.

> Hmmm.  What if the child sets an ESTAE and attempts to recover?

  The ABEND due to a DETACH is not retryable.
 
Jim Mulder   z/OS System Test   IBM Corp.  Poughkeepsie,  NY

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: STIMERM EXIT question

2005-08-26 Thread Greg Dyck
> Thank you.  A natural follow-on question is this: what about STIMERM's
that
> have been created with an ATTACH from other than the initiator TCB? More
> exactly, a sub-task of your current running task?

Don't worry.  Be happy.  Timing services will properly clean up any
outstanding STIMER(M) requests on task termination.  All task related
requests are purged.
Greg

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: STIMERM EXIT question

2005-08-26 Thread Paul Gilmartin
In a recent note, Paul Schuster said:

> Date: Fri, 26 Aug 2005 13:25:04 -0500
> 
> Thank you.  A natural follow-on question is this: what about STIMERM's that
> have been created with an ATTACH from other than the initiator TCB? More
> exactly, a sub-task of your current running task?
> 
If the parent task terminates without DETACHing the child task,
doesn't the child ABEND asynchronously?

Hmmm.  What if the child sets an ESTAE and attempts to recover?

-- gil
-- 
StorageTek
INFORMATION made POWERFUL

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: STIMERM EXIT question

2005-08-26 Thread Paul Schuster
Thank you.  A natural follow-on question is this: what about STIMERM's that
have been created with an ATTACH from other than the initiator TCB? More
exactly, a sub-task of your current running task?

Thank you.

Paul

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: STIMERM EXIT question

2005-08-25 Thread Jim Mulder
IBM Mainframe Discussion List  wrote on 08/25/2005 
05:08:53 PM:

> On Thu, 25 Aug 2005 13:16:11 -0700 Charles Mills <[EMAIL PROTECTED]> 
wrote:
> 
> :>An STIMER exit runs on the TCB of the task that issued the STIMER, so
> :>when that task goes away, the possibility of the exit goes away. I
> :>suppose what you describe is technically kind of substandard 
programming
> :>practice (you created the exit request, you cancel the exit request) 
but
> :>MVS is smart enough not to dispatch a timer exit after the program 
goes
> :>away.
> 
> As the TQE only has the TCB address (not the TTOKEN), if the address 
gets
> reused it could be dispatched there.
> 
> I wonder if EOT processing runs the chain to remove them. I don't see 
anything
> obvious hung off of the TCB.
> 
> :>-Original Message-
> :>From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
> :>Behalf Of Paul Schuster
> :>Sent: Thursday, August 25, 2005 12:18 PM
> :>To: IBM-MAIN@BAMA.UA.EDU
> :>Subject: STIMERM EXIT question
> 
> :>Hello: If you have a STIMERM EXIT=,interval=,WAIT=NO, and the time
> :>interval expires after the task has ended, what happens?
> 
> :>Specifically, if this is a batch job, and the program running issues
> :>this STIMERM EXIT, and then ends, what happens?  Does the timer 
request
> :>go away with the ending of the task?  Or can unpredictable results
> :>happen if the STIMERM EXIT code (which is in a csect of the program
> :>running) gets control and trys to do its thing?

This is what happens at end of task with repect to STIMER:

If the terminating Task was attached by the Initiator, job 
step timing is turned off by setting on ASCBTOFF and ASCBCEXT. 
The Task's TQE queue (TCBTME) is then scanned, and all Real- 
type TQEs are dequeued from the system Real TQE queue as is the
Task TQE from the Task queue.  This stops the Timer SLIH from 
scheduling any more Timer SRBs for requests from this Task. 
PURGEDQ is then issued, which causes any already-scheduled Time
SRBs to finish or be stopped (in which case the IEAVRSPG RMTR 
will run to free the SRB).  At that point, we know that none of
the TQEs owned by the Task are in use and they are freed. 

Jim Mulder   z/OS System Test   IBM Corp.  Poughkeepsie,  NY

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: STIMERM EXIT question

2005-08-25 Thread Binyamin Dissen
On Thu, 25 Aug 2005 13:16:11 -0700 Charles Mills <[EMAIL PROTECTED]> wrote:

:>An STIMER exit runs on the TCB of the task that issued the STIMER, so
:>when that task goes away, the possibility of the exit goes away. I
:>suppose what you describe is technically kind of substandard programming
:>practice (you created the exit request, you cancel the exit request) but
:>MVS is smart enough not to dispatch a timer exit after the program goes
:>away.

As the TQE only has the TCB address (not the TTOKEN), if the address gets
reused it could be dispatched there.

I wonder if EOT processing runs the chain to remove them. I don't see anything
obvious hung off of the TCB.

:>-Original Message-
:>From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
:>Behalf Of Paul Schuster
:>Sent: Thursday, August 25, 2005 12:18 PM
:>To: IBM-MAIN@BAMA.UA.EDU
:>Subject: STIMERM EXIT question

:>Hello: If you have a STIMERM EXIT=,interval=,WAIT=NO, and the time
:>interval expires after the task has ended, what happens?

:>Specifically, if this is a batch job, and the program running issues
:>this STIMERM EXIT, and then ends, what happens?  Does the timer request
:>go away with the ending of the task?  Or can unpredictable results
:>happen if the STIMERM EXIT code (which is in a csect of the program
:>running) gets control and trys to do its thing?

--
Binyamin Dissen <[EMAIL PROTECTED]>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: STIMERM EXIT question

2005-08-25 Thread Charles Mills
An STIMER exit runs on the TCB of the task that issued the STIMER, so
when that task goes away, the possibility of the exit goes away. I
suppose what you describe is technically kind of substandard programming
practice (you created the exit request, you cancel the exit request) but
MVS is smart enough not to dispatch a timer exit after the program goes
away.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Paul Schuster
Sent: Thursday, August 25, 2005 12:18 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: STIMERM EXIT question


Hello: If you have a STIMERM EXIT=,interval=,WAIT=NO, and the time
interval expires after the task has ended, what happens?

Specifically, if this is a batch job, and the program running issues
this STIMERM EXIT, and then ends, what happens?  Does the timer request
go away with the ending of the task?  Or can unpredictable results
happen if the STIMERM EXIT code (which is in a csect of the program
running) gets control and trys to do its thing?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


STIMERM EXIT question

2005-08-25 Thread Paul Schuster
Hello: If you have a STIMERM EXIT=,interval=,WAIT=NO, and the time interval
expires after the task has ended, what happens?

Specifically, if this is a batch job, and the program running issues
this STIMERM EXIT, and then ends, what happens?  Does the timer request
go away with the ending of the task?  Or can unpredictable results happen
if the STIMERM EXIT code (which is in a csect of the program running)
gets control and trys to do its thing?

Thank you.

Paul

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html