What you have said was true in the past, about jobs having more data in SMF than STCs sometimes did. Some STCs must still be single step, such as an external writer or anything running a program in the PPT. This is not true of CICS. We run multi-step CICS regions as started jobs (not tasks) as our standard. Perhaps some shops ran a process as a job just in order to run multiple steps which were procs. In the past, an STC had to be a single PROC. Also, with STC (started procs), all the STCs ran with the same, generated, pseudo-JOB card. Some shops wanted to run with different job accounting parameters, for billing purposed. They either had to do some fancy exit programming, or ran as a batch job. But with started jobs, you can now run an STC as a "started job" (complete with JOB card with all parameters except CLASS=) with multiple EXEC PROC= steps. Also, you can now nest PROCs and so have an STC be a PROC, but that that PROC can run the other PROCs required in order.
We run CICS as a "started job". I changed to this on the first release of z/OS in which it was available. -- 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 > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex R. > Sent: Friday, August 10, 2012 10:51 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: reasons for using started task or batch job > > Hi List, > > I'm sure this has been discussed but I can't find it in the > archives (probably due to my inability to narrow the search down). > > What would be the reason(s) for starting long-running tasks > like CICS as a started task or a batch job? My foggy brain > seems to remember there being issues with running multi-step > started tasks, and something about there not being as much > data gathered (performance, diagnostics, that kind of stuff) > for a started task versus a batch job. > > Any pointers to limitations or other info one way or the > other would be appreciated. > > Thanks. > > Rex > > The information contained in this e-mail may contain > confidential and/or privileged information and is intended > for the sole use of the intended recipient. If you are not > the intended recipient, you are hereby notified that any > unauthorized use, disclosure, distribution or copying of this > communication is strictly prohibited and that you will be > held responsible for any such unauthorized activity, > including liability for any resulting damages. As > appropriate, such incident(s) may also be reported to law > enforcement. If you received this e-mail in error, please > reply to sender and destroy or delete the message and any > attachments. Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
