> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Steve Comstock
> Sent: Monday, December 04, 2006 8:36 AM
> To: [email protected]
> Subject: Re: Cancelling a job/tso user in a 100% CPU situation.
> 
> And so your refusal to "up 3rd period TSO" helps how? Is
> this the politically wisest approach? [Note: I don't
> know the answers in your situation; but I do know that
> mainframers (myself included) are often accused of being
> stubborn when being helpful might be a better approach.]
> 

The problem is that if I allow TSO users to do things, they will do
them. This may be to the detriment of Production Batch. Politically
speaking, IT itself is the "bottom feeder" of IT resources (cobbler's
children). If it were shown that Production was negatively impacted by
programmers doing "batch like" work under TSO, then the bovine excrement
would impact the air moving device with negative results. No, I cannot
take away the "batch like" work from them. It is usually used with small
amounts of data, as it is supposed to be. It is when some programmer
decides to run 1,000,000 records instead of 1,000 that it becomes a
problem. And I do want to "punish" them. I want to re-iterate "DO NOT DO
THAT!!!" And "messing them up" is the only way that I have. Poor, but
there is nought else that I may do. 

There is the constant battle to have enough cycles. Management wants a
minimal cost (reasonable?), so they more look at "average" need rather
than "peak" need. When the "peak" need season hits (month end), it is
more like pirana attacking a poor beastie than even a shark attack.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
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

Reply via email to