FW: When did SMF come along?
>From MXG Newletter FIFTEEN Nov 1989 - First Part - 1000 line limit IBM-MAIN CME 20/20: The History of SMF Session M710 August 21, 1989 H. W. Barry Merrill, PhD Merrill Consultants Dallas, Texas SHARE Installation CM4 ABSTRACT SMF became available 20 years ago with OS/360 Release 18. SHARE's 1964 SORC report was part of the input to IBM's 1966 SMF design document (authored by an IBMer who had been a SHARE board member). The design objective was two-fold: the stated SHARE requirements for control and evaluation of the installation, and the unstated need for IBM to understand how its OS and its program products were being used (which and how much). That 1966 design document, when compared with the current SMF implementation, will be shown to be remarkably accurate to the needs of users even today! The presentation will also discuss the never-announced and never-released IEHMAN report package!This presentation is based on recently de-classified IBM design documents and interviews with the original designers and developers of the SMF product. CONTENTS A. Jun 15, 1964 SORC Report 46-47 B. 1964-1967 Brockish Interview Notes 48-49 C. Aug 25, 1967 Task Force Report 50 D. Nov 1, 1967 IBM Memo 51 E. Nov 1, 1966 Objectives 52-57 F. Mar 13, 1967 Addendum I Subset 2 58-59 G. Mar 14, 1967 Addendum II60 H. Jul 27, 1967 Proposal Memo 60 I. 1967-1969 Schiffman Interview Notes 61-62 J. Oct 16, 1968 Subset I Final 62 K. Jan 31, 1969 Subset II Final 63-66 L. Jun 25, 1969 Subset II Final Final 67 M. IEHMAN 68 N. Jul, 1969 Release 1869 O. Oct, 1969 Release 18.6 70 P. Jun, 1970 Release 1971 Q. Feb, 1971 Release 2072 R. Aug, 1972 Release 21.6 72 S. 1972-1974 Merrill Notes 73-74 T. 1975-1977 Hankison Interview74 U. Aug 1, 1977 Objectives 75 V. Author's summary76 W. Contributors to this paper 76 Copyright (C) 1989 Merrill Consultants, Dallas, Texas. This paper will be published in a 1989 issue of the "Technical Newsletter for Users of MXG". Permission is hereby granted to SHARE, Inc. to publish this presentation in SHARE Proceedings. Merrill Consultants retains its right to distribute copies of this presentation to whomever it chooses. On April 7, 1964, IBM Announced OS/360. Were you computer literate then? The IBM Design of SMF Was The Direct Result Of The 1964 SHARE Systems Objectives and Requirements Committee "SORC". The SORC Report was produced only two months after OS/360 announcement! APPENDIX F Report of SHARE Systems Objectives and Requirements Committee June 15, 1964 G.E. Bryan, Chairman L. Cohn P.A. Cramer R. Gillespie G.H. MealyC.H. Weisert "IV. JOB ACCOUNTING AND SYSTEM PERFORMANCE MEASUREMENT Theadventof multi-programmed and multi-processor machine configurations has re-emphasized the always present need for job accounting and made even more important the much neglected area of machine and program performance measurement. Operating systems for System/360 must provide as a standard feature a job accounting system which retains records useful for both ordinary cost allocation of machine component time and measurement of hardware and software performance. Accounting and statistical information should be carried in the system on a job basis and identified by the following information supplied by the submitter of the job: 1. A job number. 2. A programmer identification number. 3. An identification specific to the run. 4. Priority. 5. Other information as deemed necessary by the individual installation. In addition, in order to facilitate automatic scheduling of jobs for optimum performance, the following should be supplied either by the job submitter or, for "normal cases," be defined by installation standard parameters. 6. Expected execution time, cutoff time. 7.
FW: When did SMF come along?
>From MXG Newletter FIFTEEN Nov 1989 - First Part - 1000 line limit IBM-MAIN CME 20/20: The History of SMF Session M710 August 21, 1989 H. W. Barry Merrill, PhD Merrill Consultants Dallas, Texas SHARE Installation CM4 ABSTRACT SMF became available 20 years ago with OS/360 Release 18. SHARE's 1964 SORC report was part of the input to IBM's 1966 SMF design document (authored by an IBMer who had been a SHARE board member). The design objective was two-fold: the stated SHARE requirements for control and evaluation of the installation, and the unstated need for IBM to understand how its OS and its program products were being used (which and how much). That 1966 design document, when compared with the current SMF implementation, will be shown to be remarkably accurate to the needs of users even today! The presentation will also discuss the never-announced and never-released IEHMAN report package!This presentation is based on recently de-classified IBM design documents and interviews with the original designers and developers of the SMF product. CONTENTS A. Jun 15, 1964 SORC Report 46-47 B. 1964-1967 Brockish Interview Notes 48-49 C. Aug 25, 1967 Task Force Report 50 D. Nov 1, 1967 IBM Memo 51 E. Nov 1, 1966 Objectives 52-57 F. Mar 13, 1967 Addendum I Subset 2 58-59 G. Mar 14, 1967 Addendum II60 H. Jul 27, 1967 Proposal Memo 60 I. 1967-1969 Schiffman Interview Notes 61-62 J. Oct 16, 1968 Subset I Final 62 K. Jan 31, 1969 Subset II Final 63-66 L. Jun 25, 1969 Subset II Final Final 67 M. IEHMAN 68 N. Jul, 1969 Release 1869 O. Oct, 1969 Release 18.6 70 P. Jun, 1970 Release 1971 Q. Feb, 1971 Release 2072 R. Aug, 1972 Release 21.6 72 S. 1972-1974 Merrill Notes 73-74 T. 1975-1977 Hankison Interview74 U. Aug 1, 1977 Objectives 75 V. Author's summary76 W. Contributors to this paper 76 Copyright (C) 1989 Merrill Consultants, Dallas, Texas. This paper will be published in a 1989 issue of the "Technical Newsletter for Users of MXG". Permission is hereby granted to SHARE, Inc. to publish this presentation in SHARE Proceedings. Merrill Consultants retains its right to distribute copies of this presentation to whomever it chooses. On April 7, 1964, IBM Announced OS/360. Were you computer literate then? The IBM Design of SMF Was The Direct Result Of The 1964 SHARE Systems Objectives and Requirements Committee "SORC". The SORC Report was produced only two months after OS/360 announcement! APPENDIX F Report of SHARE Systems Objectives and Requirements Committee June 15, 1964 G.E. Bryan, Chairman L. Cohn P.A. Cramer R. Gillespie G.H. MealyC.H. Weisert "IV. JOB ACCOUNTING AND SYSTEM PERFORMANCE MEASUREMENT Theadventof multi-programmed and multi-processor machine configurations has re-emphasized the always present need for job accounting and made even more important the much neglected area of machine and program performance measurement. Operating systems for System/360 must provide as a standard feature a job accounting system which retains records useful for both ordinary cost allocation of machine component time and measurement of hardware and software performance. Accounting and statistical information should be carried in the system on a job basis and identified by the following information supplied by the submitter of the job: 1. A job number. 2. A programmer identification number. 3. An identification specific to the run. 4. Priority. 5. Other information as deemed necessary by the individual installation. In addition, in order to facilitate automatic scheduling of jobs for optimum performance, the following should be supplied either by the job submitter or, for "normal cases," be defined by installation standard parameters. 6. Expected execution time, cutoff time. 7.
