> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUK 3)
> Sent: Wednesday, October 24, 2007 8:44 AM
> To: [email protected]
> Subject: Re: Outsmarting WLM
>
>
> >>Wouldn't is be sufficient to run the "keep BPXAS alive"
> >>program periodically, say every 15 minutes? The new childs
> >>would use idle BPXASs and WLM would create new ones if the
> >>overall system load permits this.
> >
> >Well, I don't want to unnecessarily create new BPXASs when
> >the system is already busy handling a spike in 'real
> >workload' and that spike happens to coincide with expiration
> >of a 15-minute interval (or however long that interval is).
>
> But when that "spike" is using all but one BPXAS and this last
> one times out, the "BPXAS has ended" mechanism would trigger
> as well and create a bunch of new ones, wouldn't it?
>
> You'd need to count the number of idle BPXASs and decide then
> if and how many to "create". Idle ones are those which show
> up as "BPXAS" in a D A,BPXAS. Haven't thought about how to
> get that information in the keep-alive program, I admit.
>
>
> --
> Peter Hunkeler
If you are using CA-OPS/MVS, then you might be able to do something
like:
)MSG $HASP395
)PROC
IF WORD(MSG.TEXT,2) = 'BPXAS' THEN DO
RUNNING=OPSTATUS("A","A","BPXAS")
IF RUNNING < 10 THEN DO
ADDRESS OPER "F KEEPUP,"10-RUNNING
END
END
RETURN
The "keep alive" STC is called KEEPUP. It allows operator modify
commands. The MODIFY command's argument is simply the number of times to
fork() a child. The "10" in the rule is arbitrary. Of course, the above
does have the possibility of issuing multiple MODIFY command quickly,
possibly resulting in more than 10 fork()'s. But this can be minimized
by having the code ignore and purge any queued MODIFY commands before
waiting on the CIB again.
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.
----------------------------------------------------------------------
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
