Brian,
//EXTR EXEC PGM=LOADER,PARM='/,32(2),CUSTOMER NUMBER xxxxxxxxxx' //SYSPRINT DD SYSOUT=* //SYSLOUT DD SYSOUT=* //SMF DD DISP=SHR,DSN=MISOS.SMF.MONTHLY(+0) //OUTPUT DD DISP=(,CATLG),DSN=MISTU.SCPTOOL.CSV,UNIT=SYSDA, // SPACE=(TRK,(15,15),RLSE) //SYSLIN DD * In the above example "32" is the MSU value specified in Defined Capacity and "2" is the number of lpars. From what I've gathered reading the white paper on the subject and the JCL instructions the MSU's we would be billed from are based on the Defined Capacity (32 in our case) but I don't see that reflected anywhere in the SCRT. We are running a z800-0a2 and the MSU's show 44 even though it has been changed on the HMC and is reflected as 32 in SHOWMVS (for instance). When I let the PARM default I get a "44" and 2 lpars and one set of numbers. When I code the MSU value (Defined Capacity #) I get a much lower set of numbers which sounds to -me- like our bill would be considerably less if the MSU was coded. I'm just trying to figure out how others are doing it. This whole thing isn't making much sense to me right now, based on the numbers. Bill Mainframe - An obsolete device still used by thousands of obsolete companies, serving billions of obsolete customers, and making huge obsolete profits, for their obsolete shareholders. And this year's run twice fast as last year's. -Phil Payne- ---------------------------------------------------------------------- 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
