.ifi init_plm "SIB12.2" .srv this_release_number "12.2" .srv section "3" .srv draft_date "" .srv draft "Firmware Status" .ifi l0h "FCO and Firmware Status" .ifi l1h "Firmware" The firmware identification for MR12.2 2 is "IFAD C.3". .spb 2 IFAD (Integrated Firmware and Diagnostics) tapes, are distributed to all sites having valid Field Engineering Hardware Maintenance contracts. The IFAD C.3 tape is distributed as FCO PHAFGA726. .spb 2 T&D (Test and Diagnostic) tapes, are distributed to all sites having valid Field Engineering Hardware Maintenance contracts. The T&D tape is distributed as FCO PHAFGA888, rev. B.2. .spb 2 This version of IFAD, firmware, and T&D modules has been tested and exposed on System M in Phoenix. The modules are supplied as part of the MR12.2 release and can be found in >ldd>firmware as part of the LDD_STANDARD tape. When subsequent IFAD tapes become available, it is recommended that the site use the deckfile_manager, dfm, command to load the released IFAD tape into >system_library_tandd. The firmware modules should then be moved to >ldd>firmware and a new MST tape should be generated using generate_mst. .spb 2 The MR12.2 release requires the following firmware revision levels. .spb 2 .fif .inl +5 Disc: DSC191 -- U1 DSC500 -- V1 MSP800 -- F1 Tape: MTC0500 -- V1 MTP0601 -- T1 MTP0610 -- W2 Unit Record: Common -- S2 Reader/Punch -- B2 PRU1200/1600 -- L1 .inl .fin .ifi l1h "Field Change Order List" The following list of FCOs should be thought of as a continuation of the similar list for MR12.0. Sites that are upgrading from MR12.0 will need to verify that FCOs for that release have been installed. .spb As FCOs are completed in Phoenix, they are sent out to the field sites. Some of the FCOs affect only site documentation while others may change the hardware to improve system reliability or maintainability. An example might be a change to improve the supply of cooling air to some boards so that the boards run cooler and are therefore less likely to fail. These types of FCOs are important to the long-term success of system operation. However, because these FCOs are not required to correct the results of any computer program, they are not listed in this SRB. .spb The purpose of this section is to identify those FCOs that are of utmost importance in the short term. This list includes only those FCOs needed to correct a program malfunction. .spb For those FCOs already sent to the field, the "FCO Kit Ship Date" column contains the approximate date when shipment of the FCO kits began. .spb 2 One of the column headings in the tables on the following pages is "Round Robin". The implications of a "Yes" in this column for a particular FCO are as follows: .spb .inl +5 .unl 5 1. The FCO kit includes at least one board. The new board(s) is to replace the board(s) now in the equipment. .spb .unl 5 2. Enough FCO kits are put together for about 20% of the sites that are to take part in the Round Robin. Some FCOs result in a Round Robin for all sites. Other FCOs involve a Round Robin for some sites but not for other sites. For example, two of the factors that determine whether or not a particular site takes part in a Round Robin FCO are: .spb .inl 10 .unl 5 a. The date codes of certain integrated circuit chips on a board. .spb .unl 5 b. The board construction method -- wirewrap vs. multilayer. .spb .inl 5 .unl 5 3. The set of FCO kits are sent to the first set of sites. (For the remainder of this discussion, we will follow one kit as it makes its Round Robin journey.) .spb .unl 5 4. The site installs the FCO. When the site is satisfied that the FCO is satisfactory, the site returns the old board(s) to Phoenix. .spb .unl 5 5. If there is still equipment at other sites that have not had the FCO installed, the returned board(s) is reworked, tested, and another FCO kit is assembled in Phoenix and sent to the next site. .spb .unl 5 6. Since the length of time it takes a site to install an FCO and become satisfied that it is working correctly cannot be known in advance, there is no way to predict with accuracy how long it will be until the FCO has been installed at all sites. .inl -5 .spb 2 The FCOs have been classified into the following categories: .spb 2 .inl +13 .unl 13 C_A_T_E_G_O_R_Y__1_ - The new software for this release will not run properly unless these FCOs are installed. .spb 2 .unl 13 C_A_T_E_G_O_R_Y__2_ - The new software for this release may or may not run properly if these FCOs are not installed. It is strongly recomended to have these FCOs installed to improve reliability of the system. .spb 2 .unl 13 C_A_T_E_G_O_R_Y__3_ - FCOs whose effects are program-visible, but do not fall into categories 1 or 2. Category 3 FCOs correct problems that are not uniquely related to this release. .inl .brp .fif .hbb |C_A_T_E_G_O_R_Y__1__F_I_E_L_D__C_H_A_N_G_E__O_R_D_E_R_S_||| |||| |FIELD CHANGE ORDERS VITAL TO THIS SOFTWARE RELEASE||| |||| | Est. FCO||| | Hours for||| | FCO Kit Round To Multics||| |FCO Number Board Ship Date Robin Instl Release||| |---------- ------ --------- ----- ----- -------||| .hbe .brp No category 1 changes are required for MR12.2. .hbb |C_A_T_E_G_O_R_Y__2__F_I_E_L_D__C_H_A_N_G_E__O_R_D_E_R_S_||| |||| |FIELD CHANGE ORDERS POSSIBLY NEEDED FOR THIS RELEASE||| |||| | Est. FCO||| | Hours for||| | FCO Kit Round To Multics||| |FCO Number Board Ship Date Robin Instl Release||| |---------- ------ --------- ----- ----- -------||| .hbe .brp .tlh 1 |-----DPSM CENTRAL PROCESSOR---------------------------------||| PHAFPD382 ETMCP 86 Jan No 2.1 MR12.2 Yes 1.0 .spb 2 .tlh 1 |-----INTEGRATED MULTIPLEXER UNIT (IMU)----------------------||| PHAFQJ014 WXGJA 87 Feb Yes 1.5 MR12.2 PHXFXS801 POWER 86 Dec No 1.0 MR12.2 .spb 2 .tlh 1 |-----MEMORY CONTROLLER (SCU)-------------------------------||| PHAFPX149 SCAMM 87 May No 2.8 MR12.2 Yes 1.0 .spb 2 .hbb |C_A_T_E_G_O_R_Y__3__F_I_E_L_D__C_H_A_N_G_E__O_R_D_E_R_S_||| |||| |FIELD CHANGE ORDERS INDEPENDENT OF A PARTICULAR RELEASE||| |||| | Est. FCO||| | Hours for||| | FCO Kit Round To Multics||| |FCO Number Board Ship Date Robin Instl Release||| |---------- ------ --------- ----- ----- -------||| .hbe .brp .tlh 1 |-----INTEGRATED MULTIPLEXER UNIT (IMU)---------------------||| PHAFQJ015 WXGDA/DB-1 87 Feb No 1.0/1.3 MR12.2 Yes .2 PHAFGE920/1 Power 87 Apr No 1.0 MR12.2 PHAFXS938 Diskettes 87 Aug No 1.0 MR12.2 .spb 2 .tlh 1 |-----MICROPROGRAM CONTROLLER-------------------------------||| PHAFGE920/1 Power 87 Apr No 1.0 MR12.2 PHAFBB143 UPCRA/MT8RA 87 Jul Yes .7 MR12.2 PHAFNJ059 Bkpnl/ 86 Mar No 1.4 MR12.2 WDACI/WDAMP-1 PHAFNJ063 EProms 86 Jun No 1.0 MR12.2 .spb 2 .tlh 1 |-----DISK MSU 500/501--------------------------------------||| PHAFFP911 PDMX/FFSX 86 Feb Yes .5 MR12.2 PHAFFP914 Pwr-Down 87 Jan No 1.0 MR12.2 PHAFFP915 AYMV Card 87 Aug Yes .5 MR12.2 .spb 2 .tlh 1 |-----FIPS DISK MSU 3380/3382, MSP 3880/1/4/5---------------||| PHAFFP534 Cabinet 86 Nov No 3.0 MR12.2 PHAFFP535 Power 87 Mar No 1.2 MR12.2 PHAFFP537 SQ4N Card 87 Mar Yes 1.0 MR12.2 PHAFFP538 Cabinet 87 Mar No 1.0 MR12.2 PHAFFP539 Cabinet 87 Mar No .3/.5 MR12.2 PHAFFP544 F2 Card 87 Jun Yes .5 MR12.2 PHAFFP545 Cabinet 87 Jun No 1.0 MR12.2 .spb 2 .tlh 1 |-----PRINTER PRU 1200/1600---------------------------------||| PHAFFP800 Motor Ctrl 87 Jan No .5 MR12.2 .spb 2 .tlh 1 |-----PRINTER PRU 54----------------------------------------||| XBEFL1485 Proms 86 Feb No .3 MR12.2 .spb 2 .tlh 1 |-----TAPE MTU 630------------------------------------------||| PHAFFP326 EProms 86 Jul No .5 MR12.2 .spb 2 .tlh 1 |-----FIPS TAPE MTU 8205/06/08, MTS 8205/06/08/15/16/18-----||| PHAFFP401 TC Card 86 May Yes .5 MR12.2 PHAFFP402 Cables 86 May No 1.7 MR12.2 PHAFFP403 Disk Drive 86 May No 1.0 MR12.2 PHAFFP404 CB1 Card 86 Jul Yes 2.7 MR12.2 PHAFFP405 Backpanel 86 May No 1.7 MR12.2 PHAFFP406 Cable 86 May No .5 MR12.2 PHAFFP408 Reel Hub 86 May No .7 MR12.2 PHAFFP409 Backpanel 86 May No 1.0 MR12.2 PHAFFP410 Cabinet 86 May No .5 MR12.2 PHAFFP411 EProms 86 May No .5 MR12.2 PHAFFP412 CS1 Card 86 May Yes 1.2 MR12.2 PHAFFP418 Firmware 87 Jun No 1.0 MR12.2 .spb 2 .tlh 1 |-----IFAD RELEASE C.3--------------------------------------||| PHAFGA726 Tape 86 Oct No 2.0 MR12.1 .spb 2 .tlh 1 |-----T&D RELEASE REV. B.2----------------------------------||| PHAFGA888 Tape 87 Mar No 2.0 MR12.2 .spb 2 .tlh 1 |-----MHAT MR12.0-------------------------------------------||| PHAFPD998 Tape 87 May No 2.0 MR12.1 .fif .brp ----------------------------------------------------------- Historical Background This edition of the Multics software materials and documentation is provided and donated to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. as a contribution to computer science knowledge. This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology, Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL and BULL HN Information Systems Inc. to the development of this operating system. Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970), renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture for managing computer hardware properly and for executing programs. Many subsequent operating systems incorporated Multics principles. Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. . ----------------------------------------------------------- Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without fee is hereby granted,provided that the below copyright notice and historical background appear in all copies and that both the copyright notice and historical background and this permission notice appear in supporting documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining to distribution of the programs without specific prior written permission. Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc. Copyright 2006 by BULL HN Information Systems Inc. Copyright 2006 by Bull SAS All Rights Reserved