On Mon, 16 Nov 2009 16:15:34 -0500, David Cole wrote: > >5.) All information needed is specified through JCL or through the >PARM field. No control dataset (SYSIN, for example) is needed. > How much information can you put in that there PARM field? (Rhetoric! do not answer!)
>If you could put all your "sysin" into files and write all your >"sysprint" out to temporary files, and then have a single, final >jobstep that would write all of those files, regardless of DCB >attributes, to the printer, then you could save a boatload of money! >(Real money, in the case of a commercial customer ...) > University of Colorado, about the same era had one similar, on a CDC 6400 with a locally devised chargeback formula. They weighted a bunch of resource use, particularly I/O's by the job's storage use, averaged with respect to CPU time. So, a job that did a lot of I/O with a large region, followed by a step that used a lot of CPU time at minimal region (how much does a spin loop need?) could see its charges actually decrease during that final step. I never exploited that, but did share the algebra with a very chargeback-constrained colleague. He added to each of his jobs a final step with a spin loop carefully calculated to minimize the total charge for the job. U of C charged for disk storage according to an audit in the middle of the night. The same colleague unloaded all his files to tape in the late evening and reloaded them in the early morning. Backup was a collateral benefit. -- gil ---------------------------------------------------------------------- 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
