DOCSLIB.ORG

Systems Reference Library IBM 7090-7040 Direct

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

File No. 7090-36 Form C28-6383-2 Systems Reference Library IBM 7090-7040 Direct Couple Operating System Systems Programmer's Guide This publication contains information useful to programmers who require a thorough understanding of the IBM 7090-7040 Direct Couple Operating System (DCOS), #7090-PR-161. This system consists of the following parts: 7090/7094 Operating System (IBSYS) 7040/7044 Control Program (DCMUP) The publication provides descriptions of general DCOS program logic, the format of the DCOS System Library, the Operating System Monitor (DC-IBSYS), and the lnput/Output Executor (DC-IOEX). It also includes instructions for system library preparation and maintenance. Separate publications contain descriptions of the compo­ nents of the 7090/7094 Operating System (IBSYS). Other related publications contain information needed by applica­ tions programmers and instructions for machine operators. Form C28-6383-2 Page Revised 6/11/65 By TNL N28-0158-0 PREFACE This publication is primarily intended IBM 7040/7044 Principles of Operation, for systems programmers who are responsible Form A22-6649 for the maintenance of the 7090-7040 Direct Couple Operating System (DCOS} and any modifications to it at the installation. IBM 7090 Principles of Operation, Form It may also be of interest to individuals A22-6528 who desire a more thorough understanding of the system. IBM 7094 principles of Operation, Form A22-6703 The reader of this publication is Directly Coupled Processing Units--7040 assumed to be familiar with the contents of to 7090/7094; 7040 to 7094/7094 II, Form the publication IBM 7090-7040 Direct Couple A22-6803 Operating System: Programmer's Guide, Form C28-6382. The Direct Couple Operating System is designed for five machine configurations: Information required by machine opera­ tors is contained in the publication IBM 1. 7090-DC-7040 7090-7040 Direct Couple Operatinq Syst~ 2. 7094-DC-7040 Operator's Guide, Form C28-6384. 3. 7094-DC-7044 4. 7094 II-DC-7044 For information on the IBJOB processor, 5. 7094 II-DC-7040 the major subsystem of DCOS, the reader is referred to the following IBM publications: Throughout this publication, the terms 7090 and 7040 are used to refer to the IBM 7090/7094 IBSYS Operating System: 7090, 7094, or 7094 II and to the 7040 or IBJOB Processor, Form C28-6389 7044, respectively, as permitted in the IBM 7090/7094 Proqramming Systems: FOR­ configurations above. TRAN IV Language, Form C28-6390 IBM 7090/7094 Programminq Systems: Macro This publication is divided into ten Assembly Program (MAP) Language, Form sections. The first section is devoted to C28-6392 the logic flow of the 7040 side of the IBM 7090/7094 Programming Systems: COBOL system. The next three sections are devot­ Language, Form C28-6391 ed to the 7090 side of the system. The IBM 7090/7094 IBSYS Operating System: fifth section explains the logic used by IBJOB Processor Debugging Package, the 7040 when servicing 7090 input/output Form C28-6393 requirements. The sixth section describes the DCOS Distribution Tape. The seventh Information about the IBM 7040/7044 Data section describes system editing proce­ Processing Systems, the IBM 7090/7094/7094 dures. The eighth and ninth sections deal II Data Processing Systems, and for the with system library preparation and main­ Direct Couple feature are given in the tenance. The last section discusses DCOS following publications: unit assignment philosophies. Major Revision (March 196~ This edition, Form C28-6383-2, is a major revision of Form C28-6383-1. This publication amplifies material pre­ viously presented, and, in some cases, provides additional material. Major changes and additions are concerned with: examples of system modification, unit control blocks (7040 tape units), the DCOS distribution tape, the system editor (IBEDT), job setup, the $JOB card, and the *REMARK card. Additions or changes are indicated by a vertical line to the left of the text; new or revised illustrations are denoted by the symbol • to the left of the caption. The following publications are made obsolete by this revision: C28-6383-1, C28-6383-0,and the Technical Newslet­ ters N28-0146-0 and N28-0144-0. Copies of this and other IBM publications can be obtained through IBM Branch Offices. A form for readers' comments appears'at the back of this publication. It may be mailed directly to IBM. Address any additional comments concerning this publication to the IBM Corporation, Programming Systems Publications, Department D39, 1271 Avenue of the Americas, New York, NY., 10020. C 1964 by International Business Machines Corporation Form C2B-6383-2 Page Revised 6/11/65 By TNL N2B-015B-O CONTENTS INTRODUCTION TO DCOS 7 $UNITS Card • • • • • • • • • • • • • 26 DCOS Use of Disk/Drum Storage Units 7 DC-IBSYS NUCLEUS 27 Modes of Operation • • • • 8 Communication Region 27 The Direct Mode •• • • 8 The Compatibility Mode • 8 System Unit Function Table 28 General Logic Flow 8 Unit Availability Table •• 29 The DCOS Commutator 10 The Job Queue Table 10 Job Control Communication With The Job Description Block 10 Subsystems • • • • • • • • • • 29 Unit Control Blocks (7040 Tape Communication Region Locations Uni tS) •••••••••••••• 10 SYSRET, SYSGET, and SYSJOB •••• 29 File Control Blocks •••••• 10 Channel Information Blocks • • • •• 10 Recognition of DC-IBSYS Supervisor Input/Output File Control Block Base Control Cards by SUbsystems 30 (IOBASE) ••••••• 12 $IBSYS Card 30 Data Buffer Format • • • 13 $EXECUTE Card 30 Input Service Routine 14 $STOP Card • 30 Job Setup 14 $ID Card • • • • • 30 Initialization for 7090 Execution 17 Job Breakdown 17 DIRECT COUPLE INPUT/OUTPUT EXECUTOR • • 31 Punch Stage • • • • • 17 Print Stage • • • • • 18 Unit Control Blocks • 31 Background Utility Routines 19 Word 1 • • • • 31 7040/7044 Utility Routines • 19 Word 2 • • • • • 33 Word 3 • • • • • 33 DC-IBSYS MONITOR 21 Word 4 33 DC-IBSYS SUPERVISOR • • 22 Unit Priority on a Channel 33 Channel-Priority Location • • • • • 33 Initialization Procedures • 22 Use of Channel-Priority Location 34 Activating a Channel and/or Assigning Basic Supervisor Control Cards 22 Priority • • ~ • • • • • • • • • • 34 $Job Card 22 $EXECUTE Card 22 Non-Data Selects ••••• 35 $ID Card • • 23 Structuring of Input/Output Requests in Direct Mode • • • • 35 Unit Assignment Control Cards • 23 $ASSIGN Card • 23 INPUT/OUTPUT IN THE TWO DCOS MODES 37 $RELEASE Card 24 $RESET Card 24 Processing Input/Output Requests $SWITCH Card 24 (Direct Mode) •••••••••• 37 $CARDS Calrd 24 Processing Input/Output Requests $TAPE Card •• 24 (Compatibili ty Mode) 40 Tape-Manipulation Control Cards 24 DISTRIBUTION OF DCOS 41 $ENDFILE Card 24 $REWIND Card 25 Listings 41 $REMOVE Card • • 25 $UNLOAD Card • • • • • • 25 DCOS Distribution Tape 41 File 1 • • • • • 41 Miscellaneous Control Cards 25 File 2 41 $STOP Card • • • • • • • 25 File 3 41 $IBSYS Card • • • • 25 File 4 42 Files 5-15 42 DC-IBSYS Supervisor Control Cards • 25 $RESTORE Card 25 SYSTEM EDITOR (IBEDT) 43 $IBEDT Card 26 *EDIT Card • • • • • 48 Form C28-6383-2 Page Revised 6/11/65 By TNL N28-0158-0 Arrangement of DCMUP, DC-IBSYS, IBSYS Respecification of 7040 Disk (Drum) Subsystems and the System Editor •••• 48 Environment • • •• • • • 67 *PLACE Card • • • • • • • • • • • • • 48 Maintenance of the System Name and Preparation of a New DCSYS from a DCOS Loader Tables. • 48 PRESYS Library. • 68 Alteration Cards • • • • • • • • • • 49 Posteditor Output. • 69 Absolute Column-Binary Cards. • 50 7040 System Name Table. • 69 Octal Cards • • • • • • • • • • 50 Track Allocation and Module Definition Table ••••• • 70 Standard PRESYS Library Record Formats • 50 Utility Name Table ••••• • 70 Posteditor Output Tape (DCSYS) Maintenance Control Cards ••• • 51 Format • • • • • • • • • • • • • 71 *MODIFY Card. • • 51 *REPLACE Card • • 51 Posteditor Restrictions and Error *INSERT Card. • 52 Messages. • 71 *REMOVE Card. • • .53 *AFTER Card • • • 53 DCOS UNIT ASSIGNMENT PROCEDURES •• • 73 *DUP Card ••• • 53 7040 File Control Blocks •••• • 73 *REWIND Card. • • 54 Assignment of 7040 Tape Units to *CHECK Card • • • 54 7040 File Control Blocks • • • • 74 *REMARK Card. • • 54 Communication Of 7040 File Control Termination of Editing • • 54 Block--7090 Unit Control Block Relationship. • • • • • • • • • • • 74 Editing Relocatable Records. • • • 54 IBLDR Unit Assignment Process ••• 75 Editing Examples • • 55 Assignment of Secondary Units • 76 Example 1 • 55 Example 2 • • • • 55 Unit Assignment In Other IBSYS Subsystems. • • • • • • • • • • • • 76 DCOS PRESYS LIBRARY MAINTENANCE. • 57 Unit Assignment Procedures for Preparing a Backup DCOS Distribution Non-IBSYS Systems/Programs •• 78 Tape or PRESYS Library Tape •• •• 57 Unit Assignment Considerations 78 Changing The System Input/Output Configurations ••••••••• • 57 APPENDIXES • 80 7040 Input/Output Configuration • 58 Appendix A: DCMUP Tables and Control Incorporating a User-Designed Blocks. • • • • • • • • • 80 Installation Accounting Routine Under The Job Queue Table • • 80 DC-IBSYS. • • • • • • • • • • • • • • • 61 Job Description Block • • 80 Designing An Installation DCMUP Track Allocation Maps 83 Accounting Routine • • • • • • 61 File Control Block. • • • • • 83 Incorporating an Accounting Routine Unit Control Blocks (7040 Tape into a Subsystem. • • • • 61 Uni tS) • • • • • • • • • • • 84 Channel Information Block • 85 Incorporating IBSYS Subsystems Under DC-IBSYS. • • • • • • • • 62 Appendix B: Procedure for Defining Compatibility Mode. • • • • • • 62 an IOBASE Table • • • • • • 86 Direct Mode • • • • • • • • • • 62 Zero
Recommended publications
  • On-Line Computing with a Hierarchy of Processors

    On-Line Computing with a Hierarchy of Processors

    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science December 1968 On-Line Computing With a Hierarchy of Processors Richard P. Morton University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Richard P. Morton, "On-Line Computing With a Hierarchy of Processors", . December 1968. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-69-13. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/804 For more information, please contact [email protected]. On-Line Computing With a Hierarchy of Processors Abstract Time shared computer systems have been based upon the two techniques of multiprogramming and swapping. Multiprogramming is based on restricting each program to a portion of the total computer memory. Swapping requires considerable overhead time for loading and unloading programs. To alleviate the size restriction due to multiprogramming, segmentation is employed, resulting in fact in vastly increased swapping. A new system architecture is proposed for time shared computing that alleviates the high overhead or program size restriction. It utilizes a hierarchy of processors, where each processor is assigned tasks on the basis of four factors: interactive requirements, frequency of use, execution time, and program length. In order to study the hierarchical approach to system architecture, the Moore School Problem Solving Facility (MSPSF) was built and used. The study of the manner of operation and the reactions of the users clarified and defined the Hierarchy of Processors system architecture. The Moore School Problem Solving Facility was implemented on second generation equipment, the IBM 7040, and therefore it is not possible to adequately compare the efficiency with third generation computers operating in a swapping mode.
  • The Evolution of Econometric Software Design: a Developer's View

    The Evolution of Econometric Software Design: a Developer's View

    Journal of Economic and Social Measurement 29 (2004) 205–259 205 IOS Press The evolution of econometric software design: A developer’s view Houston H. Stokes Department of Economics, College of Business Administration, University of Illinois at Chicago, 601 South Morgan Street, Room 2103, Chicago, IL 60607-7121, USA E-mail: [email protected] In the last 30 years, changes in operating systems, computer hardware, compiler technology and the needs of research in applied econometrics have all influenced econometric software development and the environment of statistical computing. The evolution of various representative software systems, including B34S developed by the author, are used to illustrate differences in software design and the interrelation of a number of factors that influenced these choices. A list of desired econometric software features, software design goals and econometric programming language characteristics are suggested. It is stressed that there is no one “ideal” software system that will work effectively in all situations. System integration of statistical software provides a means by which capability can be leveraged. 1. Introduction 1.1. Overview The development of modern econometric software has been influenced by the changing needs of applied econometric research, the expanding capability of com- puter hardware (CPU speed, disk storage and memory), changes in the design and capability of compilers, and the availability of high-quality subroutine libraries. Soft- ware design in turn has itself impacted applied econometric research, which has seen its horizons expand rapidly in the last 30 years as new techniques of analysis became computationally possible. How some of these interrelationships have evolved over time is illustrated by a discussion of the evolution of the design and capability of the B34S Software system [55] which is contrasted to a selection of other software systems.
  • IBM 1401 System Summary

    IBM 1401 System Summary

    File No. 1401-00 Form A24-1401-1 Systems Reference Library IBM 1401 System Summary This reference publication contains brief descriptions of the machine features, components, configurations, and special features. Also included is a section on pro­ grams and programming systems. Publications providing detailed information on sub­ jects discussed in this summary are listed in IB~I 1401 and 1460 Bibliography, Form A24-1495. Major Revision (September 1964) This publication, Form A24-1401-1, is a major revision of and obsoletes Form A24-1401-0. Significant changes have been made throughout the publication. Reprinted April 1966 Copies of this and other IBM publications can be obtained through IBM Branch Offices. Address comments concerning the content of this publication to IBM Product Publications, Endicott, New York 13764. Contents IBM 1401 System Summary . ........... 5 System Concepts . ................ 6 Card-Oriented System .... ......... 11 Physical Features. 11 Interleaving. .. .................................... 14 Data Flow.... ... ... ... ... .. ... ... .. ................... 14 Checking ................................................... 15 Word Mark.. ... ... ... ... ... ... .. ... ... ... ........... 15 Stored-Program Instructions. .................. 15 Operation Codes . .. 18 Editing. .. ............ 18 IBM 1401 Console ............................................ 19 IBM 1406 Storage Unit. ........................... 20 Magnetic-Tape-Oriented System . ........................... 22 Data Flow .................................................
  • UBC Information Technology (IT) Fonds

    UBC Information Technology (IT) Fonds

    UBC Information Technology (IT) fonds Compiled by Vincent Ouellette (1986) Revised by Tahra Fung (1999), Elissa How (2013), Erwin Wodarczak (2015, 2018), Syr Reifsteck (2017), and Manfred Nissley (2019). Last revised January 2019 *** Institutional records -- researcher access subject to review *** University of British Columbia Archives Table of Contents • Fonds Description o Title / Dates of Creation / Physical Description o Administrative History o Scope and Content o Notes • Sous fonds description o Canadian Information Processing Society (CIPS) Sous-fonds • Series Descriptions o Early Computing Centre Series o Pre-1969 Series o 1969-1978 Series o Systems Hardware Operations Committee (SHOC) Series o Software Committee Series o Manuals and Technical Information Series o UBC Computing Centre Newsletter Series o 1979-1989 Alphabetical Series o 1973-1996 Chronological Series o UBC Computing Centre Documentation Series o Miscellaneous Series o Jim Tom’s Office Chronological Series o Photographs Series • File List • Catalogue entry (UBC Library catalogue) Fonds Description UBC Information Technology (IT) fonds. - 1954-1996. 8.59m of textual records. 70 photographs. Cartographic material. Administrative History In the autumn of 1955, President Norman Mackenzie appointed a Committee on Automation to investigate "the University's total interest in computers and automation in general". The Committee consisted of approximately 20 members representing most of the research interests on campus and was chaired by E.D. McPhee. At the Committee's first meeting on November 16, 1955, four sub-committees were formed: Departmental Interests and Specifications; Training and Curriculum: Type Equipment; and Library Needs and Resources. The Committee held several meetings and prepared a number of reports on various facets of computerization.
  • CERN LIBRARIES, GENEVA CERN/SPC/220 28 February, 1966

    CERN LIBRARIES, GENEVA CERN/SPC/220 28 February, 1966

    CERN LIBRARIES, GENEVA CERN/SPC/220 28 February, 1966 CM-P00095068 ORGANISATION EUROPÉENNE POUR LA RECHERCHE NUCLÉAIRE CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH SCIENTIFIC POLICY COMMITTEE Thirty-eighth Meeting 8 March, 1966 EXTENSIONS TO THE CERN COMPUTING FACILITIES by Dr. M.G.N. Hine The attached paper contains a review of CERN's needs from its central computing facilities, both in the near future and as far as 1969-1970. It describes possible ways in which these needs might be met within the budget forecasts, and suggests an optimum way to proceed. The scientific policy is to be discussed at the Scientific Policy Committee meeting on 8th March. If the policy line is cleared at that meeting, the Finance Committee could start discussion of the contractual implications at its meeting on 10th March. The Finance Committee would not be pressed to give final decisions at that meeting about contract adjudications, but those decisions will be needed in the near future. 66/348/5 CERN/SPC/220 EXTENSIONS TO THE CERN COMPUTING FACILITIES 1. Introduction The need to continue the development of computing facilities at CERN in order to keep pace with the rapidly growing use of com• puting and digital techniques in high-energy physics has been ex• plained on several occasions to the Scientific Policy Committee and the Finance Committee, and money has been reserved in the future budget forecasts for this purpose. A review of our needs has been made recently in the light of a year's experience of use of the CDC 6600 and associated equipment, and this paper describes the conclusions and the policy we propose to follow.
  • An Experimental Time-Sharing System

    An Experimental Time-Sharing System

    335 AN EXPERIMENTAL TIME-SHARING SYSTEM Fernando J. Corbato, Marjorie Merwin-Daggett, Robert C. Daley Computer Center, Massachusetts Institute of Technology Cambridge, Massachusetts summary It is the purpose of this paper to discuss The motivation for time-shared computer briefly the need for time-sharing, some of the usage arises out of the slow man-computer inter- implementation problems, an experimental time- action rate presently possible with the bigger, sharing system which has been developed for the more advanced computers. This rate has changed contemporary IBM 7090, and finally a scheduling little (and has become worse in some cases) in algorithm of one of us (FJC) that illustrates the last decade of widespread computer use. lO some of the techniques which may be employed to enhance and be analyzed for the performance In part, this effect has been due to the limits of such a time-sharing system. fact that as elementary problems become mast- ered on the computer, more complex problems immediately become of interest. As a result, Introduction larger and more complicated programs are written to take advantage of larger and faster computers. The last dozen years of computer usage have This process inevitably leads to more programm- seen great strides. In the early 1950's, the ing errors and a longer period of time required problems solved were largely in the construction for debugging. Using current batch monitor and maintenance of hardware; in the mid-1950's, techniques, as is done on most large computers, the usage languages were greatly improved with each program bug usually requires several hours the advent of compilers; now in the early 1960's, to eliminate, if not a complete day.
  • Computing at CERN Units

    Computing at CERN Units

    Inside the computer room where the CDC 6600 has served as CERN's main computer. To the left and in the background are magnetic tape Computing at CERN units. In the foreground is the console where the operators are in communication with the A review of the past, present and future of computer's operating system. On the displays computing at CERN concentrating on the large they can see which programs are running central computers which bear the brunt at that time and also the various stage which of CERN's workload. the programs going through the computer have reached. D. Ball spared a painful running-in period. The Past The growth in demand for com­ The FORTRAN era came with it. The puting at CERN continued unabated, Computing at CERN started in the problem of the mismatch of me­ amounting to a doubling each year, Autumn of 1958 with the installation of chanical input/output speed to that and this situation, plus the increasing a Ferranti Mercury, which was, for its of electronic computation soon be­ importance of computers in the work time, a modern and powerful Euro­ came apparent and a small ' satellite ' of the Laboratory, necessitated a jump pean-built computer. It was bought to computer, an IBM 1401, was installed in computing capacity preferably of provide data-handling facilities for to relieve the 709 of some of the the order of a factor of ten. The only CERN's physics programme. Its in­ drudgery. In 1962 a flying spot digit­ computer which could give this in­ stallation taught CERN that computers izer to measure bubble chamber film crease was the Control Data Corpo­ are a mixed blessing, requiring a staff was connected to the IBM 709 — the ration 6600 and, in March 1964, CERN of experts to nurse them along parti­ first use of computers on-line at placed its order.
  • F.T. Mcclure Computing Center Development

    F.T. Mcclure Computing Center Development

    ROBERT P. RICH F. T. McCLURE COMPUTING CENTER DEVELOPMENT The development of APL's F. T. McClure Comput­ Acquisition of the IBM 7090/1401 combination in ing Center has been guided by two complementary 1959 (Fig. 3) provided the Fortran language to the needs: computing power (capacity) and specific capa­ APL computing community, with access to programs bilities. written by a much larger community of Fortran users. Computing power is a measure of how much com­ Although still restricted to batch, several jobs could puting can be done per unit time, regardless of what be submitted to the system at one time, in both assem­ is being computed or the mode of man-machine in­ bly language and in Fortran. The existence of sepa­ teraction. It is measured in operations per second and rate channels made it possible for computation to has grown, since 1966, at an average annual compound proceed in parallel with input/output operations. Be­ rate of about 180/0. The growth has been impelled by ginnings were made in information retrieval and text processing during that period, and the Laboratory's 1. Growth in the staff during the early years; financial work was shifted to a separate IBM 1401. 2. The change in work habits of the staff to take The system grew to an IBM 7094 in 1962 and then advantage of increasing computer capabilities; to two 7094s in 1963. The 1401 was replaced by an IBM 3. The shift in APL programs made possible by 7040 and an IBM 1410 in response to the mentioned those capabilities (Transit, Submarine Tech­ growth in required computing power.
  • IBM 709 MANUFACTU RER IBM 709 Data Processing System International Business Machines Corporation

    IBM 709 MANUFACTU RER IBM 709 Data Processing System International Business Machines Corporation

    IBM 709 MANUFACTU RER IBM 709 Data Processing System International Business Machines Corporation Photo by International Business Machines Corporation at Point Mugu, California and one at Point Arguello, APPLICATIONS California. Land Air is the lessee, and our major Manufacturer committment is for missile test flight data reduction. This is a general purpose computer doing both scien­ In addition, we provide computing facilities for the tific computing and commercial work. The system is entire installation at Mugu (general scientific and scientifically oriented with fast internal speeds. engineering research and data processing). USA Ballistic Missile Agency Redstone Arsenal U.S.N. Pacific Missile Range Ft. Mugu Located at Computation Laboratory, Redstone Arsenal, Operated by Land Air, Inc. ALabama, the system is used for scientific and commer­ Located at the Naval Missile Faculty, Point Arguello, cial applications. California, the system is used on the main problem U. S. Army Electronic Proving Ground of range safety impact predicition in real time using Located in Greely Hall, Fort Huachuca, Arizona, sys­ FPS-l6 Radar and Cubic COTAR data. System is also tem is used in support of the tactical field army used for post flight trajectory reduction of FPS-l6 and the technical program of the departments of the radar data and for trajectory integration and analysis, U. S. Army Electronic Proving Ground. etc. U.S.N. Pacific Missile Range Ft. Mugu USN OTS China Lake, California Operated by Land Air, Inc. Located at the Data Computation Branch, Assessment Located at the Pacific Missile Range, Point Mugu, the DiVision, Test Department, the computer is used for system is used for the processing of missile test data reduction and scientific computation as related data (radar, optical, and telemetry), for real time to Naval Ordnance, Test, Development & Research applications, and for the solution of general mathe­ (l5% of computer time devoted to management data pro­ m.atical problems.
  • Copyrighted Material

    Copyrighted Material

    Index absolute summability, 348 autoregressive process adaptive mixture of t distributions, 272 vector (VAR), 365 adaptive radial-based direction sampling, auxiliary variable Gibbs sampling, 260 262 agent-based simulation, 57 backfitting, 166 AIC, 296 band-limited process, 340, 373 AIC criterion, 407 bandpass filter, 360 Akaike information criterion, 296 bandwidth, 326 aliasing, 338–340 basic structural model, 363, 365 all-pass model, 383 Bayes factor, 226 annual cycle, 361 Bayes’ theorem, 218 ant colonies, 88, 90 Bayesian estimation, 370 aperiodicity, 249 Bayesian estimation of VAR model, 294 AR(1) process, 207 benchmark, 61, 62, 65, 75, 76 ARCH test, 301 BFGS algorithm, 70 ARIMA model bias correction, 208 seasonal, 357, 364 bidirectional filter, 344 ARIMA process, 361 bilinear model, 380, 385, 391 ARMA model, 341, 377 block bootstrap, 199, 200 weak, 385 block-of-blocks bootstrap, 199, 207 ARMA process, 339, 348 block–block bootstrap, 200 artificial neural network, 85 Bonferroni inequality, 200 asymptotic convergence results, 99 bootstrap bagging, 164 asymptotic refinement, 187 bootstrap data generating process, 184, asymptotically pivotal test statistic, 187, 193 191 COPYRIGHTEDbootstrap MATERIAL DGP, 184, 193 autocovariance generating function, 341, bootstrap EDF, 184 347 bootstrap P -value, 184 partial-fraction decomposition of, double, 191 362 equal tail, 186 autocovariance matrix fast double, 192, 193 circulant, 350 symmetric, 186 Handbook of Computational Econometrics edited by D. A. Belsley, E. J. Kontoghiorghes © 2009 John Wiley &
  • LCSH Section I

    LCSH Section I

    I(f) inhibitors I-215 (Salt Lake City, Utah) Interessengemeinschaft Farbenindustrie USE If inhibitors USE Interstate 215 (Salt Lake City, Utah) Aktiengesellschaft Trial, Nuremberg, I & M Canal National Heritage Corridor (Ill.) I-225 (Colo.) Germany, 1947-1948 USE Illinois and Michigan Canal National Heritage USE Interstate 225 (Colo.) Subsequent proceedings, Nuremberg War Corridor (Ill.) I-244 (Tulsa, Okla.) Crime Trials, case no. 6 I & M Canal State Trail (Ill.) USE Interstate 244 (Tulsa, Okla.) BT Nuremberg War Crime Trials, Nuremberg, USE Illinois and Michigan Canal State Trail (Ill.) I-255 (Ill. and Mo.) Germany, 1946-1949 I-5 USE Interstate 255 (Ill. and Mo.) I-H-3 (Hawaii) USE Interstate 5 I-270 (Ill. and Mo. : Proposed) USE Interstate H-3 (Hawaii) I-8 (Ariz. and Calif.) USE Interstate 255 (Ill. and Mo.) I-hadja (African people) USE Interstate 8 (Ariz. and Calif.) I-270 (Md.) USE Kasanga (African people) I-10 USE Interstate 270 (Md.) I Ho Yüan (Beijing, China) USE Interstate 10 I-278 (N.J. and N.Y.) USE Yihe Yuan (Beijing, China) I-15 USE Interstate 278 (N.J. and N.Y.) I Ho Yüan (Peking, China) USE Interstate 15 I-291 (Conn.) USE Yihe Yuan (Beijing, China) I-15 (Fighter plane) USE Interstate 291 (Conn.) I-hsing ware USE Polikarpov I-15 (Fighter plane) I-394 (Minn.) USE Yixing ware I-16 (Fighter plane) USE Interstate 394 (Minn.) I-K'a-wan Hsi (Taiwan) USE Polikarpov I-16 (Fighter plane) I-395 (Baltimore, Md.) USE Qijiawan River (Taiwan) I-17 USE Interstate 395 (Baltimore, Md.) I-Kiribati (May Subd Geog) USE Interstate 17 I-405 (Wash.) UF Gilbertese I-19 (Ariz.) USE Interstate 405 (Wash.) BT Ethnology—Kiribati USE Interstate 19 (Ariz.) I-470 (Ohio and W.
  • IBM 7090/7094 Simulator Usage 01-Dec-2008

    IBM 7090/7094 Simulator Usage 01-Dec-2008

    IBM 7090/7094 Simulator Usage 01-Dec-2008 COPYRIGHT NOTICE The following copyright notice applies to the SIMH source, binary, and documentation: Original code published in 1993-2008, written by Robert M Supnik Copyright (c) 1993-2008, Robert M Supnik Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL ROBERT M SUPNIK BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of Robert M Supnik shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from Robert M Supnik. 1 Simulator Files.............................................................................................................3