SECTION 1 INTRODUCTION This document describes the MR12.2 package. Detailed instructions for installation of a system for the first time and upgrading to MR12.2 from an MR12.1 system constitute the major portion of this document. No attempt is made to document features of MR12.2 other than those directly required for its installation. Software Releases prior to MR12.1 are no longer supported. All sites running pre-MR12.1 software are strongly encouraged to upgrade to MR12.1 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. 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 Introduction 1-1 SIB12.2 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.2 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 Frank Martinson Mgr, MSS Martinson.sm 602/862-3592 Paul Farley TRs, C&F, Site Support Farley.sm 602/862-3621 Joe Hirneisen Sys. Integration Release Prep Hirneisen.sm 602/862-4812 Note that all of the above numbers are available through HVN 862-XXXX (eg, 862-4839 for Martinson). Introduction 1-2 SIB12.2 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.2 _C_O_N_T_E_N_T_S _O_F _M_R_1_2_._2 _P_A_C_K_A_G_E MR12.2 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.2 release from MR12.1. Sites upgrading to MR12.2 from MR12.1 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.2 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 MR12.1. Appendix B 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.2LDD_STANDARD 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.2 _T_a_p_e__N_a_m_e_s _D_e_s_c_r_i_p_t_i_o_n 12.2EXEC Complete dump of Multics executable libraries >documentation, >obs, >sss, >tools, and >firmware. 12.2UNBUNDLED 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.2LDD_STANDARD Complete dump of all standard library source, object, include files and info segs. 12.2MULTICS Complete Multics System Tape (MST). 12.2MISC The compout segment for this document and other supporting documentation, if any, are contained on this tape in >doc>MR12.2. 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. Package Description 2-3 SIB12.2 The accompanying hardcopy listings are: _L_i_s_t_i_n_g _D_e_s_c_r_i_p_t_i_o_n 12.2EXEC.DUMP.MAP Contents of the 12.2EXEC tape. 12.2UNBUNDLED.DUMP.MAP Contents of the 12.2UNBUNDLED tape (for those sites purchasing Priced Separate Software). 12.2LDD_STANDARD.DUMP.MAP Contents of the 12.2LDD_STANDARD tapes. 12.2MISC.DUMP.MAP Contents of the 12.2MISC tape. A detailed status of all MR12.2 modules contained on the Multics system tape is included on the 12.2LISTINGS 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.2 hardcore modules Package Description 2-4 SIB12.2 SECTION 3 FCO AND FIRMWARE STATUS _F_I_R_M_W_A_R_E The firmware identification for MR12.2 is "IFAD D.4". IFAD (Integrated Firmware and Diagnostics) tapes, are distributed to all sites having valid Field Engineering Hardware Maintenance contracts. The IFAD tape is nolonger distributed as an FCO. It is now sent with the MR12.2 release tapes. T&D (Test and Diagnostic) tapes, are distributed to all sites having valid Field Engineering Hardware Maintenance contracts. The T&D tape is distributed as FCO PHAFGA888, rev. B.2. This version of IFAD, firmware, and T&D modules has been tested and exposed on System M in Phoenix. The modules are supplied as part of the MR12.2 release and can be found in >ldd>firmware as part of the LDD_STANDARD tape. When subsequent IFAD tapes become available, it is recommended that the site use the deckfile_manager, dfm, command to load the released IFAD tape into >system_library_tandd. The firmware modules should then be moved to >ldd>firmware and a new MST tape should be generated using generate_mst. The MR12.2 release requires the following firmware revision levels. Disc: DSC191 -- V1 DSC500 -- X1 MSP800 -- K1 Tape: MTC0500 -- V1 MTP0601 -- T1 MTP0610 -- Y2 Firmware Status 3-1 SIB12.2 Unit Record: Common -- A2 Reader/Punch -- B2 PRU1200/1600 -- M1 _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 MR12.1. Sites that are upgrading from MR12.1 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.2 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 recommended 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.2 _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 ---------- ------ --------- ----- ----- ------- No category 1 changes are required for MR12.2. Firmware Status 3-4 SIB12.2 _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--------------------------------- PHAFPE515 ETCCZ 88 Mar Yes 1.0 MR12.2 -----INTEGRATED MULTIPLEXER UNIT (IMU)---------------------- PHXFXS852 WXGJB 88 Mar No 1.5 MR12.2 Yes .1 -----MEMORY CONTROLLER (SCU)------------------------------- PHAFGE176 BKPNL 88 Mar No 1.0 MR12.2 Firmware Status 3-5 SIB12.2 _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 ---------- ------ --------- ----- ----- ------- -----INTEGRATED MULTIPLEXER UNIT (IMU)--------------------- PHAFXS845 WXCMC-1 88 Apr No 1.2 MR12.2 PHAFXS945 MCA 88 Apr No 3.0 MR12.2 -----FIPS DISK MSU 3380/3382, MSP 3880/1/4/5--------------- PHAFFP543 Firmware 87 Oct No .4 MR12.2 PHAFFP546 F2 Card 87 Sep No .5 MR12.2 PHAFFP547 Firmware 87 Nov No .4 MR12.2 PHAFFP548 ESD PADs 88 Jan No .2 MR12.2 PHAFFP549 Firmware 88 Feb No .4 MR12.2 PHAFFP550 ESD PADs 88 Feb No .2 MR12.2 PHAFFP555 MD Diskette 88 Oct No .5 MR12.2 -----TAPE MTU 630------------------------------------------ PHAFFP328 EProms 87 Oct No .4 MR12.2 PHAFFP329 HQ Card 87 Oct No .9 MR12.2 PHAFFP330 EProms 87 Oct No .4 MR12.2 -----FIPS TAPE MTU 8205/06/08, MTS 8205/06/08/15/16/18----- PHAFFP428 Door Latch 87 Sep No 1.0 MR12.2 PHAFFP429 File Hub 87 Sep No 1.0 MR12.2 PHAFFP431 FW Patch 87 Dec No .4 MR12.2 -----T&D RELEASE REV. B.2---------------------------------- PHAFGA888 Tape 87 Mar No 2.0 MR12.1 -----MHAT MR12.0------------------------------------------- PHAFPD998 Tape 87 May No 2.0 MR12.0 Firmware Status 3-6 SIB12.2 SECTION 4 INSTRUCTIONS FOR SITES UPDATING TO MR12.2 FROM MR12.1 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.2 _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 It is recommended that sites perform a BCE SAVE. 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 MR12.1 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.2 Mult tape on any convenient tape drive. Initialize and boot the MST. 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.2. 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-> _S_T_E_P _3_: _C_H_A_N_G_E_S _T_O _C_O_N_F_I_G _D_E_C_K There are no config deck changes for MR12.2. 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. Instructions - Updating 4-2 SIB12.2 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 00:20:46 mst Is this correct? no Enter time: M-> ! 12/22/88__13:21:30 Current system time is: Thursday, December 22, 1988 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 X1. hc_load_mpc: Booting channel B20 with dsc500 Revision X1. bce (boot) 1325.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) 1325.5: boot Multics MR12.2 - 12/15/88 1201.0 est Thu. 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: Instructions - Updating 4-3 SIB12.2 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.2 Package," for a listing of all "Tape names". Enter for each library tape. When all tapes are loaded, type: standard admin _S_T_E_P _6_: _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 _S_T_E_P _7_: _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 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 8 after ensuring the CMF image statement points to the core image now located in >unb. Instructions - Updating 4-4 SIB12.2 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.6b cwd >udd>sa>a>mcs.7.6b 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. . . 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. Instructions - Updating 4-5 SIB12.2 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_. 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.* Instructions - Updating 4-6 SIB12.2 >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.2. Following a reasonable period of MR12.2 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-7 SIB12.2 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.2 _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 >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.2 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.2 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.2 generated 08/31/88 0000.0 bootload_0: Enter boot tape MPC model: ! t500 Normal response to this question should be "ipc", "t610", "t601" or "t500". However, on systems with an IMU configured the "Enter boot tape..." query will not appear. 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.2. with mtc500 rev.u1 firmware. Instructions - First Time 5-4 SIB12.2 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-> ! 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. (451 disk drive only) 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.2 _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 00:20:46 mst Is this correct? no Enter time: M-> ! 12/22/88__13:21:30 Current system time is: Thursday, December 22, 1988 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 X1. hc_load_mpc: Booting channel B20 with dsc500 Revision X1. bce (boot) 1325.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) 1325.5 : M-> ! boot -cold Do you really wish to boot cold and there by destroy the system hierarchy? M-> ! yes 1326.1 volume_registration_mgr_$check_volume_registration: Reregistered public LV root LVID 133353533031 (Initializer.SysDaemon.z) 1326.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.2 Multics MR12.2 - 12/22/88 1327.0 mst Thu. 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.2 _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.2.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.2 - 12/22/88 1400.2 mst Thu 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.2 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 14:15 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 (Note: 451 disk only) end init_vol pub02 dska_04 -special part alt high 141 (Note: 451 disk only) 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.2 _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.2 _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.2 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.2.LDD_STANDARD and MR12.2.UNBUNDLED tapes with the following commands: boot alv -all reload -nosetlvid The tape labeled MR12.2.MISC must be the final tape of the MR12.2 supplied set to be reloaded. Instructions - First Time 5-12 SIB12.2 _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. The error, "new_iod_tables_compiler: Entry not found. Accessing cdt. Channel name checks will not be performed", may be encountered during this stage. This error should be disregarded. 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.6. 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. Instructions - First Time 5-13 SIB12.2 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 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.6b cwd >udd>sa>a>mcs.7.6b ted 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 ted r CMF.cmf . . Locate the image: statement by typing: Instructions - First Time 5-14 SIB12.2 /image/ Edit the image: statement to point to the CS image, site_mcs, by making the statement read: :image: >udd>sa>a>mcs.7.6b>site_mcs; . . Make any other changes needed. . . w CMF.cmf q cv_cmf CMF.cmf copy CMF.cdt >sc1>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 _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. During this stage you will encountered the error, "set_max_length: Validation level not in ring bracket. >system_control_1>mcaa.acs", which occurs if an IMU is configured. Ignore this error message. The cause of this error, validation level of >sc1>mcaa.acs, must be fixed manually after cold2 has completed successfully. Instructions - First Time 5-15 SIB12.2 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 . scavenge_vol: No volumes. Found unexpected command_error in system start_up.ec. These messages may be ignored. _S_T_E_P _1_4_: _C_H_E_C_K _G_A_T_E _A_C_L_S 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.* Instructions - First Time 5-16 SIB12.2 >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-17 SIB12.2 _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 commands: admin 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. Instructions - First Time 5-18 SIB12.2 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 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 Module Changes for MR12.2 5-19 SIB12.2 on these directories (directories with 0 quotas are omitted from the disk report). Module Changes for MR12.2 5-20 SIB12.2 APPENDIX A MODULE CHANGES FOR MR12.2 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.2 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 or modified include files deleted segments modified segments Module Changes for MR12.2 A-1 SIB12.2 _N_E_W _I_N_F_O _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2_._2 abbrev.info list_not_accessible.info abbrev_.info list_output_requests.info add_search_paths.info list_retrieval_requests.info add_search_rules.info list_sub_tree.info alm.info list_vols.info (PRIV) ascii_table.gi.info load_mowse.info autobaud.gi.info mailbox_acls.info background_file_transfer.gi.info manage_volume_pool.info background_file_transfer.info mowse.info bft_.info mowse_io_.info canonicalize.info mowse_start.gi.info change_wdir.info mtape_.info compare_configuration_deck.info pc_bft_.info copy_deadproc.info (PRIV) pl1.info copy_dir.info print_messages.info copy_liveproc.info (PRIV) print_terminal_types.info create_mrds_db.info request_info.info delete_search_paths.info reset_soos.info (PRIV) dial_out.info ring_zero_dump.info (PRIV) disk_queue.info (PRIV) send_mail.info display_disk_label.info set_cc.info display_ttt.info set_lisp_temp_dir.info dump_segment.info set_mrds_options.info enter_abs_request.info status.info enter_imft_request.info store.info (LINUS) enter_output_request.info store_from_data_file.info (LINUS) extended_access.gi.info switch_off.info generate_mst.info (PRIV) switch_on.info help.info tty_.info help_responses.info user.info history_comment.info user_info_.info instr_speed.info (PRIV) value_get.info kermit.info video_editing.gi.info kermit_modes.gi.info where_search_paths.info list_abs_requests.info working_dir.info list_accessible.info write.info (LINUS) list_daemon_requests.info write_data_file.info (LINUS) list_lv_attachments.info (OPER) wsterm.info Module Changes for MR12.2 A-2 SIB12.2 _N_E_W _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2_._2 alm_symtab_.pl1 mrds_dsl_func_.pl1 as_lap_mpx_.pl1 mrds_dsl_parser.pl1 as_uncp_mpx_.pl1 mrds_dsl_select_clause_.pl1 bft_queue_.pl1 mrds_dsl_semantics.pl1 constant_token.pl1 mrds_dsl_tables.alm directory_commands_.pl1 mrds_dsl_where_clause_.pl1 eor_cv8_9_.pl1 mu_print_error.pl1 find_common_acl_names_.pl1 request_info.pl1 fs_star_.pl1 set_mrds_options.pl1 imft_util_.pl1 uncp.pl1 lap_dump_.pl1 uncp_boot_interrupt.pl1 lap_simplex.pl1 uncp_multiplexer.pl1 load_uncp_.pl1 uncp_util.pl1 mrds_dsl_expr_.pl1 Module Changes for MR12.2 A-3 SIB12.2 _N_E_W _O_R _M_O_D_I_F_I_E_D _I_N_C_L_U_D_E _F_I_L_E_S _F_O_R _M_R_1_2_._2 DECOR_TABLE.incl.pl1 mdbm_rm_db_info.incl.pl1 _imft_check_acl.incl.pl1 mrds_compiled_se_info.incl.pl1 _imft_driver_info.incl.pl1 mrds_dbcb.incl.pl1 _imft_ft_request.incl.pl1 mrds_dsl_keywords.incl.pl1 _imft_std_commands.incl.pl1 mrds_dsl_tables.incl.pl1 abs_message_format.incl.pl1 mrds_lex_stack.incl.pl1 abs_request_dcls.incl.pl1 mrds_scanner_tables.incl.pl1 alm_include_file_info.incl.pl1 mrds_se_error_info.incl.pl1 backup_volume_record.incl.pl1 mrds_se_info.incl.pl1 bft.incl.pl1 mrds_se_options.incl.pl1 bft_queue.incl.pl1 mrds_select_list.incl.pl1 bft_values.incl.pl1 output_request_data.incl.pl1 bsr_structures.incl.pl1 pc_bft_.incl.archive defops.incl.alm pc_mowse_.incl.archive device_error.incl.alm pc_wsterm_.incl.archive device_error.incl.pl1 pcb.incl.pl1 dfast_line_table.incl.pl1 pit.incl.pl1 dmpr_input.incl.pl1 pl1_macro_lex_dcls.incl.pl1 dn355_data.incl.pl1 prt_conv_info.incl.alm dprint_arg.incl.pl1 prt_conv_info.incl.pl1 dprint_msg.incl.pl1 pvte.incl.alm dsatm_tty_modes.incl.pl1 pvte.incl.pl1 dskdcl.incl.alm rcerr.incl.pl1 dskdcl.incl.pl1 reload_set_info.incl.pl1 emacs-rdis-dcls.incl.lisp retv_data_.incl.pl1 emacs_data.incl.alm rldr_data_.incl.pl1 emacs_data.incl.pl1 sl_info.incl.pl1 fnp_types.incl.pl1 sthedr.incl.pl1 fs_obj_access_codes.incl.pl1 tc_input_buffer_.incl.pl1 fs_star_.incl.pl1 ttt.incl.pl1 fs_vol_label.incl.pl1 tty_buffer_block.incl.pl1 help_args_.incl.pl1 tty_convert.incl.pl1 help_cis_args_.incl.pl1 tty_mode_names.incl.pl1 io_special_status.incl.pl1 tty_read_status_info.incl.pl1 kermit_info.incl.pl1 uncp_buf.incl.pl1 kermit_mode_info.incl.pl1 user_abs_attributes.incl.pl1 kermit_transfer_info.incl.pl1 user_table_entry.incl.pl1 lap_line_info.incl.pl1 wtcb.incl.pl1 lap_simplex_data.incl.pl1 xforum_data_.incl.pl1 lar_info.incl.pl1 xmail_data.incl.pl1 linus_data_file_info.incl.pl1 xmail_send_mail.incl.pl1 Module Changes for MR12.2 A-4 SIB12.2 _D_E_L_E_T_E_D _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2_._2 change_wdir.pl1 mrds_dsl_select_clause.pl1 emacs.12.7.sv.lisp mrds_dsl_where_clause.pl1 emacs_.12.7.sv.lisp tut_quit_.pl1 find_common_acl_names_.pl1 tut_terminate_sys_.pl1 mrds_dsl_expr.pl1 vip7801.compdv mrds_dsl_func.pl1 vip7801_writer_.pl1 mrds_dsl_get_token.pl1 vip7801_writer_.pl1.xdw mrds_dsl_range_clause.pl1 Module Changes for MR12.2 A-5 SIB12.2 _M_O_D_I_F_I_E_D _S_E_G_M_E_N_T_S _F_O_R _M_R_1_2_._2 abbrev.pl1 as_x25_mpx_.pl1 abs_io_v2_get_line.pl1 asd_.pl1 absentee_listen_.pl1 asr_abs_command_server_.pl1 absentee_user_manager_.pl1 asr_com_channel_info_srvr_.pl1 absentee_utility_.pl1 assign_storage.pl1 accept_fs_disk.pl1 astty_.pl1 accept_rpv.pl1 asu_.pl1 access_.pl1 attribute_parse.pl1 access_audit_.pl1 audit_file_position_.pl1 access_audit_check_ep_.alm azm_display_fdump_events.pl1 access_class_check.pl1 azm_requests_1_.pl1 accounts_overseer_.pl1 azm_requests_2_.pl1 acl.pl1 azm_why_.pl1 acl_commands_.pl1 backup_cleanup.pl1 act_ctl_.pl1 backup_load.pl1 act_proc.pl1 basic.pl1 activate.pl1 basic_.pl1 add_line_numbers.pl1 bce_appending_simulation.pl1 add_pnotice.pl1 bce_copy_disk.pl1 add_scu.pl1 bce_create_sstnt.pl1 add_search_rules.pl1 bce_display_disk_label.pl1 adjust_cutoff_.pl1 bce_parse_disk_spec.pl1 admin_.pl1 bce_save.pl1 admin_util.pl1 bce_save_util_.pl1 alm.pl1 bce_shutdown_state.pl1 alm_cross_reference_.pl1 bce_test_disk.pl1 alm_include_file_.pl1 bft.c alm_source_map_.pl1 bft.mak alm_syserr_caller.pl1 bft.pl1 amu_fdump_mgr_.pl1 bft_.pl1 amu_find_system_dump_.pl1 bft_error_table_.alm amu_get_name_.pl1 bft_main_.pl1 amu_info_.pl1 bootload_disk_io.pl1 amu_parse_ptr_args_.pl1 bootload_fs.pl1 amu_search_path_.pl1 bootload_info.cds ansi_tape_io_.pl1 bootload_io.alm append.pl1 boundfault.pl1 archive.pl1 builtin.pl1 as_access_audit_.pl1 cancel_abs_request.pl1 as_add_admin_acl_.pl1 canonicalize.pl1 as_dump_.pl1 cdt_mgr_.pl1 as_hasp_mpx_.pl1 channel_manager.pl1 as_ibm3270_mpx_.pl1 charge_disk.pl1 as_init_.pl1 charge_user_.pl1 as_mcs_mpx_.pl1 check_file_system_damage.pl1 as_request_bump_user_.pl1 check_info_segs.pl1 as_request_note_pnt_change_.pl1 chname.pl1 as_request_server_.pl1 clear_sat.pl1 as_vip7760_mpx_.pl1 cmtv.alm as_who.pl1 command_processor_.pl1 Module Changes for MR12.2 A-6 SIB12.2 command_query_.pl1 disk_control.pl1 compile_messages.pl1 disk_emergency.pl1 compute_bill.pl1 disk_error_data.cds configure_test_cpu.pl1 disk_init.pl1 convert_MR10_2_pdts.pl1 disk_left_.pl1 convert_MR10_2_sat.pl1 disk_meters.pl1 convert_MR10_2_use_totals.pl1 disk_name_pvtx.pl1 convert_date_to_binary_.rd disk_queue.pl1 convert_string_.pl1 disk_rebuild.pl1 copy_acl_.pl1 disk_rebuild_caller.pl1 copy_deadproc.pl1 disk_stat_print.pl1 copy_dir_.pl1 disk_table_.pl1 copy_disk_volume.pl1 display_account_status.pl1 copy_mrds_data.pl1 display_audit_file.pl1 copy_pdir_.pl1 display_comp_dsm.pl1 correct_qused.pl1 display_disk_label.pl1 countervalidate_label_.pl1 display_disk_label_.pl1 cpg_.pl1 display_mrds_db_access.pl1 cpm_initialize_.pl1 display_mrds_dsm.pl1 create_root_vtoce.pl1 display_mrds_scope_settings.pl1 create_rpv_partition.pl1 display_psp.pl1 create_sat.pl1 display_pvolog.pl1 create_vtoce.pl1 display_ttt.pl1 cv_cmf.rd display_user_messages.pl1 cv_rcp_attributes_.pl1 display_volume_log.pl1 cv_ttf.rd dm_dmn_requests_.pl1 daemon_user_manager_.pl1 dm_fast_lock_status.pl1 daily_summary.pl1 dmpr_finish_.pl1 date_deleter.pl1 dmpr_log_.pl1 date_time_.pl1 dmpr_output_.pl1 dbm_man.pl1 dn355.pl1 dc_find.pl1 dn355_boot_interrupt.pl1 dctl.alm do_prt_request_.pl1 deactivate_for_demount.pl1 dpg_.pl1 declare_descriptor.pl1 dprint.pl1 default_error_handler_.pl1 dprint_.pl1 delentry.pl1 dump_anstbl_.pl1 delete.pl1 dump_cdt_.pl1 delete_fnp.pl1 dump_cmf_.pl1 delete_message.pl1 dump_segment.pl1 delete_proj.pl1 dump_volume_.pl1 delete_volume_log.pl1 dumper.pl1 demount_pv.pl1 e_argument_parse_.pl1 describe_entry_type.pl1 e_basic_.lisp device_acct_.pl1 e_defpl1_.lisp device_control.alm e_find_invocation_.alm dfast_basic_resequence_.pl1 e_interact_.lisp dfast_get_table_.pl1 e_lap_.lap dfast_merge_.pl1 e_mail_pl1_.pl1 dfast_process_overseer_.pl1 e_pl1_.pl1 dial_ctl_.pl1 e_redisplay_.lisp dial_out_sl_default_.cds e_tasking_.pl1 dialup_.pl1 e_window_mgr_.lisp Module Changes for MR12.2 A-7 SIB12.2 ed_installation_parms.pl1 get_entry_point_dcl_.pl1 edit_proj.pl1 get_io_segs.pl1 edit_proj_.pl1 get_mcm_meters.pl1 emacs.pl1 get_pvtx.pl1 emacs_data_.cds get_ttt_info_.pl1 emacs_rmail_.lisp get_user_.pl1 enter_abs_request.pl1 get_userid_.pl1 enter_abs_request_.pl1 hasp_dump_.pl1 enter_imft_request.pl1 hasp_stream_.pl1 enter_output_request.pl1 hasp_ws_sim_driver_.pl1 eor_cv6_7_.pl1 hc_dmpr_primitives.pl1 eor_cv7_8_.pl1 hc_load_mpc.pl1 eor_cv8_9_.pl1 hcom_process_seg_.pl1 evaluate.pl1 head_sheet_.pl1 expand_as_ia_audit_info_.pl1 heals_mos_edac_reports_.pl1 expand_channel_audit_info_.pl1 help.pl1 expand_dial_serv_audit_info_.pl1 help_.pl1 expand_pnt_audit_info_.pl1 help_rql_.pl1 ext_code_generator.pl1 ibm2780_conv_.alm ext_parse.pl1 ibm3780_conv_.alm fast_run_unit_manager_.pl1 ibm_tape_io_.pl1 fill_vol_extents_.pl1 im_basic_search.pl1 fim_util.alm imft_cir_mir_commands_.pl1 find_dict_word_.pl1 imft_default_rqt_.pl1 find_file_partition.pl1 imft_driver_.pl1 find_partition.pl1 imft_et_.alm find_partition_.pl1 imft_find_input_switch_.pl1 find_rpv_subsystem.pl1 imft_io_.pl1 fnp_init.pl1 imft_receive_object_.pl1 fnp_multiplexer.pl1 imft_transmit_object_.pl1 fnp_util.pl1 imft_tty_.pl1 format_attributes_.pl1 init_branches.pl1 format_disk_pack.pl1 init_clocks.pl1 format_list_parse.pl1 init_disk_pack_.pl1 forum_list_meetings.pl1 init_early_config.pl1 forum_requests_.pl1 init_empty_root.pl1 forum_search_list_default_.cds init_hc_part.pl1 free_store.alm init_lvt.pl1 fs_standard_object_.pl1.pmac init_partitions.pl1 fsout_vol.pl1 init_printer_.pl1 fst_command_processor_.pl1 init_proc.pl1 fst_cv_line_num_.pl1 init_pvt.pl1 fst_edit_.pl1 init_root_vols.pl1 fst_help_.pl1 init_scavenger_data.pl1 fst_info_.pl1 init_scu.pl1 fst_process_overseer_.pl1 init_syserr_log.pl1 fst_util_.pl1 init_toehold.pl1 ftp_dialup_.pl1 init_vol_header_.pl1 ftp_misc_.alm init_volmap_seg.pl1 g115_conv_.alm initialize_process_.pl1 gcos_queue_job_.pl1 instr_speed.pl1 general_ready.pl1 io_daemon_account_.pl1 generate_mst.pl1 io_reconfig.pl1 Module Changes for MR12.2 A-8 SIB12.2 io_semantics.pl1 logical_volume_manager.pl1 ioi_init.pl1 login_server_overseer_.pl1 ioi_masked.pl1 ls_dump_.pl1 ioi_page_table.pl1 lsm_fs_.pl1 iom_connect.alm lv_request_.pl1 iom_error.pl1 mail_errfiles.pl1 iom_overhead.pl1 mail_table_mgr_.pl1 ips_.alm make_sdw.pl1 is_legal_proj.pl1 manage_volume_pool.pl1 isolts_.pl1 match_star_name_.pl1 isolts_err_log_.pl1 mc_commands_.pl1 kermit.pl1 mc_tty_.pl1 kermit_comm_mgr_.pl1 mc_wakeups_.pl1 kermit_get_filenames_.pl1 mcs_trace.pl1 kermit_log_mgr_.pl1 mcs_version.pl1 kermit_mode_mgr_.pl1 mdx.pl1 kermit_pad_.pl1 memo.pl1 kermit_receive_.pl1 memo_repeat_.pl1 kermit_receive_request_.pl1 merge_ascii.pl1 kermit_remote_requests_.pl1 merge_volume_log.pl1 kermit_send_.pl1 message_facility_.pl1 kermit_send_request_.pl1 mlsys_parse_control_args_.pl1 kermit_server_.pl1 mlsys_parse_text_.pl1 kermit_server_request_.pl1 mlsys_search_list_default_.cds kermit_xfer_modes_.pl1 monitor_cache.pl1 l6_tran_overseer_.pl1 monitor_sys_log_wakeup_.pl1 l6_tran_util_.pl1 mowse_io_.pl1 lar_util_.pl1 mowse_io_call_control_.pl1 lg_ctl_.pl1 mrds_data_.cds linus_create_data_file.pl1 mrds_dm_authorization.pl1 linus_create_list.pl1 mrds_dm_db_secured.pl1 linus_data_.cds mrds_dm_open.pl1 linus_parse_file.pl1 mrds_dsl_close.pl1 linus_store.pl1 mrds_dsl_compile.pl1 linus_store_from_data_file.pl1 mrds_dsl_create_res_copy.pl1 linus_table.pl1 mrds_dsl_db_openings.pl1 linus_write.pl1 mrds_dsl_declare.pl1 linus_write_data_file.pl1 mrds_dsl_define_temp_rel.pl1 lisp_segment_manager_.pl1 mrds_dsl_delete.pl1 list_abs_requests.pl1 mrds_dsl_delete_se.pl1 list_delegated_projects.pl1 mrds_dsl_dl_fscope.pl1 list_extra_personids.pl1 mrds_dsl_gen_srch_prog.pl1 list_help.pl1 mrds_dsl_get_attribute_list.pl1 list_imft_requests.pl1 mrds_dsl_get_builtins.pl1 list_partitions.pl1 mrds_dsl_get_fn_info.pl1 list_sub_tree.pl1 mrds_dsl_get_population.pl1 list_tape_contents.pl1 mrds_dsl_get_relation_list.pl1 list_vols.pl1 mrds_dsl_get_rslt_info.pl1 load_ctl_.pl1 mrds_dsl_get_scope.pl1 load_ctl_status.pl1 mrds_dsl_get_version.pl1 load_fnp_.pl1 mrds_dsl_init_res.pl1 load_mpc.pl1 mrds_dsl_init_select_area.pl1 lock_volmap.alm mrds_dsl_make_literal.pl1 Module Changes for MR12.2 A-9 SIB12.2 mrds_dsl_modify.pl1 pdir_volume_manager_.pl1 mrds_dsl_open.pl1 pdt_copy.pl1 mrds_dsl_optimize.pl1 pdt_counter_check.pl1 mrds_dsl_permute.pl1 pfm_utils_.pl1 mrds_dsl_ready_all.pl1 pl1_abs.pl1 mrds_dsl_retrieve.pl1 pl1_operators_.alm mrds_dsl_search.pl1 pl1_symbol_print.pl1 mrds_dsl_set_fscope.pl1 pl1_version.cds mrds_dsl_set_scope.pl1 plio2_put_util_.pl1 mrds_dsl_set_user_vals.pl1 pnotice_paths_.pl1 mrds_dsl_store.pl1 poll_fnp.pl1 mrds_dsl_thread_fn_list.pl1 poll_mpc.pl1 mrds_dsl_translate.pl1 pps_.pl1 mrds_dsm_msmi.pl1 pps_close.pl1 mrds_error_.alm pps_control.pl1 mrds_rst_format_file.pl1 pps_conv_.alm mrds_rst_proc_ctl_args.pl1 pps_detach.pl1 mseg_check_access_.pl1 pps_modes.pl1 mseg_fs_interface_.pl1 pps_open.pl1 mtape_check_status_.pl1 pps_put_chars.pl1 mtape_io_.pl1 pps_report_man_.pl1 mtape_iox_.pl1 print.pl1 mtape_mount_cntl_.pl1 print_apt_entry.pl1 mtdsim_.pl1 print_configuration_deck.pl1 mu_cursor_manager_.pl1 print_conv_.alm mu_database_index.pl1 print_imft_sites.pl1 mu_get_tuple.pl1 print_link_info.pl1 mu_retrieve.pl1 print_motd.pl1 mu_sec_init_res.pl1 print_pdt.pl1 mu_sec_make_res.pl1 print_projfile.pl1 mu_sec_reg_user.pl1 print_sat.pl1 mu_store.pl1 printer_driver_.pl1 multiplexer_mgr_.pl1 privileged_mode_ut.alm network_accounting_.pl1 probe_info_requests_.pl1 new_proj.pl1 process_dir.pl1 obs_reconfigure.pl1 process_overseer_.pl1 ocu_.pl1 program_interrupt.pl1 old_imft_io_.pl1 proj_mtd.pl1 operator_com_channel_cmds_.pl1 proj_usage_report.pl1 operator_mc_cmds_.pl1 project_start_up_.pl1 operator_process_cmds_.pl1 prt_conv_.alm output_request_.pl1 prtdim_attach.pl1 overlay.pl1 prtdim_changemode.pl1 pa_search_list.pl1 prtdim_eurc_util.pl1 page_error.alm prtdim_eurc_write.pl1 page_fault.alm prtdim_order.pl1 parse_ftp_login_line_.pl1 prtdim_util.pl1 parse_login_line_.pl1 prtdim_write.pl1 partition_io.pl1 punch_driver_.pl1 pascal_operators_statics_.cds purge_volume_log.pl1 pc_check_tables_.pl1 put_field_.alm pc_deposit.pl1 pvname_to_pvtx_.pl1 pc_recover_sst.pl1 pxss.alm Module Changes for MR12.2 A-10 SIB12.2 query.pl1 rmdb_delete_attribute.pl1 quota.pl1 rmdb_delete_domain.pl1 rbf_.pl1 rmdb_ready_db.pl1 rc_messages.cds rmdb_rq_delete_object.pl1 rcp_access_kernel_setup.pl1 rmdb_rq_ready_db.pl1 rcp_audit.pl1 run_.pl1 rcp_compute_aim_mode.pl1 salvage_pv.pl1 rcp_disk_.pl1 sc_request_table_.alm rcp_init.pl1 scas_init.pl1 rcprm_find_resource_.pl1 scavenge_vol.pl1 rdm_data_.cds scavenge_volume.pl1 rdm_mbx_requests_.pl1 scavenger.pl1 read_disk.pl1 scs_and_clock_init.pl1 read_disk_label.pl1 sdm_data_.cds reassign_work_classes_.pl1 sdm_mbx_requests_.pl1 rebuild_pvolog.pl1 search_ast.alm receive_file_.pl1 search_paths_.pl1 reclassify.pl1 search_sat_.pl1 reconfig.pl1 segment_mover.pl1 reconfigure.pl1 send_message.pl1 record_to_vtocx.pl1 send_system_message_.pl1 recover_volume_log.pl1 set.pl1 reload.pl1 set_disk_table_loc.pl1 reloader.pl1 set_search_paths.pl1 remote_driver_.pl1 set_sons_lvid.pl1 remote_printer_.pl1 set_translator_search_rules.pl1 remote_punch_.pl1 set_volume_log.pl1 remote_teleprinter_.pl1 set_work_class.pl1 rename.pl1 shutdown_file_system.pl1 rename_proj.pl1 spg_fs_info_.pl1 reorder_archive.pl1 spool_conv_.alm reset_cdt_meters.pl1 spool_driver_.pl1 reset_disk_meters.pl1 spooling_dim_order_.pl1 reset_proj.pl1 spooling_dim_write_.pl1 reset_soos.pl1 spooling_dim_xtatch_.pl1 reset_usage.pl1 ssu_listen_.pl1 resource_usage.pl1 start_cpu.pl1 restore_pdt_access.pl1 start_dump.pl1 retrieve_from_volume_.pl1 statement_type.pl1 retv_util.pl1 status.c retv_vol_control_.pl1 status.pl1 ring_0_peek.pl1 stock.alm ringbr_.pl1 stock_man.pl1 rldr_check_pvol_.pl1 stop_cpu.pl1 rldr_finish_.pl1 structure_lib_mgr_.pl1 rldr_input_.pl1 structure_library_1_.cds rldr_label_.pl1 structure_library_2_.cds rldr_vtoc_buffer_.pl1 structure_library_4_.cds rldr_vtoc_header_.pl1 structure_library_5_.cds rlm_get_tuple_id.pl1 sty_mpx.pl1 rmdb_copy_relation.pl1 suffix_forum_.pl1 rmdb_create_and_pop_rel.pl1 sus_signal_handler_.pl1 rmdb_delete_all.pl1 sweep.pl1 Module Changes for MR12.2 A-11 SIB12.2 sweep_pv.pl1 uc_logout_.pl1 switch_on.pl1 uc_ls_create_request_.pl1 system_comm_meters.pl1 uc_ls_destroy_request_.pl1 system_info_.pl1 uc_ls_dial_request_.pl1 ta_file_io_.pl1 uc_ls_disconnect_request_.pl1 tail_sheet_.pl1 uc_ls_list_request_.pl1 tape_io_interpret_.pl1 uc_ls_new_proc_request_.pl1 tape_ioi_io.pl1 uc_ls_operator_request_.pl1 tc_input.pl1 uc_ls_validate_request_.pl1 tc_io_.pl1 uc_proc_term_handler_.pl1 ted4.alm uc_set_pit_tty_info_.pl1 ted_.pl1 uc_setup_process_connect_.pl1 ted_command_.pl1 up_cdt_.pl1 tedaddr_.pl1 up_mgt_.pl1 tedhelp_.pl1 up_pdt_.pl1 tedmgr_.pl1 up_sat_.pl1 tedsort_.pl1 up_sysctl_.pl1 tedutil_.pl1 upd_install_task_.pl1 terminal_report.pl1 update_vtoce.pl1 test_fnp.pl1 usage_total.pl1 tolts_file_util_.pl1 user.pl1 tolts_init_.pl1 user_info_.pl1 tolts_pcd_.pl1 user_table_mgr_.pl1 trim_wordlist.pl1 v2pl1.pl1 tssi_.pl1 vacate_pv.pl1 ttt_info_.pl1 value_get.pl1 tty_analyze.pl1 verify_dump_volume.pl1 tty_dump.pl1 verify_label_.pl1 tty_index.pl1 verify_lock.pl1 tty_interrupt.pl1 vip7760_dump_.pl1 tty_io_.pl1 vm_vio.pl1 tty_io_call_control_.pl1 volmap.alm tty_modes.pl1 volmap_page.alm tty_printer_conv_.alm volmap_util.pl1 tty_read.pl1 volume_cross_check.pl1 tty_space_man.pl1 vt1xx_ctl_util_.pl1 tty_write.pl1 vtoc_interrupt.pl1 tut_bottom_.pl1 vtoc_man.pl1 tut_getting_help_.pl1 vtoce_stock_man.pl1 tut_giving_commands_.pl1 wioctl_.pl1 tut_log_in_.pl1 wired_shutdown.pl1 tut_mail_.pl1 write_control_form_.pl1 tut_main_menu_.pl1 write_user_usage_report.pl1 tut_storing_information_.pl1 ws_packet_receiver_.pl1 tut_wordpro_.pl1 x25_analyze_.pl1 tut_writing_text_.pl1 x25_mpx.pl1 tutorial.pl1 xforum.pl1 uc_cleanup_network_dials_.pl1 xforum_data_.cds uc_create_process_.pl1 xforum_find_path_.pl1 uc_create_process_check_.pl1 xforum_help_.pl1 uc_dial_.pl1 xforum_list_meetings_.pl1 uc_list_disconnected_procs_.pl1 xforum_status_.pl1 uc_login_.pl1 xforum_user_profile.pl1 Module Changes for MR12.2 A-12 SIB12.2 xmail.pl1 xmail_forward_msg_.pl1 xmail_Consult_Files_.pl1 xmail_get_choice_.pl1 xmail_Executive_Mail_.pl1 xmail_get_dyn_choice_.pl1 xmail_Mail_File_Maint_.pl1 xmail_im_mgr_.pl1 xmail_Process_Mail_.pl1 xmail_multics_mode_.pl1 xmail_Review_Defaults_.pl1 xmail_prepare_msg_.pl1 xmail_Review_Mlist_.pl1 xmail_print_.pl1 xmail_Review_Outgoing_.pl1 xmail_process_user_msg_.pl1 xmail_Review_Printing_.pl1 xmail_rebuild_value_seg_.pl1 xmail_Review_Processing_.pl1 xmail_reply_msg_.pl1 xmail_Send_Mail_.pl1 xmail_review_defers_.pl1 xmail_create_mlist_.pl1 xmail_select_file_.pl1 xmail_delete_dreply_.pl1 xmail_select_msgs_.pl1 xmail_dir_manager_.pl1 xmail_send_mail_print_msg_.pl1 xmail_discard_file_.pl1 xmail_send_msg_.pl1 xmail_display_help_.pl1 xmail_send_stored_msg_.pl1 xmail_display_menu_.pl1 xmail_sw_.pl1 xmail_dprint_mlist_.pl1 xmail_undelete_msgs_.pl1 xmail_dprint_msgs_.pl1 xmail_update_mlist_.pl1 xmail_dyn_menu_.pl1 xmail_validate_.pl1 xmail_emacs_ext_main_.lisp xmail_value_.pl1 xmail_error_.pl1 xmail_window_manager_.pl1 xmail_file_msgs_.pl1 xmail_write_msgs_.pl1 Module Changes for MR12.2 A-13 SIB12.2 _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. APPENDIX B 1. Enter the Total OnLine Test System (TOLTS): FORMATTING DISKS WITH MTR ox bound_tolts_$tolts_ *olts executive version 810301 on 820812 at 20.071 2. Enter the MPC OnLine Test Subsystem (MOLTS): This appendix describes a procedure for formatting disk *enter "polts", "molts", "colts", "isolts", "quit", or "msg" packs using the Media Test ??? ox molts Routines (MTRs). The procedure utilizes an annotated script 3. List the disk configuration which shows typical input and for the disk string which output. Because the formatting formatting will be done procedures differ for MSU0451 (because of page and MSU0500/0501 devices, constraints, the following separate scripts are provided. message is not an exact In the scripts, input typed by copy of that which is the user is preceded by a ox displayed by the system): (bullet). ??? 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 Formatting Disks With MTR B-1 SIB12.2 4. Enter MTR test 6 to format and5.teTsthethe MSfoUl04l5ow1idngevice:output describes steps taken by ??? ox test mmt12020t6 MTR test 6 to attach the disk drive and mount the where "test mmt12020t6" is pack for writing: a sample of the input format "test mmtICCDDtT": *molts executive versions 820601 820701 on 820812 at 19.97 *0(mmt12020) short wait, allocation queued mmt identifies the MTR *0(mmt12020) start tmt65a-rmc1, ttldat 820331, phy./log. id t//04 test package *0(mmt12020) start tmt65b-rmc2, ttldat 820331, phy./log. id t//04 *0(mmt12020) start tmt65c-rmc3, ttldat 820401, phy./log. id t//04 ICC gives the IOM *0(mmt12020) start tmt65d-rmc4, ttldat 820405, phy./log. id t//04 number (0 = IOM A, *0(mmt12020) start tmt65e-rmc5, ttldat 820421, phy./log. id t//04 1 = IOM B, etc) and *0(mmt12020) start tmt65f-rmc6, ttldat 820331, phy./log. id t//04 channel number (in *0(mmt12020) decimal) of a rmc6 is at your service to format a disk pack - channel by which *0(mmt12020) the device to be ** write permission granted *** formatted can be *0(mmt12020) addressed. It must ** begin format pack *** be one of those the test will format all tracks on the pack. format will shown in the output defined by device type. bad tracks will be marked defective of "test pcd" in (no alt. assigned). step 3. In the *0(mmt12020) sample input above, system device code = .ds450 "120" is IOM B, channel 20. 6. Answer MTR initialization questions (not a restart, DD gives the device normal formatting, and use number (in decimal) 3 write patterns during of the device to be testing): tested. In the sample input, it is *0(mmt12020) device 20 is this a restart? enter (y or n) - ox n (dskb_20). *0(mmt12020) select (f)ast or (n)ormal format? (f)ast format is designed T gives the number of for data security erase and/or test purposes. (n)ormal format the MTR test to be is designed for disk packs that are going to be used in systems run. In this case, applications. enter (f or n) - ox n test 6 should be *0(mmt12020) run to format/test select from "1" to "7" write patterns? enter (1 thru 7) - ox 3 a pack. 7. At this point, formatting of the pack begins: *0(mmt12020) ** begin disk pack format *** Formatting Disks With MTR B-2 SIB12.2 8. After the message in Step 7 9. When the .go option is is displayed, press the entered in Step 8, MTR BREAK key to interrupt reports the current formatting operations. location being formatted When MOLTS prompts for and displays the defective input, set test options to: tracks found. It then asks report the current if you want to continue cylinder/head (CCC/HH) formatting: address; display CCC/HH for transient errors; report *0(mmt12020) test progress every 100 format function current addr. = 007/00 cylinders, with summary *0(mmt12020) reports attached. format function current addr. = 007/00 *0(mmt12020) ox ** rmc6 - summary report *** ??? ox test momt12020.r no tracks were formatted defective *0(mmt12020) where "test momt12020.r" is adsoaympoulewoanftththeeintepsutt tfoormcoatntinue? enter (y or n) - ox y "test momtICCDD.O": 10. After every 100 cylinders momt identifies are formatted, MTR displays request to set defective tracks found. options For example, the final summary displayed just ICCDD are the IOM, before formatting Channel and completes, looks like: Device numbers given in Step 4. *0(mmt12020) rmc6 has formatted tracks "000/00 thru 700/00" .r is the first *0(mmt12020) option, to ** rmc6 - summary report *** report current no tracks were formatted defective CCC/HH location. *0(mmt12020) rmc6 has formatted tracks "000/00 thru 800/00" Set the remaining options *0(mmt12020) when prompted: ** rmc6 - summary report *** no tracks were formatted defective *0(mmt12020) t6 enter options: ox*0.i(mmt12020) *0(mmt12020) t6 enter options: ox**.edisk pack format complete *** *0(mmt12020) t6 enter options: ox .s *0(mmt12020) t6 enter options: ox .t *0(mmt12020) t6 enter options: ox .go Formatting Disks With MTR B-3 SIB12.2 11. After formatting is 12. When testing is complete, complete, MTR begins termination summary reports testing the tracks on the are displayed: formatted pack. Defective tracks are usually *0(mmt12020) encountered only during the ** normal termination summary reports *** testing phase. Error *0(mmt12020) summaries are displayed ** rmc6 - summary report *** after every 100 cylinders defective - marginal data field on std track have been tested. 217/10 *0(mmt12020) start media test phase ** rmc6 - summary report *** *0(mmt12020) defective - unrec. data field on std track rmc6 has tested tracks "000/00 thr2u44/10060,/0240"5/06 *0(mmt12020) *0(mmt12020) ** rmc6 - summary report *** ** rmc6 - summary report *** no tracks were formatted defectivereclaimed - reformatted and certified *0(mmt12020) 246/06 rmc6 has tested tracks "000/00 thru 200/00" *0(mmt12020) 13. MTR then asks if you want ** rmc6 - summary report *** to select a new test no tracks were formatted defective (answer "y" for yes): *0(mmt12020) rmc6 has tested tracks "000/00 thr*u0(m3m0t01/0200"20) *0(mmt12020) want to select a new test? ** rmc6 - summary report *** enter (y or n) - ox y defective - marginal data field on std track 217/10 14. MTR then displays *0(mmt12020) information describing how ** rmc6 - summary report *** to select the next test: defective - unrec. data field on std track 244/06,245/06 *0(mmt12020) *0(mmt12020) rmc6 will go into waiting! ** rmc6 - summary report *** select test (t1 thru t6) reclaimed - reformatted and certifeniteder test no. thru standard option call (test momticcddtx) - 246/06 *0(mmt12020) waiting Formatting Disks With MTR B-4 SIB12.2 15. To actually select the next 17. MTR then briefly describes test, press the BREAK key the subtest, and asks if and wait for the MOLTS you want to continue prompt. Then select test (answer "y" for yes) 3, which assigns alternate tracks for those tracks *0(mmt12020) found to be defective ** begin subtst 4 *** above. assign alternate tracks on the device a) subtst will search thru all standard tracks looking for ox tracks marked defective (no alternate assigned). ??? ox test momt12020t3 b) when a track marked defective (no alternate assigned) is detected, the subtst will stop and process this track. where "test momt12020t3" is a sca)mtplhee aolftterhneatineputrtacfkorpmartocessor will go out to the alternate "test momtICCDDtT": track cylinders and find the first available alternate. it will mark the track as assigned alternate. then it will momt identifies mark the standard track as defective (alt. assigned). request to set d) the search process will terminate after the last standard options track completes testing and/or processing. do you want the subtst to continue? enter (y or n) - ox y ICCDD are the IOM, Channel and 18. MTR then asks for Device numbers permission to overwrite the given in Step 4. pack's label (answer "y" for yes): tT gives the number of the next test *0(mmt12020) to run. ** rmc3 - label obliterate warning *** all sub tests in rmc3 will overwrite the system Test 3 initialization label on track zero. displays the following do you want the sub test to continue? enter (y or n) - ox y information: 19. MTR then asks if you are *0(mmt12020) start tmt65e-rmc5, ttldarets8t2ar0t42in1g, p(ahyn.sw/lerog."nid" ft/or/04 *0(mmt12020) start tmt65d-rmc4, ttldanot):820405, phy./log. id t//04 *0(mmt12020) start tmt65c-rmc3, ttldat 820401, phy./log. id t//04 *0(mmt12020) 16. Select subtest 4 of test 3, system device code = .ds450 to assign alternates to all *0(mmt12020) defective tracks: is this a restart? enter (y or n) - ox n *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 B-5 SIB12.2 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 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 *olts executive version 810301 off 820812 at 21.375 r 21:37 1107.348 1162 Formatting Disks With MTR B-6 SIB12.2 _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 where "test mmt12827t6" is a sample of the input format _P_A_C_K_S "test mmtICCDDtT": The following script shows how mmt identifies the to run MTR tests 6 and 7 to MTR test package format and test an MSU0500 or MSU0501 disk drive, and to ICC gives the IOM assign alternates to tracks number (0 = IOM found defective during testing. A, 1 = IOM B, etc) and channel The MPC normally treats an number (in MSU0500 or MSU0501 disk drive as decimal) of two separately addressable achannel by devices. However, MTR formats which the device and tests both logical devices to be formatted during a single invocation, can be referring to one as the "odd addressed.It device" (e.g., dskc_27) and the must be one of second as the "even device" those shown in (e.g., dskc_28). MTR refers to the output of both logical devices as a single "test pcd" in "head assembly" or "hda". step 3. In the sample input 1. Enter the Total OnLine Test System (TOLTS): above, "128" is IOM B, channel ox bound_tolts_$tolts_ 28. *olts executive version 810301 on 820812DDat 20.0gi71ves the device number (in 2. Enter the MPC OnLine Test decimal) of the Subsystem (MOLTS): device to be tested. In the *enter "polts", "molts", "colts", "isolts", "quistam"p,leori"npmsutg", it ??? ox molts is device 27 (dskc_27). 3. List the disk configuration: Always give the device number of ??? ox test pcd the "odd device" associated with peripheral configuration: the disk drive. dskc 501 32 units; starting with deviceTno. 1 gives the number 028xx primary channel of 4 logical channels oofn mthpce msMpTcR test 030xx secondary channel of 4 logical channelstoonbempcrunm.spc In 130xx secondary channel of 4 logical channelsthoisn mpccasems,pdtest 128xx primary channel of 4 logical channels o6nsmhopculdmspdbe run to format/test 4. Enter MTR test 6 to format the drive. and test the entire MSU0500 or MSU0501 device: ??? ox test mmt12827t6 Formatting Disks With MTR B-7 SIB12.2 5. The following output 7. At this point, formatting of the pack begins: describes steps taken by MTR test 6 to attach the *0(mmt12827) disk drive for writing: ** begin hda format *** *molts executive versions 8206018.8207Af01teornth82e08me05ssaagte2i0n.08Step 7 *0(mmt12827) short wait, allocation qiuseueddisplayed, press the *0(mmt12827) short wait, allocation qBuREeAueKd key to interrupt *0(mmt12827) start tmt67a-mtr1, ttldaftor8ma20tt40i1ng, phy./lopoge.raitdionts//.04 *0(mmt12827) start tmt67b-mtr2, ttldaWthe8n204M01OL,TpShyp./rlomogpt.sid ft/o/r04 *0(mmt12827) start tmt67c-mtr3, ttldaintp8u2t,04s0e2,t tpheyst./lopogt.ionids tt/o:/04 *0(mmt12827) start tmt67d-mtr4, ttldaretp8or20t405, phthye./log.ciudrretn//t04 *0(mmt12827) start tmt67e-mtr5, ttldactyl8in20de42r1/h,epadhy./log.(CiCdC/HtH//)04 *0(mmt12827) start tmt67f-mtr6, ttldaadtd8r2es0s40;5,dipsphyl.ay/lCogCC./HiHd tf/or/04 *0(mmt12827) transient errors; report mtr6 is at your service to format a ptehystsicaprlogdervesisce -every 100 *0(mmt12827) cylinders, with summary ** write permission granted *** reports attached. *0(mmt12827) ** begin upgrade/downgrade hda ***ox the test will format all tracks on??t?hexohtdae.st tmohemt1fo2r82m7at.twill be defined by device type. bad tracks will be marked defective (no alternate). where "test momt12020.r" is a sample of the input 6. Answer MTR initialization format "test momtICCDD.O": questions (ok to format with 512 words per sector, momt identifies not a restart, normal request to set formatting, and use 3 write options patterns during testing): ICCDD are the IOM, *0(mmt12827) Channel and device pair are configured as msu0501's Device numbers the hda will be formatted in (512) words/sector.given in Step 4. is this correct? enter (y or n) - ox y .r is the first *0(mmt12827) option, to is this a restart? report current enter (y or n) - ox n CCC/HH location. *0(mmt12827) select (f)ast or (n)ormal format? Set the remaining options (f)ast format is designed for data sewhcuenritpyrompted: erase and/or test purposes. (n)ormal format is designed for hd*0a'(msmtto128be27u)setd6 enter options: ox .e in systems applications. *0(mmt12827) t6 enter options: ox .s enter (f or n) - ox n *0(mmt12827) t6 enter options: ox .i *0(mmt12827) *0(mmt12827) t6 enter options: ox .r select from "1" to "7" write patte*0rn(ms?mt12827) t6 enter options: ox .go enter (1 thru 7) - ox 3 Formatting Disks With MTR B-8 SIB12.2 9. When the .go option is 10. After every 100 cylinders entered in Step 8, MTR are formatted, MTR displays reports the current defective tracks found. location being formatted For example, the final and displays the defective summary displayed just tracks found. It then asks before formatting if you want to continue completes, looks like: formatting: *0(mmt12827) *0(mmt12827) mtr6 has formatted tracks "000/00 thru 800/00" format function current addr. = 00*40(/0m0mt12827) *0(mmt12827) ** mtr6 - hda condition summary report *** format function current addr. = 004--/-00msu0501 odd device report (27) --- *0(mmt12827) defective - error logging track info ** statistics from format of hda *00**6/19,028/19,284/01,370/12 summary for msu0501 devices (27/28*)0(mmt12827) no. of tracks with 1 defect skip **= 1mtr6 - hda condition summary report *** no. of tracks with 2 defect skips =--0- msu0501 even device report (28) --- no. of tracks with 3 defect skipsde=f0ective - error logging track info no. of new defect skips generated00=80/19,026/19,096/05,174/16,381/06,736/09,778/19 total defect skips processed*0=(1mmt12827) odd device defective tracks **= 0statistics from format of hda *** even device defective tracks su=m0mary for msu0501 devices (27/28) physical device defective tracks no=.0of tracks with 1 defect skip = 33 totalno=.0of tracks with 2 defect skips = 2 *0(mmt12827) no. of tracks with 3 defect skips = 0 ** mtr6 - hda condition summary renopo.rtof**n*ew defect skips generated = 0 no tracks were marked defective. total defect skips processed = 37 *0(mmt12827) odd device defective tracks = 4 do you want the test to continue?even device defective tracks = 7 enter (y or n) - ox y physical device defective tracks = 0 total = 11 *0(mmt12827) ** hda format complete *** Formatting Disks With MTR B-9 SIB12.2 11. After formatting is 12. When testing is complete, complete, MTR begins termination summary reports testing the tracks on the are displayed: formatted pack. Error summaries are displayed *0(mmt12827) after every 100 cylinders ** normal termination summary reports *** have been tested. *0(mmt12827) ** mtr6 - hda condition summary report *** start media test phase --- msu0501 odd device report (27) --- *0(mmt12827) defective - error logging track info mtr6 has tested tracks "000/00 thr00u61/1090/,0020"8/19,284/01,370/12,816/04,818/04,832/04 *0(mmt12827) *0(mmt12827) ** mtr6 - hda condition summary re**pomrttr*6**- hda condition summary report *** --- msu0501 odd device report (27)------msu0501 odd device report (27) --- defective - error logging track inrefoclaimed - repaired data field 006/19,028/19,284/01,370/12,816/0476,84/1809/0,84,3083/02/404 *0(mmt12827) *0(mmt12827) ** mtr6 - hda condition summary re**pomrttr*6**- hda condition summary report *** --- msu0501 even device report (28-)----m-su0501 even device report (28) --- defective - error logging track indefofective - error logging track info 008/19,026/19,096/05,174/16,381/0600,78/3619/0,09,2677/18/9,19096/05,174/16,381/06,736/09,778/19 *0(mmt12827) *0(mmt12827) ** mtr6 - hda condition summary re**pomrttr*6**- hda condition summary report *** --- msu0501 even device report (28-)----m-su0501 even device report (28) --- reclaimed - repaired data field reclaimed - repaired data field 042/15 042/15,762/09,818/08 *0(mmt12827) *0(mmt12827) ** statistics from format of hda *****statistics from format of hda *** summary for msu0501 devices (27/28s)ummary for msu0501 devices (27/28) no. of tracks with 1 defect skip n=o.42of tracks with 1 defect skip = 42 no. of tracks with 2 defect skipsno=.2of tracks with 2 defect skips = 2 no. of tracks with 3 defect skipsno=.0of tracks with 3 defect skips = 0 no. of new defect skips generatedno=.1of new defect skips generated = 5 total defect skips processed = 47total defect skips processed = 51 odd device defective tracks =od7d device defective tracks = 7 even device defective tracks ev=e7n device defective tracks = 7 physical device defective tracks ph=y0sical device defective tracks = 0 total = 14 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 B-10 SIB12.2 14. MTR then displays 15. To actually select the next information describing how test, press the BREAK key to select the next test: and wait for the MOLTS prompt. Then select test *0(mmt12827) 7, which assigns alternate mtr6 will go into waiting! tracks for those tracks select test (t1 thru t7) found to be defective enter test no. thru standard option cabalovle(.test momticcddtx) - *0(mmt12827) waiting 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 Formatting Disks With MTR B-11 SIB12.2 16. Select subtest 1 of test 7, 19. MTR then begins displaying to assign alternates to all summary reports after every defective tracks: 100 cylinders are checked for alternate assignments: *0(mmt12827) mtr7 is at your service *0(mmt12827) for special physical device formatmttirn7gh-as processed tracks "000/00 thru 100/00" select the subtst *0(mmt12827) a) subtst 1 - assign all alternate**trmtacr7ks- subtst 1 summary report *** b) subtst 2 - create & write loggin--g-tmrsacu0ks501 odd device report (27) --- enter (1 thru 2) - ox 1 defective - alternate track assigned def alt def alt 17. MTR then briefly describes cyl/hd cyl/hd cyl/hd cyl/hd the subtest, and asks if 006/19 840/00 028/19 840/03 you want to continue *0(mmt12827) (answer "y" for yes): ** mtr7 - subtst 1 summary report *** --- msu0501 even device report (28) --- *0(mmt12827) defective - alternate track assigned ** begin subtst 1 *** def alt def alt assign alternate tracks on the phycsylic/ahdl devicecytl/hehdsubtstcwylil/lhd cyl/hd search "all" standard tracks on th0e08h/1da9 for de84f0ec/0ti1ve (no0a26lt/.19 840/02 assigned). if any are found, it w09il6/l0a5ssign t84he0/014st available alternate to them. *0(mmt12827) 20. After alternate assignments do you want subtst (1) to continue? are complete, MTR displays enter (y or n) - ox y a summary report describing all alternates on the pack: 18. MTR then asks if you are restarting (answer "n" for *0(mmt12827) no): ** normal termination summary reports *** *0(mmt12827) *0(mmt12827) ** mtr7 - subtst 1 summary report *** is this a restart? --- msu0501 odd device report (27) --- enter (y or n) - ox n 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 Changes to IMFT B-12 SIB12.2 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 *olts executive version 810301 off 820806 at 00.165 r 00:16 5188.584 1038 Changes to IMFT B-13 SIB12.2 2) The following changes have been made to the enter_imft_request (eir) command: New control arguments have been added to the enter_imft_request (eir) APPENDIX C command and include: -date_time_after DT, -dtaf DT SIGNIFICANT CHANGES TO IMFT skips selected files and subtrees if their date_time_contents_modified value is older than the time selected by DT. This This release contains a new option is not applied to version (4.0) of the IMFT contents of subtrees. The facility. System administrators DT string must be should note the following: acceptable to the convert_date_to_binary_ subroutine. This option 1) The "version" keyword in facilitates selecting only the attach description for modified information to an IMFT driver will no reduce IMFT traffic. longer accept "old" or "new". The only values -skipped, -skpd that will be accepted are turns on the display of the "2.0", "3.0" or "4.0". objects that are skipped when the -date_time_after The 4.0 version of the IMFT option is used. facility is able to converse with drivers on -no_skipped, -nskpd other systems using turns off the display of previous versions. The the items that are skipped version keyword identifies when the date_time_after to the local driver what option is used. (Default) version the driver at the other end is using. Changes to IMFT C-1 SIB12.2 -delete, -dl deletes source IMMEDIATELY after it is successfully 3) Access checking has been transferred. expanded to require that proper explicit ACL entries -no_delete, -ndl must exist for both the does not delete objects. IMFT driver daemon and the (Default) user for all objects being transferred. This new -extend version will check all appends the contents of the objects in the subtree for source to the contents' end proper ACL when a directory of the target path. An is specified in the IMFT error occurs if the source request. An explicit ACL path is a nonfile. An entry is one which includes error occurs if the target both the person name and does not already exist. It the project name; ie, is incompatible with the "Smith..", ".Project." or -subtree option. ".." is no longer acceptable. Each object to -replace be transferred must have an replaces the entire file appropriate target path, rather than "Person.Project." ACL entry modifying its contents as for both the IMFT driver is done by -extend and and user. -update. (Default) This expanded ACL checking -update, -ud also includes that which is replaces the contents of done with the SITE.imft.acs the target path with those segment. Only the ACL for of the source without the user is required but it deleting the target path or must have a Person.Project. changing any of its entry with the appropriate attributes. An error "r" or "rw" access. occurs if the source path is a nonfile. An error See book.imft.compout in occurs if the target path the >doc>MR12.2 directory does not already exist. It on the release tapes for is incompatible with the more details. -subtree option. C-2 SIB12.2 CONTENTS (cont) Page CONTENTS Page iii SIB12.2 ----------------------------------------------------------- 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