This is going to sound weird. It is in conjunction with some other strangeness 
that I am considering. But I need to create a z/OS task in my TSO region which 
does not "go away" (abend) when the TSO command which starts it terminates. 
I.e. it would be a "TSO DAEMON" to mix TSO and UNIX terminology. What I think I 
can do is have my TSO command back up the TCBOTC fields until I found the TCB 
whose TCBRBP points to the RB running IKJEFT01. I can then schedule an IRB to 
run under than TCB which will do an ATTACH of my "daemon" code. The problem at 
this point is that I am fairly sure that there is no way for my "daemon" task 
to shutdown normally when the user does a LOGOFF command, which would result in 
an A03 abend. I don't really mind that myself, but it is "not elegant". My next 
thought is to do the previous, but use the TCBFSA for that TCB in order to 
modify the saved value of R14 so that I can insert my own code into the 
shutdown for IKJEFT01. I'm not sure this will really work. That is, I'm not 
sure IKJEFT01 shuts down using a standard RETURN instead of, say, SVC 3.

What I want is a subtask which is started up either from the TSO READY or from 
ISPF option 6 or the TSO command in ISPF which will "stay around" until the TSO 
user either runs another "shutdown" TSO command or the standard TSO LOGOFF 
command. This subtask is a "communications end point" for another address space 
so that a TSO command can send a message and receive a response from that 
"server". It's not really a "server". But I'm still in the "vaguely mulling 
things around" stage, so I can't be more exact.

John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM


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

Reply via email to