On Dec 14, 2005, at 8:45 AM, Knutson, Sam wrote:
Most sites I have seen run CICS as a started task.
Most sites also control CICS and other on-line systems with an
automated
operations package like CA-OPSMVS, IBM SA, etc. rather than a batch
job
scheduler.
This is not universal just what I have observed as common practice.
This has the advantage of providing a clean virtual storage
environment
to CICS each time it starts.
You also have the advantage that you do not have to define an
initiator
to JES2 to run the started task especially at sites with hundreds or
thousands of CICS regions this would be a significant issue.
Mark Zelden provided the very nice answer below to a similar
question at
search390.
Sam,
While some of the reasons that Mark Z talked about are valid, my
experience is just the opposite from yours most shops I have seen do
have jobs that run CICS.
And as far as I could discern if you have good change control and jcl
conventions there seems to have little left in any real advantage to
running it as a STC.
Somewhere in the mists of time there was a good reason (storage issue
I believe) to get all the available free storage if you ran it as an
STC.
That being said, the debate on here, IIRIC came down to no real
reason to do so anymore. Of course its up to each installation how
they chose to run their CICS's. I was talking from a technical point
(the reason BEFORE they have all the bells and whistles they do now
have) why it should be done. This may come down to I have done it
this way and I will continue to do so.
Ed
----------------------------------------------------------------------
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
