SECTION 1 INTRODUCTION This document describes the MR12.0 package. Detailed instructions for installation of a system for the first time and upgrading to MR12.0 from an MR11.0 system constitute the major portion of this document. Future releases will require that sites be running the immediately previous release in order to migrate. Migration to the next release will require that sites be running MR12.0. No attempt is made to document features of MR12.0 other than those directly required for its installation. Software Releases prior to MR11.0 are no longer supported. All sites running pre-MR11.0 software are strongly encouraged to upgrade to MR12.0 as soon as possible. _S_I_T_E _S_U_P_P_O_R_T System Representatives who support Multics should apply for registration on the SiteSA project maintained in Phoenix on System M. The SiteSA project was created to allow sites to communicate with Multics System Support (MSS) personnel on matters of site support. MSS maintains and pays for usage on this project. Only System Representatives who support a Multics site are authorized to use the project. They are authorized to use it only for site support activities which require communication of information to MSS personnel. MSS would appreciate that the SiteSAs maintain the site's info segments in >udd>SiteSA>site_info (>udd>ssa>si). Information on maintaining these segments is in the info segment, >udd>ssa>si>site_info.info. Introduction 1-1 SIB12.0 In addition to normal telephone and Multics mail communications with MSS personnel, SiteSAs are encouraged to use the unusual_crash_log forum meeting to report any unusual problems encountered at their site. SiteSAs not familiar with forum can type "help forum" for usage information. Forum is a subsystem somewhat like the mail system in which an electronic meeting can be held. To invoke forum, type: forum >udd>ssa>sa_meeting>uclog Type ? to print a list of requests allowed by forum. Other forum meetings of interest to SiteSAs are: PATHNAME SHORT NAME --------------------------------------------- ---------- >udd>ssa>sa_meeting>install_instructions ii >udd>ssa>sa_meeting>hardware_problems hwp >udd>ssa>sa_meeting>critical_fixes fixes We would appreciate that sites as they complete installation of MR12.0 enter a transaction in the install_instructions (ii) forum meeting. This will allow other sites to see the amount of exposure the release is receiving and to communicate any problems encountered in the installation procedure. MSS also suggests, very strongly, that SiteSAs DO NOT attempt to reproduce site problems on System M which are known to crash the system at their site, cause processors to loop in ring 0, etc. Such problems should be reported via the Trouble Report system, and will be verified by MSS personnel using appropriate resources, so that System M service is not interrupted unnecessarily. Problems encountered while installing this release, or problems of a critical nature to a customer site (for a definition of critical, type: help tr.priorities) should be reported directly to MSS by mail or phone. European or Canadian sites should contact their local site support person for details on support from the Canadian, French or UK Technical Assistance Centers. Phoenix personnel include: NAME AREA USER ID PHONE George Gilcrease Multics TAC Gilcrease.TR 602/862-3591 Frank Martinson Mgr, MSS Martinson.sm 602/862-3592 Paul Farley TRs, C&F, Site Support Farley.sm 602/862-3621 Gary Johnson Sys. Integration Release Prep GJohnson.sm 602/862-3630 Note that all of the above numbers are available through HVN 862-XXXX (eg, 862-3592 for Martinson). Introduction 1-2 SIB12.0 SECTION 2 DESCRIPTION OF PACKAGE _L_I_B_R_A_R_Y _N_A_M_I_N_G _C_O_N_V_E_N_T_I_O_N_S The primary pathnames on most of the system directories are somewhat lengthy. For this document, abbreviated (added) names are used in lieu of the primary name. The following list gives the primary and abbreviated names used in this document. >daemon_dir_dir >system_library_1 >ddd >sl1 >documentation >system_library_obsolete >doc >obs >system_library_tandd >system_library_standard >firmware >sss >library_dir_dir >system_library_tools >ldd >tools >process_dir_dir >system_library_unbundled >pdd >unb >system_control_1 >user_dir_dir >sc1 >udd The system directories firmware and obs, are not included in the standard system search rules. Segments in these directories must either be accessed by absolute pathnames or by changing the system search rules via the set_system_search_rules command added to the system_start_up.ec. Package Description 2-1 SIB12.0 _C_O_N_T_E_N_T_S _O_F _M_R_1_2 _P_A_C_K_A_G_E MR12 includes this document, a set of magnetic tapes, hardcopy dump maps, and accompanying documentation. Sites not installing Multics for the first time will be able to proceed to the MR12 release from MR11.0. Sites upgrading to MR12 from MR11 refer to Section 4, sites installing Multics for the first time refer to Section 5. The instructions in each section will provide a procedure to guide a site through the installation. Documentation for some of the new features and TRs resolved in this release is contained in the directory >doc>MR12 which is part of this release. This is a total software release. It contains a complete set of all modules contained in the Multics standard system. Appendix A will list modules added, modified or deleted since MR11.0. Appendix B contains documentation of the new save and restore features within BCE. Appendix C contains an outline of the use of MTR under Multics. A set of master tapes was generated for this release and all dump maps reflect the contents of these master tapes. All tapes sent to the field are copies of the master tapes. Because of different lengths of magnetic tape reels, there may not be an exact correlation between a single tape and a dump map. These differences, if any, are minimal and occur only on those sets that are multi-reel (e.g., 12.0LISTINGS tapes). Site personnel may assure themselves of the contents of the tapes by visually matching the maps produced from the reload operations against the master dump maps supplied. Package Description 2-2 SIB12.0 _T_a_p_e__N_a_m_e_s _D_e_s_c_r_i_p_t_i_o_n 12.0EXEC Complete dump of Multics executable libraries >documentation, >obs, >sss, >tools, and >firmware. 12.0UNBUNDLED Complete dump of Multics unbundled libraries, or portion thereof, for those sites purchasing Priced Software Products. Includes all, or portions of >unbundled, >ldd>unbundled, >ldd>mcs and >system_library_3rd_party. 12.0LDD_STANDARD Complete dump of all standard library source, object, include files and info segs. 12.0LISTINGS ** Complete dump of all listings for modules compiled with the -list control argument. This includes the >ldd>listings>hardcore. 12.0MULTICS Complete Multics System Tape (MST). 12.0MISC The compout segment for this document and other supporting documentation, if any, are contained on this tape in >doc>MR12.0. Last minute changes, if any, made to software modules after generation of the above tapes is also contained on this tape. This is the last tape to be loaded. ** The loading of this set of tapes is optional. If disk space is critical, it is suggested that these tapes be used only for retrieval of specific listing segments on an individual basis. Total storage required for Hardcore listings is approximately 24,000 records. Package Description 2-3 SIB12.0 The accompanying hardcopy listings are: _L_i_s_t_i_n_g _D_e_s_c_r_i_p_t_i_o_n 12.0EXEC.DUMP.MAP Contents of the 12.0EXEC tape. 12.0UNBUNDLED.DUMP.MAP Contents of the 12.0UNBUNDLED tape (for those sites purchasing Priced Separate Software). 12.0LDD_STANDARD.DUMP.MAP Contents of the 12.0LDD_STANDARD tapes. 12.0LISTINGS.DUMP.MAP Contents of the 12.0LISTINGS tapes. 12.0MISC.DUMP.MAP Contents of the 12.0MISC tape. A detailed status of all MR12 modules contained on the Multics system tape is included on the 12.0LISTINGS tapes in the following files: _T_a_p_e__F_i_l_e__N_a_m_e _D_e_s_c_r_i_b_e_s _system_book_ MR12 hardcore modules Package Description 2-4 SIB12.0 SECTION 3 FCO AND FIRMWARE STATUS _F_I_R_M_W_A_R_E The firmware identification for MR12.0 is "IFAD C.3". IFAD (Integrated Firmware and Diagnostics) tapes, are distributed to all sites having valid Field Engineering Hardware Maintenance contracts. The C.3 tape is distributed as FCO PHAFGA726. 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 PHAFGA726. 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.0 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. The MR12 release requires the following firmware revision levels. Disc: DSC191 -- V1 DSC500 -- V1 MSP800 -- F1 Tape: MTC0500 -- V1 MTP0601 -- T1 MTP0610 -- W2 Firmware Status 3-1 SIB12.0 Unit Record: Common -- S2 Reader/Punch -- B2 PRU1200/1600 -- L1 _F_I_E_L_D _C_H_A_N_G_E _O_R_D_E_R _L_I_S_T The following list of FCOs should be thought of as a continuation of the similar list for MR11.0. Sites that are upgrading from MR11.0 will need to verify that FCOs for that release have been installed. 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. 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. 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. 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: 1. The FCO kit includes at least one board. The new board(s) is to replace the board(s) now in the equipment. 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: a. The date codes of certain integrated circuit chips on a board. b. The board construction method -- wirewrap vs. multilayer. Firmware Status 3-2 SIB12.0 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.) 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. 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. 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. The FCOs have been classified into the following categories: _C_A_T_E_G_O_R_Y__1 - The new software for this release will not run properly unless these FCOs are installed. _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. _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. Firmware Status 3-3 SIB12.0 _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 ---------- ------ --------- ----- ----- ------- ------------MICROPROGRAM CONTROLLER------------------------- PHAFXS650 WDAMP-1 85 May No 1.0 MR12.0 * Sites with SCUMM boards should contact the TAC Center for information on how to request, via FCO discrepency report, an updated SCUMN board. Firmware Status 3-4 SIB12.0 _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 ---------- ------ --------- ----- ----- ------- ------------DPSM CENTRAL PROCESSOR-------------------------- PHAFPD376 ETDCX/ETDCX1 85 Apr No 0.9/1.0 MR12.0 PHAFPD377 ETMBG 85 Apr Yes 1.0 MR12.0 PHAFPD379 ETMCP 85 Apr No-WW 1.0 MR12.0 Yes-HC 1.0 PHAFPD380 ETDCM/ETDPD 85 Apr No-WW 2.1 MR12.0 Yes-HC PHAFPD381 ETDBA 85 May No-WW 1.4 MR12.0 Yes-HC PHAFPD384 Backpanel 85 Oct No 0.9 MR12.0 ------------MICROPROGRAM CONTROLLER------------------------- PHAFTH939 MT8ER/MT8SB 85 Aug Yes 1.5 MR12.0 PHAFTH940 MT8ER/MT8SB 85 Aug Yes 1.5 MR12.0 ---------------MEMORY CONTROLLER---------------------------- PHAFMJ358 SCUMH 86 Jan Yes 1.0 MR12.0 ------------INPUT/OUTPUT MULTIPLEXER (IOM)------------------ PHAFPX955 NSAJB 85 Dec No 0.6 MR12.0 PHAFPX972/3 Termination 86 Nov No 0.5 MR12.0 PHAFXJ908 MQXJC/NSAJC 85 Dec No 0.7 MR12.0 PHAFXJ909 MQXJB/MSAJB 85 Dec No 0.6 MR12.0 PHAFXJ910 MQXJR 85 Dec No 0.6 MR12.0 PHAFXJ912 MQXJA/MQXJP 85 Dec No 1.2 MR12.0 NSAJP PHAFXW184 MQXJT 85 Jun No 0.7 MR12.0 -------------L68 CENTRAL PROCESSOR-------------------------- PHAFPG196 Termination 86 Oct No 0.3 MR12.0 Firmware Status 3-5 SIB12.0 _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 ---------- ------ --------- ----- ----- ------- ------------INPUT/OUTPUT MULTIPLEXER----------------------- PHAFQJ010 Various 86 Jul Yes 6.0 MR12.0 PHAFQJ012 WXGJD 86 Aug Yes 1.0 MR12.0 PHAFQJ013 WXGSA-1 86 Sep No 1.5 MR12.0 -----FIPS DISK DEVICES 3880, 3881, 3884, 3885-------------- PHAFFP527 Cable 86 Oct No 5.0 MR12.0 PHAFFP528 Cabinet 86 Oct No 0.7 MR12.0 PHAFFP529 Cabinet 86 Oct No 1.7 MR12.0 PHAFFP530 F2 card 86 Oct Yes 0.5 MR12.0 ------------MICROPROGRAM CONTROLLER------------------------ PHAFXS907 Power Supply 85 Jun Yes 1.5 MR12.0 ------------IFAD RELEASE C.3-------------------------------- PHAFGA726 Tape 86 Oct No 2.0 MR12.0 Firmware Status 3-6 SIB12.0 SECTION 4 INSTRUCTIONS FOR SITES UPDATING TO MR12 FROM MR11 If problems are encountered in any of the Steps listed below, return to the last step known to be successful and retry the Steps. Pay particular attention to procedure. This entire procedure was verified on the Multics System at Phoenix Computer Operations, but some hardware/software differences may exist at a particular site. In this section, two formats of text are used to indicate the typing of input into the system. This input usually is a command line, but could be data typed in response to a query from the operator console. Strings of input, and output messages of importance are indicated on separate lines. In addition, all input to the system is to be typed in lowercase, except when indicated by the occurrence of both uppercase and lowercase in the input line. User input is preceeded by an exclamation mark (!). System display output is shown as is, except when the displayed line exceeds the page margins for this document. When this occurs, the displayed line is split into two lines, with the second line indented from the first. SITES USING NSA IOM'S MUST INSURE OPTION WIOG008A-001 IS INSTALLED TO MAKE PAGED MODE I/O WORK. Instructions - Updating 4-1 SIB12.0 ___S___I___G___N___I___F___I___C___A___N___T ___C___H___A___N___G___E___S ___I___N ___T___H___I___S ___R___E___L___E___A___S___E With this release the Bootload Operating System (BOS) is no longer supported and is replaced by the Bootload Command Environment (BCE). The operation of BCE is described in detail in the Multics System Maintenance Procedures Manual, Order Number AM81. Sites should be familiar with this material prior to attempting a boot of this release. The presence of Bootload Multics will have no effect on any user's process or application. Appendix B of this document contains documentation for the save and restore features of BCE, which are new for this release. With this release the Information Multiplexor Unit (IMU) is supported. The IMU, also known as Dipper, is an IOM replacement and supports FIPS channels and some FIPS devices. Additional information on supported FIPS devices can be found in the MR12.0 System Release Bulletin (SRB). Instructions - Updating 4-2 SIB12.0 _S_T_E_P _1_: _P_R_E_-_I_N_S_T_A_L_L_A_T_I_O_N _P_R_E_P_A_R_A_T_I_O_N For this release there are no changes to any system exec_coms or report control files. The system is already prepared for installation of MR12.0. It is recommended that sites perform a SAVE using MR11.0 BOS. A double save is recommended to avoid any possible tape problems later. Due to the method by which unbundled software is dumped, normal trimming during reloading of new software does not occur. To ensure that unbundled directories are clean execute the following before shutting down MR11.0 for the last time enter admin mode and type: cwd >system_library_unbundled answer yes -bf hpdl ([files **]) cwd >library_dir_dir>unbundled>source answer yes -bf hpdl ([files **]) cwd >library_dir_dir>unbundled>object answer yes -bf hpdl ([files **]) To shut the system down and continue to the next step type: ame shutdown _S_T_E_P _2_: _I_N_S_T_A_L_L_A_T_I_O_N _T_O _B_C_E _(_E_A_R_L_Y_) _L_E_V_E_L Place the new MR12 Mult tape on any convenient tape drive. Initialize and boot the MST. Multics will prompt with: bootload_0: Booting system MR12 generated 12/15/86 0000.0 bootload_0: Enter boot tape MPC model: ! t500 Normal response to this question should be "ipc", "t610", "t601" or "t500". The system will boot the bootload tape controller, if necessary, and continue. At this time you will be asked to input the RPV location in channel, controller, device and unit number format: bootload_0: Booting t500 A 12. with mtc500 rev.v1 firmware. bootload_0: Booted tape MPC. 0000.1 announce_chwm: 371. pages used of 512. in wired environment. 0000.2 announce_chwm: 646. words used of 1024. in int_unpaged_page_tables. find_rpv_subsystem: Enter RPV data: M-> ! rpv a22 451 451 1 bce (early) 0012.0: M-> Instructions - Updating 4-3 SIB12.0 _S_T_E_P _3_: _C_H_A_N_G_E_S _T_O _C_O_N_F_I_G _D_E_C_K While at the early level of BCE configuration changes should be made. To examine and change the config deck enter the config qedx editor by typing: config 1,$p to display the entire config deck as currently saved in the "conf" partition. Particular attention should be given the IOM and new IPC cards. With this release the model field in the IOM card must be either IOM or IMU. Sites having the value NSA in this field should change it to IOM. With this release the IPC card has been added to define FIPS channels. this card is needed only for sites having FIPS channels. The format is: IPC FIPS Sites using "PARM DIRW" in the configuration should remove this parameter during the tape loading phase. This significantly speeds up the reloading of tapes. This parameter should be inserted again when the system is rebooted. After having made necessary changes exit the editor by typing "w" and "q". The "w" request will verify card syntax. The "q" request will leave the qedx editor and place the user at the bce(early) level. _S_T_E_P _4_: _I_N_S_T_A_L_L_A_T_I_O_N _T_O _B_C_E _(_B_O_O_T_) _L_E_V_E_L Continue installation of BCE by typing: bce (early) 0020.0: M-> ! bce Current system time is: Friday, June 7, 1974 13:13:46 mst Is this correct? no Enter time: M-> ! 12/22/86__13:21:30 Current system time is: Monday, December 22, 1986 13:21:30 mst Is this correct? M-> ! yes load_disk_mpcs: Disk mpc(s): mspa mspc appear not to be operating. Enter disk mpc names to be loaded, or "none" or "abort" or "all": M-> ! mspa mspc (The operator entered the names of other disk mpcs to be loaded.) Instructions - Updating 4-4 SIB12.0 hc_load_mpc: Booting channel A20 with dsc500 Revision V1. hc_load_mpc: Booting channel B20 with dsc500 Revision V1. bce (boot) 1200.5: M-> At this time, the operator must load firmware into all other controllers (i.e., not the bootload tape controller nor any disk controllers). bce is then considered to be fully initialized. _S_T_E_P _5_: _R_I_N_G_-_1 _E_N_V_I_R_O_N_M_E_N_T The system is now ready to cross into the ring-1 environment: bce (boot) 1200.5: boot Multics MR12 - 12/15/86 1201.0 est Fri. Command: At Initializer ring-1 command level, type: alv -all At this point the libraries will be reloaded. The release tapes should be reloaded in this specific sequence: EXEC, LDD_STANDARD, UNB, and MISC. To reload the libraries type: reload_system_release -nosetlvid When the system asks "Input tape label:" type: where is the reel identification specified for the next tape to be reloaded. See Section 2, "Contents of MR12 Package," for a listing of all "Tape names". Repeat this step for each library tape. When all tapes are loaded, type: standard admin _S_T_E_P _6_: _F_N_P _C_O_R_E _I_M_A_G_E_S _A_N_D _C_M_F _C_O_N_V_E_R_S_I_O_N A Multics Communications System (CS) core image is supplied in the >unbundled library, and is named "site_mcs". The "site_mcs" core image contains the basic support for DN6780 type FNPs with 64k of memory. CS core images are built using the bind_fnp command in conjunction with a bindfile describing the CS modules and Instructions - Updating 4-5 SIB12.0 configurations to be used. A copy of the site_mcs.bind_fnp can be found in >ldd>mcs>info. Sites should build their own CS core image tailored to their own FNP configuration, terminal type requirements, and use of additional separately priced FNP software modules. Sites using the default "site_mcs" core image should skip to Step 7 after ensuring the CMF image statement points to the core image now located in >unb. To build a new core image, the following procedure is suggested: Sites will need to extract the communications object segments from archives located in >ldd>mcs>object. Sites should create a virgin directory under >udd>sa>a for each new core image. The following example is for sites with the more common type Datanet and a larger memory configuration. Execute the following commands: create_dir >udd>sa>a>mcs.7.5 cwd >udd>sa>a>mcs.7.5 qx r >ldd>mcs>info>site_mcs.bind_fnp (or location of sites CS bind file) . . . make editing changes if any.. . . . w site_mcs.bind_fnp q ac x ([segs >ldd>mcs>o>*.archive -absp]) bind_fnp site_mcs -list Be sure the image statement in the CMF points to this newly created CS core image. The name of the CMF requires a suffix of "cmf". The following example assumes the CMF to be in the >udd>sa>a directory. This procedure will insure that the new CS image is used: cwd >udd>sa>a qx r CMF.cmf . . 1) Edit the image: statement to point to the new CS image. 2) Make any other changes needed. . . Instructions - Updating 4-6 SIB12.0 w CMF.cmf q cv_cmf CMF copy CMF.cdt >system_control_1>cdt -force The above procedure builds a site dependent CS core image and ensures that this image is loaded in the FNP by the answering service. _S_T_E_P _7_: _T_T_F _C_O_N_V_E_R_S_I_O_N A new standard TTF has been provided containing additional terminal types. Sites using a modified site dependent TTF should merge these changes with their modified version, and convert the TTF to its binary version. The converted binary version must then be installed to take effect. The TTF.ttf segment in >tools contains some of the more common used terminals on Multics. Sites using the default TTF for this release must execute the following commands to perform this conversion: cwd >udd>sa>a rename TTF.ttf TTF.save cp >t>TTF.ttf cv_ttf TTF install TTF.ttt Exit admin mode by typing "ame". Then issue the commands: stop_mpx a (sites with multiple FNPs execute this command for each FNP) multics load_mpx a -check (sites with multiple FNPs execute this command for each FNP) go The load_mpx command indicates on the FNP console any configuration errors if console_man is loaded and "console: yes;" is in the bind_file. If any errors are reported they should be corrected. Sites should assure the correct version number is reported the first time the FNP is booted. _S_T_E_P _8_: _A_C_L_S _A_N_D _R_I_N_G _B_R_A_C_K_E_T_S Check the ACLs for >sss>dm_admin_gate_, >sss>dm_daemon_gate_, >tools>installation_tools_, >tools>pnt_admin_gate_, >tools>pnt_login_gate_, >tools>pnt_network_gate_, >tools>pnt_priv_gate_, >sss>metering_gate_ and >sss>queue_admin_. Instructions - Updating 4-7 SIB12.0 The ACLs on these gates are as they appear on System M and should be restricted. The ACL for these gates are site dependent and should be changed to meet each site's needs. The dm_admin_gate_ and dm_daemon_gate_ should be restricted to data management administrators or daemons. The installations_tools_ gate should be restricted to system library maintainers. All persons on the ACL for metering_gate_ have access to the Multics metering data. All persons on the ACL for queue_admin_ are permitted to move absentee and daemon requests for themselves and other users to different queues. Users not on this ACL are only able to move their own requests. The Initializer must have access to queue_admin_. This capability is also dependent on extended access to the .ms segments. The various pnt__gate_ acls should be restricted to the following minimums for correct system operation: >t>pnt_admin_gate_ re *.SysDaemon.* re *.SysAdmin.* >t>pnt_fs_gate_ re *.*.* >t>pnt_login_gate_ re Initializer.SysDaemon.* re *.SysAdmin.* >t>pnt_network_gate_ re Initializer.SysDaemon.* re IMFT.Daemon.* re Card_Input.Daemon.* re *.SysDaemon.* >t>pnt_priv_gate_ re Initializer.SysDaemon.* r *.SysDaemon.* re *.SysAdmin.* _S_T_E_P _9_: _S_Y_S_T_E_M _C_L_E_A_N_U_P The system is now ready for normal operation under MR12.0. Following a reasonable period of MR12.0 operation, it is suggested that sites delete any segments created as part of this procedure. It is also recommended that sites salvage their systems and fix quota by running Salvager.SysDaemon, executing the following command: x repair salvquota > -rebuild -dcf Instructions - First Time 4-8 SIB12.0 SECTION 5 INSTRUCTIONS FOR SITES INSTALLING FOR FIRST TIME The following basic procedure must be performed when installing Multics for the first time. _S_T_E_P _1_: _P_R_E_P_A_R_A_T_I_O_N Ensure that all Multics active hardware components run error free in Multics mode using the latest T&D release. Peripheral equipment can be run in either Multics or GCOS mode and must also run error free. Carefully check the hardware configuration (port and channel assignments, mailbox switch settings, etc.) Create and verify the configuration description on paper for later input when BCE is running. Close consultation between the SiteSA and Field Engineering representative is of the utmost importance. (Refer to Section 9 and Appendix A of the Operator's Guide to Multics, Order Number GB61, for hardware switch setting information. Refer to Section 7 of the Multics System Maintenance Procedures, Order Number AM81-03, for configuration setup.) When selecting the storage unit for the RPV, select a disk unit with as few bad tracks as possible. For the MSS451s, T&Ds should be used to format and test the first disk to be used as the RPV (test 365, subtest 26). The MSS500/501s are formatted at the factory, however, selection of alternate tracks is not done at the factory. It can only be done using MTR at Multics command level. (Refer to Appendix B for an outline of how MTR runs under Multics.) Instructions - First Time 5-1 SIB12.0 _S_T_E_P _2_: _L_O_G_I_C_A_L _V_O_L_U_M_E _A_S_S_I_G_N_M_E_N_T_S Choose the logical volume assignments. Decide how many logical volumes are needed and how many physical volumes are to be in each. Most installations have the following: Logical Volume Contents root >system_control_1 >system_library_standard >system_library_tools >system_library_unbundled >system_library_auth_maint >system_library_1 >documentation >daemon_dir_dir >dumps >system_library_tandd >system_library_obsolete >system_library_3rd_party >site >lv partitions public >user_dir_dir >process_dir_dir >library_dir_dir>include ldd >library_dir_dir Other logical volumes may be set up for specific applications. The assignment decision requires the system administrator to balance the costs of seek interference and breakage against the advantages of being able to define and process logically different collections of data. Data bases used for only a few hours a day or only a few days a month are natural candidates for allocation to a separate logical volume. Breaking up the system's storage into several logical volumes also allows the site to operate without all logical volumes mounted if hardware goes down. For example, an MPC or channel might go down, halving the system's disk drive capacity. Instructions - First Time 5-2 SIB12.0 Logical volume assignments might be as follows: Logical Volume Contents root >system_library_tandd >library_dir_dir >system_library_obsolete >system_library_standard >system_library_tools >system_library_unbundled >system_library_3rd_party >daemon_dir_dir >documentation >dumps >system_library_1 >system_library_auth_maint >user_dir_dir>Daemon >user_dir_dir>SysAdmin >user_dir_dir>SysDaemon >user_dir_dir>SysMaint >site >lv partitions Mcc >user_dir_dir>Mcc Multics_Pubs >user_dir_dir>Pubs >user_dir_dir>Multics Old_Dumps >dumps>Old_dumps Public >user_dir_dir >experimental >process_dir_dir >ldd>include list_1 >library_dir_dir>listings>hard >library_dir_dir>mcs >library_dir_dir>unbundled list_2 >library_dir_dir>listings These particular assignments give a wide range of flexibility and Multics can run with only the root logical volume mounted, or with one or two of the less critical logical volumes not mounted due to unavailability of disk drives. For example, logical volumes, list_1 and list_2, can easily be demounted. This frees two disk drives to be available for use with other more critical logical volumes. Instructions - First Time 5-3 SIB12.0 Installations that wish to use the Access Isolation Mechanism (AIM) by specifying more than one access category (sensitivity level) should specify the maximum and minimum categories for one or more volumes and thus ensure that sensitive data is confined to a few packs, or that packs are not "contaminated" with information requiring special precautions. The logical volumes that hold process directory segments must be chosen. Because of the heavy usage of process directory segments, these segments should be spread over as many physical volumes as possible. One or more logical volumes may be selected to hold process directory segments, using the set_pdir_volumes command in system_start_up.ec. In the supplied system_start_up.ec, a single logical volume, named public, is selected. This command line should be changed to select a set of publicly accessible and permanently mounted logical volumes containing as many physical volumes as possible, subject to some constraints. Site maintenance personnel are responsible for ensuring there is always enough space available on the selected logical volumes to hold the process directory segments. The process directory placement algorithm causes process directory creations to be made on each logical volume in proportion to the number of physical volumes in the logical volume. Ensure that enough storage will be available. About 5% of each volume is used for the VTOC and volume map. In addition, some breakage is unavoidable. Since the system handles running out of storage without crashing, and since it is possible to add physical volumes to a logical volume dynamically, logical volumes can be defined with fewer physical volumes than their maximum anticipated size. _S_T_E_P _3_: _R_P_V _I_N_I_T_I_A_L_I_Z_A_T_I_O_N Mount the Multics System Tape (MST) on Magnetic Tape Handler (MTH) nn (nn is usually equal to 01). Mount the disk pack formatted by T&D on the drive selected to be the RPV. Initialize and boot the MST. Multics will prompt with: bootload_0: Booting system MR12 generated 12/15/86 0000.0 bootload_0: Enter boot tape MPC model: ! t500 Normal response to this question should be "ipc", "t610", "t601" or "t500". The system will boot the bootload tape controller, if necessary, and continue. At this time, the intention to cold boot is given. Multics will request the location of the rpv. Once this is done, the init_vol request loop will be entered to accept the layout of the rpv. bootload_0: Booting t500 A 12. with mtc500 rev.u1 firmware. bootload_0: Booted tape MPC. Instructions - First Time 5-4 SIB12.0 0000.1 announce_chwm: 371. pages used of 512. in wired environment. 0000.2 announce_chwm: 646. words used of 1024. in int_unpaged_page_tables. find_rpv_subsystem: Enter RPV data: M-> ! query find_rpv_subsystem: Enter RPV subsystem base channel, as Icc, or "cold". M-> ! cold find_rpv_subsystem: Booting cold will destroy all data on the RPV Are you sure that you want to boot cold? M-> ! yes find_rpv_subsystem: Enter RPV subsystem base channel, as Icc. M-> ! a22 find_rpv_subsystem: Enter RPV subsystem MPC model: M-> ! 451 find_rpv_subsystem: Enter RPV disk drive model: M-> ! 451 find_rpv_subsystem: Enter RPV drive device number: M-> ! 1 find_rpv_subsystem: RPV is a model 451 drive, number 1 on MPC A22 (Model 3), and this is a COLD boot. Is this correct? M-> ! yes Default RPV layout: (Respond "end" to use it.) Average seg length = 2.00 VTOC size = 2792 pages, 13920 vtoces. 27840 paging records. Constrained by average seg length. part hc 2792. 2500. part conf 5292. 4. part alt 38117. 141. part bos 37847. 270. part dump 35847. 2000. part log 35591. 256. part file 35336. 255. part bce 33136. 2200. request: M-> ! end These are the default partition assignments. Any changes to the default partitions or RPV parameters can be redefined by using the "startover" request in init_vol. The system installer should review the write-up of init_vol in the Multics Administration, Maintenance, and Operations Commands Manual, Order Number GB64-00, prior to the installation. Sizes for the various partitions and their locations can be modified based on the needs of the site. init_empty_root: Begin rpv initialization. This will take some time. init_empty_root: rpv initialized; 27840 records. bce (early) 0012.0: M-> The list above is based on a 451 disk drive. With the exception of some default values the script will be the same for 501, 3380, or 3381 disk units. Instructions - First Time 5-5 SIB12.0 _S_T_E_P _4_: _C_O_N_F_I_G_U_R_A_T_I_O_N Build the configuration description as follows (user input preceeded by an exclamation mark (!): ! config ! 1,$d ! a ! [User types in configuration fields as defined in the System Maintenance Procedures, Order Number AM81-03] ! \f ! w ! q Do not enter any part cards at this time, except for those partitions defined on the rpv. Also, make the root card specify only the rpv. Continue booting bce. bce (early) 0020.0: M-> ! bce Current system time is: Monday, April 29, 1985 13:13:46 mst Is this correct? no Enter time: M-> ! 04/29/85__13:21:30 Current system time is: Monday, April 29, 1985 13:21:30 mst Is this correct? M-> ! yes load_disk_mpcs: Disk mpc(s): mspa mspc appear not to be operating. Enter disk mpc names to be loaded, or "none" or "abort" or "all": M-> ! mspa mspc (The operator entered the names of other disk mpcs to be loaded.) hc_load_mpc: Booting channel A20 with dsc500 Revision V1. hc_load_mpc: Booting channel B20 with dsc500 Revision V1. bce (boot) 1200.5: M-> At this time, the operator must load firmware into all other controllers (i.e., not the bootload tape controller nor any disk controllers). bce is then considered to be fully initialized. bce (boot) 1200.5 : M-> ! boot -cold Do you really wish to boot cold and there by destroy the system hierarchy? M-> ! yes 1201.1 volume_registration_mgr_$check_volume_registration: Reregistered public LV root LVID 133353533031 (Initializer.SysDaemon.z) 1201.3 volume_registration_mgr_$check_volume_registration: Reregistered PV rpv PVID 133353533017 in LV root (Initializer.SysDaemon.z) disk_table_: New disk_table created Instructions - First Time 5-6 SIB12.0 Multics MR12 - 12/15/86 1202.0 mst Mon. Command: M-> Ignore the messages prefaced by disk_table_ and volume_registration_mgr_. _S_T_E_P _5_: _I_N_I_T_I_A_L_I_Z_I_N_G _R_O_O_T _V_O_L_U_M_E_S Initialize each new root volume except the RPV with the init_vol command. For better performance, it is advisable to place a hardcore partition (hc) on each physical volume of the Root Logical Volume (RLV). The placement of the hardcore partition on each volume must be low. The recommended size of additional partitions is 2500 records divided by the number of physical volume used. The RPV size should remain 2500 records to allow the system to boot with only an RPV mounted. For most volumes the command looks like: init_vol PV_NAME DRIVE_NAME -rlv {-special} Example: init_vol root2 dska_02 -rlv -special For those volumes that are to have partitions, or an average segment length other than the default of five records, add the optional "-special" as a third argument. The command then asks for instructions about the partition location. Hardcore partitions, for additional root volumes, should be specified as they are initialized. You may type one or more of the following: part NAME low nrec part NAME high nrec avg fff.ff list complete initialization by typing: end An example of typing the init_vol for an MSS0451/400 with an alternate partition on a RLV drive is: init_vol root2 dska_02 -rlv -special part alt high 141 (Note: 451 disk only) part hc low 625 (Example: 2500/4 root volumes) end when done type: shut Instructions - First Time 5-7 SIB12.0 _S_T_E_P _6_: _A_D_D_I_T_I_O_N_A_L _C_O_N_F_I_G_U_R_A_T_I_O_N _P_A_R_A_M_E_T_E_R_S At bce (boot) level enter the configuration deck editor by typing "config". The PART cards and ROOT card should be added to the deck. Subsequent boots divide the hardcore supervisor among all hardcore partitions. The following script is provided as an example where a root card exists in the configuration deck and a part card does not exist. Parameters of cards will vary according to the configuration of individual sites. User input is preceeded by an exclamation mark (!). bce (boot): M-> ! config M-> ! /root/ root -subsys dski -drive 1 M-> ! s/$/ -subsys dski -drive 2/p root -subsys dski -drive 1 -subsys dski -drive 2 M-> ! /part/ Search failed. M-> ! a M-> ! part bos dski 1 M-> ! part log dski 1 M-> ! part dump dski 1 M-> ! \f M-> ! w M-> ! q bce (boot) 1215.2: M-> reinit _S_T_E_P _7_: _R_E_L_O_A_D _O_F _E_X_E_C_U_T_A_B_L_E _L_I_B_R_A_R_I_E_S Do a normal boot "BOOT". While at ring-1 initializer command level load the executable libraries. This is done as follows: bce (boot): ! boot Command: M-> ! reload -nosetlvid Only the system libraries (MR12.0.EXEC) should be reloaded at this time. The -nosetlvid control argument ignores the logical volume ID on the tape when a directory is being reloaded. M-> ! shut 1230.1 shutdown complete. bce (boot) 1231.1: M-> ! boot standard (ignore the messages from sc_init_.) Multics MR12.0 - 12/23/85 1235.2 mst Mon Ready M-> ! admin admin: Entry not found. Could not retrieve admin password from the PNT to check admin password. Entering admin mode. [NOTE: This error message is repeated each time admin is entered until a password has been set.] Instructions - First Time 5-8 SIB12.0 Register and initialize all non-RLV volumes. For ease of typing, use of lower case names is recommended. Use the add_volume_registration (avr) command as in the following example: ! avr -pv pub01 -lv public -serial 233-81 -model 451 add_volume_registration: LV "public" does not exist. Do you wish to create it? M-> ! yes add_volume_registration: Registered PV "pub01" (pvid 100172223140) on new LV "public" lvid 100172223005). r 12:45 1.473 8 to create registration entries for each logical and physical volume. The registration file for the root logical volume is created automatically by the bootload. Since the default model number is 451, use the change_vol_registration command, if necessary, to set the correct value of model number on the rpv. The serial number can also be set as follows: lvr -pv rpv cvr -pv rpv -serial 233-79 -model ame Use the init_vol for the additional logical volumes as follows: init_vol pub01 dska_03 -special part alt high 141 end init_vol pub02 dska_04 -special part alt high 141 end After all physical volumes are registered and initialized, add them to the disk_table by typing the add_vol (av) command for all except the RPV: av pvname dskX_NN An example: av pub01 dska_03 At this point add all of the logical volumes by typing: alv -all Instructions - First Time 5-9 SIB12.0 _S_T_E_P _8_: _S_E_T_T_I_N_G _A_N_D _C_H_E_C_K_I_N_G _A_C_C_E_S_S The ACL for >lv should be set to "s" for all users. Setting initial ACLs for segments in the >lv directory is done from admin mode by typing: M-> ! admin M-> ! sis >lv rew *.SysAdmin rew *.SysDaemon M-> ! sa >lv s * sma *.SysAdmin sma *.SysMaint Create Access Control Segments (ACS) for each logical volume. For system public volumes, create them as follows: M-> ! create >lv>{lvname}.acs M-> ! cvr -lv {lvname} -acs >lv>{lvname}.acs M-> ! set_max_length >lv>*.acs 0 where {lvname} stands for name of each logical volume. The ACLs of these segments are interpreted to give permission to attach the logical volume (for private volumes) and permission to modify master directory control information in the MDCS (for specific logical volumes). Specific ACL entries for Initializer.SysDaemon should be deleted at this time by typing: delete_acl >lv>*.acs This is necessary because Initializer.SysDaemon always gets default access of "rw". This would prevent the Initializer from being a volume administrator by virtue of the missing "e" access. Deletion of specific access gives the Initializer the "rew" access allowed all SysDaemons. The ACL is now set so that all system administrators and all SysDaemons are volume administrators. The "e" bit controls executive access. For private volumes, the ACS is in a directory controlled by the volume owner. The ACS segment must reside in a directory on a logical volume different from the private logical volume. Instructions - First Time 5-10 SIB12.0 _S_T_E_P _9_: _S_E_T_T_I_N_G _V_O_L_U_M_E _Q_U_O_T_A Use the set_volume_quota command to give the Initializer process enough quota on each logical volume to create the necessary master directories. set_volume_quota LV_NAME QUOTA Example: set_volume_quota public 36000 The number QUOTA should be at least the total of the quotas of the directories to be created in the next step. Use create_dir to create master directories. The format of the command is: create_dir pathname -lv logical_volume -quota QQ where QQ <262144 Example: cd >library_dir_dir -lv no_backup -quota 40000 cd >library_dir_dir>include -lv public -quota 3000 The acct_start_up.ec will, in step 11, create a number of project directories and assign terminal quota if the directories do not exist. They are the following with the quota that will be assigned: >udd>SysAdmin 5000 >udd>SysAdmin>admin 2000 >udd>SysDaemon 5000 >udd>Daemon 1000 >udd>Operator 100 >udd>Terminals 10 >udd>HFED 5000 Set ACLs and additional names, as desired, on all master directories at this time. Directory quota should be set for each master directory by those sites that wish to have disk charges for directory pages included in monthly bills. Those sites not interested in implementing this feature may type "ame" and "shutdown" then skip to the next step. Instructions - First Time 5-11 SIB12.0 A directory quota of 1000 pages should be sufficient for all master directories with the exception of >udd. If udd is a master directory it is recommended that it be given a directory quota of 100000 pages. This provides enough directory quota for 100 projects at 1000 pages each. If the site has more than 100 active projects the 100000 figure should be adjusted accordingly. To set directory quota on each master directory execute the following command: set_dir_quota PATHNAME QQ This command allows a system administrator to place an arbitrary secondary storage quota for directories on a specified directory. PATHNAME is the name of a directory on which the directory quota is to be placed. -wd can be used to specify the working directory. QQ is the directory quota in 1024 word pages. If additional directory quota is required for a master directory the quota can be reset following movement of directory quota to inferior directories. Instructions for moving directory quota down to the project level is included in Step 18. To shut down do the following: ame shut _S_T_E_P _1_0_: _R_E_L_O_A_D _O_F _R_E_M_A_I_N_I_N_G _R_E_L_E_A_S_E _T_A_P_E_S Reboot Multics to ring-1 and reload the MR12.0.LDD_STANDARD, MR12.0.UNBUNDLED and optional MR12.0.LISTING tapes with the following commands: boot alv -all reload -nosetlvid The tape labeled MR12.0.MISC must be the final tape of the MR12.0 supplied set to be reloaded. Instructions - First Time 5-12 SIB12.0 _S_T_E_P _1_1_: _R_U_N_N_I_N_G _A_C_C_T___S_T_A_R_T___U_P_._E_C After all the release tapes have been reloaded cross into ring-4 by executing the following commands: standard admin [Ignore messages from admin at this time.] At this time you are ready to execute part 1 of the acct_start_up.ec. To do this type: ec >system_library_tools>acct_start_up cold F.ANSS where F.ANSS is the channel number of the hardwired Initializer terminal. F = FNP number (a-h) A = Adaptor type (h = hsla) N = Adaptor number (0-2 for hsla) SS = Decimal subchannel number of specified adaptor The string "F.ANSS" should be replaced by "otw_" if there is no hardwired terminal and the bootload console is to be used as the Initializer terminal. At this point, tapes dumped from other Multics sites can be reloaded as desired using the "reload" command with the control arguments "-noquota -notrim -nosetlvid" to avoid deletion of existing segments and resetting of quotas. If any segments are to be loaded into ring 1 then it cannot be done without exiting admin mode and rebooting to ring 1. _S_T_E_P _1_2_: _M_U_L_T_I_C_S _C_O_M_M_U_N_I_C_A_T_I_O_N_S _S_Y_S_T_E_M A Multics Communications System (CS) core image is supplied in the >unbundled library, and is named site_mcs. The site_mcs version for this release is 7.5. The site_mcs core image contains the basic support for DN6780 type FNPs with 64k of memory. The communication system core images are built using the bind_fnp command in conjunction with a bindfile describing the CS modules and configurations to be used. A copy of the site_mcs.bind_fnp can be found in >ldd>mcs>info. Sites should build their own CS core image tailored to their own FNP configuration, terminal type requirements, and use of additional separately priced FNP software modules. Sites using the default site_mcs core image should ensure the CMF image statement points to the correct default core image located Instructions - First Time 5-13 SIB12.0 in >unb. The initial CMF, which includes some sample channel entries in comments, as well as one FNP entry, should be checked. Edit this CMF to eliminate any inconsistencies with the actual configuration and add one or more entries for login channels. Sites modifying their own CS core image are required to use the GCOS Environment Simulator which is an unbundled software product. To build a new core image, the following procedure is suggested: Sites will need to extract the communications object segments from archives located in >ldd>mcs>object. Sites should create a virgin directory under >udd>sa>a for each new core image. The following example is for sites with the more common type Datanet and a larger memory configuration. Execute the following commands: create_dir >udd>sa>a>mcs.7.5 cwd >udd>sa>a>mcs.7.5 qx r >ldd>mcs>info>site_mcs.bind_fnp (or location of sites CS bind file) . . . make editing changes if any.. . . . w site_mcs.bind_fnp q ac x ([segs >ldd>mcs>o>*.archive -absp]) bind_fnp site_mcs -list Be sure the image statement in the CMF points to this newly created CS core image. The following example assumes the default CMF to be in the >udd>sa>a directory. This procedure will insure that the new CS image is used: cwd >udd>sa>a qx r CMF.cmf . . Edit the image: statement to point to the CS image. Make any other changes needed. . . w CMF.cmf q cv_cmf CMF.cmf copy CMF.cdt >sc1>cdt -force Instructions - First Time 5-14 SIB12.0 The above procedure builds a site dependent CS core image and ensures that this image is loaded in the FNP by the answering service. _S_T_E_P _1_3_: _C_O_M_P_L_E_T_E _A_C_C_O_U_N_T_I_N_G _S_T_A_R_T_U_P During this step, expect many messages, some with audible alarms, reporting that certain segments do not exist and are being created. These messages would be cause for concern during normal system operation but are to be expected during accounting start up and may be ignored. Execute the following example: ame stop_mpx a (sites with multiple FNPs execute this command for each FNP) multics load_mpx a -check (sites with multiple FNPs execute this command for each FNP) admin (any error messages displayed at this time, except hardware error messages can be ignored.) ec >tools>acct_start_up cold2 This procedure will finish accounting start up. The load_mpx command indicates on the FNP console any configuration errors if console_man is loaded and "console: yes;" is in the bind_file. If any errors are reported they should be corrected. A default start_up.ec is available for use by new Multics users when they first log in. This exec_com is executed by users who login to the system without their own start_up.ec. The segment >tools>start_up.ec was copied into >sc1 by the acct_start_up.ec. Individual sites can modify this exec_com to meet their own needs. The access for the segment should be "r *.*.*" and ring brackets of 4,5,5. To start the system up for normal service type: ame word login abs start go After typing "go" a number of messages will be returned. These messages are of the form: absentee_utility_: Entry not found. Creating new . These messages may be ignored. _S_T_E_P _1_4_: _C_H_E_C_K _G_A_T_E _A_C_L_S Instructions - First Time 5-15 SIB12.0 Type "admin" and enter the new admin password you selected. Check the ACLs for >sss>dm_admin_gate_, >sss>dm_daemon_gate_, >tools>installation_tools_, >tools>pnt_admin_gate_, >tools>pnt_login_gate_, >tools>pnt_network_gate_, >tools>pnt_priv_gate_, >sss>metering_gate_ and >sss>queue_admin_. The ACLs on these gates are as they appear on System M and should be restricted. The ACL for these gates are site dependent and should be changed to meet each site's needs. The dm_admin_gate_ and dm_daemon_gate_ should be restricted to data management administrators or daemons. The installations_tools_ gate should be restricted to system library maintainers. All persons on the ACL for metering_gate_ have access to the Multics metering data. All persons on the ACL for queue_admin_ are permitted to move absentee and daemon requests for themselves and other users to different queues. Users not on this ACL are only able to move their own requests. The Initializer must have access to queue_admin_. This capability is also dependent on extended access to the .ms segments. The various pnt__gate_ acls should be restricted to the following minimums for correct system operation: >t>pnt_admin_gate_ re *.SysDaemon.* re *.SysAdmin.* >t>pnt_fs_gate_ re *.*.* >t>pnt_login_gate_ re Initializer.SysDaemon.* re *.SysAdmin.* >t>pnt_network_gate_ re Initializer.SysDaemon.* re IMFT.Daemon.* re Card_Input.Daemon.* re *.SysDaemon.* >t>pnt_priv_gate_ re Initializer.SysDaemon.* r *.SysDaemon.* re *.SysAdmin.* Set ACLs on the >sc1>rcp directory and on the access control segments in it (.acs), to allow users to attach tape drives and any other peripherals they are allowed to use. After all ACLs are set, type: ame x repair salvquota > 2 -dcf -rebuild Instructions - First Time 5-16 SIB12.0 _S_T_E_P _1_5_: _S_A_V_E _C_H_E_C_K_P_O_I_N_T Type "logout * *" and "shutdown". After a successful shutdown, do a BCE save. For further information see >doc>ss>bce>save.info or Appendix B of this document. Use fresh tapes for the BCE save so that the results of the above steps are not lost. _S_T_E_P _1_6_: _T_A_I_L_O_R _S_Y_S_T_E_M _A_N_D _R_E_G_I_S_T_E_R _P_R_O_J_E_C_T_S Following the bce save, reboot the system for normal service by typing "boot star". The system is now ready for registration of projects and users from a SysAdmin process, such as Repair.SysAdmin, logged in from a standard terminal. The acct_start_up exec_com created default system_start_up.ec, admin.ec, iod_tables.iodt, RTMF.rtmf, and CMF.cmf segments. These segments should be tailored by the local Site SA to meet site operational and configuration requirements. _S_T_E_P _1_7_: _S_E_T_U_P _V_O_L_U_M_E _B_A_C_K_U_P_/_R_E_L_O_A_D_E_R The following instructions are necessary only for those sites that intend to use the Volume Backup/Reloader facility: The personids "Volume_Dumper", "Volume_Reloader", and "Volume_Retriever" are registered. These personids are registered on the Daemon project with the multip and daemon attributes and with a home_dir of >user_dir_dir>Daemon>Volume_Dumper. Sites using AIM must set the authorization for these personids at system_high and upgrade the home_dir at system_high. Login Repair SysDaemon, or if running in special session using the Initializer, execute the following command: ec >tools>setup_volume_reloader The error message that Volumes dm001 and dm002 are not registered should be ignored. This exec_com creates all directories, segments, and message segments necessary for running the volume dumper/reloader system. This exec_com also sets suggested access on the directories and segments created. Not all the access set is required. If a site wishes, the access created for *.SysMaint.* and *.SysAdmin.* may be removed. This exec_com resets the vtoce fields for both incremental and consolidated dumps by making a first dump pass with output to discard_. This is necessary since the first dump pass is Instructions - First Time 5-17 SIB12.0 equivalent to a complete dump on both the incremental and consolidated pass. Follow the instructions for normal use of this facility at the completion of this exec_com. Sites need a sufficient number of tapes to accommodate the entire file system and any incremental and consolidated dumps until a subsequent complete dump is taken. This is known as a reload group. It is suggested that new sites start with 100 reels of tape or a sufficient quantity to contain two complete reload groups. A single reel of tape at 6250 bpi holds approximately 26000 Multics records. _S_T_E_P _1_8_: _S_E_T_U_P _D_I_R_E_C_T_O_R_Y _Q_U_O_T_A This step is necessary only for those sites that wish to charge their user projects for disk storage used by directory pages, or to obtain a more complete disk report containing additional disk usage statistics. If directory quota is not already set on >udd execute the following commands from a SysAdmin process if udd is not a master directory: sac set_dir_quota > 120000 sac move_dir_quota >udd 100000 If udd is a master directory, then execute: set_dir_quota >udd 100000 Then execute the commands: cwd >udd move_dir_quota ([dirs **]) 1000 These commands move or set sufficient directory quota on udd for 100 projects with the suggested default project directory quota of 1000. If a site has more than 100 active projects a figure in excess of 100000 must be chosen for the initial directory quota of udd. The master.ec gives each new project a default directory quota of 1000 pages by moving 1000 pages of directory quota from udd. The system administrator should make sure there is always sufficient directory quota on udd to accommodate new projects. It is also suggested that all directories directly off the root with the exception of pdd and sl1 be given nonzero segment and directory quotas large enough to accommodate their current page usage and allowing for some growth. The purpose of this is to cause the disk report to contain complete statistical information on these directories (directories with 0 quotas are omitted from the disk report). Module Changes for MR12 5-18 SIB12.0 APPENDIX A MODULE CHANGES FOR MR12 This appendix provides information about changes to the Multics operating system on a segment basis. The following information applies to changes made to the system for the MR12 release only. This appendix is provided to help sites identify, to a segment level, changes they may have applied for emergency bug fixes or site dependent modifications to current system software. Information is catagorized as follows: new info segments (added to >doc>info unless otherwise noted) new segments new include files deleted segments modified segments Module Changes for MR12 A-1 SIB12.0 _N_E_W _I_N_F_O _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2 alm_.info if.info dmd_.info list_heap_variables.info dsl_.info mmi_.info dsmd_.info object_lib_.info emacs-history-comment.info pascal_cross_reference.info enter_abs_request_.info pascal_display.info find_bit_.info restore.info (BCE) find_char_.info save.info (BCE) heap_manager_.info set_process_audit_flags.info history_comment.info translate_bytes_to_hex9_.info Module Changes for MR12 A-2 SIB12.0 _N_E_W _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2 alm_.pl1 mrds_rst_.alm asr_abs_command_server_.pl1 msf_prelink_.pl1 bce_copy_disk.pl1 mu_db_xref.pl1 bce_ioi_post.pl1 object_lib_.pl1 bce_lock_mca.pl1 pascal_cross_reference.pl1 bce_parse_disk_spec.pl1 pascal_display.pl1 bce_save.pl1 pascal_ext_call_trap_proc_.pl1 bce_save_util_.pl1 pascal_init_fsb_trap_proc_.pl1 control_point_manager_call.pl1 pascal_symbol_.pl1 cpm_.pl1 pudef_.pl1 cpm_alm_.alm report_writer_request_table_.alm cpm_data_.cds rlm_get_count.pl1 cpm_et_.alm rlm_get_tuple_id.pl1 cpm_initialize_.pl1 rmdb_copy_relation.pl1 cpm_overseer_.pl1 rmdb_create_attribute.pl1 disk_name_pvtx.pl1 rmdb_create_db.pl1 dmd_.alm rmdb_create_descriptor.rd dsl_.alm rmdb_create_domain.pl1 dsmd_.alm rmdb_delete_all.pl1 e_internal_macros_.lisp rmdb_delete_attribute.pl1 e_macros_.lisp rmdb_delete_domain.pl1 emacs-history-comment.lisp rmdb_relations_used.pl1 enter_abs_request_.pl1 rmdb_rename.pl1 find_bit_.alm rmdb_rq_create_attribute.pl1 find_char_.alm rmdb_rq_create_domain.pl1 get_control_point_id_.alm rmdb_rq_delete_object.pl1 hcom.pl1 rmdb_rq_rename.pl1 hcom_cfix_validate_.pl1 rmdb_salvage_db.pl1 hcom_command_query_.pl1 set_process_audit_flags.pl1 hcom_default_validate_.pl1 switch_shutdown_file_system.alm hcom_parse_.rd tape_error_data.cds hcom_process_path_.pl1 translate_bytes_to_hex9_.alm hcom_process_seg_.pl1 versaterm.ctl.lisp heap_manager_.pl1 versaterm210.ctl.lisp help_rql_.pl1 vfile_relmgr_.alm if.pl1 xforum_attend_mtg_utilities.pl1 linus_opened_database.pl1 xforum_data_.cds linus_scope_manager.pl1 xforum_ent_attend_mtg_menu.pl1 linus_stifle_mrds_sub_error.pl1 xforum_get_selected_trans.pl1 list_heap_variables.pl1 xforum_help_menus.pl1 lock_mca.pl1 xforum_im_mgr.pl1 mca_attach_.pl1 xforum_personalize_menu.pl1 mca_init_.pl1 xforum_sub_attend_mtg_menu.pl1 mca_parse_.rd xmail_Review_Outgoing_.pl1 mca_tandd_.pl1 xmail_Review_Printing_.pl1 mca_util_.pl1 xmail_Review_Processing_.pl1 mdbm_util_.alm xmail_data_.cds mmi_.alm xmail_im_mgr_.pl1 xmail_rebuild_value_seg_.pl1 Module Changes for MR12 A-3 SIB12.0 _N_E_W _I_N_C_L_U_D_E _F_I_L_E_S _F_O_R _M_R_1_2 abs_request_dcls.incl.pl1 linus_lila_tokens.incl.pl1 active_connection_info.incl.pl1 login_server_messages.incl.pl1 alm_info.incl.pl1 ls_connection_message.incl.pl1 asr_abs_command.incl.pl1 ls_usage_types.incl.pl1 bce_ioi_post_area.incl.pl1 mca_area.incl.pl1 bsr_structures.incl.pl1 mca_config_file.incl.pl1 bsr_tape_data.incl.pl1 mca_constants.incl.pl1 check_star_name.incl.pl1 mca_data.incl.pl1 config_ipc_card.incl.pl1 mca_data_area.incl.pl1 cpm_control_point_data.incl.alm mca_diskette.incl.pl1 cpm_control_point_data.incl.pl1 mrds_res_attr_info.incl.pl1 cpm_create_ctrl_pt_info.incl.pl1 net_event_message.incl.pl1 cpm_ctrl_pt_meters.incl.pl1 object_lib_defs.incl.pl1 cpm_data_.incl.pl1 pascal_call_trap_info.incl.pl1 cpm_entries.incl.pl1 pascal_fsb_trap_info.incl.pl1 cpm_generate_call_flags.incl.pl1 pascal_ref_info.incl.pl1 cpm_internal_data.incl.pl1 pascal_symbol_.incl.pl1 dial_event_message.incl.pl1 rdm_msg_spec_keywords.incl.pl1 emacs-internal-macros.incl.lisp rdm_switch_types.incl.pl1 event_channel_name.incl.alm rmdb_create_attr_info.incl.pl1 event_channel_name.incl.pl1 rmdb_create_domain_info.incl.pl1 forum_meeting_list.incl.pl1 rmdb_crossref_info.incl.pl1 fs_dev_types_sector.incl.pl1 rmdb_delete_object_info.incl.pl1 gcos_ufas_record.incl.pl1 rmdb_rename_object_info.incl.pl1 hcom_data.incl.pl1 simone_operators_.incl.alm hcom_field_names.incl.pl1 system_constants.incl.pl1 hcom_query_info.incl.pl1 tape_error_interp.incl.pl1 ioi_direct_channel_dcls.incl.pl1 user_message_handles.incl.pl1 ipc_create_arg.incl.pl1 xforum_data_.incl.pl1 linus_forced_scope_info.incl.pl1 xmail_help_data_.incl.pl1 Module Changes for MR12 A-4 SIB12.0 _D_E_L_E_T_E_D _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2 BOOT.info (BOS) bos.header BOSTAP.info (BOS) bos.list CARDS.info (BOS) bos.search COLD.info (BOS) bos_common.incl.alm CONFIG.info (BOS) bos_iom_manager.incl.alm CONTIN.info (BOS) bos_page_info.incl.alm CORE.info (BOS) bos_ptw.incl.alm DELETE.info (BOS) bos_sdw.incl.alm DIE.info (BOS) bos_sstnt_man.incl.alm DMP355.info (BOS) bos_toequ.incl.alm EDIT.info (BOS) bos_tv.incl.alm FD355.info (BOS) boscal.ascii FMT.info (BOS) bosequ.incl.alm FWLOAD.info (BOS) bostap GO.info (BOS) bound_acceptance_test_ IF.info (BOS) bound_acceptance_test_.archive LIST.info (BOS) bound_acceptance_test_.s.archive LOADDM.info (BOS) bound_io_init MPCD.info (BOS) cache_print.incl.alm NLABEL.info (BOS) check_cpu_type.incl.alm PROMPT.info (BOS) conf355.incl.alm QUIET.info (BOS) config RDLABL.info (BOS) config_cards.incl.alm READY.info (BOS) configp.incl.alm RENAME.info (BOS) conv.incl.alm RESTOR.info (BOS) core RUNCOM.info (BOS) crash.ascii SAVE.info (BOS) cvadd.incl.alm TAPED.info (BOS) del_file_ TEST.info (BOS) die TIME.info (BOS) dmp355 TST3BT.info (BOS) dn355_trace_msgs.incl.alm TSTCHN.info (BOS) dump TTY.info (BOS) edit WARM.info (BOS) emacs.12.4a.sv.lisp WRITE.info (BOS) emacs_.12.4a.sv.lisp abs error.incl.alm abs_control esd absresolve.incl.alm exists acceptance_test fd355 alm_6180_ fdmp.incl.alm apnd fdump apnd_equ.incl.alm fill.incl.alm approved_routines.table fmt argmul.incl.alm fort_intrinsics.incl.pl1 auto.ascii forum_chairman_ badesd.ascii forum_edit_info.incl.pl1 badfd.ascii fw.dsc191.m191.t1 blast fw.dsc500.d500.r1 boot fw.msp800.msp8.a1 Module Changes for MR12 A-5 SIB12.0 fw.mtc500.m500.v1 punch.incl.alm fw.mtp601.m601.r1 qdisk.incl.alm fw.mtp610.m610.r2 rd355.incl.alm fw.urcmpc.u400.l1 rdclock.incl.alm fw.urcmpc.ucmn.p2 rdlabl fw.urcmpc.ucrp.b2 rdm_active_requests_ fwload readc.incl.alm get_cache.incl.alm readt.incl.alm getcon.incl.alm readtape.incl.alm getmpc.incl.alm reload_volume.info getportinfo.incl.alm restar.ascii getprt.incl.alm restor getsec.incl.alm rtb.ascii gogo.ascii runcom if (BOS) runcom_util.incl.alm intflt.incl.alm rw_match_star_name itape.incl.alm rwbulk.incl.alm label rwdev.incl.alm ld355 rwdisk.incl.alm ldcom.incl.alm rwsec.incl.alm linus_del_scope salv linus_match_star_name sav_equ.incl.alm linus_scope sav_io_buf_seg.incl.alm linus_set_scope sav_util.incl.alm loaddm save makefil.incl.alm scan.incl.alm makesdw.incl.alm search.incl.alm mpcd segname.incl.alm mrtb.ascii set_chand_ mst_boot_label setup ncopy source_test_ ndisk sstn nextline.incl.alm sstn_equ.incl.alm ngsw.ascii strip.incl.alm noboot.ascii submission_test normxt.ascii taped ntape tct_ ntape_equ.incl.alm tdump.ascii object_test_ test octwd.incl.alm time old_rebuild_object_ translate_to_hex9 old_relocate_symbol_ tryagn.ascii op_mnemonic tst3bt p1200i tstchn p300i util patch value_match_ print (BOS) vtoc_info.incl.alm proc.incl.alm write pt_equ.incl.alm xforum_attend_mtg_options ptpkg xmail_help.incl.pl1 Module Changes for MR12 A-6 SIB12.0 _M_O_D_I_F_I_E_D _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2 CONSTTYPE.incl.pascal alm_syserr_caller.pl1 CONTEXTTABLE.pascal alm_table_tool.pl1 DECLARE.pascal amu_print_text_.pl1 DECOR_TABLE.incl.pl1 analyze_det_stat_info.incl.pl1 EXPR.pascal analyze_detail_stat_.pl1 GENERE.pascal announce_chwm.pl1 GENOPER.pascal ansi_tape_io_.pl1 MODATTR.pascal any_to_any_.alm MODVARIABLE.pascal apte.incl.alm PROCSTAT.pascal apte.incl.pl1 RACINE.pascal arc_sine_.alm STANDSTAT.pascal arc_tangent_.alm STATE.pascal area_status.pl1 UNIQUE.pascal as_access_audit_.pl1 _cp_subsys_info.incl.pl1 as_add_admin_acl_.pl1 abbrev.pl1 as_data_.alm abbrev_data_.cds as_data_.incl.pl1 abs_io_.pl1 as_dump_.pl1 abs_io_expand_.pl1 as_hasp_mpx_.pl1 abs_io_v2_get_line.pl1 as_init_.pl1 abs_message_format.incl.pl1 as_mcs_mpx_.pl1 abs_request_dcls.incl.pl1 as_meter_.pl1 absentee_listen_.pl1 as_request_bump_user_.pl1 absentee_user_manager_.pl1 as_request_header.incl.pl1 absentee_utility_.pl1 as_request_note_pnt_change_.pl1 accept_fs_disk.pl1 as_request_sender_.incl.pl1 accept_messages.pl1 as_request_server_.pl1 accept_rpv.pl1 as_who.pl1 access_audit_.pl1 as_x25_mpx_.pl1 access_audit_gate_.alm asr_daemon_command_server_.pl1 access_audit_log_fault_.pl1 assign_resource.pl1 access_audit_util_.pl1 astty_.pl1 access_operations_.alm asu_.pl1 access_viol.pl1 asum_add_message_.pl1 acl.pl1 asum_read_delete_ops_.pl1 acl_commands_.pl1 attach_mpc_.pl1 act_ctl_.pl1 authenticate_device.pl1 activate.pl1 azm_display_fdump_events.pl1 add_dict_words.pl1 azm_requests_1_.pl1 add_pnotice.pl1 backup_dump.pl1 add_search_rules.pl1 backup_dump_recurse.pl1 adjust_cutoff_.pl1 backup_volume_contents.incl.pl1 admin_.pl1 bce_abs_seg.pl1 adopt_seg.pl1 bce_alert.pl1 aim_check_.alm bce_appending_simulation.pl1 alm.pl1 bce_check_abort.pl1 alm_.pl1 bce_command_processor_.pl1 alm_definitions_.pl1 bce_create_sstnt.pl1 alm_lc.incl.pl1 bce_die.pl1 alm_merge_.pl1 bce_display_disk_label.pl1 Module Changes for MR12 A-7 SIB12.0 bce_dump.pl1 config_data_dcls.incl.pl1 bce_exec_com_.pl1 config_deck_cards_.incl.pl1 bce_execute_command_.pl1 config_deck_edit_.pl1 bce_fwload.pl1 config_deck_keywords_.incl.pl1 bce_get_flagbox.pl1 config_part_card.incl.pl1 bce_get_to_command_level.pl1 config_root_card.incl.pl1 bce_list_requests_.pl1 console_server.pl1 bce_listen_.pl1 contents.pl1 bce_probe.pl1.pmac convert_date_to_binary_.rd bce_query_af.pl1 convert_dial_message_.pl1 bce_request_table_.alm convert_ec.pl1 bce_severity.pl1 copy_dump_tape.pl1 bce_shutdown_state.pl1 copy_dump_tape_write_.pl1 bce_state.pl1 copy_fdump.pl1 bce_subsystem_info_.incl.pl1 copy_mrds_data.pl1 bce_test_disk.pl1 countervalidate_label_.pl1 bind_.pl1 cpg_.pl1 bindext.incl.pl1 create_data_segment_.pl1 bisync_.pl1 create_mrds_db.pl1 bj_txte_util.pl1 create_mrds_dm_include.pl1 bjm_find_txns_after_crash.pl1 create_mrds_dsm.pl1 bk_output.pl1 create_root_vtoce.pl1 bndtbl.incl.pl1 create_rpv_partition.pl1 bootload_1.alm create_vtoce.pl1 bootload_console.alm create_wordlist.pl1 bootload_disk_io.pl1 cross_ring_io_.pl1 bootload_error.alm crzcpz_dim.pl1 bootload_faults.alm cu_.alm bootload_fs.pl1 cv_cmf.rd bootload_fs_cmds_.pl1 cv_config_card_.pl1 bootload_info.cds cv_entry_.pl1 bootload_io.alm cv_pmf.rd bootload_loader.alm cv_ptr_.pl1 bootload_qedx.pl1 cv_ttf.rd bootload_tape_fw.alm daemon_user_manager_.pl1 bootload_tape_label.alm data_type_info_.cds build_resource_desc_.pl1 data_type_info_.incl.pl1 bx_.cds date_compiled.pl1 cache_tester.pl1 date_time_.pl1 calendar.pl1 dbm_man.pl1 call_math_error_.alm dc_find.pl1 cancel_abs_request.pl1 dctl.alm canonicalize.pl1 deactivate_for_demount.pl1 check_entryname_.pl1 decevl_.pl1 check_file_system_damage.pl1 decode_link_.pl1 cm_delete.pl1 decode_runtime_value.pl1 cm_get_bci_header.pl1 define_area_.pl1 cm_postcommit_increment.pl1 definition.incl.pl1 command_processor_.pl1 definition_dcls.incl.pl1 command_query_.pl1 defops.incl.alm comptbl.incl.pl1 delete.pl1 config_.pl1 delete_message.pl1 config_data_.cds delete_volume_log.pl1 Module Changes for MR12 A-8 SIB12.0 demount_pv.pl1 dump_segment.pl1 dial_ctl_.pl1 dump_volume_.pl1 dialup_.pl1 dumper.pl1 discard_.pl1 e-define-command.incl.lisp disk_control.pl1 e-macros.incl.lisp disk_emergency.pl1 e_basic_.lisp disk_init.pl1 e_binding_table_.lisp disk_left_.pl1 e_define_command_.lisp disk_meters.pl1 e_defpl1_.lisp disk_pack.incl.alm e_interact_.lisp disk_pack.incl.pl1 e_macops_.lisp disk_reader.pl1 e_multics_files_.lisp disk_rebuild.pl1 e_multics_files_util_.pl1 disk_rebuild_caller.pl1 e_option_defaults_.lisp disk_table.incl.pl1 e_pl1_.pl1 disk_table_.pl1 e_redisplay_.lisp display_argument_list_.pl1 e_window_mgr_.lisp display_aste.pl1 eb_data_.alm display_disk_label.pl1 ect_structures.incl.pl1 display_disk_label_.pl1 edit_proj_.pl1 display_entry_point_dcl.pl1 emacs-alm-mode.lisp display_ioi_data.pl1 emacs-compilations.lisp display_mrds_db_population.pl1 emacs-fortran-mode.lisp display_mrds_dm.pl1 emacs-lisp-mode.lisp display_pl1io_error.pl1 emacs-object-mode.lisp display_pvolog.pl1 emacs.pl1 display_subsystem_usage.pl1 emacs_data.incl.alm display_time_info.pl1 emacs_data.incl.pl1 display_timers.pl1 emacs_data_.cds display_ttt.pl1 emf_et_.alm display_volume_log.pl1 enter_abs_request.pl1 display_vtoce.pl1 enter_abs_request_.pl1 dissect_object_.pl1 enter_output_request.pl1 dl_handler_.pl1 entries.pl1 dm_fast_lock_meters.pl1 entry_desc_info.incl.pl1 dm_interval_spec.incl.pl1 entry_sequence_info.incl.pl1 dm_log_.pl1 error_table_.alm dm_system_data_template_.cds event_channel_name.incl.alm dm_vu_append_simple_typed.pl1 event_channel_name.incl.pl1 dmpr_arg_reader_.pl1 exercise_disk.pl1 dmpr_finish_.pl1 expand_assign.pl1 dmpr_log_.pl1 expand_primitive.pl1 dmpr_output_.pl1 explain_doc.pl1 dn355.pl1 ext_code_generator.pl1 dn355_boot_interrupt.pl1 ext_link_.pl1 do.pl1 ext_listing_generator.pl1 double_arc_sine_.alm ext_parse.pl1 double_arc_tangent_.alm extract_msg_doc_.pl1 dpg_.pl1 extref.incl.pl1 dprint.pl1 fill_vol_extents_.pl1 dprint_.pl1 find_command_.pl1 dskdcl.incl.alm find_file_partition.pl1 dskdcl.incl.pl1 find_partition.pl1 Module Changes for MR12 A-9 SIB12.0 find_partition_.pl1 forum_trans_list.incl.pl1 find_rpv_subsystem.pl1 forum_trans_mgr_.pl1 find_runtime_symbol.pl1 forum_trans_specs_.pl1 fm_create_open_.pl1 forum_trans_util_.pl1 fm_open_by_uid_.pl1 free_store.alm fnp_multiplexer.pl1 fs_copy_util_.pl1 fnp_queue_entry.incl.pl1 fs_dev_types.incl.alm fnp_util.pl1 fs_dev_types.incl.pl1 form_link_info_.pl1 fs_get.pl1 format_disk_pack.pl1 fs_modes.pl1 format_tables.incl.pl1 fs_search.pl1 fort_cg_macros_.alm fs_standard_object_.pl1.pmac fort_converter.pl1 fs_vol_label.incl.alm fort_defaults_.pl1 fs_vol_label.incl.pl1 fort_eval_parm.pl1 fsout_vol.pl1 fort_make_symbol_section.pl1 ftp_dialup_.pl1 fort_message_table.alm gcos_queue_job_.pl1 fort_nodes.incl.pl1 general_format_parse_.pl1 fort_opt_macros_.alm general_ready.pl1 fort_optimizer.pl1 generate_def_.pl1 fort_optimizing_cg.pl1 generate_first_ref_traps_.pl1 fort_options.incl.pl1 generate_pnotice.pl1 fort_shared_vars.incl.pl1 get_block.pl1 fort_system_constants.incl.pl1 get_effective_access.pl1 fort_version_info.alm get_entry_arg_descs_.pl1 fortran_io_.pl1 get_entry_point_dcl_.pl1 fortran_job_bits.incl.pl1 get_io_segs.pl1 fortran_open_data.incl.alm get_library_segment.pl1 fortran_open_data.incl.pl1 get_pvtx.pl1 fortran_storage_.pl1 get_relinfo_.pl1 fortran_storage_manager_.pl1 get_single_ref.pl1 forum.pl1 get_temp_seg_.pl1 forum_.alm get_vol_list_.incl.pl1 forum_add_meeting.pl1 get_vol_list_.pl1 forum_admin.pl1 getbit_.pl1 forum_admin_.alm hash_defs_.pl1 forum_create.pl1 hc_dm_util.pl1 forum_data_.cds hc_dmpr_primitives.pl1 forum_error_table_.alm hc_initlzr_auxl_init_.pl1 forum_info.incl.pl1 hc_ipc.pl1 forum_input_requests_.pl1 hc_load_mpc.pl1 forum_list_meetings.pl1 hcom.pl1 forum_list_users.pl1 hcom_cfix_validate_.pl1 forum_logger_.pl1 hcom_data.incl.pl1 forum_mailer_.pl1 hcom_default_validate_.pl1 forum_misc_requests_.pl1 hcom_parse_.rd forum_open_mgr_.pl1 hcom_process_path_.pl1 forum_output_requests_.pl1 hcom_process_seg_.pl1 forum_passport.incl.pl1 help.pl1 forum_request_tables_.alm help_.pl1 forum_salvager_.pl1 help_args_.incl.pl1 forum_seg_mgr_.pl1 help_cis_args_.incl.pl1 forum_space_mgr_.pl1 help_rql_.pl1 Module Changes for MR12 A-10 SIB12.0 ibm3270_mpx.pl1 ipc_util_.pl1 ibm3780_.pl1 ipc_validate_.pl1 identify_io_channel_.pl1 kst.incl.pl1 incorporate_options_.pl1 lar_util_.pl1 indent.pl1 lg_ctl_.pl1 init_clocks.pl1 lib_args_.pl1 init_disk_pack_.pl1 lib_get_tree_.pl1 init_early_config.pl1 lib_output_node_list_.pl1 init_empty_root.pl1 lib_paged_output_.pl1 init_hardcore_gates.pl1 library_descriptor_compiler.rd init_hc_part.pl1 link_man.pl1 init_lvt.pl1 link_snap.pl1 init_partitions.pl1 link_trap_caller_.pl1 init_pvt.pl1 linkage_error_.pl1 init_root_vols.pl1 linus.pl1 init_scavenger_data.pl1 linus_assign_values.pl1 init_syserr_log.pl1 linus_close.pl1 init_toehold.pl1 linus_data_.cds init_vol_header_.pl1 linus_lcb.incl.pl1 init_volmap_seg.pl1 linus_lila_block.pl1 init_vtoc_man.pl1 linus_lila_build_expr_tab.pl1 initialize_process_.pl1 linus_lila_get_token.pl1 initiate.pl1 linus_list_scope.pl1 initiate_.pl1 linus_list_values.pl1 install.pl1 linus_open.pl1 install_ttt_.pl1 linus_options.pl1 insym.incl.pl1 linus_rq_table_.alm int_link_.pl1 linus_scope_manager.pl1 interpret_link_.pl1 linus_store.pl1 io_chnl_util.pl1 list.pl1 io_config_init.pl1 list_as_requests.pl1 io_error_summary.pl1 list_frame_args_.pl1 io_log_status_info.cds list_help.pl1 io_reconfig.pl1 list_init_.pl1 ioa_.pl1 list_partitions.pl1 ioam_.pl1 list_pnotice_names.pl1 ioi_assignment.pl1 list_tape_contents.pl1 ioi_config.pl1 list_vols.pl1 ioi_data.incl.pl1 load_ctl_.pl1 ioi_device.pl1 load_disk_mpcs.pl1 ioi_init.pl1 load_mpc.pl1 ioi_masked.pl1 load_mst.pl1 ioi_page_table.pl1 load_system.pl1 ioi_set.pl1 lock.pl1 ioi_suspend_devices.pl1 lock_volmap.alm ioi_verify_lock.pl1 log_read_.pl1 ioi_wire.pl1 log_wakeup_.pl1 ioi_workspace.pl1 logical_volume_manager.pl1 iom_connect.alm logout.pl1 iom_data_init.pl1 lstman_.pl1 ipc_.alm lv_request_.pl1 ipc_fast_.pl1 mail.pl1 ipc_real_.pl1 mail_format.incl.pl1 Module Changes for MR12 A-11 SIB12.0 mail_system_.alm mrds_dsl_delete.pl1 mail_system_r2_tv_.alm mrds_dsl_dl_fscope.pl1 make_bindmap_.pl1 mrds_dsl_gen_srch_prog.pl1 make_bound_object_map_.pl1 mrds_dsl_get_population.pl1 make_defs_.pl1 mrds_dsl_init_res.pl1 make_sdw.pl1 mrds_dsl_modify.pl1 makeknown_.pl1 mrds_dsl_open.pl1 makestack.pl1 mrds_dsl_optimize.pl1 match_star_name_.pl1 mrds_dsl_ready_all.pl1 mc_tty_.pl1 mrds_dsl_retrieve.pl1 mca_attach_.pl1 mrds_dsl_select_clause.pl1 mca_data.incl.pl1 mrds_dsl_set_fscope.pl1 mca_parse_.rd mrds_dsl_set_scope.pl1 mca_util_.pl1 mrds_dsl_store.pl1 mcs_echo_neg.incl.pl1 mrds_dsl_translate.pl1 mcs_echo_neg_sys.incl.pl1 mrds_error_.alm mdbm_comp_val_list.incl.pl1 mrds_finish_transaction.incl.pl1 mdbm_db_model.incl.pl1 mrds_rmdb_ctl.incl.pl1 mdbm_file_model.incl.pl1 mrds_rst_.alm mdbm_file_model_init.incl.pl1 mrds_rst_create_db.pl1 mdbm_users.incl.pl1 mrds_rst_index_handler.pl1 mdbm_util_.alm mrds_rst_semantics.pl1 mdx.pl1 mrds_select_list.incl.pl1 memo.pl1 mrds_start_transaction.incl.pl1 memo_get_.pl1 msa_manager_.pl1 memo_process_memos_.pl1 mseg_check_access_.pl1 memo_repeat_.pl1 mseg_fs_interface_.pl1 merge_volume_log.pl1 mseg_index_.pl1 message_facility_.pl1 mseg_mbx_ms_gate_target_.pl1 message_status.pl1 msf_manager_.pl1 message_table_.alm msg_facility_mailbox.incl.pl1 mexp_.pl1 mtape_mount_cntl_.pl1 mlsys_data_.cds mtdsim_.pl1 mlsys_fips98_message.incl.pl1 mu_retrieve.pl1 mlsys_internal_data.incl.pl1 mu_sec_make_res.pl1 mlsys_mailbox_mgr_.pl1 mu_temp_segments.pl1 mlsys_message.incl.pl1 multiplexer_mgr_.pl1 mlsys_misc_utils_.pl1 mus_get_att_names.pl1 mlsys_nit_interface_.pl1 new_sthedr_.alm mlsys_psp_.pl1 new_user.pl1 mlsys_transmit_.pl1 object_.alm monitor_sys_log.pl1 object_link_dcls.incl.pl1 monitor_sys_log_info_.incl.pl1 objnfo.incl.pl1 move_non_perm_wired_segs.pl1 oc_data.incl.pl1 mrds_data_.cds oc_info.incl.pl1 mrds_dbcb.incl.pl1 ocd_.pl1 mrds_dm_display.pl1 ocdcm_.pl1 mrds_dm_display_cmdb.pl1 octevl_.pl1 mrds_dm_display_history.pl1 online_355_dump_.pl1 mrds_dm_display_info.incl.pl1 opc_reconfig_options.incl.pl1 mrds_dsl_close.pl1 optimized_procedures.alm mrds_dsl_compile.pl1 pa_process_arguments.pl1 mrds_dsl_define_temp_rel.pl1 page_error.alm Module Changes for MR12 A-12 SIB12.0 pakbit_.pl1 pnotice_source_info.incl.pl1 parse_bindfile_.rd pnotice_target_info.incl.pl1 parse_resource_desc_.pl1 post_purge.alm partition_io.pl1 postp1_.pl1 pascal.pl1 postp2_.pl1 pascal_area_management_.pl1 print.pl1 pascal_build_object.pl1 print_data_.pl1 pascal_call_trap_info.incl.pl1 print_link_info.pl1 pascal_compiler_id.cds print_pdt.pl1 pascal_context_.incl.pl1 print_sys_log.pl1 pascal_context_table.incl.pl1 print_text_.pl1 pascal_create_tables.pl1 print_wordlist.pl1 pascal_cross_reference.pl1 priv_x25_mpx.pl1 pascal_display.pl1 prlst_.pl1 pascal_display_file_value.pl1 probe_assign_value_.pl1 pascal_display_text.pl1 probe_get_value_.pl1 pascal_error_table_.alm probe_info_requests_.pl1 pascal_errors_.pl1 probe_invoke_.pl1 pascal_ext_call_trap_proc_.pl1 probe_listen_.pl1 pascal_fsb.incl.pl1 probe_print_arglist_.pl1 pascal_fsb_trap_info.incl.pl1 probe_print_pascal_.pl1 pascal_gen_entry_point.pl1 proj_usage_report.pl1 pascal_gen_ext_variable.pl1 prtdim_attach.pl1 pascal_indent.pl1 prwrd_.pl1 pascal_init_fsb_trap_proc_.pl1 purge_volume_log.pl1 pascal_io_.pl1 putout_.pl1 pascal_io_close_subroutines_.pl1 pvname_to_pvtx_.pl1 pascal_operator_names_.alm pvte.incl.alm pascal_operators_.alm pvte.incl.pl1 pascal_operators_statics_.cds pxss.alm pascal_ops_statics.incl.pl1 rcp_access_kernel_.pl1 pascal_ref_info.incl.pl1 rcp_attach_.pl1 pascal_stack_frame.incl.pl1 rcp_attach_lv_.pl1 pascal_symbol_.incl.pl1 rcp_authenticate_device_.pl1 pascal_symbol_.pl1 rcp_check_attach_.pl1 pascal_symbol_node.incl.pl1 rcp_com_seg.incl.pl1 pass1_.pl1 rcp_compute_bracket_mode.pl1 pass2_.pl1 rcp_compute_raw_mode.pl1 pc_abs.pl1.pmac rcp_control_.pl1 pc_check_tables_.pl1 rcp_data.incl.pl1 pc_deposit.pl1 rcp_detach_.pl1 pc_recover_sst.pl1 rcp_detach_lv_.pl1 pdir_volume_manager_.pl1 rcp_device_info.incl.pl1 peruse_crossref.pl1 rcp_device_info_.pl1 pfm_utils_.pl1 rcp_device_info_structs.incl.pl1 picture.pl1 rcp_device_types.incl.pl1 pit.incl.pl1 rcp_disk_.pl1 pl1_operator_names_.alm rcp_disk_info.incl.pl1 pl1_version.cds rcp_get_scratch_volume_.pl1 pnotice_language_info_.cds rcp_init.pl1 pnotice_language_info_.incl.pl1 rcp_list.pl1 pnotice_paths.incl.pl1 rcp_match_.pl1 pnotice_paths_.pl1 rcp_message_.pl1 Module Changes for MR12 A-13 SIB12.0 rcp_printer_info.incl.pl1 rlm_get_count.pl1 rcp_reserve_.pl1 rlm_put_tuple.pl1 rcp_resource_types.incl.pl1 rlm_unimplemented_entries.pl1 rcp_ring1_init_.pl1 rmdb_add_rmdb_history.pl1 rcp_tape_.pl1 rmdb_create_index.pl1 rcp_tape_survey_.pl1 rmdb_create_relation.pl1 rcp_unload_.pl1 rmdb_delete_index.pl1 rcprm_journalize_.pl1 rmdb_delete_relation.pl1 rdc_end_.incl.pl1 rmdb_execute_undo.pl1 rdisk_.pl1 rmdb_history_entry.incl.pl1 rdm_data_.cds rmdb_ready_db.pl1 rdm_message_mark_mgr_.pl1 rmdb_relmgr_entries.incl.pl1 rdm_msg_requests_.pl1 rmdb_rq_create_relation.pl1 rdm_request_tables_.alm rmdb_rq_delete_relation.pl1 read_disk.pl1 rmdb_rq_free_db.pl1 read_disk_label.pl1 rmdb_rq_ready_db.pl1 real_initializer.pl1.pmac rmdb_rq_tb_.alm reassign_work_classes_.pl1 run_.pl1 rebuild_object_.pl1 runtime_symbol_info_.incl.pl1 rebuild_pvolog.pl1 runtime_symbol_info_.pl1 reclassify.pl1 rw_options.pl1 reconfigure.pl1 salv_check_vtoce_.pl1 record_to_vtocx.pl1 salv_dir_checker_.pl1 recover_volume_log.pl1 salv_directory.pl1 reduction_compiler_.rd salvage_dir.pl1 regenerate_all_links_.pl1 salvage_pv.pl1 relation_manager_.alm save_dir_info.pl1 reload_volume_.pl1 sc_admin_command_.pl1 reloader.pl1 sc_init_.pl1 relocate_symbol_.pl1 sc_request_table_.alm reset_external_variables.pl1 scavenge_vol.pl1 resource_usage.pl1 scavenge_volume.pl1 restructure_mrds_db.pl1 scavenger.pl1 retrieve_from_volume_.pl1 scs_and_clock_init.pl1 retriever.pl1 search_ast.alm return_to_user.alm seg_fault.pl1 retv_data_.incl.pl1 segment_mover.pl1 retv_vol_control_.pl1 segnfo.incl.alm ring_0_peek.pl1 segnfo.incl.pl1 ring_alarm.pl1 send_mail_.pl1 rldr_arg_reader_.pl1 send_message.pl1 rldr_check_pvol_.pl1 set.pl1 rldr_data_.incl.pl1 set_disk_table_loc.pl1 rldr_finish_.pl1 set_ext_variable_.pl1 rldr_input_.pl1 set_fortran_common.pl1 rldr_label_.pl1 set_lock_.pl1 rldr_output_.pl1 set_sys_audit_thresholds_.pl1 rldr_report_.pl1 set_time_default.pl1 rldr_volume_map_.pl1 set_volume_log.pl1 rldr_vtoc_buffer.incl.pl1 shutdown.pl1 rldr_vtoc_buffer_.pl1 shutdown_file_system.pl1 rldr_vtoc_header_.pl1 simone_operators_.incl.alm rlm_create_relation.pl1 sort_seg.pl1 Module Changes for MR12 A-14 SIB12.0 sort_seg_.pl1 tc_input.pl1 special_messages_.pl1 tc_request.pl1 ssu_info_mgr_.pl1 tedcheck_entryname_.pl1 ssu_request_processor_.pl1 tedhelp_.pl1 ssu_request_tables_.alm temp_mgr_.pl1 ssu_requests_.alm term_.pl1 stack_frame.incl.alm terminate_file_.pl1 stack_frame.incl.pl1 terminate_proc.pl1 stack_header.incl.alm test_dcw.pl1 stack_header.incl.pl1 test_tape.pl1 star_.pl1 time_defaults_.alm start_cpu.pl1 time_defaults_.incl.pl1 start_dump.pl1 time_info_.cds status_.pl1 timer_manager_.pl1 status_for_backup.incl.pl1 timer_manager_schedule.incl.pl1 std_descriptor_types.incl.alm tm_abandon.pl1 std_descriptor_types.incl.pl1 tm_abort.pl1 stock.alm tm_cleanup.pl1 stock_man.pl1 tm_commit.pl1 stop_cpu.pl1 tm_user_shutdown_real.pl1 strm_hash_.pl1 tmdb.incl.pl1 structure_library_2_.cds toehold.alm substr.pl1 toehold_save_dcls_.incl.alm suffix_forum_.pl1 toehold_save_dcls_.incl.pl1 summarize_sys_log.pl1 tolts_device_info_.pl1 sus_signal_handler_.pl1 trace_entrypoints_.pl1 sweep_pv.pl1 transaction.pl1 syserr_log_man_.pl1 trim_wordlist.pl1 syserr_seg_manager.pl1 trusted_path_flags.incl.pl1 system_control_.pl1 tty_access_class.incl.pl1 system_info_.pl1 tty_dump.pl1 system_link_init_info.incl.pl1 tty_index.pl1 system_link_names.incl.pl1 tty_interrupt.pl1 system_privilege_.alm tty_modes.pl1 system_startup_.pl1 turn_on_mc_.pl1 ta_reconstruct_table_.pl1 tutorial.pl1 tape_ansi_attach_.pl1 unpopulate_mrds_db.pl1 tape_ansi_mount_cntl_.pl1 up_mgt_.pl1 tape_ansi_parse_options_.pl1 up_pdt_.pl1 tape_ansi_tape_io_.pl1 up_rtdt_.pl1 tape_ioi_io.pl1 up_sat_.pl1 tape_ioi_wks_man.pl1 up_sysctl_.pl1 tape_mult_.pl1 upd_doc_task_.pl1 tape_mult_close_.pl1 update_seg.pl1 tape_mult_detach_.pl1 update_vtoce.pl1 tape_mult_labeler_.pl1 user.pl1 tape_mult_modes_.pl1 user_info_.pl1 tape_mult_open_.pl1 user_table_entry.incl.pl1 tape_mult_parse_.pl1 v2forum_mgr_tv_.alm tape_mult_read_.pl1 vacate_pv.pl1 tape_mult_util_.pl1 validate_cpu_card.pl1 tape_mult_write_.pl1 validate_info_seg.pl1 tape_reader.pl1 value_.pl1 Module Changes for MR12 A-15 SIB12.0 varevl_.pl1 xforum_spy.incl.pl1 verify_dump_volume.pl1 xforum_status_.pl1 verify_label_.pl1 xforum_trans_.pl1 verify_lock.pl1 xforum_user_profile.pl1 vm_vio.pl1 xforum_validate_trans_spec_.pl1 volmap.alm xforum_window_mgr.pl1 volmap_page.alm xmail.pl1 volmap_util.pl1 xmail_Consult_Files_.pl1 volume_cross_check.pl1 xmail_Executive_Mail_.pl1 volume_registration_cmds_.pl1 xmail_Mail_File_Maint_.pl1 volume_registration_mgr_.pl1 xmail_Process_Mail_.pl1 vrm_lock_.pl1 xmail_Review_Defaults_.pl1 vrm_put.pl1 xmail_Send_Mail_.pl1 vt1xx_keys_.lisp xmail_data.incl.pl1 vtoc_buffer.incl.alm xmail_dir_manager_.pl1 vtoc_buffer.incl.pl1 xmail_discard_file_.pl1 vtoc_buffer_meters.pl1 xmail_display_help_.pl1 vtoc_interrupt.pl1 xmail_display_msgs_.pl1 vtoc_man.pl1 xmail_dprint_mlist_.pl1 vtoc_pathname.pl1 xmail_dprint_msgs_.pl1 vtoce_stock_man.pl1 xmail_dyn_menu_.pl1 vtocx_to_record.pl1 xmail_emacs_ext_main_.lisp where.pl1 xmail_emacs_ext_mlist_.lisp where_doc.pl1 xmail_err_.alm window_.pl1 xmail_file_msgs_.pl1 window_io_.pl1 xmail_forward_msg_.pl1 window_io_attach_data_.incl.pl1 xmail_get_choice_.pl1 window_io_iox_.pl1 xmail_help_infos.incl.pl1 wioctl_.pl1 xmail_im_mgr_.pl1 wired_shutdown.pl1 xmail_list_msgs_.pl1 wkp_signal_handler_.pl1 xmail_multics_mode_.pl1 xforum.pl1 xmail_prepare_msg_.pl1 xforum_create_menu_.pl1 xmail_print_.pl1 xforum_default_fkeys_.pl1 xmail_process_user_msg_.pl1 xforum_dyn_menu_.pl1 xmail_prompts.incl.pl1 xforum_emacs_ext_.lisp xmail_reply_msg_.pl1 xforum_find_path_.pl1 xmail_responses.incl.pl1 xforum_format_.pl1 xmail_select_file_.pl1 xforum_help_.pl1 xmail_select_msgs_.pl1 xforum_help_line_.pl1 xmail_send_msg_.pl1 xforum_im_mgr.pl1 xmail_sw_.pl1 xforum_list_meetings_.pl1 xmail_undelete_msgs_.pl1 xforum_main_options.pl1 xmail_update_mlist_.pl1 xforum_meeting_info.incl.pl1 xmail_value_.pl1 xforum_multics_mode.pl1 xmail_window_manager_.pl1 Module Changes for MR12 A-16 SIB12.0 APPENDIX B BOOTLOAD MULTICS (BCE) MR12 completes implementation of the final phase to initialization known as the Bootload Command Environment (BCE). This release introduces a save and restore capability within BCE. Multics should now be operated without BOS which is not supported in MR12. However, capabilities have been left in BCE to allow BOS to operate, should a site feel a strong desire to do so. No BOS tape is shipped with MR12 and those sites deciding to continue use of BOS must use their MR11 BOS tape. We strongly recommend all sites no longer use BOS. The intent of this appendix is to describe the new save and restore commands now available within BCE. Information pertaining to the rest of BCE can be found in: Title: Multics System Maintenance Procedures Order No.: AM81-03 Section: 6 Title: Operator's Guide to Multics Order No.: GB61-01 Section: 11, 12, 13 Title: Multics Administration Maintenance and Operations Commands Order No.: GB64-00 Section: 9 Title: MR11.0 System Installation Bulletin (SIB) Section: Appendix A _B_C_E _C_O_M_M_A_N_D _I_N_F_O_R_M_A_T_I_O_N Information on two BCE commands is provided here since the help command is not available at BCE level. Bootload Multics (BCE) B-1 SIB12.0 _s_a_v_e _c_o_m_m_a_n_d The BCE save command has the following syntax: save {-set} CF_1 {... CF_N} {-set CF_1 {... CF_N}} {-restart_set CF_1 {... CF_N}} Function: used to save the contents of physical volumes on tape. It can be used only at BCE (boot) command level. Arguments: CF_1 {... CF_N} defines the name of a control file or set of control files that will makeup a save set. See "List of control file requests" below. At least one and up to 32 control file names may be defined per save. A control file cannot be specified multiple times for a given set, but can be specified in more than one set. This can be used to save a set of volumes to several sets of tapes at one time. Control arguments: -set used to prefix a set of control file names. The first set of control files do not require this prefix, but it is acceptable. Up to four control file sets may be defined. This may be used in combination with the -restart_set control argument. -restart_set, -restart, -rt used to prefix a set of control file names that are to be restarted. This may be used in combination with the -set control argument. List of control file requests: tape_set [tape_set_name], ts [tape_set_name] where "tape_set_name" is the name of the collection of tapes that are to be used for the save. The name can be up to 32 characters. There must be one of these requests per set. Names might be defined by the color of the tape reel (e.g. the "blue" set or the "red" set). This name becomes part of the tape label of each tape and is checked during a restore. This name will also appear in parenthesis after the program name in all output messages. tape_device [tape_device] {density}, td [tape_device] {density} where "tape_device" is the standard device identifier (i.e. Bootload Multics (BCE) B-2 SIB12.0 tapa_05) and "density" is in the form "d=NNNN", "den=NNNN", "-density NNNN", "-den NNNN" or "-d NNNN". The default density will be 6250 bpi. The order the devices are entered defines the sequence for using them. Up to 16 devices can be defined per save set. physical_volume [pv_name] [disk_device] {-all}, pv [pv_name] [disk_device] {-all} where "pv_name" is the name of the physical volume to be saved. The "disk_device" would be the standard name "dska_02" or "dske_02c" for sub-volumes. The "-all" argument specifies that all the vtoc and paging records should be saved, instead of just saving the paging records that are in use. This also occurs if the volume requires salvaging. The "-all" arg has no meaning while doing a restore. Up to 63 volumes can be saved per set. partition [pv_name] [disk_device] [part_name] {... part_name}, part [pv_name] [disk_device] [part_name] {... part_name} where "pv_name" and "disk_device" are as described in the "pv" request. "part_name" is the name of the partition to be saved or "-all" to save all the defined partitions. The RPV partition "bce" or any "hc" or "alt" partitions will not be allowed to be saved. If the RPV partitions "conf", "file" or "log" are not specified, when saving the RPV, a message will be displayed that will state that they are not being saved, just in case the operator really wishes to have them saved. Up to 7 partitions may be defined per volume. Up to 64 partitions may be defined per save set. control_file [control_file], cf [control_file] where "control_file" defines another control file to be examined. This enables control files to be linked together. For instance ONE control file could define all the tape devices for the save. The other control files could be broken down into logical volumes that only reference the tape device control file and then define the physical volumes. Up to 32 control file names may be defined per save. Notes on control file requests: Only one request may be given per line. Any lines in a control file that begin with /, & or " are treated as comments. All white space prior to a request in a line is trimmed. Partitions on a physical volume can be saved without having to save the vtoc and paging regions by only defining a partition request. The control files can be edited using the BCE qedx request, or edited while the system is running and updated in the file partition by either using bootload_fs or regeneration of the MST. Bootload Multics (BCE) B-3 SIB12.0 The following is an example of three control files used for the first set of a three set save of a system using the bce request: save part1 -set part2 -set part3 Contents of control file "part1": tape_set part1 control_file tape1 control_file root Contents of control file "tape1": tape_device tapc_01 -den 6250 tape_device tapc_02 -den 6250 Contents of control file "root": pv rpv dska_16 part rpv dska_16 conf file log dump pv root2 dska_08 pv root3 dska_23 pv root4 dska_13 pv root5 dska_07 pv root6 dska_11 pv root7 dska_20 pv phx01 dska_10 Notes on save: When a save set is complete it is necessary to write one last tape, called the "Info" tape, that will contain information used during a restore to quickly locate the tapes that items are on. Notes on operator interrupts: A save can be interrupted by use of the console "request" key. When depressed while a save is in progress, the message "save: Abort request:" will appear. The operator will be required to input one of the following responses. no, n This causes the program to ignore the request and resume the save. abort This causes the program to abort the entire save and return to BCE command level. restart TAPE_SET This allows the operator to restart the specified TAPE_SET, using its current tape device. The operator is then required to mount the "restart" tape on the device, which is either the Bootload Multics (BCE) B-4 SIB12.0 last good tape written or the current tape (as long as the tape label has been written). Once the SET has been restarted, the remaining SETs will continue operation. stop TAPE_SET This causes the program to abort the specified TAPE_SET, by marking it complete, and resume the save of the other sets. help, ? This causes the program to display the above possible responses, with a small description of each. Notes on tape error recovery: During a save there are times when errors occur which require special handling. Retries of write errors are done by doing a backspace and erase followed by the original write. If unable to write the data after eight retries the error becomes unrecoverable. When an unrecoverable error occurs a message will be displayed that shows the error interpreted in english, with detailed status in hex if required. The operator will be queried as to the course of action that the program should take. Listed below is an example error output and the possible responses and their meanings. save(blue): Device Attention, Handler check on tapa_12. detailed status: 20 8C 2B 6D 0A 01 16 00 00 16 48 87 24 18 06 00 00 0C 00 00 08 08 80 00 00 00 save: Action: abort This causes the program to abort the entire save and return to BCE command level. retry, r For errors that are retryable this will force the retry process to be redone. It is invalid for non-retryable errors. stop_set, stop This will cause this SET to be aborted, but all other SETs will continue. restart_set, restart, rt This allows the operator to restart this SET, using the current tape device. The operator is then required to mount the "restart" tape on the device. Once the SET has been restarted, the remaining SETs will continue operation. remove_device_from_set, remove Works like the "restart_set" request above, but removes the current tape device from the SET and sequences to the next device before going through the restart process. This is not Bootload Multics (BCE) B-5 SIB12.0 a valid response if this is the only tape device left in the SET. help, ? This causes the program to display the above possible responses, with a small description of each. _r_e_s_t_o_r_e _c_o_m_m_a_n_d The BCE restore command has the following syntax: restore {-set} CF_1 {... CF_N} {-set CF_1 {... CF_N}} {-restart_set CF_1 {... CF_N}} or: restore -display_info_tape TAPE_DEVICE The restore command is used to restore the contents of physical volumes from tape. It can be used only at the BCE (boot) command level. This command has the following arguments: CF_1 {... CF_N} defines the name of a control file or set of control files that will makeup a restore set. See "List of control file requests" below. At least one and up to 32 control file names may be defined per restore. TAPE_DEVICE defines the device which should be used to read the "Info" tape (e.g. tapa_01). The restore command accepts the following control arguments: -display_info_tape, -dit used to display the information contained on the "Info" tape, which is the last tape written as part of the save process. This argument should not be used in combination with any other control arguments. -set used to prefix a set of control file names. The first set of control files do not require this prefix, but it is acceptable. Up to four control file sets may be defined. This may be used in combination with the -restart_set control argument. -restart_set, -restart, -rt used to prefix a set of control file names that are to be Bootload Multics (BCE) B-6 SIB12.0 restarted. This may be used in combination with the -set control argument. List of control file requests: tape_set [tape_set_name], ts [tape_set_name] where "tape_set_name" is the name of the collection of tapes that are to be used for the restore. The name can be up to 32 characters. There must be one of these requests per set. Names might be defined by the color of the tape reel (e.g. the "blue" set or the "red" set). This name is part of the tape label and is checked during at each tape mount. This name will also appear in parenthesis after the program name in all output messages. tape_device [tape_device] {density}, td [tape_device] {density} where "tape_device" is the standard device identifier (i.e. tapa_05) and "density" is in the form "d=NNNN", "den=NNNN", "-density NNNN", "-den NNNN" or "-d NNNN". The density is only needed during a save. During a restore the save tape will define the density. The order the devices are entered defines the sequence for using them. Up to 16 devices can be defined per restore set. physical_volume [pv_name] [disk_device], pv [pv_name] [disk_device] where "pv_name" is the name of the physical volume to be restored. The "disk_device" would be the standard name "dska_02" or "dske_02c" for sub-volumes. Up to 63 volumes can be restored per set. partition [pv_name] [disk_device] [part_name] {... part_name}, part [pv_name] [disk_device] [part_name] {... part_name} where "pv_name" and "disk_device" are as described in the "pv" request. "part_name" is the name of the partition to be restored or "-all" to restore all the partitions that were saved. If "-all" is specified then all partitions defined on the volume that are not restored will be zero filled, except for any "alt" or "hc" partitions and the "bce" partition on the rpv. Up to 64 partitions may be defined per restore set. control_file [control_file], cf [control_file] where "control_file" defines another control file to be examined. This enables control files to be linked together. For instance ONE control file could define all the tape devices for the restore. The other control files could be broken down into logical volumes that only reference the tape device control file and then define the physical volumes. Up to 32 control file names may be defined per restore. Bootload Multics (BCE) B-7 SIB12.0 Notes on control file requests: Only one request may be given per line. Any lines in a control file that begin with /, & or " are treated as comments. All white space prior to a request in a line is trimmed before processing. Partitions on a physical volume can be restored without having to restore the vtoc and paging regions by only defining a partition request. This can also be used to copy a partition from one volume to another, even of different types. The control files can be edited using the BCE qedx request, or edited while the system is running and updated in the file partition by either using bootload_fs or regeneration of the MST. Notes on restore: The first tape read during a restore is always the "Info" tape, which was the last tape written when the set was saved. This gives the restore information necessary to properly locate items without wasting time spinning tape. Notes on operator interrupts: A restore can be interrupted by use of the console "request" key. When depressed while a restore is in progress, the message "restore: Abort request:" will appear. The operator will be required to input one of the following responses. no, n This causes the program to ignore the request and resume the restore. abort This causes the program to abort the entire restore and return to BCE command level. restart TAPE_SET This allows the operator to restart the specified TAPE_SET, using its current tape device. The operator is then required to mount the "restart" tape on the device, which is the tape that the operator wishs to restart from. Once the SET has been restarted, the remaining SETs will continue operation. stop TAPE_SET This causes the program to abort the specified TAPE_SET, by marking it complete, and resume the restore of the other sets. help, ? This causes the program to display the above possible responses, with a small description of each. Bootload Multics (BCE) B-8 SIB12.0 Notes on tape error recovery: During a restore there are times when errors occur which require special handling. Read data errors are retried by the program up to eight times. If unable to read the data, the error becomes unrecoverable. The recovery procedure will be selected by the operator. One choice would be to perform the retry attempts again. Another would be to skip this record and try to read the next. The full list of possibilities are listed below. When an unrecoverable error occurs a message will be displayed that shows the error interpreted in english, with detailed status in hex if required. The operator will be queried as to the course of action that the program should take. Listed below is an example error output and the possible responses and their meanings. restore(blue): Device Attention, Handler check on tapa_12. detailed status: 20 8C 2B 6D 0A 01 16 00 00 16 48 87 24 18 06 00 00 0C 00 00 08 08 80 00 00 00 restore: Action: abort This causes the program to abort the entire restore and return to BCE command level. retry, r For errors that are retryable this will force the retry process to be redone. It is invalid for non-retryable errors. skip, s This is only valid for unrecoverable data alert errors detected while doing a restore. The unreadable record is skipped and the program continues by attempting to read the next record. stop_set, stop This will cause this SET to be aborted, but all other SETs will continue. restart_set, restart, rt This allows the operator to restart this SET, using the current tape device. The operator is then required to mount the "restart" tape on the device. Once the SET has been restarted, the remaining SETs will continue operation. remove_device_from_set, remove Works like the "restart_set" request above, but removes the current tape device from the SET and sequences to the next device before going through the restart process. This is not a valid response if this is the only tape device left in the SET. help, ? This causes the program to display the above possible responses, with a small description of each. Bootload Multics (BCE) B-9 SIB12.0 APPENDIX C FORMATTING DISKS WITH MTR This appendix describes a procedure for formatting disk packs using the Media Test Routines (MTRs). The procedure utilizes an annotated script which shows typical input and output. Because the formatting procedures differ for MSU0451 and MSU0500/0501 devices, separate scripts are provided. In the scripts, input typed by the user is preceded by a ox (bullet). _F_O_R_M_A_T_T_I_N_G _M_S_U_0_4_5_1 _D_I_S_K _P_A_C_K_S The following script shows how to run MTR tests 6 and 3 to format and test an MSU0451 disk pack, and to assign alternates to tracks found defective during testing. 1. Enter the Total OnLine Test System (TOLTS): ox bound_tolts_$tolts_ ***tolts executive version 810301 on 820812 at 20.071 2. Enter the MPC OnLine Test Subsystem (MOLTS): ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" ??? ox molts Formatting Disks With MTR C-1 SIB12.0 3. List the disk configuration for the disk string which formatting will be done (because of page constraints, the following message is not an exact copy of that which is displayed by the system): ??? ox test pcd peripheral configuration: dska 451 16 units; starting with device no. 1 020xx primary channel of 4 logical channels on mpc mspa 026xx secondary channel of 4 logical channels on mpc mspa 124xx secondary channel of 4 logical channels on mpc mspb 122xx secondary channel of 4 logical channels on mpc mspb 4. Enter MTR test 6 to format and test the MSU0451 device: ??? ox test mmt12020t6 where "test mmt12020t6" is a sample of the input format "test mmtICCDDtT": mmt identifies the MTR test package ICC gives the IOM number (0 = IOM A, 1 = IOM B, etc) and channel number (in decimal) of a channel by which the device to be formatted can be addressed. It must be one of those shown in the output of "test pcd" in step 3. In the sample input above, "120" is IOM B, channel 20. DD gives the device number (in decimal) of the device to be tested. In the sample input, it is device 20 (dskb_20). T gives the number of the MTR test to be run. In this case, test 6 should be run to format/test a pack. Formatting Disks With MTR C-2 SIB12.0 5. The following output describes steps taken by MTR test 6 to attach the disk drive and mount the pack for writing: ***molts executive versions 820601 820701 on 820812 at 19.97 **0(mmt12020) short wait, allocation queued **0(mmt12020) start tmt65a-rmc1, ttldat 820331, phy./log. id t//04 **0(mmt12020) start tmt65b-rmc2, ttldat 820331, phy./log. id t//04 **0(mmt12020) start tmt65c-rmc3, ttldat 820401, phy./log. id t//04 **0(mmt12020) start tmt65d-rmc4, ttldat 820405, phy./log. id t//04 **0(mmt12020) start tmt65e-rmc5, ttldat 820421, phy./log. id t//04 **0(mmt12020) start tmt65f-rmc6, ttldat 820331, phy./log. id t//04 **0(mmt12020) rmc6 is at your service to format a disk pack - **0(mmt12020) ***** write permission granted ***** **0(mmt12020) ***** begin format pack ***** the test will format all tracks on the pack. format will defined by device type. bad tracks will be marked defective (no alt. assigned). **0(mmt12020) system device code = .ds450 6. Answer MTR initialization questions (not a restart, normal formatting, and use 3 write patterns during testing): **0(mmt12020) is this a restart? enter (y or n) - ox n **0(mmt12020) select (f)ast or (n)ormal format? (f)ast format is designed for data security erase and/or test purposes. (n)ormal format is designed for disk packs that are going to be used in systems applications. enter (f or n) - ox n **0(mmt12020) select from "1" to "7" write patterns? enter (1 thru 7) - ox 3 7. At this point, formatting of the pack begins: **0(mmt12020) ***** begin disk pack format ***** Formatting Disks With MTR C-3 SIB12.0 8. After the message in Step 7 is displayed, press the BREAK key to interrupt formatting operations. When MOLTS prompts for input, set test options to: report the current cylinder/head (CCC/HH) address; display CCC/HH for transient errors; report test progress every 100 cylinders, with summary reports attached. ox ??? ox test momt12020.r where "test momt12020.r" is a sample of the input format "test momtICCDD.O": momt identifies request to set options ICCDD are the IOM, Channel and Device numbers given in Step 4. .r is the first option, to report current CCC/HH location. Set the remaining options when prompted: *0(mmt12020) t6 enter options: ox .i *0(mmt12020) t6 enter options: ox .e *0(mmt12020) t6 enter options: ox .s *0(mmt12020) t6 enter options: ox .t *0(mmt12020) t6 enter options: ox .go 9. When the .go option is entered in Step 8, MTR reports the current location being formatted and displays the defective tracks found. It then asks if you want to continue formatting: **0(mmt12020) format function current addr. = 007/00 **0(mmt12020) format function current addr. = 007/00 **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) do you want the test to continue? enter (y or n) - ox y Formatting Disks With MTR C-4 SIB12.0 10. After every 100 cylinders are formatted, MTR displays defective tracks found. For example, the final summary displayed just before formatting completes, looks like: **0(mmt12020) rmc6 has formatted tracks "000/00 thru 700/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) rmc6 has formatted tracks "000/00 thru 800/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) ***** disk pack format complete ***** 11. After formatting is complete, MTR begins testing the tracks on the formatted pack. Defective tracks are usually encountered only during the testing phase. Error summaries are displayed after every 100 cylinders have been tested. start media test phase **0(mmt12020) rmc6 has tested tracks "000/00 thru 100/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) rmc6 has tested tracks "000/00 thru 200/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) rmc6 has tested tracks "000/00 thru 300/00" **0(mmt12020) ***** rmc6 - summary report ***** defective - marginal data field on std track 217/10 **0(mmt12020) ***** rmc6 - summary report ***** defective - unrec. data field on std track 244/06,245/06 **0(mmt12020) ***** rmc6 - summary report ***** reclaimed - reformatted and certified 246/06 Formatting Disks With MTR C-5 SIB12.0 12. When testing is complete, termination summary reports are displayed: **0(mmt12020) ***** normal termination summary reports ***** **0(mmt12020) ***** rmc6 - summary report ***** defective - marginal data field on std track 217/10 **0(mmt12020) ***** rmc6 - summary report ***** defective - unrec. data field on std track 244/06,245/06 **0(mmt12020) ***** rmc6 - summary report ***** reclaimed - reformatted and certified 246/06 13. MTR then asks if you want to select a new test (answer "y" for yes): **0(mmt12020) want to select a new test? enter (y or n) - ox y 14. MTR then displays information describing how to select the next test: **0(mmt12020) rmc6 will go into waiting! select test (t1 thru t6) enter test no. thru standard option call (test momticcddtx) - **0(mmt12020) waiting Formatting Disks With MTR C-6 SIB12.0 15. To actually select the next test, press the BREAK key and wait for the MOLTS prompt. Then select test 3, which assigns alternate tracks for those tracks found to be defective above. ox ??? ox test momt12020t3 where "test momt12020t3" is a sample of the input format "test momtICCDDtT": momt identifies request to set options ICCDD are the IOM, Channel and Device numbers given in Step 4. tT gives the number of the next test to run. Test 3 initialization displays the following information: **0(mmt12020) start tmt65e-rmc5, ttldat 820421, phy./log. id t//04 **0(mmt12020) start tmt65d-rmc4, ttldat 820405, phy./log. id t//04 **0(mmt12020) start tmt65c-rmc3, ttldat 820401, phy./log. id t//04 16. Select subtest 4 of test 3, to assign alternates to all defective tracks: **0(mmt12020) rmc3 is at your service for track and cylinder reformat - select a sub test a) subtst 1 - reformat 1 track (good) b) subtst 2 - reformat 1 cylinder (good) c) subtst 3 - reformat 1 track (defective) d) subtst 4 - assign alternate tracks enter (1 thru 4) - ox 4 Formatting Disks With MTR C-7 SIB12.0 17. MTR then briefly describes the subtest, and asks if you want to continue (answer "y" for yes) **0(mmt12020) ***** begin subtst 4 ***** assign alternate tracks on the device a) subtst will search thru all standard tracks looking for tracks marked defective (no alternate assigned). b) when a track marked defective (no alternate assigned) is detected, the subtst will stop and process this track. c) the alternate track processor will go out to the alternate track cylinders and find the first available alternate. it will mark the track as assigned alternate. then it will mark the standard track as defective (alt. assigned). d) the search process will terminate after the last standard track completes testing and/or processing. do you want the subtst to continue? enter (y or n) - ox y 18. MTR then asks for permission to overwrite the pack's label (answer "y" for yes): **0(mmt12020) ***** rmc3 - label obliterate warning ***** all sub tests in rmc3 will overwrite the system label on track zero. do you want the sub test to continue? enter (y or n) - ox y 19. MTR then asks if you are restarting (answer "n" for no): **0(mmt12020) system device code = .ds450 **0(mmt12020) is this a restart? enter (y or n) - ox n 20. MTR then begins displaying summary reports after every 100 cylinders are checked for alternate assignments: **0(mmt12020) rmc3 has tested tracks "000/00 thru 200/00" **0(mmt12020) ***** rmc3 - subtst 4 summary report ***** no alternate tracks were assigned **0(mmt12020) rmc3 has tested tracks "000/00 thru 300/00" **0(mmt12020) ***** rmc3 - subtst 4 summary report ***** defective - alt assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 217/10 811/00 244/06 811/01 245/06 811/02 Formatting Disks With MTR C-8 SIB12.0 21. After alternate assignments are complete, MTR displays a summary report describing all alternates on the pack: **0(mmt12020) ***** normal termination summary reports ***** **0(mmt12020) ***** rmc3 - subtst 4 summary report ***** defective - alt assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 217/10 811/00 244/06 811/01 245/06 811/02 22. MTR then asks if you want to select a new test (answer "n" for no, and "quit" to exit from TOLTS). **0(mmt12020) want to select a new test? enter (y or n) - ox n **0(mmt12020) normal term 1 ***molts executive version 820701 off 820812 at 21.45 p.t. 119530 ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" ??? ox quit ***tolts executive version 810301 off 820812 at 21.375 r 21:37 1107.348 1162 Formatting Disks With MTR C-9 SIB12.0 _F_O_R_M_A_T_T_I_N_G _M_S_U_0_5_0_0_/_M_S_U_0_5_0_1 _D_I_S_K _P_A_C_K_S The following script shows how to run MTR tests 6 and 7 to format and test an MSU0500 or MSU0501 disk drive, and to assign alternates to tracks found defective during testing. The MPC normally treats an MSU0500 or MSU0501 disk drive as two separately addressable devices. However, MTR formats and tests both logical devices during a single invocation, referring to one as the "odd device" (e.g., dskc_27) and the second as the "even device" (e.g., dskc_28). MTR refers to both logical devices as a single "head assembly" or "hda". 1. Enter the Total OnLine Test System (TOLTS): ox bound_tolts_$tolts_ ***tolts executive version 810301 on 820812 at 20.071 2. Enter the MPC OnLine Test Subsystem (MOLTS): ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" ??? ox molts 3. List the disk configuration: ??? ox test pcd peripheral configuration: dskc 501 32 units; starting with device no. 1 028xx primary channel of 4 logical channels on mpc mspc 030xx secondary channel of 4 logical channels on mpc mspc 130xx secondary channel of 4 logical channels on mpc mspd 128xx primary channel of 4 logical channels on mpc mspd Formatting Disks With MTR C-10 SIB12.0 4. Enter MTR test 6 to format and test the entire MSU0500 or MSU0501 device: ??? ox test mmt12827t6 where "test mmt12827t6" is a sample of the input format "test mmtICCDDtT": mmt identifies the MTR test package ICC gives the IOM number (0 = IOM A, 1 = IOM B, etc) and channel number (in decimal) of achannel by which the device to be formatted can be addressed.It must be one of those shown in the output of "test pcd" in step 3. In the sample input above, "128" is IOM B, channel 28. DD gives the device number (in decimal) of the device to be tested. In the sample input, it is device 27 (dskc_27). Always give the device number of the "odd device" associated with the disk drive. T gives the number of the MTR test to be run. In this case, test 6 should be run to format/test the drive. 5. The following output describes steps taken by MTR test 6 to attach the disk drive for writing: ***molts executive versions 820601 820701 on 820805 at 20.08 **0(mmt12827) short wait, allocation queued **0(mmt12827) short wait, allocation queued **0(mmt12827) start tmt67a-mtr1, ttldat 820401, phy./log. id t//04 **0(mmt12827) start tmt67b-mtr2, ttldat 820401, phy./log. id t//04 **0(mmt12827) start tmt67c-mtr3, ttldat 820402, phy./log. id t//04 **0(mmt12827) start tmt67d-mtr4, ttldat 820405, phy./log. id t//04 **0(mmt12827) start tmt67e-mtr5, ttldat 820421, phy./log. id t//04 **0(mmt12827) start tmt67f-mtr6, ttldat 820405, phy./log. id t//04 **0(mmt12827) mtr6 is at your service to format a physical device - **0(mmt12827) ***** write permission granted ***** **0(mmt12827) ***** begin upgrade/downgrade hda ***** the test will format all tracks on the hda. the format will be defined by device type. bad tracks will be marked defective (no alternate). Formatting Disks With MTR C-11 SIB12.0 6. Answer MTR initialization questions (ok to format with 512 words per sector, not a restart, normal formatting, and use 3 write patterns during testing): **0(mmt12827) device pair are configured as msu0501's the hda will be formatted in (512) words/sector. is this correct? enter (y or n) - ox y **0(mmt12827) is this a restart? enter (y or n) - ox n **0(mmt12827) select (f)ast or (n)ormal format? (f)ast format is designed for data security erase and/or test purposes. (n)ormal format is designed for hda's to be used in systems applications. enter (f or n) - ox n **0(mmt12827) select from "1" to "7" write patterns? enter (1 thru 7) - ox 3 7. At this point, formatting of the pack begins: **0(mmt12827) ***** begin hda format ***** Formatting Disks With MTR C-12 SIB12.0 8. After the message in Step 7 is displayed, press the BREAK key to interrupt formatting operations. When MOLTS prompts for input, set test options to: report the current cylinder/head (CCC/HH) address; display CCC/HH for transient errors; report test progress every 100 cylinders, with summary reports attached. ox ??? ox test momt12827.t where "test momt12020.r" is a sample of the input format "test momtICCDD.O": momt identifies request to set options ICCDD are the IOM, Channel and Device numbers given in Step 4. .r is the first option, to report current CCC/HH location. Set the remaining options when prompted: *0(mmt12827) t6 enter options: ox .e *0(mmt12827) t6 enter options: ox .s *0(mmt12827) t6 enter options: ox .i *0(mmt12827) t6 enter options: ox .r *0(mmt12827) t6 enter options: ox .go Formatting Disks With MTR C-13 SIB12.0 9. When the .go option is entered in Step 8, MTR reports the current location being formatted and displays the defective tracks found. It then asks if you want to continue formatting: **0(mmt12827) format function current addr. = 004/00 **0(mmt12827) format function current addr. = 004/00 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 1 no. of tracks with 2 defect skips = 0 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 0 total defect skips processed = 1 odd device defective tracks = 0 even device defective tracks = 0 physical device defective tracks = 0 total = 0 **0(mmt12827) ***** mtr6 - hda condition summary report ***** no tracks were marked defective. **0(mmt12827) do you want the test to continue? enter (y or n) - ox y Formatting Disks With MTR C-14 SIB12.0 10. After every 100 cylinders are formatted, MTR displays defective tracks found. For example, the final summary displayed just before formatting completes, looks like: **0(mmt12827) mtr6 has formatted tracks "000/00 thru 800/00" **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- defective - error logging track info 006/19,028/19,284/01,370/12 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- defective - error logging track info 008/19,026/19,096/05,174/16,381/06,736/09,778/19 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 33 no. of tracks with 2 defect skips = 2 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 0 total defect skips processed = 37 odd device defective tracks = 4 even device defective tracks = 7 physical device defective tracks = 0 total = 11 **0(mmt12827) ***** hda format complete ***** Formatting Disks With MTR C-15 SIB12.0 11. After formatting is complete, MTR begins testing the tracks on the formatted pack. Error summaries are displayed after every 100 cylinders have been tested. start media test phase **0(mmt12827) mtr6 has tested tracks "000/00 thru 100/00" **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- defective - error logging track info 006/19,028/19,284/01,370/12,816/04,818/04,832/04 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- defective - error logging track info 008/19,026/19,096/05,174/16,381/06,736/09,778/19 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- reclaimed - repaired data field 042/15 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 42 no. of tracks with 2 defect skips = 2 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 1 total defect skips processed = 47 odd device defective tracks = 7 even device defective tracks = 7 physical device defective tracks = 0 total = 14 Formatting Disks With MTR C-16 SIB12.0 12. When testing is complete, termination summary reports are displayed: **0(mmt12827) ***** normal termination summary reports ***** **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- defective - error logging track info 006/19,028/19,284/01,370/12,816/04,818/04,832/04 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- reclaimed - repaired data field 764/09,830/04 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- defective - error logging track info 008/19,026/19,096/05,174/16,381/06,736/09,778/19 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- reclaimed - repaired data field 042/15,762/09,818/08 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 42 no. of tracks with 2 defect skips = 2 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 5 total defect skips processed = 51 odd device defective tracks = 7 even device defective tracks = 7 physical device defective tracks = 0 total = 14 13. MTR then asks if you want to select a new test (answer "y" for yes) **0(mmt12827) want to select a new test? enter (y or n) - ox y Formatting Disks With MTR C-17 SIB12.0 14. MTR then displays information describing how to select the next test: **0(mmt12827) mtr6 will go into waiting! select test (t1 thru t7) enter test no. thru standard option call (test momticcddtx) - **0(mmt12827) waiting 15. To actually select the next test, press the BREAK key and wait for the MOLTS prompt. Then select test 7, which assigns alternate tracks for those tracks found to be defective above. Test 7 assigns alternates for the complete head assembly, whereas test 3 (used in the procedure for formatting MSU0451 disks) only assigns alternates for a single logical device. Thus, test 3 would have to be run twice (once for the odd device and once for the even device) to assign alternates on an MSU0500 or MSU0501 disk. ox ??? ox test momt12827t7 where "test momt12827t7" is a sample of the input format "test momtICCDDtT": momt identifies request to set options ICCDD are the IOM, Channel and Device numbers given in Step 4. tT gives the number of the next test to run. Test 7 initialization displays the following information: **0(mmt12827) start tmt67g-mtr7, ttldat 820405, phy./log. id t//04 16. Select subtest 1 of test 7, to assign alternates to all defective tracks: **0(mmt12827) mtr7 is at your service for special physical device formatting - select the subtst a) subtst 1 - assign all alternate tracks b) subtst 2 - create & write logging tracks enter (1 thru 2) - ox 1 Formatting Disks With MTR C-18 SIB12.0 17. MTR then briefly describes the subtest, and asks if you want to continue (answer "y" for yes): **0(mmt12827) ***** begin subtst 1 ***** assign alternate tracks on the physical device the subtst will search "all" standard tracks on the hda for defective (no alt. assigned). if any are found, it will assign the 1st available alternate to them. **0(mmt12827) do you want subtst (1) to continue? enter (y or n) - ox y 18. MTR then asks if you are restarting (answer "n" for no): **0(mmt12827) is this a restart? enter (y or n) - ox n 19. MTR then begins displaying summary reports after every 100 cylinders are checked for alternate assignments: **0(mmt12827) mtr7 has processed tracks "000/00 thru 100/00" **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 odd device report (27) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 006/19 840/00 028/19 840/03 **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 even device report (28) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 008/19 840/01 026/19 840/02 096/05 840/04 Formatting Disks With MTR C-19 SIB12.0 20. After alternate assignments are complete, MTR displays a summary report describing all alternates on the pack: **0(mmt12827) ***** normal termination summary reports ***** **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 odd device report (27) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 006/19 840/00 028/19 840/03 284/01 840/06 370/12 840/07 816/04 840/11 818/04 840/12 832/04 840/13 **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 even device report (28) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 008/19 840/01 026/19 840/02 096/05 840/04 174/16 840/05 381/06 840/08 736/09 840/09 778/19 840/10 21. MTR then asks if you want to select a new test (answer "n" for no, and "quit" to exit TOLTS). **0(mmt12827) want to select a new test? enter (y or n) - ox n **0(mmt12827) normal term 1 ***molts executive version 820701 off 820806 at 00.27 p.t. 5185916 ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" ??? ox quit ***tolts executive version 810301 off 820806 at 00.165 r 00:16 5188.584 1038 C-20 SIB12.0 CONTENTS Page Section 1 Introduction . . . . . . . . . . . . . . 1-1 Site Support . . . . . . . . . . . . . 1-1 Section 2 Description of Package . . . . . . . . . 2-1 Library Naming Conventions . . . . . . 2-1 Contents of MR12 Package . . . . . . . 2-2 Section 3 FCO and Firmware Status . . . . . . . . . 3-1 Firmware . . . . . . . . . . . . . . . 3-1 Field Change Order List . . . . . . . 3-2 Section 4 Instructions for Sites Updating to MR12 from MR11 . . . . . . . . . . . . . . . 4-1 _S_I_G_N_I_F_I_C_A_N_T _C_H_A_N_G_E_S _I_N _T_H_I_S _R_E_L_E_A_S_E . 4-2 Step 1: Pre-Installation Preparation 4-3 Step 2: Installation to BCE (early) Level . . . . . . . . . . . . . . . . 4-3 Step 3: Changes to Config Deck . . . 4-4 Step 4: Installation to BCE (boot) Level . . . . . . . . . . . . . . . . 4-4 Step 5: Ring-1 Environment . . . . . 4-5 Step 6: FNP Core Images and CMF Conversion . . . . . . . . . . . . . 4-5 Step 7: TTF Conversion . . . . . . . 4-7 Step 8: ACLs and Ring Brackets . . . 4-7 Step 9: System Cleanup . . . . . . . 4-8 Section 5 Instructions for Sites Installing for First Time . . . . . . . . . . . . . . . 5-1 Step 1: Preparation . . . . . . . . . 5-1 Step 2: Logical Volume Assignments . 5-2 Step 3: RPV Initialization . . . . . 5-4 Step 4: Configuration . . . . . . . . 5-6 Step 5: Initializing Root Volumes . . 5-7 Step 6: Additional Configuration Parameters . . . . . . . . . . . . . 5-8 Step 7: Reload of Executable Libraries . . . . . . . . . . . . . . 5-8 Step 8: Setting and Checking Access . 5-10 Step 9: Setting Volume Quota . . . . 5-11 iii SIB12.0 CONTENTS (cont) Page Step 10: Reload of Remaining Release Tapes . . . . . . . . . . . . . . . . 5-12 Step 11: Running acct_start_up.ec . . 5-13 Step 12: Multics Communications System . . . . . . . . . . . . . . . 5-13 Step 13: Complete Accounting Startup 5-15 Step 14: Check Gate ACLs . . . . . . 5-16 Step 15: Save Checkpoint . . . . . . 5-17 Step 16: Tailor System and Register Projects . . . . . . . . . . . . . . 5-17 Step 17: Setup Volume Backup/Reloader 5-17 Step 18: Setup Directory Quota . . . 5-18 Appendix A Module Changes for MR12 . . . . . . . . . A-1 New Info Segments for MR12 . . . . . . A-2 New Segments for MR12 . . . . . . . . A-3 New Include Files for MR12 . . . . . . A-4 Deleted Segments for MR12 . . . . . . A-5 Modified Segments for MR12 . . . . . . A-7 Appendix B Bootload Multics (BCE) . . . . . . . . . B-1 BCE Command Information . . . . . . . B-1 save command . . . . . . . . . . . B-2 restore command . . . . . . . . . . B-5 Appendix C Formatting Disks with MTR . . . . . . . . C-1 Formatting MSU0451 Disk Packs . . . . C-1 Formatting MSU0500/MSU0501 Disk Packs C-10 iv SIB12.0 ----------------------------------------------------------- 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