> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Zelden > Sent: Wednesday, May 25, 2005 3:38 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Region size question > > > On Wed, 25 May 2005 15:11:01 -0500, McKown, John > <[EMAIL PROTECTED]> wrote: > > >Of course, if an initiator is badly > >fragmented, it might be nice to have a way to automagically > restart it. > > > > You can! This became available in z/OS 1.5. We skipped 1.5, but > I implemented this as we rolled out z/OS 1.6 on each system. It > is done via VSM CHECKREGIONLOSS(below,above) setting in DIAGxx > and works with both JES2 initiators and intitiators managed by > JES3, WLM and APPC. > > For example, my DIAGxx looks like this: > > VSM TRACK CSA(ON) SQA(ON) > VSM TRACE GETFREE(OFF) > VSM CHECKREGIONLOSS(300K,10M) > > Prior to this we had automation code that recycled INITs whenever > a job abended. Back when we had JES2 managed INITs we also > recycled them on a time scheduled basis several times a day. > > Thanks again to Jim Mulder for implementing this to "fix" a problem > that has been around longer than I have been doing sysetm's > programming. > > Mark
Good. Another reason to upgrade from z/OS 1.4. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
