Re: Where do I start?

BTW, KICKS already does this, automaticially! Files are closed expect when a transaction is actually using them, so a batch job can do open/read/write/close as it wants and if a KICKS transaction comes along while that's going on the transaction just gets a "not open" abend as it would in real CICS if you had closed the file. Except in KICKS you don't have to remember to manually CLOSE the file, nor to manually OPEN the file again when your batch job finishes, 'cause KICKS just handles it.

Of course you still might want to temporarily shutdown KICKS and prevent further KICKS logons (while allowing normal TSO use), just as you sometimes need to actually shutdown real CICS, and KICKS provides a simple procedure to accomplish this as well.

--- In [email protected], Kevin Monceaux <Kevin@...> wrote:
... a proper CICS clone should be able to do things like close individual files to run batch jobs without having to shut the CICS clone down, ...