On Tue, 15 Apr 2008 12:03:58 -0400, Jack Kelly <[EMAIL PROTECTED]> wrote:
> <snip> >IDMS mechanism to serialize batch usage > <snip> > >Just thought that I'd give a final update to this issue in case it's of >any interest to other parties. >IDMS batch indeed serializes on a planned ENQ conflict. 'Enqueue >Promotion' notifies SRM and SRM boost the service of the holder (in this >case the IDMS batch job) for ERV (default: 500 CPU SU's). In our scenario, >the batch IDMS jobs were executing at a higher dispatching priority than >the rest of batch, even as high as the IDMS', even though these batch jobs >were in a discretionary Service Class. Since I had the default ERV, i.e. >no IEAOPTxx member, and we have a small processor, these batch job ate the >box. I did turn off ERV and the processing smoothed out, changing it to a >much smaller number made things less worse but not better. >Of course CA thinks that this is an IBM problem, IBM rightly (I think) >disagrees, and CA can not (or won't) change the way IDMS serializes batch >work (it's worked for years, so why change!). > We run CA-Dispatch which utilizes IDMS as its online TP. We also run the archive and extract tasks externally to the Dispatch region and after you last post I looked at the behavior you described. I didn't see it. The extract and archive tasks run at the DP I expect them to in regards to the service class I have those STCs defined in. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
