On Tue, Mar 8, 2016 at 11:59 PM, Jesse 1 Robinson <[email protected]> wrote:
> Ah, bad or perverse behaviors. Two stand out in my career. > > -- A data base application was redesigned at the last minute to read the > entire data base into memory at startup. The business unit noticed that > they were charged for I/O but not for memory use. It was cheaper to occupy > virtual storage than to perform reads. So much for common sense. > > -- An ISAM application that could have been converted to VSAM--as > discussed in a recent thread--was deliberately left to the sluggish > vicissitudes of ISAM because of how the client contract was written. Data > center would have collected less revenue with a more efficient process. > Yuck. > > We no longer do any type of charge back. But I recall one bad from the past. We charged based on service units. One group noticed that if they ran a job at night, it would take more service. So they demanded that it run during the day. The reason it got more SUs at night was because the system was closer to idle. So more real memory was available. So their "working set" wasn't being trimmed. So the MSO (Main Storage Occupancy) portion of the SU amount went up. Basically, they were penalized for running work while the system was less busy. We changed the SU calculation so that MSO was 0, or as close to 0 as we could make it. > . > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-302-7535 Office > [email protected] > > -- A fail-safe circuit will destroy others. -- Klipstein Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
