On Fri, 24 Jun 2005 11:15:58 -0400, Richard Verville wrote:

>>I have this routine that is notreentrant and needs to be OS loaded (instead
>>of CICS loaded) and while using storage protection in CICS is has to be in
>>key9 because the program updating it, is running key9. Right now the key9
>>program loads it and it gets in Key 8, fetch protected storage. So there
>>other programs reading it gets a fetch protection exception.

>Failing that, your design is apparently off where the trains don't run...
>not a good idea for most purposes (although the view is different out
>beyond the trees.)

I'm sure I'll be punished for this response, but here goes.
Writing to an ExtraPartitioned TDQ used to put CICS main-TCB into a Wait (QSAM) 
(not so long ago).
A solution for this (and other problems like SUBMITs) was to write a hand-shake 
program to run in CICS that talked to an ATTACHED (or LOADed) program. In that 
design the attached program could be a table and sort logic or anything else. 
The hand-shake had to anticipate all CICS issues, like Starting and 
initializing, single threading (hold an enqueue), Stopping, etc. The attached 
program had to manage its own Getmains, initialization, Freemains, etc.

CICS now does essentially the same thing in an archected way for TDQs, and can 
use the JesSpool interface for Submits, etc.

As others are wondering, Why non-reentrant? How can you update a program, or is 
it a table? What does it do in batch?


--

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.

----------------------------------------------------------------------
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

Reply via email to