<snip> It was set up this way when we decided we had to add a PC to our product 20 years ago. I believe the programmer was afraid that a customer could accidentally cancel the server started task and cause all running instances of our product to abend (which could include CICS and IMS/TM regions, batch jobs and a shared dataspace). He figured this technique would only prevent new instances of our product from starting and wouldn't be as big a problem for the customer to recover from. </snip>
What specifically is the "technique"? Using LXRES within a batch job is simply a bad idea. Apparently you want a separate LXRES for each user. That's OK (if likely very wasteful). But then you can have multiple started tasks. "The" server started task does not need to be the implementation. "A" server started task" could be (and each user connects to its own server). And of course the server task could be made non-cancelable. Further, canceling a server causes no abend in and of itself. Only when a client attempts to access would there be the expected problem, leaving opportunity for "waiting until restart" or whatever. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
