MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MICRO,MINI,LARGE MFG: BASIC FOUR NACS TYPE(S): N094 MFG. MODEL(S): BOSS/VX BB90 CATEGORY: SOFTWARE DESC: O.S. & UTILITIES *** TABLE OF CONTENTS AS OF 03/29/95 *** FIB 00001.GPx Software Announcement [ WPSS-168 ]......................01/22/90 FIB 00002.BOSS/VX 1.0B Software Announcement - GPx 40 [ WPSS-172 ]....07/13/90 FIB 00003.GPx 70 Software Announcement [ WPSS-175 ]...................08/09/90 FIB 00004.BOSS/VX Software Announcement Rel. 1.0C for GPx 40 [ WPSS-1809/25/90 FIB 00005.GPx40 1.0D Software Announcement [ WPSS 184 ]..............09/28/90 FIB 00006.O.S. rel. 1.0A has a problem with 7270 terminal configuratio10/05/90 FIB 00007.GPx40 Notes and Cautions for 1.0B*21 [ WPSF 624 ]..........10/11/90 FIB 00008.GPx70 BOSS/VX 1.0A Notes and Cautions [ WPSF 631 ].........10/11/90 FIB 00009.Release 1.0A*60 Available for GPx70 [ WPSF 631 A1 ]........10/11/90 FIB 00010.File Corrupt after Restore on GPx70 [ WPSF 631 A2 ]........11/27/90 FIB 00011.Conversion Tips from Product Support........................11/28/90 FIB 00012.Fix for Operator Logging in in Upper Case/Manual Err........11/28/90 FIB 00013.Full User Partition after Panic on GPx70 ...................11/30/90 FIB 00014.Performance Issue using Multikeyed Files [ WPSF 671 ].......11/30/90 FIB 00015.GPx70 Root Filesystem Full Message..........................11/30/90 FIB 00016.Indexed Files Deleted by frepair on 1.0C - GPx40............11/30/90 FIB 00017.GPx40 Password Aging [ WPSF 667 ]..........................01/07/91 FIB 00018.Procedure to Delete root Password on GPx40 [ WPSF 668 ]....12/05/90 FIB 00019.Potential File Corruption on Open Files [ WPSF 650 ].......12/05/90 FIB 00020.Root CRON Entries [ WPSF 659R ].............................12/24/91 FIB 00021.Corrupted Files not Reported by fsck - GPx70 on 1.0A........12/14/90 FIB 00022.GPx70 SAR Change for a Months Performance History [ WPSF 67512/19/90 FIB 00023.Notes for GPx40 1.1A & GPx640 Announced [ WPSF 660 ]......03/05/91 FIB 00024.Command to Print the Man Pages [ WPSF 674 ]................01/08/91 FIB 00025.Root Partition Fills Up.....................................02/18/91 FIB 00026.GPx40 /dev Files Problems [ WPSF 660 A1 ]..................04/24/91 FIB 00027.1.1A Available for GPx70 Series.............................03/05/91 FIB 00028.1.1A Software Announcement for GPx Series 70 [ WPSS 190 ]..03/06/91 FIB 00029.BOSS/VS to BOSS/VX Conversion Tips [ WPSF 673 ]............03/06/91 FIB 00030.'fcopy/fmove' on 1.1A Destroys Program Files [ WPSF 660 A2 ]03/07/91 FIB 00031.Known GPx70 Printer (Spooler) Problems [WPSF 683]..........03/27/91 FIB 00032.Repair lpq.que file without rebooting.......................04/01/91 FIB 00033.lpstat -error command [ WPSF 690 ].........................04/02/91 FIB 00034.Use of UNIX Commands on Opened Files [ WPSF 679 ]..........04/03/91 FIB 00035.1.1A Software Announcement for GPx40 [ WPSS 191 ]..........04/04/91 FIB 00036.Release 1.1A Notes & Cautions...............................04/15/91 FIB 00037.GPX 70 Semaphore Deallocation problem [ WPSF 694 ].........04/25/91 FIB 00038.4222 Pitch Change, Configurable Parallel Printers [ WPSF 6604/24/91 FIB 00039.13xx to GPx 40 ITP files conversion problem [ WPSF 708 ]....05/15/91 FIB 00040.GPX 40 dosformat problems & sample dos commands [ WPSF 710 01/20/94 FIB 00041.1.1A*24.Update Release [ WPSF 709 ]........................05/21/91 FIB 00042.1.1B.OS Release Notice for GPx40 [ WPSF 727 ]...............08/16/91 FIB 00043.Reduce Number of 'sh' Processes [ WPSF 744 ]...............10/18/91 FIB 00044.GPx Dump Procedure [ WPSF 747 ].............................01/25/95 FIB 00045.File Corruption (ERR 14, -103) in Keyed Files...............12/24/91 FIB 00046.GPX40 & 70 File Check & Repair Procedure....................12/27/91 FIB 00047.Patch Tape 49 for Printer Hangs on 1.1B is Available........12/31/91 FIB 00048."fuser' Command on 1.1B-40/1.1A-70 works differently [ WPSF 05/22/92 FIB 00049.GPx Series 40 1.1B Software Announcement [ WPSS 194 ]......06/25/92 FIB 00050.GPx 70 1.2A Release Notes and Cautions [ WPSF 782 ]........12/14/94 FIB 00051.Release 1.1C available for GPx 2/3/4/640 Systems [ WPSF 803 11/23/92 FIB 00052.ERR -307 attempting to use any MBF utility..................12/28/92 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------Table Of Contents Pg01 of 02 FIB 00053.1/2" tape BASIC READ command requires SIZ= at 1.1C/1.2A [WPS12/30/92 FIB 00054.Release 1.1C Software Announcement for GPx Series 40 [ WPSS01/20/93 FIB 00055.Release 1.2A Software Announcement for GPx70 [WPSS 201]....08/12/93 FIB 00056.1.2A*07 available for GPx70.................................08/17/93 FIB 00057.Release 1.2A*08 available for GPx70 systems.................04/05/94 FIB 00058.DON'T use OS level 1.1C*9 on GPx240 systems!................12/02/94 FIB 00059.TCP/IP installation instructions for GPx40..................12/13/94 FIB 00060.BOSS/VX 1.1C*10 reguired for all GPx40 Sytems...............02/10/95 FIB 00061.Large filesystems fail to repair automatically - modify moun03/20/95 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------Table Of Contents Pg02 of 02 FIB 00001 01/22/90 *** GPx Software Announcement [ WPSS-168 ] *** Introducing the new GPxTM Series 40 Systems. The GPx Series 40 product line includes the GPx 340 and GPx 440 models. This new product line utilizes the BOSS/VXTM Level 1.0A Operating System, hardware and related software packages. This document contains the information to install and update the GPx Series 40 system, both hardware and software. Thereare also sections on customizing the system, determiningmemory requirements, analyzing performance problems, system dump procedures, operating system and utility overviews and other topics relatedd to the operation of the system. It is recommended that before installing a GPx Series 40 system, you first read this document. For information on ordering software, hardware and other related Marketing information please see Marketing Announcements for the United States and International listed below: BOSS/VX 1.0A FOR THE GPx 340 - INTERNATIONAL 498I BOSS/VX 1.0A FOR THE GPx 440 - INTERNATIONAL 502I BOSS/VX 1.0A FOR THE GPx SERIES 40 - DOMESTIC 785 US/C GPx 340 SYSTEM - INTERNATIONAL - 499I DOMESTIC - 786 US/C GPx 440 SYSTEM - INTERNATIONAL - 503I DOMESTIC - 793 US/C TABLE OF CONTENTS 1.0 PRODUCT OVERVIEW. . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 BASE PACKAGE OVERVIEW. . . . . . . . . . . . . . . . . . . . . . 3 2.0 SYSTEM START UP AND SHUTDOWN. . . . . . . . . . . . . . . . . . . . . 4 2.1 SYSTEM START-UP. . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2 SYSTEM SHUTDOWN. . . . . . . . . . . . . . . . . . . . . . . . . 5 3.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES. . . . . . . . . . . . . . . . . . . . . . 5 3.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM . . . . . . . . . . 5 3.1.1 SYSTEM DISK PARTITIONING. . . . . . . . . . . . . . . . . 9 3.2 UPDATE OF THE OPERATING SYSTEM . . . . . . . . . . . . . . . . .10 3.3 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD . . . .12 3.4 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES. . . . . .13 3.5 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES. . . . . . . . . . .15 3.5.1 PRESENTATION SERVICES . . . . . . . . . . . . . . . . . .16 3.5.1.1 PRESENTATION SERVICES CUSTOM MENUS . . . . . . .16 3.5.1.2 PRESENTATIN SERVICES FORM. . . . . . . . . . . .16 3.5.2 ORIGIN 2.1B*10 GPx INSTALLATION PROCEDURE . . . . . . . .17 3.5.2.1 INSTALLATION REQUIREMENTS. . . . . . . . . . . .17 3.5.2.2 NEW INSTALLATION OF ORIGIN 2.1B. . . . . . . . .18 3.5.2.3 UPDATING FROM 2.1A . . . . . . . . . . . . . . .20 3.5.2.4 UPDATING FROM 2.0A . . . . . . . . . . . . . . .21 3.5.2.5 UPDATING FROM 1.3B OR 1.3A . . . . . . . . . . .22 3.5.2.6 EXECUTING ORIGIN ON THE GPx. . . . . . . . . . .23 3.5.3 ORIGIN CONVERSION . . . . . . . . . . . . . . . . . . . .23 3.5.3.1 MPx TO GPx CONVERSION. . . . . . . . . . . . . .23 3.5.3.2 SPx TO GPx CONVERSION. . . . . . . . . . . . . .24 3.5.4 ORIGIN 2.1B*10 NEW FEATURES . . . . . . . . . . . . . . .25 3.5.5 TRANSLATION . . . . . . . . . . . . . . . . . . . . . . .26 3.5.6 DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . .29 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg001 4.0 HARDWARE INFORMATION. . . . . . . . . . . . . . . . . . . . . . . . .29 4.1 GPx SERIES 40 HARDWARE MINIMUM AND MAXIMUM CONFIGURATION CHART .29 4.1.1 GPx 340 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART.29 4.1.2 GPx 440 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART.29 4.2 JUMPER CONNECTIONS AND SWITCH SETTINGS . . . . . . . . . . . . .30 4.2.1 CCA CONVER AND PCBA REMOVAL . . . . . . . . . . . . . . .31 4.2.2 CENTRAL MICROPROCESSOR BOARD (CMB). . . . . . . . . . . .31 4.2.3 MEMORY EXPENSION BOARD (MXB). . . . . . . . . . . . . . .33 4.2.4 8/16 WAY CONTROLLER PCBA. . . . . . . . . . . . . . . . .34 4.2.5 SCSI CONTROLLER PCBA. . . . . . . . . . . . . . . . . . .35 4.2.6 INTERNAL MODEM PCBA . . . . . . . . . . . . . . . . . . .37 4.2.7 SCSI HARD DISK DRIVES, TAPE DRIVE AND FLOPPY DRIVE. . . .37 4.3 CABLE DIAGRAMS . . . . . . . . . . . . . . . . . . . . . . . . .40 4.3.1 916484 SERIAL DEVICE TO CCA/BREAK-OUT BOX . . . . . . . .40 4.3.2 916073 EXTERNAL MODEM TO CCA/BREAK-OUT BOX. . . . . . . .40 4.3.3 916291 CCA TO PARALLEL PRINTER CABLE. . . . . . . . . . .40 4.4 SUPPORTED PERIPHERALS. . . . . . . . . . . . . . . . . . . . . .41 5.0 BOSS/VX SYSTEM UTILITIES. . . . . . . . . . . . . . . . . . . . . . .42 5.1 UTILITY PROGRAM OVERVIEW . . . . . . . . . . . . . . . . . . . .42 5.2 OPRINFO UTILITY. . . . . . . . . . . . . . . . . . . . . . . . .44 5.3 CONFIGURE UTILITY. . . . . . . . . . . . . . . . . . . . . . . .46 TABLE OF CONTENTS 6.0 BOSS/VX SHELL . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 6.1 DIFFERENCES BETWEEN BOSS/VX AND BOSS/IX. . . . . . . . . . . . .51 6.2 COMMANDS AND ARGUMENTS . . . . . . . . . . . . . . . . . . . . .52 6.3 USEFUL BOSS/VX COMMANDS. . . . . . . . . . . . . . . . . . . . .56 6.4 CONTROL SEQUENCES. . . . . . . . . . . . . . . . . . . . . . . .57 6.5 INPUT/OUTPUT/ERROR REDIRECTION . . . . . . . . . . . . . . . . .57 6.6 BACKGROUND PROCESSING. . . . . . . . . . . . . . . . . . . . . .57 6.7 INPUT BUFFER LIMITATION AND EFFECT ON COMMANDS . . . . . . . . .57 6.8 HUGH DIRECTORIES . . . . . . . . . . . . . . . . . . . . . . . .57 7.0 OPERATING SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . .58 7.1 MEMORY MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . .58 7.1.1 AREAS OF MEMORY . . . . . . . . . . . . . . . . . . . . .58 7.2 FILESYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . .59 7.2.1 STRUCTURE OF BOSS/VX FILESYSTEM . . . . . . . . . . . . .59 7.2.2 MOUNTABLE FILESYSTEMS . . . . . . . . . . . . . . . . . .60 7.3 SYSTEM SECURITY. . . . . . . . . . . . . . . . . . . . . . . . .62 7.3.1 FILE ACCESS PRIVILEGES. . . . . . . . . . . . . . . . . .62 7.3.2 ROOT PRIVILEGE. . . . . . . . . . . . . . . . . . . . . .63 7.3.3 ACCOUNT PASSWORDS . . . . . . . . . . . . . . . . . . . .63 7.3.4 MENU SECURITY CODES . . . . . . . . . . . . . . . . . . .63 7.3.5 SSN . . . . . . . . . . . . . . . . . . . . . . . . . . .63 7.3.6 SOFTWARE KEYS . . . . . . . . . . . . . . . . . . . . . .64 7.3.7 CONFIGURATION RECORDS . . . . . . . . . . . . . . . . . .64 8.0 CUSTOMIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 8.1 OPERATING SYSTEM PARAMETERS CUSTOMIZATION. . . . . . . . . . . .65 8.2 MODIFYING THE CMOS RAM CONFIGURATION . . . . . . . . . . . . . .66 9.0 PERFORMANCE INFORMATION . . . . . . . . . . . . . . . . . . . . . . .69 9.1 SAR (SYSTEM ACTIVITY REPORTER) PERFORMANCE TOOLS . . . . . . . .69 9.2 SYSTEM MEMORY REQUIREMENTS . . . . . . . . . . . . . . . . . . .75 10.0 SYSTEM CRASH/DUMP . . . . . . . . . . . . . . . . . . . . . . . . . .76 10.1 CORE DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . .76 10.2 SYSTEM CRASH (PANIC). . . . . . . . . . . . . . . . . . . . . .77 10.2.1 SAVING A CRASH DUMP TO TAPE . . . . . . . . . . . . . .77 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg002 10.2.2 FORCING A SYSTEM CRASH DUMP . . . . . . . . . . . . . .78 10.2.3 WRITING A CRASH DUMP TO HARD DISK . . . . . . . . . . .78 10.2.4 RECOVERY AFTER A CRASH DUMP . . . . . . . . . . . . . .78 10.2.4.1 FILES THAT LACK INTEGRITY . . . . . . . . . .79 10.2.4.2 LOST FILES. . . . . . . . . . . . . . . . . .80 11.0 HELPFUL HINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 11.1 UMASK AND BMASK . . . . . . . . . . . . . . . . . . . . . . . .81 11.2 ADDING A SECOND DISK DRIVE. . . . . . . . . . . . . . . . . . .82 11.3 RENAMING THE USR2 PARTITION . . . . . . . . . . . . . . . . . .83 11.4 ADDING A NON-MBF TERMINAL TO THE MBF CONFIGURE UTILITY. . . . .84 11.5 THIRD PARTY SOFTWARE. . . . . . . . . . . . . . . . . . . . . . 12.0 DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 13.0 BUSINESS BASIC 90 AND PORTING GUIDE . . . . . . . . . . . . . . . . .88 13.1 BUSINESS BASIC FILETYPES. . . . . . . . . . . . . . . . . . . .88 . 13.2 PORTING BASIC APPLICATIONS. . . . . . . . . . . . . . . . . . .88 . 13.3 BOSS/IX 7.4B CHANGES REQUIRED TO RUN UNDER BOSS/VX BB90 . . . .89 13.4 USING ITP FOR TRANSFERRING BETWEEN BOSS/IX AND BOSS/VX. . . . .93 The new GPx Series 40 systems are a multi-user, multi-tasking, 386-based, business computers. The GPx Series 40 supports new hardware technology, including SCSI hard disks, connectivity for 8 to 16 (GPx 340) or 32 (GPx 440) serial devices, a 1/4" 120MB SCSI tape unit, an internal modem, 4 to 8 Mb (GPx 340) or 16 Mb (GPx 440) of SIMM memory optional, floppy disk drive and a 32-bit Intel 386 Microprocessor operating at 25 MHz clock speed. The Operating System for the computer is BOSS/VXTM, a UNIXR* System V.3.2 compatible and Business BASIC compatible operating system. The BOSS/VX operating system is unlike other UNIX-based operating systems, in that it allows a customer to take full advantage of UNIX-based software applications, as well as run MBF proprietary software applications concurrently. Because BOSS/VX\ supports these two types of software application environments concurrently, MAI Basic Four has seized on the uniqueness by. developing the concept of a Dual UniverseTM. The Dual Universe concept alleviates customers from having to choose between a proprietary operating system (one Universe), and the openness of a standard operating system (another Universe). The Dual Universe concept stems from the operating system's ability to execute two different types of applications at the same time. Therefore,. the Dual Universe is composed of one universe for executing UNIX-type applications, and another universe for executing MBF proprietary Business BASIC applications. The GPx Series 40 can be customized with three different levels of software to meet the customer's needs: BOSS/VX operating system, MBF Extended Environment, and UNIX Extended Environment, as follows: BOSS/VX Operating System BOSS/VX must be present on all systems. BOSS/VX consists of the system kernel, the MBF environment and the UNIX environment. The MBF environment contains the base set of commands and utilities, Business BASIC 90, and full support for vendor Business BASIC applications. The UNIX Environment provides the complete set of tools, utilities, and other functionality SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg003 found in standard UNIX V.3.2, including the necessary libraries and kernel extensions to run standard "c" applications. Note, the UNIX Base Environment allows execution, but not the ability to develop "c" applications. MBF Optional Products MBF Optional Products offer specific Business BASIC applications designed by MBF. . Each module is independent and can be added at any time. These modules include products such as, MAI OFFICETM and MAI ORIGINTM ADS, ATP and other vertical applications. *UNIX is a Registered Trade Mark of AT&T in USA and other countries GPx SOFTWARE ANNOUNCEMENT UNIX Optional Products UNIX Optional Products consist of separate . optional modules. The "c" development module provides the ability to program, compile, and fully develop "c" application programs. Other modules will be made available in the future. 1.1 BASE PACKAGE OVERVIEW This section gives the packages found on the BASE Customer tape and an brief overview of what that package contains. Other than the BASE Package the following products can be installed using 'mbfinstall'. For information on the use of this command see Section 3.4 of this document. BASE PACKAGE This contains the BOSS/VX kernel, BASIC (BB90), system and BASIC utilities and a limited set of UNIX commands to support the MBF Enviroment. With this package installed, you will be able to run in the MBF BASIC Enviroment. To install this package requires that you boot off of the BASE tape and use the OS upgrade or install procedures, per section 3.1 of this document. INTL (International Utilities) This contains the programs and files required to modify or change the langauge of the utility message files. MBFMAN (BOSS/VX Reference Manual) This contains the programs and files required to use the 'man' command with the BOSS/VX valued added commands. This package is also required to be installed for the 'man' command in UNIX to work. UMAN (UNIX Reference Manual) This contains the files required to use the 'man' command with the UNIX commands. UTERM (UNIX terminfo files) This package contains the AT&T supplied terminfo files. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg004 UNX (UNIX Utilities) This contains the complete set of AT&T UNIX System V.3.2 BASE commands and utilities. UPDR (PDF Runtime) This package is required if you wish to use PDFs that were created or modified in the field. A public ID or key is required to use this package. TOOLS (Operating System Tools) This package includes operating system tools. Presently, all the programs in this package are included in the UNX package. ITP (Intersystem Tape Transport Utilities with ATP 4.0*13) This package contains the programs and files required to run the Intersystem Transport package. It also, includes ATP 4.0*13. A public ID or key is only required if you wish to use the ATP auto-scheduler and/or the ATP autodialer features. Without the key, you are able to use the package for transporting your programs and data files between MPx, SPx, 13xx and GPx systems. * PS (Presentation Services Tools) This package contains the programs and files required to use the Form Builders section of Presentation Services. * ADS (Application Development Software) This package contains the programs and files required to develop ORIGIN Applications. * DSS (Decision Software Support) This package contains the programs and files to use MAI Business DataTM 2.1B (MBF Business DATATM). * OTU (ORIGIN Translation Utilities) This package contains the programs and utilities to translate ORIGIN to a different language. These packages are not on the international version of the BASE tape and must be ordered separately. 2.0 SYSTEM START-UP AND SHUTDOWN 2.1 SYSTEM START-UP The GPx Series 40 can be booted from 1/4" tape or from the hard disk. When the system is powered up or rebooted it will first attempt to load from the tape drive. If a tape is not present, or the tape in the drive is not a boot tape it will then load from the hard disk, using the load parameters found in the '/etc/default/boot' file. Following are the steps to boot from the tape or from the hard disk, assuming that the AUTOBOOT flag in the '/etc/default/boot' file is set to 'YES': Step 1: Locate the console terminal, the terminal connected to the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg005 COMM 1 port. The console terminal will be used by the system to display messages and receive inputs during the load process. Step 2: If the system is powered down, power it up by pressing the power button located on the front of the system. If the system has been shutdown, but is still powered up, ensure the message: PRESS RETURN TO REBOOT, OR POWER OFF THE SYSTEM is displayed and then press . Step 3: If you wish to load from tape, put a bootable tape in the tape drive and close the drive door during the self test if powering up, or put the tape in the drive before pressing . Otherwise the system will load automatically from the hard disk drive. After the self test, a message telling you the BOSS/VX system is being booted is displayed, followed by a message displaying the name of the OS and the DCT file being loaded Step 4: After the proprietary message is displayed, the system will go into multi-user mode. When the load process is complete, the MAI/BASIC FOUR logon screen will be displayed. The system is now started up and ready for use. 2.2 SYSTEM SHUTDOWN Following are the steps to properly shutdown the system so that it can be powered down or rebooted. WARNING: To avoid possible damage to your files, ensure you follow this procedure before powering down or rebooting the system. Step 1: Login as root/super-user on the system's console. Get to command mode, with your working directory set to '/'. Step 2: Enter the command 'shutdown (options)',. The options for this command are: -y: If this is not added, the procedure will prompt to ask if you wish to continue with the shutdown after the grace period. If added, the system will not prompt before completing the shutdown. . -g: -g followed by a number will give time in seconds before the system will shutdown or prompt for you to continue with the shutdown if the '-y' option is not used. The default if the option is not used is 60 seconds. -i: -i followed by an init state will cause the system to go into the state after the shutdown. The default is init 0. The available init states are: 0 = shutdown so that the system can be powered down or rebooted S,s,1 = go into single user mode 2 = go to multi user mode This cannot be used with the shutdown command 3,4 & 5 = not available at this SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg006 time 6 = shutdown and automatically reboot After the command is entered a message will be displayed to all terminals logged in, telling the users to log off the system. Step 3: If you have not used the '-y' option in the command, after the grace-period, the following prompt will be displayed: Do you want to continue? (y or n): Before answering this question check with the other users on the system to ensure they have logged off the system before continuing. If you answer 'n',, a message will be displayed to all the terminals telling them that the shutdown has been stopped. Answering 'y',, will shutdown the system. Step 4: Messages will be displayed during the shutdown telling you that the system is coming down and that system services are being stopped. When the shutdown is complete the following message will be displayed: PRESS RETURN TO REBOOT, OR POWER OFF THE SYSTEM At this point the system is completely shutdown and can be powered down or rebooted by pressing . 3.0 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM The following are the steps to install or upgrade the BOSS/VX Operating System. Before installing or upgrading the system it is recommended that you read these instructions completely. 3.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all files that exist on your system. It first creates partitions on the fixed disk, makes the file system according to default or user input specifications, and then installs the standard BOSS/VX software (BOSS/VX, Business BASIC, and system utilities) on your system. WARNING: Installation of the Operating System will destroy any installed software on the system. If you are doing an OS installation on a system that already contains customer data, ensure you have a verified back-up of the data. This back-up should not contain any OS files. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record for the target system NOTE: During Step 4 you will be required to answer questions pertaining to the system disk partitioning. This information should be decided before the start of the installation, as changing these values will require a re-install of the OS. For information on partitioning see Section 3.1.1. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg007 Step 1: If the system is powered down, power up the system. During the system self test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. Step 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a , if not answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. Step 3: Enter option 'f' to do a full installation. A warning message telling you that a full installation will . destroy all files on the system will be displayed. You will then be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', to exit the installation procedure. Step 4: System disk information will now be displayed, including the default system disk partitioning, followed by the prompt: Is this allocation acceptable to you (y/n)? If you answer 'y',, to this prompt, the default partition will be used to partition your system disk. If you answer 'n' to this prompt, you will next be prompted with: Do you wish to have separate root and usr filesystems (y/n)? If you answer 'y', to this question your system will contain a root partition and a separate usr partition. Answering 'n',, will put both the root and usr in the same partition. You will next be prompted with the question: Do you want an additional /usr2 filesystem (y/n)? If you answer 'y', to this question a separate usr2 partition will be created on your system disk during the installation. With a 'n',, answer to this question the usr2 partition will not be created. Next a message will be displayed showing approximately how many bytes a cylinder contains on your disk. You will then be asked: How many cylinders would you like for swap/paging? The minimum size this partition can be is 16Mb. Enter the number of cylinders you wish the swap/paging partition to be, followed by a . You will next be prompted for the size you wish for SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg008 the rest of the partitions to be created. After you give the size for each partition, you will be again asked if the allocation is acceptable. An answer of 'n',, will take you back to the beginning of this step. Step 5: After you have answered 'y' to the allocation question, messages will be displayed indicating that the file systems are being made. After the file systems are made, the BOSS/VX software will be installed with the name of the files displayed as they are copied to disk. Step 6: After the BASE system is installed, the Date and Time are displayed. You will be prompted with: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y',, and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. Step 7: You will next be asked if the Date and Time are correct. If they are correct, answer 'y',; otherwise, answer 'n',, and you will be prompted with the questions to set the Date and Time correctly. Step 8: You will next be asked to enter the password for the root or super-user: You will be asked for this password twice. Be sure that you remember this password, as it will be required when you wish to login as root. Step 9: The next step is to install the System's Configuration Record. You will be prompted with: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you wish to install this configuration record? Enter 'y',, to install the configuration record. If you enter 'n',, the configuration record will not be installed and you will be returned to the BOSS/VX SOFTWARE INSTALLATION menu. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg009 NOTE: You must install a configuration for your system to boot. If you entered 'n',, in the above step, see Section 3.3 "Installation/Upgrade of the Security Configuration Record" to install the configuration record. Step 10: After the configuration record is installed the installation of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r',, to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 3.4 "Installation and Update of Optional Software Packages" 3.1.1 SYSTEM DISK PARTITIONING The BOSS/VX installation procedure will allow you to define one, two or three partitions containing a file system on the system disk. The swap/paging partition will automatically be on the system disk, but doesn't contain a file system. You will be required in Step 4 of the BOSS/VX installation procedure to provide information on the number and size of the partitions you wish defined. Before starting an installation, you should have this information. To change this after an OS installation will require backing up the customer's data and doing a complete re-installation of the OS. The following are the different partition options that are available during the installation: 1 partition: root and usr together on the same partition, no usr2 partition. (not recommended) 2 partitions: separate root and usr partition, no usr2 partition. 2 partitions: root/usr partition together and a separate usr2 partition. 3 partitions: separate root, usr and usr2 partitions. During the installation procedure, commands and files required when the system is in single user mode will be installed to the root partition. While in single user mode, the root is the only partition automatically mounted. These commands will allow you . to repair or work with one of the other partitions if they are damaged. During the installation procedure, the rest of the standard BOSS/VX software will be installed on the usr partition, if you specified you wanted a separate root and usr partition. Otherwise, the rest of the standard BOSS/VX software will be installed in a directory called '/usr', on the root partition. The OS doesn't put any commands, programs or files automatically into the usr2 partition if it is defined. At the minimum it is recommended that you define your system disk with a separate root and usr partition. In this case if a SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg010 problem occurs on the usr partition, (the partition where the customer's data is located), the system can be booted into single user mode and the usr partition can be worked with from the root partition. If you wish to put the customer's programs and data files on a separate partition or wish to have a separate partition that can be easily unmounted for security reasons, then the usr2 partition should be defined. Following is the approximate amount of disk space in Mega Bytes by package for the root and usr partitions: Package root usr BASE 2.5MB 8.6MB UNIX* .9MB 6.6MB MANPAGES** 3.1MB ITP .9MB PS 3.5MB For ADS, DSS and OTU see Section 3.5.2.1 * UNIX = UNX and UTERM ** MANPAGES = MBFMAN and UMAN NOTE: The amount of disk space required for the above may grow in future releases. 3.2 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the original ones. WARNING: Before attempting any update, it is recommended you have a verified back up of the customer's data. Ensure that this back up doesn't contain any of the OS files. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record for the target system (if you wish to re-install the configuration record) Step 1: If the system is powered down, power up the system. During the . system self test, put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. Step 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a . If not, answer 'n',. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg011 The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. Step 3: Enter option 'u', to do an update installation. Messages telling you that the file systems are being checked will be displayed. The file systems must not contain errors for the update to continue. Next, messages telling you the BASE system package is being searched for, followed by a message telling you the BOSS/VX software will be installed, are displayed. This is followed by the OS files being installed, with the names of files displayed as they are installed. Step 4: After the OS files have been installed you will be given the option to install the OS files that the user can modify. Step 5: Next the Date and Time are displayed. You will be prompted with: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change time zones answer 'y',, and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone, you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. Step 6: You will next be prompted with: Install the configuration record (y/n)? If you don't want to install the configuration enter 'n',. The update is now complete. Remove the BASE system tape and enter 'r', to reboot the system. If you don't wish to install the configuration record, enter 'n', and you will bedonewith the O.S. update. Step 7: If you wish to install the configuration record, enter 'y', and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg012 Do you want to install this configuration record? If you enter 'y',, the configuration record will be installed If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. Step 8: After the configuration record is installed, the update of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 3.4 "Installation and Update of Optional Software Packages". 3.3 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration record on a system that doesn't already have one or overwrites the . one already on the system. It will display the configuration record before installing it and give the option to install it or go back to the menu. The following will be required to install the Configuration Record: o BASE Operating System Tape o Configuration Record tape for the target system Step 1: If the system is powered down, power up the system. During the system self test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. Step 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y', followed by a . If not, answer 'n', The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. Step 3: Enter option 'i', to install the configuration record. The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg013 Take the tape containing the BASE system out of the tape drive and put the tape containing the configuration record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record? If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. Step 4: After the configuration record is installed you will be prompted with: Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r',, to reboot the system. The installation of the configuration record is now complete. 3.4 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES The following steps outline the procedure to install optional BOSS/VX packages, for example, ITP, MAI OFFICE, PS, tools, ORIGIN and other packages supplied in a BOSS/VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified back-up of the customer's data files before attempting the update. The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. Step 1: If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. Step 2: Shut the system down to single user mode by using the command 'shutdown -is'. Do you want to continue (y/n)? enter 'y' When prompted for the password use your root password. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg014 Enter terminal type (default is TERM=dt4313) or terminal type. Step 3: At the command mode prompt enter the command mbfinstall . The following messages will be displayed: Installing products on / WARNING: This program should only be executed in single-user mode press to continue. Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. Step 4: Insert the tape containing the package(s) you wish to install in the tape drive and enter . If the BASE system tape is being used for the installation, a message telling you that the tape is an operating system tape, followed by a prompt to continue is displayed. Enter . Messages will be . displayed telling you the procedure is skipping to the part of the tape containing the package(s). Next, the MBF Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. Step 5: Enter the number of the package you wish to install followed by a . You can enter them in any order. The procedure will put them in the order they are found on the tape. After you enter a number you will be prompted with: Are you sure (y/n)? If you answer 'y',, to this question, the number will be added to the list and you will be returned to the menu. If you answer 'n',, the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, . If you wish to abort the procedure and go back to command mode enter ab, . SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg015 Step 6: After you have entered the number of all the products you want to install, enter 's',. The procedure will display the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. Step 7: If a public id is required a message displaying the current public id and its length will be displayed after the package is installed, followed by: Enter an 8-char. new Public ID (Hit <0> for a Null Public ID or for no change): Enter the public id you received with the package if it is different than the one displayed. Step 8: If you are installing more than one package, the next package will be installed. This will continue until all the packages you selected have been installed. After all the packages are installed, the procedure will take you back to command mode. You are now done with the installation of your package(s). If you wish to install additional package(s) from other tape(s) repeat this procedure to install them. Step 9: Enter '^d and 2' to return to multi-user mode or '^d and 0' to shut the system down. 3.5 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES The following sections include special instructions or installation procedures when installing the optional software packages. There are no special instructions for installation and customization of Presentation Services. Ensure the users Path includes the following to access Presentation Services: /usr/mbf/PS /usr/mbf/PS/tools 3.5.1.1 PRESENTATION SERVICES CUSTOM MENUS If the user has created their own menus through PS MENUBUILDER for either their own applications or OFFICE and ORIGIN, they need to transfer those files to the GPx Series 40 system using Intersystem Transport. The files to be transferred are as follows: SPx: ../PS/MSMF and ../PS/MSSF-->MENU FILES ../PS/MSH1 and ../PS/MSH2-->HELP FILES MPx names would be: .PS.MSMF and .PS.MSSF .PS.MSH1 and .PS.MSH2 3.5.1.2 PRESENTATION SERVICES FORMS When transferring forms to the GPx system, port only the source form files. Do not port the compiled form file. You will need to recompile your forms once you get them on the destination system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg016 If the user has created their own forms through PS FORMSBUILDER, they need to transfer the following using Intersystem Transport. SPX: /PS/FS1.ENG /PS/FS2.ENG /PS/FS3.ENG /PS/FS4.ENG MPX: .PS.FS1.ENG .PS.FS2.ENG .PS.FS3.ENG .PS.FS4.ENG All programs created and associated files must also be transferred. Programs will need to be modified to use only BB90 directives. Bring the files over using cread but not doing the conversion during porting. Then run BQR to convert the files. After this is done, run MKCONVERT. 3.5.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities ******************************************************************. * WARNING * * *. * o PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING * * THIS PRODUCT. * * *. * o Your system should be in single user mode. This ensures a * * safe product installation without conflicts with active * * systems users. *. * *. * o You must be logged on as 'root'. This will avoid security * * conflicts during the product installation. * * *. * o Make a full backup of your product (programs & files) * * before installing this new version. * ****************************************************************** NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 3.5.2.1 INSTALLATION REQUIREMENTS: New installations: o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.0A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg017 ADS or DSS or (ADS + DSS): 8.16 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB Updating: o The same requirements for a new installation, plus the following: o You must port all of your current ORIGIN data files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). WARNING: The only way to keep separate directories is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 3.5.1 (Presentation Services) ******************************************************************* * *. * Make a full backup of all ORIGIN program and data files, * * currently located at '/usr/origin/r21b and the directories in * * which your *DC0 files are located BEFORE installing this * * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix or directory. * * *. ******************************************************************* NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 3.5.3.1 for MPx and Section 3.5.3.2 for SPx. 3.5.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 3.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 3.4. 4. Go into BASIC and start with 256 pages of memory. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg018 basic s=256 5. RUN "UPDATE" from BASIC. During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR .ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appears) SECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY You may now go to step 6 or quit and shutdown before rebooting system. 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg019 cd /usr/origin/r21b/language rm * 3.5.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B, the program UPDATE does NOT have to be executed. 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 3.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 3.4. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), for (a default will appear) For example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 3.5.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 3.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 3.4. 4. Go into BASIC and start with 256 pages of memory. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg020 basic s=256 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT : This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files E. INSTALL STAND ALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 3.5.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg021 NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 3.5.2.3, "Installations Updating from 2.0A". 3.5.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic >start 256 >PREFIX "/usr/origin /usr/origin/r21b /usr/mbf/PS /usr/mbf/PS/tools" >run "ORIGIN" NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. 3. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. _____ Select User Maintenance, use the password "ADMIN". 4. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities. The password is ADMIN. _____ Select ORIGIN System Parameters Maintenance option. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg022 _____ Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this directory is "/usr/origin/work/". 3.5.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 3.5.3.1 MPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 3.5.2.4. 2. Perform a verified backup of the ORIGIN system. 3. Using the DIRectory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. For example: .USR.ORIGIN.JKSF01 ---> data file .USR.ORIGIN.JKSF02 ---> data file .USR.ORIGIN.JKSFM2 ---> Application Generated Program .USR.ORIGIN.JKSFM1 ---> Application Generated Program .USR.ORIGIN.JKSR01 ---> Report Generated Program .USR.ORIGIN.JKSR02 ---> Report Generated Program .USR.ORIGIN.xxxDC0 ---> Technical Documentation File .ORIGIN.R20A.DATA.IDD000 ---> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with IDDxxx and reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From command mode, execute MCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem . Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 3.5.3.2 SPx TO GPx CONVERSION SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg023 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 3.5.2.4. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 ---> data file /usr/origin/JKSF02 ---> data file /usr/origin/JKSFM2 ---> Application Generated Program /usr/origin/JKSFM1 ---> Application Generated Program /usr/origin/JKSR01 ---> Report Generated Program /usr/origin/JKSR02 ---> Report Generated Program /usr/origin/xxxDC0 ---> Technical Documentation File /origin/r20a/data/IDD000 ---> Integrated Data Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Using cwrite utility, write BQR filelist to tape. 5. Restore Intersystem tape on GPx machine using cread utility Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem. Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 3.5.4 ORIGIN 2.1B NEW FEATURES o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re-generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity between the 're-generated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg024 avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 3.5.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) -and- /pgm/SPA004 - ORIGIN message file in foreign language (*). /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language * SPA will be used as the language code in this document. o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. MESSAGE TRANSLATION o Set your prefix to work with ORIGIN 2.1B and perform the following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilities -> -> Password (ADMIN) -> Language Translation Menu -> Language -> Maintain Language -> Enter the language code -> -> Done, you may go to console mode at this point. o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file, to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005. file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg025 o Using with the system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program directory (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily modified from 2.1A to 2.1B, so a re-translation of this program is recommended: . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until translation is complete. 3.5.6 DOCUMENTATION Manual Number Part Number Pages Title M7511E 007511-012A 170 MAI Business DATATM Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATATM Technical Reference M0058C 910058-002 132 MAI ORIGINTM User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGINTM Application Generator User Guide M7512D 007512-002 112 MAI ORIGINTM Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATATM System Support Manual SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg026 M7557G 007557-011 74 MAI Business DATATM User Guide M7561E 007561-002A 166 Presentation Services Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services Forms Management User Guide 4.0 HARDWARE INFORMATION 4.1 GPx SERIES 40 HARDWARE MINIMUM AND MAXIMUM CONFIGURATION CHART There are two different model systems in the GPx Series 40 Family of computers. The following charts give the minimum and maximum hardware for each type of system. 4.1.1 GPx 340 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART The following chart gives the minimum and maximum hardware configuration for the GPx 340. _______________________________MINIMUM________MAXIMUM__ CPU 1 1 Chassis 1 1 Memory Capacity 4MB 8MB 4MB Memory Modules 1 2 4MB Memory Expansion Board 0 0 Disk Capacity 115MB 355MB Hard Disk Drives 1 1 3.5" 1.44MB Floppy Drive 0 1 1/4" 120MB Tape Drive 1 1 Serial Devices 1 16* Terminals 1 16 Printers 0 15 Internal Modem 1 1** Parallel Printers 0 1 SCSI Controller 1 1 Intelligent Serial Devices 1 2 Controllers (ISDC) ISDC/8-Way 1 2 ISDC/16-Way 0 0 * Port-connected serial devices, not including slave printers. Slave printer and its companion terminal count as one terminal. ** Internal Modem is standard on systems sold for installation in the U.S. and other seleted areas. 4.1.2 GPx 440 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg027 The following chart gives the minimum and maximum hardware configurations for the GPx 440. _______________________________MINIMUM________MAXIMUM__ CPU 1 1 Chassis 1 1 Memory Capacity 4MB 16MB 4MB Memory Modules 1 4 4MB Memory Expansion Board 0 1 Disk Capacity 115MB 710MB Hard Disk Drives 1 2 3.5" 1.44Mb Floppy Drive 0 1* 1/4" 120Mb Tape Drive 1 1 Serial Devices 1 32** Terminals 1 32 Printers 0 31 Internal Modem 1 1*** Parallel Printers 1 1 SCSI Controller 1 1 Intelligent Serial Devices Controllers (ISDC) 1 2 ISDC/8-Way 1 2 ISDC/16-Way 1 2 * Not available if system is configured with two 355MB disk drives. ** Port-connected serial devices, not including slave printers. Slave printer and its companion terminal count as one terminal. *** Internal Modem is standard on Domestic Systems only. 4.2 JUMPER CONNECTIONS AND SWITCH SETTINGS This section describes the default jumper connections and switch settings for the GPx Series 40 systems. If you need to set these for something other than the default setting see MBF Manual M8215A 'INSTALLATION AND MAINTENANCE MANUAL' for more details. 4.2.1 CCA COVER AND PCBA REMOVAL CAUTION: Ground straps (worn on the wrist and connected to ground) should be used while handling PCBAs to prevent electrostatic discharge (ESD) from damaging components. To remove the CCA cover from the GPx Series 40, remove the five screws, one in each corner in the back and the screw on the top middle on the back of the CCA. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg028 While facing the front of the unit carefully slide the cover towards you until the rear portion of the mounting grooves reaches the front panel. Lift the cover up from the CCA and set it aside. The PCBAs can be removed after the CCA cover has been removed by first removing the mounting bracket screw holding the PCBA in place. The screw is located at the rear of the CCA. Next ensure that all cables connected to the PCBA are removed. The PCBA can now be removed by lifting it out. 4.2.2 CENTRAL MICROPROCESSOR BOARD (CMB) This section describes the switch settings and jumper connections for the Central Microprocessor Board (CMB). ______________________________________________________ | DESCRIPTION SWITCH POSITION | |------------------------------------------------------| | SWITCH # 1 | |______________________________________________________| |NAME | FUNCTION | 1 2 3 4 5 6 7 8 | |--------|-----------|---------------------------------| |EPROM | | | | | | | |TYPE | 27256 | ON OFF OFF ON d d d d | | | | | |________|___________|_________________________________| |I/O | | | |RECOVER | 2.23us | d d d d ON OFF OFF OFF | |TIME____|___________|_________________________________| d = DON'T CARE ________________________________________________________________ | SWITCH # 2 _| | DESCRIPTION | SWITCH SETTING _| |NAME | FUNCTION | 1 2 3 4 5 6 7 8 9 10 _| |SERIAL |SERIAL1=COM2 | | |PORT |AND | OFF d d d d d d d d d | |ASSIGN-|SERIAL2=COM1 | | |MENT | | _| | COM1 | ENABLE | d OFF d d d d d d d d | | IRQ4 | | _| | COM2 | DISABLE * | d d ON d d d d d d d | | IRQ3 | | _| |LINE | LP1 ENABLE | d d d OFF OFF OFF ON d d d | |PRINTER| | _| | RAM | DISABLE | d d d d d d d ON d d | | BIOS | | _| |MONITOR| MONOCHROME | d d d d d d d d OFF d | |USED | | _| | DRAM |ENABLE (8M)**| d d d d d d d d d OFF | | BANK B| | | |_ENABLE|DISABLE (4M)**| d d d d d d d d d ON _| * = SET POSITION 3 OFF IF INTERNAL MODE NOT INSTALLED ** = CONFIGURE TO MATCH THE AMOUNT OF MEMORY INSTALLED ON YOUR CMB. d = DON'T CARE _________________________________________________________ SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg029 | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION _| | | | JP1 | | BELL | ENABLE | 1-2 _| | CO- |WT 3167 CO- | JP6 | JP7 | JP8 | | | PROCES-|PROCESSOR OR | | | | | | SOR |NO COPROCESSOR| 1+2-3 | 1 2- | 1+2-3 | | | MOVEOUT| | JP12 | | 256K | DISABLE | | | MEMORY | | 1+2-3 _| | MEMORY | 4 MB AND | JP13 | JP14 | JP15 | JP16 | | ON CMB | 8 MB | | | | | | * | | 1-2 3 | 1-2 3 | 1 2-3 | 1 2-3 _| * = 4MB AND 8MB JUMPERS ARE THE SAME S2-10 DETERMINES AMOUNT OF MEMORY ON THE CMB 1-2 3 = JUMPER 1 TO 2, 1 2-3 = JUMPER 2 TO 3 4.2.3 MEMORY EXPANSION BOARD (MXB) This section describes the switch settings and jumper connections for the Memory Expansion Board (MXB). A minumim of 4MB should be installed on the CMB. This section shows switch settings up to 12MB on the MXB. ______________________________________________________ | DESCRIPTION SWITCH POSITION _| | SWITCH # 1 _| |NAME | FUNCTION | 1 2 3 4 5 6 7 8 _| |MEMORY | 0MB | ON ON ON ON OFF OFF OFF OFF | |SIZE |-----------|---------------------------------| |INSTALL | 4MB | ON ON ON ON ON OFF OFF OFF | |ON MXB* |-----------|---------------------------------| | | 8MB | ON ON ON ON ON ON OFF OFF | | |-----------|---------------------------------| | | 12MB | ON ON ON ON ON ON ON OFF_| | SWITCH #2 AND SWITCH #3 | | | | SWITCH #2 AND #3 ARE USED IN CONJUNCTION _| |NAME | FUNCTION | 1 2 3 4 5 6 7 8 _| |START |___________|___________SWITCH_#2_____________| |ADDR. | 4MB | ON ON ON OFF ON OFF OFF OFF | |OF MXB |-----------|---------------------------------| |(=CMB | 8MB | ON ON OFF ON ON OFF OFF OFF | |MEMORY |-----------|---------------------------------| |SIZE) |___________|___________SWITCH_#3_____________| | | 4MB | ON ON ON ON ON ON ON ON | | |-----------|---------------------------------| | | 8MB | ON ON ON ON ON ON ON ON _| ______________________________________________________ | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION| JUMPER POSITION _| |MXB MEMORY| | JP1 | |(FROM | | | |00Exxxx | DISABLE | 1-2 3 | |TO | | | |00Fxxxx) | | _| |MXB MEMORY| | | |(FROM | | JP2 | |0F0xxxx | DISABLE | | |TO | | 1-2 3 | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg030 |0FFxxxx) | | _| |MXB MEMORY| | | |(FROM | | JP3 | |0FAxxxx | DISABLE | | |TO | | 1-2 3 | |0FDxxxx) | | _| |PARITY | | JP4 | |CHECK | ENABLE | | | | | 1 2-3 _| 1-2 3 = JUMPER 1 TO 2, 1 2-3 = JUMPER 2 TO 3 4.2.4 8/16 WAY CONTROLLER PCBA This section describes the switch settings and jumper connections for the 8/16 Way Controller PCBA. ____________________________________________________________________ . | SWITCH # 1 _| | DESCRIPTION | SWITCH SETTING _| |NAME | FUNCTION| 1 2 3 4 5 6 7 8 9 10 11 12 _| |BASE | | | |ADDRESS| SET TO | OFF OFF OFF OFF OFF OFF ON ON d d d d | |SELECT | FC0000H | _|. |BOARD | BOARD 1 | d d d d d d d d ON ON d d | |SELECT |---------|--------------------------------------------------| |(IN | BOARD 2 | d d d d d d d d ON OFF d d | |SAME |---------|--------------------------------------------------| |ADDR. | BOARD 3 | d d d d d d d d OFF ON d d |. |SPACE) |---------|--------------------------------------------------| | | BOARD 4 | d d d d d d d d OFF OFF d d _| |BOARD | 16 WAY | d d d d d d d d d d ON d | |TYPE |---------|--------------------------------------------------| |SELECT | 8 WAY | d d d d d d d d d d OFF d _| |OPERA- |OPERATION| | |TION |MODE | d d d d d d d d d d d OFF | |SELECT | | _| d = DON'T CARE ______________________________________________________ | DESCRIPTION | JUMPER SETTING | | NAME | FUNCTION | JUMPER POSITION | |--------|-----------|---------------------------------| |CLOCK | | JP1 | |SIGNAL | ENABLE | | |TO CPU | | 1-2 | |--------|-----------|---------------------------------| |UART | | JP2 | |CLOCK | ENABLE | | |TO UART | | 1-2 | |--------|-----------|---------------------------------| | | | O O O O |X| O | |IRQ | IRQ12 | 1 O O O |X| O | |SELECT | | _| 1-2 = JUMPER INSTALLED, |X| = JUMPER INSTALLED O = JUMPER NOT INSTALLED NOTE: JP4 IS FOR THE NMI CONNECTION. THE SWITCH SHOULD BE CONNECTED TO ONE OF THE 8/16 WAYS. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg031 4.2.5 SCSI CONTROLLER PCBA This section describes the jumper connections for the SCSI Controller PCBA. NOTE: J1 consist of 13 pairs of jumpers. The chart below will show each jumper pair and indicates if it should have the jumper installed or not. J2 is the SCSI bus cable connector. J3 is the SCSI bus cable extended connector. J4 is the optional floppy drive cable connector. J5 is the front panel LED header. ______________________________________________________ | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION _| | | | J1 - PAIR 1 | |SYNCHRONOUS| DISABLE | | | | | JUMPER NOT INSTALLED _| |DIAGNOSTICS| | J1 - PAIR 2 | |LOOP ON | DISABLE | | | | | JUMPER NOT INSTALLED _| |SCSI PARITY| | J1 - PAIR 3 | |CHECKING | ENABLE | | | | | JUMPER NOT INSTALLED _| |SCSI | | J1 - PAIRS 4, 5, 6 | |CONTROLLER | SCSI ID 7 | | |ID | | JUMPERS NOT INSTALLED _| |DMA | | J1 - PAIRS 7, 8 | |CHANNEL | CHANNEL 5 | | |SELECTION* | | JUMPER PAIR 8 _| |INTERRUPT | | J1 - PAIRS 9, 10, 11 | |CHANNEL | CHANNEL 11| | |SELECT** | | JUMPER PAIR 10 ONLY _| |DMA | | J1 - PAIRS 12, 13 | |TRANSFER | 5.0 MB/s | | |SPEED | | JUMPERS NOT INSTALLED _| ______________________________________________________ | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION _| |HOST ADDR. | | J6 | |FOR | | | |ADAPTEC | 330H | |X| O O | |CARD | | |1| O O _| | | | J7 | |BIOS |WAIT STATE | | |WAIT |DISABLE | |X| O O O | |STATE | | |1| O O O _| |AUTO | | J9 | | | DISABLE | | |REQUEST | | JUMPER NOT INSTALLED _| |HOST | | J10 | |STARTING | 0DC000H | | |ADDRESS | | JUMPER NOT INSTALLED | |FOR BIOS | | _| | | | J11 | |BIOS | ENABLE | | | | | JUMPER INSTALLED _| |FLOPPY | | J12 | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg032 |CONTROLLER | 3F0-3F7H | | |I/O ADDR. | | JUMPER NOT INSTALLED | |SELECT | | _| |FLOPPY | | J13 | |CONTROLLER | ENABLE | | | | | JUMPER INSTALLED _| | | | J14 J15 | |DMA | | | |CHANNEL | CHANNEL 5 | O |X| O O X |X| O O | |SELECT* | | 1 |X| O O 1 |X| O O _| | | | J16 | |INTERRUPT | | | |CHANNEL | IRQ11 | O O |X| O O O | |SELECT** | | 1 O |X| O O O _| |INTERRUPT | | J17 | |CHANNEL | IRQ6 | | |SELECT | | 1-2 3 _| |DMA | | J18 | |CHANNEL | CHANNEL 2 | | |SELECT | | 1-2 3 _| |DMA | | J19 | |ACKNOWLEDGE| CHANNEL 2 | | |SELECT | | 1-2 3 _| * = J1-PAIRS 7,8 USED IN CONJUNCTION WITH J14 & J15 ** = J1-PAIRS 9,10,11 USED IN CONJUNCTION WITH J16 1-2 3 = JUMPER 1 TO 2 X = JUMPER INSTALLED O = JUMPER NOT INSTALLED 4.2.6 INTERNAL MODEM PCBA This section describes the switch settings and jumper connections for the Internal MODEM PCBA. ______________________________________ | DESCRIPTION SWITCH POSITION _| | SWITCH # 1 _| |NAME | FUNCTION | 1 2 3 4 _| |PORT | SELECT | OFF ON d d | |SELECT | COM2 | _| |MNP | ENABLE | d d OFF d _| |DAIL UP | ENABLE | d d d OFF_| ______________________________________________ | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION_| |INTERRUPT | | JP2 JP3 | |CHANNEL | ENABLE | | |SELECT | IRQ3 | 1-2 3 NO JUMPER_| 4.2.7 SCSI HARD DISK DRIVES, TAPE DRIVE AND FLOPPY DRIVE This section describes the jumper connections for the SCSI hard drives, tape drive and optional floppy disk drive. NOTE: All drives on the SCSI bus should have their SCSI terminators removed as the terminator is in the cable. No two drives can have the same ID address and the primary disk drive must have Drive ID0. The second drive SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg033 must have Drive ID1. ID 6 is reserved for the Tape Drive and ID 7 is reserved for the SCSI Controller. ____________________________________________ | 355 MB _| | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION_| | | SCSI | JP35 JP36 JP37 | | |-----------|--------------------| | | ID 0 | O O O | | | | O O O | | |-----------|--------------------| | | ID 1 | |X| O O | | | | |X| O O | | |-----------|--------------------| |DRIVE | ID 2 | O |X| O | | | | O |X| O | |SELECT |-----------|--------------------| | | ID 3 | |X| |X| O | | | | |X| |X| O | | |-----------|--------------------| | | ID 4 | O O |X| | | | | O O |X| | | |-----------|--------------------| | | ID 5 | |X| O |X| | | | | |X| O |X| _| |POWER | SPINUP | JP14 JP38 | |ON | WITH | | |OPTIONS | POWER | |X| d | | | | |X| d _| |TERM. | | JP34 JP41 | |POWER | INTERNAL | | | | | O |X| | | | | O |X| _| |WRITE | | JP18 | |PROTECT | DISABLE | | | | | O | | | | O _| |PARITY | ENABLE | JP40 | | | | | | | | |X| | | | | |X| _| X = JUMPER INSTALLED O = JUMPER NOT INSTALLED d = DON'T CARE ____________________________________________ | 115MB/200MB _| | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION_| | | SCSI | J6-PAIRS 1,2,3 | | |-----------|--------------------| | | ID 0 | O O O O O | | | | 1 O O O O | | |-----------|--------------------| | | ID 1 | |X| O O O O | | | | |1| O O O O | | |-----------|--------------------| |DRIVE | ID 2 | O |X| O O O | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg034 | | | 1 |X| O O O | |SELECT |-----------|--------------------| | | ID 3 | |X||X| O O O | | | | |1||X| O O O | | |-----------|--------------------| | | ID 4 | O O |X| O O | | | | 1 O |X| O O | | |-----------|--------------------| | | ID 5 | O |X||X| O O | | | | 1 |X||X| O O _| |POWER | SPINUP | J6-PAIR 4 | |ON | WITH | | |OPTIONS | POWER | O O O |X| O | | | | 1 O O |X| O _| |PARITY | ENABLE | J6-PAIR 5 | | | | | | | | O O O O |X| | | | | 1 O O O |X| _| X = JUMPER INSTALLED O = JUMPER NOT INSTALLED ____________________________________________ | 120 MB SCSI TAPE DRIVE _| | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION_| | | SCSI | SEL2 SEL1 SEL0 | | | |--------------------| | | | J3-PAIRS | |SCSI ID | | 7/8 9/10 11/12 | |SELECT | ID 6 | | | | | |X| |X| O | | | | |X| |X| O _| X = JUMPER INSTALLED O = JUMPER NOT INSTALLED ____________________________________________ | 3.5" FLOPPY DRIVE _| | DESCRIPTION | JUMPER SETTING _| | NAME | FUNCTION | JUMPER POSITION_| |DRIVE | | J1 | |SELECT | DS1 | | | | | O |X| O O | | | | O |X| O O _| X = JUMPER INSTALLED O = JUMPER NOT INSTALLED 4.3 CABLE DIAGRAMS This section give the cable diagrams for the GPx Series 40 cables. 4.3.1 916484 SERIAL DEVICE TO CCA/BREAK-OUT BOX This cable is used to connect serial devices (terminals and printers) to the CCA serial port or the 8/16 Way Break-out Box. 4.3.2 916073 EXTERNAL MODEM TO CCA/BREAK-OUT BOX This cable is used to connect an external MODEM to the CCA serial port or the 8/16 Way Break-out Box. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg035 4.3.3 916291 CCA TO PARALLEL PRINTER CABLE This cable is used to connect a parallel printer to the CCA parallel printer port. 4.4 SUPPORTED PERIPHERALS This section lists the MBF peripherals that are supported on the GPx series 40 System. MBF peripherals not listed here are not supported on the GPx Series 40 System. Terminals Support in Supported in MBF UNIX Environment Environment DT-4301(7270) Yes No DT-4309 Yes No DT-4312 Yes No DT-4313 Yes Yes DT-4314 Yes Yes Printers MAI Business MAI Business Industry Parallel/ GRAPH WORD Standard Serial Interface Interface Slave PT-4214 No No No Both PT-4215 Yes Yes Yes Both* PT-4217 No No Yes Both* PT-4218 No No Yes Both PT-4222 No No No Both PT-4223 No Yes No Both PT-4224 No No No Both * NOTE: The 4217/4218 uses the IBM character set 2 for foreign translation. Hard Disk Drives The GPx 340 systems support one disk drive for a maximum capacity of 355MB. The GPx 440 system supports any combination of two hard disk drives for a maximum capacity of 710MB. Note that it is not possible to configure two 355MB disk drives and the floppy disk option in the same system. The hard disk drive sizes supported on the GPx Series 40 Systems are the 115MB, 200MB and 355MB. On the GPx 440 the 115MB disk is supported only when brought across as part of a GPx 340 to GPX 440 upgrade. Tape drive The GPx Series 40 comes standard with a 1/4" 120MB SCSI Tape Drive. This tape drive requires 600 foot tapes to write, but can read tapes written on a 45MB and 60MB 1/4" tape drive. Floppy Drive The GPx Series 40 supports an optional 3.5" 1.44MB floppy drive for UNIX data interchange and UNIX program loading. GPx SOFTWARE ANNOUNCEMENT 5.0 BOSS/VX SYSTEM UTILITIES SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg036 The BOSS/VX operating system includes a set of system utilities which emulate BOSS/VX commands. The utility programs interact with the user, prompting him/her for any needed information, and return the desired information in a nicely displayed format. To further assist the user, a "utility menu system" has been integrated "utility menu system" makes use of Presentation Services, and can easily be customized to include (or subtract) different menu options. With the . "utility menu system", system utilities can be accessed by name, or via a The BOSS In addition, an on-line help facility is available with the "utility menu . system". On-line help, which can be activated with the key or , and can be used to obtain information regarding available menu selections. 5.1 UTILITY PROGRAM OVERVIEW The BOSS/VX base system comes with eight utility modules. They are: o BASIC Programs o Directories o Files o Filesystem & disk o Intersystem Transfer o Printers o Save & Restore o System These modules can be seen from the main Utility Menu or accessed directly by entering 'menu eut.'. For example to access the Files module directly enter 'menu eut.file' and the files menu will be brought up. The following two pages list the utility modules and the utility programs within each module. To access these programs directly, enter the program given under the Program Name heading. UTILITY MODULE PROGRAM NAME BASIC Program Utilities basic Compare bcompare Display Program Names bdisplay Encrypt bencrypt List and Cross-Reference bxref Merge bmerge Renumber brenumber Search & Replace bsearch Directory Utilities dir Change Working Directory workdir Create Directory dcreate Display Directory ddisplay File Utilities file Change File Size fchange Copy fcopy Create fcreate Delete fdelete Display Information finfo SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg037 File List Maintenance filelist File Repair frepair Move fmove Rename frename Security secure Filesystem and Disk Utilities filesys Free Space Analysis freespace Mount & Unmount smount Intersystem Transfer Utilities isys Asynchronous Transfer ATP (BASIC program located in /usr/mbf/atp) Batch File Queuer BQR (BASIC program located in /usr/mbf/atp) Cartridge Transfer eut.cisys (uses the programs cwrite, cread, creport, and clabel) Printer Utilities printer Change Print Form pformchg Maintain Print Queue pqueue Printer Parameters pparams Printer Status pstatus Submit Print Job psubmit Save & Restore Utilities save Compare Save Tape tcompare Label Tape tlabel Report Save Tape Contents tlist Restore from Tape trestore Save to Tape tsave System Utilities system Edit Menus menuedit Error Log Utilities serror Operator Information oprinfo Port Configuration configure Set Date & Time sdate 5.2 OPRINFO UTILITY The oprinfo utility is an MBF value-added utility designed to enable a quick, easy, and straight-forward creation of operator accounts. Oprinfo is the recommended utility for all user-account operations, including modification and deletion of existing accounts and changing account passwords. In addition, with the inclusion of groups within BOSS/VX, the "oprinfo" utility will contain support for group creation, modification, and deletion. OPTIONS The oprinfo utility provides eight (8) options. They are: Option 1: Add a User Creates a user account. Includes the creation of a home directory and an optional user ".profile" file. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg038 Option 2: Modify a User Modifies user account information. Option 3: Delete a User Removes a user account and home directory (optional) from the system. Option 4: Change Password Changes the password on a user account. Option 5: Generate Report Lists either the user accounts, group accounts, or initial start programs to the terminal, a printer, or a file. Option 6: Add a Group Creates a new group name. Option 7: Modify a Group Modifies a group name, group ID, or group members. Option 8: Delete a Group Removes a group from the system. USER ACCOUNT PARAMETERS There are 8 parameters used to define a user on the system. They are: 1. Login name: The name the user will use when logging on the system. The "login name" can be no longer than 8 characters and must contain at least one lower case character. 2. User id: The numerical ID to be associated with the "login name". User ID's must be positive, and the default will be the first available ID number greater than 100. Only ID number 0 will contain root privilege. 3. Group name (id): The name and associated ID of the users primary group. The default value will be group name other, with the corresponding ID of 1. Group names can be a maximum of 8 character long, Group IDs must be positive. 4. Home directory: The directory the user will be placed in upon login. The default will be "/usr/". The home directory will automatically be created when the user account is created. 5. Login shell: The full pathname of the initial program to be executed upon login. The default value is /bin/sh. If the program option contains arguments, then the "program" field must be used with a "login shell" of /bin/execsh. 6. Program: This is really another login shell, except this field allows parameters to be specified with the initial program. Remember, if this field is used, the "login shell" field must be /bin/execsh. 7. Menu permissions: The menu codes corresponding to the menus which the user may access. The default is full access to all menus, indicated with no permission codes specified. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg039 8. Additional groups: This is a list of secondary or additional groups to which the user may also belong. NOTE: After the following parameters are specified, the utility will prompt for a password, and whether a user .profile file should be created by the system. GROUP PARAMETERS There are only 3 parameters used to specify a group. They are: 1. Group name: The name of the group. Group names can be no longer then 8 characters. 2. Group name (id): The numerical ID to be associated with the group name. The group ID must be unique and positive, and only one ID may be assigned to a group name. 3. Group members: The user login names which are members of the group. GENERAL INFORMATION Below is some general information regarding the "oprinfo" utility: o When deleting an operator you will be asked if you wish to delete the operators directory. Doing this will completely delete all programs and data files in that directory. o When defining a user account with an initial program of /usr/mbf/bin/basic in the "program" field, the oprinfo utility will prompt for a start size, a program name, and any additional BASIC parameters. o Only a user with "root" privilege may add, delete, or modify user accounts and groups. A user without "root" privileges will only be able to view information regarding his own account. o The files used to store the information related to the "oprinfo" utility are "/etc/passwd, /etc/group, /etc/programs, and /etc/shadow". 5.3 CONFIGURE UTILITY The configure utility is an MBF value-added tool which provides a user- friendly interface to the port, terminal, and printer configuration files. The configure utility allows for the configuration of all GPx supported peripherals. Supported MBF configurations on BOSS/VX are shown below: Graphic Printers Terminals Terminals Plotters Modems Special Device PT-4214 DT-4312 DT-4314 HP-7475A Standard SP1 PT-4215 DT-4313 Other Auto Dial PT-4217 DT-4314 PT-4224 PT-4218 DT-4309 PT-4222 DT-7270 PT-4223 Other PT-4224 PT-4225 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg040 PT-4226 PT-4227 PT-4228 PT-4229 special isp This section covers the configuration options and parameters, highlights the features of the configuration utility, and summarizes miscellaneous information regarding the utility. OPTIONS The configure utility provides eight (8) configuration options. They are: Option 1: Add a device Configures a specified port for a terminal, printer, plotter, or modem. Option 2: Remove a device Removes all parameters associated with a port, leaving the port as "Not configured". Option 3: Move a device Moves a configured device to a non-configured ports. Option 4: Switch two devices Swaps the port locations of two configured ports. Option 5: Report port attributes Lists the port configuration parameters for selected ports to a terminal, a printer, or a file. Option 6: Modify port attributes Allows parameters associated with configured ports on the system to be modified. Option 7: Modify number of ghost ports Modifies the number of ghost tasks available on the system. Option 8: Save configuration and exit Save configuration changes to appropriate files on disk. This must be done for changes to take effect. TERMINAL AND GRAPHIC TERMINAL PARAMETERS There are 21 parameters used to configure terminals and graphic terminals on the operating system. They are: 1. Device Type: Type of device attached to the port. For ports on the 8 and 16 way, these may be terminals, graphic terminals, printers, plotters, modems, and special devices. CMB ports (port 0, 1, 2) are restricted to particular device types. 2. Terminal Type: Model number of terminal attached to the port. The only acceptable graphic terminal type is 4314. 3. Device Name: Name which BASIC will use to access the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg041 port. A mapping of BASIC device names to system device filenames can be found in the /etc/bfsdevs file. 4. Start Process: Name of process to execute on terminal when system is brought up in multi-user mode. The default process is /bin/login. 5. Comment: Any 50 character string. Only restriction is the : character cannot be used. 6. Baud Rate: Baud rate for both input and output to the port. Maximum baud rate is 19200. 7. Parity: Parity for the port. Choices are even, odd, or none. 8. Character length: Number of bits used to determined a character. Choices are 7 or 8. 9. Stop bits: Number of bits used to indicate end of character. Choices are 1 or 2. 10. DTR flow control: Determines if DTR (Data Terminal Ready) hardware flow control will be enabled. DTR is used to start/ stop the input to the port. 11. CTS flow control: Determines if CTS (Clear To Send) hardware flow control will be enabled. CTS is used to start/stop the output from the port. 12. IXOFF flow control: Determines if the port will have the ability to send XON/XOFF flow control characters. Enabling IXOFF gives the port control over the flow of input to the port. 13. IXON flow control: Determines if the port will have the ability to receive XON/XOFF flow control characters. Enabling IXON gives the port control over the flow of output from the port. 14. IXANY flow control: Valid only if IXON is enabled. Determines if any, except XOFF, received character may restart output, including an XON. If IXANY is disabled, then only an XON character may restart output. 15. Disconnect on break: Determines if a hangup signal is sent to all processes within the process group when a break condition is detected. 16. Input translation file: The name of a translation table file which the controller will use to translate each character received by the port. 17. Output translation file: The name of a translation table file which . the controller will use to translate each character sent out from the port. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg042 * 18. Slave printer attached: Determines if a slave printer is connected to the terminal. If yes, then options 19, 20, and 21 will appear. 19. Printer type: Type of slave printer attached. (only if 18 is yes) 20. Read/status timeout: Number of tenths of seconds to wait for a (only if 18 is yes) printer status. 21. Write timeout: Number of tenths of seconds to wait for a (only if 18 is yes) printer write. * NOTE: Option 18 will be 'graphics terminal parameters' if graphic terminal is entered. NOTE: For Port 1 and Port 2, the Baud rate, Parity, Character length, and Stop bits parameters will not be displayed. This is because that information for Port 1 & 2 is stored in CMOS on the CPU board, and is not controlled by the operating system. PRINTER PARAMETERS There are 17 parameters used to configure printers on the operating system. They are: 2. Printer type: Model number of printer attached to the port. 14. Spooling: Determines if spooler queue will be created for the printer connected to the port. 17. Hold priority: The priority associated with the spooler queue. A print job must have a greater priority than the spooler queue in order to be removed from the queue. The remaining parameters for printers have been defined in the terminal parameter section. PLOTTER PARAMETERS There are 17 parameters used to configure plotters on the operating system. They are: 2. Plotter Name: Model number of plotter attached to the port. The remaining parameters for plotters have been defined in the terminal and printer parameter sections. MODEM PARAMETERS There are 20 parameters used to configure modems on the operating system. They are: 2. Modem type: Type of modem (internal or external) attached to the port. 11. RTS flow control: Determines if RTS (Request To Send) hardware flow control will be used. RTS is only supported on the last 2 ports of an MBF breakout box. 17. Carrier required: Determines if the presences of a modem must be SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg043 detected, before reads and writes to the port will be enabled. 18. Report carries lost: Determines if reads and writes should be disabled when DCD (Data Carrier Detected) goes from high-to-low. The remaining parameters for modems have been defined in the terminal parameter section. IMPROVEMENTS IN CONFIGURE A number of significant design changes in the "configure" utility from previous port configuration utilities on prior MBF systems (BOSS/IX in particular) have been implemented. These design changes include: 1. Allowing a range of ports to be configured when a device is added. When adding a device, if multiple ports are to contain the same device type, then all the ports containing the device type may be configured at the same time. For example, if ten ports are to be configured for 4314 terminals, then the ten ports may be configured at the same time by specifying the range of ports to be configured for 4314 terminals. A sample range may be 2-4, 6, 8-14. 2. Displaying a warning message to the user of changes being lost, if an attempt is made to exit the "configure" utility with an or a . If a user attempts to exit the "configure" utility, and modifications have been made and not saved, then the utility will prompt the user, Save configuration (y/n)? GENERAL INFORMATION Below is some general information regarding the "configure" utility: 1. The "configure" utility will only display ports if the corresponding hardware is installed on the system. 2. All port modifications must be done in single-user mode. Only the "Report port attributes" and "Exit" options are selectable in multi-user mode. 3. The configuration/modification of ghosts will not take effect until the system is shutdown and rebooted. Note, that every ghost configured with the "configure" utility will be allocated table space in memory, whether the ghosts are used or not used. A high allocation of ghost tasks may have an adverse effect on performance (16 ghosts are defined by default). 6.0 BOSS/VX SHELL The BOSS/VX shell is the UNIX System V.3.2 Bourne shell. The BOSS/VX shell, which is also referred to as the command interpreter, is very similar to the BOSS/IX command interpreter (or shell), with minor differences. These notes, therefore, will introduce the BOSS/VX shell by focusing on the similarities and differences between the BOSS/VX shell (referred to in notes as VX) and BOSS/IX shell (referred to in notes as IX) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg044 6.1 DIFFERENCES BETWEEN BOSS/VX AND BOSS/IX A number of fundamental differences between the IX and VX shells exist. 1. In VX, there is no ADMIN user. Instead there is a "root" user which contains special "root" privileges. The "root" logon can ONLY be done at the system console, however, a normal user can receive "root" privileges by entering supervisor mode with the "su" command and entering the "root's" password. 2. In IX, two sets of file access privileges exist--one for the owner and one for the other users on the system. In VX, the same two sets of file access privileges exist, however, a third set of privileges have been added. The new set of file access privileges is called the group file access privileges. Group file access privileges allow a number of users working on a common project to share certain files, without giving access to other users on the system. 3. In VX, command arguments are specified differently than on IX; and in some cases, the order in which the arguments are specified on VX is important. On VX, a three-argument command would typically be specified as "-lar" as opposed to "-l -a -r", where a single -lar dash (-) is used followed by all the desired arguments, as opposed to an individual dash (-) for every argument. This method works in VX, because every argument for a command is designed to be a single character in length. 4. In IX, the order of options and arguments did not matter; on VX, options MUST be specified before arguments. If an option is specified after an argument, the option will be ignored. 5. In VX, command options are case sensitive. IX only used lower case options. Example: ls -r will list the directory in reverse order, ls -R will do a recursive listing. 6. In IX, macros existed to shorten commonly executed commands. In VX, a macro facility does not exist. To accomplish similar functionality on VX, an environment variable must be created or a command file may be used. 6.2 COMMANDS AND ARGUMENTS This section gives some of the more commonly used commands on BOSS/IX and their use on BOSS/VX. 1. Command "ls" The "ls" command will produce a directory listing of the current working directory or any specified directory. Below is a sample directory listing of the VX root directory. $ls -l (a) total 12 drwxr-xr-x 2 root root 128 Jun 9 12:58 bin drwxr-xr-x 5 root root 256 Jul 13 9:21 dev drwxr-xr-x 10 root root 512 Aug 22 11:02 etc -rw-r--r-- 1 joe other 987 Sep 11 17:15 test drwxr-xr-x 2 root root 128 Nov 30 14:31 tmp drwxr-xr-x 10 root root 512 Aug 22 11:02 u SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg045 drwxr-xr-x 12 root root 512 Nov 30 8:02 usr drwxr-xr-x 8 root root 256 Nov 30 8:03 usr2 (b) (c) (d) (e) (f) (g) (h) (a) The first line displayed in all "ls" listings will be "total ##", where ## represents the summation of 512 byte disk blocks used by the files in the listing. (b) The first ten characters of each line in a long directory listing represent the filetype and the file access privileges. The first character specifies the file's type, the next three characters specify access privileges for the owner, the next three characters specify access privileges for the group, and the last 3 characters specify access privileges for all other users on the system. (c) The second column is called the "link" field. For regular files the link field indicates the number of different filenames which refer to the file. Normally, a 1 will appear in this field for regular files. For directory files, this field can often be used to determined the number of sub-directories within the directory. Since each directory always contains dot (.) and dot-dot (..) directories, a minimum of 2 will always be displayed for directory files. This field allows a user to determined if there are sub-directories without having to list the contents of a sub-directory. (d) The third column indicates the owner of the file. The owner's logon ID name is displayed. (e) The next column indicates the primary group to which the owner belongs. (f) The next column indicates the size of the file in bytes. For directory files, the minimum directory size is 32 bytes (an empty directory), since all directories contain the . and .. sub- directories. GPx SOFTWARE ANNOUNCEMENT 6.2 (Cont.) (g) The next column indicates the date and time the file was last modified. (h) The last column indicates the name of the file. Many of the arguments for the "ls" command in VX are similiar to the arguments in IX. The arguments which have NOT changed are: -l : long listing -a : display all files, including the dot (.) files. The arguments for the "ls" command which are new or have changed in VX are: -R : recursive listing -C : displays directory listing in columns (only filenames displayed) -s : display size of file in blocks -r : display listing in reverse order -t : display listing according to time-last-modified -i : display the file's inode number SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg046 2. Command "cd" The "cd" command on VX works identically to the "cd" command on IX. The "cd" command is used to change the current working directory. The directories . and .. can be used as arguments, and typing "cd" with no arguments returns the user to their login (or home) directory. 3. Command "pwd" The "pwd" command on VX works identically to the "pwd" command on IX.. The "pwd" command displays the current working directory. 4. Command "pg" The "pg" command on VX functions similiar to the "p" command on IX. The "pg" command is used to print the contents of a file to the screen, one screen at a time. The "pg" command introduces new functionality by allowing the user to page forward and backwards in a file, and allowing the user to jump forward and backwards multiple pages at a time. Other VX commands with similiar functionality are "cat", "more", and "pr". The "pg" options for moving through the file can be viewed by typing "h" at the colon (:) prompt, which appears after the first screen of output has been displayed. 5. Command "mkdir" The "mkdir" command on VX functions identically to the "makedir" command on IX. The "mkdir" command is used to create sub-directories. within VX. GPx SOFTWARE ANNOUNCEMENT 6.2 (Cont.) 6. Command "rm" The "rm" command on VX functions similiar to the "delete" command on IX. The "rm" command is used to delete only files from the filesystem. Unlike the "delete" command on IX, directory files should not be deleted with the "rm" command in VX. Instead, a second command, the "rmdir" command, is used to remove directory files. Only empty, non-active directory files can be removed. 7. Command "ps" The "ps" command is used to display the status of processes currently on the system, just as on IX. The differences between the two are the available arguments, and the information shown in the listing. Below is a sample listing of all processes currently executing on the system. $ps -ef UID PID PPID C STIME TTY TIME COMMAND root 0 0 0 08:15:33 ? 0:03 sched root 1 0 0 08:15:33 ? 0:01 /etc/init root 2 0 0 08:15:33 ? 0:00 vhand root 3 0 0 08:15:33 ? 0:03 bdflush root 103 1 2 08:17:34 console 0:02 -sh root 173 103 6 09:13:28 console 0:00 ps -ef SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg047 root 90 1 0 08:17:28 ? 0:00 mbf_errlog root 94 1 0 08:17:31 ? 0:01 lpsched (a) (b) (c) (d) (e) (f) (g) (h) (a) UID: The User ID number (as specified in the /etc/passwd file) of the process owner. In a full listing, the login name is displayed in place of the ID number. (b) PID: The process ID number. This field is necessary in order to kill a process. (c) PPID: The process ID number of the parent process. (d) C: Processor utilization for scheduling. (e) STIME: The time the process was created (or started). If started within 24 hrs, then listing is HH:MM:SS. If started over 24 hrs, then listing is Month and Day. (f) TTY: The controlling terminal for the process. If no controlling terminal can be identified, then a "?" is printed. (g) TIME: The cumulative execution time (system and user) for the process. (h) COMMAND: The command name of the process. In a full listing, the full command and all its arguments are listed. GPx SOFTWARE ANNOUNCEMENT 6.2 (Cont.) The arguments for the "ps" command are: -e : list every process on the system -d : list every process, minus parent processes -a : list every process, minus parents and "?" getty processes -f : print a full listing -l : print a long listing -n : names- List only processes for the user ID logon names specified. -t : termlist- List only processes for the terminal identifier specified. -p : proclist- List only processes for the process ID numbers specified. -u : uidlist- List only processes for the user ID numbers specified. -g : grouplist-List only processes for the group ID numbers specified. 8. Command "cp" The "cp" command on VX works similiar to the "copy" command on IX. The "cp" command is used to copy files to the same directory or to other directories. Another VX command with similiar functionality is "mv", which is used for renaming or moving a file between directories. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg048 9. Command "grep" The "grep" command (Global search for a Regular Expression and Print) on VX works similiar to the "match" command on IX. The "grep" command is used to search files for a matching pattern of characters. Every line within a file containing the matching character string will be displayed. The "find" command contains similiar functionality to the "grep" command, except that "find" will match the pattern of characters to the file's name, rather than to the contents of the file. The "find" command provides an excellent method for locating a file within the filesystem. 10. Command "set" The "set" command displays all system environment variables. Among the prominent system environment variables are: HOME: Defines pathname of logon directory (specified in /etc/passwd) PATH: Defines the directory search path for commands PS1: Defines the primary shell prompt PS2: Defines the secondary shell prompt--used to indicate more information is needed for the command to run TERM: Defines the users terminal type; used by vi and other programs GPx SOFTWARE ANNOUNCEMENT 6.3 USEFUL BOSS/VX COMMANDS The following is a list of useful BOSS/VX commands, the list includes BOSS/IX system commands and their BOSS/VX counterparts. Command options for these and other commands may differ. BOSS/IX BOSS/VX Comments file lists the file type of a file, such as commands, ASCII, BASIC or C program find finds a file with a specified name hd prints the contents of standard input in hex and ASCII format kill kill kills a process. On VX kill with the -9 option should be used nice change the priority of a task nohup prevents a child task from aborting when the parent task stops. e.g. nohup nightly.backup > /dev/null & rel creates mbfinstall tapes su changes of the user's user name who am i lists the user on this terminal delete rm removes files and directories SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg049 diskusage du displays amount of diskspace used by a directory install mbfinstall software installation utility rename mv renames a file space df shows the available space on all file systems space dfspace shows the available space and total space for. each file system ttymodes stty changes the terminal attributes ved vi, ed text editors, vi is full-screen screen-editor, ed is a line editor. GPx SOFTWARE ANNOUNCEMENT 6.4 CONTROL SEQUENCES Control sequences are signals which are sent to the current process in execution. The following is a list of control sequences supported in BOSS/VX. ^D = EOF (ends session) ^C = Kills the command being executed ^S = Stops screen output ^Q = Undoes the ^S (restarts screen output) 6.5 INPUT/OUTPUT/ERROR REDIRECTION The input redirection character is < The output redirection character is > The output redirection "with append" character is >> The error redirection character is 2> The error redirection "with append" character is 2>> 6.6 BACKGROUND PROCESSING Background processing on BOSS/VX is accomplished via the & character. Example: To redirect a recursive directory listing of the filesystem to a file (normally takes 30 seconds) in the background, the command would be: ls -lR / > & 6.7 INPUT BUFFER LIMITATION AND EFFECT ON COMMANDS There is about a 5K byte input buffer limit, this means that a shell command cannot have a parameter string longer than 5K bytes. When using commands with masking, such as ls *, the masking character is expanded to a list of files. This list of files is passed to ls as a parameter string. If the length of the parameter string exceeds the input buffer size, an error occurs and the command aborts displaying the message "arg list to long". This is a UNIX limitation, and does not exist on a BOSS/IX system. A workaround for this limit is to 'cd' to the directory you are SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg050 working with or use the utility that does the same as the command. 6.8 HUGE DIRECTORIES If a directory exceeds 32k bytes in size, (2000 or more files) several shell commands display the warning message "WARNING: Directory size > 32KB (directory); notify system administrator", when processing the directory. This is a UNIX limitation and does not cause any troubles. The limitation does not exist on a BOSS/IX system. GPx SOFTWARE ANNOUNCEMENT 7.0 OPERATING SYSTEM OVERVIEW This section gives an overview of the BOSS/VX Memory Management, Filesystem and System Security. 7.1 MEMORY MANAGEMENT Memory management on BOSS/VX is a virtual memory, demand paging implementation. This means that an entire process does NOT have to be in memory in order to execute--only the code being executed at any given instance of time is required to be in memory. If a reference is made to code not residing in memory, than the block (or page) containing the reference will be demanded and brought in from disk (hence, the term demand paging). NOTE: A memory page size is 4 Kb. A BASIC page size (specified in a START size) is approximately 309 bytes. The beauty in this memory management scheme can be seen by considering the fact that most processes, on average, spend 90% of their time in a 10% area of code. Therefore, with virtual memory, a process 20 pages in size, Which seldom executes code in but 2 or 3 of the pages, would only need 2 or 3 pages of memory the majority of the time, rather than 20 pages which would be required in non-virtual memory system. Historically, UNIX required the entire process to be present in order to execute, but with the release of System V, only the pages containing code being referenced is required to be in memory. The advantage of the demand paging algorithm is less swapping because processes larger in size than the amount of available memory space can now begin their execution without forcing the system to swap initially, and more process can exist simultaneously in memory at one time. 7.1.1 AREAS OF MEMORY Main memory is divided into three parts. The first part (lower. address memory) is dedicated to the operating system kernel, the second part contains all the OS tables, and the third portion is user process space. OS Kernel Area The first portion of memory contains the OS kernel. The OS kernel (the /unix file) is the first program loaded into memory by the system loader. The size is approx 644 KB; this area is FIXED in size and cannot be moved or paged. GPx SOFTWARE ANNOUNCEMENT 7.1.1 (Cont.) OS Table Area SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg051 The second portion of memory is allocated for system table space. There are approx 26 tables which are built when the system is booted, and the majority of the table sizes are determined by the dct (dynamic configuration table) file and port configurations. This area is FIXED once the system has booted, and cannot be moved or paged. User Process Area The third and final area of memory is space allocated for 1) process execution and 2) OS workspace. In the past, these two sections (user process space and OS workspace) were separated because memory within the OS workspace was unswappable, however, on BOSS/VX, pages used for both process execution and OS workspace are eligible to be swapped out, hence it is no longer necessary to separate these areas. 7.2 FILESYSTEM The BOSS/VX filesystem is a hierarchical directory structure using similiar directory names as those found on BOSS/IX. The BOSS/VX filesystem is moderately different. This section focuses on the structure of the BOSS/VX filesystem. Included, will be new directory names containing new information, old directory names containing new information, and old directory names . containing old information. 7.2.1 STRUCTURE OF BOSS/VX FILESYSTEM Below is the skeleton structure of the BOSS/VX filesystem. This is how the filesystem will appear in single-user mode. / (root) | ________________________________________________ | | | | | | | | | /bin /dev /etc /shlib /tmp /unix /usr /usr2 /lost+found The directories shown in the base filesystem store the following information: /bin: The /bin directory contains commands. /dev: The /dev directory contain all the device files on the system. The device files for the disk are located within sub-directories called /dev/dsk and /dev/rdsk. GPx SOFTWARE ANNOUNCEMENT 7.2.1 (Cont.) /etc: The /etc directory contains system administration programs and data files. Files include port configuration data, operator account information, and filesystem maintenance programs. /shlib: The /shlib directory contains the system shared libraries and other related files. /tmp: The /tmp directory is used to hold temporary system files. Users should not store files in this directory, SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg052 except on a temporary basis, as contents in this directory are deleted at system startup. /unix: The /unix file contains the operating system kernel. This file is loaded into memory when the system is first booted. /usr: The /usr directory is used for mounting the filesystem (also called usr) containing all the files, programs, and applications normally used in a multi-user configuration. NOTE: If the system doesn't have a separate usr filesystem the files, and programs are contained within the root filesystem. /usr2: The /usr2 directory is used for mounting the filesystem (also called usr2) containing the users' private directories and private files. /lost+found: A /lost+found directory will be present on any partition containing a filesystem. The lost+found directory is used to hold lost files for a filesystem, after a file system repair. 7.2.2 MOUNTABLE FILESYSTEMS During a new install of the OS two additional filesystems can be created on drive 0. If either one or both of these filesystems are created they will be mounted each time the system enters multi-user mode. The filesystems are usr and usr2, which get mounted to the /usr and /usr2 directories respectively. The usr Filesystem Below is a skeleton sketch of the BOSS/VX filesystem after the usr partition is mounted to the /usr directory. This is how the filesystem will appear in multi-user mode. NOTE: If a seperate filesystem is not created for usr then the directories listed below would be in the /usr directory on the root. GPx SOFTWARE ANNOUNCEMENT 7.2.2 (Cont.) /(root) _________________________|______________________ | | | | | | | | | /bin /dev /etc /shlib /tmp /usr /unix /usr2 /lost+found | | ____|___ | | | | /dsk /rdsk _______________|____________________ | | | | | | | /adm /bin /lib /mbf /spool /tmp /lost+found _____|_________ | | | | /PS /bin /etc /atp The additional directories shown under /usr store the following SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg053 information: /usr/adm: The /usr/adm directory contains log files which monitor the access and usage of the system. /usr/bin: The /usr/bin directory contains UNIX commands and utilities which are normally accessed in multi-user mode. /usr/lib: The /usr/lib directory contains UNIX libraries and other related files. /usr/mbf: The /usr/mbf directory contains MBF value-added commands, utilities, tools, and other related MBF enhancements. /usr/mbf/PS: The /usr/mbf/PS directory contains MBF Presentation Services files. /usr/mbf/bin: The /usr/mbf/bin directory contains MBF value-added command and utilities. Note, both utilities and commands are stored in the same directory. /usr/mbf/etc: The /usr/mbf/etc directory contains MBF system administration files, such as MBF spooler-related files, error messages file, and software (Public ID) keys. /usr/spool: The /usr/spool directory contains UNIX spooler-related files. /usr/tmp: The /usr/tmp directory is used to hold temporary system files related to commands and utilities located under the /usr directory. /usr/lost+found: The /usr/lost+found directory is used to hold lost files for the /usr filesystem. GPx SOFTWARE ANNOUNCEMENT 7.2.2 (Cont.) The usr2 Filesystem The usr2 filesystem is an optional filesystem which may be present on drive 0. If usr2 partition is present and in the /etc/fstab file, then its filesystem will be mounted to the /usr2 directory automatically when the system enters multi-user mode. The usr2 filesystem can be used as a separate filesystem for storing application software and related application data files.. The creation of the usr2 filesystem can only be specified during the initial OS installation. 7.3 SYSTEM SECURITY On a multi-user computer system, a minimum amount of security is required to protect user files and system integrity from malicious acts of other users. Such protection is achieved on BOSS/VX through: o file access privileges o root privileges o account passwords o menu permission codes SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg054 Additional security is often added to protect product revenue and to guard against software pirating. On BOSS/VX, such protection is achieved through: o SSN o Software keys o Configuration records 7.3.1 FILE ACCESS PRIVILEGES The command "chmod" and the utility "secure" are used on BOSS/VX to define file access privileges for a file. Every file on BOSS/VX has three sets of access privileges, one for the "owner", one for the "group", and one for everyone else on the system. For example, -rwxr-xr-- 1 root sys 4096 Jul 23 11:19 file1 would specify access privileges of "read", "write", and "execute" for the owner (in this case root), access privileges of "read" and "execute" for the group (in this case sys), and access privileges of "read" for all other users on the system. The command syntax for changing the access modes is: chmod (u|g|o|a) (=|+|-) (r|w|x) OR chmod (nnn) where each n represents a type of privilege (owner, group, other), when translated to binary. GPx SOFTWARE ANNOUNCEMENT 7.3.2 ROOT PRIVILEGE A user with root privilege has the authority to modify characteristics of the operating system environment. Caution must be used when exercising root privileges since actions may effect other users on the system. Examples of commands and utilities requiring root privilege are: o shutdown o date -i o oprinfo o configure 7.3.3 ACCOUNT PASSWORDS Account passwords prevent users from logging onto other user's accounts and altering their files. Account passwords are optional and can be changed using the "oprinfo" utility or the "passwd" command. User account information is stored in the file /etc/passwd, which is accessible (readable) by everyone. The encrypted password for each user is saved in the file /etc/shadow, which is only readable by the "root" user. 7.3.4 MENU SECURITY CODES SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg055 Menu security codes are used to deny some user's access to certain utility programs and menus while allowing access to other users. The menu security codes can be viewed/displayed through the menuedit utility. NOTE: Security for menus is only active if the user's starting point is menus. If menu security codes are defined for a user, then the user may only access utility programs or menus for which he has a corresponding security code. If menu security codes are not defined for a user, then the user will have access to all the utility programs and menus (i.e., full access is assumed). Below is a list containing the menu security codes: o BASIC utility programs: code b o System Utilities: code u o Communication: code c o Intersystem Transport: code i o File Transfer Utility: code f o MAGNET: code l 7.3.5 SSN The SSN is a number which is used to uniquely identify every multi- user system which MAI Basic Four sells. This SSN is used by software keys and configuration records to identify the system. GPx SOFTWARE ANNOUNCEMENT 7.3.6 SOFTWARE KEYS Software keys are used to protect integrety and ownership/license rights to MAI Basic Four software. When a secured software package is licensed by a customer, a key (8 digits) is included with the package. This key is a value unique to the customer's system and the software application being installed. The values of the current software keys installed can be viewed by typing # pg /usr/mbf/etc/level/* New software keys can be entered when the product is originally installed, or by using the following command: # install_key 7.3.7 CONFIGURATION RECORDS Configuration records indicate to the operating system which hardware components are available for use on a system. A sample configuration record appears below: BOSS/VX System Configuration Record System Type 4127-xxxxxxx Release Level xxxx Subrelease Level xxx Serial Number xxxxxxxx Memory Limit (KB) 16 Max # 8-Way Controllers 2 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg056 Max # 16-Way Controllers 2 Max # SCSI Controllers 1 Max # Disks 1 Max # 1/4 Tape Drives 1 Max # Parallel Printers 1 Max # Floppy Drives 1 Max MegaBytes of FS space 380 The values of the current configuration record for the system can be viewed by typing: # rconf The Configuration Record information is stored on disk, in a file called /etc/scr. This file is encrypted and should not be touched or tampered with. If this file is missing, or if information in the file is corrupted, the system will not boot; i.e., a panic (system crash) will occur. GPx SOFTWARE ANNOUNCEMENT 8.0 CUSTOMIZATION This section give details for customizing your Operating System Parameters (DCT file) and the System CMOS. 8.1 OPERATING SYSTEM PARAMETERS CUSTOMIZATION On standard UNIX V.3.2, system configuration of buffers, processes, file descriptors, etc, is defined at compile time, and once the Operating System is compiled, these values cannot be changed without re-compiling the OS. For the market place which MBF deals with, this form of system configuration is unacceptable because it does not allow flexibility of changing parameters as user's needs change. As a result, MBF engineering has modified the initialization of these variables to take place at system boot time rather than compile time, thus allowing the allocation of system resources to vary from system- to system, and from boot-to-boot. On BOSS/VX, a DCT (Dynamic Configuration Table) file is used to hold 77 different OS parameters which the kernel will use during system boot to define various OS data structures and variables. The DCT file is a compiled binary file and must exist on disk in the root's filesystem. The majority of the 77 parameters should not need to be modified, and. should remain the same for each and every customer. The only parameters which may need modification are: - Number of System Buffers - Number of Inodes - Number of Open Files - Number of Processes - Verbose Kernel Messages In addition, the compilation, de-compilation, and editing of DCT files can be moderately complex and confusing, and errors made while editing the DCT file(s) can degradate system performance and/or cause system hangs and system errors. It is for the above two reasons that the "configdct" utility was developed, and the "configdct" utility is the recommended method for modifying the DCT file(s). SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg057 Upon invoking "configdct", the utility will prompt for an input DCT binary file, and an output DCT binary file. The input DCT file will be read, and its values loaded into the utility. All values are loaded, however, only the above five parameters will be displayed. The output DCT file is where the changes will be saved--this can be the same filename as the input DCT file (old configuration will be overwritten), or it can be a new filename which previously did not exist. NOTE: The default system DCT file is /etc/dct. Before running this utility, a copy of this file should be made to a different name. on the root so it can be used if the modified file fails. GPx SOFTWARE ANNOUNCEMENT 8.1 (Cont.) The current values of the five parameters will be displayed, along with the range of acceptable values for each parameter. NOTE: For the Verbose Kernel Messages parameter, a 0 indicates "verbose mode" OFF, and a 1 indicates "verbose mode" ON. 8.2 MODIFYING THE CMOS RAM CONFIGURATION This section gives the steps necessary to change the system's CMOS RAM. The CMOS RAM contains information on the physical hardware installed in the CCA. If this hardware is changed, more added or something removed, the CMOS RAM must be changed. The CMOS RAM also contains the port attributes for COM1 and COM2. NOTE: If power is lost to the CMOS RAM the default configuration will be used and the configuration of the system must be restored. Step 1: If the system is powered down, power up the system. If the system is already powered up, ensure that it is shutdown properly before rebooting it. During the self test/load the following message will be displayed: PLEASE ENTER '1' FOR SETUP OR NECESSARY CONTROL FUNCTIONS TO ENABLE COM2 . Step 2: Entering a '1' will cause the CMOS RAM configuration menu to be displayed. If a is entered or if nothing is entered the system will continue with a normal boot. The CMOS RAM configuration menu will have the following options: (The information after each option is used as an example.) 1. DATE: 07/14/1989 2. TIME: 12:00:37 3. FLOPPY DRIVE A: 1.44M FLOPPY DRIVE 4. FLOPPY DRIVE B: NOT PRESENT 5. FIXED DISK 1: SCSI PRESENT 6. FIXED DISK 2: SCSI PRESENT 7. PRIMARY DISPLAY: MONOCHROME 8. MEMORY BELOW 1 MEG.: 00640K 9. MEMORY ABOVE 1 MEG.: 03072K A. COPROCESSOR.: NOT PRESENT B. COM1: 9600,O,7,1 C. COM2: 2400,O,7,1 D. UPDATE ALL ITEM SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg058 E. END AND REBOOT SELECT WHICH ITEM ? GPx SOFTWARE ANNOUNCEMENT 8.2 (Cont.) Step 3: Enter the number of the item you wish to change followed by a . If after you get into the menu to change an item you decide not to change any of the information enter a for all prompts and the present information will remain the same. The following is the information for each item: 1. DATE: This item will change the system's date. You will be prompted for year, month and day. Follow each entry with a . Enter alone to keep the present information. 2. TIME: This item will change the system's time. You will be prompted for hour, minute and second. Follow each entry with a . Or enter alone to keep the present information. 3. FLOPPY DRIVE A: This will allow you to change the size of floppy drive A or show that one is not present. The options are displayed for all floppy drive sizes available. Enter the option number of the drive you wish followed by a . Enter a alone for no change or 0, if no drive is present. 4. FLOPPY DRIVE B: Only floppy drive A is supported, this should stay 'NOT PRESENT'. 5 & 6. FIXED DISK: This will remain 'SCSI PRESENT' for SCSI disk drives. 7. PRIMARY DISPLAY: The BOSS/VX OS uses COM1 as the primary display, so this should remain "MONOCHROME'. 8. MEMORY BELOW 1 MEG.: This should always remain 640K. 9. MEMORY ABOVE 1 MEG.: This will be a minimum of 3072K for a 4 Meg. system. You will be prompted for the amount of memory above 1 Meg. The entry is in 1024K increments. Follow your entry with a . If you don't wish to change the information already present enter a alone. A. COPROCESSOR: A 387 coprocessor is not supported, this should remain 'NOT PRESENT'. B. COM1: This will set the attributes for your COM1 port. The terminal must be set to match these entries. After you get out of this utility you will have the option to change the attributes on your terminal, so while you are in this utility don't change the attributes on the terminal. Follow each entry with a , or just enter for no change. The options available for the COM1 port attributes are: GPx SOFTWARE ANNOUNCEMENT SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg059 8.2 (Cont.) BAUD RATE: 300, 600, 1200, 2400, 4800, 9600 PARITY: NONE, ODD, EVEN DATA BITS: 7 BITS, 8 BITS STOP BITS: 1 BITS, 2 BITS C. COM2: This will set the attributes for your COM2 port. The instructions for this option are the same as for COM1 above. D. UPDATE ALL ITEMS: This option will allow you to change all the items. Follow the instructions starting with item 1 and follow the instructions for each item through item C. Step 4: After you have made the necessary changes to the CMOS RAM configuration enter 'e', to end and reboot. You will be given the COM1 and COM2 port attributes followed by the prompt: PLEASE CHECK CONFIGURATION OF COM1, THEN TYPE 'ENTER' TO CONTINUE. (TYPE 'BREAK' FOR OUTPUT SCREEN TEST) If you have changed the COM1 port attributes, at this time change the attributes on the terminal. Enter to continue, if you didn't change COM1's attributes or after you have changed the terminal's attributes. Step 5: Next you will be prompted with: CONFIGURATION OF COM1 O.K., TYPE 'ENTER' TO CONTINUE. You are now done with the configuration of the CMOS RAM. Enter and the system will automatically reboot starting with the self test. GPx SOFTWARE ANNOUNCEMENT 9.0 PERFORMANCE 9.1 SAR (SYSTEM ACTIVITY REPORTER) PERFORMANCE TOOLS The BOSS/VX Operating System comes standard with the UNIX performance tools "sar". These tools are used to gather system activity data or to extract it from a file where previously data was stored. This data is useful for tuning your system's configuration. Included in this section are instructions for invoking and using the tools, information on to interpret the tool's results, and appropriate actions to take if a problem is found. SAR SYNTAX A major advantage of the sar performance tool is the variety of ways it can be used. Sar can be setup to perform data collection in the background, display a file containing collected data, or report current system information directly to the terminal screen. The syntax for displaying current system information to the screen is: # sar (options) (delay between snapshots) (no. of snapshot) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg060 The syntax for starting sar in the background, redirecting the data to a file is: # nohup sar -o (filename) (delay) (no. of snapshot) > /dev/null & The syntax for viewing a file containing collected sar data is: # sar -f (filename) (options) The syntax for displaying the default sar data file is: # sar (options) The default file, when 'cron' is running, takes a snapshot once every 20 minutes during normal work hours (8 AM to 5 PM), and once an hour during nonwork hours. SAR OPTIONS The sar utility monitors over 12 different system activities. Below is a list of options for displaying the different activities: -a File Access -b Buffers -c System Calls -d Disk I/O -m Message and Semaphore Calls -p Paging -q Run and Swap Queues -r Memory and Swap Space -u CPU Utilization -v DCT Tables -w Swapping and CPU Switching -y Terminal Activity -A All of the Above GPx SOFTWARE ANNOUNCEMENT 9.1 (Cont.) The five areas of most interest in the MBF Environment are DCT tables, buffers, remaining memory and swap space, disk I/O, and CPU utilization. The following is a discussion of each of those 5 areas. 1. DCT System Table Utilization (sar -v) The "sar -v" command reports the usage levels of system tables allocated in accordance with the DCT file. The "sar -v" command is used to determine if system tables are over or under configured. The. system tables monitored by "sar -v" include processes, inodes, and open files (buffers activity is displayed with a different sar option). Below is a sample listing from a "sar -v" command: 13:20:00 proc-sz ov inod-sz ov file-sz ov lock-sz 13:40:00 33/100 0 78/300 0 62/300 0 2/100 14:00:00 53/100 0 142/300 0 134/300 0 2/100 14:20:00 83/100 1 210/300 0 187/300 0 2/100 proc-sz Number of process table entries being used at time shown, and total number of entries in process table. inod-sz Number of inode table entries being used at time shown, and total number of entries in inode table. file-sz Number of file table entries being used at time shown, and total number of entries in file table. ov Number of times an overflow occurred (one column for each of SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg061 the above three items) lock-sz Number of "shared memory records" being used at time shown (this field should never need to be modified on the BOSS/VX OS). In the above example, the number of process table entries should be increased since an overflow regarding processes occurred between 14:00 and 14:20. The number of inodes and files appear to be large enough since no overflows occurred regarding these parameters. 2. Buffer Activity (sar -b) The "sar -b" command is useful for monitoring the efficiency of the file system. The file system buffers consist of a number of 1024 byte memory blocks. Read and write requests from the user do not necessarily do a physical read/write on a device. Instead a write may be delayed and written later, or a read may read the data from the file system buffer in memory that already contains the desired disk block. This reduces the overhead of data transfer between disk and the user's memory area. GPx SOFTWARE ANNOUNCEMENT 9.1 (Cont.) Below is a sample listing from a "sar -b" command. Note that values below are displayed in average per second over a 20 minute period in this example. 13:20:00 bread/s lread/s %rcache bwrit/s bwrit/s %wcache/s pread/s pwrit/s 13:40:00 1 4 80 2 8 78 0 0 14:00:00 0 2 94 3 9 68 0 0 14:20:00 3 10 68 1 2 54 0 0 bread/s Average number of physical blocks read into system buffers from disk per second. lread/s Average number of logical blocks read from system buffers per second. %rcache Percentage of disk reads found in buffer cache; often referred to as the disk read cache hit ratio. bwrit/s Average number of physical blocks written from the system buffers to disk per second. lwrit/s Average number of logical blocks written to system buffers per second. %wcache Percentage of disk writes to buffer cache; often referred to. as the disk write cache hit ratio. pread/s Average number of physical read requests per second. pwrit/s Average number of physical write requests per second. It is recommended that the disk read cache hit ratio average 90% or better, and the disk write cache hit ratio average 65% or better, in order to maintain an effective level of system buffering. In the above example, both the read hit ratio and the write hit ratio have fallen below the recommended level for effective buffering. In SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg062 this case, the number of buffers should be increased using the "configdct" command to improve system buffering. 3. Memory Availability and Amount of Swapping (sar -r and sar -w) sar -r The "sar -r" command monitors the amount of memory and swap space remaining on the system. The "sar -r" is a tool for determining if the system is swapping, how much memory remains before swapping occurs, and how much data is on the swap partition. Below is sample listing of the "sar -r" command. 13:20:00 freemem freeswp 13:40:00 206 81920 14:00:00 198 81920 GPx SOFTWARE ANNOUNCEMENT 9.1 (Cont.) freemem Amount of 4KB pages of memory available at that instance of time. freeswp Amount of disk blocks available at that instance of time. In the above example, the system is not swapping, and approximately 200 pages (or about 800KB) of memory is available before swapping will occur. If swapping does occur, this will be indicated with a swap partition containing less than the maximum amount of free swap space. sar -w If swapping has occurred, more information regarding the amount of swapping can be obtained with the "sar -w" command. The "sar -w" command displays when and how much information is being swapped out and swapped in, and its effect on the CPU in terms of process switches. Below is a sample listing of the "sar -w" command. 13:20:00 swapin/s bswin/s swapot/s bswout/s pswch/s 13:40:00 0.0 0.0 0.0 0.0 37 14:00:00 0.0 0.0 0.0 0.0 42 14:20:00 1.7 5.1 2.5 9.8 101 swapin/s Average number of transfers from swap partition into memory per second. bswin/s Average number of blocks transferred from swap partition into memory per second. swapot/s Average number of transfers from memory to swap partition per second. bswot/s Average number of blocks transferred from memory to swap partition per second. pswch/s Average number of times CPU switched processes per second. In the above example, the system began swapping at around 14:00, and an average of 9.8 blocks of data per second were swapped out over the 20 minute period. Note that in general, swapping will impact the number of SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg063 process switches. If the value of swapot/s is greater than 1, add more memory. Also check %swpocc in the -q option. Check the value of %wcache and %rcache, and if possible reduce the number of system buffers to make more memory available. 4. Disk I/O and File Access Activity (sar -d and sar -a) sar -d The "sar -d" command monitors the amount of disk I/O being performed on the system, and the efficiency in which the disk I/O is being performed. The "sar -d" is used to identify faulty disk controllers, and to determined if the amount of disk I/O is excessive enough to slow down the system. GPx SOFTWARE ANNOUNCEMENT 9.1 (Cont.) Below is a sample listing of the "sar -d" command. 13:20:00 device %busy avque r+w/s blks/s avwait avserv 13:40:00 dsk-0 6 1.1 3 5 2.0 23.9 fdsk-0 93 2.1 2 4 467.8 444.0 device Name of the device being monitored. %busy Percent of time device was servicing a transfer request. avque The average number of requests outstanding during the period of time (measured only when the queue is occupied). r+w/s Number of read and write transfers to the device per second. blks/s Number of 512 byte blocks transferred to the device per second. avwait Average time in milliseconds that transfer requests wait idle in the queue (measured only when the queue is occupied). avserv Average time in milliseconds for a transfer request to be completed by the device (includes seek, rotational latency, and data transfer times). If the value of r+w/s is greater than 50 it may be possible to improve the performance by: 1) Partition the disk in such a way that the most commonly used files are on the same partition. If more than one disk is available, divide the most commonly used files between different disks. 2) Backup the files, make a new file system and restore the files. This will be useful only if the existing file system is reasonably old and its files are fragmented. 3) Add another disk and divide the load between the disks. 4) Check the file system buffer hit rates using option -b to ensure they are being used efficiency. sar -a The "sar -a" command monitors file access activity, including how many files are looked up, the number of inodes looked up, and the number SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg064 of directory blocks used for file lookup activities. If the number of directory blocks and inodes used to look up files is excessively greater than the number of files looked up, then the BASIC prefix list may be too long and not defined efficiently. GPx SOFTWARE ANNOUNCEMENT 9.1 (Cont.) Below is a sample listing of the "sar -a" command. 13:20:00 iget/s namei/s dirbk/s 13:40:00 10 4 12 14:00:00 47 2 55 iget/s Number of inodes accessed per second. Only inodes accessed in relation to file lookup are counted. namei/s Number of files accessed (or looked up) per second. dirbk/s Number of directory block read (related to file lookup) per second. 5. CPU Utilization (sar -u and sar -q) sar -u The "sar -u" command displays the utilization of the CPU. The "sar -u" command can be used to detect a CPU-bound system, insufficient memory or disk bottlenecks. Below is a sample listing of the "sar -u" command. 13:20:00 %usr %sys %wio %idle 13:40:00 1 6 10 82 14:00:00 12 31 33 24 14:20:00 7 28 15 50 %usr Percent of time CPU is in user mode. %sys Percent of time CPU is in system mode. %wio Percent of time CPU is waiting for Input/Output completion. %idle Percent of time CPU has no work to do. On a typical system, the amount of time in user mode and system mode will be approximately equal. A high %wio (greater than 7) generally indicates a disk bottleneck. Use option -d to determine and fix a disk. bottleneck. A high %idle with poor system response generally indicates a memory bottleneck, as time spent waiting for memory is attributed to %idle. sar -q The "sar -q" command monitors the process run and process swap queues. The "sar -q" command provides additional information regarding the CPU utilization and the degree of swapping. 13:20:00 runq-sz %runocc swpq-sz %swpocc 13:40:00 1.7 63 14:00:00 1.0 74 1.0 31 14:20:00 1.3 58 1.2 39 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg065 GPx SOFTWARE ANNOUNCEMENT 9.1 (Cont.) runq-sz The average length of the run queue of processes in memory (measured only when the queue is occupied). %runocc Percentage of time run queue is occupied. swpq-sz The average length of the swap queue of processes to be swapped out to swap partition (measured only when the queue is occupied). %swpocc Percentage of time swap queue is occupied. If the runq-sz is consistently greater than 2 and % runocc is greater than 90, then the system is CPU-bound. Try reducing system load or shift workload so some jobs are running during non-peak hours. If values are consistently logged in the swpq-sz and %swpocc columns, then more memory or a smaller buffer pool would help reduce swapping activity. 9.2 SYSTEM MEMORY REQUIREMENTS Following are the memory charts for the GPx 340 and GPx 440 systems. The right side of these charts show the amount on memory in the system, the bottom shows the number of users and the left side shows the response time in seconds using the CBS-II Benchmark test. From these charts you can determine the amount of memory a customer would need depending on the type of response they are looking for. GPx SOFTWARE ANNOUNCEMENT 9.2 (Cont.) 10.0 SYSTEM CRASH/DUMP If the BOSS/VX Operating System encounters an error it can't recover from it will either produce a Core Dump or System Crash (PANIC). This section describes the two and gives the procedures to recover from both. 10.1 CORE DUMP If the OS encounters an error or finds a corruption in a process that it can't recover from involving only that process, it will produce a core dump and exit. The core dump effects only the process that caused it, the rest of the system is not effected. The core dump is an image of the process's work area in memory. This data is written to a file called 'core' located in the working directory. This file can be looked at to help determine the cause of the dump. If a core dump occurs, write down as much as you or the operator running the process can about the steps that occured just prior to the core dump. This should include information on what was running, what was displayed, what other users were doing at that time and anything else that can later be used to reproduce the core dump. A back-up of the core dump should be made. This can be done by the use of the 'tsave' command or utility. GPx SOFTWARE ANNOUNCEMENT 10.2 SYSTEM CRASH (PANIC) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg066 The BOSS/VX Operating System provides a 'user friendly' program to recover from a premature system shutdown situation (Crash). A 'premature shutdown' is typically a power loss, inadvertent use of the NMI button, forced dump for troubleshooting, or fatal operating system error. When the user attempts to reboot, the system will check all filesystems to see if any of them were left mounted. If it finds a filesystem that was left mounted it will automatically repair that filesystem. Some data maybe lost, but the filesystem will be restored to an usable condition. In addition to repairing the mounted filesystems, the BOSS/VX Operating System recovery will allow the user to save a copy of the system's memory at the time of the crash. This memory information is called a crash dump. The rest of this section gives the information required to save the crash dump to tape and how to force a crash dump. 10.2.1 SAVING A CRASH DUMP TO TAPE When the system crashes, the console terminal will display a PANIC message, followed by the message: Trying to dump xxx Pages ............................................... Where 'xxx' will be determined by the size of system memory. Make sure you write down the PANIC number and description . displayed. In addition write down as much as you or the operators can about the steps that occured just prior to the crash dump. This should include processes that were running,. what was displayed on the terminals at the time of the crash and anything else that can be used to help determine the cause of the crash dump. This information should stay with the crash dump tape, as it will be required when the crash dump is being analyzed. When the system has completed writing the crash dump to the swapper the following messages will be displayed: xxx Pages dumped PRESS RETURN TO REBOOT, OR POWER OFF THE SYSTEM At this point press the to reboot the system. After the proprietary message is displayed the following messages will be displayed: There may be a system dump memory image in the swap device. Do you want to save it? (y/n)> If you enter 'n', the boot process and automatic recovery procedure will continue and the crash dump will be lost. If you enter 'y', you will be prompted with: Insert tape cartridge and press return, or enter q to quit.> GPx SOFTWARE ANNOUNCEMENT 10.2.1 (Cont.) If you enter 'q', the boot process and automatic recovery SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg067 procedure will continue and the crash dump will be lost. If you press messages will be displayed telling you to wait, followed by messages telling you that the crash dump is being saved. When the write to tape is complete the following will be displayed: Done. Press return to continue> Remove the tape from the tape drive and enter to continue with the boot process and automatic recovery process. 10.2.2 FORCING A SYSTEM CRASH DUMP For troubleshooting reasons, a look at the system's memory might be required, for example, if all the terminals on a system are frozen for more than 15 minutes, then a crash dump of memory will help determine the problem. To force a system crash dump, press the NMI button located on the back of the CCA. A PANIC message will be displayed. Follow the steps in the above procedure to save the crash dump to tape. 10.2.3 WRITING A CRASH DUMP TO HARD DISK At times a copy of the crash dump may need to be written to the customer's hard disk so that it can be looked at. To do this, after the system is back up, place the crash dump tape in the tape drive. Enter the command '/etc/ldsysdump filename'. Where 'filename' is any name you choose to restore the dump. The file will require at least 10% more filesystem space than the system's memory to be restored. After the file is restored to the hard disk, remove the tape from the tape drive. The '/etc/crash' command can now be used to look at the crash dump. 10.2.4 RECOVERY AFTER A CRASH DUMP As described previously in this section, after a system crash dump, the automatic recovery program will check and repair any filesystem that was left mounted during the crash dump. In addition to checking and repair the filesystems, it will check to see if any of the files lack integrity. Also, at times, the directory pointer to a file maybe lost. The rest of this section describes what needs to be done to recovery from both cases. GPx SOFTWARE ANNOUNCEMENT NOTE: At this point we lose user friendliness 10.2.4.1 FILES THAT LACK INTEGRITY A file that lacks integrity, is one that did not. have all of the written data, flushed to disk by the OS. (The OS will automatically flush the system buffers every 30 seconds). A file that lacks integrity will have an integrity flag set and when it is accessed by BASIC will produce an error 65. In addition, since the data written to the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg068 file was not written to disk, its contents will have to be checked for accuracy. During the automatic file repair, a file list is produced of the inodes of the files lacking integrity. This list will be found in the '/etc/tmp' directory. After the system is repaired and up and running again, before any data processing, perform the following steps: 1. Do an 'ls' of '/etc/tmp'. If any file(s) with the following name format is found , then continue following these steps, otherwise there were no files lacking integrity found and you can skip the rest of these steps. 2. Use the following command to convert the filelist of inodes to a filelist containing the file names. The command is 'fscklist /etc/tmp/'. This will need to be run for each file found in the '/etc/tmp' directory. 3. This conversion process could take a few minutes. For future reference, make a copy of the ".f" files generated. Next, run frepair analyze mode under the "selected files" option of the utility. In response to the prompts under this option, enter the file list names (the ".f" files) which have been generated for each of the . repaired file systems. If the files appear to be in good shape (no problems), use fsck -c to clear the integrity bit. GPx SOFTWARE ANNOUNCEMENT 10.2.4.1 (Cont.) Those files which have problems may be restored from backups. If the backups are inappropriate or unavailable, an frepair in repair mode (using an edited version of the ".f" file) may be used to reconstruct the file. The ability of frepair to restore a file reflecting all application data records at the time of the system crash will depend on the nature of the file corruption which frepair encounters. A manual inspection of the file, or comparison of the file with the last backup, is recommended after reconstruction of the file. 10.2.4.2 LOST FILES If, during the automatic file repair, a file is found. that has lost its directory pointer, it will be renamed 'lost_' and placed in the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg069 '/lost+found' directory for the filesystem the file was on. So there is a '/lost+found' directory for each filesystem. For the /usr filesystem the file will be found in the '/usr/lost+found' directory. Before continuing to process, the file(s) will have to be identified, renamed back to their proper name and placed back in the directory they came from. To recover the file(s), first get a directory listing of the '/lost+found' directory using the 'ddisplay' utility. After getting this listing go. into BASIC. If the file is a BASIC data file OPEN the file and read its contents. If the file is a BASIC program load it and list it. From this information you or the Software Vendor should be able to identify any application files. If the file is a OS program or data file that can not be identified, then an OS update should be performed. In many cases the file was a file that the OS was using to perform one of its tasks. These types of files can be removed (erased). After a file is identified it can be renamed and moved back to its proper directory by using the 'fmove' utility. If you are unable to identify a file, it should be backed up and removed from the system. If you later find a file is missing the backup can be restored and the file checked to see if it is the missing file. GPx SOFTWARE ANNOUNCEMENT 11.0 FOR YOUR INFORMATION This section gives helpful hints to aid you while you are working with the GPx Series 40 System and BOSS/VX. 11.1 UMASK AND BMASK BOSS/VX uses two system variables to determine the file modes or access rights for a file when it is created. One, umask, is used when the file is created in the UNIX enivorment and is a standard UNIX system variable. The other, BMASK, is used when files are created in the BB90 environment. This variable is an MBF added value variable. Both variables work the same way. The variable has a value assigned such as 022 or some other 3 number value. Each one of these numbers is an octal number. The value in the variable is masked with 666 at the time a file is created to come up with an octal number that when translated to binary represents the file modes for the file. Below are a few examples using umask, keep in mind BMASK works the same way: umask=022 000 010 010 NOTE: When masking 1+0=1 all mask =666 110 110 110 others = 0. --------------------------- 644 110 100 100 file modes rw- r-- r-- umask=000 000 000 000 mask =666 110 110 110 --------------------------- 666 110 110 110 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg070 file modes rw- rw- rw- umask=111 001 001 001 mask =666 110 110 110 --------------------------- 666 110 110 110 Note in the last example the last digit or the execute bit was not set, this is per design. There are only two ways to set the execute bit. The first is to use the chmod command or file security utility and do it manually. The second is to create the file as a 'C' program using the 'C' compiler. Also a umask or BMASK value of just 0 means 000. To find what the system value for these are, from the shell enter umask or echo $BMASK . To set umask enter 'umask ###' and to set BMASK enter 'BMASK=###', both must be entered from. the shell. After changing BMASK it must be exported: "export BMASK". GPx SOFTWARE ANNOUNCEMENT 11.1 (Cont.) The standard default for umask is 022 or rw- r-- r--, for BMASK is 0 or rw- rw- rw-. umask is set in the /.profile file and can be changed there to the standard your system will use or it can be removed from there and added to the /etc/profile file. The /etc/profile file is where the BMASK variable is set. NOTE: Before restoring files using the transport utilities ensure that umask and BMASK are set to match the file modes you wish. Otherwise you will have to change them manually. NOTE: umask has a 4th octal digit that is a leading digit and used for a forth option in each file mode as follows: OWNER GROUP OTHERS set user id set group id save swapped text If this digit is not added when umask is set, it is assumed to be 0. 11.2 ADDING A SECOND DISK DRIVE UNIX provides a user friendly utility to add another disk drive to a system. This utility is used after the disk hardware has been installed using the information in section 4 of this document or by using the GPx INSTALLATION and MAINTANCE manual. This utility will allow you to set the number and size of the disk partitions on the new disk. It will also ask for the name of the directory you wish to mount the partition on and if you want to have the partition mounted automatically at boot time. Following are the instructions to use this utility. Ensure you are the super-user or root before starting. From the shell enter 'diskadd ' You will be prompted to enter the drive number to be added. Enter 1 if this is the second disk on the system. You will then be given disk information on how many cylinders are on SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg071 the disk. A listing of the default partitioning is displayed next. The default contains three partitions, one of which is 'tmp'. This partition (tmp) can be used if you want to move the tmp directory on the root to the second disk. You are prompted with: Is this allocation acceptable to you (=n; y/n)? If you answer yes to this prompt then the default partitions will be used. If you enter no to this prompt you will be prompted with questions to tailor the number of disk partitions to met your system's needs. GPx SOFTWARE ANNOUNCEMENT 11.2 (Cont.) Next you will be asked the directory name(s) to use for mounting the partitions. After you have entered the names of the disk partitions you wish, the size of a cylinder on the disk is displayed. You will then be prompted to enter the number of cylinders for each partition. After you have accepted the number of disk partitions, names and size of the partitions you will be asked if you wish to have the partitions mounted automatically. If you answer yes, the partitions will be mounted automatically at mount time. If you answer no, you will have to manually mount the partitions. The partitions and directories requested will be created and filesystems created on the partitions. The utility will return to the. shell when it completes. To use the new partitions prefix your file names with the directory names used in the utility. For example if you use the name dsk2 for a directory in diskadd then to access a file on that partition use '/dsk2/filename'. NOTE: If you answered yes to automatically mount the filesystems, they will be mounted at the end of the utility and can be used without a reboot. 11.3 RENAMING THE USR2 PARTITION In some cases you may wish to mount the usr2 partition to a directory other then /usr2. If you do this without changing the disk label a warning message will be given each time the partition is mounted telling you that is mounted to . This is not a problem, but may cause an issue with the customer. This section details the steps required to change the disk label and other information on the system to have the partition mounted to the new directory automatically. NOTE: Before preforming this operation it is recommend you have a. complete verified back-up of the customer's usr2 partition. WARNING: Do not rename the usr partition. The OS uses this partition and if it can not find it, the OS will not operate properly. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg072 The first step is to create the new directory you wish to mount the usr2 partition to. To do this use the command: mkdir /new_name /new_name = the new directory name you wish to use. This will be the same name used later for the partition name and is limited to 6 characters. GPx SOFTWARE ANNOUNCEMENT 11.3 (Cont.) NOTE: Ensure you do not use a name of a directory that already exists. To label a disk volume first unmount the usr2 partition and then use the following command: labelit /dev/dsk/0s4 new_name new_name new_name = the name used for the mkdir command. To ensure you keep the same name thoughout the system use 'vi' to modify the /etc/partitions file. Change usr2 in the file to new_name. To have the partition automatically mounted to the new directory use 'vi' to modify the /etc/fstab file. Change /usr2 in the file to /new_name. After these steps are complete the next time the system is booted into multi-user mode the data on the usr2 partition will now be accessed by using the new name you defined. 11.4 ADDING A NON-MBF TERMINAL TO THE MBF CONFIGURE UTILITY. This section gives the steps required to add a non-MBF terminal to the MBF Configure Utility, which will allow you to use the terminal in BASIC. WARNING: Using these steps will not guarantee that the terminal will function properly in BASIC. There may be some functions of the terminal that do not work in BASIC and/or some BASIC functions that do not work with the terminal. It is a good idea to have the customer test the terminal with their application to ensure it works the way the want it to. NOTE: These steps are to add a terminal for use in BASIC. To add a. terminal for use in UNIX, ensure there is an entry for the terminal in the /usr/lib/terminfo directory. To enable the terminal, set the term system variable to equal the terminal you wish to use then export the term variable. ex: term=wyse50 export TERM To add a terminal for use in the configure utility and for use in BASIC, 'vi' the /etc/termdef, and add the default entries for the terminal. The entries in the termdef file are as follows: Terminal_name:baud_rate:parity:char_length:stop_bits:DTR:CTS: IXOFF:IXON:IXANY:disconnect_on_break:input_translation: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg073 output_translation:slave_printer_attached GPx SOFTWARE ANNOUNCEMENT 11.4 (Cont.) When you run the configure utility there will now be an entry for the new terminal. The next step is to create a tty mnemonics table for the terminal. First 'cd' to the /etc/ttymntbl directory. You can create your own tty mnemonics table or copy a present table to the new terminal name and modify that table. After modifing the table, use the makettymntbl command to compile the table. After this is complete you will now have a tty mnemonics table for the new terminal for use in BASIC. Below is an example of the steps for modifing a tty mnemonics table for a wyse50 terminal. cd /etc/ttymntbl cp 7270.mntbl wyse50.mntbl vi wyse50.mntbl (modify the mnemonics for your terminal) makettymntbl wyse50.mntbl wyse50 After these steps are complete you will be able to configure the terminal using the configure utility and use the terminal in BASIC. Keep in mind that these steps do not guarantee that the customer will have full use of all the functionality of the terminal and/or that all of the mnemonics in BASIC will work with the terminal. 11.5 THIRD PARTY SOFTWARE In the UNX product is a directory called '/usr/tps'. This directory contains sub-directories, such as 2020, WordPerfect and others. In These sub-directories are README files. These files contain information that supplements the installation instructions, but do not replace them, for packages that MBF has installed on the GPx system. NOTE: These products have been installed on the GPx system, but have not been certified by MBF. These instructions are provided as a help for installing the packages. GPx SOFTWARE ANNOUNCEMENT 12.0 DOCUMENTATION This section gives the manuals that are available for the GPx Series 40 system. GPx Series 40 Software Installation and Configuration Manual - M0186A This manual provides information on installing and configuring the BOSS/VX operating system on GPx Series 40 Systems. It is assumed that the system hardware has been installed, and all necessary switch and jumper settings. have been made, as described in the Installation and Maintenance Manual for the system. BOSS/VX System Administrator Guide - M0187A This manual describes the procedures used in the administration of the BOSS/VX operating system running the UNIX Operating System. This manual is SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg074 designed to provide instructions on how to perform the required administrative tasks, provide background information about when and why these tasks are required and serve as a reference guide to administrative procedures. BOSS/VX Reference Manual - M0188A This manual provides a full description of the BOSS/VX Utility Programs and the BOSS/VX Commands that are included in the MBF Environment. BOSS/VX USER GUIDE - M0189A This manual is designed as an overview of the basic features of MBF's BOSS/VX operating system. It includes a general description of the two environments that make up the Dual Universe of the BOSS/VX operating system. Also included is a description of the Business File System, which is shared by both environments. The manual also contains information on how to preform the basic system. functions of the MBF environment, including instructions on the use of selected utilities designed for the file system maintenance, printing, and tape access. BOSS/VX Diagnostics Manual - M0190A This manual describes the diagnostics features developed for the GPx Series 40 systems. The features consist of a system error logging facility and a set of programs to aid in diagnosing system problems to various levels. GPx Series 40 Installation & Maintenance Manual - M8215A This manual supports the installation, startup, and maintenance of assemblies within the GPx 340/440 Central Cabinet Assembly (excluding disk drives). Information on disk drives and system peripherals devices is provided in separate manuals. GPx SOFTWARE ANNOUNCEMENT 12.0 (CONT.) The following manuals have been updated to reflect changes required for the BOSS/VX operating system and GPx Series 40 hardware: PC-Link User Guide - M6340 Intersystem Transport Package User Guide - M6354 Business BASIC 90 Reference Manual - M6262 UNIX System V/386 User Guide - P0001 UNIX System V/386 System Administrator Guide - P0002 UNIX System V/386 System Administrator Reference Manual - P0003 UNIX System V/386 Programmer Guide Volume I - P0004 UNIX System V/386 Programmer Guide Volume II - P0005 UNIX System V/386 Programmer Reference Manual - P0006 GPx SOFTWARE ANNOUNCEMENT 13.0 BUSINESS BASIC 90 AND PORTING GUIDE Business BASIC 90 (BB90) on BOSS/VX has been designed to be compatible with BB90 on both the BOSS/IX and BOSS/VS systems. To the end-user, BB90 will look identical to BB90 on other systems, however, internally the design of BB90 and the structure of Business BASIC filetypes are different from other MBF systems. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg075 This section covers the filetype differences contained in BB90 on BOSS/VX,. and provides a detailed guide to porting Business BASIC applications to the BOSS/VX system. NOTE: The instructions for porting BASIC applications assume a BOSS/IX 7.4B operating system as the source OS. The information for porting from. other OS's may vary slightly depending on the source the porting application. 13.1 BUSINESS BASIC FILETYPES On BOSS/IX, the structure of the inode or file descriptor was modified by MBF to hold Business BASIC specific information, such as the record size, maximum number of records, etc. In addition, Keyed files, such as Direct and Multi-keyed, were composed of two separate and distinct files--a Data file and an invisible Key file. On BOSS/VX, this method of storing information was no longer practical. Modifying the inode to hold specific Business BASIC filetype information would mean the BOSS/VX inode structure would no longer be compatible with the UNIX inode structure (meaning BOSS/VX would not be UNIX compatible). Therefore, on BOSS/VX, specific Business BASIC filetype information is stored within the Business BASIC file as header information. This new header will be present on all Indexed, Serial, Direct, Sort, and Multi-keyed files. In addition, there is no longer two separate files for Direct and Mulit-keyed files. 13.2 PORTING BASIC APPLICATIONS This section describes the steps required to port a BOSS/IX Business BASIC 7.4B compatible application to a BOSS/VX system. Below is an overview of the porting process. Each program change specified in step 1 is explained later in this section. 1. Examine the programs and files and, o Change file names longer than 14 characters to 14 or less characters. o As needed, change hard coded path names. To keep the program source the same between operating systems, the path name can be calculated based upon the operating system. System commands need to be reviewed for compatibility between the BOSS/IX and BOSS/VX operating systems and as needed changed. GPx SOFTWARE ANNOUNCEMENT 13.2 (Cont.) o Access rights need to be changed to the BOSS/VX format. o Check for pre-BOSS/IX Business BASIC 7.4B sensitive code, such as checks for "BB86" in SYS function. Update the programs as needed. o Check for use of terminal names "TA" through "TZ" and change to "T10" to "T35". o Check for use of the FID function and replace it with the appropriate ATTR function. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg076 2. Use BOSS/IX tools to validate the integrity of the files being transported. Corrupted files may not be successfully transported. 3. Transfer the programs and data from the BOSS/IX system to the BOSS/VX system by MCS tape or asynchronous communications. 4. Examine and correct any errors documented in the .errs files on. the BOSS/VX system. 5. Test the product. 13.3 BOSS/IX 7.4B CHANGES REQUIRED TO RUN UNDER BOSS/VX BB90 A. Path names A BOSS/VX disk is divided into several partitions. For efficiency, the root partition (directory /) is kept at a minimum size. Therefore, to prevent premature filling of the root partition, applications should be placed in another partition such as /usr or /usr2. Place all application programs in a directory not being used by MBF. Any directory being used by an MBF product may be changed during use or during an update. A new directory in a non-root. partition can be created for the programs being ported, such as. /usr/asd or /usr2/asd. Any programs containing hard coded path names must be changed if the directory containing the application is changed. The maximum size of a path name, starting from root, on a BOSS/VX system is 1024 bytes, on a BOSS/IX system it is 128 bytes. The following pseudo code establishes if the system being used is a BOSS/VS, BOSS/IX, or BOSS/VX. This information can be used to determine a path name based on the operating system. GPx SOFTWARE ANNOUNCEMENT 13.3 (Cont.) SYSTYPE$ = "BOSSVX" IF ASC("A") <> ASCII("A") THEN SYSTYPE$ = "BOSSVS" ELSE IF LEN(SSN) <= 10 THEN SYSTYPE = "BOSSIX" ENDIF ENDIF The path name can then be setup for the proper system, as shown by the following pseudo code: USEPATH$ = "/usr/bfms13b/" IF SYSTYPE$ = "BOSSVS" THEN USEPATH$ = ".BFMS13B.DATA." ELSE IF SYSTYPE$ = "BOSSIX" THEN USEPATH$ = "/bfms13b/data/" ENDIF ENDIF B. File names SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg077 File and directory names longer than 14 characters, including the extension and excluding the path name, are not supported and must be changed to less than 14 characters. ok: /usr/name/A234567890.234 /usr/name/A234567.901234 /usr/name/A bad: /usr/name/A2345678901.345 C. Access Rights The directive used to create files "CREATE" is unchanged. However the usage rights format specified as a directive attribute has changed. BOSS/IX uses a period (.) to indicate a specific right is not granted (rw. rw.) and the BOSS/VX system uses a dash (-) to indicate the same (rwxrw-rw-). The concept of "group rights" has been added to the BOSS/IX concept of owner and others. Example: The following BASIC commands are used to change the access rights to the file samplefile.dta to owner: read, write, no execute, others: read, write, no execute, and on the BOSS/VX system users in the same group have same access rights. BOSS/IX example: CREATE ATTR="name=samplefile.dta USAGE_RIGHTS=rw. rw." BOSS/VX example: CREATE ATTR="samplefile.dta USAGE_RIGHTS=rw-rw-rw-" GPx SOFTWARE ANNOUNCEMENT 13.3 (Cont.) D. Initial Prefix List Changes On BOSS/IX, BASIC's initial prefix list is the same as the operating system's prefix list. On BOSS/VX only the working directory is used as BASIC's prefix list. This can be setup, however, on BOSS/VX by using the environment variable PFXALT. Example: If the current directory is /usr/bfms13b/data, and the inclusion of /usr/bfms13b/pgms is desired in prefix list, type: PFXALT="/usr/bfms13b/pgms" export PFXALT basic s=300 You will now have a prefix of /usr/bfms13b/data /usr/bfms13b/pgms. E. Support for pre-BOSS/IX Business BASIC 7.4B versions of BASIC Programs checking for the version of Business BASIC must take into account the change in the Business BASIC version number from BB86 to BB90. The method used to determine the version of Business BASIC needs to assume the version number of Business BASIC will continue to change over time. For example change: IF POS("BB86"=SYS) = 1 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg078 THEN .... to IF ( POS("BB86"=SYS) = 1 OR POS("BB9"=SYS) = 1 ) THEN . F. FID Function Rather than using the FID function, use the ATTR function to obtain the information about the file. The FID function may function differently on BOSS/VX, depending on how it is used. G. Error Handling Whenever an error occurs in BASIC, two error values are returned. As with BOSS/IX, the BASIC error value is stored in the system variable ERR. On both, the Operating System error value is stored in TCB(12). The definition of the error code can be displayed on BOSS/VX by using the shell command errno. An example code segment follows: 1000 CMD$ = "errno "+ STR(ABS(TCB(12))) 1010 SYSTEM CMD$ All system errors are stored in the file /usr/mbf/bin/stderror. H. CPL and LST Functions These two functions, which compile and list lines of BASIC code, require the user to know BASIC's table and file layout. Since these tables and layouts changed for BOSS/VX and will continue to. change as BB90 changes, these functions have been replaced by the functions SYNTAX, MAKEPROGRAM, and LISTPROGAM. GPx SOFTWARE ANNOUNCEMENT 13.3 (Cont.) I. LIB Directive The LIB directive has been replaced with the ability to call "C" programs from within BB90. A "C" program is called from within BASIC the same as a BASIC subroutine (CALL "pgm", arg1, arg2, ...). But the "C" program must be designed to be called from BASIC. J. New Functions: MIN, MAX, ATN, COS, EXP, LOG, SIN, SQR and ^ MIN returns the smallest of its arguments: MIN(1,2,3) is 1. MAX returns the largest of its arguments: MAX(1,2,3) is 3. ATN Returns the arctangent (in radians) of its argument: ATN(90) is 1.5596 COS Returns the cosine of its argument: COS(90) is -0.4480 EXP Returns the value of e raised to the specified value: EXP(10) is 22026.4657 LOG Returns the natural log (e) of the specified value: LOG(22026.4645) is 9.9999 SIN Returns the sine of its argument: SIN(90) is 0.89399 SQR returns the square root of its argument: SQR(4) is 2. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg079 ^ The exponentiation operator "^" will now raise a value to a non-integer power. For instance, PRINT X^ (1/3) will print the cube root of X. K. CALL'ed programs dropping into console mode CALL'ed BASIC programs can now drop into console mode where there are "uncaught" errors or the key is pressed (just like run programs). Once in console mode, variables may be examined and printed, but, the CALL'ed program itself may not be modified or saved. L. Edit, List, and Print Abbreviations The abbreviations of ' / and ? are supported for the commands edit, list, and print. M. Easy Edit Typing ' or edit allows the last program or console-mode statements (with or without statement numbers) to be easily edited and re-executed. GPx SOFTWARE ANNOUNCEMENT 13.3 (Cont.) O. Larger Program Size Business BASIC programs may now be larger than 64KB. The program is limited to the area specified by the START size, which may be several million bytes. P. DEVINFO and TSK(0) device ordering BOSS/IX DEVINFO and TSK(0) functions return devices arranged in ascending device number order (e.g., T1, T2, ... T10, T11). BOSS/VX will still group like devices together, as does BOSS/IX, but will not necessarily return the devices sorted in ascending number order. This may be changed in the future. Q. Device Naming BOSS/IX supports the naming convention of TA to TZ or T10 to T35 to mean terminals 10 to 35. BOSS/VX only supports the T10 to T35 naming convention. 13.4 USING ITP FOR TRANSFERRING BETWEEN BOSS/IX AND BOSS/VX A. Cread changes Cread now provides the following options which ease the transport and conversion of programs and data: o automatic file renaming, overwriting, skipping the file, asking the user what to do if the file name already exists in the . directory. o program conversion with output to a file, printer, or terminal while the program is being loaded from the tape. You no longer need to run BQR to convert programs. o files with file names containing special characters, such as SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg080 !*{}[]()#^$, can be always renamed, or left as is. The special characters can be user specified, or a default set of characters used. B. Cread and BQR Program Conversion Syntax Checking Changes When program conversion is performed by either cread or BQR, each. program is checked for the following possible problems: 1) Use of the following functions or directives: CPL, LST, LIB 2) Text strings longer than 14 characters used as file names. 3) Instances of the characters "TA" to "TZ" used as terminal names. 4) Syntax errors, such as error 20's and 26's. Other potential problems, such as HEX codes or use of the FID command are not checked during program conversion. GPx SOFTWARE ANNOUNCEMENT 13.4 (Cont.) C. String File Conversion If tape is being used to transport the information, string files are first converted to Serial files, ported as Serial files by tape, and then converted back into String files on the BOSS/VX system. If asynchronous communications is being used, string files are transferred without any conversion. D. Tape Timings The approximate time required to load and convert data and programs into a BOSS/VX system is shown is the following table. File Type #files # bytes minutes Data 364 21.6Mb 27 Programs 803 4.5Mb 56 The timing was run on a BOSS/VX system with one user running BOSS/VX release 1.0A*09.6. The CREAD options were: no tape retention, program and data conversion enabled, errors logged and continue enabled, all files, and special characters renamed. The data files were from an BOSS/IX system, so no data conversion was required. The program files were from a BOSS/VS system. E. Tape Compatibility Across Systems The following table shows which Intersystem Transport tapes can be read or written on which drives and systems. Writing Reading Drive Tape Drive 45MB 60MB 120MB Required 120Mb rw 600ft 60Mb rw r 450 or 600ft 45Mb rw r r 450 ft r = read w = write 1) BOSS/VX has only 120MB tape drives. BOSS/IX and BOSS/VS uses 45, 60, and 120MB tape drives. GPx SOFTWARE ANNOUNCEMENT SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg081 13.4 (Cont.) F. File Size Changes The figures presented are an estimate of the file size changes which occurred when an application consisting of 803 programs and 384 data file were ported from a BOSS/IX system to a BOSS/VX system. BOSS/VX BOSS/IX %change data 18.89Mb 16.35Mb +15.5 programs 4.7Mb 4.3Mb +8.2 The size of the data files was calculated on both systems by totaling the byte count shown for each file using a ls -l command. The size of the programs was calculated by using the du and diskusage commands. G. Using Asynchronous Communications The features and function of asynchronous file transfer is the same on BOSS/VX as on BOSS/IX. Cabling Direct and modem to modem uses 916073-001 Rev B Available Ports The last two ports (J6 and J7) on each breakout box are available for use with ATP when using modems. This corresponds to ports 6 and 7 on the first breakout box, 14 and 15 on the second, and so on. This port restriction is for ATP only, it does not exist for general modem use. All ports on a breakout box are available for direct connect ATP use. Port Configuration Using the configure utility set the port's parameters as specified below. The default value can be used for any unspecified parameter. Direct Device Type: terminal Terminal Type: 4313 or 4314 Input Baud Rate: 9600 Parity: no parity Character Length: 8 Stop Bits: 1 IXANY flow control: no GPx SOFTWARE ANNOUNCEMENT 13.4 (Cont.) Modem to Modem SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg082 Device Type: modem Modem type: external Input Baud Rate: 2400 Parity: no parity Character Length: 8 Report Carrier Loss: yes Carrier Required: no Stop Bits: 1 IXANY flow control: no Modems ATP uses only a Paradyne FDX 2400 PLUS modem, no other modems, including an internal modem, are currently supported. Modem Configuration The modem is configured the same as for an SPx using ATP modem transfer. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB001 Pg083 FIB 00002 07/13/90 *** BOSS/VX 1.0B Software Announcement - GPx 40 [ WPSS-172 ] *** Level 1.0B of BOSS/VX for the GPx Series 40 is now available. It is the recommended Operating System for the GPx 340 and GPx 440, and is the only Operating System for the GPx 240. The 1.0B Operating System is derived from the 1.0A O.S, and contains new features and enhancements/corrections to the 1.0A Operating System release. This Software Announcement contains general information about the Level 1.0B BOSS/VX Operating System. Installation and update procedures are fully documented in this announcement. Also, this document has sections on enhancements/corrections, new features and new/updated manuals. It is recommended that you read this document before installing Level 1.0B. For information on the GPx 240 hardware see Hardware Announcement 30. For information on ordering 1.0B refer to Marketing Announcement 841 US/C for the United States or 534 I for International. For information on ordering the GPx 240 see Marketing Announcement 840 US/C. WARNING: IF YOU ARE REPLACING THE MOTHER BOARD ON A GPx 440 WITH PART 916556-004 THE SYSTEM MUST BE ON 1.0B OR GREATER OR THE SYSTEM WILL NOT BOOT DUE TO A SECURITY PANIC. TABLE OF CONTENTS 1.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES. . . . . . . . . . . . . . . . . . . . . . 1 1.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM . . . . . . . . . . 1 1.1.1 SYSTEM DISK PARTITIONING. . . . . . . . . . . . . . . . . 4 1.2 UPDATE OF THE OPERATING SYSTEM . . . . . . . . . . . . . . . . . 5 1.3 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD . . . . 8 1.4 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES. . . . . . 9 1.5 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES. . . . . . . . . . .12 1.5.1 PRESENTATION SERVICES . . . . . . . . . . . . . . . . .12 1.5.1.1 PRESENTATION SERVICES CUSTOM MENUS. . . . . . . . . . .12 1.5.1.2 PRESENTATIN SERVICES FORM . . . . . . . . . . . . . . .12 1.5.2 ORIGIN 2.1B*10 GPx INSTALLATION PROCEDURE . . . . . . .13 1.5.2.1 INSTALLATION REQUIREMENTS . . . . . . . . . . . . . . .13 1.5.2.2 NEW INSTALLATION OF ORIGIN 2.1B . . . . . . . . . . . .14 1.5.2.3 UPDATING FROM 2.1A. . . . . . . . . . . . . . . . . . .16 1.5.2.4 UPDATING FROM 2.0A. . . . . . . . . . . . . . . . . . .17 1.5.2.5 UPDATING FROM 1.3B OR 1.3A. . . . . . . . . . . . . . .19 1.5.2.6 EXECUTING ORIGIN ON THE GPx . . . . . . . . . . . . . .20 1.5.3 ORIGIN CONVERSION . . . . . . . . . . . . . . . . . . .20 1.5.3.1 MPx TO GPx CONVERSION . . . . . . . . . . . . . . . . .21 1.5.3.2 SPx TO GPx CONVERSION . . . . . . . . . . . . . . . . .22 1.5.4 ORIGIN 2.1B*10 NEW FEATURES . . . . . . . . . . . . . .22 1.5.5 TRANSLATION . . . . . . . . . . . . . . . . . . . . . .23 1.5.6 DOCUMENTATION . . . . . . . . . . . . . . . . . . . . .25 2.0 CHANGES TO THE 'CONFIGURE' UTILITY. . . . . . . . . . . . . . . . . .26 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg001 3.0 NEW PRODUCTS IN LEVEL 1.0B. . . . . . . . . . . . . . . . . . . . . .26 3.1 27XX/37XX BATCH EMULATION. . . . . . . . . . . . . . . . . . . .26 3.1.1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . .26 3.1.2 SOFTWARE REQUIREMENTS AND INSTALLATION. . . . . . . . . .26 3.1.3 HARDWARE REQUIREMENTS AND INSTALLATION. . . . . . . . . .27 3.1.4 GENERAL INFORMATION . . . . . . . . . . . . . . . . . . .29 4.0 BOSS/VX OPERATING SYSTEM HISTORY. . . . . . . . . . . . . . . . . . .30 .............................................................................. 1.0 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM The following are steps to install or upgrade the BOSS/VX Operating System. Before installing or upgrading the system it is recommended that you read these instructions completely. 1.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all files that exist on your system. It first creates partitions on the fixed disk, makes the file system according to default or user input specifications, and then installs the standard BOSS/VX software (BOSS/VX, Business BASIC, and system utilities) on your system. WARNING: Installation of the Operating System will destroy any installed software on the system. If you are doing an OS installation on a system that already contains customer data, ensure you have a verified back-up of the data. This back-up should not contain any OS files. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record NOTE: During Step 4 you will be required to answer questions pertaining to the system disk partitioning. This information should be decided before the start of the installation, as changing these values will require a re-install of the OS. For information on partitioning see Section 1.1.1. STEP 1: If the system is powered down, power up the system. During the system self-test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the. BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a , if not answer 'n',. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg002 The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. STEP 3: Enter option 'f' to do a full installation. A warning message telling you that a full installation will destroy all files on the system will be displayed. You will. then be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', to exit the installation procedure. STEP 4: System disk information will now be displayed, including the default system disk partitioning, followed by the prompt: Is this allocation acceptable to you (y/n)? If you answer 'y',, to this prompt, the default partition will be used to partition your system disk. If you answer 'n' to this prompt, you will next be prompted with: Do you wish to have separate root and usr filesystems (y/n)? If you answer 'y', to this question your system will contain a root partition and a separate usr partition. Answering 'n',, will put both the root and usr in the same partition. You will next be prompted with the question: Do you want an additional /usr2 filesystem (y/n)? If you answer 'y', to this question a separate usr2 partition will be created on your system disk during the installation. With an 'n',, answer to this question the usr2 partition will not be created. Next, a message will be displayed showing approximately how many bytes a cylinder contains on your disk. You will then be asked: How many cylinders would you like for swap/paging? The minimum size this partition can be is 16Mb. Enter the number of cylinders you wish the swap/paging partition to be , followed by a . You will next be prompted for the size you wish for the rest of the partitions to be created. After you give the size for each partition, you will be again asked if the allocation is acceptable. An answer of 'n',, will take you back to the beginning of this step. STEP 5: After you have answered 'y' to the allocation question, messages will be displayed indicating that the file systems are being made. After the file systems are made, the BOSS/VX software will be installed with the name of the files displayed as they are copied to disk. STEP 6: After the BASE system is installed, the Date and Time are displayed. You will be prompted with: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg003 Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y',, and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. STEP 7: You will next be asked if the Date and Time are correct. If they are correct, answer 'y',; otherwise, answer 'n',, and you will be prompted with the questions to set the Date and Time correctly. STEP 8: You will next be asked to enter the password for the root or super-user. You will be asked for this password twice. Be sure that you remember this password, as it will be required when you wish to login as root. STEP 9: The next step is to install the System's Configuration Record. You will be prompted with: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you wish to install this configuration record? Enter 'y',, to install the configuration record. If you enter 'n',, the configuration record will not be installed and you will be returned to the BOSS/VX SOFTWARE INSTALLATION menu. NOTE: You must install a configuration for your system to boot. If you entered 'n',, in the above step, see Section 1.3 "Installation/Upgrade of the Security Configuration Record" to install the configuration record. STEP 10: After the configuration record is installed the installation of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r',, to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 1.4 "Installation and Update SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg004 of Optional Software Packages" 1.1.1 SYSTEM DISK PARTITIONING The BOSS/VX installation procedure will allow you to define one, two or three partitions containing a file system on the system disk. The swap/paging partition will automatically be on the system disk, but doesn't contain a file system. You will be required in Step 4 of the BOSS/VX installation . procedure to provide information on the number and size of the partitions you wish defined. Before starting an installation, you should have this information. To change this after an OS installation will require backing up the customer's data and doing a complete reinstallation of the OS. The following are different partition options that are available during the installation: 1 partition: root and usr together on the same partition, no usr2 partition. (not recommended) 2 partitions: separate root and usr partition, no usr2 partition. 2 partitions: root/usr partition together and a separate usr2 partition. 3 partitions: separate root, usr and usr2 partitions. During the installation procedure, commands and files required when the system is in single user mode will be installed to the root partition. While in single user mode, the root is the only partition automatically mounted. These commands will allow you to repair or work with one of the other partitions if they are damaged. During the installation procedure, the rest of the standard BOSS/VX software will be installed on the usr partition, if you specified you wanted a separate root and usr partition. Otherwise, the rest of the standard BOSS/VX software will be installed in a directory called '/usr', on the root partition. The OS doesn't put any commands, programs or files automatically into the usr2 partition if it is defined. At the minimum it is recommended that you define your system disk with a separate root and usr partition. In this case if a problem occurs on the usr partition, (the partition where the customer's data is located), the system can be booted into single user mode and the usr partition can be worked with from the root partition. If you wish to put the customer's programs and data files on a separate partition or wish to have a separate partition that can be easily unmounted for security reasons, then the usr2 partition should be defined. Following is the approximate amount of disk space in Mega Bytes by package for the root and usr partitions: Package root usr SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg005 BASE 2.5MB 8.6MB UNIX* .9MB 6.6MB MANPAGES** 3.1MB ITP .9MB PS 3.5MB For ADS, DSS and OTU see Section 1.5.2.1 * UNIX = UNX and UTERM ** MANPAGES = MBFMAN and UMAN NOTE: The amount of disk space required for the above may grow in future releases. 1.2 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the original ones. WARNING: Before attempting any update, it is recommended that you have a verified backup of the customer's data. Ensure that this backup doesn't contain any of the OS files. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record (if you wish to re-install the configuration record) STEP 1: If the system is powered down, power up the system. During the system self-test, put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a . If not, answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. STEP 3: Enter option 'u', to do an update installation. Messages telling you that the file systems are being checked will be displayed. The file systems must not contain errors for the update to continue. Next, messages telling you the BASE system package is being searched for, followed by a message telling you the BOSS/VX software will be installed, are displayed. This is followed by the OS files being installed, with the names of files displayed SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg006 as they are installed. STEP 4: After the OS files have been installed you will be given the option to install the OS files that the user can modify. STEP 5: Next the Date and Time are displayed. You will be prompted with: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change time zones answer 'y',, and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone, you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. STEP 6: You will next be prompted with: Install the configuration record (y/n)? If you don't want to install the configuration enter 'n',. The update is now complete. Remove the BASE system tape and enter 'r', to reboot the system. STEP 7: If you wish to install the configuration record, enter 'y', and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. Do you want to install this configuration record? STEP 8: After the configuration record is installed, the update of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg007 You will now be booting off of your system disk. To install additional packages see Section 1.4 "Installation and Update of Optional Software Packages". 1.3 INSTALLATION/UPDATE OF THE CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration record on a system that doesn't already have one or overwrites the one already on the system. It will display the configuration record. before installing it and give the option to install it or go back to the menu. The following will be required to install the Configuration Record: o BASE Operating System tape o Configuration Record tape STEP 1: If the system is powered down, power up the system. During the system self-test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y', followed by a . If not, answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed STEP 3: Enter option 'i', to install the configuration record. The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the configuration record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record? If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. STEP 4: After the configuration record is installed you will be prompted with: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg008 Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r',, to reboot the system. The installation of the configuration record is now complete. 1.4 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES The following steps outline the procedure to install optional BOSS/VX packages, for example, ITP, MAI OFFICE, TBC, Presentation Services, tools, ORIGIN and other packages supplied in a BOSS/VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified backup of the customer's data files before attempting the update. The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. STEP 1: If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. STEP 2: Shut the system down to single user mode by using the command 'shutdown -i1'. Do you want to continue (y/n)? enter 'y' When prompted for the password use your root password. Enter terminal type (default is TERM=dt4313) TERM= or terminal type. STEP 3: At the command mode prompt enter the command mbfinstall . The following messages will be displayed: WARNING: This program should only be executed in single-user mode press to continue. Installing products on / Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg009 has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. If it is not mounted, type 'mountall' to mount it. STEP 4: Insert the tape containing the package(s) you wish to install in the tape drive and enter . If the BASE system tape is being used for the installation, a message telling you that the tape is an operating system tape, followed by a prompt to continue is displayed. Enter . Messages will be displayed telling you the procedure is skipping to the part of the tape containing the package(s). Next, the MBF Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. STEP 5: Enter the number of the package you wish to install followed by a . You can enter them in any order. The procedure will put them in the order they are found on the tape. After you enter a number you will be prompted with: Install product(s) number Are you sure (y/n)? If you answer 'y',, to this question, the number will be added to the list and you will be returned to the menu. If you answer 'n',, the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, . If you wish to abort the procedure and go back to command mode enter 'ab', . STEP 6: After you have entered the number of all the products you want to install, enter 's',. The procedure will display the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. STEP 7: If a public id is required a message displaying the current public id and its length will be displayed after the package is installed, followed by: ENTER an 8-character new Public ID (Hit <0> for a Null Public ID or for no change): Enter the public id you received with the package if it is different than the one displayed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg010 STEP 8: If you are installing more than one package, the next package will be installed. This will continue until all the packages you selected have been installed. After all the packages are installed, the procedure will take you back to command mode. You are now done with the installation of your package(s). If you wish to install additional package(s) from other tape(s) repeat this procedure to install them. STEP 9: Enter ^d and 2 to return to multi-user mode or ^d and 0 to shut the system down. NOTE: After installing TBC the system must be shutdown using ^d and 0'. The following sections include special instructions or installation procedures when installing the optional software packages. 1.5.1 MAI PRESENTATION SERVICESTM There are no special instructions for installation and customization of Presentation Services. Ensure the users Path includes the following to access Presentation Services: /usr/mbf/PS /usr/mbf/PS/tools 1.5.1.1 PRESENTATION SERVICES CUSTOM MENUS If the user has created their own menus through PS MENUBUILDER for either their own applications or OFFICE and ORIGIN, they need to transfer those files to the GPx Series 40 system using Intersystem Transport. The files to be transferred are as follows: SPx names would be: ../PS/MSMF and ../PS/MSSF-->MENU FILES ../PS/MSH1 and ../PS/MSH2-->HELP FILES MPx names would be: .PS.MSMF and .PS.MSSF .PS.MSH1 and .PS.MSH2 1.5.1.2 PRESENTATION SERVICES FORMS When transferring forms to the GPx system, port only the source form files. Do not port the compiled form file. You will need to recompile your forms once you get them on the destination system. If the user has created their own forms through PS FORMSBUILDER, they need to transfer the following using Intersystem Transport. SPx: /PS/FS1.ENG /PS/FS2.ENG /PS/FS3.ENG /PS/FS4.ENG MPx: .PS.FS1.ENG SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg011 .PS.FS2.ENG .PS.FS3.ENG .PS.FS4.ENG All programs created and associated files must also be transferred. Programs will need to be modified to use only BB90 directives. Bring the files over using cread but do not perform the conversion during porting. Then run BQR to convert the files. After this is done, run MKCONVERT 1.5.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities *********************************************************************** * WARNING * * *. * o PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING * * THIS PRODUCT. * * *. * o Your system should be in single user mode. This ensures a safe * * product installation without conflicts with active systems users.* * *. * o You must be logged on as 'root'. This will avoid security * * conflicts during the product installation. * * *. * o Make a full backup of your product (programs & files) * * before installing this new version. * * *. * o The following Path names used are examples only and will change * * if you install the packages into a directory other than '/usr'. * *********************************************************************** NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 1.5.2.1 INSTALLATION REQUIREMENTS: New installations: o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.0A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: ADS or DSS or (ADS + DSS): 8.16 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB Updating: o The same requirements for a new installation, plus the following: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg012 o You must port all of your current ORIGIN data files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). WARNING: The only way to keep separate directories is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 1.5.1 Presentation Services. ******************************************************************* * *. * Make a full backup of all ORIGIN program and data files, * * currently located at '/usr/origin/r21b and the directories in * * which your *DC0 files are located BEFORE installing this * * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix or directory. * * *. ******************************************************************* NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 1.5.3.1 for MPx and Section 1.5.3.2 for SPx. 1.5.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 1.4. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg013 A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, MB-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appears) SECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY > You may now go to step 6 or quit and shutdown before rebooting system. 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/lanuage directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg014 1.5.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B, the program UPDATE does NOT have to be executed. 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 1.4. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), for (a default will appear) For example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 1.5.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. NOTE: Use the 'chmod' command to change the file usage rights on all files ported to the GPx from another system. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 1.5.2.4 UPDATING FROM 2.0A 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg015 cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 1.4. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT: This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files. E. INSTALL STAND ALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg016 /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 1.5.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14 The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 1.5.2.4, "Installations Updating from 2.0A". 1.5.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic >start 256 >PREFIX "/usr/origin /usr/origin/r21b SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg017 /usr/mbf/PS /usr/mbf/PS/tools" >RUN "ORIGIN" NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. 3. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu _____ Select User Maintenance, use the password "ADMIN". 4. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities. The password is ADMIN. _____ Select ORIGIN System Parameters Maintenance option. _____ Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this directory is "/usr/origin/work/". 1.5.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 1.5.2.5. 2. Perform a verified backup of the ORIGIN system. 3. Using the DIRectory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. For example: .USR.ORIGIN.JKSF01 -> data file .USR.ORIGIN.JKSF02 -> data file .USR.ORIGIN.JKSFM2 -> Application Generated Program .USR.ORIGIN.JKSFM1 -> Application Generated Program .USR.ORIGIN.JKSR01 -> Report Generated SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg018 Program .USR.ORIGIN.JKSR02 -> Report Generated Program .USR.ORIGIN.xxxDC0 -> Technical Documentation File .ORIGIN.R20A.DATA.IDD000 -> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with IDDxxx and reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From command mode, execute MCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 1.5.2.5. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 -> data file /usr/origin/JKSF02 -> data file /usr/origin/JKSFM2 -> Application Generated Program /usr/origin/JKSFM1 -> Application Generated Program /usr/origin/JKSR01 -> Report Generated Program /usr/origin/JKSR02 -> Report Generated Program /usr/origin/xxxDC0 -> Technical Documentation File /origin/r20a/data/IDD000 -> Integrated Data Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg019 be used for each destination. 4. Using cwrite utility, write BQR filelist to tape 5. Restore Intersystem tape on GPx machine using cread utility. Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 1.5.4 ORIGIN 2.1B NEW FEATURES o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re-generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity between the 're- generated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 1.5.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) -and- /pgm/SPA004 - ORIGIN message file in foreign language (*) /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg020 * SPA will be used as the language code in this document. o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. MESSAGE TRANSLATION o Set your prefix to work with ORIGIN 2.1B and perform the following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilities -> -> Password (ADMIN) -> Language Translation Menu -> Languages -> Maintain Languages -> Enter the language code -> -> Done, you may go to console mode at this point. o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file, to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) o Using with system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program directory (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg021 modified from 2.1A to 2.1B, so a re-translation of this . program is recommended: . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until translation is complete. 1.5.6 DOCUMENTATION Manual Number Part Number Pages Title _ M7511E 007511-012A 170 MAI Business DATATM Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATATM Technical Reference M0058C 910058-002 132 MAI ORIGINTM User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGINTM Application Generator User Guide M7512D 007512-002 112 MAI ORIGINTM Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATATM System Support Manual M7557G 007557-011 74 MAI Business DATATM User Guide M7561E 007561-002A 166 Presentation Services Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services Forms Management User Guide 2.0 CHANGES TO THE 'CONFIGURE' UTILITY SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg022 The 'configure' utility has been modified to include communication devices. For details on configuring communication devices see Section 3.1.2 in this Announcement. In addition, the options menu of the 'configure' utility has been modified. Option '1' is now the Save configuration and exit' option. The rest of the options have been moved down by one number. 3.0 NEW PRODUCTS IN LEVEL 1.0B This section contains information on products that are new for Level 1.0B. 3.1 27xx/37xx BATCH EMULATION 3.1.1 INTRODUCTION - The release of 1.0B for the GPx 240,340 and 440 systems includes support for 27xx/37xx Batch Emulation package (TBC). The package is fully tested and supported as on other MBF products using up to 9600 baud synchronous modems. - You may configure up to 4 ports on the GPx 40 for TBC but only 2 communications sessions may be run at the same time from that controller. One cable will support up to 4 synchronous modems. An error -615 will result if an attempt is made to run more than two sessions at the same time. - This package is lock and key protected. 3.1.2 SOFTWARE REQUIREMENTS AND INSTALLATION - Operating System Level Operation System Level 1.0B is the minimum level for support of this package. - Package Installation: The package requires a minimum of 2296 disk blocks on the /usr partition for the program files. The files are in the /usr/mbf/tbc/, /usr/mbf/comm/ ,/usr/mbf/magnet/ and /usr/mbf/etc/ directories. There are approximately 176 disk blocks required for each emulator data directory defined by the user. 1. Installation of this package is done using the 'mbfinstall' utility. 2. The name used to select the installation of this package is 'TBC'. 3. A prompt to enter the software key will be given after the files have been restored. If the key is not entered at that time, the command: 'install_key TBC' can be used to install the key. The key must be entered in upper case. - Port Configuration: The 'configure' utility has been modified to include communication devices. Option '9' is used to configure communication devices. There are 4 ports available per controller (0-3). When you add a SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg023 device, select 'tbc' as the protocol and any I-device group from IA to IZ. NOTE: You must be in Single User mode to install this package and configure the communication devices. After the install you must enter CTRL D and 0 to shutdown the system down and re-boot. 3.1.3. HARDWARE REQUIREMENTS AND INSTALLATION - Although it is not required, it may be necessary to increase system memory to keep system performance at an acceptable level. The determination of this should be based on individual system load parameters. - Board Part number: The part number for the controller is 916593-001. NOTE: This is the same controller that is used on the 1800, but has been modified for use in the GPx 40 Series systems, so it has a different part number. The controllers may not be interchanged. NOTE: There are 4 ports on one controller which are paired and driven by 2 sync chip drivers. This can be useful for troubleshooting purposes. - Cable Part number: The part number for the controller multi-modem cable is 400694-003, the extender cable part number is 907753 with a dash number to indicate length. A connector gender adapter part number 300118-001 is required if the extender cable is used. NOTE: The one multi-modem cable has connections for up to 4 synchronous modems. - Board installation: The Board may be installed in any 16 bit slot available on the GPx CMB. - Switch settings: The following table contains the required controller switch settings: ___________________________________________________________ | JUMPER SETTING | DESCRIPTION | |-----------------------------|---------------------------| | JB1 | Interrupt Request Line 10 | | O O O O O |X| O O | | | 1 O O O O |X| O O | | |-----------------------------|---------------------------| | JB2 | Ports 0-3 connected as DTE| | O O |X| |X| | (For normal operation and | | 1 O |X| |X| | all tests except the Loop| |-----------------------------| test. For the Loop test, | | JB3 | all jumpers MUST be | | |X| O O |X| | removed. All DEMON test | | |1| O O |X| | may run with these | | | jumpers removed. | |-----------------------------|---------------------------| | JB4 | Shared memory starts at | | |X| O |X| O |X| |X| | A0000h | | |X| |X| |X| |X| |X| |X| | | | O |X| O |X| O 1 | | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg024 |-----------------------------|---------------------------| | JB6 JB7 | Shared Memory size 64KB | | O |X| | | | O |X| | | |_____________________________|___________________________| | SW1 | | | | I/O Address of 240H| | 1 2 3 4 5 6 7 8 9 10 | | | OFF ON ON OFF ON ON ON ON OFF OFF | | |____________________________________|____________________| |X| = Jumper installed O = Jumper not installed 3.1.4 GENERAL INFORMATION - Operation 1. The 27xx/37xx Batch Emulation package may be accessed through the Utility menu and selecting the 'communications' option or by setting the user prefix list to '/usr/mbf/tbc' and then running "BCOM" from BASIC. No start size is required. The program "SBCOM" is also supported. 2. The TBC session menu on the GPx family of products has been changed so that option 1 is now called "TRANSMISSION DEFINITION" and not "TERMINAL DEFINITION" . as on previous products. 3. The 'CONTROLLER/PORT' option under 'TRANSMISSION DEFINITION' selection expects numerics from 0 to 3. 4. There are two new entries to the file '/etc/rc2.d/S20sysetup' that performs the necessary operations to load the TBC controller and start the process '/* MAGNET RSM */' for use with TBC. The file is installed with these entries with the installation of the TBC package and is executed during boot. The two new entries are "/usr/mbf/magnet/netinit" (starts the MAGNET RSM process) and "/usr/mbf/comm/commload -b0" (loads the TBC board 0 ). If you are not using TBC, you may want to remove these entries from the '/etc/rc2.d/S20sysetup' file so that errors due to missing hardware and non configured devices will not be displayed during boot. 5. At system load time, a message 'loading /usr/mbf/comm/iccos' will be displayed. 'ICC 186 - rom version 20' will be displayed during the system hardware self tests at load time. 6. The software supports a serial interface autodialer and will require a dedicated terminal port per autodialer. The Ark 2.4K Plus Modem (Paradyne 2400 Plus) and UDS 801 A/C Direct Connect Automatic Calling Unit with RS-232 input are both supported. The UDS A/C is used in conjunction with any 201C/208B compatible modem. The terminal port should be configured as: Device type: terminal Terminal type: other SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg025 There should be no Start process and the baud rate, Parity and character length should match that of the setting for. the modem. the default settings are used for the remaining fields. A serial modem cable is required (P/N 9 16073) for the ACU. 7. A complete system shutdown (power off) and startup should be done after the software and hardware have been installed and configured for the first time. You may see errors during the load process indicating 'error' resetting controller '0' if this is not done. - Diagnostics 1. A synchronous modem eliminator may be used to test the software and controller since there are 4 ports available. 2. DEMON has been updated to include tests for the ICC186 controller. 3. A loopback connector number 905178 is available for DEMON loopback testing. - Related Documentation The manual "M0205A BOSS/VX TRANSPORTABLE BATCH COMMUNICATIONS (27xx/37xx) USER GUIDE" describes the full use of this software package. 4.0 BOSS/VX OPERATING SYSTEM HISTORY 1.0A First release of BOSS/VX. It was required for the GPx 340 and 440. 1.0B This release is required for the GPx 240 and 27xx/37xx Communication . It is also required to use a mother board part number 9217556-004 on a GPx 440, due to the security key being changed. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB002 Pg026 FIB 00003 08/09/90 *** GPx 70 Software Announcement [ WPSS-175 ] *** Introducing the new GPx Series 70 Systems. The GPx Series 70 product line includes the GPx 5070 and GPx 6070 systems. This new product line utilizes the BOSS/VXTM Level 1.0A Operating System, hardware and related software packages. This document contains the information to install and update the GPx Series 70 System, both hardware and software. There are also sections on customizing the system, determining memory requirements, analyzing performance problems, system dump procedures, operating system and utility overviews and other topics related to the operation of the system. It is recommended that before installing a GPx Series 70 system, you first read this document. For information on ordering software, hardware and other related Marketing information please see Marketing Announcements for the United States and International listed below: BOSS/VX 1.0A FOR THE GPx SERIES 70 - INTERNATIONAL 536I DOMESTIC 843 US/C GPx SERIES 70 SYSTEMS - INTERNATIONAL - 535I DOMESTIC - 842 US/C TABLE OF CONTENTS 1.0 PRODUCT OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 BASE PACKAGE OVERVIEW . . . . . . . . . . . . . . . . . . . . . . 2 2.0 SYSTEM STARTUP AND SHUTDOWN. . . . . . . . . . . . . . . . . . . . . . 4 2.1 SYSTEM STARTUP. . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2 SYSTEM SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.3 ALTERNATE LOAD FROM TAPE OR HARD DISK . . . . . . . . . . . . . . 6 3.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES . . . . . . . . . . . . . . . . . . . . 9 3.1 INSTALLATION OF A NEW VTOC AND/OR A NEW MINIROOT (PHASE 0). . . . 9 3.1.1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.1.2 BOOTING THE SSM FIRMWARE . . . . . . . . . . . . . . . . .10 3.1.3 WRITING A NEW VTOC . . . . . . . . . . . . . . . . . . . .11 3.1.4 INSTALLING A NEW MINIROOT. . . . . . . . . . . . . . . . .12 3.1.5 BOOTING ON TO THE MINIROOT . . . . . . . . . . . . . . . .12 3.2 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM . . . . .13 3.2.1 BOOTING TO THE MINIROOT. . . . . . . . . . . . . . . . . .13 3.2.2 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM . . . . . . .14 . 3.2.3 UPDATE OF THE OPERATING SYSTEM . . . . . . . . . . . . . .18 3.2.4 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD .20 . 3.2.5 UPDATE OF THE SSM FIRMWARE . . . . . . . . . . . . . . . .21 3.3 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES (PHASE 2) .22 3.4 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES . . . . . . . . . . .24 3.4.1 MAI PRESENTATION SERVICESTM. . . . . . . . . . . . . . . .24 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg001 3.4.1.1 PRESENTATION SERVICES CUSTOM MENUS. . . . . . . .24 3.4.1.2 PRESENTATION SERVICES FORMS . . . . . . . . . . .25 3.4.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE . . . . . . . . . .26 3.4.2.1 INSTALLATION REQUIREMENTS . . . . . . . . . . . .26 3.4.2.2 NEW INSTALLATIN OF ORIGIN 2.1B. . . . . . . . . .27 3.4.2.3 UPDATING FROM 2.1A. . . . . . . . . . . . . . . .29 3.4.2.4 UPDATING FORM 2.0A. . . . . . . . . . . . . . . .30 3.4.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A. . . . .31 3.4.2.6 EXECUTING ORIGIN ON THE GPx . . . . . . . . . . .32 3.4.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx . . . . . . . . . . . . . . . . . .33 3.4.3.1 MPx TO GPx CONVERSION . . . . . . . . . . . . . .33 3.4.3.2 SPx TO GPx CONVERSION . . . . . . . . . . . . . .34 3.4.4 ORIGIN 2.1B NEW FEATURES . . . . . . . . . . . . . . . . .35 3.4.5 TRANSLATION. . . . . . . . . . . . . . . . . . . . . . . .35 3.4.6 DOCUMENTATION. . . . . . . . . . . . . . . . . . . . . . .38 4.0 HARDWARE INFORMATION. . . . . . . . . . . . . . . . . . . . . . . . . .38 4.1 GPx SERIES 70 HARDWARE MINIMUM AND MAXIMUM CONFIGURATION CHART . .38 4.1.1 GPx 5170 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .39 4.1.2 GPx 5270 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .39 4.1.3 GPx 6170 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .40 4.1.4 GPx 6270 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .41 4.1.5 GPx 6370 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .42 4.1.6 GPx 6370 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .43. 4.1.7 GPx 6370 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART .44 4.2 JUMPERS CONNECTIONS AND SWITCH SETTINGS. . . . . . . . . . . . . .44 4.2.1 MODULAR POWER SYSTEM. . . . . . . . . . . . . . . . . . . .44 4.2.2 DUAL CPU BOARD (DPU) - 903685-002 . . . . . . . . . . . . .47 4.2.3 8/16 MB MEMORY CONTROLLER - 903689-001/002. . . . . . . . .47 4.2.4 8/16 MB MEMORY EXPANSION - 903691-001/002 . . . . . . . . .48 4.2.5 SYSTEM SERVICES MODULE (SSM) - 903683-001 . . . . . . . . .48 4.2.6 INTERNAL MODEM - 400812-001 . . . . . . . . . . . . . . . .49 4.2.7 16-WAY CONTROLLER - 400736-001. . . . . . . . . . . . . . .50 4.2.8 DIFFERENTIAL SCSI ADAPTER - 400814-001. . . . . . . . . . .52 4.2.9 SCSI HARD DISK DRIVES AND TAPE DRIVES . . . . . . . . . . .53 4.3 PCBA LOCATION/PLACEMENT REQUIREMENTS . . . . . . . . . . . . . . .54 4.4 CABLE DIAGRAMS . . . . . . . . . . . . . . . . . . . . . . . . . .55 4.4.1 916484 SERIAL DEVICE TO CCA/BREAK-OUT BOX . . . . . . . . .55 4.4.2 916073 EXTERNAL MODEM TO CCA/BREAK-OUT BOX. . . . . . . . .56 4.4.3 916291 CCA TO PARALLEL PRINTER CABLE. . . . . . . . . . . .56 4.4.4 916428 CCA TO PARALLEL PRINTER CABLE (Data Products). . . .57 4.4.5 RJ45 ADAPTERS . . . . . . . . . . . . . . . . . . . . . . .57 4.5 SUPPORTED PERIPHERALS. . . . . . . . . . . . . . . . . . . . . . .58 5.0 BACKUP AND RESTORE. . . . . . . . . . . . . . . . . . . . . . . . . . .59 5.1 USING dump AND restore FOR BACKUP/RESTORE. . . . . . . . . . . . .60 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg002 5.1.1 FEATURES OF 'dump' AND 'restore'. . . . . . . . . . . . . .60 5.1.2 WHEN TO USE 'dump/restore'. . . . . . . . . . . . . . . . .61 5.2 'dump' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 5.2.1 'dump' OPTIONS (USED WITHOUT PRECEDING "-") . . . . . . . .61 5.2.2 USING dump BACKUPS. . . . . . . . . . . . . . . . . . . . .62 5.2.3 RECOMMENDED dump PROCEDURE. . . . . . . . . . . . . . . . .62 5.3 restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 5.3.1 'restore' OPTIONS . . . . . . . . . . . . . . . . . . . . .63 5.3.2 USING restore TO RESTORE BACKUPS. . . . . . . . . . . . . .64 5.4 dump AND restore EXAMPLES. . . . . . . . . . . . . . . . . . . . .65 5.5 NOTES AND CAUTIONS ON dump/restore . . . . . . . . . . . . . . . .67 6.0 BOSS/VX SYSTEM UTILITIES. . . . . . . . . . . . . . . . . . . . . . .67 6.1 UTILITY PROGRAM OVERVIEW . . . . . . . . . . . . . . . . . . . .67 6.2 OPRINFO UTILITY. . . . . . . . . . . . . . . . . . . . . . . . .69 6.3 CONFIGURE UTILITY. . . . . . . . . . . . . . . . . . . . . . . .71 7.0 BOSS/VX SHELL . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 7.1 DIFFERENCES BETWEEN BOSS/VX AND BOSS IX. . . . . . . . . . . . .77 7.2 COMMANDS AND ARGUMENTS . . . . . . . . . . . . . . . . . . . . .77 7.3 USEFUL BOSS/VX COMMANDS. . . . . . . . . . . . . . . . . . . . .82 7.4 DIFFERENCES BETWEEN GPx 40 AND GPx 70 SHELL. . . . . . . . . . .83 7.5 CONTROL SEQUENCES. . . . . . . . . . . . . . . . . . . . . . . .85 7.6 INPUT/OUTPUT/ERROR REDIRECTION . . . . . . . . . . . . . . . . .85 7.7 BACKGROUND PROCESSING. . . . . . . . . . . . . . . . . . . . . .86 7.8 INPUT BUFFER LIMITATION AND EFFECT ON COMMANDS . . . . . . . . .86 7.9 HUGE DIRECTORIES . . . . . . . . . . . . . . . . . . . . . . . .86 7.10 UNIX TRAINING AND HELP TOOLS . . . . . . . . . . . . . . . . . .86 8.0 OPERATING SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . .87 8.1 MEMORY MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . .87 8.1.1 AREAS OF MEMORY . . . . . . . . . . . . . . . . . . . . .88 8.2 FILESYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . .89 8.3 SYSTEM SECURITY. . . . . . . . . . . . . . . . . . . . . . . . .91 8.3.1 FILE ACCESS PRIVILEGES. . . . . . . . . . . . . . . . . .91 8.3.2 ROOT PRIVILEGE. . . . . . . . . . . . . . . . . . . . . .92 8.3.3 ACCOUNT PASSWORDS . . . . . . . . . . . . . . . . . . . .92 8.3.4 MENU SECURITY CODES . . . . . . . . . . . . . . . . . . .92 8.3.5 SSN . . . . . . . . . . . . . . . . . . . . . . . . . . .93 8.3.6 SOFTWARE KEYS . . . . . . . . . . . . . . . . . . . . . .93 8.3.7 CONFIGURATION RECORDS . . . . . . . . . . . . . . . . . .94 9.0 CUSTOMIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 9.1 OPERATING SYSTEM PARAMETERS CUSTOMIZATION. . . . . . . . . . . .95 9.2 MODIFYING THE BOOT ENVIRONMENT . . . . . . . . . . . . . . . . .96 9.1.1 SSM MONITOR COMMANDS. . . . . . . . . . . . . . . . . . .96 9.1.2 DEFAULT SETTINGS. . . . . . . . . . . . . . . . . . . . .96 9.1.3 SET CONSOLE ATTRIBUTES - LOCAL/REMOTE . . . . . . . . . .97 9.1.4 BOOT THE SSM MONITOR - bs . . . . . . . . . . . . . . . .98 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg003 9.1.5 BOOT THE OPERATING SYSTEM - bh. . . . . . . . . . . . . .99 9.1.6 REQUEST HELP ON POWER-UP COMMANDS - help. . . . . . . . .101 9.1.7 PRINT COMMAND PARAMETERS - print. . . . . . . . . . . . .101 9.1.8 CONTROL THE SYSTEM CONFIGURATION - config/deconfig. . . .102 9.1.9 SHOW THE SYSTEM LOG - log . . . . . . . . . . . . . . . .103 9.1.10 GO TO THE MONITOR FROM THE OPERATING SYSTEM . . . . . . .104 10.0 SYSTEM PERFORMANCE TOOLS . . . . . . . . . . . . . . . . . . . . . . .105 10.1 monitor - MONITOR SYSTEM ACTIVITY. . . . . . . . . . . . . . . .105 10.2 sar - SYSTEM ACTIVITY REPORTED . . . . . . . . . . . . . . . . .106 10.3 timex - TIME EXECUTION . . . . . . . . . . . . . . . . . . . . .107 11.0 SYSTEM CRASH/DUMP. . . . . . . . . . . . . . . . . . . . . . . . . . .107 11.1 CORE DUMP. . . . . . . . . . . . . . . . . . . . . . . . . . . .107 11.2 SYSTEM CRASH (PANIC) . . . . . . . . . . . . . . . . . . . . . .107 12.0 FOR YOUR INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . .114 12.1 UMASK AND BMASK. . . . . . . . . . . . . . . . . . . . . . . . .114 12.2 ADDING ADDITIONAL DISK DRIVES. . . . . . . . . . . . . . . . . .115 12.3 ADDING A NON-MBF TERMINAL TO THE MBF CONFIGURE UTILITY . . . . .118 13.0 DOCUMENTATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 14.0 BUSINESS BASIC 90 AND PORTING GUIDE. . . . . . . . . . . . . . . . . .120 14.1 BUSINESS BASIC FILETYPES . . . . . . . . . . . . . . . . . . . .120 14.2 PORTING BASIC APPLICATIONS . . . . . . . . . . . . . . . . . . .121 14.3 BOSS/VS AND BOSS IX CHANGES REQUIRED FOR BOSS/VX . . . . . . . .122 14.4 USING ITP FOR TRANSFERRING FILES . . . . . . . . . . . . . . . .127 1.0 PRODUCT OVERVIEW The GPx Series 70 systems are an entirely new line of advance technology multi-processor business computer systems introduced by MAI Basic Four (MBF). These new systems are based on the BOSS/VX Dual Universe software platform that combines MBF's BOSS environment with AT&T's UNIX System V which was introduced on the smaller GPx Series 40. The GPx Series 70 are based on industry-standard components, such as 80386 CPUs, VME I/O Bus and SCSI disk and tape drives. The architecture of the GPx Series 70 are based on a new approach to computing called tightly-coupled symmectrical computing. The Operating System for the computer is BOSS/VXTM, a UNIXR* System V.3.2 compatible and Business BASIC compatible operating system. The BOSS/VX operating system is unlike other UNIX-based operating systems, in that it allows a customer to take full advantage of UNIX-based software applications, as well as run MBF proprietary software applications concurrently. Because BOSS/VX\ supports these two types of software application environments concurrently, MAI Basic Four has seized on the uniqueness by. developing the concept of a Dual UniverseTM. The Dual Universe concept alleviates customers from having to choose between a proprietary operating system (one Universe), and the openness of a standard operating system (another Universe). The Dual Universe concept stems from the operating system's ability to execute two different types of applications at the same time. Therefore,. the Dual Universe is composed of one universe for executing UNIX-type SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg004 applications, and another universe for executing MBF proprietary Business BASIC applications. The GPx Series 70 can be customized with three different levels of software to meet the customer's needs: BOSS/VX operating system, MBF Optional Software Packages, and UNIX Optional Software Package, as follows: BOSS/VX Operating System BOSS/VX must be present on all systems. BOSS/VX consists of the system kernel, the MBF environment and the UNIX environment. The MBF environment contains the base set of commands and utilities, Business BASIC 90, and full support for vendor Business BASIC applications. The UNIX Environment provides the complete set of tools, utilities, and other functionality found in standard UNIX V.3.2, including the necessary libraries and kernel extensions to run standard "C" applications. Note, the UNIX Base Environment allows execution, but not the ability to develop "C" applications. MBF Software Packages MBF Software Packages offer specific Business BASIC applications designed by MBF. Each module is independent and can be added at any time. These modules include products such as, MAI OFFICETM and MAI ORIGINTM ADS, ATP and other vertical applications. *UNIX is a Registered Trade Mark of AT&T in USA and other countries GPx SERIES 70 SOFTWARE ANNOUNCEMENT UNIX Optional Software Packages UNIX Optional Software Package consist of separate optional modules. The "C" development module provides the ability to program, compile, and fully develop "C" application programs. Other modules will be made available in the future. 1.1 BASE PACKAGE OVERVIEW This section gives the packages found on the BASE Customer tape and brief overview of what that package contains. Other than the BASE Package the following products can be installed using 'mbfinstall'. For information on the use of this command see Section 3.3 of this document. BASE PACKAGE This contains the BOSS/VX kernel, BASIC (BB90), system and BASIC utilities,UNIX commands and utilities, and Printer Definition Files (PDF). To install this package see section 3.0 of this document. INTL (International Utilities) This contains the programs and files required to modify or change the language of the utility message files. MBFMAN (BOSS/VX Reference Manual) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg005 This contains the programs and files required to use the 'man' command with the BOSS/VX valued added commands. This package is also required to be installed for the 'man' command in UNIX to work. UMAN (UNIX Reference Manual) This contains the files required to use the 'man' command with the UNIX commands. UTERM (UNIX terminfo files) This package contains the AT&T supplied terminfo files. NOTE: MBF terminal terminfo files are provided as part of the Base package. UPDR (PDF Runtime) This package is required if you wish to use PDFs that were created or modified in the field. A public ID or key is required to use this package. UHELP (ASSIST and HELP) This package contains the UNIX self-teach package ASSIST and the online help package. PDF (Printer Driver Files) This package contains the Printer Driver Files and translation files. This would only be required if you wish to update the PDFs and translation files without doing an OS update. SSM (System Services Module Firmware) This package contains the SSM firmware. This would only be required if you wish to update the SSM firmware. SYSADM (System Administration Utilities) This package contains the UNIX System V System Administrator utilities. TOOLS (Operating System Tools) This package includes operating system tools. ITP (Intersystem Tape Transport Utilities with ATP 4.0*13) This package contains the programs and files required to run the Intersystem Transport Package. It also, includes ATP 4.0*13. A public ID or key is only required if you wish to use the ATP auto-scheduler and/or the ATP autodialer features. Without the key, you are able to use the package for transporting your programs and data files between MPx, SPx, 13xx and GPx systems. * PS (Presentation Services Tools) This package contains the programs and files required to use the Form Builders section of Presentation Services. * ADS (Application Development Software) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg006 This package contains the programs and files required to develop ORIGIN Applications. * DSS (Decision Software Support) This package contains the programs and files to use MAI Business DataTM 2.1B (MBF Business DATATM). * OTU (ORIGIN Translation Utilities) This package contains the programs and utilities to translate ORIGIN to a different language. * These packages are not on the international version of the BASE tape and must be ordered separately. 2.0 SYSTEM START-UP AND SHUTDOWN 2.1 SYSTEM START-UP During the GPx 70 booting process 3 levels of firmware are loaded into the SSM and then an operating system is loaded into memory and executed. The first level of firmware is loaded off the SSM. Commands entered at the console and/or settings in the NVRAM . determine from where the next two levels of firmware and an operating system will be loaded. At each step, after the first, the operator will have the option to stop an automatic boot and enter commands. This procedure assumes that NVRAM is set to do an autoboot, with the data coming from the hard disk. For information on doing an . alternate load see Section 2.3 ALTERNATE LOAD FROM TAPE OR HARD DISK. For information on changing the defaults in the NVRAM see Section 9.1 NVRAM CUSTOMIZATION. 1) Locate the console terminal, the terminal connected to Syscon port on the back of the CCA. The console terminal will be used by the system to display messages and receive inputs during the load process. 2) If the system is powered off, power it on by first placing the OFF/ON/SECURE key on the front panel to the ON position. Next, press the POWER ON button on the front panel. If the system has been shutdown, but is still powered up, ensure the ---> is displayed and then type: bh bh = boot host 3) If the system is booting from a powered off state, first the SSM will perform a self test, during this time nothing will be displayed on the console. After the SSM self test a character will be displayed on the console, followed by the loading of the level 1 firmware. After the level 1 firmware is loaded, the system will do a self test. Next the level 2 and 3 firmware will be loaded. After each loading a higher level of self tests are run. After the level 3 firmware is loaded and the self test run or if 'bh' is entered at the '--->' prompt, the operating system will be loaded into memory and executed. The operating system will perform a self test followed by the proprietary message. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg007 Next the system will go into multi-user mode; the console displays a message that the system is coming up, and then the various devices are mounted and the system error logger is started. When the load process is complete the MAI/BASIC FOUR logon screen will be displayed. The system is now started and ready for use. 2.2 SYSTEM SHUTDOWN Following are the steps to properly shutdown the system so that it can be powered down or rebooted. WARNING: To avoid possible damage to your files, ensure you follow this procedure before powering down or rebooting the system. 1) Login as root/super-user on the system's console. Get to command mode, with your working directory set to '/'. 2) Enter the command shutdown . The options for this command are: -y If this is not added, the procedure will prompt you as to if you wish to continue with the shutdown after the grace period. If added, the system will not prompt before completing the shutdown -g -g followed by a number will allow you to specify time in seconds before the system will shutdown or prompt for you to continue with the shutdown if the -y option is not used. If the option is not used, the default is 60 seconds. -i -i followed by an init state will cause the system to go into the state after the shutdown. The default is init 0. The available init states are: 0 = Shut the machine down so it is safe to remove the power. This state can be executed only. from the console. 1 = Put the system in single-user mode. Unmount all file systems except root. All user processes are killed except those connected to the console. This state can be executed only from the console. 2 = Put the system in multi-user mode. All multi-user environment terminal processes and daemons are spawned. This state is commonly referred to as the multi-user state. 3 = Start the remote file sharing processes and daemons. Mount and advertise remote resources. Run level 3 extends multi-user mode and is known as the remote file sharing . state. 4 = This state is available to be defined as an alternative multi-user environment configuration. It is not necessary for system operation and is usually not used. 5 = Stop the UNIX system and go to the firmware SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg008 monitor. 6 = Stop the UNIX system and reboot to the state . defined by the initdefault entry in /etc/inittab. After the command is entered, a message will be displayed to terminals telling users to log off the system. 3) If you have not used the -y option in the command, after the grace-period the following prompt will be displayed: Do you want to continue (y/n)? Before answering this question, check with the other users on the system to ensure they have logged off the system before continuing. If you answer n a message will be displayed to all the terminals telling them that the shutdown has been stopped. Answering y will shutdown the system. Messages will be displayed during the shutdown telling you that the system is coming down, and that system services are being stopped. When the shutdown is complete, the following will be displayed: ---> At this point, the system is completely shutdown, and can be powered down or rebooted. NOTE: To go from multi-user mode to single-user with no time delay, use the following command from the console logged in as 'su': shutdown -i1 -g0 To go from single-user to multi-user enter ^d and enter 2 for run level. 2.3 ALTERNATE LOAD FROM TAPE OR HARD DISK The GPx 70 can be alternately booted from tape or different partitions on disk. This section discusses the steps to do an alternate load from either. It is divided up into two steps. The first step is required to stop the booting process so an alternate load can be performed. The second step gives the commands used to boot from the tape or the hard disk. 1) As mentioned above, the first step in the booting process from a power down state is the loading of the level 1 firmware from the SSM. This step is automatic. After the level 1 firmware is loaded a '->' will be displayed if the system is not set to autoboot. If it is set to autoboot a message will be displayed saying that you have 5 seconds to stop the autoboot of the next level. This message is displayed at all boot levels. To stop the automatic boot enter a . After the boot process is stopped a prompt will be displayed SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg009 telling the operator the level the system is at. The prompts are as follows: -> (level 1) --> (level 2) ---> (level 3) 2) After the boot process is stopped the system can be alternately booted from information entered at the console or from the information in the NVRAM. Booting from level 1 to level 2 At the level 1 firmware the system doesn't recognize partitions, so when booting off of the hard disk a block or sector number must be used. The command to boot from level 1 to level 2 is: bs (options) bs = boot SSM If the system is to be booted from the information in the NVRAM enter bs with no other information. If the system is to be booted from hard disk enter: bs wd(d,s) where wd=hard disk d=disk number (0 for the primary disk) s=sector or block number If the system is to be booted from tape enter: bs tm(48,f) where tm=tape drive 48=the tape drive SCSI number f=the file on tape to boot from (0=first file on tape) Example: to boot from sector 32 on the hard disk enter: bs wd(0,32) Booting from level 2 to level 3 firmware At the level 2 firmware the system recognizes partitions. To boot from the information in the NVRAM enter bs with no options. To boot from hard disk enter: bs wd(d,p)file where wd=hard disk d=disk number (0=primary disk) p=partition number file=file were the information is located To boot from tape enter: bs tm(48,f) where tm=tape 48=SCSI tape device number SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg010 f=file number on tape to boot from (0=first file on tape) Booting from level 3 At this point the system's firmware has been loaded and is now ready for an OS or an executable file. If an OS is going to be booted information on the root partition and swap partition are needed. At this step the root and swap partitions must be on a hard disk. To boot from the information in the NVRAM enter bh with no options. Where bh = boot host. To boot from hard disk enter: bh 'wd(x,p)file -r wdysp -s wdysp' where wd=hard disk x=disk number (SCSI address 0=primary disk 8, 16,...) y=disk number (logical address 0=primary 1, 2,...) p=partition number file=the file to be loaded or booted Following the '-r' and '-s' options are the partition to be used for the root and the partition used for the swapper in that order. Other options are available and will be included in the instructions if you are required to do an alternate load using these other options. To boot from tape enter: bh 3tm(48,f) where tm=tape 48=SCSI tape device number f=file number on tape to boot from (0=first file on tape) 3=load and then execute the file The bh is the last step in the boot process. At this point an OS or executible program will be loaded into memory. WARNING: After doing an alternate load go back and check the NVRAM to make sure it is still set correctly. 3.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES The GPx70 installation process consists of three phases. In the initial phase, phase 0, 'Installation of a New VTOC and/or a New miniroot', the OS boot tape is used to load SSM firmware into the SSM and to boot the SSM from level 1 to level 3 operational firmware. Then, using stand-alone too ls from the boot tape, the user may optionally write a minimal VTOC (volume table of contents) on the primary disk and then copy the miniroot file system from tape to disk. Next, the machine is booted up from level 3 to single user mode OS. In the next phase, phase 1, 'Installation and Update of the BOSS/VX Operating System', a script is executed which allows either full or update installation. After the first two phases, the machine can be booted automatically from level 1 firmware to multi-user mode without the user's intervention. In the last phase, phase 2, 'Installation and Update of Optional Software Packages', another tape is . used to install MBF or vendor products while the system is running on the standard operating system in single user mode. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg011 Phase 0 must be done for the very first installation. Thereafter, phase 0 installation may be required if disk formatting or re-partitioning is necessary. Phases 1 and 2 are performed for each operating system update or application package installation. NOTE: For purposes of this document Phase 0 and 'Installation of a New VTOC and/or a New miniroot' will be interchanged. Likewise, Phase 1 and 'Installation and Update of the BOSS/VX Operating System' and Phase 2 and 'Installation and Update of Optional Software Packages' will be interchanged. NOTE: During the installation/update procedure the system will be booted and programs loaded from tape and/or hard disk. The command 'tm(48,x)' ,(where x=file number on the tape) will be used to boot or load a program from tape. For hard disk access 'wd(0,x)', (where x=block offset) or 'wd0sx', (where x= partition on disk) will be used. 3.1 INSTALLATION OF A NEW VTOC AND/OR A NEW MINIROOT (Phase 0) The following section outlines the steps to install a new VTOC and/or miniroot. If you don't need to install a new VTOC or miniroot go to section 3.2 'Phase 1 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM'. 3.1.1 OVERVIEW Phase 0 should normally be done for the very first installation only. Occasionally a disk hardware problem or the nature of an update to the operating system will require the steps of a phase 0 installation. The steps are described below, grouped into 3 sections by their function: booting the SSM firmware, writing a new minimal vtoc (volume table of contents) and installing a new miniroot. The BASE OS tape is used to boot the SSM firmware into SSM memory. The SSM has three states that it goes through during the boot process. On a new system with the BASE OS tape inserted and the machine powered on, the system will come up in level 1 indicated by a single dash followed by a greater-than symbol (->). The user enters a boot command to bring the system to level 2 indicated by the prompt -->. Then another command is typed in to bring it to level 3 operational firmware, indicated by the prompt '--->'. The OS boot tape has several stand-alone programs that can be used to write a minimal vtoc on it, or to copy the miniroot from tape to its special partition (wd0s8). The final step of phase 0 is to boot the system from the miniroot. Installation then proceeds to phase 1. 3.1.2 BOOTING THE SSM FIRMWARE The following steps are used to bring the system to the operational firmware state to prepare for the subsequent operations possible in phase 0 installation: 1) If the system is already running, shut it down with the shutdown command ('shutdown -i0 -g# -y' where # is the number of seconds to wait). Proceed to step 5. 2) If the system is not running, insert the BASE OS tape SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg012 and power the system on. If the system responds with the '->' prompt, the SSM firmware must be loaded from tape (continue with step 3). If the system responds with the '--->' prompt, proceed to step 5. If the system boots to single or multi user mode, shut it down as in step 1 above. 3) Enter bs tm(48,2) This reads and runs the boot program from tape. This is called level 2 (system prompts -->). 4) Enter bs tm(48,3) This brings the system to the operational firmware level (level 3). The system prompts with '--->'. 5) Enter bh 3tm(48,4) to execute the tape boot program. It responds with the prompt ':'. Once the system is running the tape boot program, the installer may use the standalone tape programs to write a minimal vtoc or install a new miniroot. 3.1.3 WRITING A NEW VTOC If hardware failure or installation instructions require writing of a minimal vtoc, proceed with the following steps. Writing of a minimal vtoc is required when the disk partitioning of the primary disk is unknown or is changing from one release to the next. Writing a minimal vtoc writes a volume table of contents that describes a single partition on the disk. In this case, the partition being described is partition 8 for the miniroot. Writing of the minimal vtoc is handled by a stand-alone program on the BASE OS tape. Perform the following steps: 1) It is assumed that the BASE OS tape is in the tape drive and that the boot program is running (prompt ':'). (If at the ---> prompt, enter 'bh 3tm(48,4)'.) 2) At the ':' prompt of the OS tape boot program, enter tm(48,5) This reads and runs the program from tape that handles writing of a minimal vtoc. 3) This program will prompt for the device on which to write the vtoc. Enter the device name wd(0,0) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg013 Accept the default partition number, location and size. 4) When complete, the program returns to the level 3 '--->' prompt. Enter bh 3tm(48,4) to return to the boot program (':' prompt). After writing a minimal vtoc on the primary disk, the installer must install a new miniroot (next section). 3.1.4 INSTALLING A NEW MINIROOT Occasionally it may be necessary to install a new miniroot filesystem prior to performing a full or partial installation. The following steps may be performed to copy the miniroot from the BASE OS tape to disk. 1) It is assumed that the BASE OS tape is in the tape drive and that the boot program is running (prompt ':'). (If at the ---> prompt, enter 'bh 3tm(48,4)'.) 2) At the ':' prompt enter tm(48,6) This reads and runs the copy program from tape. This program is used to copy the miniroot from the tape to the primary disk. 3) The copy program will prompt for input file. Enter tm(48,10) Copy next prompts for output file. Enter wd(0,8) Enter 'y' at the verify prompt and enter (carriage return) to all of the remaining prompts. When the copy is complete, the system will return to the '--->' prompt. 4) At the '--->' prompt enter bh 3tm(48,4) to return to the boot program. Proceed to the next step of booting the miniroot just installed. 3.1.5 BOOTING ON TO THE MINIROOT The previous steps have installed a new miniroot and re-executed the OS tape boot program. To boot the system onto the new miniroot perform the following command: At the ':' prompt enter wd(0,8)unix -M -r wd0s8 -s wd0s8 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg014 After completion of the installation and booting of the miniroot, proceed to Phase 1, 'Installation and Update of the BOSS/VX Operating System'. 3.2 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM (Phase 1) The following section outlines the steps to install or update the BOSS/VX Operating System. 3.2.1 BOOTING TO THE MINIROOT Phase 1 begins with single user mode rooted on the miniroot file system. If phase 0 installation of a new miniroot has just been. completed, the following steps may be skipped because the system is already booted from the miniroot partition. If this is the case, proceed to Section 3.2.2. If a phase 1 installation is to be performed on a running system, it must first be shut down using the shutdown command 'shutdown -i0 -g# -y'...where # is the number of seconds to wait. When the shutdown is complete, the system will prompt '-- ->'. Since a valid miniroot partition already exists on the disk, it is only necessary to boot it using the following steps. 1) Insert the BASE OS tape into the tape drive. 2) At the operational firmware prompt ('--->'), enter bh 3tm(48,4) to execute the OS boot program. It responds with the prompt ':'. 3) Enter wd(0,8)unix -M -r wd0s8 -s wd0s8 This will boot the system to single user mode on the miniroot partition. At the root directory of the miniroot partition the user (in single user mode) invokes the installation script by typing ./INSTALL The copyright and then the BOSS/VX SOFTWARE INSTALLATION menu screen will be displayed. NOTE: If the system contains a valid miniroot the system can be booted to it by using the command bh 'wd(0,8) UNIX -M -r wd0s8 -s wd0s8' from the '--->' prompt. 3.2.2 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all the files on the 'root' and 'usr' SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg015 filesystems. It makes a new vtoc for the disk, makes the filesystem for the 'root' and 'usr' partitions and installs the standard BOSS/VX software (BOSS/VX, Business BASIC and system utilities) on the disk. WARNING: A full installation completely destroys the contents of the root and usr partitions. Other partitions may not be affected, but they must be backed up as a precaution. Other partitions will definitely be destroyed if the disk partitioning changes as a result of the installation. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record tape for the target system Do the following steps to Install the BOSS/VX Operating System. 1) It is assumed that the BASE OS tape is in the tape drive and the system is booted on the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed. If the system is not booted off the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed go to Section 3.2.1 first to get to this point. 2) From the BOSS/VX SOFTWARE INSTALLATION menu enter option 'f' for Full Install. 3) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 4) A warning message is displayed telling you that a full installation will destroy all files on the primary disk will be displayed. You will be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', to exit the installation procedure. 5) After a message is displayed saying Extracting data, a table will now be displayed giving present system disk partitioning information. This information will be used to update the system disk's vtoc (volume table of contents) and contains the following information: Partition number, partition label (name), size in MBs, mount point (directory to mount the partition to if its to be mounted automatically at boot), auto mount flag (this tells the system if the partition should be mounted at boot time or not), and swap (this tells the system if . this is a swap partition or not). At the bottom of the table is the prompt: Enter selection (0-11, h=help, i=install) to modify: If you wish to use the disk partitioning information in the table to set up the system disk enter i and proceed to step 6. If you wish to modify the disk partitioning information enter the partition number you wish to modify. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg016 NOTE: Partitions 8,12,13,14 and 15 are reserved for the OS and cannot be modified. After entering a partition number to modify you will be given the following options: Label - This will allow you to label (name) the partition. This field can be 1 to 6 characters long. Size - This will allow you to give the size for the partition. This option is used to increase or decrease the size of a partition. The size can changed in increments of 1 megabyte. NOTE: A partition's size cannot be increased if there is no available disk, so decrease other partitions before increasing any. Mount point - The mount point is the directory the partition will be mounted to. The root and usr mount points cannot be changed. An entry of a . (period) remove a mount point. If a partition is not automounted, it doesn't HAVE to have a mount point. Automount - If this option is set to yes, the partition will be mounted at boot time. A yes for this option requires a mount point. A partition cannot have swap and automount both set to yes. Swap - If a partition is to be used as swap when the system is in multi-user mode, set swap to yes. If it is not to be used as a swap partition then set swap to no. redisPlay screen - As updates are made to the table the information in the table will not be displayed until you are done with that partition update or this option is used. Help - The help messages will be displayed. Remove - Removes a partition from the disk. The root, swap, usr, firmware, vtoc, boot, and miniroot partitions cannot be removed. Done - Indicates that changes to this partition are complete. Final verification for this partition takes place. The screen and main menu is displayed. This partition can be selected again for editing. Enter the capital letter in each option to select that option. When you are done with the update of the system disk partitioning, enter i to install this information into the system disk's vtoc. 6) Messages will now be displayed indicating that the file systems are being made and mounted. After the filesystems are made, the BOSS/VX software will be copied from tape to disk. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg017 7) After the BOSS/VX software is copied to disk messages will be displayed telling you that the SSM firmware is being copied to disk, that the /dev devices are being made and that /etc/versionlog is being created, followed by a message giving the current system name. You will be prompted with: prompted with: Do you wish to change it (y/n)? If you wish to change the name enter 'y', and you will be allowed to enter a 8 character name. If you don't wish to change it enter 'n', . 8) The Date and Time are displayed. You will be prompted with: Would you like to set date and time (y/n)? To set date, time and timezone enter 'y', , and the following will be displayed: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y', , and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n', . If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. Next the current date and time are displayed followed with the prompt: Change the date and time (y/n)? If they are correct, answer 'n', ; otherwise, answer 'y', , and you will be prompted with the questions to set the Date and Time correctly. After the date and time are changed you will be prompted with: Date and time will be set to: MM/DD/YY HH:MM (y/n)? If the date and time is correct enter 'y', . If you need to go back and change the date or time enter 'n', . 9) You will next be prompted with: Please remove the release tape and insert the tape containing the configuration record. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg018 Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? Enter 'y', , to install the configuration record. If you enter 'n', , the configuration record will not be installed. NOTE: You must install a configuration for your system to boot. If you entered 'n', , in the above step, see Section 3.2.4, "Installation/Upgrade of the Security Configuration Record" to install the configuration record. 10) After the configuration record is installed the installation of the BASE system is complete. You will be prompted with: Remove the configuration record tape from the tape drive and enter 'r', , to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 3.3, "Installation and Update of Optional Software Packages" 3.2.3 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the original ones. WARNING: Before attempting any update, it is recommended you have a verified backup of the customer's data. Ensure that this backup doesn't contain any of the OS files. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record for the target system (if you wish to re-install the configuration record) 1) It is assumed that the BASE OS tape is in the tape drive and the system is booted on the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed. If the system is not booted off the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed go to Section 3.2.1 first to get to this point. 2) Enter option 'u', for Update Install. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg019 Messages telling you that the file systems are being checked and mounted will be displayed. The primary disk must contain a valid BOSS/VX filesystem for the update to continue. 3) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 4) A list of files that will not be updated will be displayed with the prompt: Would you like to change the list (y/n)? Enter 'n', if this list is correct. If you wish to modify the list enter 'y', and you will be prompted to add or delete files from the list. 5) The BOSS/VX software will be copied from tape to disk. After which the files that were marked not to be changed will be copied back to their proper place from the gap partition. 6) After the BOSS/VX software is installed you will be prompted with: Would you like to re-install dct (y/n)? If the system's configuration has changed and the DCT file needs to be changed updated with the correct DCT file or you want to put down a default DCT file enter 'y', . Otherwise, enter 'n', . 7) You will next be prompted with: Install the configuration record (y/n)? If you don't wish to install the configuration record, enter 'n', and you will be done with the O.S. update. If the system's configuration has changed so that it requires a new configuration record or you want to re-install the old configuration record, enter 'y', and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? If you enter 'y', , the configuration record will be installed. If you answer 'n', , the configuration record will not be installed. 8) After the configuration record is installed, the update of SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg020 the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 3.3 "Installation and Update of Optional Software Packages". 3.2.4 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration record on a system that doesn't already have one or overwrites the one already on the system. This procedure is used to install a configuration record on a new system if that step was skipped on the OS Installation, put down a new configuration record if hardware changes require a new configuration record or over-write using the same configuration record if the configuration record on disk is corrupt. It will display the configuration record before installing it and give the option to install it or go back to the menu. The following will be required to install the Configuration Record: o BASE Operating System Tape (optional if booting off disk) o Configuration Record tape for the target system 1) It is assumed that the system is booted on the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed. If the system is not booted off the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed go to Section 3.2.1 first to get to this point. 2) Enter option 'i', for Configuration Record install. The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Put the tape containing the System's Configuration Record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? If you enter 'y', , the configuration record will be installed. If you answer 'n', , the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. 3) After the configuration record is installed you will be prompted with: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg021 Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r', , to reboot the system. The installation of the configuration record is now complete. 3.2.5 UPDATE OF THE SSM FIRMWARE The following steps outline the procedure to update the SSM firmware on disk. This procedure overwrites the SSM firmware already on the disk. This procedure would be required if on an OS Installation the steps to install the SSM firmware were skipped, new firmware was released and needed to be installed on the disk, or the SSM firmware on disk became corrupt. The following will be required to update the SSM firmware: o BASE Operating System Tape 1) It is assumed that the BASE OS tape is in the tape drive and the system is booted on the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed. If the system is not booted off the miniroot with the BOSS/VX SOFTWARE INSTALLATION menu displayed go to Section 3.2.1 first to get to this point. 2) Enter option 's', for SSM firmware install. 3) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 4) The SSM Firmware will now be copied to disk. 5) After the SSM Firmware is copied to disk you will be prompte with: Press to main menu, or "r" to reboot the system. Remove the BASE OS tape from the tape drive and enter 'r', , to reboot the system. The installation of the SSM Firmware is now complete. 3.3 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES (Phase 2) The following steps outline the procedure to install optional BOSS/VX packages, for example, ITP, MAI OFFICE, Presentation Services, tools, ORIGIN and other packages supplied in a BOSS/VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified back-up of the customer's data files before attempting the update. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg022 The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 1) If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. 2) Shut the system down to single user mode by using the command 'shutdown -i1 -gx' (where x= the number of seconds to wait). After the number seconds you gave the command has passed you will be prompted with: Do you want to continue (y/n)? enter 'y' Next you will be prompted with: Enter terminal type (default is TERM=dt4313) TERM= Enter your terminal type or . 3) At the command mode prompt enter the command mbfinstall . The following messages will be displayed: Installing products on / Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. 4) Insert the tape containing the package(s) you wish to install in the tape drive and enter . If the BASE system tape is being used for the installation, a message telling you that the tape is an operating system tape, followed by a prompt to continue is displayed. Enter . Messages will be displayed telling you the procedure is skipping to the part of the tape containing the package(s). Next, the MBF Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. 5) Enter the number of the package(s) you wish to install followed by a. . You can enter them in any order. If entering more than one package on a line follow each entry with a comma. The procedure will put them in the order they are found on the tape. After you SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg023 enter a number you will be prompted with: Install Product(s) # Are you sure (y/n)? If you answer 'y', , to this question, the number will be added to the list and you will be returned to the menu. If you answer 'n', , the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . The installation of the packages will begin after you enter , you will not have to enter 'S'. If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, . If you wish to abort the procedure and go back to command mode enter ab . 6) After you have entered the number of all the products you want to install, enter 's', . The procedure will display the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. 3.4.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities ******************************************************************. * WARNING * * *. * o PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING * * THIS PRODUCT. * * *. * o Your system should be in single user mode. This ensures a * * safe product installation without conflicts with active * * systems users. *. * *. * o You must be logged on as 'root'. This will avoid security * * conflicts during the product installation. * * *. * o Make a full backup of your product (programs & files) * * before installing this new version. * * *. * o The following Path names used are examples only and will * * change if you install the packages into a directory other * * than '/usr'. * ****************************************************************** NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 3.4.2.1 INSTALLATION REQUIREMENTS: New installations: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg024 o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.0A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: ADS or DSS or (ADS + DSS): 8.16 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB Updating: o The same requirements for a new installation, plus the following: o You must port all of your current ORIGIN data files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). WARNING: The only way to keep separate directories is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004 ' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 3.4.1 (Presentation Services) ******************************************************************* * *. * Make a full backup of all ORIGIN program and data files, * * currently located at '/usr/origin/r21b and the directories in * * which your *DC0 files are located BEFORE installing this * * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix or directory. * * *. ******************************************************************* NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 3.4.3.1 for MPx and Section 3.4.3.2 for SPx. 3.4.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 3.3. 2. Set your PREFIX to /usr/origin/r21b. From command mode: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg025 cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 3.3. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR .ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appea rsECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY> You may now go to step 6 or quit and shutdown before rebooting system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg026 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 3.4.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B, the program UPDATE does NOT have to be executed. 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 3.3. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 3.3. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), for (a default will appear) For example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 3.4.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 3.4.2.4 UPDATING FROM 2.0A SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg027 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 3.3. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 3.3. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT : This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files. E. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg028 /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 3.4.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14 The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. . 2. Turn to Section 3.4.2.3, "Installations Updating from 2.0A". 3.4.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic >start 256 >PREFIX "/usr/origin /usr/origin/r21b /usr/mbf/PS /usr/mbf/PS/tools" >run "ORIGIN" SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg029 NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. 3. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. _____ Select User Maintenance, use the password "ADMIN". 4. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities. The password is ADMIN. _____ Select ORIGIN System Parameters Maintenance option. _____ Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this irectory is "/usr/origin/work/". 3.4.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 3.4.3.1 MPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 3.4.2.4. 2. Perform a verified backup of the ORIGIN system. 3. Using the DIRectory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. For example: .USR.ORIGIN.JKSF01 ---> data file .USR.ORIGIN.JKSF02 ---> data file .USR.ORIGIN.JKSFM2 ---> Application Generated Program .USR.ORIGIN.JKSFM1 ---> Application Generated Program .USR.ORIGIN.JKSR01 ---> Report Generated Program .USR.ORIGIN.JKSR02 ---> Report Generated Program .USR.ORIGIN.xxxDC0 ---> Technical Documentation File .ORIGIN.R20A.DATA.IDD000 ---> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with IDDxxx and SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg030 reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From command mode, execute MCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 3.4.3.2 SPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 3.4.2.4. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 ---> data file /usr/origin/JKSF02 ---> data file /usr/origin/JKSFM2 ---> Application Generated Program /usr/origin/JKSFM1 ---> Application Generated Program /usr/origin/JKSR01 ---> Report Generated Program /usr/origin/JKSR02 ---> Report Generated Program /usr/origin/xxxDC0 ---> Technical Documentation File /origin/r20a/data/IDD000 ---> Integrated Data Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Using cwrite utility, write BQR filelist to tape. 5. Restore Intersystem tape on GPx machine using cread utility. Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem. Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 3.4.4 ORIGIN 2.1B NEW FEATURES SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg031 o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re-generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity between the 're-generated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 3.4.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) -and- /pgm/SPA004 - ORIGIN message file in foreign language (*). /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language * SPA will be used as the language code in this document. o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. MESSAGE TRANSLATION o Set your prefix to work with ORIGIN 2.1B and perform the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg032 following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilities -> . -> Password (ADMIN) -> Language Translation Menu -> Langua'e -> Maintain Language -> Enter the language code -> -> Done, you may go to console mode at this point. o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) o Using with the system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program directory (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily modified from 2.1A to 2.1B, so a re-translation of this program is recommended: . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg033 WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until translation is complete. 3.4.6 DOCUMENTATION Manual Number Part Number Pages Title M7511E 007511-012A 170 MAI Business DATATM Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATATM Technical Reference M0058C 910058-002 132 MAI ORIGINTM User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGINTM Application Generator User Guide M7512D 007512-002 112 MAI ORIGINTM Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATATM System Support Manual M7557G 007557-011 74 MAI Business DATATM User Guide M7561E 007561-002A 166 Presentation Services Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services Forms Management User Guide 4.0 HARDWARE INFORMATION 4.1 GPx SERIES 70 HARDWARE MINIMUM AND MAXIMUM CONFIGURATION CHART The GPx 70 is comprised of two systems - GPx 5070 and GPx 6070. The difference between the two systems is the chassis size and maximum configuration limits. The GPx 5070 uses a 17" wide chassis with six System slots and 12 I/O slots, whereas the GPx 6070 has a 24" wide chassis with 14 System slots and 16 I/O slots. The GPx 5070 systems have a maximum of two Dual Processing Units (DPUs - each containing two 80386 CPUs) and are designed for medium-sized businesses and mid-range network servers with support up to 192 users. The GPx 6070 systems have a maximum of five DPUs and are designed for medium-to-large sized businesses and large network server uses with support up to 256 users. The following are the Minimum and Maximum Configuration Charts for the different GPx 70 systems models. 4.1.1 GPx 5170 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg034 ______________________________Minimum________Maximum____ System Services Module 1 1 Dual Processing Unit 1 (2 x 80386) 1 (2 x 80386) Memory Capacity 8MB 32MB Memory Boards* 1 4 Memory Controller Board 1 2 Memory Expansion Board 0 2 Disk Capacity 355MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 355MB 355MB, 670MB Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 128 Direct-connect Serial Ports 16 128 Parallel Printers 0 1 VME I/O Controllers 1 12 16-port SDC 1 8 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct-connect serial devices may be less than 128 depending on number and type of I/O controllers installed. 4.1.2 GPx 5270 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART ________________________Minimum________Maximum__ System Services Module 1 1 Dual Processing Unit 2 (2 x 80386) 2 (2 x 80386) Memory Capacity 16MB 48MB Memory Boards* 1 3 Memory Controller Board 1 2 Memory Expansion Board 0 1 Disk Capacity 670MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 670MB 355MB,670MB Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 192 Direct-connect Serial Ports 32 192 Parallel Printers 0 1 VME I/O Controllers 2 12 16-port SDC 2 12 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg035 slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct- connect serial devices may be less than 192 depending on number and type of I/O controllers installed. 4.1.3 GPx 6170 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART _______________________________Minimum________Maximum__ System Services Module 1 1 Dual Processing Unit 1 (2 x 80386) 1 (2 x 80386) Memory Capacity 16MB 32MB Memory Boards* 1 4 Memory Controller Board 1 2 Memory Expansion Board 0 2 Disk Capacity 670MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 670MB 355MB,670MB Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 128 Direct-connect Serial Ports 16 128 Parallel Printers 0 1 VME I/O Controllers 1 16 16-port SDC 1 16 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct-connect serial devices may be less than 128 depending on number and type of I/O controllers installed. 4.1.4 GPx 6270 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART _______________________________Minimum________Maximum___ System Services Module 1 1 Dual Processing Unit 2 (2 x 80386) 2 (2 x 80386) Memory Capacity 16MB 48MB Memory Boards* 1 6 Memory Controller Board 1 3 Memory Expansion Board 0 3 Disk Capacity 670MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 670MB 355MB,670MB Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 256 Direct-connect Serial Ports 32 256 Parallel Printers 0 1 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg036 VME I/O Controllers 2 16 16-port SDC 2 16 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct-connect serial devices may be less than 256 depending on number and type of I/O controllers installed. 4.1.5 GPx 6370 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART _______________________________Minimum________Maximum__ System Services Module 1 1 Dual Processing Unit 3 (2 x 80386) 3 (2 x 80386) Memory Capacity 32MB 64MB Memory Boards* 2 8 Memory Controller Board 1 4 Memory Expansion Board 1 4 Disk Capacity 670MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 670MB 355MB,670MB Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 256 Direct-connect Serial Ports 48 256 Parallel Printers 0 1 VME I/O Controllers 3 16 16-port SDC 3 16 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct-connect serial devices may be less than 256 depending on number and type of I/O controllers installed. 4.1.6 GPx 6470 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART _______________________________Minimum________Maximum__ System Services Module 1 1 Dual Processing Unit 4 (2 x 80386) 4 (2 x 80386) Memory Capacity 32MB 80MB Memory Boards* 2 9 Memory Controller Board 1 5 Memory Expansion Board 1 4 Disk Capacity 670MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 670MB 355MB,670MB SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg037 Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 256 Direct-connect Serial Ports 48 256 Parallel Printers 0 1 VME I/O Controllers 3 16 16-port SDC 3 16 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct-connect serial devices may be less than 256 depending on number and type of I/O controllers installed. 4.1.7 GPx 6570 MINIMUM AND MAXIMUM HARDWARE CONFIGURATION CHART _______________________________Minimum________Maximum__ System Services Module 1 1 Dual Processing Unit 5 (2 x 80386) 5 (2 x 80386) Memory Capacity 32MB 96MB Memory Boards* 2 8 Memory Controller Board 1 4 Memory Expansion Board 1 4 Disk Capacity 670MB 3.4GB Hard Disk Drives 1 5 Disk Drive Types 670MB 355MB,670MB Tape Drives 1 2 Tape Drive Types 1/4" 120MB MCS 1/4" 120MB MCS 1/2" 240MB GCR Serial Devices** 1 256 Direct-connect Serial Ports 48 256 Parallel Printers 0 1 VME I/O Controllers 3 16 16-port SDC 3 16 * Memory boards available in 8MB or 16MB increments. All memory boards must be 16MB to achieve maximum memory configuration. ** Total connected serial devices, not including slave printers. A slave printer and its companion terminal count as one serial device. Due to I/O slot limitations, maximum number of direct-connect serial devices may be less than 256 depending on number and type of I/O controllers installed. 4.2 JUMPERS CONNECTIONS AND SWITCH SETTINGS This section gives the jumper connections, switch settings LEDs for the GPx Series 70 systems. 4.2.1 MODULAR POWER SYSTEM SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg038 Power Distribution Unit (PDU) - 903754-001 SWITCHES: Circuit breaker, CB1, controls the AC input power to the PDU. On 110 volt systems CB1 will be a single switch, on 220 volt . systems CB1 will be a dual switch. NOTE the WARNING below. LEDS: DS1, an AMBER LED, when ON indicates that there is voltage present on the 300 volt DC bus (power supply backplane). WARNING: When the circuit breaker is turned OFF DS1 will remain ON until the voltage on the 300 volt DC bus has been dissipated. DO NOT ATTEMPT TO REMOVE OR INSTALL A POWER SUPPLY MODULE WHILE DS1 IS ON. CONNECTORS: J1: at the top of the PDU is an AC "output", it makes available 110 or 220 VAC after passing thru the PDU's circuit breaker, line filter and transient voltage suppressor. Reserved for future use. J2: along the edge of the PDU is an interface for an Uninterruptable Power Supply (UPS). This connector provides warning signals to an UPS indicating when power is or is not needed. TB1: a barrier strip, is accessible by removing the PDU from the power supply cardcage. TB1 has four terminals. Two terminals connect to the AC input line and the remaining two terminals connect to the 300 Volt DC Bus. These last two terminals may be connected to a DC output UPS. Control Module - 903750-001 The Control Module has seven LEDs, one 4-position dipswitch, six test points and three "trim-pots". LEDS: DS1: An AMBER LED, is the second LED from the top when looking at the edge of the card. When ON, this LED indicates that the Auxiliary voltages (+12 volts) are being margined (either HI or LO). DS2: An AMBER LED, is the top most LED when looking at the edge of the card. When ON, this LED indicates that the +5 VDC is being margined (either HI or LO). DS3: A GREEN LED, is the bottom most (very bottom of the PCBA) LED when looking at the edge of the card. This LED should be ON whenever a Power Fail Detect (PFD) condition does NOT exist. DS4: A RED LED, is the top LED in group of four red LEDs near the bottom of the board (when looking at the edge of the . card). When ON, this LED indicates that the +5 VDC is "Out of Tolerance": greater then +5.25 V or less then SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg039 +4.75 V. NOTE: DS4 may be ON when margining the +5 VDC. DS5: A RED LED, is the second from the top LED of the red LEDs near the bottom on the board. When ON, this LED indicates that the +12 VDC is "Out of Tolerance", greater then +12.70 V or less then +11.25 V. NOTE: DS5 may be ON when margining the +12 VDC. 5 Volts at TP5 = 50% of maximum current capability | | 10 Volts at TP5 = 100% of maximum current capability TP6: percent of auxiliary current capability. This test point is functionally the same as TP5 except that it (TP6) represents the summed +12 VDC currents. TP7: is ground ADJUSTMENTS: R30: Adjusts the output of the +5 Volt converters (+5%) R70: Adjusts the output of the Auxiliary converters (+5%). NOTE: that the -12 VDC is slaved to the +12 VDC and adjustments to the +12 VDC will also change the -12 V. R160: THIS IS A FACTORY ADJUSTMENT ONLY. +5 VDC Converter Module - 903744-001 There are no switches or jumpers on the converter modules. There is a single RED LED which will be turned ON if the module's own monitor circuit detects a malfunction. Auxiliary ( +12 VDC) Converter Module - 903748-001 There are no switches or jumpers on the converter modules. There is a single RED LED which will be turned ON if the module's own monitor circuit detects a malfunction. 4.2.2 DUAL CPU BOARD (DPU) - 903685-002 There are no switches or changeable jumpers on the DPU. There are two LEDs on the DPU. LEDS: Two GREEN LEDs can be seen from the front edge of the DPU, one near the top (D1) and one near the bottom (D2). Each LED indicates processor activity for its respective processor. 4.2.3 8/16 MB MEMORY CONTROLLER - 903689-001/002 There are no switches or jumpers on the Memory Controller board. There is one LED and three connectors on this assembly. The physical space in main memory occupied by the Memory Controller is assigned during the boot process. LEDS: D1: a GREEN LED, mounted just below the center connector/header SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg040 indicates while ON that memory on the respective memory controller (or expansion memory) is being accessed. CONNECTORS: There are three connectors along the edge of the Memory Controller. These interconnect via ribbon cables to corresponding connectors on the Memory Expansion board providing an interface for the memory address, data and signals. 4.2.4 8/16 MB MEMORY EXPANSION - 903691-001/002 There are no switches or jumpers on the Memory Expansion board. There are three connector on this assembly. The physical space in main memory is assigned during the boot process. CONNECTORS: There are three connectors along the edge of the Memory Expansion board. These interconnect via ribbon cables to corresponding connectors on the Memory Controller board providing an interface for the memory address, data and signals. 4.2.5 SYSTEM SERVICES MODULE (SSM) - 903683-001 There are no switches on the SSM. There are five LEDs, and numerous jumpers on the SSM. LEDS: The "LEDS" are actually one 5-segment GREEN LED display where each segment is treated as an individual LED. DS1: is the top most LED. This LED is the most significant (Code Bit 3) of four bits used to display self-test error codes. DS2: is Code Bit 2, used to display self-test error codes. DS3: is Code Bit 1, used to display self-test error codes. DS4: is Code Bit 0, used to display self-test error codes. DS5: is the bottom most LED and is the RUN LIGHT, turned on when the SSM passes all test and goes "on-line". JUMPERS: The jumpers on the SSM have the following functions: NOTE: There are NO jumpers designated as J1 or J2. J3: is used in conjunction with other jumpers to indicate to. the firmware to loop on selected test group. Jumper should NOT be installed. J4: Selects Level 0 and Level 1 tests. Jumper should NOT be installed. J5: Selects Level 2 tests. Jumper should NOT be installed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg041 J6: When installed, tells the SSM to ignore commands from OS to change console communication parameters. Jumper should be INSTALLED. J7: Indicates to the firmware that it should erase ("scrub") the non-volatile RAM. Jumper should NOT be installed. J8: is bit 2 of the SCSI ID Jumper should be INSTALLED (for SCSI ID = 7) J9: is bit 1 of the SCSI ID Jumper should be INSTALLED (for SCSI ID = 7) J10: is bit 0 of the SCSI ID Jumper should be installed (for SCSI ID = 7) J11: is actually a trigger for a scope or logic analyzer. A trigger is issued when a test is first entered and there after only when an error occurs. J12: is used by manufacturing to disable the on-board battery. Jumper should be INSTALLED. Jumpers designed as E1, E2, E3, E4, E8, E9 and E10 are used to configure the SSM's RAM. Jumpers are set as follows: E1 to E2; INSTALLED E3 to E4; INSTALLED E8 to E10; INSTALLED Jumpers designated as E5, E6 and E7 are used to configure the SSM's PROm and are NOT installed. NOTE E6 is jumpered to E7 by an etch. 4.2.6 INTERNAL MODEM - 400812-001 There are no LEDs or jumpers on the internal modem. There is one "toggle" switch and three connectors on the board. SWITCHES: A "toggle" on the RS-232 conversion board controls power to the modem assembly; power is ON when the handle is leaning toward the modem board. CONNECTORS: Power (from the system backplane) is connected to the modem assembly via a coaxial type power jack on the conversion board. A DB25, also on the conversion board, provides the RS-232 interface connection for the modem. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg042 A four pin header on the Modem board provides the means to connect the modem to an RJ11 jack on the SSM connector panel. Only pins 1 and 2 are used for the connection. 4.2.7 16-WAY CONTROLLER - 400736-001 The 16 Way has 10 jumpers sets, two LEDs, six Test Points and no switches. LEDS: LED1: The RED LED designed as "ERR" on the metal faceplate. This is a status LED giving the following indications: 1. LED flashes once per second, 16 Way is waiting for a reset. 2. LED flashes twice per second, 16 Way in RUN mode. 3. LED flashes four times per second, 16 Way in maintenance mode. 4. LED does not lite OR remains on, 16 Way is not functioning properly. LED2: The RED LED designed as "BSY", on the metal faceplate. This LED has NO function and may be ignored. JUMPERS: Note the silk screen does not indicate jumper pin numbers. JA,JH(1&2): JA and pins 1 and 2 on JH select the crystal speed for the 2-eight port UARTS. The higher speed is used for the faster baud rates: JUMPER NORMAL SETTING JA 1-2 JH installed JH (3&4): Pins 3 and 4 on JH determine how the 16-Way handles an error encountered during the power self-test. If the 16-Way detects an error during self-test it will post an error and either (1) go offline or (2) continue and attempt limited use (i.e. one port test bad). JH 3-4 installed, 16-Way disabled after an self-test error. JH 3-4 NOT installed, 16-Way attempts limited use after self-test error. (default) JE,JF,JG: These three sets of jumpers determine which bus request/bus grant lines are used by the 16-Way controller. Jumpers ARE to be installed as follows: (The 16 Way uses level 3 bus request/bus grant) o o o o--o o 0 o o o o--o o 1 o o o o--o o 2 o----o o----o o----o 3 | JE | | JF | | JG | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg043 JJ: Jumper JJ is selects the appropriate prom size: Jumpered 1-2 = 256K Prom Jumpered 2-3 = 128K Prom (normal setting) JB,JC,JD: These three sets of jumpers are used to set the base address of the 16-Way. Each 16-Way must have a different base address: o A15 o o A11 o o A07 o o A14 o o A10 o o A06 o o A13 o o A09 o o A05 o o A12 o o A08 o o A04 o | JB | | JC | | JD | NOTE: For below table, I= INSTALLED, O= NOT installed Board (HEX) | JB | JC | JD | Number Address|A15 A14 A13 A12|A11 A10 A09 A08|A07 A06 A05 A04| 01 C000 | O O I I | I I I I | I I I I | 02 C010 | O O I I | I I I I | I I I O | 03 C020 | O O I I | I I I I | I I O I | 04 C040 | O O I I | I I I I | I O I I | 05 C080 | O O I I | I I I I | O I I I | 06 C100 | O O I I | I I I O | I I I I | 07 C110 | O O I I | I I I O | I I I O | 08 C120 | O O I I | I I I O | I I O I | 09 C140 | O O I I | I I I O | I O I I | 10 C180 | O O I I | I I I O | O I I I | 11 C200 | O O I I | I I O I | I I I I | 12 C210 | O O I I | I I O I | I I I O | 13 C220 | O O I I | I I O I | I I O I | 14 C240 | O O I I | I I O I | I O I I | 15 C280 | O O I I | I I O I | O I I I | 16 C400 | O O I I | I O I I | I I I I | 17 C410 | O O I I | I O I I | I I I O | 18 C420 | O O I I | I O I I | I I O I | 19 C440 | O O I I | I O I I | I O I I | 20 C480 | O O I I | I O I I | O I I I | AA7: Although designated at a test point, AA7 is actually a jumper. The jumper is installed when an alternate crystal is being used. Normal setting is jumper AA7 NOT installed TEST POINTS: AA1: Ground AA2: Ground AA3: Ground AA4: Ground AA5: Connected to the cathode of the "ERR" LED. AA6: Ground CONNECTORS: There are two 60 pin connectors on the front edge of the controller. J1: The lower connector, provides the connections for ports SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg044 0 thru 7. J2: The upper connector, provides the connections for ports 8 thru 15. 4.2.8 DIFFERENTIAL SCSI ADAPTER - 400814-001 There are no switches or LEDs on this assembly. There are two jumpers and three connectors. JUMPERS: W1: is the set of jumpers posts on the "single ended" side of the board. W1 INSTALLED = terminator power provided to device connected to J1 W1 NOT installed = device connected to J1 provides its own terminator power. (NORMAL SETTING) W2: is the set of jumpers posts on the "differential" side of the board. W2 INSTALLED = terminator power provided to device connected to J2. (NORMAL SETTING) W2 NOT installed = device connected to J2 provides its own terminator power. CONNECTORS: J1: is a 50 pin connector which connects to a "single ended" SCSI device. J2: is a 50 pin connector which connects to a "differential" SCSI device. J3: is the four pin power connector. 4.2.9 SCSI HARD DISK DRIVES AND TAPE DRIVES This section gives the jumper connections for the SCSI hard drives, and tape drives. NOTE: All drives on the SCSI bus should have their SCSI terminators removed. No two drives can have the same ID address and the primary disk drive must have Drive ID0. The second drive must have Drive ID1. ID 7 is reserved for the SCSI Controller. ____________________________________________ | 355/670MB Disk Drive | | (M380/M760) | |____________________________________________| | DESCRIPTION | JUMPER SETTING | | NAME | FUNCTION | JUMPER POSITION | |-----------|-----------|--------------------| | | SCSI | JP35 JP36 JP37 | | |-----------|--------------------| | | ID 0 | O O O | | |-----------|--------------------| | | ID 1 | I O O | | |-----------|--------------------| |DRIVE | ID 2 | O I O | |SELECT |-----------|--------------------| | | ID 3 | I I O | | |-----------|--------------------| SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg045 | | ID 4 | O O I | | |-----------|--------------------| | | ID 5 | I O I | |-----------|-----------|--------------------| |POWER | SPINUP | JP14 JP38 | |ON | WITH | | |OPTIONS | POWER | I O | |-----------|-----------|--------------------| |TERM. | | JP34 JP41 | |POWER | INTERNAL | | | | | O I | |-----------|-----------|--------------------| |WRITE | | JP18 | |PROTECT | DISABLE | | | | | O | |-----------|-----------|--------------------| |PARITY | ENABLE | JP40 | | | | | | | | I _| I = INSTALLED, O = Jumper NOT installed (OPEN) ____________________________________________ | 120 MB SCSI TAPE DRIVE | |____________________________________________| | DESCRIPTION | JUMPER SETTING | |-----------------------|--------------------| | NAME | FUNCTION | JUMPER POSITION | |-----------|-----------|--------------------| | | SCSI | SEL2 SEL1 SEL0 | | | |--------------------| | | | J3-PAIRS | |SCSI ID | | 7/8 9/10 11/12 | |SELECT | ID 6 | | | | | I I O | |___________|___________|____________________| I = JUMPER INSTALLED, O = JUMPER NOT INSTALLED (OPENED) 4.3 PCBA LOCATION/PLACEMENT REQUIREMENTS There are three different cardcages on the GPx Series 70 Systems, each having its own requirements. SYSTEM BUS CARDCAGE o In the System Bus cardcage, slot one is the left-most card position as viewed from the front of the cabinet. o There is one, and only one, SSM card in the system. The SSM is located in card slot one of the System Bus cardcage. o The CPU card(s) are installed to the immediate right of the SSM card. o The first Memory Controller card is installed to the immediate right of the CPU card(s). o Expansion Memory is installed to the immediate right of the Memory Controller it is cabled to. VME (I/O) BUS CARDCAGE o Card slot number one (1) is the right-most card slot as viewed from SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg046 the rear of the cabinet. o There will be NO empty card slots between VME I/O controllers. - The first VME I/O controller will be installed in card slot one. - The second VME I/O controller will go in card slot two, the immediate left. NOTE: If necessary, a slot may be left open if the five jumpers are installed to right of the top connector of the vacant card slot. Ensure that these jumpers are removed when re-installing a VME card. POWER SYSTEM CARDCAGE o There is one, and only one, Control Module per power system. The Control Module occupies the left most card slot in the power system card cage. o Each cabinet assembly will have a PDU. The PDU occupies the right most card slot in the power system cardcage. o Card position one (1) is the left most position next to the Control Module. o Card slots for the converter modules are identical. Following is there placement scheme: Install +5 VDC Modules starting at the left, next to the Control Module. Install Auxiliary (+/- 12 VDC) Modules staring at the right, next to the PDU. 4.4 CABLE DIAGRAMS This section give the cable diagrams for the GPx Series 70 cables. 4.4.1 916484 SERIAL DEVICE TO CCA/BREAK-OUT BOX This cable is used to connect serial devices (terminals and printers) to the CCA serial port or the 8/16 Way Break-out Box. 4.4.2 916073 EXTERNAL MODEM TO CCA/BREAK-OUT BOX This cable is used to connect an external MODEM to the CCA serial port or the 8/16-Way Break-out Box. 4.4.3 916291 CCA TO PARALLEL PRINTER CABLE (Centronics) This cable is used to connect a Centronics interface parallel printer to the CCA parallel printer port. 4.4.4 916428 CCA TO PARALLEL PRINTER CABLE (Data Products) 4.4.5 RJ45 ADAPTERS The following two diagrams are for the DB-9/DB-25 to RJ45 adapters. 4.5 SUPPORTED PERIPHERALS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg047 This section lists the MBF peripherals that are supported on the GPx series 70 System. MBF peripherals not listed here are not supported on the GPx Series 70 System. TERMINALS Terminals MAI Business Slave Supported in GRAPH Printing UNIX Interface Functionality Environment DT-4301(7270) No No No DT-4309(EVDT) No No No DT-4310(EDT) Yes* No No DT-4312 No Yes** No DT-4313 No Yes Yes*** DT-4314 Yes Yes Yes*** * Requires installed graphics board to support MAI Business GRAPH ** Requires Revision K firmware to support slave printing *** Does not support slave printing in UNIX environment PRINTERS Printers MAI Business MAI Business Industry Parallel Serial GRAPH WORD Standard Interface Interface Slave PT-4201 No No No * * PT-4214 Yes No No Yes Yes PT-4215 Yes Yes Yes No Yes PT-4217 No No Yes No Yes PT-4218 No No Yes No Yes PT-4219 No No No No Yes PT-4220 No No No Yes No PT-4221 No No No Yes No PT-4222 No No Yes No Yes PT-4223 No Yes No No Yes PT-4224 Yes No No Yes Yes PT-4225 No No Yes No Yes PT-4226 No No Yes No Yes PT-4227 Yes Yes Yes No Yes PT-4228 Yes Yes Yes No Yes PT-4229 Yes Yes Yes No Yes * The PT-4201 is supported as a serial printer with a protocol converter box. HARD DISK DRIVES The GPx Series 70 System supports up to five (5) 5.25" SCSI hard disk drives. Following is the disk drive information: Unformatted Capacity Formatted Capacity Average Access Time 380MB 355MB 16MS 760MB 670MB 18MS TAPE DRIVES The GPx Series 70 comes standard with a 1/4" 120MB SCSI Tape Drive. This tape drive requires 600 foot tapes to write, but can read tapes written on a 45MB and 60MB 1/4" tape drive. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg048 The GPx Series 70 also supports a SCSI version of the 240MB 1/2" 1600/6500BPI GCR tape drive. UNINTERRUPTIBLE POWER SUPPLY (UPS) The following is the UPS requirements for the GPx Series 70: Cabinet UPS Size GPx 5070 3KVA GPx 6070 5KVA 5.0 BACKUP AND RESTORE A backup is defined to be "an exact copy of a file as it exists on the disk." In most computer installation sites, backups are made on a regular, if not daily, basis. Backup media is normally kept in an area removed from the computer room, preferably in a fireproof vault. The reason for these precautions are many. Data may be lost through fire, theft, hardware failure, a new program that did not function correctly, or even an operator error. For the above reasons, MAI Basic Four, Inc. recommends that backups be performed regularly (preferably daily), and that backup tape media be stored in a fireproof facility for maximum protection. These backups should, at the minimum, be done with two tape sets, rotating them daily. With this type of rotation, if a tape is lost or damaged, only one day's data will be lost. In the best case, files and programs that are modified are backup up daily using a different set of tapes for each day, and on Mondays the complete system is backed up, with that final tape taken off site. The BOSS/VX OS allows for the customer to backup and restore data using four different backup and restore commands. The rest of this section talks about the recommended backup/restore command 'dump/restore'. The other commands are 'tar', 'cpio' and 'dd'. These three commands are UNIX commands and can be used for data transfer between UNIX systems and used when special type backups are required. For information on these commands see the UNIX System V/386 System Administrator's Reference Manual. 5.1 USING dump AND restore FOR BACKUP/RESTORE The UNIX commands dump and restore may be used to perform system backup and restore functions. 5.1.1 FEATURES OF 'dump' AND 'restore' o 1/4" cartridge, 1/2" GCR and standard output or file o dump allows incremental filesystem dump. The files modified after a certain date can be dumped or the entire filesystem can be dumped. The date of the dump for each filesystem that was dumped is recorded in the file /etc/dumpdates. o Can specify the size of the tape in feet. When the specified size is reached, dump will wait for reels to change. o dump tells the operator what filesystems need to be dumped. For each filesystem that dump keeps track of, dump displays recent dump date and level, highlighting those filesystems that should be dumped. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg049 o dump will also notify all operators in the group adm whenever it requires operator attention. o restore allows complete or incremental restoration of files. o Allows multi-volume set. This allows restore to be interrupted and then restarted. o dump is optimized; as fast as image backup, but individual files may be restored. o Allows interactive restoration of files from a dump tape. It provides an interface that allows the user to move around the directory tree selecting files to be extracted (-i option). o dump and restore can be used in a pipeline to dump and restore a filesystem. o Allows multiple short dumps to reside on a single tape. o Doesn't care if partition is mounted or unmounted. o Will backup open files (so do it in single user mode). 5.1.2 WHEN TO USE 'dump/restore' dump/restore should be used whenever: 1. filesystems need to be backed up 2. Daily, weekly or monthly backups are required 5.2 'dump' Dump copies to magnetic tape all files changed after a certain date in the filesystem. The specifies the date and other options about the dump. consists of characters from the set 0123456789cfusdWn. dump tells the operator what is going on at periodic intervals, including usually low estimates of the numbers of blocks to write, the number of tapes it will take, the time to completion, and the time until the tape change. The output is verbose, so that others know that the terminal controlling dump is busy and will be so for some time. 5.2.1 'dump' OPTIONS (used without preceding "-") 0-9 This is the dump level (or "key"). The command dumps all files modified at lesser levels since the last date stored in the file /etc/dumpdates for the same filesystem. The option 0 causes the entire filesystem to be dumped. c This option will use the 1/4" tape drive (tm0) as the default output device. f Put this option last because it implies that the file name follows. Places the dump on the next file or device named as an argument in the command line instead of on the default tape. If file is "-", dump writes to standard output. NOTE: If the c option is used then the tm0 tape drive will be the backup device and then the f option should not be used. If both the c and f options are left off the dump command will default to the 1/2" tape drive tg0h. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg050 u If the dump completes successfully, writes the date of the beginning dump on the /etc/dumpdates file. This file records a separate date for each filesystem and each dump level. This file also can be edited to change any of the fields, if necessary. s Specifies the size of the tape in feet. When the specified size is reached, dump waits for reels to be changed. (It will also wait at the physical end of tape.) d Specifies the tape density in bpi (bits per inch). 1600 or 6250 bpi. GCR default is 1600 bpi. W dump tells what filesystems need to be dumped. It prints out, for each filesystem in /etc/dumpdates, the most recent dump date and level and highlights those filesystems that should be dumped. w Like W, but prints only those filesystems that need to be dumped. n Whenever dump requires operator attention, notify, all operators in the group adm. 5.2.2 USING dump BACKUPS To use dump to backup a filesystem, use the following command: /etc/dump 0du 6250 /usr (for 1/2" tape drives) or /etc/dump 0uc /usr (for 1/4" tape drives) where all of the files on the /usr filesystem are copied to a tape. If no arguments are given, the key is assumed to be 9u and a default filesystem is dumped to the default tape /dev/rmt/tg0. The default tape size being 2300 feet. NOTE: Specify /etc/dump to avoid conflict with another program /bin/dump. WARNING: If the default tape is in use and not on the system a file will be created called /dev/rmt/tg0h and the data written to it, filling up your root partition. 5.2.3 RECOMMENDED dump PROCEDURE As mentioned above the 'dump' command allows for incremental filesystem backups. By specifying key only, the files modified . after a certain date can be dumped or the entire filesystem can be dumped. Below is a recommended backup schedule for a five week rotation. This schedule will start off with a full filesystem backup and then only backup files that were modified since the last backup. Each week after that, for the next four weeks, on Monday a greater level is done then only files modified during that week are backed up. This schedule would require a set of tapes for each incremental level. The command to use is as follows: /etc/dump Xuc /filesystem (for 1/4" tape drives) /etc/dump Xud 6250 /filesystem (for 1/2" tape drives) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg051 where X=the incremental backup number from the chart below: M T W Th F Sat First week 0 5 6 7 8 9 everything since 0 1 5 6 7 8 9 everything since 1 2 5 6 7 8 9 everything since 2 3 5 6 7 8 9 everything since 3 4 5 6 7 8 9 filesystem=the filesystem to back-up. tapesize=the size of the tape, in feet, being used. To avoid running out of tape, the tape size should be 5 feet less than the actual tape size. NOTE: for 1/4" 600 feet tapes use 7300 for size. 5.3 restore restore reads tapes dumped with the dump command. Its actions are controlled by the argument. Other arguments to the command are file or directory names specifying the files that are to be restored. When from tape, restore reads until it needs no more data. restore is in the root directory /restore 5.3.1 'restore' OPTIONS r The tape is read and loaded into the current directory. This should only be used to restore a complete dump tape onto a clear filesystem or to restore an incremental dump tape after a full level zero dump. R restore requests a particular tape of a multi-volume set on which to restart a full restore. (It will ask you so you can start on second reel.) x The named files are extracted from the tape. If the named files matches a directory whose contents were written onto the tape and the key is not specified, the directory is recursively extracted. (You may not know what files are on which tape.) t The names of the files are listed. (table of contents) i This mode allows interactive restoration of files from a dump tape. An interface allows the user to perform the following tasks; with "restore >" as the prompt: ls List the current or specified directory cd Change the current directory pwd Print the full pathname add Add current directory or the specified argument to list of files to be extracted delete Delete current directory or the specified argument from the list of files extract All the files on the extraction list are extracted from the dump tape SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg052 verbose Prints out information about each file as it is extracted help List a summary of commands quit Allows to quit immediately y restore will not ask whether it should abort the restore if it gets a tape error. m restore will extract by inode numbers rather than by filename. h restore extracts the actual directory instead of files s designates the number of files to skip from the beginning of the tape. This allows multiple dumps Session 0 Session 1 Session 2 ....... /...... /.... ^ position | # /restore xs 2 f /dev/tape b specifies the block size; default on 1/2" tape: 6250 bpi 32K buffer size default on 1/4" tape: 1K buffer size 5.3.2 USING restore TO RESTORE BACKUPS The following is a typical sequence to restore a complete dump. /etc/newfs /dev/rdsk/wd0s3 /etc/mount /dev/dsk/wd0s3 /mnt cd /mnt restore r where newfs will create a new filesystem, mount will mount the new filesystem to /mnt mount point, and restore start restoring to this new filesystem. Another restore can be done to get an incremental dump on top of this. restore leaves a file restoresymntab in the root directory to pass information between incremental restore passes. This file should be removed when the last incremental tape has been restored. 5.4 dump AND restore EXAMPLES As mentioned in section 5.2.2 the command to backup a filesystem would be: /etc/dump 0ud 6250 /usr (for 1/2" GCR tape drives) /etc/dump 0uc /usr (for 1/4" tape drives) These commands will do a full backup of the usr partition and record the date of the backup in the /etc/dumpdates file. /etc/dump 1ud 6250 /usr (for 1/2" GCR tape drives) /etc/dump 1uc /usr (for 1/4" tape drives) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg053 These commands will do an incremental backup, only getting the files that were modified since the 0 dump was used and writes the date of the backup to the /etc/dumpdates file. The above commands can be put into a shell script to give the user a easy backup tool as follows: echo "Backup program" echo "Do you wish to do a full(0) or incremental(1) backup(0 or 1):" read type echo "Please load 1st tape for /usr backup" echo "Enter when ready to start \c" read enter /etc/dump "$type"uc /usr echo "Backup of /usr complete" echo "Please load 1st tape for /usr2 backup" echo "Enter when ready to start \c " read enter /etc/dump "$type"uc /usr2 echo "Backup of /usr2 complete" echo "Backup complete" In the above shell script the 1/4" tape drive is being used for the example. To use the 1/2" tape drive replace the dump command with /etc/dump "$type"ud 6250 /usr If more filesystems need to be backed up then add to the above shell script. To restore a complete filesystem from these backups, first cd to the directory you wish to restore the backup to and then use the commands: /restore xc (for 1/4" tape drives) /restore x (for 1/2" GCR tape drives) If you wish to restore individual files or directories, first cd to the directory you wish to restore then use the commands: /restore ic (for 1/4" tape drives) /restore i (for 1/2" GCR tape drives) This will put you into the interactive utility for restore. In restore cd to the directory that contains the file(s) you wish to restore and then use the add command to add these files to the extract list. Multiple files and directories can be added to the extract list. After all the files to restored are added to the extract list enter the command extract. The files will now be restored. Multiple dumps can also be saved on one tape with the following commands: WARNING: Since the number of files that dump will write to tape is determined by the size of the tape, if a dump of a filesystem other then the first spans a tape you will get a tape at the end of the tape. For example if I have three filesystems to backup and their total size is less than 120MB I can write all three to the same tape. If, on the hand, the total size is greater than 120MB tape errors will occur at the end of tape, since the the number files that could be saved to tape was determined assuming the use of a complete tape. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg054 NOTE: tg0h for 1/2" tape with rewind, tg0hn for 1/2" tape with no rewind, tm0 with rewind for 1/4" tape and tm0n for 1/4" tape no rewind are the devices used in these examples. The full path name is used since the no rewind option is being used. (command using 1/2" tape drive) /etc/dump 0udf 6250 /dev/rmt/tg0hn /usr /etc/dump 0udf 6250 /dev/rmt/tg0h /usr2 (command using 1/4" tape drive) /etc/dump 0usf 7300 /dev/rmt/tm0n /usr /etc/dump 0usf 7300 /dev/rmt/tm0 /usr2 This will backup /usr and /usr2 separately and save it on one tape. This can be restored separately to other partitions with the following commands: cd /mnt /restore x (for 1/2" GCR tape drives) /restore xf /dev/rmt/tm0 (for 1/4" tape drives) cd /scratch /restore x (for 1/2" GCR tape drives) /restore xf /dev/rmt/tm0 (for 1/4" tape drives) This allows restoration of /usr partition to /mnt and /usr2 to a /scratch partition. dump and restore can also be used in a pipeline to dump and restore a filesystem with this command: /etc/dump 0f - /usr | (cd /mnt;/ restore xf -) This will copy /usr partition to whatever partition is mounted on /mnt. 5.5 NOTES AND CAUTIONS ON dump/restore o A level zero dump should be done after a full restore since inodes of files are now in different places than originally. Because restore runs in user level, it has no control over inode allocation; thus a full dump must be done to get a new set of directories reflecting the new inode numbering; even though the contents of the files is unchanged. o restore will restore the files that were dumped before. In doing so, new inodes for this filesystem are created. Therefore, if you need to backup again, a 0 level dump will take a new image again. o If the x or i key has been specified, restore will ask which volume the user wishes to mount. The fastest way to extract a few files is to start with the last volume and work towards the first volume. 6.0 BOSS/VX SYSTEM UTILITIES The BOSS/VX operating system includes a set of system utilities which emulate BOSS/VX commands. The utility programs interact with the user, prompting him/her for any needed information, and return the desired information in a nicely displayed format. To further assist the user, a "utility menu system" has been integrated into BOSS/VX to facilitate easy access to the utility programs. The "utility menu system" makes use of Presentation Services, and can easily be customized to include (or subtract) different menu options. With the . "utility menu system", system utilities can be accessed by name, or via a SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg055 menu. In addition, an on-line help facility is available with the "utility menu . system". On-line help, which can be activated with the key or , and can be used to obtain information regarding available menu selections. 6.1 UTILITY PROGRAM OVERVIEW The BOSS/VX base system comes with nine utility modules. They are: o BASIC Programs o Communications o Directories o Files o Filesystem & disk o Intersystem Transfer o Printers o Save & Restore o System These modules can be seen from the main Utility Menu or accessed directly by entering 'menu eut.'. For example to access the Files module directly enter 'menu eut.file' and the files menu will be brought up. The following two pages list the utility modules and the utility programs within each module. To access these programs directly, enter the program given under the Program Name heading. UTILITY MODULE PROGRAM NAME BASIC Program Utilities basic Compare bcompare Display Program Names bdisplay Encrypt bencrypt List and Cross-Reference bxref Merge bmerge Renumber brenumber Search & Replace bsearch Communications Utilities comm NOTE: BCOM is not available at this time. This menu option is for future use and will not be discussed in this announcement. Directory Utilities dir Change Working Directory workdir Create Directory dcreate Display Directory ddisplay File Utilities file Change File Size fchange Copy fcopy Create fcreate Delete fdelete Display Information finfo File List Maintenance filelist File Repair frepair Move fmove Rename frename Security secure SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg056 Filesystem and Disk Utilities filesys Free Space Analysis freespace * Mount & Unmount smount * NOTE: Free Space is not supported. Use the UNIX command df to display Free Space. Intersystem Transfer Utilities isys Asynchronous Transfer ATP (BASIC program located in /usr/mbf/atp) Batch File Queuer BQR (BASIC program located in /usr/mbf/atp) Cartridge Transfer eut.cisys (uses the programs cwrite, cread, creport, and clabel) Printer Utilities printer Change Print Form pformchg Maintain Print Queue pqueue Printer Parameters pparams Printer Status pstatus Submit Print Job psubmit Save & Restore Utilities save NOTE: This set of utilities is not supported on the GPx 70. For information tape backup and restore see Section 5.0 BACKUP AND RESTORE. System Utilities system Edit Menus menuedit Error Log Utilities serror Operator Information oprinfo Port Configuration configure Set Date & Time sdate 6.2 OPRINFO UTILITY The oprinfo utility is an MBF value-added utility designed to enable a quick, easy, and straight-forward creation of operator accounts. Oprinfo is the recommended utility for all user-account operations, including modification and deletion of existing accounts and changing account passwords. In addition, with the inclusion of groups within BOSS/VX, the "oprinfo" utility will contain support for group creation, modification, and deletion. OPTIONS The oprinfo utility provides eight (8) options. They are: Option 1: Add a User Creates a user account. Includes the creation of a home directory and an optional user ".profile" file. Option 2: Modify a User Modifies user account information. Option 3: Delete a User Removes a user account and home directory (optional) from the system. Option 4: Change Password Changes the password on a user account. Option 5: Generate Report Lists either the user accounts, group SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg057 accounts, or initial start programs to the terminal, a printer, or a file. Option 6: Add a Group Creates a new group name. Option 7: Modify a Group Modifies a group name, group ID, or group members. Option 8: Delete a Group Removes a group from the system. USER ACCOUNT PARAMETERS There are 8 parameters used to define a user on the system. They are: 1. Login name: The name the user will use when logging on the system. The "login name" can be no longer than 8 characters and must contain at least one lower case character. 2. User id: The numerical ID to be associated with the "login name". User ID's must be positive, and the default will be the first available ID number greater than 100. Only ID number 0 will contain root privilege. 3. Group name (id): The name and associated ID of the users primary group. The default value will be group name other, with the corresponding ID of 1. Group names can be a maximum of 8 character long, Group IDs must be positive. 4. Home directory: The directory the user will be placed in upon login. The default will be "/usr/". The home directory will automatically be created when the user account is created and must be an unique. 5. Login shell: The full pathname of the initial program to be executed upon login. The default value is /bin/sh. 6. Program: This is really another login shell, except this field allows parameters to be specified with the initial program. 7. Menu permissions: The menu codes corresponding to the menus which the user may access. The default is full access to all menus, indicated with no permission codes . specified. 8. Additional groups: This is a list of secondary or additional groups . to which the user may also belong. NOTE: After the following parameters are specified, the utility will prompt for a password. GROUP PARAMETERS There are only 3 parameters used to specify a group. They are: 1. Group name: The name of the group. Group names can be no longer then 8 characters. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg058 2. Group name (id): The numerical ID to be associated with the group name. The group ID must be unique and positive, and only one ID may be assigned to a group name. 3. Group members: The user login names which are members of the group. GENERAL INFORMATION Below is some general information regarding the "oprinfo" utility: o When deleting an operator you will be asked if you wish to delete the operators directory. Doing this will completely delete all programs and data files in that directory. o When defining a user account with an initial program of /usr/mbf/bin/basic in the "program" field, the oprinfo utility will prompt for a start size, a program name, and any additional BASIC parameters. o Only a user with "root" privilege may add, delete, or modify user accounts and groups. A user without "root" privileges will only be able to view information regarding his own account. o The files used to store the information related to the "oprinfo" utility are "/etc/passwd, /etc/group, /etc/programs, and /etc/shadow". 6.3 CONFIGURE UTILITY The configure utility is an MBF value-added tool which provides a user- friendly interface to the port, terminal, and printer configuration files. The configure utility allows for the configuration of all GPx supported peripherals. Supported MBF configurations on BOSS/VX are shown below: Graphic Special Printers Terminals Terminals Plotters Modems Devices PT-4201 7270 DT-4314 PT-4215 Standard SP1 PT-4214 DT-4309 PT-4224 Auto Dial PT-4215 DT-4312 PT-4229 PT-4217 DT-4313 HP-7475A PT-4218 DT-4314 Other PT-4219 DT-4315 PT-4220 Other PT-4221 PT-4222 PT-4223 PT-4224 PT-4225 PT-4226 PT-4227 PT-4228 PT-4229 special isp This section covers the configuration options and parameters, highlights the features of the configuration utility, and summarizes SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg059 miscellaneous information regarding the utility. OPTIONS The configure utility provides nine (9) configuration options. They are: Option 1: Save configuration and exit Save configuration changes to appropriate files on disk. This must be done for changes to take effect. Option 2: Add a device Configures a specified port or range of ports for a terminal, printer, plotter, or modem. Option 3: Remove a device Removes all parameters associated with a port, or range of ports leaving the port as "Not configured". Option 4: Move a device Moves a configured device to a non-configured ports. Option 5: Switch two devices Swaps the port locations of two configured ports. Option 6: Report port attributes Lists the port configuration parameters for selected ports to a terminal, a printer or a file. Option 7: Modify port attributes Allows parameters associated with configured ports on the system to be modified. Option 8: Modify number of ghost ports Modifies the number of ghost tasks available on the system. Option 9: Configure Comm Devices This is used to configure BCOM device on the system. Since BCOM is not available on the GPx 70 for this release this option will not covered TERMINAL AND GRAPHIC TERMINAL PARAMETERS There are 21 parameters used to configure terminals and graphic terminals on the operating system. They are: 1. Device Type: Type of device attached to the port. For ports on the 16 way, these may be terminals, graphic terminals, printers, plotters, modems, and special devices. Backplane ports (port 0, 1, 2) are restricted to particular device types. 2. Terminal Type: Model number of terminal attached to the port. The only acceptable graphic terminal type is 4314. 3. Device Name: Name which BASIC will use to access the port. A mapping of BASIC device names to system device filenames can be found in the /etc/bfsdevs file. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg060 4. Start Process: Name of process to execute on terminal when system is brought up in multi-user mode. The default process is /bin/login. 5. Comment: Any 50 character string. Only restriction is the : character cannot be used. 6. Baud Rate: Baud rate for both input and output to the port. Maximum baud rate is 38400. 7. Parity: Parity for the port. Choices are even, odd, or none. 8. Character length: Number of bits used to determined a character. Choices are 7 or 8. 9. Stop bits: Number of bits used to indicate end of character. Choices are 1 or 2. 10. RTS flow control: Determines if RTS hardware flow control will be enabled. RTS is used to start/stop the input to the port. 11. CTS flow control: Determines if CTS (Clear To Send) hardware flow control will be enabled. CTS is used to start/stop the output from the port. 12. IXOFF flow control: Determines if the port will have the ability to send XON/XOFF flow control characters. Enabling IXOFF gives the port control over the flow of input to the port. 13. IXON flow control: Determines if the port will have the ability to receive XON/XOFF flow control characters. Enabling IXON gives the port control over the flow of output from the port. 14. IXANY flow control: Valid only if IXON is enabled. Determines if any, except XOFF, received character may restart output, including an XON. If IXANY is disabled, then only an XON character may restart output. 15. Disconnect on break: Determines if a hangup signal is sent to all processes within the process group when a break condition is detected. 16. Input translation file: The name of a translation table file which the controller will use to translate each character received by the port. 17. Output translation file: The name of a translation table file which the controller will use to translate each character sent out from the port. * 18. Slave printer attached: Determines if a slave printer is connected to the terminal. If yes, then options 19, 20, and 21 will appear. 19. Printer type: Type of slave printer attached. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg061 (only if 18 is yes) 20. Read/status timeout: Number of tenths of seconds to wait for a (only if 18 is yes) printer status. 21. Write timeout: Number of tenths of seconds to wait for a (only if 18 is yes) printer write. * NOTE: Option 18 will be 'graphics terminal parameters' if graphic terminal is entered and options 18,19,20 and 21 of the above will becomed 19,20,21 and 22 respectively. NOTE: For Port 1, the Baud rate, Parity, Character length, and Stop bits parameters will not be displayed. This is because that information for Port 1 is stored in the NVRAM on the SSM board, and is not controlled by the operating system. PRINTER PARAMETERS There are 17 parameters used to configure printers on the operating system. They are: 2. Printer type: Model number of printer attached to the port. 14. Spooling: Determines if spooler queue will be created for the printer connected to the port. 17. Hold priority: The priority associated with the spooler queue. A print job must have a greater priority than the spooler queue in order to be removed from the queue The remaining parameters for printers have been defined in the terminal parameter section. PLOTTER PARAMETERS There are 17 parameters used to configure plotters on the operating system. They are: 2. Plotter Name: Model number of plotter attached to the port. The remaining parameters for plotters have been defined in the terminal and printer parameter sections. MODEM PARAMETERS There are 20 parameters used to configure modems on the operating system. They are: 2. Modem type: Type of modem (internal or external) attached to the port. 17. Carrier required: Determines if the presences of a modem must be detected, before reads and writes to the port will be enabled. 18. Report carries lost: Determines if reads and writes should be disabled when DCD (Data Carrier Detected) goes from high-to-low. The remaining parameters for modems have been defined in the terminal parameter. section. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg062 IMPROVEMENTS IN CONFIGURE A number of significant design changes in the "configure" utility from previous port configuration utilities on prior MBF systems (BOSS/IX in particular) have been implemented. These design changes include: 1. Allowing a range of ports to be configured when a device is added or removed. When adding a device, if multiple ports are to contain the same device type, then all the ports containing the device type may be configured at the same time. For example, if ten ports are to be configured for 4314 terminals, then the ten ports may be configured at the same time by specifying the range of ports to be configured for 4314 terminals. A sample range may be 2-4, 6, 8-14. 2. Displaying a warning message to the user of changes being lost, if an attempt is made to exit the "configure" utility with an or a . If a user attempts to exit the "configure" utility, and modifications have been made and not saved, then the utility GENERAL INFORMATION Below is some general information regarding the "configure" utility. 1. The "configure" utility will not display ports if the corresponding. hardware is not installed on the system. Configuring ports that are not physical will cause 'getty' errors at boot time. 2. All port modifications must be done in single-user mode. Only the "Report port attributes" and "Exit" options are selectable in multi-user mode. 3. The configuration/modification of ghosts will not take effect until the system is shutdown and rebooted. Note, that every ghost configured with the "configure" utility will be allocated table space in memory, whether the ghosts are used or not used. A high allocation of ghost tasks may have an adverse effect on performance (16 ghosts are defined by default). 7.0 BOSS/VX SHELL The BOSS/VX shell is the UNIX System V.3.2 Bourne shell. The BOSS/VX shell, which is also referred to as the command interpreter, is very similar to the BOSS/IX command interpreter (or shell), with minor differences. These notes, therefore, will introduce the BOSS/VX shell by focusing on the similarities and differences between the BOSS/VX shell (referred to in notes as VX) and BOSS/IX shell (referred to in notes as IX). 7.1 DIFFERENCES BETWEEN BOSS/VX AND BOSS/IX A number of fundamental differences between the IX and VX shells exist. 1. In VX, there is no ADMIN user. Instead there is a "root" user which contains special "root" privileges. The "root" logon can ONLY be done at the system console, however, a normal user can receive "root" privileges by entering supervisor mode with the "su" command and entering the "root's" password. 2. In IX, two sets of file access privileges exist--one for the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg063 owner and one for the other users on the system. In VX, the same two sets of file access privileges exist, however, a third set of privileges have been added. The new set of file access privileges is called the group file access privileges. Group file access privileges allow a number of users working on a common project to share certain files, without giving access to other users on the system. 3. In VX, command arguments are specified differently than on IX; and in some cases, the order in which the arguments are specified on VX is important. On VX, a three-argument command would typically be specified as "-lar" as opposed to "-l -a -r", where a single -lar dash (-) is used followed by all the desired arguments, as opposed to an individual dash (-) for every argument. This method works in VX, because every argument for a command is designed to be a single character in length. 4. In IX, the order of options and arguments did not matter; on VX, options MUST be specified before arguments. If an option is specified after an argument, the option will be ignored. 5. In VX, command options are case sensitive. IX only used lower case options. Example: ls -r will list the directory in reverse order, ls -R will do a recursive listing. 6. In IX, macros existed to shorten commonly executed commands. In VX, a macro facility does not exist. To accomplish similar functionality on VX, an environment variable must be created or a command file may be used. 7.2 COMMANDS AND ARGUMENTS This section gives some of the more commonly used commands on BOSS/IX and their use on BOSS/VX. 1. Command "ls" The "ls" command will produce a directory listing of the current working directory or any specified directory. Below is a sample directory listing of the VX root directory. $ls -l (a) total 12 drwxr-xr-x 2 root root 128 Jun 9 12:58 bin drwxr-xr-x 5 root root 256 Jul 13 9:21 dev drwxr-xr-x 10 root root 512 Aug 22 11:02 etc -rw-r--r-- 1 joe other 987 Sep 11 17:15 test drwxr-xr-x 2 root root 128 Nov 30 14:31 tmp drwxr-xr-x 10 root root 512 Aug 22 11:02 u drwxr-xr-x 12 root root 512 Nov 30 8:02 usr drwxr-xr-x 8 root root 256 Nov 30 8:03 usr2 (b) (c) (d) (e) (f) (g) (h) (a) The first line displayed in all "ls" listings will be "total ##", where ## represents the summation of 512 byte disk blocks used by the files in the listing. (b) The first ten characters of each line in a long directory listing represent the filetype and the file access privileges. The first character specifies the file's type, the next three characters SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg064 specify access privileges for the owner, the next three characters specify access privileges for the group, and the last 3 characters specify access privileges for all other users on the system. (c) The second column is called the "link" field. For regular files the link field indicates the number of different filenames which refer to the file. Normally, a 1 will appear in this field for regular files. For directory files, this field can often be used to determined the number of sub-directories within the directory. Since each directory always contains dot (.) and dot-dot (..) directories, a minimum of 2 will always be displayed for directory files. This field allows a user to determined if there are sub-directories without having to list the contents of a sub-directory. (d) The third column indicates the owner of the file. The owner's logon ID name is displayed. (e) The next column indicates the primary group to which the owner belongs. (f) The next column indicates the size of the file in bytes. For directory files, the minimum directory size is 32 bytes (an empty directory), since all directories contain the . and .. sub- directories. (g) The next column indicates the date and time the file was last modified. (h) The last column indicates the name of the file. Many of the arguments for the "ls" command in VX are similar to the arguments in IX. The arguments which have NOT changed are: -l : long listing -a : display all files, including the dot (.) files. The arguments for the "ls" command which are new or have changed in VX are: -R : recursive listing -C : displays directory listing in columns (only filenames displayed) -s : display size of file in blocks -r : display listing in reverse order -t : display listing according to time-last-modified -i : display the file's inode number 2. Command "cd" The "cd" command on VX works identically to the "cd" command on IX. The "cd" command is used to change the current working directory. The directories . and .. can be used as arguments, and typing "cd" with no arguments returns the user to their login (or home) directory. 3. Command "pwd" The "pwd" command on VX works identically to the "pwd" command on IX. The "pwd" command displays the current working directory. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg065 4. Command "pg" The "pg" command on VX functions similar to the "p" command on IX. The "pg" command is used to print the contents of a file to the screen, one screen at a time. The "pg" command introduces new functionality by allowing the user to page forward and backwards in a file, and allowing the user to jump forward and backwards multiple pages at a time. Other VX commands with similar functionality are "cat", "more", and "pr". The "pg" options for moving through the file can be viewed by typing ;"h" at the colon (:) prompt, which appears after the first screen of output has been displayed. 5. Command "mkdir" The "mkdir" command on VX functions identically to the "makedir" command on IX. The "mkdir" command is used to create sub-directories within VX. 6. Command "rm" The "rm" command on VX functions similar to the "delete" command on CorIX. The "rm" command is used to delete only files from the filesystem. Unlike the "delete" command on IX, directory files should not be deleted with the "rm" command in VX. Instead, a second command, the "rmdir" command, is used to remove directory files. Only empty, non-active directory files can be removed. 7. Command "ps" The "ps" command is used to display the status of processes currently on the system, just as on IX. The differences between the two are the available arguments, and the information shown in the listing. Below is a sample listing of all processes currently executing on the system. $ps -ef UID PID PPID C STIME TTY TIME COMMAND root 0 0 0 08:15:33 ? 0:03 sched root 1 0 0 08:15:33 ? 0:01 /etc/init root 2 0 0 08:15:33 ? 0:00 vhand root 3 0 0 08:15:33 ? 0:03 bdflush root 103 1 2 08:17:34 console 0:02 -sh root 173 103 6 09:13:28 console 0:00 ps -ef root 90 1 0 08:17:28 ? 0:00 mbf_errlog root 94 1 0 08:17:31 ? 0:01 lpsched (a) (b) (c) (d) (e) (f) (g) (h) (a) UID: The User ID number (as specified in the /etc/passwd file) of the process owner. In a full listing, the login name is displayed in place of the ID number. (b) PID: The process ID number. This field is necessary in order to kill a process. (c) PPID: The process ID number of the parent process. (d) C: Processor utilization for scheduling. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg066 (e) STIME: The time the process was created (or started). If started within 24 hours then listing is HH:MM:SS. If started over 24 hours, then listing is Month and Day. (f) TTY: The controlling terminal for the process. If no controlling terminal can be identified, then a "?" is printed. (g) TIME: The cumulative execution time (system and user) for the process. (h) COMMAND: The command name of the process. In a full listing, the full command and all its arguments are listed. The arguments for the "ps" command are: -e : list every process on the system -d : list every process, minus parent processes -a : list every process, minus parents and "?" getty processes -f : print a full listing -l : print a long listing -n : names- List only processes for the user ID logon names specified. -t : termlist- List only processes for the terminal identifier specified. -p : proclist- List only processes for the process ID numbers specified. -u : uidlist- List only processes for the user ID numbers specified. -g : grouplist-List only processes for the group ID numbers specified. 8. Command "cp" The "cp" command on VX works similar to the "copy" command on IX. The "cp" command is used to copy files to the same directory or to other directories. Another VX command with similar functionality is "mv", which is used for renaming or moving a file between directories. 9. Command "grep" The "grep" command (Global search for a Regular Expression and Print) on VX works similar to the "match" command on IX. The "grep" command is used to search files for a matching pattern of characters. Every line within a file containing the matching character string will be displayed. The "find" command contains similar functionality to the "grep" command, except that "find" will match the pattern of characters to the file's name, rather than to the contents of the file. The "find" command provides an excellent method for locating a file within the filesystem. 10. Command "set" The "set" command displays all system environment variables. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg067 Among the prominent system environment variables are: HOME: Defines pathname of logon directory (specified in /etc/passwd) PATH: Defines the directory search path for commands PS1: Defines the primary shell prompt PS2: Defines the secondary shell prompt--used to indicate more information is needed for the command to run TERM: Defines the users terminal type; used by vi and other programs 7.3 USEFUL BOSS/VX COMMANDS Tzhe following is a list of useful BOSS/VX commands, the list includes BOSS/IX system commands and their BOSS/VX counterparts. Command options for these and other commands may differ. BOSS/IX BOSS/VX Comments file lists the file type of a file, such as commands, ASCII, BASIC or C program find finds a file with a specified name hd prints the contents of standard input in hex and ASCII format kill kill kills a process. On VX kill with the -9 option should be used nice change the priority of a task nohup prevents a child task from aborting when the parent task stops. e.g., nohup nightly.backup > /dev/null & rel creates mbfinstall tapes su changes of the user's user name who am i lists the user on this terminal delete rm removes files and directories diskusage du displays amount of diskspace used by a directory install mbfinstall software installation utility rename mv renames a file space df shows the available space on all file systems space dfspace shows the available space and total space for each file system ttymodes stty changes the terminal attributes ved vi, ed text editors, vi is full-screen screen-editor, . ed is a line editor. 7.4 DIFFERENCES BETWEEN GPx SERIES 40 AND GPx SERIES 70 SHELL SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg068 Both the GPx Series 40 and GPx Series 70 use the UNIX System V.3.2 Bourne shell. The GPx Series 70 has had some enhancements/changes made to allow for the parallel processing and the fast file system. This section gives those differences. GENERAL DIFFERENCES o chown must be superuser o Filename length from 14 to 255 characters o Terminal device names changed tty001 to /dev/ttyXA/XAAB o Limit to disk space and number of files a user may have ADDED COMMANDS bootflags Display or change system boot flags bp Binary patcher csh C shell dcheck Filesystem directory consistency check devbuild Build virtual devices devdestroy Destroy virtual devices dmesg Collect system diagnostic message to form error log dumpfs Dump filesystem information edquota Set disk quotas for users fsirand Install random inode generation numbers icheck Filesystem storage consistency check ksh Korn shell mkpwdbm Make a database for fast password lookup more View a screen one full page at a time ncheck Generate pathnames from inode numbers noage Run a command with no priority aging nopff Run a command with no-page-fault frequency adjustments noswap Run a command with no swapping offline Bring a processor offline onproc Run a command with processor migration disabled online Bring a processor online otar Standard System V tar for compatibility pwdhd Daemon to oversee password database creation quota Report on user's disk quotas quotaon Turn disk quotas on quotaoff Turn disk quotas off repquota Report on all user's disk quotas savecore Save a core dump of the operating system showcfg Show the configuration of the machine sweepd Patrol seek daemon tunefs Tune up an existing filesystem vmtune Tune system-wide virtual-memory parameters CHANGED COMMANDS acctdusg File blocks are counted using nblocks. ar Names used for lookup operations are truncated to 14 characters. as The .file directive stores file names longer than 14 characters in the string table. See as for details about other extensions. cc This is a new C compiler. See cc for details. clri Changes have been made to accommodate fast filesystem. crash Changes have been made to accommodate fast filesystem. Some system tables do not have print options. Instead, SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg069 references by C language primitives are supported, such as array of and pointer to member. Statistical displays are, in general, not supported except for STREAMS buffer usage. The version of crash supports multiple nested redirection and pipes. cpio This has been replaced with the POSIX version. delta The file owner cannot be preserved because of POSIX-related chown changes. df Space available to superusers is displayed with the -S option. diskusg File blocks are counted using nblocks. dodisk Comment lines in /etc/fstab are now skipped. du File blocks are counted using nblocks. ff Changes have been made to accommodate fast filesystem. find Symbolic links are supported. fsck Changes have been made to accommodate fast filesystem. fsstat Changes have been made to accommodate fast filesystem. fstyp Changes have been made to accommodate fast filesystem. getty The TERM environment variable is set if the terminal type argument is set. init The initdefault settings from /etc/inittab can be over-ridden by the boot flags. The file /etc/syscon.ioctl has been removed. It was no longer needed since init does not try to alter the console terminal modes when a different terminal is used as a virtual console. A new shell script /etc/init.d/addswap was added to add swap devices when the system comes up in multi-user mode. labelit Changes have been made to accommodate fast filesystem. ld Shared externals are placed in .shbss instead of .bss. lint Like cc, recognizes Sequent keywords shared, private, const, volatile, and signed when - Wc, -seq is specified; it has been extended to process files in parallel, if the environment variable PARALLEL is set to a number greater than one (1). ls Symbolic link support has been added. File blocks are counted using nblocks. login Quota support was added. make &, PARALLEL, and -P options were added for controlling parallelism in make files. MAKEDEV Creates device-special files. man This works more like the BSD version in that it understands aliases and pipes its output through a pager. mkfs Changes have been made to accommodate fast filesystem. mkvtoc Disks are populated with a Volume Table of Contents. mount Quota and NFS information for mounted filesystems is reported. pack Filenames are allowed with greater than 12 characters. File owners cannot be preserved because of POSIX-related chown changes. pcat Filenames are allowed with greater than 12 characters. prtvtoc A different VTOC structure is supported. ps The value of some of the process states has changed. The -F option was added to print out a process's size, resident set size, and engine. sh PARALLEL modifications were made. An IFS security hole was fixed. split Filenames are allowed with greater than 12 characters. tar This has been replaced with the POSIX version. stty The sane setting was changed so that it is in 8 bit mode. stty can now set iexten, stop, start, susp, rows, cols, SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg070 xpixel and ypixel to support POSIX. uugetty The TERM environment variable is set if the terminal type argument . . . volcopy Changes have been made to accommodate fast filesystem. whodo Changes have been made to accommodate fast filesystem. 7.5 CONTROL SEQUENCES Control sequences are signals which are sent to the current process in execution. The following is a list of control sequences supported in BOSS/VX. ^D = EOF (ends session) ^C = Kills the command being executed ^S = Stops screen output ^Q = Undoes the ^S (restarts screen output) 7.6 INPUT/OUTPUT/ERROR REDIRECTION The input redirection character is < The output redirection character is > The output redirection "with append" character is >> The error redirection character is 2> The error redirection "with append" character is 2>> 7.7 BACKGROUND PROCESSING Background processing on BOSS/VX is accomplished via the & character. Example: To redirect a recursive directory listing of the filesystem to a file (normally takes 30 seconds) in the background, the command would be: ls -lR / > & 7.8 INPUT BUFFER LIMITATION AND EFFECT ON COMMANDS There is about a 5K byte input buffer limit, this means that a shell command cannot have a parameter string longer than 5K bytes. When using commands with masking, such as ls *, the masking character is expanded to a list of files. This list of files is passed to ls as a parameter string. If the length of the parameter string exceeds the input buffer size, an error occurs and the command aborts displaying the message "arg list to long". This is a UNIX limitation, and does not exist on a BOSS/IX system. A workaround for this limit is to 'cd' to the directory you are working with or use the utility that does the same as the command. 7.9 HUGE DIRECTORIES If a directory exceeds 32k bytes in size, (2000 or more files) several shell commands display the warning message "WARNING: Directory size > 32KB (directory); notify system administrator", when processing the directory. This is a UNIX limitation and does not cause any problem. The limitation does not exist on a BOSS/IX system. 7.10 UNIX TRAINING AND HELP TOOLS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg071 This section describes the Training and Help packages available on the. GPx 70. These packages come on the base tape and can be installed using the 'mbfinstall' command. MANUAL PAGES These packages allow on-line display of manual pages for UNIX and MAI Basic Four commands. It requires that the 'UMAN' (UNIX manual pages) and 'MBFMAN' (MAI Basic Four manual pages) products are installed from the base tape. The format for the command from any shell prompt is: man Ex: man ls man -k search all man pages and suggests possible matches to look into. HELP Help allows an user to look for a keyword in the command description (locate), get a description of a command (usage), get a list of special UNIX characters and their meaning (glossary) or go into help interactively (starter). Help is located in the UHELP product on the base tape. Following are some examples of its use: help starter locate usage glossary help locate help locate find Displays all commands that have the word find in its description. help usage help usage ls Gives a description on the ls command. ASSIST Assist is a UNIX self teach package. It allows an user to interactively learn the different areas of UNIX. Assist is in the UHELP product on the base tape. To access assist, enter: assist Assist will then walk the user through terminal set-up and to the point the user can start working with assist. 8.0 OPERATING SYSTEM OVERVIEW This section gives an overview of the BOSS/VX Memory Management, Filesystem SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg072 and System Security. 8.1 MEMORY MANAGEMENT Memory management on BOSS/VX is a virtual memory, demand paging implementation. This means that an entire process does NOT have to be in memory in order to execute--only the code being executed at any given instance of time is required to be in memory. If a reference is made to code not residing in memory, than the block (or page) containing the reference will be demanded and brought in from disk (hence, the term demand paging). NOTE: A OS memory page size is 4 Kb. A BASIC page size (specified in a START size) is approximately 309 bytes. The beauty in this memory management scheme can be seen by considering the fact that most processes, on average, spend 90% of their time in a 10% area of code. Therefore, with virtual memory, a process 20 pages in size, which seldom executes code in but 2 or 3 of the pages, would only need 2 or 3 pages of memory the majority of the time, rather than 20 pages which would be required in non-virtual memory system. Historically, UNIX required the entire process to be present in order to execute, but with the release of System V, only the pages containing code being referenced is required to be in memory. The advantage of the demand paging algorithm is less swapping because processes larger in size than the amount of available memory space can now begin their execution without forcing the system to swap initially, and more process can exist simultaneously in memory at one time. 8.1.1 AREAS OF MEMORY Main memory is divided into three parts. The first part (lower. address memory) is dedicated to the operating system kernel, the second part contains all the OS tables, and the third portion is user process space. OS Kernel Area The first portion of memory contains the OS kernel. The OS kernel (the /unix file) is the first program loaded into memory by the system loader. The size is approxi 644 KB; this area is FIXED in size and cannot be moved or paged. OS Table Area The second portion of memory is allocated for system table space. There are approxi 26 tables which are built when the system is booted, and the majority of the table sizes are determined by the dct (dynamic configuration table) file and port configurations. This area is FIXED once the system has booted, and cannot be moved or paged. User Process Area The third and final area of memory is space allocated for 1) process execution and 2) OS workspace. 8.2 FILESYSTEM The BOSS/VX filesystem used on the GPx Series 70 is a hierarchical directory structure using the Berkeley fast file system. Below are some SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg073 of the features of this filesystem: o Based on Berkeley fast file system (ufs - UNIX file system/Berkeley) o Standard interfaces for ufs from vfs (virtual file system - Dynix) o MBF interface for bfs (business file system) MBF file types o 255 byte maximum length of individual file name component o Maximum efficiency for large systems -- Large block size 8K(default) and 4K -- Addressing: direct, single indirect, double indirect o Cylinder groups for more efficient disk operations This filesystem with similar directory names as those found on BOSS/IX. The BOSS/VX filesystem is moderately different. The following are charts showing the root and usr filesystems. Included, are the most commonly used directories and a short description of what they contain. root / filesystem Below is the skeleton structure of the most commonly use files on the root filesystem. This is the filesystem mounted in single user mode. / (root) | __________________________________________ | | | | | | | | /bin /dev /etc /tmp /unix /usr /usr2 /lost+found The directories shown in the base filesystem store the following information: /bin: The /bin directory contains commands. /dev: The /dev directory contain all the device files on the system. The device files for the disk are located within sub-directories called /dev/dsk and /dev/rdsk. /etc: The /etc directory contains system administration programs and data files. Files include port configuration data, operator account information, and filesystem maintenance programs. /tmp: The /tmp directory is used to hold temporary system files. Users should not store files in this directory, except on a temporary basis, as contents in this directory are deleted at system startup. /unix: The /unix file contains the operating system kernel. This file is loaded into memory when the system is first booted. /usr: The /usr directory is used for mounting the filesystem (also called usr) containing all the files, programs, and applications normally used in a multi-user configuration. /usr2: The /usr2 directory is used for mounting the filesystem (also called usr2) containing the users' private directories and private files. /lost+found: A /lost+found directory will be present on any partition SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg074 containing a filesystem. The lost+found directory is used to hold lost files for a filesystem, after a file system repair. /usr filesystem Below is the skeleton structure of the most commonly used directories on the usr filesystem. This is the filesystem automatically mounted in multi-user mode. /(root) __________________|______________________ | | | | | | | | /bin /dev /etc /tmp /usr /unix /usr2 /lost+found | | ____|__ | | | | /dsk /rdsk | ______________|____________________ | | | | | | | /adm /bin /lib /mbf /spool /tmp /lost+found _______|_______ | | | | /PS /bin /etc /atp The additional directories shown under /usr store the following information: /usr/adm: The /usr/adm directory contains log files which monitor the access and usage of the system. /usr/bin: The /usr/bin directory contains UNIX commands and utilities which are normally accessed in multi-user mode. /usr/mbf: The /usr/mbf directory contains MBF value-added commands, utilities, tools, and other related MBF enhancements. /usr/mbf/PS: The /usr/mbf/PS directory contains MBF Presentation Services files. /usr/mbf/bin: The /usr/mbf/bin directory contains MBF value-added command and utilities. Note, both utilities and commands are stored in the same directory. /usr/mbf/etc: The /usr/mbf/etc directory contains MBF system administration files, such as MBF spooler-related files, error messages file, and software (Public ID) keys. /usr/spool: The /usr/spool directory contains UNIX spooler-related files. /usr/tmp: The /usr/tmp directory is used to hold temporary system files related to commands and utilities located under the /usr directory. /usr/lost+found: The /usr/lost+found directory is used to hold lost files for the /usr filesystem. 8.3 SYSTEM SECURITY SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg075 On a multi-user computer system, a minimum amount of security is required to protect user files and system integrity from malicious acts of other users. Such protection is achieved on BOSS/VX through: o file access privileges o root privileges o account passwords o menu permission codes Additional security is often added to protect product revenue and to guard against software pirating. On BOSS/VX, such protection is achieved through: o SSN o Software keys o Configuration records 8.3.1 FILE ACCESS PRIVILEGES The command "chmod" and the utility "secure" are used on BOSS/VX to define file access privileges for a file. Every file on BOSS/VX has three sets of access privileges, one for the "owner", one for the "group", and one for everyone else on the system. For example, -rwxr-xr-- 1 root sys 4096 Jul 23 11:19 file1 8.3.1 (Cont.) would specify access privileges of "read", "write", and "execute" for the owner (in this case root), access privileges of "read" and "execute" for the group (in this case sys), and access privileges of "read" for all other users on the system. The command syntax for changing the access modes is: chmod (u|g|o|a) (=|+|-) (r|w|x) OR chmod (nnn) where each n represents a type of privilege (owner, group, other), when translated to binary. 8.3.2 ROOT PRIVILEGE A user with root privilege has the authority to modify characteristics of the operating system environment. Caution must be used when exercising root privileges since actions may effect other users on the system. Examples of commands and utilities requiring root privilege are: o shutdown o date -i o oprinfo o configure 8.3.3 ACCOUNT PASSWORDS Account passwords prevent users from logging onto other user's accounts and altering their files. Account passwords are optional and can be changed using the "oprinfo" utility or the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg076 "passwd" command. User account information is stored in the file /etc/passwd, which is accessible (readable) by everyone. The encrypted password for each user is saved in the file /etc/shadow, which is only readable by the "root" user. 8.3.4 MENU SECURITY CODES Menu security codes are used to deny some user's access to certain utility programs and menus while allowing access to other users. The menu security codes can be viewed/displayed through the menuedit utility. NOTE: Security for menus is only active if the user's starting point is menus. If menu security codes are defined for a user, then the user may only access utility programs or menus for which he has a corresponding security code. If menu security codes are not defined for a user, then the user will have access to all the utility programs and menus (i.e., full access is assumed). Below is a list containing the menu security codes: o BASIC utility programs: code b o System Utilities: code u o Communication: code c o Intersystem Transport: code i o File Transfer Utility: code f o MAGNET: code l 8.3.5 SSN The SSN is a number which is used to uniquely identify every multi-user system which MAI Basic Four sells. This SSN is used by software keys and configuration records to identify the system. 8.3.6 SOFTWARE KEYS Software keys are used to protect integrity and ownership/license rights to MAI Basic Four software. When a secured software package is licensed by a customer, a key (8 digits) is included with the package. This key is a value unique to the customer's system and the software application being installed. The values of the current software keys installed can be viewed by typing # pg /usr/mbf/etc/level/* New software keys can be entered when the product is originally installed, or by using the following command: # install_key 8.3.7 CONFIGURATION RECORDS Configuration records indicate to the operating system which hardware components are available for use on a system. A SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg077 sample configuration record appears below: BOSS/VX System Configuration Record System Type 4120-xxxxxxx Release Level xxxx Subrelease Level xxx Number CPUs 4 Serial Number xxxxxxxx Memory Limit (KB) 16 Max # 16-Way Controllers 4 Max # SCSI Controllers 1 Max # Disks 1 Max # 1/4 Tape Drives 1 Max # 1/2 Tape Drives 1 Max # Serial Ports 64 Max # Parallel Printers 1 Chassis Number 1 Max MegaBytes of FS space 760 The values of the current configuration record for the system can be viewed by typing: # rconf The Configuration Record information is stored on disk, in a file called /etc/scr. This file is encrypted and should not be touched or tampered with. If this file is missing, or if information in the file is corrupted, the system will not boot; i.e., a panic (system crash) will occur. 9.0 CUSTOMIZATION This section give details for customizing your Operating System Parameters (DCT file) and Modifying the system boot environment. 9.1 OPERATING SYSTEM PARAMETERS CUSTOMIZATION On standard UNIX V.3.2, system configuration of buffers, processes, file descriptors, etc, is defined at compile time, and once the Operating System is compiled, these values cannot be changed without re-compiling the OS. For the market place which MBF deals with, this form of system configuration is unacceptable because it does not allow flexibility of changing parameters as user's needs change. As a result, MBF engineering has modified the initialization of these variables to take place at system boot time rather than compile time, thus allowing the allocation of system resources to vary from system- to system, and from boot-to-boot. On BOSS/VX, a DCT (Dynamic Configuration Table) file is used to hold different OS parameters which the kernel will use during system boot to define various OS data structures and variables. The DCT file is a compiled binary file and must exist on disk in the root's filesystem. The majority of the parameters should not need to be modified, and should remain the same for each and every customer. The only parameters which may need modification are: - % Memory for System Buffers - Number of Inodes - Number of Open Files SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg078 - Number of Processes In addition, the compilation, de-compilation, and editing of DCT files can be moderately complex and confusing, and errors made while editing the DCT file(s) can degradate system performance and/or cause system hangs and system errors. It is for the above two reasons that the "configdct" utility was developed, and the "configdct" utility is the recommended method for modifying the DCT file(s). Upon invoking "configdct", the utility will prompt for an input DCT binary file, and an output DCT binary file. The input DCT file will be read, and its values loaded into the utility. All values are loaded, however, only the above four parameters will be displayed. The output DCT file is where the changes will be saved--this can be the same filename as the input DCT file (old configuration will be overwritten), or it can be a new filename which previously did not exist. NOTE: The default system DCT file is /etc/dct. Before running this utility, a copy of this file should be made to a different name on the root so it can be used if the modified file fails. The current values of the four parameters will be displayed, along with the range of acceptable values for each parameter. 9.2 MODIFYING THE BOOT ENVIRONMENT Usually, the GPx 70 system boots automatically. Rarely is interaction . with the SSM monitor required. However, there are times when there will need to be changes to or the boot values restored due to hardware problems, or to turn off a component because of a suspect hardware failure. This section gives information how to use the SSM monitor commands to accomplish these tasks. 9.1.1 SSM MONITOR COMMANDS The following are the SSM Monitor Commands used to modify and display the boot environment. help Shows the syntax for a specified command. This command is useful at any time. local/remote Sets console attributes. This command is useful when powering up the system for the first time and when changing the system monitor. print Prints the current settings for the specified command. This command is useful at any time. bs Boots the system test stage. This command is needed the first time the system comes up and is useful for controlling the power-up characteristics of your system and for isolating system problems. bh Boots the host system. config/deconfig Changes the hardware configuration of the system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg079 log Displays system console I/O since the booting sequence began. This command is useful for checking the system response to what was entered at the console, which could be very important in case of a failure. 9.1.2 DEFAULT SETTINGS The local and remote commands control the port attributes for the console and remote ports. The bs and bh commands control the boot environment, items such as where to get the boot information from and should the system autoboot or not. This information is stored in the NVRAM on the SSM. The default settings for these are as follows: local/remote baud=9600 parity=odd size=7 stop=1 flow=xoff bs opfw=wd(0,0)ssm/fw/opfw lvl2=wd(0,32) diagPath=wd(0,0)ssm/diag/exec monAuto=1 diagAuto=0 bh osPath=0wd(0,0)unix -r wd0s0 -s wd0s1 auxPath=88wd(0,0)stand/dump wd(0,1) 8000 /dev/rdsk/wd0s1 tmpPath=0wd(0,0)unix -r wd0s0 -s wd0s1 autoBoot=1 autoDump=0 To view the parameters of the system see Section 9.1.7 Print Command Parameters. To change a parameter type in the command followed by the parameter to change with an equal sign and the new value. For example to change the baud rate for the local port enter: local baud=1200 NOTE: More then one parameter can be changed for one command on the same line. NOTE: BACKSPACE will erase one character at a time on a line. To erase the entire line, press CTRL+U. The next sections give information on the syntax and examples for the SSM Monitor Commands. 9.1.3 SET CONSOLE ATTRIBUTES - LOCAL/REMOTE The local and remote commands set console attributes so that the SSM monitor can recognize the type of console being used. The SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg080 local command sets attributes for the local TTY line; the remote command sets attributes for the remote TTY line. Syntax (local | remote) (baud=[300 | 1200 | 2400 | 4800 | 9600 | 19200]) (parity=[none | even | odd | mark | space]) (size=[7 | 8 ]) (stop=[1 | 2]) ' Where baud=terminal baud rate parity=the parity setting on the terminal size=data byte size stop=number of stop bits Set the Baud Rate There are two ways to set the baud rate: by specifying the baud rate parameter or by pressing the BREAK key. You can set the baud rate to any of the values specified in the syntax with the baud rate parameter. You can use BREAK while in the SSM monitor to cycle through the baud rates. The recognized baud rates are as follows: 300 4800 1200 9600 2400 19200 If your console is not responding correctly, the problem is often an incorrect baud rate setting. Use BREAK to correct the setting. Accessibility . The local and remote commands can be entered at any stage of the SSM monitor power-up sequence. Example of the remote Command The following command sets parameters for a terminal transmitting at 2400 baud, with parity checking (odd), and a transmission byte size of 8, using one stop-bit per transmission. The syntax would be exactly the same for the local command. remote baud=2400 parity=odd size=7 stop=1 9.1.4 BOOT THE SSM MONITOR - bs The boot command, bs, loads the level 2 and level 3 boot stage software. Syntax bs (opfwPath=lvl3Path) (lvl2Path=lvl2Path) (diagPath=lvl3DiagPath) (monAuto=[1 | 0]) (diagAuto=[1 | 0]) Example of bs Command SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg081 The bs command entered with no parameters boots the default level 2 or level 3 stage software if you are currently in the level 1 to level 2 stage. If the monAuto flag is set to 1 the system will perform subsequent boots automatically. The following command instructs the SSM monitor to automatically boot the level 3 stage (the next time the system is restarted): bs monAuto=1 Accessibility The bs command can be entered only at the level 1 or level 2 stage of the SSM monitor. 9.1.5 BOOT THE OPERATING SYSTEM - bh The bh command boots the operating system and allows the setting of defaults and flags. Syntax bh (osPath=flag[bootpath]) (autoBoot=[1 | 0]) (tmpPath=[bootpath]) (auxPath=[bootpath]) (autoDump=[1 | 0]) ([bootpath]) (opfw stage only) Example of the bh Command For example, the bh command can signal the SSM monitor to boot the operating system automatically: bh autoBoot=1 You can enter this command at any stage of the monitor. Even with the autoBoot flag set, the SSM monitor pauses before automatically rebooting and queries the system console for an alternate boot path. At this time, you can specify a boot path if you don't want to use the default. Turn off the autoboot function by entering a 0 for the auto_boot flag. Set Boot Paths The boot path consists of a number of boot flags plus the path of the bootstrap program on disk or tape. The appropriate boot flags are shown below: Flag Description 0 Autoboot 03 Ask for filename to reboot from 02 Reboot to single-user only 08 Do not clear memory 80 Boot auxiliary boot name The above flags can be put together if more than one option SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg082 makes sense and is needed. For example if a auxiliary boot name is needed and you don't want memory cleared for a dump then the 80 and 08 can be used as follows: bs auxPath='88 wd(0,0)stand/dump wd(0,1) 8000 /dev/rdsk/wd0s1' Request a Memory Dump on Error The parameters of the bh command can be set to perform a memory dump for diagnostic purposes if a system error occurs during a boot of the operational stage. There are two parameters to set: the autoDump flag and the dumper boot path. Set the autoDump flag to 1 if you want a memory dump to occur, and to 0 to disable a memory dump. The following example sets the auto_dump flag: bh autoDump=1 The auxPath parameter defines a boot path to use if a system error occurs. The code specified at this location is executed bh auxPath=pathname The path to the code that performs the dump is a full pathname Accessibility Parameters for the bh command can be set at any stage, but the command to boot is accepted only at the level 3 stage. 9.1.6 REQUEST HELP ON POWER-UP COMMANDS - help The help command, when entered with a specific command as its following parameter (for example, help log), shows the syntax of that command. If you enter the help command with no parameter, the SSM monitor lists all the commands that it understands, but without syntax. The syntax for each command shown by the help command is represented by a combination of brackets, equal signs (=), pipes (|), and braces ({}). Brackets are used to group related items, equal signs are self-explanatory, pipes are read as "or," and braces enclose groups needing a specific value. For example, the following help command syntax has this meaning: "help for bh or bs or log ..." and so on. Syntax help ([bh | bs | log | config | deconfig | local | remote]) Accessibility The help command can be entered during any stage of the SSM monitor power-up sequence. Examples of the help Command The following example requests the syntax of the log command. help log log (clear | all | last=(n)) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg083 9.1.7 PRINT COMMAND PARAMETERS - print The print command prints the current settings of all nonvolatile parameters of the command you specify. Syntax print ([bh | bs | log | config | deconfig | local | remote]) Accessibility The print command can be entered at any stage of the SSM monitor. Example of the print Command The following example shows both a request to print the settings for the local command and the response by the SSM monitor. print local baud=1200 parity=none size=8 stop=1 9.1.8 CONTROL THE SYSTEM CONFIGURATION - config/deconfig The config and deconfig commands are used to add, delete, or change the configuration of the hardware on the system. The current system configuration can be displayed with the config command. Syntax config (SLIC=[slic_id}) (flags=5[hex_value]) deconfig (slic=[SLIC_id]) Display the System Configuration Enter the config command with no parameter to display the system configuration. config This command shows the SLIC IDs and additional information for all controllers, processors, and additional SSMs on the system. Remove a Channel from the System Configuration To remove a channel from the system configuration, enter the deconfig command, followed by the SLIC ID of the controller being removed. deconfig slic=34 The SLIC ID of the controller can be obtained by entering the config command, which lists information about the hardware configuration of the system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg084 Add a Controller to the System Configuration To add a controller to the system configuration, enter the config command followed by the appropriate SLIC ID. config slic=34 Accessibility The config and deconfig commands can be entered at either the level 2 or the level 3 stage before the operating system is booted. 9.1.9 SHOW THE SYSTEM LOG - log The log command displays all system console I/O since the beginning of the boot sequence. Syntax log (clear | all | last=([n])) Clear the Log To erase the system log and start over, use the clear parameter. log clear Show the Log To show the entire log, use the all parameter. log all To set a value to show only the last n lines of the log, use the last parameter. The following example sets the display of future log requests to 10 lines. log last=10 After the last parameter is set, you can simply enter log to display the last n lines of the log. To find out how many lines the log command is currently set to display, use the last parameter with no value, as in the following example: log last The SSM monitor displays the current setting of the last parameter. Accessibility The log command can be entered at any stage of the SSM monitor. . However, remember that the log is not saved across power cycles or firmware reboots. Example of the log Command The following example requests the setting for the last SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg085 parameter of the log command. The SSM monitor responds with the current setting. log last 16 The command shown on the following screen requests the log for the last n input/output entries on the system console. For example, if your last two command sequences were help log and print local, the screen might appear as follows: help log log (clear | all | last(=[n])) print local baud=1200 parity=noParity size=8 stop=1 9.1.10 GO TO THE MONITOR FROM THE OPERATING SYSTEM In certain extraordinary circumstances, it may be desirable to enter the SSM monitor while the system is up and running (for example, when the system is hung and a memory dump should occur). To do this, press CTRL+P. This makes the monitor active and suspends all operating system activities on that TTY. line. To return to an active system, type quit. WARNING: Operations on the SSM firmware are generally unprotected. The system will crash if you try to boot the system while the system is already running. 10.0 SYSTEM PERFORMANCE TOOLS The BOSS/VX Operating System on the GPx 70 comes standard with a set of performance monitor and tuning tools. These tools are as follows: PERFORMANCE MONITORING TOOLS showcfg displays system configuration memsize displays amount of system memory monitor displays various measures of system activity sar samples cumulative activity counters internal to the system, and provides reports on various system-wide activities timex logs the amount of system time, user time, and real time required to execute a command PERFORMANCE TUNING vmtune allows display and tuning of system-wide virtual-memory parameters mkdct, configdct DCT file management SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg086 The following gives a brief discription of the performance tools monitor, sar and timex. 10.1 monitor - MONITOR SYSTEM ACTIVITY monitor displays various measures of system activity. The first portion of the display is a set of bar graphs of processor activity, one for each processor plus a graph for the system labeled "Total". Each bar indicates the percentage of time the respective processor was busy, and is composed of two symbols:'=' for system time and '-' for user time. The rest of the display contains a number of user selectable groups of system activity monitors. To exit monitor, a , Linefeed, or the letter q may be typed. A -I will cause the screen to be redrawn. SYNTAX /monitor [-c n] [-i n] [-p n] [-t] [-f] the command-line options are as follows: -c n Specifies the number of columns to use for displaying the processor bar graphs. Valid choises for n are 1,2, and 3. -i n Specifies the length of the interval (in seconds) to sleep between updates of the screen. The default is 1. -p n If the monitor process is running with sufficient privileges, it will "affinity" itself to processor n. The default is "no affinity"; i.e., the operating system schedules monitor like any other process, running it across all processors. -t Specifies that terse activity monitor descriptions should be used. This allows more information to fit on the screen. -f Indicates that two screens are to be used; one for the processor graphs and one for the activity monitors. While monitor is running, typing an f will flip between the two screens. 10.2 sar - SYSTEM ACTIVITY REPORTED The sar performance tool monitors every form of activity which takes place on the system. sar can be setup to perform data collection in background, display a file containing collected data, or report current system information directly to the terminal screen. SYNTAX sar [options] [delay between snapshots] [no. of snapshots] The command-line options are as follows: -a number of file accesses -b buffer activity -c number of system calls SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg087 -d Disk I/O activity -m number of message and semaphore calls -p memory paging activity -q run and swap queues activity -r memory and swap space -u CPU utilization -v DCT table activity -w swapping and CPU switching activity -y terminal activity -A all of the above 10.3 timex - TIME EXECUTION The timex command is used to log the amount of system time, user time, and real time required to execute a command. The timex command can also be used to display (in sar format) all system activity which occurred during the execution of the command. If no other programs are running, the timex will give a good indication of which resources a specific command uses during its execution. SYNTAX timex [-s] [command] where -s will report the total system activity for the command's execution. 11.0 SYSTEM CRASH/DUMP If the BOSS/VX Operating System encounters an error it can't recover from it will either produce a Core Dump or System Crash (PANIC). This section describes the two and gives the procedures to recover from both. 11.1 CORE DUMP If the OS encounters an error or finds a corruption in a process that it can't recover from involving only that process, it will produce a core dump and exit. The core dump effects only the process that caused it, the rest of the system is not effected. The core dump is an image of the process's work area in memory. This data is written to a file called core located in the working directory. This file can be looked at to help determine the cause of the dump. If a core dump occurs, write down as much as you or the operator running the process can about the steps that occured just prior to the core dump. This should include information on what was running, what was displayed, what other users were doing at that time and anything else that can later be used to reproduce the core dump. A back-up of the core dump should be made since future core dumps will overwrite present ones. This can be done by the use of the 'tar' command. 11.2 SYSTEM CRASH (PANIC) The BOSS/VX Operating System provides a 'user friendly' program to recover from a premature system shutdown situation (Crash). A SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg088 'premature shutdown' is typically a power loss, inadvertent use of the NMI button, forced dump for troubleshooting, or fatal operating system error. When the user attempts to reboot, the system will check all filesystems to see if any of them were left mounted. If it finds a filesystem that was left mounted it will automatically repair that filesystem. Some data maybe lost, but the filesystem will be restored to an usable condition. In addition to repairing the mounted filesystems, the BOSS/VX Operating System recovery will allow the user to save a copy of the system's memory at the time of the crash. This memory information is called a crash dump. The rest of this section gives the dump recovery procedure and steps to force a dump on a hung system. RECOVERY PROCEDURES FOLLOWING A SYSTEM CRASH OR FORCED DUMP The following procedures define the steps to be taken to recover file systems and files after a system crash (also known as a Panic dump) or a system hang. These procedures are similar to those used for the GPx40 series but contain some steps peculiar to the GPx70. LACK OF INTEGRITY FLAGS Whenever a system panic occurs, inevitably there are files open on one or more file systems which are mounted at the time. In order to minimize the loss of data, confusion and possible subsequent damage that can result from in-progress modifications, the system does two things: first, the system flushes from memory to disk any file blocks that were modified but not yet recorded on disk; secondly, the mounted file systems and individual files that were active at the time of the crash are marked in such a way that they cannot be accessed until they have been repaired. The file system check program, fsck, is available for repairing file systems. The file repair program, frepair, is used to repair individual Business Basic data files. These procedures are explained later. CAPTURING THE SYSTEM DUMP The first step following a Panic dump is to "capture" the dump. The GPx70 has a dump program that copies all of physical memory to disk. The NVRAM variable "auxPath" has the path name of this dump program and the location on disk where the dump is to be written. Typically, the dump area is a section of the system swap area. In this case, the value of auxPath would be: auxPath= 88 wd(0,0)stand/dump wd(0,1) 8000 /dev/rdsk/wd0s1 This path indicates the dump program resides on partition wd(0,0) (which is the root partition) and that the filename is stand/dump. the rest of auxPath indicates that the dump area is to be the wd(0,1) partition (the swap partition) but that the dump should start at block offset 8000 (4 MegaBytes) from the beginning of the partition. This allows for a small amount of swapping to occur without overwriting When the auxPath has been set up correctly, the next step is to get the system to execute the dump program. This will happen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg089 automatically if the NVRAM flag "autoDump" is set to 1. If the autoDump flag is set to 0, the panic dump will pass control to the operational firmware (which prompts ---> ). At this point the operator should enter bh doAux, which will cause the dump program to be executed. When the dump program has completed, it returns control to the operational firmware. The operator must manually reboot the system by entering bh to the ---> prompt. AUTOMATIC FILE SYSTEM CHECK After the system has been rebooted, the file system checking command, /etc/fsck is automatically run on all mounted file systems. This clears up glaring errors and inconsistencies in the file system partitions so as to permit the system to access the file systems in the next phases of recovery. When the system boots to single user mode the system checks the root file system. As the system initializes multi-user mode, all file systems referenced in the file /etc/checklist will be checked. If no major file sytem problems are encountered, the system will boot to the level requested with no further intervention. However, under certain circumstances of high volume activity at the time of the system failure, major file system problems may be encountered in the root file system which require the manual execution of fsck to resolve. MANUAL FILE SYSTEM CHECK AND THE MINIROOT Although not normally required, it is sometimes necessary to execute fsck manually to repair a file system. The fsck that is done automatically during the initialization process corrects only certain problems that don't require operator intervention. The manual fsck can correct additional problems but these require operator acknowledgement before they can be done. If the root file system has problems that require manual fsck, the system will detect this during the automatic fsck performed when initiating single-user mode. The system will then attempt to invoke a special system mode where only fsck operations are allowed. An explanatory message is displayed indicating the exact command to be entered and the prompt given is special. For example: ATTENTION: THE ROOT FILESYSTEM IS CORRUPTED IN A WAY THAT CANNOT BE CORRECTED AUTOMATICALLY. THE ROOT FILESYSTEM MUST BE FIXED MANUALLY BY RUNNING: /etc/fsck -b /dev/rdsk/wd0s0 Entering /bin/sh. Avoid unnecessary writes to the filesystem. Please type /etc/fsck -b /dev/rdsk/wd0s0 to repair the root filesystem. When repair is complete, type "exit" to exit the shell and reboot the system. (fix filesystem)# _ At this point, the operator should enter the fsck command as it appears in the screen message. If the fsck operation finds SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg090 severe but repairable damage to the file system, fsck will prompt the operator for confirmation before repairing the damage. If there are many errors, the operator may escape from fsck (by pressing Ctl-c) and re-enter the fsck command with the -y option. This informs fsck that all repair operations should be performed without waiting for confirmation. When the fsck operation completes successfully, the system will shut down to operational firmware, ready for a new attempt to reboot the system. Sometimes the nature of the root file system corruption is such that the manual fsck command cannot be performed or completed successfully. In that case, the system should be shut down to operational firmware level (if this hasn't happened already) by pressing Ctl-p; turning off the autoDump to avoid losing the original dump (type: bh autoDump=0); and resetting the system (type: reset). Next, the operator should boot the miniroot operating system by entering ---> bh 'wd(0,8)unix -M -r wd0s8 -s wd0s8' Once booted to the miniroot, the operator can use the fsck available there to repair the root file system using the command: # fsck /dev/rdsk/wd0s0 If all of the above steps fail to repair the root file system so that it can be booted, the operator should back up as much information as possible from the /usr file system (first mounting it as /mnt and then using tar or cpio to back up files). Then, a full install should be performed from the Operating System release tape. This will cause the root and /usr file systems to. be initialized and re-loaded from tape. SAVING THE DUMP TO TAPE OR A FILE On its way back up to multi-user mode the system will execute the /etc/savecore program. This program will allow the operator to save the dump to a file on disk, to tape, delete the dump from the disk swapper or leave the dump on the swapper and continue with the boot process. After the filesystems are repaired the following message is displayed: Enter within 10 sec to select the dump device (default is /usr/crash) If the user does not enter within 10 seconds the program will automatically write the dump to the /usr/crash directory. The file ;name will be vcore.n, where 'n' is the lowest available number starting with 0. In addition to the dump, the system capture the dmesg file at the time of the savecore in a file called dmesg.n and UNIX in use at the time in unix.n. If the /usr partition is too full to accept large dumps, the operator may alter the /etc/rc2.d/S13savecore file to specify a different directory. NOTE: The above information will be the same if the operator SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg091 selects option D, savecore to disk, from the savecore menu. If the user enters before 10 seconds are up a menu will be displayed. this menu has five options as follows: D - Savecore to disk T - Savecore to tape C - Clear dump A - Abort savecore process H - Help The first option, savecore to disk, will save the dump to the disk as talked about in the previous paragraph. Option T, savecore to tape, will prompt the operator with the following: Please insert the tape and press to continue. The operator should insert a tape in the 1/4" tape drive and enter to save the dump files to tape. NOTE: Saving the dump directly to tape is the recommended way to. save a dump after a crash as it does not require any disk space and saves the operator from having to save the dump from disk to tape late. Entering option C, clear dump, will delete the dump from the swapper. The dump at that time will be lost. Enter option A, abort savecore process, will abort the savecore program and leave the dump on the swapper. Each time the system is booted the savecore program will be run, until the dump is erased or saved to disk or tape. fsck OUTPUT As mentioned previously, the fsck program is automatically run on each file system that was mounted at the time of the crash. In addition to checking and repairing file systems, fsck reports how many Business Basic data files (indexed, serial, direct or multi . keyed files) on that file system lack file integrity, meaning that files were left open and modified when the system crashed. The fsck program creates a file under the /etc/tmp directory which contains all the inodes which lack integrity. There will be one file for each partition listed in the /etc/fstab file. The file name assigned will be .1, where is the file name of the device where the file system resides. If the ".1" file already exists, fsck will delete the old one. The file may be empty if no files without integrity are found. For example, the fsck outputs to /etc/tmp/wd0s3.1 for the file system on /dev/dsk/wd0s3. INDIVIDUAL FILE RECOVERY Since BFS files which lack integrity could be corrupted, users should analyze the files using frepair command, or restore the files from backups. In order to run frepair, users have to convert the inode list generated by fsck into file names after the file system is mounted. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg092 For each file system checked, run the command /etc/fscklist to create a list of files to be analyzed and repaired. The command /etc/fscklist /etc/tmp/.1 creates a file /usr/mbf/bin/fl/fsck..f where is the directory name on which the file system is mounted. If the ".f" created already exists, fscklist will delete the old one. For example, etc/fscklist /etc/tmp/wd0s3.1 creates a file /usr/mbf/bin/fl/fsck.usr2.f for the /usr2 file system (assuming that /usr2 is the mount directory for /dev/dsk/wd0s3). This conversion process could take a few minutes. Next, run frepair in analyze mode under the "selected files" option of the utility. In response to the prompts under this option, enter the file list names (the ".f" files) which have been generated for each of the repaired file systems. The full pathnames of these files need not be specified - the system automatically looks in the /usr/mbf/bin/fl directory. If frepair finds no problems with a file other than the fact that the lack-of-integrity flag was set, it will automatically reset this flag, even though the frepair operation was performed in analyze mode. Files in this state may be used without further recovery procedures. Those files which have problems may be restored from backups. If the backups are inappropriate or unavailable, an frepair in repair mode (using an edited version of the ".f" file) may be used to reconstruct the file. The ability of frepair to restore a file reflecting all application data records at the time of the system crash will depend on the nature of the file corruption which frepair encounters. A manual inspection of the file, or comparison of the file with the last backup, is recommended after reconstruction of the file. The availability of the frepair utility does not eliminate the need for periodic backups, the frequency of which will be site dependent. SYSTEM HANGS When a system has stopped all visible signs of activity for at least 15 minutes and does not respond to any keyboard input for the same length of time, that system may be hung. Longer waits SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg093 are rarely required, so at this point it may be time to force the system to panic and then reboot. To force a panic, one may either issue a reset command directly to the SSM firmware from the system console or press the reset switch on the front panel of the GPx70. To use the console method, type control-p to start communication with the console monitor. The correct setting of the NVRAM auxPath, autoDump, autoBoot and osPath fields should be verified. Next, enter reset If the SSM doesn't respond to the control-p or to the reset command, then press the reset switch on the front panel. Once the panic completes, just follow the steps outlined above for a complete recovery of file systems and user files. 12.0 FOR YOUR INFORMATION This section gives helpful hints to aid you while you are working with the GPx Series 70 System and BOSS/VX. 12.1 UMASK AND BMASK BOSS/VX uses two system variables to determine the file modes or access rights for a file when it is created. One, umask, is used when the file is created in the UNIX environment and is a standard UNIX system variable. The other, BMASK, is used when files are created in the BB90 environment. This variable is an MBF added value variable. Both variables work the same way. The variable has a value assigned such as 022 or some other 3 number value. Each one of these numbers is an octal number. The value in the variable is masked with 666 at the time a file is created to come up with an octal number that when translated to binary represents the file modes for the file. Below are a few examples using umask, keep in mind BMASK works the same way: umask=022 000 010 010 NOTE: When masking 1+0=1 all mask =666 110 110 110 others = 0. --------------------------- 644 110 100 100 file modes rw- r-- r-- umask=000 000 000 000 mask =666 110 110 110 --------------------------- 666 110 110 110 file modes rw- rw- rw- umask=111 001 001 001 mask =666 110 110 110 --------------------------- 666 110 110 110 Note in the last example the last digit or the execute bit was not set, this is per design. There are only two ways to set the execute bit. The first is to use the chmod command or file security utility and do it manually. The second is to create the file as a 'C' program using the 'C' compiler. Also a umask or BMASK value of just 0 means SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg094 000. To find what the system value for these are, from the shell enter umask or echo $BMASK . To set umask enter 'umask ###' and to set BMASK enter 'BMASK=###', both must be entered from the shell. After changing BMASK it must be exported: "export BMASK". The standard default for umask is 022 or rw- r-- r--. The standard default for BMASK is 0 or rw- rw- rw-. umask is set in the /.profile file and can be changed there to the standard your system will use or it can be removed from there and added to the /etc/profile file. The /etc/profile file is where the BMASK variable is set. NOTE: Before restoring files using the transport utilities ensure that umask and BMASK are set to match the file modes you wish. Otherwise you will have to change them manually. NOTE: umask has a 4th octal digit that is a leading digit and used for a forth option in each file mode as follows: OWNER GROUP OTHERS set user id set group id save swapped text If this digit is not added when umask is set, it is assumed to be 0. 12.2 ADDING ADDITIONAL DISK DRIVES BOSS/VX provides a utility to add a secondary disk drive to the system. This utility is used after the disk hardware has been installed using the information in section 4 of this document or by using the GPx INSTINTANCEC manual. This utility will allow you to set the number and size of the disk partitions on the new disk. It will also ask for name of the directory you wish to mount the partition on and if you want to have the partition mounted automatically at boot time. Following are the instructions to use this utility. Ensure you are the super-user or root before starting. Following are the steps to use the diskadd utility: 1) From super-user or root enter diskadd A warning message will be displayed telling the user that this utility will destroy all the data on the selected disk. The user will be prompted to answer YES to continue or anything else to abort. Enter YES in upper case to continue. 2) After the warning message is displayed, the disk available for partitioning are displayed. The first column is the disk number. It is used to select the disk for partitioning. The second column is the type of disk drive, or unavailable if the disk is unavailable, or unknown if the disk is available but of an unknown type. The third column shows in use if any partitions on the drive are mounted, if so the disk may not be selected. If the selected disk's type is unknown, the Disk Type Selection Screen is displayed, otherwise the Partition Screen is displayed. At this time the disk being partitioned is selected by entering the number in the Disk column. The disk number is also the drive SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg095 number, in that entry 1 is wd1, entry 4 is wd4. If the disk selected is of unknown type the Disk Type Selection Screen is displayed allowing the user to specify the type of disk installed. The number to the left of the appropriate disk type is entered. 3) Once the disk type is known, either automatically or after the user specifies the disk type. The current disk partition information is read, displayed, and is available for modification. The Partition information is displayed in a table format giving present system disk partitioning information. This information will be used to update the system disk's vtoc (volume table of contents) and contains the following information: Partition number, partition label (name), size in MBs, mount point (directory to mount the partition to if its to be mounted automatically at boot), auto mount flag (this tells the system if the partition should be mounted at boot time or not), and swap (this tells the system if this is a swap partition or not). At the bottom of the table is the prompt: Enter selection (0-15, x=exit, i=install) to modify: If you wish to use the disk partitioning information in the table to set up the system disk enter i and the main diskadd menu will be redisplayed. If you wish to modify the disk partitioning information enter the partition number you wish to modify. After entering a partition number to modify you will be given the following options: Label - This will allow you to label (name) the partition. This field can be 1 to 6 characters long. Size - This will allow you to give the size for the partition. This option is used to increase or decrease the size of a. partition. The size can be changed in increments of 1 megabyte. NOTE: A partition's size can not be increased if there is no available disk, so decrease other partitions before increasing any. Mount point - The mount point is the directory the partition will be mounted to. The root and usr mount points can not be changed. An entry of a . (period) removes a mount point. If the partition is Automounted, a mount point is required. If a partition is not Automounted, it doesn't have to have a mount point. Automount - If this option is set to yes, the partition will be mounted at boot time. A yes for this option requires a mount point. A partition can not have swap and automount both set to yes. sWap - If a partition is to be used as swap when the system is in multi-user mode, set swap to yes. If it is not to be used as a swap partition then set swap to no. redisPlay screen - As updates are made to the table the information in the table will not be displayed until you are SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg096 done with that partition update or this option is used. Help - The help messages will be displayed. Remove - Removes a partition from the disk. The root, swap, usr, firmware, vtoc, boot, and miniroot partitions can not be removed. Done - Indicates that changes to this partition are complete. Final verification for this partition takes place. The screen and main menu is displayed. This partition can be selected again for editing. Enter the capital letter in each option to select that option. When you are done with the update of the system disk partitioning, enter i to install this information into the system disk's vtoc. 4) Next messages will be displayed telling the user that the information is being written to disk and that the filesystems are being made. After this is complete the diskadd main menu will be redisplayed. If you wish to set-up another disk go back to step 1, if you are done with the update enter x to exit. The secondary disk will be now ready for use. 12.3 ADDING A NON-MBF TERMINAL TO THE MBF CONFIGURE UTILITY This section gives the steps required to add a non-MBF terminal to the MBF Configure Utility, which will allow you to use the terminal in BASIC. WARNING: Using these steps will not guarantee that the terminal will function properly in BASIC. There may be some functions of the terminal that do not work in BASIC and/or some BASIC functions that do not work with the terminal. It is a good idea to have the customer test the terminal with their application to ensure it works the way they want it to.' NOTE: These steps are to add a terminal for use in BASIC. To add a terminal for use in UNIX, ensure there is an entry for the terminal in the /usr/lib/terminfo directory. To enable the terminal, set the term system variable to equal the terminal you wish to use then export the term variable. ex: term=wyse50 export TERM To add a terminal for use in the configure utility and for use in BASIC, 'vi' the /etc/termdef, and add the default entries for the terminal. The entries in the termdef file are as follows: Terminal_name:baud_rate:parity:char_length:stop_bits:DTR:CTS: IXOFF:IXON:IXANY:disconnect_on_break:input_translation: output_translation:slave_printer_attached When you run the configure utility there will now be an entry for the new terminal. The next step is to create a tty mnemonics table for the terminal. First 'cd' to the /etc/ttymntbl directory. You can create your own SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg097 tty mnemonics table or copy a present table to the new terminal name and modify that table. After modifying the table, use the makettymntbl command to compile the table. After this is complete yKou will now have a tty mnemonics table for the new terminal for use in BASIC. Below is an example of the steps for modifing a tty mnemonics table for a wyse50 terminal. cd /etc/ttymntbl cp 7270.mntbl wyse50.mntbl vi wyse50.mntbl (modify the mnemonics for your terminal) makettymntbl wyse50.mntbl wyse50 After these steps are complete you will be able to configure the terminal using the configure utility and use the terminal in BASIC. Keep in mind that these steps do not guarantee that the customer will have full use of all the functionality of the terminal and/or that all of the mnemonics in BASIC will work with the terminal. 13.0 DOCUMENTATION This section gives the manuals that are available for the GPx Series 70 system. BOSS/VX Installation and Configuration Manual - M0186 This manual provides information on installing and configuring the BOSS/VX operating system on GPx Series Systems. It is assumed that the system hardware has been installed, and all necessary switch and jumper settings . have been made, as described in the Installation and Maintenance Manual for the system. BOSS/VX System Administrator Guide - M0187 This manual describes the procedures used in the administration of the BOSS/VX operating system running the UNIX Operating System. This manual is designed to provide instructions on how to perform the required administrative tasks, provide background information about when and why these tasks are required and serve as a reference guide to administrative procedures. BOSS/VX Utilities Reference Manual - M0188 This manual provides a full description of the BOSS/VX Utility Programs. BOSS/VX User Guide - M0189 This manual is provides basic information on the BOSS/VX operating system and instructions for working with it. Special attention is given to working with the filesystem and the shell programs (C and Bourne shells, the use of the ed and vi text editors and printing.) BOSS/VX Diagnostics Manual - M0190 This manual describes the diagnostics features developed for the BOSS/VX systems. The features consist of a system error logging facility and a set of programs to aid in diagnosing system problems to various levels. GPx Series 70 Installation & Maintenance Manual - M8223 This manual provides information on hardware system installation, troubleshooting, and removal and replacement of subassemblies. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg098 BOSS/VX Commands Manual - M0226 This manual provides descriptions of commands, file formats and additional information for system administration. sysadm Utilities Manual - M0225 This manual provides procedural and reference information for system administration using the sysadm utilities on GPx Series 70 systems. The following manuals have been updated to reflect changes required for the BOSS/VX operating system and GPx Series hardware: PC-Link User Guide - M6340 Intersystem Transport Package User Guide - M6354 Business BASIC 90 Reference Manual - M6262 The following manuals are for use in the UNIX environment: UNIX System V/386 User Guide - P0001 UNIX System V/386 System Administrator Guide - P0002 UNIX System V/386 System Administrator Reference Manual - P0003 UNIX System V/386 Programmer Guide Volume I - P0004 UNIX System V/386 Programmer Guide Volume II - P0005 UNIX System V/386 Programmer Reference Manual - P0006 14.0 BUSINESS BASIC 90 AND PORTING GUIDE Business BASIC 90 (BB90) on BOSS/VX has been designed to be compatible with BB90 on both the BOSS/IX and BOSS/VS systems. To the end-user, BB90 will look identical to BB90 on other systems, however, internally the design of BB90 and the structure of Business BASIC filetypes are different from other MBF systems. This section covers the filetype differences contained in BB90 on BOSS/VX,. and provides a detailed guide to porting Business BASIC applications to the BOSS/VX system. These procedures are based on the following assumptions: 1. All BASIC programs are either BOSS/IX or BOSS/VS Business BASIC 90 compatible. 2. The person reading this document has a working knowledge of BOSS/IX or BOSS/VS and BOSS/VX OSs. 14.1 BUSINESS BASIC FILETYPES On BOSS/IX, the structure of the inode or file descriptor was modified by MBF to hold Business BASIC specific information, such as the record size, maximum number of records, etc. In addition, Keyed files, such as Direct and Multi-keyed, were composed of two separate and distinct files--a Data file and an invisible Key file. On BOSS/VX, this method of storing information was no longer practical. Modifying the inode to hold specific Business BASIC filetype information would mean the BOSS/VX inode structure would no longer be compatible with the UNIX inode structure (meaning BOSS/VX would not . be UNIX compatible). Therefore, on BOSS/VX, specific Business BASIC filetype information is stored within the Business BASIC file as header information. This new header will be present on all Indexed, Serial, Direct, Sort, and Multi-keyed files. In addition, there is no longer two separate files for Direct and Multi-keyed files. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg099 14.2 PORTING BASIC APPLICATIONS This section describes the steps required to port a BOSS/IX or BOSS/VS Business BASIC 90 compatible application to a BOSS/VX system. Below is an overview of the porting process. Each program change specified in step 1 is explained later in this section. 1. Examine the programs and files and, o Change file names longer than 14 characters to 14 or less characters. o As needed, change hard coded path names. To keep the program source the same between operating systems, the path name can be calculated based upon the operating system. System commands need to be reviewed for compatibility between the BOSS/IX and BOSS/VX operating systems and as needed changed. o Access rights need to be changed to the BOSS/VX format. o Check for pre-Business BASIC 90 sensitive code, such as checks for "BB86" in SYS function. Update the programs as needed. o Check for use of terminal names "TA" through "TZ" and change to "T10" to "T35". o Check for use of the FID function and replace it with the appropriate ATTR function. 2. Use BOSS/IX or BOSS/VS tools to validate the integrity of the files being transported. Corrupted files may not be successfully transported. 3. Create a BQR filelist by first creating a system filelist and then running BQR to turn it into a BQR filelist. 4. Transfer the programs and data from the BOSS/IX or BOSS/VS system to the BOSS/VX system by MCS tape or asynchronous communications. NOTE: To write to tape on the BOSS/IX system use 'cwrite', to write to tape on the BOSS/VS system use 'MCSI'. To port using asynchronous communications use Level 4 ATP on both systems. 5. Examine and correct any errors documented in the .itplog files on the BOSS/VX system. 6. Test the product. 14.3 BOSS/VS AND BOSS/IX CHANGES REQUIRED FOR BOSS/VX The following changes must be made to BOSS/IX and BOSS/VS Business BASIC 86 files and programs for them to successfully execute under BOSS/VX Business BASIC 90. A. Path names A BOSS/VX disk is divided into several partitions. For efficiency, the root partition (directory /) is kept at a minimum size. Therefore, to prevent premature filling of the root SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg100 partition, applications should be placed in another partition such as /usr or /usr2. Place all application programs in a directory not being used by MBF. Any directory being used by an MBF product may be changed during use or during an update. A new directory in a non-root partition can be created for the programs being ported, such as /usr/asd or /usr2/asd. Any programs containing hard coded path names must be changed if the directory containing the application is changed. The maximum size of a path name, starting from root, on a BOSS/VX system is 1024 bytes, on a BOSS/IX system it is 128 bytes. On a BOSS/VS system it is 255. The following pseudo code establishes if the system being used is a BOSS/VS, BOSS/IX, or BOSS/VX. This information can be used to determine a path name based on the operating system. SYSTYPE$ = "BOSSVX" IF ASC("A") <> ASCII("A") THEN SYSTYPE$ = "BOSSVS" ELSE IF LEN(SSN) <= 10 THEN SYSTYPE = "BOSSIX" ENDIF ENDIF The pathname can then be setup for the proper system, as shown by the following pseudo code: USEPATH$ = "/usr/bfms13b/" IF SYSTYPE$ = "BOSSVS" THEN USEPATH$ = ".BFMS13B.DATA." ELSE IF SYSTYPE$ = "BOSSIX" THEN USEPATH$ = "/bfms13b/data/" ENDIF ENDIF B. File names File and directory names longer than 14 characters, including the extension and excluding the path name, are not supported and must be changed to less than 14 characters. Acceptable: /usr/name/A234567890.234 /usr/name/A234567.901234 /usr/name/A Not Acceptable: /usr/name/A2345678901.345 NOTE: On the GPx 70 the file name limit is 255 characters. To ease porting files between systems in the GPx family, keep file names to 14 or fewer characters. C. Access Rights The directive used to create files "CREATE" is unchanged. However the usage rights format specified as a directive attribute has changed. BOSS/IX uses a period (.) to indicate a specific right is not granted (rw. rw.) and the BOSS/VX system uses a dash (-) to indicate the same (rwxrw-rw-). The concept of "group rights" SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg101 has been added to the BOSS/IX concept of owner and others. Example: The following BASIC commands are used to change the access rights to the file samplefile.dta to o owner: read, write, no execute, o others: read, write, no execute, and o group: on the BOSS/VX system users in the same group have same access rights. BOSS/IX example: CREATE ATTR="name=samplefile.dta USAGE_RIGHTS=rw.rw." BOSS/VX example: CREATE ATTR="samplefile.dta USAGE_RIGHTS=rw-rw-rw-" BOSS/VS permits specifies file access based upon the user name attempting access and a list of access "rules". For example, the following BASIC commands are used to change the access rights to the file samplefile.dta to: o owner (GP.AAA): read, write, execute access o group (GP.*): read, execute access, o (AA.XXX): no access, o others (*.*): execute only. BOSS/VS example: CREATE ATTR="name=simplefile.dta USAGE_RIGHT=W(GP.AAA);R(GP.*);E(*.*-(AA.XXX))" BOSS/VX example: CREATE ATTR="samplefile.dta USAGE_RIGHTS=rwxr-x--x" One person in a group cannot be excluded. D. Initial Prefix List Changes On BOSS/IX, BASIC's initial prefix list is the same as the operating system's prefix list and on the BOSS/VS, BASIC's initial prefix list is the same as the user's prefix list combined with the system prefix list. On BOSS/VX only the working directory is used as BASIC's prefix list. This can be setup, however, on BOSS/VX by using the environment variable PFXALT. Example: If the current directory is /usr/bfms13b/data, and the inclusion of usr/bfms13b/pgms is desired in prefix list, type: PFXALT="/usr/bfms13b/pgms" export PFXALT basic s=300 You will now have a prefix of /usr/bfms13b/data /usr/bfms13b/pgms. E. Earlier Versions of Business BASIC Programs checking for the version of Business BASIC must take into SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg102 account the change in the Business BASIC version number from BB86 to BB90. The method used to determine the version of Business BASIC needs to assume the version number of Business BASIC will continue to change over time. For example change: IF POS("BB86"=SYS) = 1 THEN .... to IF ( POS("BB86"=SYS) = 1 OR POS("BB9"=SYS) = 1 ) THEN . F. FID Function Rather than using the FID function, use the ATTR function to obtain the information about the file. The FID function may function differently on BOSS/VX, depending on how it is used. G. Error Handling Whenever an error occurs in BASIC, two error values are returned. As with BOSS/IX, the BASIC error value is stored in the system variable ERR. On both, the Operating System error value is stored in TCB(12). The definition of the error code can be displayed on BOSS/VX by using the shell command errno. An example code segment follows: 1000 CMD$ = "errno "+ STR(ABS(TCB(12))) 1010 SYSTEM CMD$ All system errors are stored in the file /usr/mbf/bin/stderror. H. CPL and LST Functions (BOSS/IX only) These two functions, which compile and list lines of BASIC code, require the user to know BASIC's table and file layout. Since these tables and layouts changed for BOSS/VX and will continue to change as BB90 changes, these functions have been replaced by the functions SYNTAX, MAKEPROGRAM, and LISTPROGAM. I. LIB Directive (BOSS/IX only) The LIB directive has been replaced with the ability to call "C" programs from within BB90. A "C" program is called from within BASIC the same as a BASIC subroutine (CALL "pgm", arg1, arg2, ...). But the "C" program must be designed to be called from BASIC. J. New Functions (BOSS/IX only) MIN returns the smallest of its arguments: MIN(1,2,3) is 1. MAX returns the largest of its arguments: MAX(1,2,3) is 3. ATN Returns the arctangent (in radians) of its argument: ATN(90) is 1.5596 COS Returns the cosine of its argument: COS(90) is -0.4480 EXP Returns the value of e raised to the specified value: EXP(10) is 22026.4657 LOG Returns the natural log (e) of the specified value: LOG(22026.4645) is 9.9999 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg103 SIN Returns the sine of its argument: SIN(90) is 0.89399 SQR returns the square root of its argument: SQR(4) is 2. ^ The exponentiation operator "^" will now raise a value to a non-integer power. For instance, PRINT X^ (1/3) will print the cube root of X. K. CALL'ed programs - Console Mode CALL'ed BASIC programs can now drop into console mode where there are "uncaught" errors or the key is pressed (just like run programs). Once in console mode, variables may be examined and printed, but, the CALL'ed program itself may not be modified or saved. The following commands do not work within CALL'ed programs: DELETE, LIST, MERGE, PSAVE, RUN, and SAVE. L. Edit, List, and Print Abbreviations (BOSS/IX change only) The abbreviations of ' / and ? are supported for the commands edit, list, and print. M. Easy Edit Typing ' or edit allows the last program or console-mode statements (with or without statement numbers) to be easily edited and re-executed. O. Larger Program Size Business BASIC programs may now be larger than 64KB. The program is limited to the area specified by the START size, which may be several million bytes. For Business BASIC programs being ported from a BOSS/VS system, the START directive requires specifying the number of pages. P. DEVINFO and TSK(0) device ordering BOSS/IX DEVINFO and TSK(0) functions return devices arranged in ascending device number order (e.g., T1, T2, ... T10, T11). BOSS/VX will still group like devices together, as does BOSS/IX, but will not necessarily return the devices sorted in ascending number order. This may be changed in the future. The BOSS/VS DEVINFO returns different information in bytes: 6,7, and 9 than the BOSS/VX DEVINFO. Q. Device Naming (BOSS/IX only) BOSS/IX supports the naming convention of TA to TZ or T10 to T35 to mean terminals 10 to 35. BOSS/VX only supports the T10 to T35 naming convention. U. Optional $ after string functions (BOSS/VS only) BOSS/VS permits an optional $ after a string function or reserved word, like SYS$, BOSS/VX does not permit the $. 14.4 USING ITP FOR TRANSFERRING FILES A. cread changes SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg104 cread now provides the following options which ease the transport and conversion of programs and data: . o automatic file renaming, overwriting, skipping the file, asking the user what to do if the file name already exists in the directory. o program conversion with output to a file, printer, or terminal while the program is being loaded from the tape. You no longer need to run BQR to convert programs. o files with file names containing special characters, such as !*{}[]()#^$, can be always renamed, or left as is. The special characters can be user specified, or a default set of characters used. B. cread and BQR Program Conversion Syntax Checking Changes When program conversion is performed by either cread or BQR, each. program is checked for the following possible problems: 1) Use of the following functions or directives: CPL, LST, LIB 2) Text strings longer than 14 characters used as file names. 3) Instances of the characters "TA" to "TZ" used as terminal names. 4) Syntax errors, such as error 20's and 26's. Other potential problems, such as HEX codes or use of the FID command are not checked during program conversion. C. String File Conversion If tape is being used to transport the information, string files are first converted to Serial files, ported as Serial files by tape, and then converted back into String files on the BOSS/VX system. If asynchronous communications is being used, string files are transferred without any conversion. D. Tape Compatibility Across Systems The following table shows which Intersystem Transport tapes can be read or written on which drives and systems. Writing Reading Drive Tape Drive 45MB 60MB 120MB Required 120Mb rw 600ft 60Mb rw r 450 or 600ft 45Mb rw r r 450 ft r = read w = write 1) BOSS/VX has only 120MB tape drives. BOSS/IX and BOSS/VS uses 45, 60, and 120MB tape drives. E. Using Asynchronous Communications The features and function of asynchronous file transfer is the same on BOSS/VX as on BOSS/IX. Cabling SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg105 Direct and modem to modem uses 916073-001 Rev B Available Ports The last two ports (J6 and J7) on each breakout box are available for use with ATP when using modems. This corresponds to ports 6 and 7 on the first breakout box, 14 and 15 on the second, and so on. This port restriction is for ATP only, it does not exist for general modem use. All ports on a breakout box are available for direct connect ATP use. Port Configuration Using the configure utility set the port's parameters as specified below. The default value can be used for any unspecified parameter. Direct Device Type: terminal Terminal Type: 4313 or 4314 Input Baud Rate: 9600 Parity: no parity Character Length: 8 Stop Bits: 1 IXANY flow control: no Modem to Modem Device Type: modem Modem type: external Input Baud Rate: 2400 Parity: no parity Character Length: 8 Report Carrier Loss: yes Carrier Required: no Stop Bits: 1 IXANY flow control: no Modems ATP uses only a Paradyne FDX 2400 PLUS modem, no other modems, including an internal modem, are currently supported. Modem Configuration The modem is configured the same as for an SPx using ATP modem transfer. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB003 Pg106 FIB 00004 09/25/90 *** BOSS/VX Software Announcement Rel. 1.0C for GPx 40 [ WPSS-182 ] *** 1.0 INTRODUCTION Level 1.0C of BOSS/VX for the GPx Series 40 is now available. It is the recommended Operating System for the GPx 240, GPx 340 and GPx 440. The 1.0C Operating System is derived from the 1.0B O/S, and contains new features and enhancements/corrections to the 1.0A and 1.0B Operating System releases. This Software Announcement contains general information about the Level 1.0C BOSS/VX Operating System. Installation and update procedures are fully documented in this announcement, as well as sections on enhancements/corrections, new features and new/updated manuals. It is recommended that you read this document before installing Level 1.0C. For information on ordering 1.0C refer to Marketing Announcement 881 US/C for the United States or 554 I for International. WARNING: The performance for GPx 2/3/440s with 4MB and 8MB of memory running 1.0C is not as high as on prior operating system releases such as BOSS/VX 1.0A/B. This is because additional software functionality added to 1.0C has increased the size of memory required for the operating system. Because of this increase, the performance on the 4MB and 8MB systems may be impacted. We recommend that when upgrading to BOSS/VX 1.0C that 4MB of memory be added to all systems presently c onfigured with 4MB or 8MB of memory. This is particularly important for those systems which are presently configured near the top-end of the recommended concurrent user range or those systems pushing the limit of acceptable response time. Additional memory where needed to maintain performance must be purchased by the customer at their own expense. On the GPx 240, the response time with eight concurrent users will be slower than with BOSS/VX 1.0B, but still less than four seconds. WARNING: If you are replacing the Mother Board on a GPx 440 with part 916556-004, the system must be on 1.0B or greater or the system will not boot due to a security PANIC. TABLE OF CONTENTS 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cover 2.0 Boss/vx Operating System History . . . . . . . . . . . . . . . . . . 1 3.0 New Products in Level 1.0C . . . . . . . . . . . . . . . . . . . . . 1 3.1 New Software Products . . . . . . . . . . . . . . . . . . . . . 1 3.1.1 Support of 64 users. . . . . . . . . . . . . . . . . . . 1 3.1.2 User Access of BFS C-Library Functions . . . . . . . . . 1 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg001 3.1.3 DOS READ/WRITE Capabilities. . . . . . . . . . . . . . . 1 3.1.4 PDF. . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3.1.4.1 printversion Command . . . . . . . . . . . . . . . . . 2 3.1.4.2 pdfversion BASIC Program . . . . . . . . . . . . . . . 3 3.1.5 bbmap. . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2 New Hardware Products . . . . . . . . . . . . . . . . . . . . . 4 3.2.1 1/2" Tape Drive with SCSI Adapter. . . . . . . . . . . . 4 3.2.2 VGA Monitor and Keyboard . . . . . . . . . . . . . . . . 6 3.2.2.1 Installation of the VGA Monitor . . . . . . . . . . . . 6 3.2.3 Ethernet Controller. . . . . . . . . . . . . . . . . . . 7 3.2.4 670 MB SCSI Disk Drive . . . . . . . . . . . . . . . . . 7 3.2.4.1 System/Disk Drive Matrix . . . . . . . . . . . . . . . 7 3.2.5 PT-4220 Serial Printer . . . . . . . . . . . . . . . . . 8 3.2.6 New Internal MODEM Card. . . . . . . . . . . . . . . . . 8 3.2.7 New SCSI Controller, Model 1542B . . . . . . . . . . . . 8 3.3 Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3.1 oprinfo. . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3.2 Serial Port Numbering. . . . . . . . . . . . . . . . . . 9 3.3.3 Slave Printing on the DT-4312. . . . . . . . . . . . . . 9 3.3.4 termcaps and terminfo Files for the DT-4312 and DT-430 . 9 3.3.5 Configurable Parallel Printers on 1.0C . . . . . . . . . 9 3.3.6 Printer Matrix . . . . . . . . . . . . . . . . . . . . .10 3.3.7 lphold Command . . . . . . . . . . . . . . . . . . . . .11 3.3.8 UNIX Package now included in BASE O/S. . . . . . . . . .12 4.0 Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 4.1 DEMON Diagnostics . . . . . . . . . . . . . . . . . . . . . . .13 4.2 DIVE Diagnostics. . . . . . . . . . . . . . . . . . . . . . . .13 4.3 BASS Diagnostics. . . . . . . . . . . . . . . . . . . . . . . .13 4.4 Security Violation PANIC Analysis . . . . . . . . . . . . . . .14 5.0 Installation and Update of the Operating System and Optional Software Packages. . . . . . . . . . . . . . . . . . . . . 15 5.1 Installation of the BOSS/VX Operating System . . . . . . . . ..15 5.1.1 System Disk Partitioning . . . . . . . . . . . . . . . .19 5.2 Update of the Operating System . . . . . . . . . . . . . . .. .20 5.3 Installation/Update of the Security Configuration Record . .. .23 5.4 Installation and Update of Optional Software Packages and Diagnostics. . . . . . . . . . . . . . . . . . . . . . .. .24 5.5 Customization of Optional Software Packages. . . . . . . . .. .27 5.5.1 Presentation Services . . . . . . . . . . . . . . .. .27 5.5.1.1 Presentation Services Custom Menus. . . . . . . . .. .27 5.5.1.2 Presentatin Services Form . . . . . . . . . . . . .. .27 5.5.2 ORIGIN 2.1B GPx Installation Procedure. . . . . . .. .28 5.5.2.1 Installation Requirements . . . . . . . . . . . . .. .28 5.5.2.2 New Installation of ORIGIN 2.1B . . . . . . . . . .. .29 5.5.2.3 Updating From 2.1A. . . . . . . . . . . . . . . . .. .31 5.5.2.4 Updating From 2.0A. . . . . . . . . . . . . . . . .. .33 5.5.2.5 Updating From 1.3B or 1.3B. . . . . . . . . . . . .. .34 5.5.2.6 Executing ORIGIN on the GPx . . . . . . . . . . . .. .35 5.5.3 ORIGIN Conversion . . . . . . . . . . . . . . . . .. .35 5.5.3.1 MPx to GPx Conversion . . . . . . . . . . . . . . .. .36 5.5.3.2 SPx to GPx Conversion . . . . . . . . . . . . . . .. .37 5.5.4 ORIGIN 2.1B New Features. . . . . . . . . . . . . .. .37 5.5.5 Translation . . . . . . . . . . . . . . . . . . . .. .38 5.5.6 Related Documentation . . . . . . . . . . . . . . .. .40 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg002 6.0 Communication Packages. . . . . . . . . . . . . . . . . . . . . . . 41 6.1 27xx/37xx Batch Emulation. . . . . . . . . . . . . . . . . .. .41 6.1.1 Software Requirements and Installation. . . . . . . .. .41 6.1.2 Hardware Requirements and installation. . . . . . . .. .41 6.1.3 General Information . . . . . . . . . . . . . . . . .. .43 7.0 Notes and Cautions. . . . . . . . . . . . . . . . . . . . . . . .. .45 7.1 ATP Notes and Cautions . . . . . . . . . . . . . . . . . . .. .46 7.2 PC-Link Notes and Cautions . . . . . . . . . . . . . . . . .. .47 7.3 TBC Notes and Cautions . . . . . . . . . . . . . . . . . . .. .47 8.0 Related Documentation . . . . . . . . . . . . . . . . . . . . . .. .49 2.0 BOSS/VX OPERATING SYSTEM HISTORY 1.0A First release of BOSS/VX. It was required for the GPx 340 and 440. 1.0B This release introduced the GPx 240 and 27xx/37xx Communication. It also supported use of mother board part number 916556-004 on a GPx 440, and will cause a PANIC if the mother board is used on 1.0A. 3.0 NEW PRODUCTS IN LEVEL 1.0C This section contains information on products that are new for Level 1.0C 3.1 NEW SOFTWARE PRODUCTS 3.1.1 SUPPORT OF 64 USERS The GPx 440 will support up to 4 serial device controllers raising the maximum number of users to 64 if 4 16-ways are installed. 3.1.2 USER ACCESS OF BFS C-LIBRARY FUNCTIONS BFSINT (BASIC File System INTerface) is a library which providesa set of C-callable procedures for applications which . require record level access to BFS files. Access to files may be by KEY or INDEX, and locking/timeout control is performed using options which are similar to those found in Business BASIC. Record level access includes the ability to create, delete, open, close, lock and unlock files. Multi-keyed file create and MAGNET remote access are not supported on the initial release. Refer to the BFSINT Reference Maunal, #M0228 for detailed information. 3.1.3 DOS READ/WRITE CAPABILITIES Commands to support READing from and WRITEing to MS-DOS format 3-1/2" floppy diskettes is provided. The supported commands include: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg003 - dosdir - DOS directory listing. - doscopy - file copy to or from a DOS floppy. - dosrm - remove a file from a DOS floppy. - dosformat - format a DOS diskette. - dosmkdir - create a directory on a DOS floppy. - dosrmdir - remove a directory from a DOS floppy. NOTE: dosrm will cause a core dump if used with a floppy that has write-protect on. 3.1.4 PDF On 1.0C the PDF's have been written to comply with the updated MBF Mnemonics Standard. These PDF's have been compiled with the new Simple compiler and are version stamped. The PDF product, which is installed as part of the BASE O/S contains: - all currently supported PDF's - translation tables and source for translation tables - configuration files needed to configure printers and slave printers - PDFVERSION and printversion (Programs which display the PDF version) This product has been created to allow the release of new and/or updated PDFs from O/S releases, but is also a standard. product in the 1.0C release. 3.1.4.1 printversion COMMAND The 'printversion' command will display the version level of the PDF files with version stamping on 1.0C and later levels. To use it do the following: Enter: printversion The screen will display 'Enter file name: ' Enter the complete file name: /usr/mbf/etc/ptrtbl/4228 The following will display: PDF NAME: 4224 PDF PLATFORM: GPx PDF VERSION NUMBER: 0106 SIMPLE COMPILER VERSION: INTERNAL SIMPLE COMPILER VERSION NUMBER: 1 3.1.4.2 PDFVERSION BASIC Program PDFVERSION BASIC program is used to display the version level of PDF files with version stamping. 10 BEGIN 20 INPUT (0)'CS',"ENTER PDF NAMES: ",NAME$ 30 OPEN (1,ERR=20)NAME$ 40 READRECORD (1,IND=0,SIZ=8)SIMPLE$ 50 IF SIMPLE$<> ".SIMPLE." THEN CLOSE(1); PRINT SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg004 50: "NON MAI BASIC FOUR PDF"; STOP 60 READRECORD(1,IND=140,SIZ=24)REC$ 70 LET VERSION$=REC$(1,5), PDFNAME$=REC$ 80 PRINT "PDF VERSION NUMBER IS: ",VERSION$, 80: " NAME: ",PDFNAME$ 90 END 3.1.5 bbmap bbmap is used to identify files that reside on bad blocks when disk errors occur. mbf_errorlog command will report the disk unit number and the physical block numbers that have disk errors. If the errors are non-recoverable, the user can run bbmap to help decide whether or not the bad blocks contain critical data. For example, if the bad block resides in a data file the user should run DIVE to map out the block. Then frepair can be run to repair the file or restore the backup copy. If the bad block resides in the file system i-node area or super-block free list, the user should run DIVE to relocate the bad block, then run fsck to repair the file system. bbmap generates the file path name(s) from physical block numbers. The usage is as follows: bbmap -b number(s) device - number(s) is the block number that you wish to determine the file residing on that block. - device is the disk which is being searched, the names of the devices can be found in /etc/partitions. Example: bbmap -b 11111 disk0 displays: 11111 block in file /bin/make NOTE: Certain conditions may not be recoverable under fsck and could result in some loss of data. 3.2 NEW HARDWARE PRODUCTS 3.2.1 1/2" MTS Tape Drive with SCSI Adapter The existing MBF 1/2" MTS drive (model 4402) can be field upgraded with the Single-Ended SCSI Adapter, P/N 400494-015. The drive will be supported by the UNIX utilities cpio and tar and will be supported by Business BASIC READ/WRITERECORD for data interchange. The MBF utility tsave is NOT supported. NOTE: The following information can also be found in the GPxTM Series 40 Installation and Maintenance Manual Addendum Package, #M8215B, pages 18 - 23. To install the 1/2" MTS tape with SCSI interface: Remove terminators RN3, RN4 and RN5 from the SCSI controller in the main CCA. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg005 On the SCSI interface controller on the rear of the MTS drive, jumper W7, the only jumper on the controller, should be removed. Below are the switch settings for the SCSI Interface Adapter Board, Switch 210 SCSI ID SCSI ID# Switch Position +----------------------------------------------+. | 0 1 2 3 4 5 6 7 |. +----------------------------------------------+. 0 | OFF OFF OFF OFF ON ON ON ON | 1 | OFF OFF ON OFF ON ON ON ON | 2 | OFF ON OFF OFF ON ON ON ON | 3 | OFF ON ON OFF ON ON ON ON | 4 | ON OFF OFF OFF ON ON ON ON | 5 * | ON OFF ON OFF ON ON ON ON | 6 | ON ON OFF OFF ON ON ON ON | 7 | ON ON ON OFF ON ON ON ON | +----------------------------------------------+. NOTE: The ON position is indicated by a Black dot on the switch. * MBF default 1/2" MTS SCSI Interface Adapter Board Switch Settings, Switch 76543210. Name Function Switch Position +-------------+---------------+---------------------------------+ | | | 0 1 2 3 4 5 6 7 |. | # of | 1* | ON ON | | available | 2 | OFF ON | | units on | 3 | ON OFF | | controller | 4 | OFF OFF | +-------------+---------------+---------------------------------+ | | | 2 3 | | | Normal * | ON ON | | | | |. | | Loop On | | | | Power Up | OFF ON | | | Routine | | | | | |. | Self-test | Loop On | |. | Features | RAM Data | ON OFF | | | Pump | |. | | | | . | | Allow | | | | Execution | | | | after | OFF OFF | | | Power Up | | | | Failure | | +-------------+---------------+---------------------------------+ | | | 4 5 | | | 880* | ON ON |. | Drive | 890/891 | OFF ON | | Models | 900 ** | ON OFF | | | 990 *** | OFF OFF |. +-------------+---------------+---------------------------------+ | | | 6 | | Parity | Enabled * | ON | | | Disabled | OFF | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg006 +-------------+---------------+---------------------------------+ | | | 7 | | | Arbitrating * | ON | | Model | Non- | OFF| | | Arbitrating | | +-------------+---------------+---------------------------------+ | NOTE: The ON position is indicated by a black dot on the | | switch. | +---------------------------------------------------------------+ * MBF default ** Up to 32-KBytes blocks--data recoverable after fatal drive error. *** Up to 64-KBytes blocks--data not recoverable after fatal drive error. 3.2.2 VGA MONITOR AND KEYBOARD The MBF VGA color and monochrome monitors are supported on the GPx 40 platforms. The monitor will be usable as a standard UNIX device with UNIX System V Release 3.2 'C' applications, but cannot be used as a BFS (BASIC-capable) device. The 240 has a built-in VGA interface, which the monitor is attached to. The 340/440 systems will need the 16-bit optional adapter card, P/N 400078-001. For more information refer to the GPxTM Series 40 Installation and Maintenance Manual Addendum Package , #M8215B, pages 15-19. NOTE: To change the CMOS on a system with a monitor, the operator can press ++ any time between the Self-test at boot-time and when UNIX boots 3.2.2.1 INSTALLATION OF THE VGA MONITOR STEP 1: Power down the system, install the VGA controller, plug in the keyboard and monitor and power on the monitor. NOTE: If the operating system is already 1.0C or higher, it is not necessary to use an Operating System tape in this procedure. Skip to step 5. STEP 2: Place the 1.0C Base operating system tape in the tape drive and power on the system so that the system boots from the tape. NOTE: If a monitor is being added to a GPx 240, skip to Step 4. STEP 3: All boot messages will appear on the monitor. On the GPx 340/440 the following message will appear: EQUIPMENT CONFIGURATION ERROR - RUN SETUP PRESS F1 KEY TO CONTINUE OR CTRL-ALT-ESC FOR SETUP Press CTRL-ALT-ESC to display the SETUP menu. Select 7. PRIMARY DISPLAY: The monitor types will be displayed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg007 Select 4. SPECIAL ADAPTER The Hardware Configuration Menu will redisplay. Select E. END AND REBOOT The system test will be performed again and the Operating System Installation Menu will be displayed STEP 4: Select I for Install or U for Upgrade. No . additional packages need to be installed for the VGA to work. After the Operating System installation, reboot from the hard disk. STEP 5: While the system is booting, the following message will appear: Configuring monitor, please wait . The configuration files are being changed to allow COM1 to be used as a user port. The installation is complete. Refer to Section 5.1 Step 11 when doing a complete O/S installation or refer to Section 5.2, Step 9 when doing an O/S upgrade. 3.2.3 ETHERNET CONTROLLER 1.0C provides support for the 10 M-bit/sec Ethernet Controller , P/N 400817-001, and the needed cabling and transceiver requirements for MAI Local Area Network (MAINET). Any orders for Ethernet controllers MUST go through the Networking Business Unit, at (714) 730-3018. Refer to the GPx Series 40 Installation and Maintenance Manual Addendum Package, #M8215B, pages 2-14 for hardware information. 3.2.4 670 MB SCSI DISK DRIVE The 670 MB SCSI disk drive is now supported on the GPx 440. A maximum of 2 670 MB disk drives can be installed in the main chassis. If 2 670 MB disk drives are installed, no floppy disk drives can be installed because there is no available space within the machine. The addressing for the 670 MB drive is the same as the 347 MB drive and can be found in the GPx Series 40 Installation and Maintenance Manual, #M8215A on page s 2-45 thru 2-47. 3.2.4.1 SYSTEM/DISK DRIVE MATRIX Below is a matrix of the disk drives and the systems they are supported on. Disk Drive System +-------------+----------+----------+----------+ | | GPx 440 | GPx 340 | GPx 240 _| | 115 MB | No | Yes | Yes | +-------------+----------+----------+----------+ | 200 MB | Yes | Yes | Yes | SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg008 +-------------+----------+----------+----------+ | 355 MB | Yes | Yes | No | +-------------+----------+----------+----------+ | 670 MB | Yes | No | No _| 3.2.5 PT-4220 SERIAL PRINTER Support for the PT-4220S 600 LPM serial printer is available for the GPx 40 system. Customers upgrading to GPx systems with a parallel PT-4220 can have their printer converted to serial with the PT-4220 serial conversion kit, P/N 514220-021. Select 4220S when configuring the printer in the configure utility. NOTE: For optimal performance, the PT-4220 with serial interface should have 'despool wait' set to 'yes' in its printer defaults. The printer defaults can be changed with the pparams utility. 3.2.6 NEW INTERNAL MODEM CARD The 24M internal MODEM card, P/N 400822-001, is now being shipped with GPx 340/440 systems. This MODEM meets the requirements for U.S. and Canadian communications. The MODEM is compatible with CCITT V.22B, CCITT V.22bis, Bell 212A and Bell 103 protocols. The MODEM can communicate with other MODEMs at 300, 1200 and 2400 bps. The MODEM can communicate with serial devices at rates of 110, 300, 600, 1200, 2400, 4800, and 9600 bps. For more information refer to the GPx Series 40 Installation and Maintenance Manual Addendum Package , #M8215B, pages 24-28. 3.2.6.1 525 MB 1/4" CARTRIDGE TAPE DRIVE The 525 MB tape drive can replace the current 120 MB 1/4" tape drive in the main chassis. Only one internal 1/4" tape drive is allowed in a system. The drive appears the same to the system as the 120 MB tape drive and uses the UNIX commands tar and cpio and the MBF utilities tsave and trestore. T 1000 ft. tape 600 ft. tape a Read Write Read Write p +----------+----------+---------+---------+ e 525 MB | Yes | Yes | Yes | Yes | |----------+----------+---------+---------| D 120 MB | No | No | Yes | Yes | r +----------+----------+---------+---------+ i 60 MB | No | No | Yes | Yes | v +----------+----------+---------+---------+ e 45 MB | No | No | No | No | +----------+----------+---------+---------+ NOTE: The 525 MB 1/4" cartridge tape drive can READ 600 ft. tapes written on the 60 MB tape drive but a 60 MB tape drive cannot read a 525 MB tape. 3.2.7 8mm HIGH CAPACITY CARTRIDGE TAPE DRIVE The 8mm tape drive will provide up to 2.3GB storage capacity for backup purposes. One external 8mm tape drive, P/N 400828-011, will be supported with the GPx 440 which requires the expansion chassis with the Rancho Card. Information can be SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg009 copied to this drive by using the UNIX commands tar and cpio. 3.2.8 GCR 1/2" SCSI INTERFACE TAPE DRIVE The primary purpose of this drive is to provide high speed backup plus data interchangeability with other systems. The GCR drive supports 6250 BPI high density recording to provide up to 240 MB tape capacity when 3600 ft. tapes are used. The GCR can also be set from the front panel for 1600 BPI format tapes. The existing MBF GCR 1/2" tape drive (Model 4405) can be field upgraded with the Differential SCSI adapter, P/N 400652-007. One external GCR drive will be supported on the GPx 440 with the Expansion Chassis and Rancho Card. The drive can be accessed with the UNIX command tar, cpio and Business Basic with READ RECORD and WRITE RECORD for data interchange. 3.2.8.1 NEW SCSI CONTROLLER, MODEL 1542B The 1542B (P/N 916601-002) has the same functionality as the 1542A (P/N 916601-001). An extension cable (P/N 916477-002) for the LED on the front of the CCA is also included with the 1542B. The card is physically smaller than the 1542A and has different switches and jumpers which can be found in the GPx . Series 40 Installation and Maintenance Manual Addendum Package , #M8215B, pages 39-61. 3.2.9 5 1/4" FLOPPY DISK DRIVE The 340/440 will support the existing 5 1/4", 1.2 MB floppy disk drive, P/N 514127-311. The GPx 40 Series allows a maximum of 1 floppy disk drive per system. 3.2.10 EXPANSION CHASSIS The Expansion Chassis will support additional internal and external SCSI devices. The expansion chassis will support up to 5 half-high devices; or 2 full-high and 1 half-high; or 1 . full-high and 3 half-high devices. The maximum number of hard disk drives supported is 5. A total of 7 SCSI devices can be supported per SCSI controller. The Expansion Chassis will be placed vertically next to the GPx 440 system to form a twin tower configuration with a SCSI bus from the main chassis. Disk Drives Full-High Half-High 355 MB 115 MB 670 MB 200 MB 3.2.11 SCSI CONVERTER (RANCHO CARD) The SCSI converter, P/N 400814-001, will convert the Singled Ended SCSI Adapter to the Differential SCSI Adapter for external SCSI devices such as GCR and HCC tape drives. The converter card will be mounted in the expansion chassis. 3.2.12 UPS REQUIREMENTS FOR GPx 440 WITH THE EXPANSION CHASSIS. The main chassis, expansion chassis and a terminal can run on a single uninterruptable power supply that is provided by MBF. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg010 3.3 CHANGES/ENHANCEMENTS 3.3.1 oprinfo oprinfo (Operator Information) utility has had some changes which will be explained below. o Each operator must have a unique directory. This directory is required because when an operator is deleted 'oprinfo' asks if you would like to delete the home directory. A unique directory prevents accidental loss of application programs or data files a unique directory used by others. o The login shell will now be /bin/sh instead of /bin/execsh. Each operator will have a .profile created when an operator is created or modified in their home directory, within the .profile /bin/execsh will be used to access BASIC. If the . .profile is not used the with /bin/sh the operator will not go into BASIC. o Since the home directory will be different for each operator, the prefix for the application programs can be set in the 'Program' option. Example: /usr/mbf/bin/basic s=128 pgm=/usr2/pgms/MENU -nr 'prefix"/usr2/pgms /usr2/data"' 3.3.2 SERIAL PORT NUMBERING Previous to 1.0C, 8-way ports were numbered as if they were 16-ways. Therefore, a system with 2 8-ways had ports from tty000 to tty007 and tty016 to tty023. On 1.0C, a system with 2 8-ways will have the ports numbered consecutively. The addressing of 8/16-ways will remain the same as in the GPx Series 40 Installation and Maintenance Manual, #M8215A, pages 25 - 30. 3.3.3 SLAVE PRINTING ON THE DT-4312 1.0C provides support for slave printing on the DT-4312 with a minimum of Revision K or later firmware. 3.3.4 TERMCAP AND TERMINFO FOR THE DT-4312 AND DT-4309 The TERMCAP and TERMINFO files for the DT-4312 and DT-4309 are also included in 1.0C. 3.3.5 CONFIGURABLE PARALLEL PRINTERS ON 1.0C Prior to 1.0C, all printers could be configured as either parallel or serial regardless of the characteristics of the printer itself. Now the configure utility displays only those printers with parallel capabilities. Below is a list of configurable printers: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg011 PT-4217 PT-4223 Laser printer PT-4218 PT-4224 PT-4214 Dual Mode special PT-4222 isp 3.3.6 PRINTER MATRIX Printer Interface Emulation GPx 240 GPx 340/440 PT-4201 Serial, Printronix Yes * Yes * Requires GPx Protocol Converter -------------------------------------------------------- PT-4214 Serial Printronix Yes Yes Parallel Printronix Yes Yes BCFO Serial Printronix Yes Yes -------------------------------------------------------- PT-4215 Serial Diablo Yes Yes SLVD Serial Diablo Yes Yes -------------------------------------------------------- PT-4217/18 Serial IBM Yes Yes SLVD Serial IBM Yes Yes Parallel IBM Yes Yes -------------------------------------------------------- PT-4219 BCFO Serial Printronix Yes ** Yes ** -------------------------------------------------------- PT-4220 DATAPROD DATAPROD-P No No -------------------------------------------------------- PT-4220S Serial DATAPROD-S No Yes -------------------------------------------------------- PT-4221 DATAPROD DATAPROD-P No No -------------------------------------------------------- PT-4222 Serial Printronix Yes Yes Parallel Printronix Yes Yes -------------------------------------------------------- PT-4223 Serial Diablo Yes Yes Parallel Diablo Yes Yes -------------------------------------------------------- PT-4224 Serial Printronix Yes Yes Parallel Printronix Yes Yes BCFO Serial Printronix Yes Yes -------------------------------------------------------- PT-4225 Serial IBM Yes Yes SLVD Serial IBM Yes Yes Parallel IBM No No -------------------------------------------------------- PT-4226 Serial IBM Yes Yes SLVD Serial IBM Yes Yes Parallel IBM No No -------------------------------------------------------- PT-4227 Serial IBM Yes Yes SLVD Serial IBM Yes Yes Parallel IBM No No -------------------------------------------------------- PT-4228 Serial IBM Yes Yes SLVD Serial IBM Yes Yes Parallel IBM No No -------------------------------------------------------- PT-4229 Serial Diablo Yes Yes SLVD Serial Diablo Yes Yes Serial HP No No Parallel HP No No -------------------------------------------------------- * Configure as 4224 on 1.0A and 1.0B. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg012 ** Configure as 4214. 3.3.7 lphold COMMAND The lphold command is designed to keep a printer assigned to one user until the user frees the printer. A print job can be completed and the printer closed but no spooled jobs will print until the lphold command is given again. Previously OPTS="-off" was used in the OPEN statement to turn off spooling. The problem with that method was that once the printer was closed, any spooled print jobs would print immediately which could print on special forms. OPTS="-off" is still supported. lphold will stop all print jobs to a printer until the lphold command is issued again to start despooling the print jobs. Below are steps for using lphold: Within a BASIC program you can issue the command: 10 !lphold list=LP hold=6 The default hold priority for a spooled printer is 2. By making the hold priority 6, with the lphold command, jobs will not despool. Open the printer with spooling off and print the information: 20 OPEN (1,OPTS="-off")"LP" 30 Print (1)"Report Heading" 40 . Once the job has finished, CLOSE the printer and reissue the lphold command: 9000 CLOSE(1) 9010 !lphold list=LP hold=2 9020 OPEN(1)"LP"; CLOSE(1) The OPEN and CLOSE on line 9020 are needed to restart the despooler and print any jobs in the print queue. The OPEN alone will start jobs printing. Take into consideration that the operator may have to change paper and that the OPEN after the second lphold command should be done at a later time. 3.3.8 UNIX PACKAGE INCLUDED IN THE BASE O/S The UNIX portion of the Operating System is now included in the Base portion of the O/S. In previous levels the UNIX package had to be installed with 'mbfinstall', which is no longer possible since it is no longer a seperate a package. 3.2.9 5 1/4" FLOPPY DISK DRIVE The 340/440 will support the existing 5 1/4", 1.2 MB floppy disk drive, P/N 514127-311. The GPx 40 Series allows a maximum of 1 floppy disk drive per system. 3.2.10 EXPANSION CHASSIS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg013 The Expansion Chassis will support additional internal and external SCSI devices. The expansion chassis will support up to 5 half-high devices; or 2 full-high and 1 half-high; or 1 full- high and 3 half-high devices. The maximum number of hard disk drives supported is 5. A total of 7 SCSI devices can be supported per SCSI controller. The Expansion Chassis will be placed vertically next to the GPx 440 system to form a twin tower configuration with a SCSI bus from the main chassis. Disk Drives Full-High Half-High 355 MB 115 MB 670 MB 200 MB 3.2.11 SCSI CONVERTER (RANCHO CARD) The SCSI converter, P/N 400814-001, will convert the Single Ended SCSI Adapter to the Differential SCSI Adapter for external SCSI devices such as GCR and HCC tape drives. The converter card will be mounted in the expansion chassis. 3.2.12 UPS REQUIREMENTS FOR GPx 440 WITH THE EXPANSION CHASSIS. The main chassis, expansion chassis and a terminal can run on a single uninterruptable power supply that is provided by MBF. 3.2.6 525 MB 1/4" CARTRIDGE TAPE DRIVE The 525 MB tape drive can replace the current 120 MB 1/4" tape drive in the main chassis. Only one internal 1/4" tape drive is allowed in a system. The drive appears the same to the system as the 120 MB tape drive and uses the UNIX commands tar and cpio and the MBF utilities tsave and trestore. T 1000 ft. tape 600 ft. tape a Read Write Read Write p +----------+----------+---------+---------+ e 525 MB | Yes | Yes | Yes | Yes | |----------+----------+---------+---------| D 120 MB | No | No | Yes | Yes | r +----------+----------+---------+---------+ i 60 MB | No | No | Yes | Yes | v +----------+----------+---------+---------+ e 45 MB | No | No | No | No | +----------+----------+---------+---------+ NOTE: The 525 MB 1/4" cartridge tape drive can READ 600 ft. tapes written on the 60 MB tape drive but a 60 MB tape drive cannot read a 525 MB tape. 3.2.7 8mm HIGH CAPACITY CARTRIDGE TAPE DRIVE The 8mm tape drive will provide up to 2.3GB storage capacity for backup purposes. One external 8mm tape drive, P/N 400828-011, will be supported with the GPx 440 which requires the expansion chassis with the Rancho Card. Information can be copied to this drive by using the UNIX commands tar and cpio. 3.2.8 GCR 1/2" SCSI INTERFACE TAPE DRIVE SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg014 The primary purpose of this drive is to provide high speed backup plus data interchangeability with other systems. The GCR drive supports 6250 BPI high density recording to provide up to 240 MB tape capacity when 3600 ft. tapes are used. The GCR can also be set from the front panel for 1600 BPI format tapes. The existing MBF GCR 1/2" tape drive (Model 4405) can be field upgraded with the Differential SCSI adapter, P/N 400652-007. One external GCR drive will be supported on the GPx 440 with the Expansion Chassis and Rancho Card. The drive can be accessed with the UNIX command tar, cpio and Business Basic with READ RECORD and WRITE RECORD for data interchange. 4.0 DIAGNOSTICS Below is a matrix of the new diagnostics added to 1.0C. Diagnostic DEMON DIVE BASS ------------------------------+----------+---------- 1/2" tape x | | x ------------------------------+----------+---------- Ethernet x | | ------------------------------+----------+---------- Monitor x | | ------------------------------+----------+---------- 760 MB Disk x | x | x ------------------------------+----------+---------- 5 1/4" Floppy x | | x ------------------------------+----------+---------- Monitor as Console x | x | ------------------------------+----------+---------- Boot/Reboot x | | Functionality | | ------------------------------+----------+---------- Multiple SCSI x | x | x Controllers | | ------------------------------+----------+---------- 4 16-ways x | | x ------------------------------+----------+---------- DOS Utilities | | x ------------------------------+----------+---------- 4309 and 4312 | | x ------------------------------+----------+---------- 4.1 DEMON DIAGNOSTICS Ethernet diagnostics test the D-Link controller, the functionality of the card and the ability to communicate to the host system. Monitor diagnostics test for the monitor controller card. Monitor as console tests will sense the presence of the monitor when the system is booted. If found, the DEMON screen will be displayed on the monitor. Boot/Reboot Functionality allows the user at a remote site (remote diagnostics) to shutdown and reboot any kernel from tape or from the hard disk. Multiple SCSI controller tests will provide the ability to test supported SCSI peripherals on the controllers. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg015 4.2 DIVE DIAGNOSTICS Monitor as console senses the presence of the monitor on the system. If the monitor is connected the DIVE logon screen will be displayed on the monitor. DIVE provides formatting and disk operation for the 670 MB disk drive. 4.3 BASS DIAGNOSTICS DOS Utilities tests are available and require a non-write protected floppy. 4309 and 4312 terminals can be tested with BASS. NOTE: BASS will NOT run on the VGA monitor with the PC keyboard. The VGA is not a BFS device and is not supported in BASIC. 4.4 SECURITY VIOLATION PANIC ANALYSIS If a security violation PANIC occurs on the GPx 40 series, a number of dashes (---) will display above the 'SECURITY VIOLATION' message. This number of dashes will determine the cause of the PANIC. Security violation PANICS will NOT write to tape. Dashes Cause ----------------------------------------------------------------- 1 /etc/scr files is missing 2-7 /etc/scr file is corrupted 8 cannot access keyring 9 SSN in keyring does not match /etc/scr file 10 model type in keyring does not match /etc/scr file 11 saved value of SSN in memory has changed 12 saved SCR in memory has changed ----------------------------------------------------------------- SSN = System Serial Number, SCR = System Configuration Record 1 through 7 dashes indicate a problem in the SCR, a new SCR must be installed. 8 dashes indicate a problem in the keyring. A new keyring or keyring cable should be installed. 9 dashes indicate a mismatch in SSN between the keyring and SCR. Perhaps the keyring has been programmed for the wrong SSN, or the wrong SCR was installed on the system. 10 dashes indicate the Model Number (type) in the keyring does not match the SCR. Perhaps the keyring has been programmed for the wrong model number, or the wrong SCR was installed on the system. 11 or 12 dashes may only occur after the system has been running for a period of time. Either one could indicate a problem in system memory. 5.0 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg016 The following are steps to install or upgrade the BOSS/VX Operating System. Before installing or upgrading the system it is recommended that you read these instructions completely. 5.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all files that exist on your system. It first creates partitions on the fixed disk, makes the file system according to default or user input specifications, and then installs the standard BOSS/VX software (BOSS/VX, Business BASIC, and system utilities) on your system. WARNING: Installation of the Operating System will destroy any installed software on the system. If you are doing an OS installation on a system that already contains customer data, ensure you have a verified backup of the data. This backup should not contain any OS files. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record NOTE: During Step 4 you will be required to answer questions pertaining to the system disk partitioning. This information should be decided before the start of the installation, as changing these values will require a re-install of the OS. For information on partitioning see Section 5.1.1. STEP 1: If the system is powered down, power up the system. During the system self-test put the tape containing the BASE system in the tape drive. If the system is already powered up, . ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a , if not answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed STEP 3: Enter option 'f' to do a full installation. A warning message telling you that a full installation will destroy all files on the system will be displayed. You will. then be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', to exit the installation procedure. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg017 STEP 4: System disk information will now be displayed, including the default system disk partitioning, followed by the prompt: Is this allocation acceptable to you (y/n)? If you answer 'y',, to this prompt, the default partition will be used to partition your system disk. If you answer 'n' to this prompt, you will next be prompted with: Do you wish to have separate root and usr filesystems (y/n)? If you answer 'y', to this question your system will contain a root partition and a separate usr partition. Answering 'n',, will put both the root and usr in the same partition. You will next be prompted with the question: Do you want an additional /usr2 filesystem (y/n)? If you answer 'y', to this question a separate usr2 partition will be created on your system disk during the installation. With an 'n',, answer to this question the usr2 partition will not be created. Next, a message will be displayed showing approximately how many bytes a cylinder contains on your disk. You will then be asked: How many cylinders would you like for swap/paging? The minimum size this partition can be is 16Mb. Enter the . number of cylinders you wish the swap/paging partition to be, followed by a . You will next be prompted for the size you wish for the rest of the partitions to be created. After you give the size for each partition, you will be again asked if the allocation is acceptable. An answer of 'n',, will take you back to the beginning of this step. STEP 5: After you have answered 'y' to the allocation question, messages will be displayed indicating that the file systems are being made. After the file systems are made, the BOSS/VX software will be installed with the name of the files displayed as they are copied to disk. STEP 6: After the BASE system is installed, the Date and Time are displayed. You will be prompted with: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y',, anda list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg018 Answer the question as it pertains to your time zone. STEP 7: You will next be asked if the Date and Time are correct. If they are correct, answer 'y',; otherwise, answer 'n',, and you will be prompted with the questions to set the Date and Time correctly. STEP 8: You will next be asked to enter the password for the rootor super-user. You will be asked for this password twice. Be sure that you remember this password, as it will be required when you wish to login as root. STEP 9: The next step is to install the System's Configuration Record. You will be prompted with: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you wish to install this configuration record? Enter 'y',, to install the configuration record. If you enter 'n',, the configuration record will not be installed and you will be returned to the BOSS/VX SOFTWARE INSTALLATION menu. NOTE: You must install a configuration for your system to boot. If you entered 'n',, in the above step, see Section 1.3 "Installation/Upgrade of the Security Configuration Record" to install the configuration record. STEP 10: After the configuration record is installed the installation of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r',, to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 5.4 "Installation and Up of Optional Software Packages" NOTE: Step 11 is for systems 240/340/440's with a VGA monitor. It is necessary to have a terminal on COM1 because utilities such as 'configure' and 'oprinfo' are not legible on the VGA STEP 11: After the system has rebooted, logon to the terminal connected to COM1 (SERIAL2, the 9 pin port) by entering: install You will be asked to enter a password, enter: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg019 chngt0 Then enter it again. Use this password on all 240/340/440's with VGA monitors. Enter: su Enter: init S The system will go into single-user mode and the terminal will now be the system console. We made a terminal the system console because MBF utilities do not display correctly on monitors. At this point you will be able to run configure and oprinfo. After configuring all the ports and creating operators, shutdown down the system and reboot. Enter: init 0 The system will do a complete shutdown and will come up with all the ports configured and the VGA monitor will again be the system console. 5.1.1 SYSTEM DISK PARTITIONING The BOSS/VX installation procedure will allow you to define one, two or three partitions containing a file system on the system disk. The swap/paging partition will automatically be on the system disk, but doesn't contain a file system. You will be required in Step 4 of the BOSS/VX installation procedure to provide information on the number and size of the partitions you wish defined. Before starting an installation, you should have this information. To change this after an OS installation will require backing up the customer's data an doing a complete reinstallation of the OS The following are different partition options that are available during the installation: 1 partition: root and usr together on the same partition, no usr2 partition. (not recommended) 2 partitions: separate root and usr partition, no usr2 partition. 2 partitions: root/usr partition together and a separate usr2 partition. 3 partitions: separate root, usr and usr2 partitions. During the installation procedure, commands and files required when the system is in single user mode will be installed to the root partition. While in single user mode, the root is the only partition automatically mounted. These commands will allow you to repair or work with one of the other partitions if they are damaged. During the installation procedure, the rest of the standard BOSS/VX software will be installed on the usr partition, if you specified you wanted a separate root and usr partition. Otherwise, the rest of the standard BOSS/VX software will be installed in a directory called '/usr', on the root partition. The OS doesn't put any commands, programs or files SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg020 automatically into the usr2 partition if it is defined. At the minimum it is recommended that you define your system disk with a separate root and usr partition. In this case if a problem occurs on the usr partition, (the partition where the customer's data is located), the system can be booted into single user mode and the usr partition can be worked with from the root partition. If you wish to put the customer's programs and data files on a separate partition or wish to have a separate partition that can be easily unmounted for security reasons, then the usr2 partition should be defined. Following is the approximate amount of disk space in Mega Bytes by package for the root and usr partitions: Package root usr BASE* 4.3MB 15MB UTERM 2.8MB MANPAGES** 3.3MB ITP .9MB PS 3.5MB For ADS, DSS and OTU see Section 5.5.2.1 * BASE = BASE and UNIX (UNIX is under /usr only) ** MANPAGES = MBFMAN and UMAN NOTE: The amount of disk space required for the above may grow in future releases. 5.2 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the original ones. WARNING: Before attempting any update, it is recommended that you have a verified backup of the customer's data. Ensure that this balckup doesn't contain any of the OS files. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record (if you wish to re-install the configuration record) STEP 1: If the system is powered down, power up the system. During the system self-test, put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg021 Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a . If not, answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. STEP 3: Enter option 'u', to do an update installation. Messages telling you that the file systems are being checked will be displayed. The file systems must not contain errors for the update to continue. Next, messages telling you the BASE system package is being searched for, followed by a message telling you the BOSS/VX software will be installed, are displayed. This is followed by the OS files being installed, with the names of files displayed as they are installed. STEP 4: After the OS files have been installed you will be given the option to install the OS files that the user can modify. STEP 5: Next the Date and Time are displayed. You will be prompted with: 6 Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to the change time zone answer 'y',, anda list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone, you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. STEP 6: You will next be prompted with: Install the configuration record (y/n)? If you don't want to install the configuration enter 'n',. The update is now complete. Remove the BASE system tape and enter 'r', to reboot the system. STEP 7: If you wish to install the configuration record, enter 'y', and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg022 If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. Do you want to install this configuration record? STEP 8: After the configuration record is installed, the update of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 5.4 "Installation and Update of Optional Software Packages". NOTE: Step 9 is for systems 240/340/440's with a VGA monitor. It is necessary to have a terminal on COM1 because utilities such as 'configure' and 'oprinfo' are not legible on the VGA. STEP 9: After the system has rebooted, logon to the terminal connected to COM1 (SERIAL2, the 9 pin port) by entering: install You will be asked to enter a password, enter: chngt0 Then enter it again. Use this password on all 240/340/440's with VGA monitors. Enter: su Enter: init S The system will go into single-user mode and the terminal will now be the system console. We made a terminal the system console because MBF utilities do not display correctly on monitors. At this point you will be able to run configure and oprinfo. After configuring all the ports and creating operators, shutdown down the system and reboot. Enter: init 0 The system will do a complete shutdown and will come up with all the ports configured and the VGA monitor will again be the system console. 5.3 INSTALLATION/UPDATE OF THE CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration . record on a system that doesn't already have one or overwrites the one already on the system. It will display the configuration record before installing it and give the option to install it or go back to the menu. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg023 The following will be required to install the Configuration Record: o BASE Operating System tape o Configuration Record tape STEP 1: If the system is powered down, power up the system. During the system self-test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y', followed by a . If not, answer 'n', The BOSS/VX SOFTWARE INSTALLATION menu will now be displa yed. STEP 3: Enter option 'i', to install the configuration record The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the configuration record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record? If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. STEP 4: After the configuration record is installed you will be prompted with: Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r',, to reboot the system. The installation of the configuration record is now complete. If a monitor is being installed on the system refer to Section 5.1, Step 11 for O/S installations and Section 5.2, Step 9 for O/S updates. 5.4 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES AND DIAGNOSTICS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg024 The following steps outline the procedure to install optional BOSS/VX packages, for example; BASS, DEMON, ITP, MAI OFFICE, TBC, Presentation Services, tools, ORIGIN and other packages supplied in a BOSS/6VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified backup of the customer's data files before attempting the update. The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. STEP 1: If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. STEP 2: Shut the system down to single user mode by using the command 'shutdown -i1'. Do you want to continue (y/n)? enter 'y' When prompted for the password use your root password. Enter terminal type (default is TERM=dt4313) TERM= or terminal type. STEP 3: At the command mode prompt enter the command mbfinstall . The following messages will be displayed: WARNING: This program should only be executed in single-user mode press to continue. Installing products on / Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. If it is not mounted, type 'mountall' to mount it. STEP 4: Insert the tape containing the package(s) you wish to install in the tape drive and enter . The BASE system tape will display a message that the tapeis SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg025 an operating system tape. The Diagnostic tape message will display that it is a Diagnostic tape. Either are followed by a prompt to continue. Enter . Messages will be displayed telling you the procedure is skipping the product(s) not to be installed. Next, the MBF Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. STEP 5: Enter the number of the package you wish to install followed by a . You can enter them in any order. The procedure will put them in the order they are found on the tape. After you enter a number you will be prompted with: Install product(s) number Are you sure (y/n)? If you answer 'y',, to this question, the number willbe added to the list and you will be returned to the menu. If you answer 'n',, the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, . If you wish to abort the procedure and go back to command mode enter 'ab', . STEP 6: After you have entered the number of all the products you want to install, enter 's',. The procedure will display. the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. STEP 7: If a public id is required a message displaying the current public id and its length will be displayed after the package is installed, followed by: ENTER an 8-character new Public ID (Hit <0> for a Null Public ID or for no change): Enter the public id you received with the package if it is different than the one displayed. STEP 8: If you are installing more than one package, the next package will be installed. This will continue until all the packages you selected have been installed. After all the packages are installed, the procedure will take you back to command mode. You are now done with the installation of your package(s) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg026 If you wish to install additional package(s) from other tape(s) repeat this procedure to install them. STEP 9: Enter ^d and 2 to return to multi-user mode or ^d and 0 to shut the system down. NOTE: After installing TBC the system must be shutdown using ^d and 0' and then powered off and on so the system will recognize the ICC186 board. 5.5 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES The following sections include special instructions or installation procedures when installing the optional software packages. 5.5.1 MAI PRESENTATION SERVICESTM There are no special instructions for installation and customization of Presentation Services. Ensure the user's Path includes the following to access Presentation Services: /usr/mbf/PS /usr/mbf/PS/tools 5.5.1.1 PRESENTATION SERVICES CUSTOM MENUS If the user has created their own menus through PS MENUBUILDER for either their own applications or OFFICE and ORIGIN, they need to transfer those files to the GPx Series 40 system using Intersystem Transport. The files to be transferred are as follows: SPx names would be: ../PS/MSMF and ../PS/MSSF-->MENUFILES ../PS/MSH1 and ../PS/MSH2-->HELPFILES MPx names would be: .PS.MSMF and .PS.MSSF .PS.MSH1 and .PS.MSH2 5.5.1.2 PRESENTATION SERVICES FORMS When transferring forms to the GPx system, port only the source form files. Do not port the compiled form file. You will need to recompile your forms once you get them on the destination system. If the user has created their own forms through PS FORMSBUILDER, they need to transfer the following using Intersystem Transport. SPx: /PS/FS1.ENG /PS/FS2.ENG /PS/FS3.ENG /PS/FS4.ENG MPx: .PS.FS1.ENG SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg027 .PS.FS2.ENG .PS.FS3.ENG .PS.FS4.ENG All programs created and associated files must also be transferred. Programs will need to be modified to use only BB90 directives. Bring the files over using cread but do not perform the conversion during porting. Then run BQR to convert the files. After this is done, run MKCONVERT. 5.5.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities *********************************************************************** * WARNING * * * * o PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING * * * * THIS PRODUCT. * * * * * * o Your system should be in single user mode. This ensures a safe * * product installation without conflicts with active system users. * * * * o You must be logged on as 'root'. This will avoid security * * conflicts during the product installation. * * * * o Make a full backup of your product (programs & files) * * before installing this new version. * * * * o The following Path names used are examples only and will change * * if you install the packages into a directory other than '/usr'. * *********************************************************************** NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 5.5.2.1 INSTALLATION REQUIREMENTS: New installations: o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.0A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: ADS or DSS or (ADS + DSS): 8.16 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg028 Updating: o The same requirements for a new installation, plus the following: o You must port all of your current ORIGIN data files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). WARNING: The only way to keep separate directo{ries is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 5.5.1 Presentation Services. ******************************************************************* * * * Make a full backup of all ORIGIN program and data files, * * currently located at '/usr/origin/r21b and the directories in * * which your *DC0 files are located BEFORE installing this * * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix or directory * * * ******************************************************************* NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 5.5.3.1 for MPx and Section 5.5.3.2 for SPx. 5.5.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.4. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg029 During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, MB-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appears) SECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY> You may now go to step 6 or quit and shutdown before rebooting system. 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg030 cd /usr/origin/r21b/language rm * 5.5.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B, the program UPDATE does NOT have to be executed. 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 5.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.4. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), for (a default will appear) For example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 5.5.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. NOTE: Use the 'chmod' command to change the file usage rights on all files ported to the GPx from another system. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.5.2.4 UPDATING FROM 2.0A 1. Restore all files from tape following the directions for Installation of Optional Software SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg031 Packages under Section 5.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.4. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on the root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT: This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files. E. INSTALL STAND ALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg032 Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.5.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 5.5.2.4, "Installations Updating from 2.0A". 5.5.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg033 >start 256 >PREFIX "/usr/origin /usr/origin/r21b /usr/mbf/PS /usr/mbf/PS/tools" >RUN "ORIGIN" NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. 3. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. _____ Select User Maintenance, use the password "ADMIN". 4. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities. The password is ADMIN. _____ Select ORIGIN System Parameters Maintenance option. _____ Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this directory is "/usr/origin/work/". 5.5.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 5.5.3.1 MPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done.For information on how to convert to 2.0A, please refer to Section 5.5.2.5. 2. Perform a verified backup of the ORIGIN system. 3. Using the DIRectory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. For example: .USR.ORIGIN.JKSF01 -> data file .USR.ORIGIN.JKSF02 -> data file SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg034 .USR.ORIGIN.JKSFM2 -> Application Generated Program .USR.ORIGIN.JKSFM1 -> Application Generated Program .USR.ORIGIN.JKSR01 -> Report Generated Program .USR.ORIGIN.JKSR02 -> Report Generated Program .USR.ORIGIN.xxxDC0 -> Technical Documentation File .ORIGIN.R20A.DATA.IDD000 -> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with ID Dxxx and reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From command mode, execute MCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 5.5.3.2 SPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 5.5.2.5. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 -> data file /usr/origin/JKSF02 -> data file /usr/origin/JKSFM2 -> Application Generated Program /usr/origin/JKSFM1 -> Application Generated Program /usr/origin/JKSR01 -> Report Generated Program /usr/origin/JKSR02 -> Report Generated Program /usr/origin/xxxDC0 -> Technical Documentation File /origin/r20a/data/IDD000 -> Integrated Data SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg035 Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Using cwrite utility, write BQR filelist to tape. 5. Restore Intersystem tape on GPx machine using cread utility. Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 5.5.4 ORIGIN 2.1B NEW FEATURES o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re-generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity be tween the 're-generated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 5.5.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg036 -and- /pgm/SPA004 - ORIGIN message file in foreign language (*) /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language * SPA will be used as the language code in this document o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. MESSAGE TRANSLATION o Set your prefix to work with ORIGIN 2.1B and perform the following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilitie s -> -> Password (ADMIN) -> Language Translation Menu -> Languages -> Maintain Languages -> Enter the language code -> -> Done, you may go to console mode at this point. o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file, to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) o Using with system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program director (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg037 . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily modified from 2.1A to 2.1B, so a re-translation of this program is recommended: . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until translation is complete. 5.5.6 DOCUMENTATION Manual Number Part Number Pages Title _ M7511E 007511-012A 170 MAI Business DATATM Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATATM Technical Reference M0058C 910058-002 132 MAI ORIGINTM User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGINTM Application Generator User Guide M7512D 007512-002 112 MAI ORIGINTM Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATATM System Support Manual M7557G 007557-011 74 MAI Business DATATM User Guide M7561E 007561-002A 166 Presentation Services Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg038 Forms Management User Guide 6.0 COMMUNICATION PACKAGES 6.1 27xx/37xx BATCH EMULATION 6.1.1 SOFTWARE REQUIREMENTS AND INSTALLATION - Package Installation: The package requires a minimun of 2296 disk blocks on the /usr partition for the programs. The files will reside in the /usr/mbf/comm, /usr/mbf/magnet, /usr/mbf/tbc and /usr/mbf/etc directories. There are approximately 176 disk blocks required for each data directory defined by the user. - You may configure up to 4 ports on the GPx 40 for TBC, but only two communication sessions may run at the same time. If two sessions are run simultaneously, they may only be run at 4800 bps. If more than two sessions are attempted at the same time an error -615 will occur. - TBC requires a security key to operate. 1. Installation of this package is done using the 'mbfinstall' utility. 2. The name used to select the installation of this package is 'TBC'. 3. A prompt to enter the software key will be given after the files have been restored. If the key is not entered at that time, the command: 'install_key TBC' can be used to install the key. The key must be entered in upper case. - Port Configuration: The 'configure' utility has been modified to include communication devices. Option '9' is used to configure communication devices. There are 4 ports available per controller (0-3). When you add a device, select 'tbc' as the protocol and any I-device group from IA to IZ. NOTE: You must be in Single User mode to install this package and configure the communication devices. After the install you must enter CTRL D and 0 to shutdown the system. Power the system down and re-boot. 6.1.2. HARDWARE REQUIREMENTS AND INSTALLATION - Although it is not required, it may be necessary to increase system memory to keep system performance at an acceptable level. The determination of this should be based on individual system load parameters. - ICC186 Part number: The part number for the controller is 916593-001. NOTE: There are 4 ports on one controller which are paired and driven by 2 sync chip drivers. This can be useful for SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg039 troubleshooting purposes. - Cable Part number: The part number for the controller multi-modem cable is 400694-003, the extender cable part number is 907753 with a dash number to indicate length. A connector gender adapter part number 300118-001 is required if the extender cable is used. NOTE: The one multi-modem cable has connections for up to 4 synchronous modems. - Board installation: The Board may be installed in any 16 bit slot available on the GPx CMB. - Switch settings: The following table contains the required controller switch settings: ___________________________________________________________ | JUMPER SETTING | DESCRIPTION | |-----------------------------|---------------------------| | JB1 | Interrupt Request Line 10 | | O O O O O |X| O O | | | 1 O O O O |X| O O | | |-----------------------------|---------------------------| | JB2 | Ports 0-3 connected as DTE|. | O O |X| |X| | (For normal operation and | | 1 O |X| |X| | all tests except the Loop| |-----------------------------| test. For the Loop test, | | JB3 | all jumpers MUST be | | |X| O O |X| | removed. All DEMON test | | |1| O O |X| | may run with these | | | jumpers removed. | |-----------------------------|---------------------------| | JB4 | Shared memory starts at | | |X| O |X| O |X| |X| | A0000h | | |X| |X| |X| |X| |X| |X| | | | O |X| O |X| O 1 | | |-----------------------------|---------------------------| | JB6 JB7 | Shared Memory size 64KB | | O |X| | | | O |X| | | |_____________________________|___________________________| | SW1 | | | | I/O Address of 240H| | 1 2 3 4 5 6 7 8 9 10 | | | OFF ON ON OFF ON ON ON ON OFF OFF | | |____________________________________|____________________| |X| = Jumper installed O = Jumper not installed 6.1.3 GENERAL INFORMATION - Operation 1. The 27xx/37xx Batch Emulation package may be accessed through the Utility menu and selecting the 'communications' option or by setting the user prefix list to '/usr/mbf/tbc' and then running "BCOM" from BASIC. No start size is required. The program "SBCOM" is also supported. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg040 2. The TBC session menu on the GPx family of products has been changed so that option 1 is now called "TRANSMISSION DEFINITION" and not "TERMINAL DEFINITION" as on previous products. 3. The 'CONTROLLER/PORT' option under 'TRANSMISSION DEFINITION' selection expects numerics from 0 to 3. 4. There are two new entries to the file '/etc/rc2.d/S20sysetup' that performs the necessary operations to load the TBC kcontroller and start the process '/* MAGNET RSM */' for use with TBC. The file is installed with these entries with the installation of the TB|C package and is executed during boot. The two new entries are "/usr/mbf/magnet/netinit" (starts the MAGNET RSM process) and "/usr/mbf/comm/commload-b0" (loads the TBC board 0 ). If you are not using TBC, you may want to remove these entries from the '/etc/rc2.d/S20sysetup' file so that errors due to missing hardware and non configured devices will not be displayed during boot. 5. At system load time, a message 'resetting ISCC board number 0' will be displayed. 'ICC 186 sync. comm. board - rom version 20' will be displayed during the system hardware self tests at load time. 6. A complete system shutdown (power off) and startup should be done after the software and hardware have been installed and configured for the first time. You may see errors during the load process indicating 'error' resetting controller '0' if this is not done. 7. Run "BCOMPFX" the first time communications is installed on the system. 8. The software supports a serial interface autodialer and will require a dedicated terminal port per autodialer. The Ark2400 Plus Modem (Paradyne) and UDS 801 A/C Direct Connect Automatic Calling Unit with RS-232 input are both supported. The ARK DM424 modems only contain a synchronous port and will require a dedicated external autodialer to work with TBC. The terminal port should be configured as: Device type: terminal Terminal type: other There should be no start process and the baud rate, parity and character length should match that of the setting for. the modem. the default settings are used for the remaining fields. A serial modem cable is required (P/N 916073) for the ACU. - Diagnostics 1. A synchronous modem eliminator may be used to test the software and controller since there are 4 ports available 2. DEMON has been updated to include tests for the ICC186 controller. 3. A loopback connector number 905718-001 is available for SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg041 DEMON loopback testing. 7.0 NOTES AND CAUTIONS WARNING: After upgrading to 1.0C you MUST delete /usr/mbf/etc/_queues/lpq.que, the printer queue file. The format has changed from previous levels. WARNING: The 1/2" MTS tape drive does NOT detect the End-of-Tape mark when writing to the tape with BASIC, tar or cpio. This will be fixed in 1.0D. WARNING: If /etc/bfsdevs is installed during an O/S upgrade the port configuration will be corrupted. To fix the corruption go into the configure utility and perform a Save and Exit. WARNING: After upgrading to 1.0C the internal MODEM port settings may change, so check the port configuration for the internal MODEM in configure. WARNING: 'pqueue' will display a status of 'unknown' instead of 'formchange' when waiting for a form change. WARNING: After upgrading to 1.0C you may should do a chmod 777 /tmp because non-root operators will not be able to logon. WARNING: DO NOT configure ports for 38.4K baud rate. This can cause the system to hang. WARNING: The PT-4220 serial printer defaults are set incorrectly in the configure utility. The defaults should be: Baud: 9600 Data Bits: 7 Stop Bits: 1 Parity: Odd The PT-4220 serial printer should also have 'despool wait' set to 'yes'. WARNING: The mnemonics for START BOLD and END BOLD are not supported on the PT-4220 serial printer. PROBLEM: Error 31's in CALLed programs. If a CALLed program has an ENTER A$ and within the program A$ is set reassigned A$=A$+B$ then an error 31 is possible. Workaround: After the ENTER A$, set A$ equal to another variable and use that variable throughout the CALLed program, eg. B$. Then before EXITing set A$=B$. WARNING: It is possible to have 2 printers named LP. If a serial printer is named LP and a parallel printer is added it can ONLY be LP. The result will be 2 printers being named LP. WARNING: When installing WordPerfect, a prompt askes for 'Y/N'. The only input accepted in 'y'. NOTE: The message 'Press CTRL+C or ESCAPE' is missing from the BOSS/VX login screen. NOTE: DEMON cannot recover from a media error on the 8mm tape drive. This will be fixed in 1.1A NOTE: All files being transported to a 1.0C system, with cread, will have SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg042 their permissions set to rw-rw-rw-, regardless of the permissions that existed on the previous system. NOTE: DT-4314 terminals configured as a DT-4313 will NOT take advantage of software capabilities designed for the DT-4314, such as boxes. NOTE: The UNIX Package on the Operating System tape is now included in the Base portion of the O/S and will not be necessary to be installed to run UNIX packages. NOTE: To convert the number of blocks into number of MB do the following equation: (# blocks * 512)/1,048,576. Example: 8670 blocks * 512 / 1,048,576 = 4.23 MB 7.1 ATP NOTES AND CAUTIONS: A. A BASIC program being transferred with ATP from a GPx to a 1500 system will error on multi-line statements in BASIC. Workaround: Edit the BASIC program on the 1500 after the transfer. B. When using ATP over a modem between an SPx and a GPx, the SPx side must start communications first. C. A STRING file with certain unprintable characters, between $00$ and $1F$, could corrupt when transferred with ATP from a BOSS/VX system to a BOSS/IX system. Change the following programs on the BOSS/IX system: /util/ARP 4205 IF F4<>7 THEN GOTO 4210 ELSE LET R9=0; IF S1=1 THEN WRITERECORD(6,TBL=6900,ERR=4500)R0$(3,S9-2) ELSE WRITERECORD(6,ERR=4500)R0$(3,S9-2) /util/ATP1 5135 IF F4=7 THEN LET R9=0; READRECORD(6,ERR=6000,END=5700)X9$; GOTO 5150 D. ATP cannot be started on 2 terminals at 1 time. E. Using ATP to transfer a string file to a system that does not support string files will cause the BOSS/VX system to skip the string file and the destination system to report "Invalid receive file type". F. STRING files will be changed to SERIAL files on a BOSS/VS system with M.6G Operating system or higher G. Using ATP to attempt to transfer Multi-keyed files to a system that does not support MK files will cause the MK file and the following file to be skipped. H. Because SERIAL files are not supported on the MAI-1500, they will be skipped when attempting to use ATP to transfer them to the MAI-1500. I. Avoid giving BQR filelists similar names. If the first 3 characters are similar BQR may become confused and delete some of the BQR filelist names. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg043 7.2 PC-Link Notes and Cautions: A. PC-Link does NOT support slave printing on the GPx 40, because PC-Link requires an MBF interface. Slave printing will be available on a future release of PC-Link. B. Use BOSS/IX as the system type when running PC-Link on a BOSS/VX system. C. The PC-Link file transfer programs on the GPx 40 must be in UPPERCASE. D. To use "vi" via PC-Link require that the terminal configuration be at least a DT-4309. The operator can set the terminal by using the following steps: TERM=4309 export TERM E. CTRL+S will hang the PC port when running PC-Link over a modem. To resume operation, hang-up the modem and redial. F. Pressing at the "$" prompt will hang the PC for 30 seconds. 7.3 TBC NOTES AND CAUTIONS: A. TBC should not be run with less than 8 MB of memory, when running with 4MB of memory a BASIC qcode error is reported. B. Do NOT create a /debug directory, if TBC sees that directory it will create files which may fill the /root partition. C. ESCAPE during a TBC communication may hang the ICC186 controller, if an ESCAPE or something else causes a hang the following steps will free it: cd /usr/mbf/comm ./commload -b0 If the controller remains hung the system must be shutdown and powered off and on to free the controller. D. If MAGNET is stopped by removing the RSM process, TBC will also stop running. E. TBC may report an error 26 during a file transfer in transparent mode from GPx to MPx or SPx. The following programs changes will prevent this: MPx: .PGMTBC.BRCV 1455 IF T2=1 THEN A9=0; GOTO 1513 SPx: /tbc/BCOM/BRCV 1456 IF T2=1 THEN GOTO 1525 F. TBC supports only 1 port communicating at 9600 baud. If 2 TBC ports are running simultaneously they must communicate at 4800 bps. G. Data in received files should be verified if an Auto-Restart or RVI occurred during a BCOM session. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg044 H. A premature termination of a TBC session may be caused by a "TIMEOUT TERMINATION" occurring without waiting for the length of time specified in the TIMEOUT value. I. If a remote system fails because of a dump or power failure or some other catastrophic failure the local system may terminate communication by hitting . J. Device T000 should be removed from the /etc/bfsdevs file because it can cause screen display problems in BCOM. K. If a BASIC program is in a BQR filelist that is to be transmitted by TBC, an error 67 and "sh: checksum : not found" will occur. L. The ITP product must be installed with "mbfinstall" if the user wants to use BQR utilities to create TBC transmit queues. M. BASIC error 59 with a system error -657 is occurs when attempting to open a TBC comm port and the incorrect TBC public key is installed. N. The full path name must be entered for the destination file when modifying the TBC Transmit Queue for File Transfer. O. TBC may report a BASIC error 95 with a system error -614 and a message "unknown I-Device open error", this is caused by insufficient disk space. P. When the LSLOG is full, the LSLOG program may go into an infinite loop to locate the last TBC session. Q. The termination sequence ETX/DLE-EOT, which is normal for non-MBF TBC is treated as abnormal by MBF TBC. 8.0 RELATED DOCUMENTATION Manual Number Title _ _ M8215A GPxTM Series 40 Installation and Maintenance Manual M8215B GPxTM Series 40 Installation and Maintenance Manual Addendum Package M8224A GPxTM 240 Installation and Maintenance Manual M8224B GPxTM 240 Installation and Maintenance Manual Addendum Package M0186A GPxTM Series 40 Software Installation and Configuration Manual M0187A BOSS/VXTM System Administrator Guide M0188A BOSS/VXTM Reference Manual M1089A BOSS/VXTM User Guide M0190 BOSS/VXTM Diagnostics Manual M0205A BOSS/VXTM Transportable Batch Communications SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg045 (27xx/37xx) User Guide M0228A BFSINT Reference Manual ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB004 Pg046 FIB 00005 09/28/90 *** GPx40 1.0D Software Announcement [ WPSS 184 ] *** 1.0 Introduction Level 1.0D of BOSS/VX for the GPx Series 40 is now available. It is the recommended Operating System for the GPx 240, GPx 340 and GPx 440. The 1.0D Operating System is derived from the 1.0C O/S, and contains PS Forms 3.3B, 2 tape related corrections and is the carrier for 1/2" tape drives (MTS and GCR). This Software Announcement contains general information about the 1.0D BOSS/VX Operating System. Installation and update procedures can be found in the GPx 40 1.0C Software Announcement, #182. It is recommended that you read this document and the GPx 40 1.0C Software Announcement, #182 before installing Level 1.0D. For information on ordering 1.0D refer to Marketing Announcement 896 US/C for the United States or 561 I for International. WARNING: The performance for GPx 2/3/440s with 4MB and 8MB of memory running 1.0C and 1.0D is not as high as on prior operating system releases such as BOSS/VX 1.0A/B. This is because additional software functionality added to 1.0C has increased the size of memory required for the operating system. Because of this increase, the performance on the 4MB and 8MB systems may be impacted. We recommend that when upgrading to BOSS/VX 1.0D from 1.0A or 1.0B that 4MB of memory be added to all systems presently configured with 4MB or 8MB of memory. This is particularly important for those systems which are presently configured near the top-end of the recommended concurrent user range or those systems pushing the limit of acceptable response time. Additional memory where needed to maintain performance must be purchased by the customer at their own expense. On the GPx 240, the response time with eight concurrent users will be slower than with BOSS/VX 1.0B, but still less than four seconds. WARNING: If you are replacing the Mother Board on a GPx 440 with part 916556-004, the system MUST be on 1.0B or greater or the system will not boot due to a security PANIC. TABLE OF CONTENTS 1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . .Cover 2.0 BOSS/VX Operating System History. . . . . . . . . . . . . . . . .1 3.0 New Products in Level 1.0D. . . . . . . . . . . . . . . . . . . .1 3.1 New Software Products. . . . . . . . . . . . . . . . . . . .1 3.1.1 PS 3.3B . . . . . . . . . . . . . . . . . . . . . . .1 3.2 New Hardware Products. . . . . . . . . . . . . . . . . . . .2 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg001 3.2.1 1/2" MTS Tape Drive with SCSI Interface . . . . . . .2 3.2.2 1/2" GCR Tape Drive with SCSI Interface . . . . . . .5 3.2.3 GPx 40 Expansion Chassis. . . . . . . . . . . . . . .6 3.2.4 SCSI Converter (Rancho Card). . . . . . . . . . . . .6 3.2.5 UPS Requirements for GPx 40 with Expansion Chassis. .6 4.0 Notes and Cautions. . . . . . . . . . . . . . . . . . . . . . . .7 5.0 Related Documentation . . . . . . . . . . . . . . . . . . . . . .9 1.0D GPx 40 Software Announcement 2.0 BOSS/VX Operating System History 1.0A First release of BOSS/VX. It was required for the GPx 340 and 440. 1.0B This release introduced the GPx 240 and 27xx/37xx Communication and is needed if mother board part number 916556-004 is installed in a GPx 440. This mother board will cause a PANIC if installed with 1.0A. 1.0C This release introduced the 1/2" MTS tape drive, VGA monitor, Ethernet controller, 670 MB disk drive, support of up to 64 users, DOS Read/Write capabilities, PT-4220 serial printer, Slave printing on the DT-4312, TERMCAPS and TERMINFO files on the DT-4312 and DT-4309, displaying dashes when Security Violation PANICS occur and the addition of lphold, printversion and bbmap commands. There were a number of bug fixes/enhancements including automatic shutdown when the UPS becomes active, the spooler will only reprint the page it failed on rather than restart at the beginning of the print job when there are form feeds in the application and changes to oprinfo. 3.0 New Products In Level 1.0D This section contains information on products that are new for Level 1.0D 3.1 New Software Products 3.1.1 PS 3.3B PS Forms Management 3.3B, an enhanced version of its predecessor, PS Forms Management 3.3A, adds flexibility and creativity to designing user-friendly applications. Existing BASIC applications can easily incorporate PS Forms Management functionality with the aid of one new feature, ROOTWINDOW. Some of the highlights of the 3.3B release are: o Allow Gradual Conversion of Applications to Forms o Modified REFRESH Mnemonic o 'START' at Last Field in IOLIST o 'RB' on Message Mnemonic o Multiple Configuration Files o Modified Required Field Validation o Addition of Color o Increased Performance in Menus and Repeating Groups o More than 999 Help ID's The following are fixes that were made to the PS 3.3B release: o Allows backspace to left of field SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg002 o Form display problem corrected on the 7270 terminals o Help text incorrectly displayed function key eight instead of ACCEPT o With no styles defined, NEXT key displays data o Error 14 in BUILDCONF if bad family name entered o Insert mode not allowed on masked fields with only ALX# o Function keys should default to same color as form o Error 43 at line 1430 in FBMKFORMAT o Incorrect path in UPGRADE program o Error 14 from demo menu o Edit mode displays extra character o Help for set default function keys displays form/menu function keys o Error 41 printing form o Error 41 in UPGRADE program o Error 39 in BLACKJACK if ESCape pressed o Workaround added to local field definition since BASIC time out not corrected in this release o Some words truncated in PS demo help text o Double borders not printing o Menu system security problems o Increased number of pages in list forms, list menus, list form sets, and list menu sets from 10 to 50 3.2 New Hardware Products 3.2.1 1/2" MTS Tape Drive with SCSI Adapter NOTE: The 1/2" MTS was announced in the 1.0C S/A but there was a problem that allowed the drive to write beyond the EOT mark. This has been fixed in 1.0D. The existing MBF 1/2" MTS drive (model 4402) can be field upgraded with the Single-Ended SCSI Adapter, P/N 400494-015. The drive will be supported by the UNIX utilities cpio and tar and will be supported by Business BASIC READ/WRITERECORD for data interchange. The MBF utility tsave is NOT supported. NOTE: The following information can also be found in the GPxTM Series 40 Installation and Maintenance Manual Addendum Package, #M8215C, pages 25 - 29. To install the 1/2" MTS tape with SCSI interface: The SCSI controller in the CCA should have the terminators removed RN3, RN4 and RN5 from the 1542A (long) card or RN2, RN3 and RN5 from the 1542B (short) card. On the SCSI interface controller on the rear of the MTS drive, jumper W7, the only jumper on the controller, should be removed. (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg003 Below are the switch settings for the SCSI Interface Adapter Board, Switch 210 SCSI ID SCSI ID# Switch Position +----------------------------------------------+ | 0 1 2 3 4 5 6 7 | +----------------------------------------------+ 0 | OFF OFF OFF OFF ON ON ON ON | 1 | OFF OFF ON OFF ON ON ON ON | 2 | OFF ON OFF OFF ON ON ON ON | 3 | OFF ON ON OFF ON ON ON ON | 4 | ON OFF OFF OFF ON ON ON ON | 5 * | ON OFF ON OFF ON ON ON ON | 6 | ON ON OFF OFF ON ON ON ON | 7 | ON ON ON OFF ON ON ON ON | +----------------------------------------------+ NOTE: The ON position is indicated by a Black dot on the switch. * MBF default (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg004 1/2" MTS SCSI Interface Adapter Board Switch Settings, Switch 76543210. Name Function Switch Position +-------------+---------------+---------------------------------+ | | | 0 1 2 3 4 5 6 7 |. | # of | 1* | ON ON | | available | 2 | OFF ON | | units on | 3 | ON OFF | | controller | 4 | OFF OFF | +-------------+---------------+---------------------------------+ | | | 2 3 | | | Normal * | ON ON | | | | |. | | Loop On | | | | Power Up | OFF ON | | | Routine | | | | | |. | Self-test | Loop On | |. | Features | RAM Data | ON OFF | | | Pump | |. | | | |. | | Allow | | | | Execution | | | | after | OFF OFF | | | Power Up | | | | Failure | | +-------------+---------------+---------------------------------+ | | | 4 5 | | | 880* | ON ON |. | Drive | 890/891 | OFF ON | | Models | 900 ** | ON OFF | | | 990 *** | OFF OFF |. +-------------+---------------+---------------------------------+ | | | 6 | | Parity | Enabled * | ON | | | Disabled | OFF | +-------------+---------------+---------------------------------+ | | | 7 | | | Arbitrating * | ON | | Model | Non- | OFF| | | Arbitrating | | +-------------+---------------+---------------------------------+ | NOTE: The ON position is indicated by a black dot on the | | switch. | +----------------------------------------------------------+ . * MBF default ** Up to 32-KBytes blocks--data recoverable after fatal drive error. *** Up to 64-KBytes blocks--data not recoverable after fatal drive error. 3.2.2 GCR 1/2" SCSI Interface Tape Drive The primary purpose of this drive is to provide high speed backup plus data interchangeability with non-MBF and GPxTM family systems. The GCR drive supports 6250 BPI high density recording to provide up to 240 MB tape capacity when 3600 foot tapes are used. The GCR can also be set from the front panel for 1600 BPI format tapes. The existing MBF GCR 1/2" tape drive (Model 4405) can be field upgraded with the Differential SCSI adapter, P/N 400652-007. One SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg005 external GCR drive will be supported on the GPx 440 with the Expansion Chassis and Rancho Card. The drive can be accessed with the UNIX command tar, cpio and Business BASIC with READ RECORD and WRITE RECORD for data interchange. The GPx 440 Expansion Chassis is required to connect the tape drive with cable P/N 915636-001. NOTE: The following information can also be found in the MT-4405 Tape Drive SCSI Interface Conversion Instructions, #M8219, pages 1 - 7. To the SCSI Differential Interface on the 1/2" GCR drive: The mother board in the tape drive must be removed and replaced with the SCSI interface board. The switch settings should be as follows: Switch MH07 +------------------------------------------------------------+ | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | | OFF | OFF | ON | ON | ON | OFF | ON | ON | OFF | OFF | +------------------------------------------------------------+ Switch MH11 +------------------------------------------------------------+ | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | | ON | OFF | ON | ON | OFF | OFF | ON | ON | OFF | OFF | +------------------------------------------------------------+ Reinstall the cards in the card cages as follows: o SV (existing) into Slot A1 o CS (NEW) into Slot A2 o IF (existing) into Slot A3 o WR (existing) into Slot A4 o DP (existing) into Slot A5 o RD (existing) into Slot A6 Attach the SCSI termination module to connector S2 on the motherboard. Attach the SCSI signal cable to connector S1 on the motherboard. Disconnect and remove the ribbon cables attached to the PA and PB cards and remove the PA and PB cards. Remove the old Configured End Item label and dispose of it. Fill in a new CEI label with the following information: o Volts: same as old CEI label o Hertz: same as old CEI label o Serial Number : same as old CEI label o Interface: SCSI Differential o Speed: 100 IPS 3.2.3 Expansion Chassis The Expansion Chassis (EC) will support additional internal and external SCSI devices. The expansion chassis will SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg006 support up to 5 half-high devices; or 2 full-high and 1 half-high; or 1 full-high and 3 half-high devices. The maximum number of hard disk drives supported is 5. A total of 7 SCSI devices can be supported per SCSI controller. The Expansion Chassis will be placed vertically next to the GPx 440 system to form a twin tower configuration with a SCSI bus connection from the main chassis. Disk Drives Full-High Half-High 355 MB 115 MB 670 MB 200 MB The EC connects to the Main CCA from a second SCSI controller which should be immediately to the left of the first SCSI controller in a 6-bit slot. A cable, P/N 916443-001 runs from the CCA to the SCSI IN port of the EC. The SCSI controller in the CCA should have the terminators installed RN3, RN4 and RN5 on the 1542A (long) card and RN2, RN3 and RN4 on the 1542B (short) card. The power is run in series from the EC to the CCA. The EC will have a power cord going to the UPS or AC power and to the CCA. The CCA will also have a power cord going to the UPS or AC power. 3.2.4 SCSI Converter (Rancho Card) The SCSI converter, P/N 400814-001, will convert the Single . Ended SCSI Adapter to the Differential SCSI Adapter for external SCSI devices such as the GCR. The converter card will be mounted in the expansion chassis. 3.2.5 UPS Requirements for GPx 440 with the Expansion Chassis. The main chassis, expansion chassis and a terminal can run on a single uninterruptable power supply that is provided by MBF. 4.0 Notes and Cautions WARNING: If upgrading from 1.0A or 1.0B you MUST delete the printer queue file, /usr/mbf/etc/_queues/lpq.que. The format has changed from previous levels. WARNING: The trestore problem below has been fixed in 1.0D, BUT trestore will restore linked files as 2 separate files. This could be a problem if a system has a lot of linked files and a small amount of disk space, because the disk could become filled with the double files. WARNING: When using trestore on 1.0C you MUST specify each full path when restoring rather than a partial path with the -r option. The result will be a directory which is recursive and too large to access. An example of a directory that would be created is: /usr/cust/data/pgm/pgm/pgm/pgm/pgm/pgm/pgm/pgm/pgm/pgm/... Example: To restore /usr/cust/pgm and /usr/cust/data from a tape use the following command: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg007 trestore d=tp /usr/cust/pgm -v trestore d=tp /usr/cust/data -v Do NOT use: trestore d=tp /usr/cust -r -v Workaround: To remove the long directory do the following: /etc/unlink /usr/cust/data/pgm trestore d=tp /usr/cust/pgm -v The unlink will delete the 'pgm' portion of the directory and will have to be restored again using the trestore command above. CORRECTION: In the 1.0C Software Announcement it is stated in the 1.0B History, Section 2, that mother board 916556-004 is required. It should have stated that if the 916556-004 mother board is. installed, then 1.0B or higher level of the Operating System must be installed. WARNING: The trestore command may receive a 'Bus error or odd address error' or 'Text file busy' when restoring files. The problem is caused by attempting to restore locked files; these files are usually O/S files. Also, once the error occurs, files on the tape after the error may NOT be able to be restored. If O/S files cannot be restored, an O/S upgrade will be necessary to recover the files. Workaround: It is recommended that operating system and application files be backed-up SEPARATELY if 'tsave' is going to be used for backups. Another option of. course is to use cpio, because it will do multi-volume backups. WARNING: After upgrading to 1.0C or 1.0D operators that have /usr/.../basic as their program and /bin/execsh as their Login shell may not be able to access system utilities or commands. The correct Login shell to use is /bin/sh. That's right, change it to /bin/sh. 1.0C or higher will create a .profile that accesses /bin/execsh automatically and that profile will be in the Home directory. This is also the reason that oprinfo does not allow /bin/execsh as the Login shell any longer. WARNING: It is possible that the /tmp directory may become filled with files that are not being deleted. These files are created by doing a RELEASE instead of a QUIT or other abnormal exits from BASIC. The file names will be in the form of /tmp/.execsh1111, the 1111 is the process id number. These files will not list unless an ls -la is done on the /tmp directory. A regular ls -l will not display them. Enter 'rm /tmp/.e*' to remove the files. WARNING: Application data files with the names R0 or R1 will have to use. their full path name or a translation file to OPEN the file otherwise an error 17 will occur. An error 17 will also occur when attempting to OPEN an off-line 1/2" tape drive. This should be an error 0 and will be fixed in 1.1A. FIX: Previous to 1.0C, if a spooled printer went offline and timed-out the spooler would restart the print job on the first page even if SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg008 the application program used form feeds. In 1.0C and 1.0D this has been fixed so that after a spooled printer times-out the print job will reprint only the page on which it failed, if the application used form feeds. Of course, if there are NO form feeds the spool job will begin at the beginning of the job. 5.0 Related Documentation Manual Number Title _ S/A 182 GPxTM 40, 1.0C Software Announcement M8219 MT-4405 (GCR) Tape Drive SCSI Interface Conversion Instructions M5163 MT-4405 (GCR) Tape Drive Installation and Operation Manual M8140 MT-4405 (GCR) Tape Drive Maintenance Manual M8215 GPxTM Series 40 Installation and Maintenance Manual M8215 GPxTM Series 40 Installation and Maintenance Manual Addendum Package M8224 GPxTM 240 Installation and Maintenance Manual M8224 GPxTM 240 Installation and Maintenance Manual Addendum Package M0186 GPxTM Series 40 Software Installation and Configuration Manual M0187 BOSS/VXTM System Administrator Guide M0188 BOSS/VXTM Reference Manual M1089 BOSS/VXTM User's Guide M0190 BOSS/VXTM Diagnostics Manual M0217 BOSS/VXTM Transportable Batch Communications (27xx/37xx) User Guide M0228 Business File System Library Interface Guide 3.2.7 525 MB 1/4" Cartridge Tape Drive The 525 MB tape drive can replace the current 120 MB 1/4" tape. drive in the main chassis. The 525 and 120 are terminated the same way. Only one internal 1/4" tape drive is allowed in a system. The drive appears the same to the system as the 120 MB tape drive and uses the UNIX commands tar and cpio and the MBF utilities tsave and trestore. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg009 T 1000 foot tape 600 foot tape a Read Write Read Write p +----------+----------+---------+---------+ e 525 MB | Yes | Yes | Yes | Yes | |----------+----------+---------+---------| D 120 MB | No | No | Yes | Yes | r +----------+----------+---------+---------+ i 60 MB | No | No | Yes | Yes | v +----------+----------+---------+---------+ e 45 MB | No | No | No | No | +----------+----------+---------+---------+ NOTE: The 525 MB 1/4" cartridge tape drive can READ 600 foot tapes written on the 60 MB tape drive but a 60 MB tape drive cannot read a 525 MB tape. Jumper Settings +--------------------------------------------+ | Jumper Open or Jumpered Description | +--------------------------------------------+ | 1 Open | | 2 Open | | 3 Open | | 4 Open | | 5 Open Spare | | 6 Jumpered Parity Enabled | | 7 Jumpered Sel2 | | 8 Jumpered Sel1 | | 9 Open Sel0 | +--------------------------------------------+ ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB005 Pg010 FIB 00006 10/05/90 *** O.S. rel. 1.0A has a problem with 7270 terminal configuration *** SYMPTOM: System experiences severe slowdown, "framing" errors log on random serial devices, "ARCP timeout" warnings are posted on the console terminal, serial port processes may hang. PROBLEM DETERMINATION: Check to see if the application software is issuing OPENs to ports configured as 7270. FIX: This is a known problem with release 1.0A. If the application software OPENs a port that is configured as 7270 and then writes to that port and you are experiencing the above symptoms, contact Product Support for assistance. ORIGINATOR: Harvey Mitchell SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB006 Pg001 FIB 00007 10/11/90 *** GPx40 Notes and Cautions for 1.0B*21 [ WPSF 624 ] *** PROBLEM: Spooler doesn't despool, a BASIC error 255 and system error - 4060 occurs. WORKAROUND: While in superuser, do the following: Enter: ps -ef |grep LP (or whatever the printer name is) Look for the task with ptstart and kill it. Enter: kill -9 459 (459 is an example PID number). PROBLEM: 'frepair' deletes INDEXED files when using interactive mode. WORKAROUND: Use the non-interactive mode when repairing INDEXED files. This has been fixed in 1.0C. PROBLEM: The home directory will be deleted when 'oprinfo' is used to delete an operator. This could delete application data and/or program directories if the home directory for this particular operator is the same as other operators. WORKAROUND: When adding an operator give a unique home directory to each operator (in 1.0C). PROBLEM: Printer status doesn't change in 'pstatus' or 'pqueue' when a printer is offline. WORKAROUND: None. Fixed in 1.0C. PROBLEM: 'tsave' will not backup a combination of a directory and a filelist. The directory will be saved to tape but the files in the filelist will not. The following message will appear: CAN'T OPEN FILELIST''. WORKAROUND: Put all the files in a filelist or save only directories. ***************************************************************** THE FOLLOWING ARE NOTES AND CAUTIONS REGARDING THE TBC PACKAGE ON THE 1.0B RELEASE. A RECOMMENDED WORKAROUND IS ALSO PROVIDED WHEREVER POSSIBLE. It is recommended to review this list before installing the TBC product. 1. After the TBC product is installed with 'mbfinstall', a software reboot will cause the system not to recognize the ICC186 controller board. * Workaround: (on all GPx 40 Series Systems) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB007 Pg001 1) Shutdown the system with the command: "shutdown -y -i0. 2) At the prompt "Power Off or Reboot the system Now", turn the system power off, wait for 10 seconds, and then turn the system on. 3) The system will reset and reboot. 2. If a wrong TBC public key is installed, a system error -657 and a BASIC error 59 may be returned. 3. If you plan to use BQR utilities with TBC, please install the "ITP" product during "mbfinstall". 4. Due to a translation problem in TBC transparent mode, we recommend the user run TBC on 2 ISCC ports with maximum 4800 BPS or on 1 ISCC port with maximum of 9600 BPS. 5. ESCAPE during a Comm session may hang the ISCC port. * Workaround: #1 - If the ISCC port is hung and there are no other communication sessions in progress on the same ISCC board, the user may be able to run /usr/mbf/comm/commload to re- cover the ports without a reboot. Please do the following: 1) cd /usr/mbf/comm 2) ./commload -bO 3) Check to see if the load is successful. If the load is not successful, please follow the instruction in Workaround #2. * Workaround: #2 - 1) log on at the console as root. 2) cd / 3) Shutdown the system with the command: "shutdown -y -i0". 4) At the prompt "Power Off or Reboot the system Now", turn the system power off, wait 10 seconds, and then turn the system on. 5) The system will reset and reboot. 6. BCOM may hang for up to 30 minutes during multi-port communications. It will recover automatically. 7. During a file transfer from GPx 40 Series systems to SPx systems, full SERIAL files (Data bytes are the same as declared at creation) may receive error 2 on SPx side. 8. During a file transfer in transparent mode from GPx to MPx or SPx systems an error 26 may occur. Workaround: The following patches need to be on MPx & SPx. 1) MPx: In program .PGMTBC.BRCV: 1455 IF T2=1 THEN A9=0; GOTO 1525. 2) SPx: In program /tbc/BCOM/BRCV: 1456 IF T2=1 THEN GOTO 1525. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB007 Pg002 9. When modifying a Transmit Queue for File Transfer, entering a destination directory without a terminating "/" will con- catenate the entered file name to that directory without a "/" between the two. 10. Wrong error message was reported when saving the receive queue with the name "DEFAULT". * Workaround: Do not save the receive queue with the name default. 11. Terminal hang when press key during a receive operation and select the RVI option. Workaround: Reboot the system. 12. Using an autodial autoprompt which does not have the correct communication port specified in the Transmission definition, BCOM will not return a STA=C AUTODIAL Destination Connection message to the Local Status Message area of the Batch Emulator Status Screen when the connection is successful. 13. While using BQR to create TBC transmit queue, BASIC program files will not be accepted. * Workaround: Convert the BASIC program files to string files and transmit them as string files. 14. Data should be verified in the transmitted files after an auto-restart. 15. If "T000" is defined in the '/etc/bfsdevs' ("T000" allows an 'init s' on a non console terminal to work properly), the screen displays may move up one line and cause display problems. "T000" is not in the 'etc/bfsdevs' files as a default and could be removed as a work around for this problem. ORIGINATOR: Dan Arteritano/Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB007 Pg003 FIB 00008 10/11/90 *** GPx70 BOSS/VX 1.0A Notes and Cautions [ WPSF 631 ] *** TYPE: Informational The GPx Series 70 is now available. The GPx Series 70 product line includes the GPx 5070 and GPx 6070 models. This new product line utilizes the BOSS/VX Level 1.0A Operating System, hardware and related software packages. This Field Bulletin contains Notes and Cautions and possible workarounds for Level 1.0A BOSS/VX Operating System. Installation and update information for the GPx Series 70 system, both hardware and software is fully documented in the GPx Series 70 Software Announcement. In addition, the Software Announcement contains sections on customizing the system, system dump procedures, operating system and utility overviews and other topics related to the operation of the system. For information on ordering software, hardware and other related Marketing information please see Marketing Announcements for the United States and International listed below: BOSS/VX 1.0A FOR THE GPx SERIES 70 - INTERNATIONAL 536I DOMESTIC 843 US/C GPx SERIES 70 SYSTEMS - INTERNATIONAL 535I DOMESTIC 842 US/C Before installing or working with the GPx system it is recommended that you read the following Notes and Cautions. GPx70 NOTES AND CAUTIONS 1. The SSM monitor has a help command that displays useful information and if the system console is not set up to handle tabs properly, the help information is unreadable. Use the following procedure to set up the terminal for tabs: A. Put the terminal in BLOCK MODE. To get into this mode use the 'FUNCT A' keys on a 4313 or the 'FUNCT MODE' keys on a 4314. The status line should show 'BK'. B. Move the cursor with the space bar to the desired tab stop (ex. 8 spaces). C. Enter 'FUNCT Q' to set the tab stop. (If this procedure doesn't work, try using 'ESC' and '1', entered sequentially). D. Return the terminal to normal mode with 'FUNCT S' or 'FUNCT MODE' on the 4313 or 4314, respectively. 2. To properly initialize the GPx70 internal modem, do the following: A. Ensure that the modem is powered off until properly initialized. B. Ensure that the remote enable/disable switch is in the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg001 disable position. C. Use the Configure utility to set AltCon (port 1) to 2400 baud. D. Get into BASIC and do the following: Power ON the modem and Enable the remote port. Enter: OPEN (1) "T1" PRINT (1) "AT" (allows modem to auto baud) PRINT (1) "ATS0=1" (Enables auto answer & 1 ring) PRINT (1) "AT\N3" (Enables auto selection of error correction) PRINT (1) "ATE0" (Disables echo) PRINT (1) "ATQ1" (Sets quiet mode - NO status msgs) PRINT (1) "AT&W" (Writes config to NVRAM in modem) END QUIT The modem will remain configured when powered off. Note that if echo is enabled or quiet mode is OFF the modem will cause problems for DEMON and possibly the OS. 3. A large number of terminal definition files exist to describe various default mode settings for the 4313 and 4314 terminals. The standard terminal definition, dt4313, defines a terminal that has black letters on a white background in a 24 x 80 format. Other terminal definition files describe optional features such as 35 x 120 compressed format. The desired terminal definition file should be specified as the "TERM= " value at login. The file /usr/lib/terminfo/mbf.ti contains descriptions of all the variants. 4. The vi editor will flash the screen when an erroneous command is given. If this causes the screen mode to change from white letters on black background to black on white, it is because the video mode of the terminal does not match the TERM type entered at login. If white on black format is desired, the TERM value should be dt4314-rv. 5. "C" programs which are called from Business BASIC programs should be relinked whenever a new BASIC is installed (as part of a full or update installation). 6. The release level is 1.0A. However, the utilities will display their version numbers as 1.0C. 7. Controllers on the VME backplane must be installed with no gaps and must be installed starting from the right (as you face the back of the system). 8. The system uses dynamic configuration tables based on the amount of physical memory configured. An assumption is made that for each 16 MB of memory, 4 16-way controllers may be supported. Further, there is assumed to be 1 serial printer for each 15 terminals and 4 slave printers for every 10 terminals. For example, a 16 MB system would support 60 terminals, 4 serial printers and 24 slave printers. Configurations that differ significantly from the above assumptions may need to have specially configured dct files. See the man pages for dct for further information. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg002 9. The installation process automatically establishes a partitioning of the primary disk that allocates a swap partition that is 2.5 times as large as the physical memory on the system. This ratio has proven to be a minimal but safe allocation. 10. The capacity of disks indicated in the installation procedures document refer to megabytes which are 10^6 (millions), not 2^10 (1024*1024). 11. The sizes of the file system and swap partitions are dependent on system memory size and disk type. Although the Maxtor 8380 is not certified as a boot load device, partitioning has been defined which would allow this device to be used as the primary disk. This disk has only one partition, regardless of system memory size. The root and usr partitions are the same size on all systems. The other partitions are allocated as follows: On all disks, regardless of system memory size: root partition: 33 MB usr partition: 97 MB miniroot partition: 8 MB If 8 or 16 MB is configured: swap partition: 52 MB usr2 partition: 443 MB If 24 or 32 MB are configured: swap partition: 80 MB usr2 partition: 411 MB For larger configurations the swap partition size is set to 2.5 times the physical memory size (rounded up to the nearest 16 MB). The remainder of the primary disk is allocated to the usr2 partition. 12. Partitioning of additional disks is facilitated by the diskadd utility. This utility may be run from single or multi-user mode. See the man page for more information. 13. The overhead associated with each partition may be modified either when a file system is created on the partition (with newfs) or dynamically after the file system has been created (with tunefs). Read the man pages for these commands, specifically the -i option in newfs and the -m option in tunefs. 14. The UNIX printer services are also included in the release. The status command for UNIX is the same as the one for MBF 'lpstat'. If you just type lpstat you will get the UNIX command and not the MBF command. You can either move the UNIX command or use the extended path name for the MBF command, i.e. '/usr/mbf/bin/lpstat', or change the search path in your environment variable PATH. 15. When configuring serial printers insure that item #13 IXANY, of the printer options setup menu, is set to NO. If set to yes it SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg003 will cause loss of data or overflow conditions. Under certain circumstances data sent to a serial printer may be lost. No data will be lost when the printer is spooled or if the printer is non-spooled and the job is submitted with the lpr command. If a BASIC program writes to a non-spooled printer, data may be lost when the printer goes offline. If additional data is sent to the printer without bringing the printer online, the new data will be lost and no error will be reported. This condition will be fixed in an upcoming release. 16. Following a system panic, the system should return to the operational firmware level (the console should display the ---> prompt). In certain circumstances, however, the system will not display the prompt. If this happens, the operator should enter and/or Ctl-p on the system console. This should cause the system to display the ---> prompt. Enter ---> bh doAux to cause a dump of memory for analysis. If the system does not respond with the operational firmware prompt after entering or Ctl-p, it will be necessary to cycle the power on the system and the dump will be lost. 17. The system console is not intended to be a data entry device. In general, it should be reserved for operator functions and to record system messages. Specifically, applications that require the use of Ctl-p should not be run on the system console. 18. The physical characteristics of the system console and altcon (e.g. word length and baud rate) should be set via commands to the SSM monitor. (See the "local" and "remote" commands.) The "stty" command and changes to gettydefs do not affect these devices. GPx 40/70 DIFFERENCES 1. Device Names: o Tape drives: /dev/rmt/tm0 .... 1/4" tape drive Note: /dev/tape and /dev/tp link to this device /dev/rmt/tm0n .... 1/4" tape drive, no rewind device. Note: /dev/tpnr links to this device /dev/rmt/tg0 .... 1/2" tape drive /dev/rmt/tg0h .... 1/2" tape drive, high density. o Disk drives: /dev/dsk/wd0s0 ... SCSI disk 0, partition 0. o Printers: /dev/printer/wp0 . parallel printer. o The console is called syscon. o tty01 is called altcon. 2. On the GPx 70 sixteen 16-ways are supported. 3. On the GPx 70 the serial devices are split into 4 sub- SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg004 directories: /dev/ttyXA, /dev/ttyXB, /dev/ttyXC, /dev/ttyXD. 4. The mt program is located in the /etc directory rather than the /bin directory as in GPx40. 5. On the GPx 70 both Centronics and Dataproducts parallel printers are supported. 6. GPx 70 does not support the t* utilities (tsave, trestore, tcompare, etc.). 7. GPx70 file name may be 255/256 characters long. GPx40 has a 14 character limit. GENERIC GPx NOTES AND CAUTIONS & GENERAL INFORMATION NOTES: 1. Difference between SPx and GPx: a ^D will not abort the login sequence on GPx as it does on SPx, although a will. This is to preserve UNIX compatibility on GPx. 2. oprinfo will not allow usernames which are all uppercase. This is because if login sees an all uppercase username, login will force the login session to use all uppercase letters. (aka, stty olcuc.) This semantic is a historical relic from the days where teletypes only had uppercase. So, use oprinfo and lowercase user names to by-pass the problem entirely. 3. While at the shell prompt, if you enter characters, then enter escape, backspace, backspace to remove characters on the screen, you will lose a character. For example, typing in configure will appear as 'configure' on the screen, but the system will actually see 'confiure'. 4. If a UNIX command which is issued to the shell using variable or filename substitution, such as cp, gives an 'Arg list too long' error when full path names are used. Use xargs to shorten the list. For example: cp /usr/mbf/atp/isys/* /usr2/PGM/WEEKDAY can generate the error if there are a substantial number of files in the /usr/mbf/atp/isys directory. Instead, do the following: ls /usr/mbf/atp/isys/* | xargs -i -t cp {} /usr2/PGM/WEEKDAY For further details, see 'man xargs'. 5. The ATTR function in BASIC will return SORT files as DIRECT files with 0 record length. 6. In order to have full access to and utilization of the online man (manual) pages, the MBFMAN and UMAN products must be installed. 7. There are certain times that a UNIX shell will be running in "sane" mode. (aka, stty sane; also, stty ek.) While in "sane" SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg005 mode, the tty device will be configured to use the number sign (i.e., "#") for backspace and the at sign (i.e., "@") for line kill. Sane mode is another feature based historically on the teletype and is typically used during password entry. 8. The UNIX System V filesystem (as well as UNIX/BSD) fragments files and with normal usage, the system performance, will suffer from fragmentation. For example, file (system) backups times will increase with increasing file system disorder. (For further reading, try Bell Labs Technical Journal, July/Aug '78, "UNIX Implementation," K. Thompson.) To reduce the fragmentation of files and free space use the dump/newfs/restore sequence to create a filesystem of contiguous files. Contiguous files will result after: a. full filesystem backup. b. newfs to erase and re-create the volume. c. full restore to the erased volume. BUT, as files are subsequently re-written, created, and destroyed, the file system again becomes fragmented, and tape backup performance will degrade. CAUTION: 9. If a tape drive is used to access a tape which is severely physically damaged, it may cause the drive to go into an error state. To recover from this error state, the drive must be powered down and then powered back up. To do this safely, the system must be shutdown and powered down and then back up. Unpredictable results may occur if the tape drive has its power cycled while the machine is up. 10. The default terminal modes for non-configured terminals (non-getty) will be modified in later releases. If you have an application is that is setting these explicitly, set them all to avoid the necessity of changing them on future upgrades. 11. When a serial file is created on GPx using cread the maximum number of records is automatically set to 0, which tells the GPx file system that the file can grow without limit. This is incompatible with the MPx file system, and will result in an error message when the files are transported from GPx to MPx. If the user wishes to move these files to MPx he should first run fchange and modify the Max. records parameter (e.g., to match the actual number of records) before saving the file via cwrite. PRINTER NOTES 1. The ISP PDF does not support pitch or lpi in forms. 2. The Pstatus utility does not reinitialize the page count when the job is interrupted and restarted. SLAVE PRINTER NOTES SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg006 3. If you are using a 4313 terminal the firmware must be Rev. E or higher. 4. If you are using a 4314 terminal the firmware must be Rev. L or higher. 5. If a slave printer goes offline while printing, and the data to be printed fits in the terminal buffer (128 for 4313 and 1024 for the 4314) no error is issued. The user must manually reset the terminal or turn on the printer. 6. When using a slave printer, the terminal should be configured for bidirectional software (XOFF/XON) flow control. The printer port on the terminal and the printer should be configured for DTR/CTS flow control. 7. On a write timeout to a slave printer, 3 ESCAPE B's are written by upd to the port. This sequence resets the terminal. For 4313's it causes the screen to flash and the function key settings to be lost. It is necessary to do this to get the terminal out of bypass mode so that an error message can be written to the terminal. This will only happen if the terminal is configured for software flow control, as recommended above. Hardware flow control is not recommended for terminals with slave printers. If the terminal is configured for DTR/CTS flow control, the 3 ESCAPE B's will not be written to the terminal because CTS is low and this cannot be overridden as we do for the XOFF condition. This may result in data printed on the printer that was not intended to go to the printer. 8. If the printer port on the terminal is configured for XOFF/XON flow control, data could be lost after a printer timeout. This is because the terminal has been reset and will start sending data to the printer even though the printer has not sent an XON. With DTR/CTS flow control, the terminal will still recognize the CTS low condition as a signal not to send data. 9. If a slave printer is opened from a ghost and the ghost is released from another process, then the terminal modes may be improperly set. This will not happen if the ghost releases itself. DIAGNOSTIC NOTES AND CAUTIONS 1. When DIVE is performing a format or a surface analysis the system should not be powered down to exit either of these operations. Doing so will destroy the format on the drive and render the drive un-usable. 2. The 1/4" MCS tests 3.8 and 3.9 fail. The problem is under investigation. 3. The off-line DIVE program is file number 30 on the diagnostic tape. 4. The DEMON csd 2.1 test fails during the default run with a compare error. This only occurs on a newly formatted disk. Running test csd 3.1 corrects the error. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg007 BASIC NOTES AND CAUTIONS CAUTION: 1. BASIC sometimes ignores Escapes when executing in very tight loops. 2. Executing a system command from BASIC reports a non-zero exit status code as a system error. NOTES: 3. 'start' is a stand alone program to start a task on another terminal. Such a task is terminated by 'RELEASE'. 'START' is a BASIC directive which starts a ghost task. A ghost task is terminated by 'QUIT', 'END', or 'RELEASE'. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB008 Pg008 FIB 00009 10/11/90 *** Release 1.0A*60 Available for GPx70 [ WPSF 631 A1 ] *** TYPE: Informational PURPOSE This Field Bulletin is to inform the field that the new revision (*60) of BOSS/VX 1.0A for the GPx Series 70 has been released. This new version contains a fix for a system hang problem having to do with the system errorlogger. Since this problem can hang a customer's system, it will be sent out to all present GPx Series 70 sites. All GPx Series 70 systems should be updated to this release as soon as possible. This release also contains a fix for a problem where an ISP nonspooled printer would get errors when a 'FF' was sent to it and a fix that allows the tty translation tables to work. PROCEDURE This release will be sent to all sites that have ordered and received a GPx Series 70 before August 10. All systems shipped after August 10, received the 1.0A*60 release. For systems that have a release earlier than 1.0A*60, the update procedure should be followed to update the system as soon as possible. If the customer has not received the new release by the end of the month, Field Product Support should be contacted so the update can be sent to them. RELATED DOCUMENTATION Since this is a bug fix release, there are no documentation changes required. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB009 Pg001 FIB 00010 11/27/90 *** File Corrupt after Restore on GPx70 [ WPSF 631 A2 ] *** TYPE: Problem PURPOSE This field bulletin describes a problem with a file being corrupt after restoring it. SYMPTOM A file that spans a 1/4" tape using the /etc/dump command is corrupt after being restored. frepair says the file is unrepairable. CAUSE If the file is backed up with the /etc/dump command using the 'c' option to default to 1/4" tape, a 10K blocking factor is used. When the tape is restored using /restore a 32K blocking factor is used. So after the program restores the first part of the file and then goes to the second tape it sees that it is off by 22K, so it skips 22K to get back in synchronization. SOLUTION 1) Use the 'f' option with the device /dev/rmt/tm0 for the /etc/dump command. 2) If the 'c' option is used with the /etc/dump command, use the 'b' option in the /restore command with a size of 10. Example: /restore rfb /dev/rmt/tm0 10 ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB010 Pg001 FIB 00011 11/28/90 *** Conversion Tips from Product Support *** Subject: BOSS/VX Conversion Tips Type: Informational Purpose Due to the number of calls received on transport/conversion, this Update will serve as a Helpful Hints Guide. Procedure The transport/conversion to the GPx is similar to the transport/conversion to the 2000-4000 so it has been written with that in mind. To transport programs and data files to the GPx you use the same tools that are used on the 2000-4000, mainly 'cread' and level 4 ATP. These tools come on the base tape and are in the ITP package when you run 'mbfinstall' (see the GPx Software Announcement for more details on how to install the package). NOTE: When installing the ITP package, you will be asked for a key. The key is only needed if you want the auto features of ATP, it is not needed to do transports. If you are using ATP, configure the port as you did on the 2000-4000. For tape, the GPx will read 45/60/120 MB tapes, but only writes to 120 MB tapes Note: If using ATP over modems, you must use one of the last two ports on the breakout box. This restriction is for ATP only and does not apply to general modem use. The GPx is a lower order ASCII system as is the 2000-4000 so any program modifications that were required on the 2000-4000, will also be required on the GPx. In addition, the GPx is running pure BB90 so there may be othe modifications required to be BB90 compatible. To date, the main problems have been 'LST' and 'CPL' as they will not work on the GPx and should be replace with 'LIST PROGRAM' and 'MAKE PROGRAM'. When using tape for the transport, you can set the menu so that both progra and data files are converted during the transport (default). In addition, option 3 will allow you to have error logging for programs. The GPx Series restores tapes with conversion and error logging at the approximate rate of 115MB per hour for data files and 6.9MB per hour for program files. On the GPx, errors found in the programs are now written to a file called 'itplog.###' and is found in the directory that the files you are transporting go in. This one file contains the program name, last statemen number, and any problems found for all programs. There is no longer one file for each program. To print this file use 'lpr /directory/itplog.### list=printer(lp,p1,etc.)'. The basic steps required for porting are as follows : 1. File preparation a. Validate and reconstruct all data files. Use DISKANALYZER and RECONSTRUCT on the MPx and 'fsck' and 'frepair' on the SPx. b. Determine file path names and logical grouping of files. The 'BQR' utility keeps only the last part of a file name during transfer when system filelist are used. This can cause several duplicate names on the receiving system. Smaller filelists and splitting up backups SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB011 Pg001 may help organize file directory paths during restore. Example : .MPX.ACCT.FILE1 and .MPX.PAYROLL.FILE1 would be restored on the GPx as /rcv/directory/FILE1 and /rcv/directory/FILE1.000 c. File access rights will be different on the GPx and include the file owner, group and others permissions. 2. Examine programs : a. Make sure programs are BB86 compatible. b. Check programs for use of system commands and determine what changes will have to be made. The MPx 'SORT' utility is the most difficult system command to change. c. Check programs for usage of fully specified path names when OPEN, RUN START or CALL directives are used. d. The most common system functions that may be different are the 'FID' and 'TBC' functions. You should replace the 'FID' function with 'ATTR'. Check the BB90 reference manual for differences. e. Protected or PSAVED programs can not be transported. f. The MPx uses high order ASCII and the GPx uses low order ASCII. Check programs that rely on specific hex string values. g. The MPx would allow a space in directives such as 'GO TO', 'GO SUB' and 'INIT FILE' but the space is not allowed on the GPx. h. Reserved words used as variable should be replaced by non reserved words. i. The MPx would allow a ';' prior to an 'ENDIF' or 'FI' directive and the GPx does not. j. The MPx would allow a '$' after a function name such as 'PNM$' and the GPx does not. k. Make as many of the required program modifications as possible prior to doing the conversion. 3. Create 'BQR' filelists for the data to be transferred. Individual file names can be entered or a system filelist may be used. 4. Transport the data using the intersystem transport utilities. If tape is used the backup programs are '!MCSI' on the MPx and 'cwrite' on the SPx. The GPx uses 'cread' to read the tapes. ATP level 4.0 can be used for async transfers. 5. Print the 'itplog.###' files and make any additional code modifications. 6. Test the applications. Refer to the related documentation section for the manuals that provide more specific details. The Business BASIC 90 Reference Manual and the Intersystem Transport Package User Guide are most useful. Again, think of the conversion to the GPx as if you were converting to the 2000/3000 and things will go a lot easier. Related documentation - GPx Software Announcement numbers 168 and 175. - Business BASIC 90 Reference Manual number M6262, chapter 15 - BOSS/VX System Administrator Guide number M0187, chapter 9 - GPx Series 40 Sales Guide page 9-34 - GPx Series 70 Sales Guide page 9-34,35 - Intersystem Transport Package User Guide number M6354 Notes and Cautions - Files that contain binary fields should be identified and can be transported as text data. After the files have been restored to the GPX, the binary fields can be converted back using the 'XOR' function with a $80$ for each byte of the field if the data came from a high order ASCII system. - There is a bug in FLAGIT that will cause error logging to stop after the first SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB011 Pg002 program with an error in it is found. In addition, the deletion of the .ser files used for the program transport will stop. Below is the fix for this problem. Be sure you make this change before doing the transport: In '/usr/mbf/atp/FLAGIT' 7080 ...LENG-LSTPTR+1) change to ...LENG-LSTPTR) add the following two lines: 9010 CLOSE(1);CLOSE(2) 9020 ERASE SERF$, ERR=9030 Note : This problem only occurs on the 1.0A release for the GPx 40 Series and has been fixed in the later releases. - Another thing that may cause a problem is 'umask'. 'umask' determines the fil. modes for files created in UNIX. During the transport this is what is used for data files and comes set for read/write for owner and read only for everyone else. Before starting the transport make sure 'umask' is set to 000 for the operator running the transport. To set it, at the UNIX prompt enter umask 0 . For more information on 'umask' see the Software Announcement. - The 'MCSI' utility on the MPx Series System will support multi reel backups but the 'cread' Utility does not. Do not span tapes on the MPx while doing conversions. - Multikeyed files are not supported by the conversion utilities on releases prior to M.6G for the MPx Series systems and 7.5B for the SPx Series systems. - The 'bsearch' utility can be used with the 'search and replace' option on the. GPx Series system to detect error 20's. A none existent search string can be used if no replacements are required. This may be useful since 'FLAGIT' can only be run once during the actual conversion. - When output from the 'bsearch' utility is sent to a printer, the program name is on wrong page. The errors reported will be listed under the wrong program name. The program name on the next page will be the correct name. - In cases where programs are converted and there is more than one syntax error on a line of code, if 'bsearch' is being used to 'search and replace' code, the changes will not be save. The program '/usr/mbf/bin/SREP' executes a SYNTAX directive on the line of code to be changed and takes an error branch due to the second syntax error on the line. The change is not saved. Line 5297 can be modified to REM out the SYNTAX check and the changes will be saved. Do not leave this modification in the program after the conversion i complete and be aware that any replace patterns will not be checked for prope syntax with the modification. ORIGINATOR: Product Support SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB011 Pg003 FIB 00012 11/28/90 *** Fix for Operator Logging in in Upper Case/Manual Err *** Problem: User logs in with upper case characters only, causing BASIC to convert all characters to lower case only. Workaround: Use the UNIX command 'stty -iuclc -olcuc -xcase'. This command can be put into the user's '.profile' file so it is executed each time he logs in, avoiding the problem. Problem: Manual M0186 'GPx Series 40 Software Installation and Configuration' on page 2-4 states that you must be in single user mode to use 'diskadd'. This is false, you must be in multi-user mode to use 'diskadd'. ORIGINATOR: Product Support SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB012 Pg001 FIB 00013 11/30/90 *** Full User Partition after Panic on GPx70 *** Type: Informational Purpose: After a system PANIC the memory information at the time of the PANIC is written to the swap area. While the system is coming up, just after the filesystems are repaired, the user is given the option to override the default writing of the dump to the usr partition. The user has ten seconds to enter a return to do this, if the user doesn't enter anything the PANIC information will be written to the /usr/crash directory. This information takes up a lot of the usr disk space, as it includes the contents of memory, the OS file and other message files. To avoid problems with a full or near full usr partition the PANIC information should be backed up after the system is back up again and then removed from the system. Procedure: To back-up the PANIC information from the system do the following: cd /usr/crash tar cvf /dev/tape (/dev/tape is for 1/4" tape; /dev/rmt/tg0 would be used for the 1/2" Tape) To remove the PANIC information from the system do the following: rm * Related Documentation: GPx SERIES 70 SYSTEM Software Announcement number 175 (FIB 3). ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB013 Pg001 FIB 00014 11/30/90 *** Performance Issue using Multikeyed Files [ WPSF 671 ] *** Type : Problem Purpose This field bulletin is to address a difference in the way the file system on the GPx Series works compared to the MPx Series system. Symptom All terminals running an application which is accessing the same multikeyed file may hang for several seconds, or up to a few minutes, when one record is removed. Cause This problem may be caused by the way the multikeyed file is defined. If the file contains several keysets which allow duplicates, the removal of one record can lock the file for a given amount of time. The reason is that record deletions must search through duplicate keys sequentially. The more duplicate keys that have been read, the longer the remove will take. All other accesses of the file will hang until the remove is complete. Solution To avoid this situation, append an additional field or byte to each duplicate key to make it more unique. In this manner, the sequential search of duplicate keys will take less time. The application and file definition will have to be changed to speed up the process. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB014 Pg001 FIB 00015 11/30/90 *** GPx70 Root Filesystem Full Message *** Type: Informational Purpose If the root filesystem gets full UNIX will put a warning message on the console. When this occurs many of the UNIX commands will be unusable and users (including the root user) many not be able to login into the system. This Field Bulletin will give you ways to find the problem and correct it. Procedure The most common way the root filesystem will become full is if a tape backup is attempted with the tape device was not seen by the system at boot time or tape device is used that is not connected to the system. If the tape device is not seen by the system at boot time all of its device files will be deleted. Then when the backup to tape is attempt a file is created on the root partition with the tape device name and the backup data is written to that file. This will quickly fill up the root partition. Likewise, a backup to a tape device that is not connect will produce the same results. To check for this do the following: cd /dev/rmt ls -l The file type for all tape drives should be 'c'. The number in the file size column should contain a major, minor number and not one large number, for example it should be 11, 26 not 1327189. If you find a tape device file that has a size and not a major, minor number it should be removed using the 'rm' command. Also, the problem needs to be identified and correct so it will not occur again. The other way the root partition can become full is if data meant for an other partition is restored to the root partition by accident. This can occur if the data is backed up without path names and the restore of the data is done without first setting the proper directory, the /restore command is used without first setting the proper directory, data is restored to a directory thought to be a partition mount point and is not or data restored to a directory that is a partition mount point, but the partition is unmounted at the time (this would most likely happen if the restore was done in single user mode). In these cases the customer and/or vendor need to examine the root partition for the data that doesn't belong on the root partition and move it. In the case of data in a directory that is a mount point, the mounted directory will need to be unmounted and checked to see if it contains data. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB015 Pg001 FIB 00016 11/30/90 *** Indexed Files Deleted by frepair on 1.0C - GPx40 *** Purpose: To WARN the Field that INDEXED files may be deleted by frepair. Sympton: The problem is usually seen after a PANIC has occurred and the user is in the process of repairing files with the utility 'frepair'. Workaround: Copy Indexed files before running frepair on them, in case they get deleted. This problem will be fixed in 1.1A. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB016 Pg001 FIB 00017 01/07/91 *** GPx40 Password Aging [ WPSF 667 ] *** ***********************REVISED************************************ * This is being sent again to make sure that the correct * options are being used with the 'passwd' command. The previous * procedure was correct, this is to be sure that the '-1', as in * 'one' is used, not '-l' as in larry. See the example below. ****************************************************************** Type: Problem Background: Password Aging is the procedure that tells the Operating System how often the operator password should be changed or not be changed. Purpose: The password aging procedure explained to the field has NOT been preventing the passwords from being changed by using the MINWEEK and MAXWEEK in the /etc/defaults/passwd file. Symptom Every so often, once a month or every 2 weeks, the operator will be prompted to change the password. Solution To prevent the Operating System from asking for a new password use the . following command: passwd -x -1 admin ('-1' as in '-one') The '-1' will turn off password aging immediately. If you want to use password aging use the following command: passwd -x30 -n7 admin This will make the password for root valid for a maximum of 30 days and the minimum number of days the password is valid is 7 days. To test the aging, change the system date to a date at least 1 month ahead to see if the password aging acts in the manner you want. Caution: I recommend that you try this on a non-root account before trying it on root. Do NOT use the '-l' as in 'larry' option because it locks the password. Related Documentation UNIX System V/386 System Administrator's Guide, pages 4-10 - 4-11 manpages for passwd ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB017 Pg001 FIB 00018 12/05/90 *** Procedure to Delete root Password on GPx40 [ WPSF 668 ] *** GPx 40 Wally Moore 12/05/90 Deleting Root Password Type: Informational Purpose This Field Bulletin gives the steps to remove the password from the root user in the case the customer has forgot the password or it has changed and the customer doesn't know the password. Procedure If no one can login as root or change to super-user because the root password is unknown the system will have to be crashed and rebooted from the OS installation tape. Before crashing the system have everyone log-off the system and wait 5 minutes to let the system sync (write) the data from the buffers to disk. To crash the system either press the NMI button on the back of the system or power the system off and then on. Make sure the OS installation tape is in the tape drive before crashing the system. Next follow these steps: 1. With the OS installation tape in the tape drive at boot the system will boot off the tape and bring up the Installation menu. From this menu choose option E: Exit. This will take you to a UNIX prompt. 2. Since the system was crashed you will need to repair the root and usr partitions. To do this use the following commands: fsck -y /dev/dsk/0s1 fsck -y /dev/dsk/0s3 3. Next make a usr directory to mount the usr partition to by using the command: mkdir /usr 4. Next mount the root partition to /mnt and the usr partition to /usr: mount /dev/dsk/0s1 /mnt mount /dev/dsk/0s3 /usr 5. To remove the password from root 'vi' the '/mnt/etc/shadow' file by entering: /usr/bin/vi /mnt/etc/shadow Position your curser to the root entry in the file. Move it to the right to the first character past the first colon ':'. Use 'x' to remove all the characters betwen the first colon and the second colon. Exit 'vi' by using :w! followed by :q ex: before root:xD4hn7:7693:: after root::7693:: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB018 Pg001 6. To reboot the system enter INSTALL this will bring up the installation menu. Choose option R : REBOOT. 7. Remove the OS tape and reboot the system. If you have any other filesystems they will automatically be repaired. There will be no password for root, if you want root password go into oprinfo and add the password. Related Documentation man pages on the above commands. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB018 Pg002 FIB 00019 12/05/90 *** Potential File Corruption on Open Files [ WPSF 650 ] *** Subject : BOSS/VX Author : D. Jensen Use of UNIX Commands Date : 12/5/90 on Opened Files Type : Problem Purpose The purpose of the Field Bulletin is to eliminate possible file corruption by performing UNIX commands on opened files. Symptom The exact symptom resulting from performing UNIX commands on opened files is unpredictable. Some of the symptoms will include: data files missing records, data files have incorrect record counts, errors reported when 'frepair' is run, unexpected BASIC errors, terminal hangs when accessing corrupt files, or other file related problems. Cause UNIX commands such as 'cp','mv','dd','tar','cpio','dump' and 'restore' can be done on opened or locked files. When these commands are executed on a . file that is in use, the file integrity of the new copy (either on tape or disk) will be unknown. If these files are used to replace the original, such as restored from tape, the file corruption may be compounded by repeating the process. Solution Although UNIX allows online backups and file copies, these commands should never be used when files are being accessed by users due to the unpredictable results described above. An on-line backup facility is currently being developed which will allow opened files to be backed up to tape using 'cpio'. This facility is expected to be included in the 1.1A release for the GPx Series 40/70. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB019 Pg001 FIB 00020 12/24/91 *** Root CRON Entries [ WPSF 659R ] *** Type : Informational Purpose: To show how to modify 'crontabs' without affecting the running crontab. Also to warn that care should be taken when logged in as an operator that has a crontab, because processes running on the system could be affected. Procedure: Operating systems have default crontabs for adm, root, sys, sysadm and possibly others depending on the operating system. Existing entries should be left intact and new entries should be added at the bottom. The following steps show how to change the 'sys' crontab. If you wish to change a different crontab substitute its name for sys. login as root su sys cd /usr/spool/cron/crontabs cp sys sys.org (sys.org is an extra copy just in case) crontab -l >sys.new (this will copy the sys crontab to sys.new) Add the change to the end of the sys.new file to do what you want. vi sys.new (make the change and save the file) crontab sys.new (this will make your sys.new file the sys crontab because you are currently 'sys') The crontab has been changed and is effectively IMMEDIATELY. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB020 Pg001 FIB 00021 12/14/90 *** Corrupted Files not Reported by fsck - GPx70 on 1.0A *** Subject: GPx Series 70 File Header Record may not be Flushed to Disk Type : Problem Purpose The purpose of this field bulletin is to inform the field of a problem on the 1.0A*60 release that can cause possibly damaged files to not get reported by the 'fsck' program. Symptom When accessing data files, BASIC errors may be encountered or a terminal hang may occur. Cause When a file is opened and being modified, the file header is not always flushed to disk during a normal buffer flush. The file header contains a file integrity bit. If the system panics or is shutdown improperly, an a files header has not been flushed to disk after the file has been modified, the file may be in a damaged state. When the 'fsck' is run afte a system reload, the damaged file will not be detected because the integrity bit is not set. Solutions To prevent BASIC errors or terminal hangs caused by an access to a damaged file, run the 'frepair' utility and analyze all files that may have been opened at the time of the system panic or improper shutdown procedure. Use 'frepair' in the repair mode to fix any damaged files or if necessary, restore the file from a backup. This problem has been fixed in the 1.0A*63 release. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB021 Pg001 FIB 00022 12/19/90 *** GPx70 SAR Change for a Months Performance History [ WPSF 675 ] *** Subject : GPx Series 70 Author : Dale Jensen SAR Data Collection Type : Informational Purpose This field bulletin is to provide the necessary changes to a system shell script so that a full months worth of system performance information is saved instead of only one weeks worth as currently done. Procedure A change to the shell script '/usr/lib/sa/sa2' is required to increase the amount of days the SAR data will be saved. SAR is the system activity report package used to collect performance data. The line that needs to be modified currently reads : find /usr/adm/sa \( -name 'sar*' -o -name 'sa*' \) -mtime +7 -exec rm {} \; Modifying that line to save 30 days worth of data will read : find /usr/adm/sa \( -name 'sar*' -o -name 'sa*' \) -mtime +30 -exec rm {} \; This change can easily be done using the 'vi' editor. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB022 Pg001 FIB 00023 03/05/91 *** Notes for GPx40 1.1A & GPx640 Announced [ WPSF 660 ] *** GPx 40 1.1A RELEASE DAN ARTERITANO 1/91 660 TYPE: Informational PURPOSE: Announce the Release of 1.1A-40 and the GPx 640. Notes and Cautions are also included for this release. 1.1A has been released for the GPx Series 40 and is the MINIMUM LEVEL Operating System for the GPx 640. 1.1A contains new features, enhancements and fixes. Some new features include: Errorlog Watcher Third Party Software Product Dynamic Serial Port Configuration Enhanced NMI & UPS Support UPD Simple Complier (Public Key necessary) 80486 Processor Multi-Volume 'cread' Support 128 User Connectivity File Write Options The 80486 Processor is the processor for the GPx 640. The 640 is the high end of the GPx Series 40 with 128 users connectivity, storage of up to 2.2 GB and initially up to 16 MB of RAM. Additional features include: Multi-Function Card (MFC) which supports: - 2 parallel ports which support DataProducts and Centronics interfaces - COM1 and COM2 ports which support BASIC applications (slave printing is NOT supported on these ports) - Internal MODEM (COM2) 128 User Connectivity via four 16-ways for terminals and printers and 64 users via Terminal Servers for terminals only. 2.2 GB of disk storage with an Expansion Chassis. 16 MB of RAM. 525 MB cartridge tape drive which will Read/Write in 120 MB or 525 MB format. The drive detects the length of the tape and writes the format that particular tape needs. And more. In 1.1B, the 640 will support 64 MB of memory utilizing the SCSI EISA controller. The Beta for 1.1B is scheduled to begin at the end of January. If you have a potential Beta site contact Velma Novak at x2825. NOTES AND CAUTIONS: Caution: Improved handling of the NMI and UPS signals has exposed a possible hardware problem on 3/440s. When booting from tape to upgrade to 1.1A, the following message my appear: HALT: DO NOT REBOOT ON BATTERIES! This is caused by incorrect wiring in the NMI/UPS assembly. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg001 Workaround: Unplug the cable connected to the NMI/UPS assembly from the CMB. Fix: Order a new 'Reset UPS Assembly', P/N 903845-001. Caution: bbmap can not be run on multiple terminals, if multiple copies are run the system may PANIC. Caution: DT-4309 and older terminals do not work on the console port (COM1) with the standard cable P/N 916484-xxx. NOTE: The error messages "NVRAM error" and "Keyboard error" are displayed because the system has a SCSI controller which can only access up to 16 MB of main memory. These errors have no affect on the system. Caution: The address of the SCSI controller must be changed on the 1542A and 1542B when a system is upgraded from a 3/440 to a GPx 640. The changes are as follows: 1542A (long controller): GPx 2/3/440 Jumper J10 has no jumpers. GPx 640 has both jumpers installed on J10. 1542B (short controller): GPx 2/3/440 Jumper 7, pairs 7 & 8 have no jumpers. GPx 640 Jumper 7, pairs 7 & 8 have jumpers installed. This changes the address of the SCSI controller from DC000 to C8000 because the address of the MFC (D8000-DFFFF) overlaps the old SCSI controller address. Caution: To boot the GPx 640 from tape the system must be correctly shutdown, powered-off and rebooted. A tape boot cannot be performed by doing a shutdown and rebooting only. NOTE: When using cpio to backup files to the HCC tape drive, it is recommended to use the 'B' option to write to tape with a block size of 5120. When using a non-default blocksize, the blocksize should be written on the tape. Example: cpio -ocvmudB > /dev/8t Caution: The major:minor number for the device files of the 8mm tape drive are incorrect. The correct numbers are: /dev/8t 11, 144 /dev/8tnr 11, 145 NOTES AND CAUTIONS: To change the major:minor do the following steps as 'super user': rm /dev/8t* mknod /dev/8t c 11 144 mknod /dev/8tnr c 11 145 chmod +w /dev/8t* ln /dev/8t /dev/8t0 ln /dev/8tnr /dev/8tnr0 Warning: Do not configure more than 2 teriminal port at 19.2 baud with XON/XOFF flow control, data will be lost at that speed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg002 Caution: After upgrading to 1.1A, the following message may appear on the BOSS/VX screen twice: --- Press 'CTRL' + 'C' or 'ESCAPE' --- if so, 'vi' /etc/exem and remove the above line so the message will only display once. Caution: The floppy diskette device /dev/dsk/f015d cannot be used to make a floppy based filesystem. The mkfs command will not return an error but mount will fail. Caution: Password aging using MINWEEK and MAXWEEK does not work. Workaround: Use the 'passwd' command to turn off password aging. Enter: passwd -x -1 root (-1 as in the number 1) The '-1' parameter turns off password aging immediately. Warning: When upgrading from 1.0A or 1.0B to 1.0C, 1.0D or 1.1A you MUST delete /usr/mbf/etc/_queues/lpq.que, the printer queue file. The format has changed from previous levels. Warning: 'pformchg' does not print a live data form alignment test if the report uses @ for positioning. If @s are not used a live data form alignment will print. The static data alignment works with or without @s. Warning: The 1/2" MTS and HCC tape drives do NOT detect the End-of-Tape mark when writing to the tape with BASIC, tar or cpio. *This has been fixed in 1.0D. Warning: If /etc/bfsdevs is installed during an O/S upgrade the port configuration will be corrupted. To fix the corruption go into the 'configure' utility and perform a Save and Exit. Warning: After upgrading to 1.0C and 1.0D the internal MODEM port settings may change, so check the port configuration for the internal MODEM in configure. NOTES AND CAUTIONS: Warning: 'pqueue' will display a status of 'unknown' instead of 'formchange' when waiting for a form change. *This has been fixed in 1.1A. Warning: After upgrading to 1.0C you may need to do a chmod 777 /tmp because non-root operators will not be able to logon. Warning: DO NOT configure ports for 38.4K baud rate. This can cause the system to hang. Warning: The PT-4220 serial printer defaults are set incorrectly in the configure utility. The defaults should be: Baud: 9600 Data Bits: 7 Stop Bits: 1 Parity: Odd The PT-4220 serial printer should also have 'despool wait' set to 'yes'. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg003 Warning: The mnemonics for START BOLD and END BOLD are not supported on the PT-4220 serial printer. Problem: Error 31's in CALLed programs. If a CALLed program has an ENTER A$ and within the program A$ is set reassigned A$=A$+B$ then an error 31 is possible. Workaround: After the ENTER A$, set A$ equal to another variable and use that variable throughout the CALLed program, eg. B$. Then before EXITing set A$=B$. Warning: It is possible to have 2 printers named LP. If a serial printer is named LP and a parallel printer is added it can ONLY be LP. The result will be 2 printers being named LP. *This has been fixed in 1.1A. Warning: When installing WordPerfect, a prompt askes for 'Y/N'. The only input accepted in 'y' (lower case). NOTE: DEMON cannot recover from a media error on the 8mm tape drive. NOTE: All files being transported to a 1.0C and above O/S levels, with cread, will have their permissions set to rw-rw-rw-, regardless of the permissions that existed on the previous system. NOTE: DT-4314 terminals configured as a DT-4313 will NOT take advantage of software capabilities designed for the DT-4314, such as boxes. NOTE: The UNX Product on the Operating System tape is included in the Base portion of the O/S on levels 1.0C and higher and will not have to be installed with 'mbfinstall' to run UNIX packages. ATP NOTES AND CAUTIONS: NOTE: To convert the number of blocks into number of MB do the following equation: (# blocks * 512)/1,048,576. Example: 8670 blocks * 512 / 1,048,576 = 4.23 MB A. A BASIC program being transferred with ATP from a GPx to a 1500 system will error on multi-line statements in BASIC. Workaround: Edit the BASIC program on the 1500 after the transfer. B. When using ATP over a modem between an SPx and a GPx, the SPx side must start communications first. C. A STRING file with certain unprintable characters, between $00$ and $1F$, could corrupt when transferred with ATP from a BOSS/VX system to a BOSS/IX system. Change the following programs on the BOSS/IX system: /util/ARP 4205 IF F4<>7 THEN GOTO 4210 ELSE LET R9=0; IF S1=1 THEN WRITERECORD(6,TBL=6900,ERR=4500)R0$(3,S9-2) ELSE WRITERECORD(6,ERR=4500)R0$(3,S9-2) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg004 /util/ATP1 5135 IF F4=7 THEN LET R9=0; READRECORD(6,ERR=6000,END=5700)X9$;. GOTO 5150 D. ATP cannot be started on 2 terminals at 1 time. E. Using ATP to transfer a string file to a system that does not support string files will cause the BOSS/VX system to skip the string file and the destination system to report "Invalid receive file type". F. STRING files will be changed to SERIAL files on a BOSS/VS system with M.6G Operating system or higher G. Using ATP to attempt to transfer Multi-keyed files to a system that does not support MK files will cause the MK file and the following file to be skipped. H. Because SERIAL files are not supported on the MAI-1500, they will be skipped when attempting to use ATP to transfer them to the MAI-1500. I. Avoid giving BQR filelists similar names. If the first 3 characters are similar BQR may become confused and delete some of the BQR filelist names. PC-LINK NOTES AND CAUTIONS: A. PC-Link does NOT support slave printing on the GPx 40, because PC-Link requires an MBF interface. Slave printing will be available on a future release of PC-Link. B. Use BOSS/IX as the system type when running PC-Link on a BOSS/VX system. C. The PC-Link file transfer programs on the GPx 40 must be in UPPERCASE. D. To use "vi" via PC-Link requires that the terminal configuration be at least a DT-4309. The operator can set the terminal by using the following steps: TERM=4309 export TERM E. CTRL+S will hang the PC port when running PC-Link over a modem. To resume operation, hang-up the modem and redial. F. Pressing at the "$" prompt will hang the PC for 30 seconds. TBC NOTES AND CAUTIONS: A. TBC should not be run with less than 8 MB of memory. When running with 4MB of memory a BASIC qcode error is reported. B. Do NOT create a /debug directory. If TBC sees that directory it will create files which may fill the /root partition. *This has been fixed in 1.1A. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg005 C. ESCAPE during a TBC communication may hang the ICC186 controller on 1.0D and lower levels. If an ESCAPE causes a hang or the controller becomes hung the following steps will free it: cd /usr/mbf/comm ./commload -b0 If the controller remains hung the system must be shutdown and powered off and on to free the controller. D. If MAGNET is stopped by removing the RSM process, TBC will also stop running. E. TBC may report an error 26 during a file transfer in transparent mode from GPx to MPx or SPx. The following program changes will prevent this: MPx: .PGMTBC.BRCV 1455 IF T2=1 THEN A9=0; GOTO 1513 SPx: /tbc/BCOM/BRCV 1456 IF T2=1 THEN GOTO 1525 TBC NOTES AND CAUTIONS: F. TBC now supports 2 ports communicating at 9600 bps or 1 port at 19.2K bps. Previous to 1.1A, TBC supported only 1 port communicating at 9600 baud. If 2 TBC ports were running simultaneously they had to communicate at 4800 bps. G. Data in received files should be verified if an Auto-Restart or RVI occurred during a BCOM session. H. A premature termination of a TBC session may be caused by a "TIMEOUT TERMINATION" occurring without waiting for the length of time specified in the TIMEOUT value. I. If a remote system fails because of a dump or power failure or some other catastrophic failure the local system may terminate communication by hitting . J. Device T000 should be removed from the /etc/bfsdevs file because it can cause screen display problems in BCOM. K. If a BASIC program is in a BQR filelist that is to be transmitted by TBC, an error 67 and "sh: checksum : not found" will occur. *This has been fixed in 1.1A. L. The ITP product must be installed with "mbfinstall" if the user wants to use BQR utilities to create TBC transmit queues. M. BASIC error 59 with a system error -657 occurs when attempting to open a TBC comm port and the incorrect TBC public key is installed. N. The full path name must be entered for the destination file when modifying the TBC Transmit Queue for File Transfer. O. TBC may report a BASIC error 95 with a system error -614 and a message "unknown I-Device open error", which is caused by insufficient disk space. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg006 P. When the LSLOG is full, the LSLOG program may go into an infinite loop to locate the last TBC session. Q. The termination sequence ETX/DLE-EOT, which is normal for non-MAI, TBC is treated as abnormal by MAI TBC. TCP/IP NOTES AND CAUTIONS Warning: The FTP application is NOT certified and NOT supported on the 1.1A release for the GPx Series 40. NOTE: Systems that run TCP/IP will display the following messages when the system boots: lo0: flags=29 (UP, LOOPBACK, NOTRAILERS) inet 127.0.0.1 netmask 0xFF000000 dlk flags=63 (UP, LOOPBACK, NOTRAILERS, RUNNING) inet aa.bb.cc.dd netmask 0xFF000000 broadcast aa.255.255.255 The messages originate from 'ifconfig' which runs when the system boots and checks the network configuration. The first line of the message is the optional flags for the interface and the second line is the internet address, the mask and the address for broadcasts to the network. The aa.bb.cc.dd will vary from machine to machine and is the internet address assigned to the system. For more detail see the 'ifconfig' section in the TCP/IP User Guide. 7.5 TERMINAL SERVER NOTES AND CAUTIONS NOTE: Control codes, the CTL-I thru IV and combinations of the CTRL key and another key may be trapped by the terminal server. Workaround: Set the teminals server control codes by using the CLI stty command or the NA "set port" command so the codes do not match. Control codes to be aware of are: - Input start/stop characters - Ouput start/stop characters - Attention character - Telnet ESCAPE character - Erase character/word/line characters Warning: Macros defined in the /usr/spool/ercpd/bfs/macros file will not be recognized. NOTE: The rtelnet and aprint commands are not supported on the GPx Series 40 in the 1.1A release. Warning: The table of contents does not match the order of the Sections of the MAI-NET Terminal Server Network Administrator's Guide, M0221. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB023 Pg007 FIB 00024 01/08/91 *** Command to Print the Man Pages [ WPSF 674 ] *** Type : Informational Purpose This document contains the command line required to send the output from 'man' pages to a printer so the format is readable. Procedure An example of a command that can be used to send the output of 'man' pages to a printer is as follows : $man |col -b |lpr list=P1 The 'col -b' filters out the backspaces and will make the print format readable. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB024 Pg001 FIB 00025 02/18/91 *** Root Partition Fills Up *** SYMPTOM/TEXT: Customer notices that the available space in the root partition is slowly decreasing over a period of days or weeks. There are no user files in the root, just the normal O.S. files. FIX: Check the size of the login file, /etc/wtmp. This file contains login info for every login. It is supposed to get Cleared out when the cleanup programs are run automatically by the system. On this system, it was set up to take place every Sunday. The customer had. The system off every weekend and the file grew to 6MB. To fix, either delete the contents of this file, or log on as root and execute crontab -l. This will show you when these cleanup routines are executed. You can edit /etc/cleanup, to do cleanup jobs differently. For further info., see the UNIX System V/386 System Administrator's Guide. ORIGINATOR: Pete Dobrow & Ed Schmedes SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB025 Pg001 FIB 00026 04/24/91 *** GPx40 /dev Files Problems [ WPSF 660 A1 ] *** GPx Series 40 Dan Arteritano Addendum 660 /dev files problems Type: Problem Purpose: These are two problems with /dev files which are separate and related ------------------------------------------------------------------------------- Symptom: System PANIC during backup of "/" directory. Cause: A Kernel mode trap PANIC may occur when doing a backup of the "/" directory. The PANIC would occur while saving the "/dev" directory. Solution: A full system backup which saves the "/" directory and all its contents is not necessary. A complete backup should include the "/etc" and "/usr/mbf/etc" directories, the application program and data file directories and any Third Party or horizontal products. All other Operating System utilities and files can be retrieved from the O/S Base tape. *This has been fixed in the 1.1B relase of the Operating System. ------------------------------------------------------------------------------- Symptom: The major:minor numbers for the 8mm tape drive device files are defined incorrectly (different problem than above). Field Bulletin 660 has the steps to redefine the device files but the last two steps contribute to PANICS caused when saving "/dev" files to tape (same problem as above). Solution: Do the following steps to redefine the device file: rm /dev/8t* mknod /dev/8t c 11 144 mknod /dev/8tnr c 11 145 mknod /dev/8t0 c 11 144 mknod /dev/8tnr0 c 11 145 chmod +w /dev/8t* ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB026 Pg001 FIB 00027 03/05/91 *** 1.1A Available for GPx70 Series *** GPx Series 70 Wally Moore 02/27/91 Release of 1.1A Type: Informational Level 1.1A of BOSS/VX for the GPx Series 70 is now available. This release is the recommended Operating System for the GPx Series 70 Systems. The 1.1A Operating System is derived from the 1.0A O.S, and contains the following new features and enhancements: UPD Simple Compiler On-Line Backup CISAM/BFS User Access of BFS C-Library Functions New File Write Options Auditor's Log Book Errorlog Monitor Bad Block Mapping lphold Command New dct scripts * Ethernet and TCP/IP * 2780/3780 Batch Communication SMD 8" Disk Drives * 8MM HCC Tape Drive 1/2" MTS Tape Drive * New Parallel Printer Controller On Line Configure * are not released at this time but are expected to be released soon. The Software Announcement, which contains general information about the Level 1.1A BOSS/VX Operating System, will be available shortly. For information on ordering new Software and Hardware in 1.1A see Marketing Announcements 1006 and 1015. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB027 Pg001 FIB 00028 03/06/91 *** 1.1A Software Announcement for GPx Series 70 [ WPSS 190 ] *** 1.0 INTRODUCTION Level 1.1A of BOSS/VX for the GPx Series 70 is now available. This release is the recommended Operating System for the GPx Series 70 Systems. The 1.1A Operating System is derived from the 1.0A Operating System and contains the following new features and enhancements: UPD Simple Compiler On-Line Backup CISAM/BFS User Access Of BFS C-Library Functions New File Write Options Auditor's Log Book Errorlog Monitor Bad Block Mapping lphold Command New dct scripts Ethernet and TCP/IP 2780/3780 Batch Communication SMD 8" Disk Drives 8mm HCC Tape Drive 1/2" MTS Tape Drive New Parallel Printer Controller On Line Configure This Software Announcement contains general information about the Level 1.1A BOSS/VX Operating System. Installation and update procedures are fully documented in this announcement. Also, this document has sections on new features and enhancements/corrections. It is recommended that you read this document before installing Level 1.1A. For information on ordering new Software and Hardware in 1.1A see Marketing Announcements 1006 and 1015. TABLE OF CONTENTS 1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . .Cover 2.0 BOSS/VX OPERATING SYSTEM HISTORY . . . . . . . . . . . . . . . . . . . 1 3.0 NEW SOFTWARE PRODUCTS IN LEVEL 1.1A. . . . . . . . . . . . . . . . . . 1 3.1 UPD SIMPLE COMPILER . . . . . . . . . . . . . . . . . . . . . . . 1 3.2 ON-LINE BACKUP. . . . . . . . . . . . . . . . . . . . . . . . . . 1 3.3 CISAM/BFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.4 USER ACCESS OF BFS C-LIBRARY FUNCTIONS. . . . . . . . . . . . . . 5 3.5 WRITE OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.6 AUDITOR'S LOG BOOK. . . . . . . . . . . . . . . . . . . . . . . . 6 3.6.1 WHAT ALB LOGS. . . . . . . . . . . . . . . . . . . . . . . 6 3.6.2 WRITE OPTIONS AVAILABLE WITH ALB . . . . . . . . . . . . . 8 . 3.6.3 UTILITIES CHANGED FOR ALB. . . . . . . . . . . . . . . . . 8 3.6.4 SWITCHING LOG FILES. . . . . . . . . . . . . . . . . . . .10 3.6.5 TECHNICAL ASPECTS OF ALB . . . . . . . . . . . . . . . . .11 3.6.6 ALB DIFFERENCES. . . . . . . . . . . . . . . . . . . . . .13 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg001 3.7 ERRORLOG MONITOR. . . . . . . . . . . . . . . . . . . . . . . . .14 3.7.1 ERRORLOG WATCHER INSTALLATION INSTRUCTIONS . . . . . . . .14 3.7.2 CONFIGURING ERRORLOG WATCHER . . . . . . . . . . . . . . .14 3.7.3 STARTING ERRORLOG WATCHER. . . . . . . . . . . . . . . . .16 3.7.4 SEEING THE RESULTS FROM ERRORLOG WATCHER . . . . . . . . .17 3.8 BAD BLOCK MAPPING . . . . . . . . . . . . . . . . . . . . . . . .18 3.9 LPHOLD COMMAND. . . . . . . . . . . . . . . . . . . . . . . . . .18 3.10 NEW DCT SCRIPTS . . . . . . . . . . . . . . . . . . . . . . . . .19 3.11 ETHERNET AND TCP/IP . . . . . . . . . . . . . . . . . . . . . . .20 . 3.12 2780/3780 BATCH COMMUNICATION . . . . . . . . . . . . . . . . . .23 3.12.1 SOFTWARE REQUIREMENTS AND INSTALLATION . . . . . . . . . .24 4.0 NEW HARDWARE PRODUCTS IN LEVEL 1.1A. . . . . . . . . . . . . . . . . .24 4.1 NEW TAPE AND DISK DRIVES. . . . . . . . . . . . . . . . . . . . .24 4.2 SYNCHRONOUS COMMUNICATION CONTROLLER (SSC). . . . . . . . . . . .25 4.3 ETHERNET LAN CONTROLLER (ELC) . . . . . . . . . . . . . . . . . .34 4.4 DUAL CHANNEL CONTROLLER (DCC) . . . . . . . . . . . . . . . . . .36 4.5 CABLE ROUTING BOARD (CRB) . . . . . . . . . . . . . . . . . . . .37 4.6 PARALLEL PRINTER CONTROLLER (PPC) . . . . . . . . . . . . . . . .37 4.7 VME (I/O) BUS CARD CAGE BOARD PLACEMENT . . . . . . . . . . . . .39 4.8 CHANGES TO THE REMOTE ENABLE/DISABLE SWITCH FUNCTIONALITY . . . .39 5.0 ENHANCEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 5.1 ON-LINE PORT CONFIGURATION. . . . . . . . . . . . . . . . . . . .40 5.2 USER SCRIPTS. . . . . . . . . . . . . . . . . . . . . . . . . . .40 5.3 ERROR LOG CHANGES . . . . . . . . . . . . . . . . . . . . . . . .41 5.4 NEW PARAMETERS TO USE WITH THE /ETC/DUMP COMMAND. . . . . . . . .42 6.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES . . . . . . . . . . . . . . . . . . . . . . 2.0 BOSS/VX OPERATING SYSTEM HISTORY 1.0A First release of the Operating System for the GPx Series 70. Supported the 5070 and 6070. 3.0 NEW SOFTWARE PRODUCTS 3.1 UPD SIMPLE COMPILER Universal Printer Driver (UPD) is a software subsystem that provides printer support for all MAI system. It is now available on 1.1A and requires a public key for use. o SIMPLE Compiler: Reads driver source code and generates interpretive object code which, when executed, processes a stream of data for delivery to a specific printer. o Printer Definition Files (PDFs): The object code produced by the SIMPLE compiler. MAI provides one PDF for each model printer it supports in the /usr/mbf/etc/ptrtbl directory. o UPD Interpreter: Interprets and provides runtime support for PDFs. PDF source code is platform independent, but the interpreter is programmed for a specific host. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg002 o DESPOOLER: Part of the host operating system that opens print files, reads data records and delivers them to the UPD Interpreter for processing by the PDF. o TRANSLATION FILE: Translates the data received to what the printer understands. Refer to the Universal Printer Driver Reference Manual, M0053 for detailed instructions. 3.2 ON-LINE BACKUP On-line backup provides the ability to backup one or more files while the files continue to be accessed by users. This is performed in such a way that the integrity of the backup copy is maintained. The backup may be made to any tape device or to another disk. The cpio command includes a new option, -J. A new utility, olb, provides support for Cross-File Integrity (explained below). On-line backup is made possible by the use of a technique called journaling. Journaling is used when a file is being backed up and modified at the same time. The original data in the file is "shadowed" or set aside for use by the backup utilities. Thus, an application has the new records available to it while the backup utility accesses the shadow records. When the shadow copy is no longer needed, it is deleted. File Integrity A group of files can be backed up using one of three methods. The first two methods, File Integrity and Extended File Integrity, allow the files to change in relationship to each other. The third method, Cross-file Integrity, backs up a group of files in such a way that they are unchanged relative to each other. File Integrity is preserved by the cpio command. The cpio command can be used to backup one or more files using the journaling technique. Since cpio processes one file at a time, journaling is used on each file in turn, guaranteeing the integrity of each file as it is backed up. The effective time of the "snapshot" of each file in the filelist will be different, and depends on the position of the file in the filelist. Thus, it is possible to make a multi-file update, and have a backup which includes the change made to one file but not to the others. For example, suppose a client data base consists of three interrelated files. The first may contain the client name, the second the client address, and the third the client phone number. An on-line backup is started by invoking cpio on the three files with the journaling option. After the name file is backed up, while the address file is being backed up, and before the phone number file is backed up, a client is deleted from the data base, removing a record from each of the three files. The backup will have the client's name and address, but not the phone number. The data in the backup is therefore inconsistent. The olb utility provides Extended File Integrity, which narrows the window when the data is inconsistent. olb starts journaling on all of the files in the file list, then starts the specified backup process. Journaling is stopped after the backup process is complete. Changes made to a file before olb starts journaling will be backed up, while those made after olb starts journaling SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg003 will not be. A window exists from the time olb is started on the first file to the time journaling is started on the last file. This window is much smaller than in the previous example. Cross-file Integrity exists when the user guarantees that there will be no multi-file updates to the data during the time olb starts journaling on a group of files. Since the BOSS/VX Operating System has no method of determining when all files are in synchronization, guaranteeing file synchronization is the user's responsibility. Some suggestions on how to achieve file synchronization follow. To create a backup with Cross-File Integrity requires several steps: 1. Stop the application from making changes to the files being backed up, 2. Invoke olb to start journaling on all files "simultaneously," 3. Wait until olb starts the backup using cpio with journaling, 4. Release the application so that modifications may continue. The first step of synchronizing the application is done prior to invoking olb. The actual method used will be tailored to the application. Some possibilities are: o User logoff - the simplest method; all users would be voluntarily or forcibly logged off the system until journaling has been started on all files. o Menu lock - prevent operators from starting new transactions . by locking them in a high level menu. The synchronization program would wait until all operators were locked in a safe . menu. o Transaction boundaries - similar to menu lock, but could involve massive application changes. This technique amounts to making the application perform rudimentary transaction processing. At the beginning of each "transaction," the application would check for an "olb synchronization request" and wait until authorized to continue, and then register "in transaction." At the end of the transaction, it would change its status to "not in transaction." o Batched updates - file modifications would be made to a special set of temporary files during synchronization. The application would have to be modified to switch over and back. This method is practical only if file I/O is centralized. The second, third and fourth steps of guaranteeing Cross-File Integrity would be performed by invoking olb on a shell script instead of an individual cpio command. The shell script would be executed after olb had started journaling on all files to . be backed up. The shell script would restart the application, reversing whatever technique was used to synchronize the application, before invoking cpio with journaling. cpio -J Journaling is employed by using the -J option, which has been added to the standard UNIX backup utilities. This option is initially provided for cpio only. The -J option causes the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg004 file system to start journaling and access the shadow records. If journaling was already in effect, the program "sees" the file as it was when journaling was first started. When cpio is used with -J but without olb, journaling for each file is started when it is first accessed by cpio, and is stopped when cpio moves to the next file. Backing up with Extended File Integrity is provided by using the new olb utility in conjunction with cpio. olb accepts a list of files requiring journaling from standard input, then executes a user specified command. The command is responsible for performing the backup. System Performance The impact of On-Line Backup on the system is a function of the amount of data being backed up, the degree of Cross-File Integrity requested, and the amount of file modifications made to the files which are in journaling mode. The impact of using olb may include reduced system throughput, using large amounts of additional disk space and using up inodes. To minimize the impact on system performance, olb, like any other backup utility, is best used during non-peak hours. In addition, the use of the Cross-File Integrity feature should be minimized by choosing the smallest set of files that must be synchronized for backup. Backing up large sets of files with the olb utility will result in all files being opened simultaneously in journaling mode which may exhaust some system resources. olb uses a file pointer for each file with journaling turned on. Until journaling is turned off that file pointer is not available for other use. Therefore, the DCT maximum number of open files parameter may need adjusting in environments where file use approaches the maximum number of open files. For further information, see the manpages for cpio(1) and olb(1). 3.3 CISAM/BFS CISAM/BFS functions are used to create, maintain and manipulate primarily multikeyed files from 'C'. It is also possible to open and manipulate direct and sort files that were previously created. The CISAM/BFS library has to be linked with the user program to perform all tasks necessary for the maintenance and manipulation of a user defined indexed file system. These functions provide for: o the creation of files and associated primary indexes o the addition and deletion of further indexes o the opening, closing and deletion of existing files o the selection of the index to be used for subsequent reading and/or writing of records and the start point within the file o the reading, writing and updating of data records o the random and sequential access of records within an indexed file o locking of individual records, groups of records or whole files SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg005 3.4 USER ACCESS OF BFS C-LIBRARY FUNCTIONS BFSINT (BASIC File System INTerface) is a library which provides a set of C-callable procedures for applications which require record level access to BFS files. Access to files may be by KEY or INDEX, and locking/timeout control is performed using options which are similar to those found in Business BASIC. Record level access includes the ability to create, delete, open, close, lock and unlock files. Multi-keyed file create and MAGNET remote access are not supported on the initial release. Refer to the BFSINT Reference Manual, #M0228 for detailed information. 3.5 WRITE OPTIONS Business BASIC data files now can have write-through capabilities similar to BOSS/VS. BOSS/VX implements three different types of write-through as described below. Buffered Write This method buffers each write in memory before it is written out to disk. Each buffer is automatically flushed out to disk every 30 seconds or when the file is closed. Writes with the buffered option return immediately to the user after the data has been written to a buffer in memory. Write Thru When file write thru is in affect all writes are written directly to disk. With the write thru option each write operation waits until the write to disk has completed before it returns. Although this method eliminates the small 30 second window of the buffered option, a performance penalty will occur with its use. Async Write The async write option is not as costly as the write thru, but not as fast as the buffered write. Async write means that on each write operation, the memory block is marked for immediate write to disk, but the user does not wait for the write to disk to complete before the write operation returns. Utility Changes The 'fcreate' and 'fchange' utilities have an added option 'Source File Write:' which allows the user to select which of the three write modes should be used for the file. The 'finfo' utility has an added field 'SOURCE FILE WRITE' to show which of the three writes modes the file is using. 3.6 AUDITOR'S LOG BOOK ALB is a new feature, for the GPx Series 70, that provides automatic audit information recording capability. It is a means of storing the modification history of a data file, and is based on the MPx ALB feature. The Auditor's Log Book supports the following data file types: Indexed, Direct, Sort and Multi-keyed. ALB does not support Serial, String or Business BASIC program file types. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg006 3.6.1 WHAT ALB LOGS Audit logging is selected on a file by file basis. Two separate log files, primary and backup, are maintained for each source data file for which logging is requested. The primary log file is where all record updates to the source file are recorded. The backup log file is used occasionally to hold the primary log file's data for archiving when the primary log file becomes full. The types of file/record operations that are logged by ALB are: o Addition of a record o Rewriting of a record o Deleting a record o Turning Audit logging ON or OFF o Turning Audit Write Thru ON or OFF o Turning Audit Write Ahead ON or OFF o Renaming the data file o Erasing the data file o Switching the primary and backup log files The types of file/record operations that are NOT logged by ALB are: o Reads/extracts of a record o Addition of key sets to a multi-keyed file o Changes to the number of records in a file There are two types of log entries that can be made to a log file. They are based on the type of modification being made. Information that is logged on a record basis includes: o A code denoting the type of operation o The user ID number of the person who made the modification o The group ID number of the person who made the modification o The process ID number of the process that made the modification o A date stamp denoting the date and time the modification occurred. The date recorded on the GPx systems is the systems Greenwich Mean Time (GMT). o On indexed files, the index number of the record being modified. On a direct or sort file this field will be null. On a multi-keyed file this field will contain the record length. o On write or rewrite operations, a copy of the new data that is being written to that record, and on remove operations, a copy of the old data being deleted, are appended to the end of the log entry. Information that is logged on a file basis includes: o A code denoting the type of operation o The user ID number of the person who made the modification o The group ID number of the person who made the modification o The process ID number of the process that made the modification o A date stamp denoting the date and time the modification occurred. The GPX systems is the systems Greenwich Mean SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg007 Time (GMT). ALB environment The ALB features can be used on the GPx Series 70 systems from: o BASIC - Audit logging from BASIC is transparent to the user. If logging is started for a file and turned on, all writes to that file will automatically be logged. There is one exception, if the source file is opened with an 'isz=' clause, an error will be returned. There are no changes to syntax in any of the BASIC commands to support the ALB feature. o BOSS/VX System Utilities - All Audit logging facilities, e.g. start/stop audit logging, are modified from the System Utilities. NOTE: ALB is only supported by commands that utilize the bfs file system, as with Business BASIC and the system utilities. Modifications made outside of the bfs environment to the data or log files, such as the UNIX commands 'cp', 'mv', 'rm' etc., are not logged in the . log file and may cause problems in later operations of the ALB features. 3.6.2 WRITE OPTIONS AVAILABLE WITH ALB ALB log files have the same three write options that are available for other Business BASIC files: Buffered Write, Write Thru, and Async Write. 3.6.3 UTILITIES CHANGED FOR ALB File level modifications are made for ALB via the MAI system utilities. Each of the following utilities were changed to include options that support audit logging for a data file. fcreate The 'fcreate' utility provides four additional parameters for logging: Audit Logging: This allows the user to specify if record updates to the source data file need to be logged. Turn logging ON or OFF. If logging is turned ON the next three options will be displayed. Audit File Name: This option allows the user to specify in which directory the log file is to be created. Once the directory name is entered or CR for the current working directory, the primary auditlog file is created. The new log file will be the same name as the data file with the addition of a suffix '.aud'. Audit File Write: This option allows the user to select which of the three SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg008 write modes should be used for the log file. Audit Log Records: This option allows the user to specify the maximum number of records in the primary log file. The default is 2 times the number of records in the source data file. If logging is started from 'fcreate' a log entry will be added to the log file. fchange The 'fchange' utility provides the same four additional parameters as above and one more parameter: File Switch: If a backup log file exists a YES value will display, if a backup log file does not exist then a NO value will be displayed. If a NO value is displayed the user can select to switch log files. Once the switch is complete, a YES will be displayed. After each change has been made to the source or log file a log entry is added to the log file to record the change that has taken place. There are no log entries for changes to source file write options or changes to the number of log records. finfo 'finfo' has been enhanced to display the audit log information of the data file. The following display lines have been added: AUDIT LOGGING.... AUDIT FILE WRITE. AUDIT FILE NAME.. AUDIT LOG RECORDS fcopy If an audited file is copied, its log files will not be copied to the destination directory, only the default log file name will be defined within the file header. The copy operation will not be logged. Any updates to the destination file will be logged within a newly created log file, or in an existing audit log file. If the log file is copied, the default source file name will be defined within the log file header even in the case that the source file does not exist. ddisplay A new column, AUDIT/WRITE, has been added to the 'ddisplay' utility display. AUDIT/WRITE column contains two items: o The 1st will denote if auditing is started or not. If auditing is started, an 'A' will display otherwise the space will be blank. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg009 o The second will denote the type of write mode assigned to the file, WT for Write Thru, BW for Buffered Write and AW for Async Write. An additional file type of 'aud' will be displayed for audit log files. fdelete The deletion of a source data file does not automatically delete its log files. The deletion of a source data file which has logging enabled causes a log entry to be written to the log file. frename 'frename' utility automatically renames the source data file and its primary and secondary log files. The file name pointers within the header are also updated. Explicit renames of individual log files are allowed. If a log file is explicitly renamed, no change is made to the file name pointer within the file header of the source file or log file. fmove 'fmove' utility automatically renames the source data file and its primary and secondary log files. The file name pointers within the header are also updated. Explicit moves of individual log files are allowed. If a log file is explicitly moved, no change is made to the file name pointer within the file header of the source file or log file. 3.6.4 SWITCHING LOG FILES In the event that the primary log file becomes full and cannot grow, or it is desired to backup the log file, a switch operation may be performed. The actual switch is done in the bfs file system by the following series of operations: link of the primary file name to the backup file name, delete the primary file then create a new primary file. The backup log file will be the same name as the log file, but will have a '.audbak' suffix similar to the primary log files '.aud' suffix. Example: primary log file name '/usr/alb/logfilename.aud' backup log file name '/usr/alb/logfilename.audbak' There are two types of switch operations, manual and automatic. Manual Switch A manual switch operation is done via the 'fchange' utility. This is done by selecting the File Switch option from the fchange utility menu. If the parameter to the right of this option is NO, a manual switch can be done by answering yes to the prompt. After the switch is complete a YES will appear to the right of the File SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg010 Switch option. If the parameter to the right of this option is YES, this means that there is already an active backup log file for that source file. In order to continue with the manual switch the backup log file must be either backed-up to tape and then deleted or moved to another directory. Once the backup log no longer exists in that directory the manual switch can proceed as in the above paragraph. Automatic Switch The automatic switch is performed by the filesystem to switch the primary log file with the backup log file. An automatic switch is done automatically by the file system when the primary log file is full so that the user can proceed with normal file operations without having to run the fchange utility. An automatic switch takes place when the primary log file is full and another operation is performed on the source file which requires a log file entry. As with the manual switch the backup log file must not exist in the primary log file directory. Notification of Switch Operation For every manual or automatic switch operation a 'mail' message will be automatically sent to the 'root' system administrator. The mail message will contain the time, date, user ID, type of switch operation (manual or automatic) and the complete filename of the source data file. 3.6.5 TECHNICAL ASPECTS OF ALB Format of the Log File The ALB log files, both primary and backup, are indexed file types. An indexed file was chosen because it has a fixed record length and it is easy for user applications or Origin to generate reports. The following is the format of the log entry: +---------------------------------------------------------------+ |Format|Op|Filler| User|GrpID|Proc| Date | Time |Misc|Data | | | | | ID | | ID | | (GMT) | | | +---------------------------------------------------------------+ | | | | | | | | | | | | 0 |A | Nil |123 |101 |2345|01/23/90|05:07:45| 4 |Rec 4 |. | | | | | | | | | | | +---------------------------------------------------------------+ Format level: 1-byte character; The format level for the log record. Its value will be 0 for 1.1A. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg011 Operation: 1-byte character; Type of operation performed on the data file. 'A' Addition of a record. 'W' Rewriting of a record. 'D' Deleting a record. '1' Turn Audit logging ON. '0' Turn Audit logging OFF. 'Y' Turn Audit WriteThru ON. 'N' Turn Audit WriteThru OFF. 'a' Turn Audit WriteAhead ON. 'd' Turn Audit WriteAhead OFF. 'R' Rename the data file. 'E' Erase the data file. 'S' Switch the primary and backup log files. Filler: 6-byte filler; This field is used to accommodate potential log expansion in the future. User ID: 16-byte string; Owner's user identification number. Group ID: 16-byte string; Owner's group identification number. Process ID: 8-byte string; Process identification number. Date: 8-byte string; This field is used to record the date the event occurred. The format will be the current system date format, which is either 'MM/DD/YY', 'YY/MM/DD' or 'DD/MM/YY'. Time: 8-byte string: This field records the time the event occurred. The time used is the system's. Greenwich Mean Time (GMT). This was done to save the time it took to convert from GMT to local time. The format is 'hh:mm:ss'. Misc: Short integer(binary); For multi-keyed files, this field will indicate the record length. For indexed files, this field contains the record index number. For direct or sort files, this field will be null. Data Record: Variable length: This field contains the record image. For an indexed file, the record image will be the data record. For a direct file, the record image will contain the key value followed by the data record. For a sort file, the record image will be simply the key value since sort files are direct files with the record size equal to zero. For a multi-keyed file, the record image will be the data record. 3.6.6 ALB DIFFERENCES BOSS/VX and BOSS/VS Differences: o GPx supports source and log file Async Write, MPx does not support Async Write. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg012 o DIR utility on MPx displays the audit log file as type indexed, where the 'ddisplay' lists the file type as 'aud'. o CREATE utility on MPx will define both the primary and backup log files at the time the source file is created and logging is started. 'fcreate' on GPx will only define the primary log file, the backup log file will be defined during a switch operation. The same situation occurs when audit logging is started from UPDATE and 'fchange'. o Save/Restore: MPx has special handling of source and log files during the save/restore processes. GPx has no special procedures for ALB files. All files to be backed-up must be specified in the proper backup filelist. 3.7 ERRORLOG WATCHER Errorlog Watcher is a program that runs as a background task and monitors the system for excessive disk, tape, printer, and asynchronous ports errors. If Errorlog Watcher detects an excessive. amount of errors, then a message is broadcast and mailed to specific users. The user then can take immediate action to remedy the situation. This product is designed to catch errors before they become major problems. 3.7.1 ERRORLOG WATCHER OPERATING INSTRUCTIONS Errorlog Watcher consists of 3 programs: we - Actual Errorlog Watcher program weconfig - Errorlog Watcher configuration program werep - Errorlog Watcher report program The Errorlog Watcher programs are on the diagnostic tape. To install follow "mbfinstall" instruction, installing the WTR package. WTR does require a key to work. To run any of the above programs, the user should be in the directory where Errorlog Watcher is installed. Presently, Errorlog Watcher is under /usr/mbf/diag/watch when installed by "mbfinstall". 3.7.2 CONFIGURING ERRORLOG WATCHER Associated with each item that Errorlog Watcher monitors is an LIMIT and a WARNING LIMIT. The LIMIT is the number of errors required to flag that particular device in the Errorlog Watcher report program. The WARNING LIMIT is the number of errors required to make Errorlog Watcher broadcast . and mail a warning message to the users. Each device has it's own configurable LIMIT and WARNING LIMIT. To configure Errorlog Watcher, just execute "weconfig" by typing: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg013 weconfig "weconfig" will create several configurations files, one for . each type of device. These files are used to store the LIMIT and WARNING values of each device. All files created by any program in Errorlog Watcher will have the extension ".f" at the end. If the configurations files already exist, Errorlog Watcher will not create new files to replace old files. Thus, if a device is added or removed from a system, its' configuration file needs to be manually removed by the user for the system to create a new configuration file for that device. Running the weconfig will cause the following menu to be displayed: ERRORLOG WATCHER CONFIGURATION 1. Modify sleep time 2. Modify time period 3. Modify user mail list 4. Modify limits 5. Exit (MB_IV) Enter option: _ Option #1 "Modify sleep time" will change the time that Errorlog Watcher sleeps between checks. The value defaults to 30 minutes. After selecting this option, the prompt: Current sleep time is xx minutes. Enter new sleep time (1-255) (CR=xx): _ will appear. Pressing will leave the value the same. The user can also enter the number of minutes for Errorlog Watcher to sleep between checking the system. The range is 1-255 minutes. Option #2 "Modify time period" will change the time that Errorlog Watcher looks back in hours. When Errorlog Watcher awakens, it will scan through the file /etc/error.log for a given time period. That time period is from the current time minus the "time period" hours. So if this value is 24, then Errorlog Watcher will always look at the previous 24 hours for errors. When this option is selected the prompt: Current period time is xx hours. Enter new period time (1-720) (CR=xx): will appear. Pressing will leave the value the same. The user can also enter a new value. The default is 24 hours. The range is 1-720 hours. Options #3 "Modify user mail list" is used to determine which users will receive the warning message when sent by Errorlog Watcher. When this option is chosen, the prompt: Current mail list is: xxxxx Enter new mail list (CR=same as current): _ SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg014 will appear. The values for these are limited to ten characters and can be any valid user login (i.e. root, sa, etc.). Presently, the program doesn't check for validity of the user list input. The default user list is "root". Options #4 "Modify limits" will allow the user to change the . limits and warning limits for each device. Once this option is chosen, the following screen will be displayed: 1. Modify disk limits 2. Modify tape limits 3. Modify printer limits 4. Modify comm port limits 5. Modify 8/16way limits 6. Exit/(MB_IV) Choosing one of these options allows the user to change the values for a given area. For example, when #2 is chosen, a screen will ask which type of tape drives the user wishes to change, 1/4", 1/2", or 8mm. Then the number of tape drives for the particular device will be displayed along with its limit and warning limit. At the prompt a tape number can be entered and new limits and warning limits are entered. The changes are always done in pairs, limit and warning limit. If the user wants to keep the current value then press CR when prompted for a new value. If the device is not connected or is incorrectly configured, the user will not be able to set up the LIMIT and WARNING for that device. To exit any screen, press CTL_IV. The disk, printer, comm port and 8/16way limits screens work the same. 3.7.3 STARTING ERRORLOG WATCHER Errorlog Watcher is started simply by typing the command as follows: we& The command above will start Errorlog Watcher in background mode. Errorlog Watcher will run continuously until it is stopped by the "kill" command or when the user logs off. To keep Errorlog Watcher running even after the user has logged off, start Errorlog Watcher with the following command: nohup we& To have Errorlog Watcher started when the system is boot use 'vi' to create the file /etc/rc2.d/S85errwatch'. The file should contain: #TO START ERRORLOG WATCHER AT BOOT echo "Starting Errorlog Watcher" /usr/mbf/diag/watch/we& When Errorlog Watcher is started, it will initialize all configuration files if this has not already been done by first . running "weconfig", then after the amount of time specified in the sleep time has passed, Error will wake up to run its' SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg015 first active cycle and check for errors in /etc/error.log. 3.7.4 SEEING THE RESULTS FROM ERRORLOG WATCHER While Errorlog Watcher is running and it detects a warning limit has been exceeded, a message will be displayed and mailed to all users specified in the users list. The message will contain the time, the number of error count and the device that needs attention. Errorlog Watcher activity can also be monitored by the "werep" program. This program displays the information gathered by Errorlog Watcher on its' last run. The report will show the number of disk, tape, async. port and 8/16way card errors. If any value exceeds the limit specified in the configuration, then that value will have an asterisk ("*") next to it indicating that the device requires attention. The current time and the time when Errorlog Watcher was last active will be displayed in the upper left corner of the error report. To run error report, type in the command as follows: werep Error report will only be available after Errorlog Watcher first active cycle. If the user attempts to run "werep" before Errorlog Watcher become active, the error report will not be available or will be empty. All errors are stored in the file "wderror.f". If this file already existed when the user starts "we", then Errorlog Watcher will erase this file and create a new one. Note that Errorlog Watcher only updates the error count of a device when the device reports an error. Therefore, if the device gets 5 errors during Errorlog Watcher first active cycle and no error in the second active cycle, the error report will still show that 5 errors exist. If the device has 5 errors in the first cycle and 2 in the second cycle, the error report will show 2 errors exist. When the faulty device has been fixed, and the user wants to clear the error report, the error file "wderror.f" should only be cleared by re-starting "we". 3.8 BAD BLOCK IDENTIFICATION (bbmap) A new command exists (bbmap) that will map a physical disk block into a file that contains that block. This allows the identification of files affected by bad blocks so that those files may be checked for integrity problems. On previous releases, if a sector went bad, there was no way of knowing what file occupied that sector. With this new command, a user knows exactly what file is affected so that the appropriate action can be taken to insure its integrity. To use bbmap, first use the mbf_errorlog command. This command will report the disk unit number and the physical block numbers that have disk errors. If the errors are non-recoverable, the user can run bbmap to determine the file that resides on the bad blocks. If the bad block reside in a data file, the user should run DIVE to map out the block. Then frepair can be run to repair the file SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg016 or restore the backup copy. If the bad block resides in the file system i-node area or super-block free list, the user should run DIVE to relocate the bad block, then run fsck to repair the file system. bbmap generates the file path name(s) from physical block numbers. The usage is as follows: bbmap -b number(s) device - number(s) is the block number that you wish to determine the file residing on that block. - device is the disk which is being searched. Example: bbmap -b 11111 disk0 displays: 11111 block in file /bin/make NOTE: Certain conditions may not be recoverable under fsck and could result in some loss of data. 3.9 lphold COMMAND The lphold command is designed to keep a printer assigned to one user until the user frees the printer. A print job can be completed and the printer closed but no spooled jobs will print until the lphold command is given again. Previously OPTS="-off" was used in the OPEN statement to turn off spooling. The problem with that method was that once the printer was closed, any spooled print jobs would print immediately which could print on special forms. OPTS="-off" is still supported. lphold will stop all print jobs to a printer until the lphold command is issued again to start despooling the print jobs. Following are the steps for using lphold: Within a BASIC program you can issue the command: 10 system"lphold list=LP hold=6" The default hold priority for a spooled printer is 2. The default print priority for a spooled print job is 5. By making the printer's hold priority 6, with the lphold command, jobs will not despool. Open the printer with spooling off and print the information: 20 OPEN (1,OPTS="-off")"LP" 30 PRINT (1) "Report Heading" 40 .... Once the job is complete and the printer can be released back to the spooler, CLOSE the printer and reissue the lphold command: 9000 CLOSE(1) 9010 system "lphold list=LP hold=2" 9020 OPEN(1)"LP"; CLOSE(1) The OPEN and CLOSE on line 9020 are needed to restart the despooler and print any jobs in the print queue. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg017 NOTE: The OPEN alone will start jobs printing. So take that into consideration, as the operator may have to change the paper before the spooled jobs start again. 3.10 NEW dct UTILITIES BOSS/VX for the GPx Series 70 contains three new commands that allow a user to view their systems configuration, installed packages and to customize their system's dct parameters for their systems configuration. The commands are: /etc/newdct: A script which uses the amount of memory on the system and passed parameters to create a dct. /etc/packages: A script which prints information about the software packages installed on the system. /etc/prtcfg: A script which prints information about the system resources. prtcfg Shows the number of disks, partitions, inodes, serial and parallel printers, terminals, ghost tasks, slave printers, log on accounts, and lan boards on the system. There are cases where the information is misleading, such as people sharing logons, disks not accessible, printers configured as terminals. packages [-id] Shows the names and optionally installation date and description of each software package installed that created an /usr/mbf/etc/level file. newdct [lots of options -help: shows on-line help] Takes information from a file or command line and creates a dct for the system described. Both man page and on-line help are available for more information on the different options. Examples: Below are examples of using newdct to create dcts for a system. NOTE: You must be root to use these examples. Make and install a dct for the current system: prtcfg > /tmp/data packages >> /tmp/data newdct -f /tmp/data >/tmp/dct.asc mkdct -o /etc/dct -f /tmp/dct.asc NOTE: In the above example the command: prtcfg | packages | newdct > /tmp/dct.asc can be used to replace the first three commands. Make and install a dct for the current system, but overriding the number of users: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg018 prtcfg > /tmp/data packages >> /tmp/data newdct -f /tmp/data -users 56 >/tmp/dct.asc mkdct -o /etc/dct -f /tmp/dct.asc Make and install a dct for a 48 MB system: newdct -memory 48 > /tmp/dct.asc mkdct -o /etc/dct -f /tmp/dct.asc 3.11 ETHERNET AND TCP/IP TCP/IP (Transmission Control Protocol/Internet Protocol is a powerful communications Protocol that has become an industry-standard for linking multiple system and devices from many different manufactures. TCP/Ip is being made available as an option on the GPx Series 70 running BOSS/VX 1.1A to facilitate expanded terminal connectivity via Ethernet-based terminal servers. The usual method for allowing dynamic configuration of BASIC device names (B-name) calls for random allocation of a Tnnn name (within a range) each time a remote terminal logs on and accesses BASIC. This means that the terminal number assigned will be different from login to login. BOSS/VX for the GPx Series 70 1.1A provides the ability to assign a B-name (e.g. T123) to a specific port on terminal server. See Constant Ethernet Terminal Names below. In addition, Slave printers are supported off the terminal server. All that is required for slave printer support is to connect an ISP printer to your terminal and then open the printer with Lnnn, where nnn=terminal number. For more information on TCP/IP networks and terminal servers, please refer to Marketing Announcements 1006 and 1015. For information on . the Ethernet controller see Section 4.3 of this announcement. For installation instruction see Section 6.7 of this announcement or Section 1.7 of the installation instructions provided with the OS tape. Constant Ethernet Terminal Names As stated above, BOSS/VX version 1.1A for the GPx Series 70 provides. the ability to assign a B-name to a specific port on a terminal server. By setting up three files, the user can cause specific terminal server ports using a specific connection ports to be assigned a specific Tnnn name. Restrictions Only a one-to-one mapping of terminal server ports to B-names is supported. If more than one terminal server port is assigned to one B-name, only the first valid entry will be accepted. Any port on the terminal server will be able to access any Connection Port and be assigned the B-name associated with that terminal server, Connection Names combination. If the B-name is already in use, the second BASIC session attempting to use the B-name will not be able to use BASIC. This feature is only available through telnet. It is not available through rlogin. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg019 Configuring Static B-Device Names The administrator must set up the following files on the host system: /etc/remote.in This file will be created on the system for the purpose of making static assignments. Its relates the terminal server name, Ethernet port name and BASIC terminal name. The format of each record is: server_name:port_name: BASIC_terminal_name For example, a record may contain: serverl:port5:T999 The server must be defined in etc/hosts. /etc/inetd.conf This file contains the names and parameters for the services defined in /etc/services. The format of each record is: servicename type protocol wait/nowait user program arguments For the purpose of setting constant remote port numbers, this file contains records for ports 1 - 64 as follows: #telnet1 stream tcp nowait root /etc/telnetd telnetd port1 #telnet2 stream tcp nowait root /etc/telnetd telnetd port2 . . . . . . #telnet64 stream tcp nowait root /etc/telnetd telnets port64 The '#' as the first character of each line makes that line a comment, and so it is not used. To activate a port definition, use the text editor 'vi' to remove the '#' from the desired definition. The servicename must be defined in /etc/services, and the last arguement must be defined in /etc/remote.in. /etc/services This file defines each service name, and relates it to a port and protocol. The format of each record is: sername port#/protocol alias_list For the purpose of setting constant remote port numbers, this file contains records for ports 1 -64 as follows: #telnet1 6001/tcp #telnet2 6002/tcp . . . . . . #telnet64 6064/tcp To activate a service definition, use the text editor 'vi' to remove the '#' from the desired definition' SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg020 After these changes are made the system must be rebooted to stop and restart inetd. Access from the Terminal Server To use this feature from a Xylogics terminal server use the TLI command. For example to access tcpline 6005 on the host sam would be: $ telnet sam 6005 How Terminal Assignments Are Made. Suppose the remote.in file has been set up as shown: server1:port5:T990 server1:port6:T991 server2:port5:T992 server2:port8:T993 and the lines for telnet5, telnet6 and telnet8 have been activated (the '#' removed). Then the terminal assignments are made as follows. When the system starts in multi-user mode, the inetd daemon begins watching tcp lines 6005, 6006 and 6008 for a signal. When a signal arrives on port 6005 from server2, for example, inetd passes it to telnet5, as specified by the example, inetd passes it to telnet5, as specified by the /etc/services and /etc/inetd.conf files. Telnet assigns it a random device name, say /dev/ttyAF/AXFB. When BASIC starts, it is passed to the device name ttyAF/AXFB. BASIC then checks the remote.in file to find the server_name specified in /etc/remote.in, and the signal arrived on the port using the port_name specified in /etc/remote.in and inetd.conf. If so, BASIC assigns the BASIC Terminal name T992 to device ttyAF/AXFB, otherwise a random terminal name is assigned. In the above example, if the server1 had signed inetd line 6005 the information in the remote.in file for server1 port 5 would have been used and the BASIC Terminal name T990 would be assigned. 3.12 2780/3780 BATCH COMMUNICATION The 2780/3780 Batch Communications Emulation product provides high-speed synchronous batch file transfer between MAI systems or between the MAI system and those non-MAI systems supporting the IBM 2780/3780 protocol. Transfer can take place over dialup or leased lines at speeds up to 9600 baud. Other features provide full autodial support, enabling computers to dial each other, send and receive large files and hang up the phone . at any number of sites, without the intervention of an operator. BOSS/VX 1.1A provides the base operating system support, but 2780/3780 Batch Communications requires the cu\stomer to order the optional 2780/3780 Batch Communications Emulation software key, the Synchronous Communications Controller (SCC), appropriate cables and data communications equipment. See Marketing Announcement 1006 for more information regarding the SCC. 3.12.1 SOFTWARE REQUIREMENTS AND INSTALLATION 2780/3780 Batch Communication requires a minimum of 1654 disk SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg021 blocks on the /usr partition for the programs. The files will reside in the /usr/mbf/comm, /usr/mbf/magnet, /usr/mbf/tbc and /usr/mbf/etc directories. To install the package in single user mode use the 'mbfinstall' command. Select the 'TBC' option from the menu. This package requires a key to work. The key MUST be installed in upper case. The 'configure' utility has been modified to include communication devices. Option '9' is used to configure the communication devices. NOTE: Only port 0 may be used for TBC at speeds up to 9600 baud. NOTE: You must be in single user mode to install this package and configure the communication devices. After the install you must shutdown and reboot the system. 4.0 NEW HARDWARE PRODUCTS IN LEVEL 1.1A 4.1 NEW TAPE AND DISK DRIVES Tape Drives: 1.1A for the GPx Series 70 supports the following new tape drives: 1/2" MTS tape drive. Present non-SCSI tape drives would have to be upgraded with the SCSI interface upgrade kit. SCSI 8MM High Capacity Cartridge Drive. Both of the above tape drives are connected to the Differential SCSI Adapter. The GCR is the only other device supported off the Differential SCSI Adapter. The SCSI bus will support up to 7 SCSI devices, with up to 4 of them on the Differential SCSI Adapter. The address of the devices are SCSI ID 5, 4, 3, or 2. It is best to start with the highest address and work your way down, so that added disk drives starting at SCSI ID 0 will not overlap. A tape drive set as SCSI ID 5 is named /dev/rmt/tg0 in the Operating System, SCSI ID 4 is /dev/rmt/tg1, SCSI ID 3 is /dev/rmt/tg2 and SCSI ID 2 is /dev/rmt/tg3. If you are missing an SCSI ID number the device name will not move. Example: There is no SCSI ID 5 or 4, only SCSI ID 3. This device will still be called /dev/rmt/tg2 and there will not be a tg0 or tg1. Disk Drive: 1.1A now supports the 8-inch SMD F621 Disk Drives on the GPx 6070. The drives are mounted in the SMD Expansion Cabinet Assembly (ECA) and are controlled by the Dual Channel Controller (DCC) (see below). This is the same drive used on the MPx/AS system. Before using the drive in a GPx system it must be formatted using DIVE on the GPx system. The formatted Capacity of the drive is 569 MBs. The device name for the disk drive is zdxx (where xx=drive SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg022 number). The diskadd utility can be used to set the drive up after it is formatted on the system. 4.2 SYNCHRONOUS COMMUNICATIONS CONTROLLER (SCC) SCC provides four bisynchronous communication channels for support of batch communications (2780/3780). NOTE: In the 1.1A release only one bisynchronous communication channel is supported. The SCC has five (5) LEDs, 37 sets of jumpers (from 1 to 8 positions each) and one switch. LEDs: DS1 through DS4 are RED LEDs designated L3 through L0 (respectively) on VME faceplate. These are used to display self-test error status. In the event that the self-test fails, an error number is flashed by the LEDs. 1= ON, 0=OFF L3 L2 L1 L0 0 0 0 1 Dynamic Ram Address lines fail 0 0 1 0 Dynamic Ram data/data lines fail 0 1 0 1 Dual port Ram Address lines fail 0 1 1 0 Dual port Ram data/data lines fail 0 1 1 1 DMA test fails 1 0 0 0 DMA test fails 1 0 0 1 Prom checksum fails 1 0 1 0 8255 fails 1 0 1 1 serial I/O interrupt fails 1 1 0 0 Serial I/O fails 1 1 1 0 8255 failure 1 1 1 1 8255 failure DS5: RED LED designated SYS on VME faceplate, is driven by the SCC's SYSFAIL signal on the VME bus. This LED will be ON during self-test and will be turned OFF at completion of self-test. Switches: SW1: SW1 is a push button switch located below the LEDs on the VME faceplate. This switch is software readable, it is NOT supported by Model 4020/4028 software. Jumpers: W1: This jumper block sets software selectable options. Installing a jumper will select a specific option. Option 3 | Option 2 | Option 1 | Short Self-test Pins 1,2 | Pins 3,4 | Pins 5,6 | Pins 7,8 ---------|----------|----------|------------------ Out | Out | Out | In W2: This jumper for FACTORY USE ONLY Normal setting = NOT installed SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg023 W3: This jumper selects how the SCC responds to the VME SYSRESET signal. Installed = SCC is reset with VME SYSRESET signal. Not Installed = SCC ignores VME SYSRESET signal. Normal setting = INSTALLED W4: Jumper block W4 is for FACTORY USE ONLY (NOTE that these are "hard" wired) Pins 1,2: Normal setting = INSTALLED Pins 3,4: Normal setting = INSTALLED W5: pins 1,2: If installed SCC memory in supervisory space Normal setting = NOT INSTALLED pins 3,4: If installed SCC uses standard addressing Normal setting = NOT installed W6, W7, W10, W11, W12: These jumper blocks determine which Bus Grant and Bus Request are used. Normal setting = Bus Grant/Request two (2) Bus Grant/ Jumper Pins Installed Request W6 W7 W10 W11 W12 ------------------------------------------------------- W8: This jumper block selects how SCC memory is utilized. See below: Normal setting = Pins 3-4 INSTALLED W8 Pins | 1,2 | 3,4 | 5,6 | 7,8 | Memory Usage -----|-----|-----|-----|------------------------------ Out | In | Out | Out | memory used for data space W9: If in, on-board timeout sets on-board bus error (BERR). Normal setting = INSTALLED W13: Sets the VME bus release. Normal setting = NOT installed W14: Channel A, connects DSR to DCD pins 1,2: Normal setting = INSTALLED (Hard Wired) pins 2,3: Normal setting = NOT installed W15: Channel A, connects RS232 ground to logic ground Normal setting = INSTALLED W16: Channel A, part of RS442/449 Configuration Normal setting = NOT installed SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg024 W17: Channel A, connects logic to "frame" ground. Normal setting = NOT installed W18: Channel A, selects receive or transmit clock for receive USART Installed 1-2, transmit clock to receive USART. Installed 2-3, receive clock to receive USART. Normal setting = Installed 2-3. W19, W34: Sets the local DMA address range as follows: Normal setting = 64K Byte Addressing Address Jumper and Pins Connected Range W19 W34 --------------------------------------------- 32K Byte 2-3 1-3 and 2-4 64K Byte 1-2 1-2 and 3-4 W20: FACTORY USE ONLY Normal setting = NOT installed W21, W22, W23, W27: These are set to determine which VME interrupt and acknowledge is used. Normal setting = IRQ4/IACK4 Interrupt Level W21 W22 W23 W27 Pins ---------------|-----|-----|-----|---------- IRQ4/IACK4 Out In In pins 7-8 W24: FACTORY USE ONLY Normal setting = NOT installed W25: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W26: FACTORY USE ONLY Normal setting = NOT installed W28: Channel A, RT/ST Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) W29: Channel A, ST/TT Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) W30: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W31: Channel A, if installed, multidrop (RS449) is enabled. Normal setting = NOT installed SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg025 W32: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W33: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W35 and W36: Set for the size of the EPROMs in sockets U56 and U57. W35 jumpered 2 - 3 & W36 jumpered 2 - 3 = 32 Kbyte EPROMS W35 jumpered 2 - 3 & W36 jumpered 1 - 2 = 64 Kbyte EPROMS Normal setting = W35 jumpered 2 - 3 and W36 jumpered 1 - 2 W37: This jumper block sets the base address for the dual-port memory. W37 PINS: Board VME Jumper Settings Number Address 1-2 3-4 5-6 7-8 9-10 11-12 13-14 15-16 ------------------------------------------------------------- 0 0xA0000 In In In In Out In Out In ------------------------------------------------------------- 1 0xB0000 In In In In Out In Out Out ------------------------------------------------------------- 2 0xC0000 In In In In Out Out In In ------------------------------------------------------------- 3 0xD0000 In In In In Out Out In Out ------------------------------------------------------------- NOTE: In = 0 Out = 1 W38: FACTORY USE ONLY Normal setting = NOT installed W39: FACTORY USE ONLY Normal setting = NOT installed W40: Channel B, if installed, multidrop (RS449) is enabled. Normal setting = NOT installed W41: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W42: FACTORY USE ONLY Normal setting = INSTALLED 1-2 (Hard Wired) Normal setting = INSTALLED 3-4 (Hard Wired) W43: This jumper block sets the status/ID byte value for the interrupt acknowledge cycle. Note that each board must have a different value for the status/ID byte. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg026 Board Status/ID Jumper Settings Number Byte 1-2 3-4 5-6 7-8 9-10 11-12 13-14 15-16 ------------------------------------------------------------- 0 0x10 Out Out Out In Out Out Out Out ------------------------------------------------------------- 1 0x11 Out Out Out In Out Out Out In ------------------------------------------------------------- 2 0x12 Out Out Out In Out Out In Out ------------------------------------------------------------- 3 0x13 Out Out Out In Out Out In In ------------------------------------------------------------- NOTE: In = 1 Out = 0 W44: Channel B, connects DSR to DCD pins 1,2: Normal setting = INSTALLED (Hard Wired) pins 2,3: Normal setting = NOT installed W45: Channel B, connects RS232 ground to logic ground Normal setting = INSTALLED W46: Channel B, part of RS442/449 Configuration Normal setting = NOT installed W47: Channel B, connects logic to "frame" ground. Normal setting = NOT installed W48: Channel B, selects receive or transmit clock for receive USART Installed 1-2, transmit clock to receive USART. Installed 2-3, receive clock to receive USART. Normal setting = Installed 2-3. W49: Channel B, RT/ST Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) W50: Channel B, ST/TT Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) W51: Channel B, if installed connects transmit clock is connected to USART transmit clock input/output pin. Normal setting = INSTALLED W52: FACTORY USE ONLY Normal setting = INSTALLED 2-3 (Hard Wired) W53: Byte swap enable, if installed makes byte order same as Intel. Normal setting = INSTALLED SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg027 W54: If installed, sets SCC for extended addressing. Normal setting = NOT installed W55: This set of jumpers sets addresses A24 thru A32 for extended addressing. Extended addressing is NOT used so their actual setting does not matter. Pins 1,2 = Don't care Pins 3,4 = Don't care Pins 5,6 = Don't care Pins 7,8 = Don't care Pins 9,10 = Don't care Pins 11,12 = Don't care Pins 13,14 = Don't care Pins 15,16 = Don't care W56: Channel D, selects receive or transmit clock for receive USART Installed 1-2, transmit clock to receive USART. Installed 2-3, receive clock to receive USART. Normal setting = Installed 2-3. (NOTE: Channel D not supported) W57: Channel A, if installed connects transmit clock is connected to USART transmit clock input/output pin. Normal setting = INSTALLED W58: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W59: Channel C, connects RS232 ground to logic ground Normal setting = INSTALLED W60: Allows usage of optional oscillator/baud rates. Normal setting = INSTALLED (Hard Wired) W61: Channel C, part of RS442/449 Configuration Normal setting = NOT installed W62: Channel C, connects logic to "frame" ground. Normal setting = NOT installed W63: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W64: Channel D, if installed transmit clock is connected to USART transmit clock input/output pin. Normal setting = INSTALLED (NOTE: Channel D not supported) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg028 W65: Channel D, if installed, multidrop (RS449) is enabled. Normal setting = NOT installed (Note- Channel D not supported) W66: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W67: Channel D, RT/ST Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) (NOTE: Channel D not supported) W68: Channel C, selects receive or transmit clock for receive USART Installed 1-2, transmit clock to receive USART. Installed 2-3, receive clock to receive USART. W69: Channel C, RT/ST Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) W70: Channel C, if installed transmit clock is connected to USART transmit clock input/output pin. Normal setting = INSTALLED W71: Channel C, if installed, multidrop (RS449) is enabled. Normal setting = NOT installed W72: FACTORY USE ONLY Normal setting = INSTALLED (Hard Wired) W73: Channel C, connects DSR to DCD pins 1,2: Normal setting = INSTALLED (Hard Wired) pins 2,3: Normal setting = NOT installed W74: Channel C, ST/TT Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) W75: FACTORY SETTING - all positions are HARD WIRE INSTALLED: 1-2; 3-4; 5-6; 7-8; 9-10; 11-12; 13-14; 15-16; 17-18; 19-20; 21-22. W76: FACTORY SETTING - all positions are HARD WIRE INSTALLED: 1-2; 3-4; 5-6; 7-8; 9-10; 11-12; 13-14; 15-16; 17-18; 19-20. W77: Channel D, connects RS232 ground to logic ground Normal setting = INSTALLED (NOTE: Channel D not supported) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg029 W78: Channel D, part of RS442/449 Configuration Normal setting = NOT installed (NOTE: Channel D not supported) W79: Channel D, connects logic to "frame" ground. Normal setting = NOT installed (NOTE: Channel D not supported) W80: Channel D, connects DSR to DCD pins 1,2: Normal setting = INSTALLED (Hard Wired) pins 2,3: Normal setting = NOT installed (NOTE: Channel D not supported) W81: Channel D, ST/TT Receive selection Normal setting = INSTALLED 2-3 (Hard Wired) (NOTE: Channel D not supported) Connectors: J1, top (CH 1) DB-25S connectors for each channel which J2, center (CH 2) map directly to standard RS-232 pinouts. J3, bottom (CH 3) 4.3 ETHERNET LAN CONTROLLER (ELC) Up to two ELC boards may be configured in a local network with 8/16/32 Port Terminal Servers thus permitting the GPx 5070/6070 to support up to 256/512 serial devices. ELC boards can also serve as host in a network of Ethernet-equipped personal computers, where the GPx 5070/6070 functions as a file server. For wide-area insystem file transfers, one ELC can be configured to exchange data between the GPx 5070/6070 and other Ethernet-equipped systems. The ELC has 10 jumper sets (two of which are on the small daughter board), one LED and three switches packages. LEDs: The single LED on the metal faceplate is a bi-color LED which shows RED at power up or when a reset is received by the ELC. The LED shows green after successful board initialization. Switches: There are two addresses associated with the ELC; one address is associated with the communications buffer, the second is associated with the upper 2K memory space of the buffer used for I/O parameter blocks. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg030 NOTE: 1 = OPEN/OFF 0= CLOSED/ON Short I/O Space | Corresponding VME Base Address (Hex) | Address (Hex) ------------------|---------------------------- (5000) (FF900000) Switch 1 Switch 3 Switch 2 Board ----------- --------------- ---------- 0 1|2|3|4|5 1|2|3|4|5|6|7|8 1|2|3|4|5 0|1|0|1|0 1|1|1|1|1|1|1|1 1|0|0|1|0 ------------------|---------------------------- (5800) (FF980000) Switch 1 Switch 3 Switch 2 Board ----------- --------------- ---------- 1 1|2|3|4|5 1|2|3|4|5|6|7|8 1|2|3|4|5 0|1|0|1|1 1|1|1|1|1|1|1|1 1|0|0|1|1 ------------------|---------------------------- (6000) (FFA00000) Switch 1 Switch 3 Switch 2 Board ----------- --------------- ---------- 2 1|2|3|4|5 1|2|3|4|5|6|7|8 1|2|3|4|5 0|1|1|0|0 1|1|1|1|1|1|1|1 1|0|1|0|0 ------------------|---------------------------- (6800) (FFA80000) Switch 1 Switch 3 Switch 2 Board ----------- --------------- ---------- 3 1|2|3|4|5 1|2|3|4|5|6|7|8 1|2|3|4|5 0|1|1|0|1 1|1|1|1|1|1|1|1 1|0|1|0|1 ------------------|---------------------------- (7000) (FFB00000) Switch 1 Switch 3 Switch 2 Board ----------- --------------- ---------- 4 1|2|3|4|5 1|2|3|4|5|6|7|8 1|2|3|4|5 0|1|1|1|0 1|1|1|1|1|1|1|1 1|0|1|1|0 Jumpers: NOTE: The Following Jumpers Are Located On The Main Logic Board JA1: Installed = Enables clock for memory array Normal setting = Installed JA2: Installed = Enables clock for CPU circuit Normal setting = Installed JA3: Jumpered to select Eprom size Normal setting = Jumpered 1-2 JA4, JA5, JA6: These three jumpers set the Priority of the VME Bus Request; they are to be set for Bus Request 1. o o o o--o o 0 o----o o----o o----o 1 o o o o--o o 2 o o o o--o o 3 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg031 JA7: Jumpered 1-2 = Early release of BBSY Jumpered 2-3 = Late release of BBSY Normal setting = Jumpered 2-3 JA8: Installed = Enables tri-state drivers Normal Setting = Installed NOTE: The Following Jumpers Are Located On The "Daughter" Card JA1: Jumpered 1-2 = Transceiver power is connected at VME bus connector P2. Jumpered 2-3 = Transceiver power is NOT connected at VME bus connector P2. Normal Setting = Jumpered 2-3 JA2: Jumpered 1-2 Selects version 1 Ethernet (as opposed to 802.3 & version 2 Ethernet) Jumpered 2-3 Selects 802.3 and version 2 Ethernet (As opposed to version 1 Ethernet) Though application dependent, JA2 would most likely be jumpered 2-3 4.4 DUAL CHANNEL CONTROLLER (DCC) Each DCC board supports up to eight 8-inch SMD disk drives, as contained in the optional SMD expansion Cabinet Assemblies (ECAs). Two DCC boards and up to four SMD ECAs, with four 8-inch disks each, may be configured. NOTE: That the DCC board and 8-inch disks are used only on the GPx 6070 systems. The DCC has four LEDs, NO jumpers and no switches. The DCC's "address" is determined by its position in the cardcage. The DCC closest to the SMM has the lowest address and its drives have lower device numbers then a DCC farther from the SSM. Note that a DCC requires at least one Cable Routing Board (CRB). (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg032 LEDS: LEDs DS0 through DS3 represent the lower four bits of the DCC's status register. NOTE: L = ON/LIGHTED O = OFF/NOT LIGHTED Bottom-------->Top DS4 DS2 DS1 DS01 ------------------- Reset L L L L Initializing L L L O Normal operation O L x x Parity error and ZDC OTL x x x x WCS parity error L L L O ZDC->OK parity error L L O L OK->ZDC parity error L L O O LRAM->HSC parity error L O L L LRAM->SB8000 parity error L O L O LRAM->Channel A parity error L O O L LRAM->Channel B parity error L O O O ZDC panic O L L L DMA C time out O L L O ZDC WB O L O L Reserved O L O O Reserved O O L L Reserved O O L O Reserved O O O L Reserved O O O O Out of Bounds CB L L O L Request without CB base L L O O CB Access error L O L L Reserved L O L O Reserved L O O L Reserved L O O O 4.5 CABLE ROUTING BOARD (CRB) The CRB board provides the cabling, control, and data interface between the Dual Channel Controller (DCC) and the 8-inch SMD disk drives. Each CRB board will support up to four 8-inch drives. Two CRB boards may be daisy-chained, thus permitting a single DCC board to control up to eight disk drives. The CRB has no LEDs, no switches and no jumpers. 4.6 PARALLEL PRINTER CONTROLLER (PPC) The PPC board supports up to four Centronics- or Dataproducts-compatible parallel printers. Permits a total of 5 parallel printers to be configured (including printer on SSM parallel port). The PPC has three LEDs, five sets of jumpers and no switches. LEDs: DS1: a RED LED, is the top most LED. This LED will be lit at power on and will be turned off at successful completion of self-test. Additionally, this LED will light if a BUSERR error occurs during operation. DS2 is exclusively ORed with DS1. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg033 DS2: the GREEN LED, will be turned on at successful completion of the self-test. Additionally, this LED will be turned off if a BUSERR error occurs during operation. DS2 is exclusively ORed with DS1. DS3: a RED LED, is the bottom LED. This LED will be lit if a buffer parity error is encountered. Jumpers: JMP1, JMP2, JMP3: These three jumper blocks set the priority of the VME Bus Request/Grant; they are to be set for Bus Request 1. JMP1 JMP2 JMP3 Bus Request 1 3-4 3-4 3-4 JMP4: This jumper block consists of 13 two pin jumpers whose functions are listed below. Pins 1,26: Jumper INSTALLED = Loop on Self-test Jumper NOT installed = Normal operation Normal setting = NOT installed Pins 2,25: Jumper installed = Printer #3 is present This Jumper MUST be INSTALLED for the PPC to pass self-test. Pins 3,24: Jumper installed = Printer #2 is present This Jumper MUST be INSTALLED for the PPC to pass self-test. Pins 4,23: Jumper installed = Printer #1 is present This Jumper MUST be INSTALLED for the PPC to pass self-test. Pins 5,22: Jumper installed = Printer #0 is present This Jumper MUST be INSTALLED for the PPC to pass self-test. Pins 6,21 thru pins 13,14: Used to set VME base address as follows: Board |Address|LSB Jumper Pins MSB # |(Hex) |6,21|7,20|8,19|9,18|10,17|11,16|12,15|13,14 ------|-------|----|----|----|----|-----|-----|-----|------ 0 |F0XX | In | In | In | In | Out | Out | Out | Out ------|-------|----|----|----|----|-----|-----|-----|------ 1 |F2XX | In |Out | In | In | Out | Out | Out | Out ------|-------|----|----|----|----|-----|-----|-----|------ JMP5 & JMP6: These two jumpers select the clock used on the PPC. JMP5 JMP6 Clock -----|-------|------------- Out | In | Normal Setting = onboard clock Connectors: J3, J4: 25-pin cable connectors for parallel printers 0 and 1, respectively. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg034 J5: 50-pin cable cable connector, J5 is a two-in-one, where a special "Y-cable" (916768-001) is used to connect parallel printers 2 and 3. 4.7 VME (I/O) BUS CARD CAGE BOARD PLACEMENTS The GPx 5070 VME card cage will hold up to 12 PCBAs and the GPx 6070 holds up to 16 PCBAs. The following chart can be used for both system types. If you are not using a PCBA all the cards should be shifted to the right. The cards must start at the right and have no gaps. PCBA Left 16 Way Controllers (all VME cards can be 16 Ways) Parallel Printer Controller (max of 1) Synch Communications Controller (max of 1) Right Ethernet LAN Controller (max of 2) 4.8 CHANGES TO THE REMOTE ENABLE/DISBALE SWITCH FUNCTIONALITY With the 1.1A release new functionality has been added to allow the remote port (altcom) to run in parallel with the console port (syscom). With this functionality someone can dial into a remote port and be console. What every is typed in on the remote port is seen on the console and like wise what is typed in at the console can be seen on the remote port. Both ports can be used at the same time, that is one person can enter data on the console and then someone can enter data on the remote. This allows for a remote analyst to either work on the system, allowing someone at the console to see what is being done (good as a training tool) or console can work on the system and remote site can see what is typed (this allows for the remote site to see errors that may be made, or see the results of a test being run). To enable this functionality requires that the 'REMOTE ENABLE/DISABLE' switch on the front panel is in the ENABLE position. As soon as the switched is changed the remote port is in parallel with the console, at any level of the boot or any init state. To disable the remote port requires that the 'REMOTE ENABLE/DISABLE' switch be in the DISABLE position. For security reasons it is highly recommended that the 'REMOTE ENABLE/DISABLE' switch be keep in the DISABLE position unless someone is at the console monitoring the port, and that after the ENABLE is used the system be rebooted with the switch in the DISABLE position. NOTE: With the 'REMOTE ENABLE/DISABLE' switch in the DISABLE position the remote port will act like any non-console port. 5.0 ENHANCEMENT 5.1 ON-LINE CONFIGURE The configure utility will now allow existing terminals and printers to be changed while the system is in multi-user mode. NOTE: If you want to only view a port configuration it is recommended that you run the utility as a non-root user. This SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg035 will allow you to view the ports without being able to modify the configuration. This will avoid accidentally changing a port. o To run 'configure' to add/delete/modify ports, the operator must be 'root' and it can only be run on 1 terminal at a time. o Any modifications made to a terminal MUST be made while the terminal is inactive (at the BOSS/VX screen). o All printer options can be changed except the printer type and name, while in multi-user mode. o New devices can be added but will not be recognized until the system is rebooted. o DO NOT swap 2 ports because the ports that are swapped will become hung after the operator logs off. 5.2 USER SCRIPTS Changes have been made to the login script '/etc/profile' and the 'diskadd' script to make them more user friendly. This section gives the added enhancements. /etc/profile o Will now determine if the terminal is set as an uppercase only terminal by examining the stty variables, this would be true if the operator entered their login in uppercase. If the terminal is an uppercase only terminal, the operator is allowed to switch the terminal to a mixed case setting. o If the terminal was set up using configure, an entry in /etc/ttytype will exist and is used to set the TERM system variable. If an entry does not exist in /etc/ttytype, as when logging in remotely, the user is presented with a default terminal and slave printer configuration, which they may use or modify. If they modify the configuration, they may save the modifications for later use. NOTE: Since /etc/profile has been modified, it is recommended that if the customer has modified his version of /etc/profile he makes a copy of it to another name. After the update he can check the differences and make the necessary changes to the new profile file. diskadd o Added an update option so existing partitions can be reinstalled or slightly modified without data loss. o Added support for zd drives. o Added ability to partition any non-boot zd, vd, or wd drive. o Operates in single user mode. o Allows an initial digit as a partition name or mount point. o Warns and requires authorization before initializing a partition. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg036 5.3 ERROR LOG CHANGES The format of the error log reported has the following enhancements: o SCSI Tape and Disk format for GPx Series 40 and 70 is the same. o Format is aligned for better readability. o Format is broken into three columns as follows: - Column 1: Field Description - Column 2: Numerical value of error in Hex - Column 3: Description of error if applicable The mbf_errlog command has a new option '-noasync'. This option prevents the logging of any terminal error(s) in the error log file. This is the desired option to avoid display of warning message(s) to the console. If the system administrator desires to set the '-noasync' flag at boot, the '/etc/rc2.d/S85errlog file should be edited to add the '-noasync' option following the '-quiet' option. The system then would need to be rebooted for this new option to take effect. To restart error logging of async errors remove the '-noasync' flag. 5.4 NEW PARAMETERS TO USE WITH THE /etc/dump COMMAND The '/etc/dump' command has had new options added to make using the command more user friendly. Following is a description of these new options. Each row of the following table represents one permutation of tape device type, media size and density setting. Also indicated is the approximate capacity in MegaBytes (10^6). The dump utility now supports a new optional parameter (option "C") which may be used in lieu of the density and media size options. The density and size options are still supported. The C option, if specified, overrides the density and media size. Only the capacities listed may be used with the dump command. Each capacity is unique and corresponds to a specific device type, media size and density. Entering an invalid capacity will cause an error message to be displayed. Example, instead of typing: dump 0nufsd /dev/rmt/tg2h 3500 6250 /usr4 (meaning GCR tg2 with 3500 ft. reel at high density) you may enter: dump 0nufC /dev/rmt/tg2h 240 /usr4 Important notes: 1) If no device name is specified the default will be /dev/rmt/tg0h, with 2300 for media size and 6250 density. 2) Using dump 0uc /usr2, will set the device name to /dev/rmt/tm0, with 9000 for media size and 1250 for density. 3) Any time a high density GCR (6250) is selected, a high density tape drive should be specified too (tg0h). 4) "f" option should be used with "C" or "d" and "s" options. The device name specified for the "f" option should be the full device name such as /dev/rmt/tm0 rather than link names such as /dev/tape. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg037 5) "c" option cannot be used with "f" option. 6) The default setting for b option is set to 32, as opposed to 10 (old default), in both dump and restore. Any 1/4" cartridge tapes backed up with the old release should now be restored with the b option set to 10. 7) To use dump for backing up multiple partitions, a) Rewind the tape b) Dump with no rewind (dump 0ufC /dev/rmt/tg0hn ...) c) Dump the next partition with no rewind 8) To restore a partition from a tape with multiple backups: a) Rewind the tape b) bring the tape to the start of a particular partition (mt -f /dev/rmt/tg0hn fsf 1 ... for the second dump session on the tape) c) Run restore. Another way to do this is use the s option with restore command. Device Media Size Density Capacity Type (feet) (cpi) (MBytes) _______________________________________________ 1/4" 5400 1000 60 1/4" 9000 1250 120 (Default using c option) 1/4" 25000 @ 2000 525 GCR 1/2" 500 1600 11 GCR 1/2" 1100 1600 21 GCR 1/2" 2300 1600 41 * GCR 1/2" 3500 1600 61 GCR 1/2" 500 6250 40 GCR 1/2" 1100 6250 80 GCR 1/2" 2300 6250 160 (Default) GCR 1/2" 3500 6250 240 MTS 1/2" 500 1600 12 MTS 1/2" 1100 1600 22 MTS 1/2" 2300 1600 42 MTS 1/2" 3500 1600 62 HCC 8mm 19300 ~ 5400 1100 HCC 8mm 38400 ~ 5400 2200 * This value of 41 instead of 40MB is used in order to differentiate 1600 cpi from 6250 cpi. This was done to avoid introducing another option for high/low density level. @ This value is less than 1020*26, in order to account for ECC overhead in QIC-320 format. ~ This value is not the same as the physical length of the tape. This is due to Helical scan recording format. 6.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES This procedure gives the steps required to install or update the BOSS/VX operating system on the GPx Series 70 hardware platform. It is divided up into seven sections. Section 1 provides the information required to load. the system to the third level prompt from tape; normally called loading the SSM firmware. This step is required for all new installs were the OS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg038 is not already on the disk and for all systems on OS level 1.0A. Section 2 details the steps required to install a new VTOC (volume table of contents). This step is required for all new installs or for a primary disk (the disk the OS will be booted from) after a format. Section 3 provides the steps for installation and update of the OS. Section 4 details the steps to install or update the system security record. Section 5 provides the steps to install or update optional software packages. Section 6 gives the steps to customize the optional software packages. Section 7 gives the steps to install the LAN and TCP/IP packages. WARNING: OS updates from 1.0A to 1.1A requires that a new dct file be installed. Before attempting an update make a copy of your current. dct file and save it in another directory. At the prompt to reinstall dct enter 'Y'. After the system comes back up compare the 1.0A dct to the 1.1A dct and make the required changes. NOTE: The mini-root is automatically installed during the OS installation update. NOTE: During the installation/update procedure the system will be booted and programs loaded from tape and/or hard disk. The command 'tm(48,x)', (where x=file number on the tape) will be used to boot or load a program from tape. For hard disk access 'wd(0,x)', (where x=block offset) or 'wd0sx', (where x= partition on disk) will be used. NOTE: This procedure uses the install script loaded in the SSM firmware to install a new mini-root and then boot to it. This is the recommended procedure as the latest programs and files will be loaded on the mini-root. If for troubleshooting reasons you need to load the mini-root, not re-installing it first, from the level 3 prompt (--->) enter: bh 'wd(0,8)unix -M -r wd0s8 -s wd0s8' 6.1 BOOTING THE SSM FIRMWARE FROM TAPE The following section outlines the steps to load the SSM to the third level prompt from tape. The SSM firmware will need to be loaded from tape if this is a new installation, the primary disk does not contain a operating system or the operating system on the disk is a 1.0A release. If the primary disk contains a OS release of 1.1A or greater the SSM can be booted from the primary disk and this section skipped. The BASE OS tape is used to boot the SSM firmware into SSM memory. The SSM has three states that it goes through during the boot process. On a new system with the BASE OS tape inserted and the machine powered on, the system will come up in level 1 indicated by a single dash followed by a greater-than symbol (->). The user enters a boot command to bring the system to level 2 indicated by the prompt -->. Then another command is typed in to bring it to level 3 operational firmware, indicated by the prompt '--->'. 1) If the system is already running, shut it down with the shutdown. command ('shutdown -i0 -g# -y' where # is the number of seconds to wait). The '--->' prompt will be displayed when the shutdown is complete. Go to Step 3. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg039 2) If the system is not running, power the system on. If during the load, after the selftest the following message is displayed '5 . seconds to boot, press any key to stop:' enter a to stop the auto-boot. The system will respond with the level prompt. Continue on to Step 3. If the system boots to single or multi user mode, shut it down as in Step 1 above. 3) Put the BASE OS tape in the tape drive and enter: bs tm(48,2) This reads and runs the boot program from tape. This is called level 2 (system prompts -->). If the system displays the message '5 seconds to boot, press any key to stop:' enter to stop the auto-boot. 4) Enter bs tm(48,3) This brings the system to the operational firmware level (level 3). The system prompts with '--->'. If the system displays the message '5 seconds to boot, press any key to stop:' enter to stop the auto-boot. At this time the SSM is booted with the latest FIRMWARE level and the system is at the level 3 prompt. From here go to the VTOC or OPERATING SYSTEM INSTALLATION AND UPDATE section depending on the installation requirements. 6.2 WRITING A NEW VTOC If hardware failure or installation instructions require writing of a minimal vtoc, proceed with the following steps. Writing of a minimal vtoc is required when the disk partitioning of the primary disk is unknown or is changing from one release to the next. Writing a minimal vtoc writes a volume table of contents that describes a single partition on the disk. In this case, the partition being described is partition 8 for the miniroot. WARNING: THIS PROCEDURE WILL ERASE YOUR DISK. IF THERE IS CUSTOMER DATA ON THE DISK, ENSURE THERE IS A BACKUP BEFORE CONTINUING. To write a minimal VTOC perform the following steps: 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt (--->), if not go to Section 6.1 to boot the SSM firmware to the level 3 prompt. 2) At the (--->) prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg040 tape is in the tape drive before entering 'y' . This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 3 'Special Installation' to install the minimal VTOC. 4) At the prompt : enter tm(48,5) 5) A menu of disk drives the VTOC can be installed on is displayed. Enter the drive number that the minimal VTOC is to be installed on. will cause the VTOC to be written to the primary disk drive (wd0). 6) Next disk drive and minimal VTOC information is displayed. Followed by the prompt 'Use this layout (y/n)?'. Enter y at this prompt. A minimal VTOC will now be written to the disk drive. After it is complete the system will prompt with the level 3 prompt (--->). 6.3 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM The following section outlines the steps to install or update the BOSS/VX Operating System. NOTE: Installation or Updating the OS will write a new mini-root. There is no need for a special step to install the mini-root. 6.3.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all the files on the 'root' and 'usr' filesystems. It makes a new vtoc for the . disk, makes the filesystem for the 'root' and 'usr' partitions and installs the standard BOSS/VX software (BOSS/VX, Business BASIC and system utilities) on the disk. WARNING: A full installation completely destroys the contents of the root and usr partitions. Other partitions may not be affected, but they must be backed up as a precaution. Other partitions will definitely be destroyed if the disk partitioning changes as a result of the installation. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record tape for the target system Do the following steps to Install the BOSS/VX Operating System. 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt (--->), if not go to Section 6.1 to boot the SSM firmware to the level 3 prompt. 2) At the (--->) prompt enter: install SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg041 The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS tape is in the tape drive before entering 'y' This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 1 'Full Installation'. 4) A menu of disk drives the OS can be installed on will be . displayed. Enter the drive number that the OS is to be installed on. will cause the OS to be installed on the primary disk drive (wd0). 5) Next disk drive and minimal VTOC information is displayed. Followed by the prompt 'Use this layout (y/n)?'. Enter y for this prompt. A new mini-root will be installed on the target disk. After the new mini-root is installed the system will be booted on to the mini-root. 6) After the boot process is complete the '#' will be displayed. From this prompt enter ./INSTALL This will bring up the BOSS/VX SOFTWARE INSTALLATION menu 7) From the BOSS/VX SOFTWARE INSTALLATION menu enter option 'f' for Full Install. 8) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 9) A warning message is displayed telling you that a full installation will destroy all files on the primary disk. You will be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', to exit the installation procedure. 10) A message is displayed saying Extracting data, after which a table will be displayed giving present system disk partitioning information. This information will be used to update the system disk's vtoc (volume table of contents) and contains the following information: Partition number, partition label (name), size in MBs, mount point (directory to mount the partition to if its to be mounted automatically at boot), auto mount flag (this tells the system if the partition should be mounted at boot time or not), and swap (this tells the system if . this is a swap partition or not). At the bottom of the table is the prompt: Enter selection (0-11, h=help, i=install) to modify: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg042 If you wish to use the disk partitioning information in the table to set up the system disk enter i and proceed to Step 6. If you wish to modify the disk partitioning information enter the partition number you wish to modify. NOTE: Partitions 8,12,13,14 and 15 are reserved for the OS and cannot be modified. After entering a partition number to modify you will be given the following options: Label - This will allow you to label (name) the partition. This field can be 1 to 6 characters long. Size - This will allow you to give the size for the partition. This option is used to increase or decrease the size of a partition. The size can changed in increments of 1 megabyte. NOTE: A partition's size cannot be increased if there is no available disk, so decrease other partitions before increasing any. Mount point - The mount point is the directory the partition will be mounted to. The root and usr mount points cannot be changed. An entry of a . (period) removes a mount point. If a partition is not automounted, it doesn't HAVE to have a mount point. Automount - If this option is set to yes, the partition will be mounted at boot time. A partition option requires a mount point. A partition cannot have swap and automount both set to yes. Swap - If a partition is to be used as swap when the system is in multi-user mode, set swap to yes. If it is not to be used as a swap partition then set swap to no. redisPlay screen - As updates are made to the table the information in the table will not be displayed until you are done with that partition update or this option is used. Help - The help messages will be displayed. Remove - Removes a partition from the disk. The root, swap, usr, firmware, vtoc, boot, and miniroot partitions cannot be removed. Done - Indicates that changes to this partition are complete. Final verification for this partition takes place. The screen and main menu is displayed. This partition can be selected again for editing. Enter the capital letter in each option to select that option. When you are done with the update of the system SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg043 disk partitioning, enter i to install this information into the system disk's vtoc. 11) Messages will now be displayed indicating that the file systems are being made and mounted. After the filesystems are made, the BOSS/VX software will be copied from tape to disk. 12) After the BOSS/VX software is copied to disk, messages will be displayed telling you that the SSM firmware is being copied to disk, that the /dev devices are being made and that /etc/versionlog is being created, followed by a message giving the current system name. You will be prompted with: Do you wish to change it (y/n)? If you wish to change the name enter 'y', and you will be allowed to enter a 8 character name. If you don't wish to change it enter 'n', . 13) The Date and Time are displayed. You will be prompted with: Would you like to set date and time (y/n)? To set date, time and timezone enter 'y', , and the following will be displayed: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y', , and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n', . If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. Next the current date and time are displayed followed with the prompt: Change the date and time (y/n)? If they are correct, answer 'n', ; otherwise, answer 'y', , and you will be prompted with the questions to set the Date and Time correctly. After the date and time are changed you will be prompted with: Date and time will be set to: MM/DD/YY HH:MM (y/n)? If the date and time is correct enter 'y', . If you need to go back and change the date or time enter 'n', . SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg044 14) You will next be prompted with: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? Enter 'y', , to install the configuration record. If you enter 'n', , the configuration record will not be installed. NOTE: You must install a configuration for your system to boot. If you entered 'n', , in the above step, see Section 6.4, "Installation/Upgrade of the Security Configuration Record" to install the configuration record. 15) After the configuration record is installed the installation of the BASE system is complete. You will be prompted with: Remove the configuration record tape from the tape drive and enter 'r', , to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 6.5, "Installation and Update of Optional Software Packages" 6.3.2 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the original ones. WARNING: Before attempting any update, it is recommended you have a verified backup of the customer's data. Ensure that this backup doesn't contain any of the OS files. WARNING: OS updates from 1.0A to 1.1A requires that a new dct file be installed. Before attempting an update make a copy of your current dct file and save it in another directory. At the prompt to reinstall dct enter 'Y'. After the system comes back up compare the 1.0A dct SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg045 to the 1.1A dct and make the required changes. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record for the target system (if you wish to re-install the configuration record) 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt (--->), if not go to Section 6.1 to boot the SSM firmware to the level 3 prompt. 2) At the (--->) prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS tape is in the tape drive before entering 'y' This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 2 'Update Installation'. 4) A menu of disk drives the OS can be updated on will be displayed. Enter the drive number that the OS is to be updated on. will cause the OS to be updated on the primary disk drive (wd0). A new mini-root will be installed on the target disk. After the new mini-root is installed the system will be booted on to the mini-root. 5) After the boot process is complete the '#' will be displayed. From this prompt enter ./INSTALL This will bring up the BOSS/VX SOFTWARE INSTALLATION menu 6) From the BOSS/VX SOFTWARE INSTALLATION menu enter option 'u' for Update Install. Messages will be displayed telling that the file systems are being checked and mounted. The target disk must contain aE}" valid BOSS/VX filesystem for the update to continue. 7) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 8) A list of files that will not be updated will be displayed with the prompt: Would you like to change the list (y/n)? Enter 'n', if this list is correct. If you wish to modify the list enter 'y', and you will be prompted SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg046 to add or delete files from the list. 9) The BOSS/VX software will be copied from tape to disk. After which the files that were marked not to be changed will be copied back to their proper place from the gap partition. 10) After the BOSS/VX software is installed you will be prompted with: Would you like to re-install dct (y/n)? NOTE: Updates from 1.0A to 1.1A require this prompt to be answered 'Y'. If the system's configuration has changed and the DCT file needs to be changed/updated with the correct DCT file or you want to put down a default DCT file enter 'y', . Otherwise, enter 'n', . 11) You will next be prompted with: Install the configuration record (y/n)? If you don't wish to install the configuration record, enter 'n', and you will be done with the O.S. update. If the system's configuration has changed so that it requires a new configuration record or you want to re-install the old configuration record, enter 'y', . and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? If you enter 'y', , the configuration record will be installed. If you answer 'n', , the configuration record will not be installed. 12) After the configuration record is installed, the update of the BASE system is complete. You will be prompted with: NOTE: It is recommended at this time you go to Section 6.3.3 'Update of the SSM Firmware' before rebooting the system. Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. You will now be booting off of your system disk. To SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg047 install additional packages see Section 6.5 "Installation and Update of Optional Software Packages". 6.3.3 UPDATE OF THE SSM FIRMWARE The following steps outline the procedure to update the SSM firmware on disk. This procedure overwrites the SSM firmware already on the disk. This procedure would be required if on an OS Installation the steps to install the SSM firmware were skipped, new firmware was released and needed to be installed on the disk, or the SSM firmware on disk became corrupt. The following will be required to update the SSM firmware: o BASE Operating System Tape 1) From the standalone installation program menu choose option 's', for SSM firmware install. 2) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 3) The SSM Firmware will now be copied to disk. 4) After the SSM Firmware is copied to disk you will be prompted with: Press to main menu, or "r" to reboot the system. Remove the BASE OS tape from the tape drive and enter 'r', , to reboot the system. The installation of the SSM Firmware is now complete. 6.4 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration record on a system that doesn't already have one or overwrites the one already on the system. This procedure is used to install a configuration record on a new system if that step was skipped on the OS Installation, put down a new configuration record if hardware changes require a new configuration record or over-write using the same configuration record if the configuration record on disk is corrupt. It will display the configuration record before installing it and give the option to install it or go back to the menu. The following will be required to install the Configuration Record: o BASE Operating System Tape (optional if booting off disk) o Configuration Record tape for the target system 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt (--->), if not go to section 6.1 to boot the SSM firmware to the level 3 prompt. 2) At the (--->) prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg048 tape is in the tape drive before entering 'y' . This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 2 'Update Installation'. 4) A menu of disk drives the OS can be updated on will be displayed. Enter the drive number that the configure record is to be installed on. will cause the OS to be updated on the primary disk drive (wd0). A new mini-root will be installed on the target disk. After the new mini-root is installed the system will be booted on to the mini-root. 5) After the boot process is complete the '#' will be displayed. From this prompt enter ./INSTALL This will bring up the BOSS/VX SOFTWARE INSTALLATION menu. 6) Enter option 'i', for Configuration Record install. The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Put the tape containing the System's Configuration Record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? If you enter 'y', , the configuration record will be installed. If you answer 'n', , the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. 7) After the configuration record is installed you will be prompted with: Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r', , to reboot the system. The installation of the configuration record is now complete. 6.5 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES The following steps outline the procedure to install optional BOSS/VX packages, for example, ITP, MAI OFFICE, Presentation Services, tools, ORIGIN and other packages supplied in a BOSS/VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg049 one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified back-up of the customer's data files before attempting the update. The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 1) If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. 2) Shut the system down to single user mode by using the command 'shutdown -i1 -gx' (where x= the number of seconds to wait). After the number seconds you gave the command has passed you will be prompted with: Do you want to continue (y/n)? enter 'y' Next you will be prompted with: Enter terminal type (default is TERM=dt4313) TERM= Enter your terminal type or . 3) At the command mode prompt enter the command mbfinstall . The following messages will be displayed: Installing products on / Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. 4) Insert the tape containing the package(s) you wish to install in the tape drive and enter . If the BASE system tape is being used for the installation, a message telling you that the tape is an operating system tape, followed by a prompt to continue is displayed. Enter . Messages will be displayed telling you the procedure is skipping to the part of the tape containing the package(s). SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg050 Next, the MAI Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. 5) Enter the number of the package(s) you wish to install followed by a . You can enter them in any order. If entering more than one package on a line follow each entry with a comma. The procedure will put them in the order they are found on the tape. After you enter a number you will be prompted with: Install Product(s) # Are you sure (y/n)? If you answer 'y', , to this question, the number will be added to the list and you will be returned to the menu. If you answer 'n', , the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . The installation of the packages will begin after you enter , you will not have to enter 'S'. If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, . If you wish to abort the procedure and go back to command mode, enter 'ab' . 6) After you have entered the number of all the products you want to install, enter 's', . The procedure will display the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. 7) If a public id is required, a message displaying the current public id and its length will be displayed after the package is installed, followed by: ENTER an 8-char. new Public ID (Hit <0> for a Null Public ID or for no change): Enter the public id you received with the package if it is different than the one displayed. 8) If you are installing more than one package, the next package will be installed. This will continue until all the packages you selected have been installed. After all the packages are installed, the procedure will take you back to command mode. You are now done with the installation of your package(s). If you wish to install additional package(s) from other tape(s), repeat this procedure to install them. 9) Enter '^d' and '2' to return to multi-user mode or '^d' and '0' to shut the system down. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg051 6.6 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES The following sections include special instructions or installation procedures when installing the optional software packages. 6.6.1 MAI PRESENTATION SERVICESTM There are no special instructions for installation and customization of Presentation Services. Ensure the users Path includes the following to access Presentation Services: /usr/mbf/PS /usr/mbf/PS/tools 6.6.1.1 PRESENTATION SERVICES CUSTOM MENUS If the user has created their own menus through PS MENUBUILDER for either their own applications or OFFICE and ORIGIN, they need to transfer those files to the GPx Series 40 and 70 system using Intersystem Transport. The files to be transferred are as follows: SPx: names would be: ../PS/MSMF and ../PS/MSSF-->MENU FILES ../PS/MSH1 and ../PS/MSH2-->HELP FILES MPx names would be: .PS.MSMF and .PS.MSSF .PS.MSH1 and .PS.MSH2 6.6.1.2 PRESENTATION SERVICES FORMS When transferring forms to the GPx system, port only the source form files. Do not port the compiled form file. You will need to recompile your forms once you get them on the destination system. If the user has created their own forms through PS FORMSBUILDER, they need to transfer the following using Intersystem Transport. SPX: /PS/FS1.ENG /PS/FS2.ENG /PS/FS3.ENG /PS/FS4.ENG MPX: .PS.FS1.ENG .PS.FS2.ENG .PS.FS3.ENG .PS.FS4.ENG All programs created and associated files must also be transferred. Programs will need to be modified to use only BB90 directives. Bring the files over using cread but not doing the conversion during porting. Then run BQR to convert the files. After this is done, run SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg052 MKCONVERT. ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities ******************************************************************. * WARNING * * *. * o PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING * * THIS PRODUCT. * * *. * o Your system should be in single user mode. This ensures a * * safe product installation without conflicts with active * * systems users. *. * *. * o You must be logged on as 'root'. This will avoid security * * conflicts during the product installation. * * *. * o Make a full backup of your product (programs & files) * * before installing this new version. * * *. * o The following Path names used are examples only and will * * change if you install the packages into a directory other * * than '/usr'. * ****************************************************************** NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 6.6.2.1 INSTALLATION REQUIREMENTS: New installations: o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.1A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: ADS or DSS or (ADS + DSS): 8.16 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB Updating: o The same requirements for a new installation, plus the following: o You must port all of your current ORIGIN data files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg053 WARNING: The only way to keep separate directories . is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 1.6.1 Presentation Services. ******************************************************************* * *. * Make a full backup of all ORIGIN program and data files, * * currently located at '/usr/origin/r21b and the directories in * * which your *DC0 files are located BEFORE installing this * * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix or directory. * * *. ******************************************************************* NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 6.6.3.1 for MPx and Section 6.6.3.2 for SPx. 6.6.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 6.5. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 6.5. 4. Go into BASIC and start with 256 pages of memory basic s=256 5. RUN "UPDATE" from BASIC. During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR .ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg054 partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the run time directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appears) SECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY > You may now go to step 6 or quit and shutdown before rebooting system. 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 6.6.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B,. the program UPDATE does NOT have to be executed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg055 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 6.5. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 6.5. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), for (a default will appear) Example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 6.5.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 6.6.2.4 UPDATING FROM 2.0A 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 6.5. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 6.5. 4. Go into BASIC and start with 256 pages of memory basic s=256 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg056 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT : This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files. E. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language To delete this node, enter the following from command mode: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg057 cd /usr/origin/r21b/language rm * 6.6.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14 The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 13 The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 6.6.2.3, "Installations Updating from 2.0A". 6.6.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic >start 256 >PREFIX "/usr/origin /usr/origin/r21b /usr/mbf/PS /usr/mbf/PS/tools" >run "ORIGIN" NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. 3. Set up your ORIGIN users. Select Utilities from the ORIGIN main menu. Select User Maintenance, use the password "ADMIN". SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg058 4. Set up your ORIGIN System Parameters. Select Utilities from the ORIGIN main menu Select System Administrator Utilities. The password is ADMIN. Select ORIGIN System Parameters Maintenance option. Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this. directory is "/usr/origin/work/". 6.6.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 6.6.3.1 MPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 6.6.2.4. 2. Perform a verified backup of the ORIGIN system. 3. Using the DIRectory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. Example: .USR.ORIGIN.JKSF01 ---> data file .USR.ORIGIN.JKSF02 ---> data file .USR.ORIGIN.JKSFM2 ---> Application Gen. Program .USR.ORIGIN.JKSFM1 ---> Application Gen. Program .USR.ORIGIN.JKSR01 ---> Report Generated Program .USR.ORIGIN.JKSR02 ---> Report Generated Program .USR.ORIGIN.xxxDC0 ---> Tech. Documentation File .ORIGIN.R20A.DATA.IDD000 ---> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with IDDxxx and reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg059 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From command mode, execute MCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 6.6.3.2 SPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 6.6.2.4. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 ---> data file /usr/origin/JKSF02 ---> data file /usr/origin/JKSFM2 ---> Application Gen. Program /usr/origin/JKSFM1 ---> Application Gen. Program /usr/origin/JKSR01 ---> Report Generated Program /usr/origin/JKSR02 ---> Report Generated Program /usr/origin/xxxDC0 ---> Tech. Documentation File /origin/r20a/data/IDD000 ---> Integrated Data Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Using cwrite utility, write BQR filelist to tape. 5. Restore Intersystem tape on GPx machine using cread utility. Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 6.6.4 ORIGIN 2.1B NEW FEATURES o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg060 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re-generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity between the 're-generated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 6.6.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) -and- /pgm/SPA004 - ORIGIN message file in foreign language (*). /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language * SPA will be used as the language code in this document. o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. MESSAGE TRANSLATION o Set your prefix to work with ORIGIN 2.1B and perform the following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilities -> -> Password (ADMIN) -> Language Translation Menu -> Language. -> Maintain Language -> Enter the language code -> -> Done, you may go to console mode at this point. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg061 o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file, to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) o Using with the system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program directory (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily modified from 2.1A to 2.1B, so a re-translation of this program is recommended: . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg062 translation is complete. 6.6.6 DOCUMENTATION Manual Number Part Number Pages Title _ M7511E 007511-012A 170 MAI Business DATATM Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATATM Technical Reference M0058C 910058-002 132 MAI ORIGINTM User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGINTM Application Generator User Guide M7512D 007512-002 112 MAI ORIGINTM Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATATM System Support Manual M7557G 007557-011 74 MAI Business DATATM User Guide M7561E 007561-002A 166 Presentation Services Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services Forms Management User Guide 6.7 ETHERNET AND TCP/IP For those systems where TCP/IP is not already installed, the following is the installation procedure for Local Area Network (LAN) and Transmission Control Protocol (TCP). 1. Ensure that your system is properly connected to the network, and that you have installed the Eagle Ethernet Controller (refer to the GPx Series 70 Installation and Maintenance Manual, M8226). 2. Mount the operating system release tape that contains the TCP/IP files. 3. Shutdown the system to single-user mode. At the command prompt, enter mbfinstall. From the list on your screen, select both the LAN and TCP products to install. NOTE: Select LAN first, as LAN should be installed before TCP. The system prompts you to confirm your selections. Files are restored from the tape, and you are prompted for controller and . public key information, as explained in the next steps. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg063 4. ENTER LOCAL AREA NETWORK CONTROLLER INSTALLED: o Eagle Ethernet Controller o SCED Ethernet Controller o Eagle and SCED Ethernet Controllers o None Enter the option number for the Eagle Ethernet Controller, which is the only controller presently supported on GPx 70. 5. HOW MANY EAGLE ETHERNET CONTROLLERS ARE CONFIGURED?: Enter the number of controllers configured. 6. Changing network configuration will update the following files /etc/hosts, /etc/hosts.equiv, /etc/netconf, /etc/inetd.conf, /etc/services and destroy the previous configuration. Do you want to change network configuration (y/n)? (CR=no) NOTE: You must enter 'y' to install the product. 7. ENTER THE INTERNET ADDRESS: Enter the Internet Address. Assuming you are installing the network for the first time, you must assign a series of Internet addresses to the various devices on the network. It is highly recommended that an address of 50.0.0.1 be used as a starting point. The additional devices on the network can be set up as 50.0.0.2, 50.0.0.3, etc. 8. ENTER PUBLIC KEY (8 CHARACTERS): Enter the public key. The system prompts you to enter the key a second time for verification. Because TCP/IP is an optional, chargeable feature, a public key unique for your system serial number must be installed. If you do not have a public key, contact your MAI representative. You may enter the key later by using the install_key command. 9. You must assign a unique name to the system using this command: #uname -S 10. After installing TCP/IP and a public key, shut the system down (to the firmware level), and reboot the new TCP kernel to enable Ethernet operations. 11. Edit the /etc/hosts file. Add the name and IP address of your system; then add the name and IP address of a second system on the same network. (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg064 For example, the /etc/hosts file for a system named mfg1 contains the following entries: # # Host Database # This file should contain the names and addresses # for local hosts that share this file # # If the name server is running this file is not consulted # # Choose a distinguished local network address for local host. # 127.0.0.1 loopback lb localhost # #Imaginary network 97.0.0.1 mfg1 #this host 97.0.0.2 mfg2 #second system 12. You can now communicate with the selected system using applications such as rlogin, rcp, or ftp. NOTE: If terminal servers are going to be used, the ntcp parameter in a dct file will need to be set to at least 1-1/2 times the number of terminal server ports. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB028 Pg065 FIB 00029 03/06/91 *** BOSS/VS to BOSS/VX Conversion Tips [ WPSF 673 ] *** BOSS/VS TO BOSS/VX CONVERSION TIPS DALE JENSEN 2/91 673 TYPE: Informational PURPOSE: Due to the number of calls received on transport/conversion, this Field Bulletin will serve as a quide when converting from an MPx or Advanced Series System to a GPx Series. PROCEDURE: The transport/conversion to the GPx is similar to the transport/conversion between an MPx Series and the MAI 2000-4000 and has been written to be compatible with those existing transport packages. Only transports using 1/4" cartridge tape will be discussed, although ATP 4.0 or TBC could be used. Please refer to the Intersystem Transport Package User Guide, number M6354, for more specific information on the use of these packages. PLANNING: Planning is an important part of a successful conversion. There are many steps which need to be performed from selecting the transport media to be used to testing the applications once converted. Below are some key steps in planning the conversion and some suggestions on when the steps should take place. 1. Select the media to be used. The most common conversion method is using 1/4" cartridge tape drives. Ensure the MPx/AS has the proper controller, tape drive, configuration record and cable. Also ensure enough tapes are available. Order any equipment as needed. This should be planned at least two months in advance. Below is a list of hardware requirements. Cartridge Tape Tape System Drive Controller Cable 8000 MTC MODEL BMTC # PART # Series 4403/4406 903413-001 907567-001 9000 & MTC MODEL BMTC # PART # ASxx 4403/4406 903413-001 907567-001 Series OR SCSI MTC DMA II PART # 4408/4410 916170-001 916170-001 Note: The 7000 Series, AS20 Series and 9400 Series system have a catridge tape drive as part of the base unit. The AS40 Series also comes with a cartridge tape drive when shipped as a new unit but is not required if the system was an upgrade. 2. File preparation (see below for details). This can be started well in advance of the actual conversion. Allow at least 3 weeks for this step. Determine if the software vendor needs to be involved. Some application packages already have programs that will perform conversion steps required when porting from MPx/AS to GPx. Some application packages will need an updated version ordered and only SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB029 Pg001 the data files transferred. 3. Examine programs (see below for details). Make as many program modifications prior to the conversion as possible and document changes that can not be done until the application is ported. It is a good idea to port the program to a GPx system at least 3 weeks in advance and print the FLAGIT output file. The FLAGIT output file contains a list of possible errors for each program ported. 4. If possible, start testing the applications and making changes as required either on a test system or the customer's system 2 weeks prior to going live using test data files. Any special devices such as non-MAI printers and terminals should be tested for compatibility. 5. Build system filelists of data to be transferred and build BQR filelists at least 3 days prior to the final conversion. 6. Determine the amount of data to transfer and estimate the time it will take. See tape conversion tips, below, for average times. Start the tape backups and restores in at least the estimated time in advance. 7. Set up new operator log-ons, define terminal and printer ports, define new spooler classes and forms and set up file access rights. 8. If the above steps were followed, you should be able to go live with few remaining changes. In our experience, it may take up to one week to make these changes. PROGRAM AND DATA FILE CONVERSION: The GPx is a lower order ASCII system as is the MAI 2000-4000 so any program modifications that were required on the MAI 2000- 4000, will also be required on the GPx. In addition, the GPx is running pure BB90 so there may be other modifications required to be BB90 compatible. The basic steps required for porting are as follows: 1. File preparation a. Validate and reconstruct all data files. Use !DISKANALYZER to validate all files and use !RECONSTRUCT to repair them. Files with errors can cause errors during the tape . transfer process which may cause the process to abort. NOTE: The M.7A version of 'MCSI' will deal with some errors such as 'File claims xxx records, yyy actually found'. b. Determine file path names and logical grouping of files. The 'BQR' utility keeps only the leaf name of the file when using a system filelist to create the BQR filelist. As a result, there could be several duplicate file names in the BQR filelist. When restoring the data using the 'cread' utility, the user is asked to enter a directory for receive files and the duplicate names will be restored as follows : .MPX.ACCT.FILE1 and .MPX.PAYROLL.FILE1 would be named FILE1 and FILE1 in the . BQR filelist. If /rcv/directory is specified for the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB029 Pg002 directory to receive the files, the file names will then become /rcv/directory/FILE1 and /rcv/directory/FILE1.000. It is recommended to backup files you want grouped in different directories on separate tapes. c. File access rights will be different on the GPx. The access rights are divided into three groupings which include the owner of the file, a group access, and all others. If file security is to be enforced, current file usage rights should be documented. d. Files should be transferred in text mode unless the entire file contains binary data. Any file that has binary fields within a record should be transferred in text mode and then the binary fields will need to be converted with a BASIC program on the GPx system using an XOR function with a $80$. 2. Examine programs: a. Programs should be BB86 compatible to minimize program modifications. b. Check programs for use of system commands and determine what changes will have to be made. Some common utilities used in programs that will require several changes are : '!SORT' must be changed to use the UNIX '!sort' command which only works with string files. '!SUMBIT' will have to be changed to '!psubmit' and allows only string files to be submitted. c. Check programs for usage of fully specified path names when OPEN, RUN START or CALL directives are used. Changes will be required to use the new directory name. d. System functions that may be different are the 'FID' and 'TCB' functions. You should replace the 'FID' function with the 'ATTR' function. Check the BB90 reference manual for differences. e. Protected or PSAVED programs can not be transported. You must use the source code which may be protected again after the conversion. f. The MPx uses high order ASCII and the GPx uses low order ASCII. Check programs that rely on specific hex string values. In most cases you will have to modify high order hex codes to low order hex codes. Hex values will be flagged during the conversion process on the GPx system if level 1.1A or greater is used. g. The MPx allows a space in directives such as 'GO TO', 'GO SUB' and 'INIT FILE' but the space is not allowed on the GPx. h. BB90 reserved words used as variables should be replaced by nonreserved words. See the Business BASIC 90 Reference Manual for the Keyword list in appendix D. i. The MPx allows a ';' prior to an 'ENDIF' or 'FI' directive and the GPx does not. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB029 Pg003 j. The MPx allows a '$' after a function name such as 'PNM$' and the GPx does not. TAPE CONVERSION TIPS: The most common way to get data and programs from an MPx to a GPx is by using 1/4" cartridge tapes. The program used to write the tape on the MPx is 'MCSI' and the GPx uses 'cread' to read the tapes. The GPx will read 45/60/120 MB tapes, but only writes to 120 MB tapes. The GPx will also read 525 MB tapes with the release of 1.1A. The GPx requires the ITP package to be restored from the base operating system tape using the 'mbfinstall' program. The MPx will have the intersystem transfer package restored during the O.S. installation. NOTE: When installing the ITP package, you will be asked for a key. The key is only needed if you want the auto features of ATP, it is not needed to do transports. When using tape for the transport, you should select the option to convert both program and data files during the transport (default). In addition, option 3 will allow you to have error logging for programs. On the GPx, errors found in programs during the conversion are written to a file called 'itplog.###' which is found in the directory that the files you are transporting go in. This one file contains the program name, last statement number, and any problems found for all programs. To print this file use 'lpr /directory/itplog.### list=printer(lp,p1,etc.)'. The GPx Series restores tapes with conversion and error logging at the approximate rate of 115MB per hour for data files and 6.9MB per hour for program files. The MPx will complete building 'BQR' filelists and backup files at the approximate rate of 108MB per hour for data files and 14MB per hour for program files. RELATED DOCUMENTATION: There are several manuals that contain conversion topics. The Business BASIC 90 Reference Manual and the Intersystem Transport Package User Guide are the most useful. Below also lists some additional documentation. - GPx Software Announcement numbers 168 and 175. - Business BASIC 90 Reference Manual number M6262, chapter 15 - BOSS/VX System Administrator Guide number M0187, chapter 9 - GPx Series 40 Sales Guide page 9-34 - GPx Series 70 Sales Guide page 9-34,35 - Intersystem Transport Package User Guide number M6354 NOTES AND CAUTIONS: 1. Files that contain binary fields should be identified and transported as text data. After the files have been restored to the GPX, the binary fields can be converted back using the 'XOR' function with a $80$ for each byte of the field. 2. Another thing that may cause a problem is 'umask'. 'umask' determines the file modes for files created in UNIX. During the transport this is used for data files and comes set for read/write SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB029 Pg004 for owner and read only for everyone else. Before starting the transport, make sure 'umask' is set to 000 for the operator running the transport. To set it on at the UNIX prompt, enter 'umask 0 '. For more information on 'umask' see the Software Announcement 168 or 175. 3. The 'MCSI' utility on the MPx Series System will support multi- reel backups but the 1.0A version of 'cread' does not. Do not span tapes on the MPx while doing conversions until 1.1A is available on the GPx. The BOSS/VX Release 1.1A 'cread' will support multi-reel tapes. 4. Multikeyed files are not supported by the conversion utilities on releases prior to M.6G for the MPx Series systems. To transport multikeyed files, use BOSS/VS Release M.6G or higher. 5. The 'bsearch' utility can be used with the 'search and replace' option on the GPx Series system to detect error 20's. A non- existent search string can be used if no replacements are required. This may be useful since 'FLAGIT' will only run once during the actual conversion. 6. When output from the 'bsearch' utility is sent to a printer, the program name is on the wrong page. The errors reported will be listed under the wrong program name. The program name on the next page will be the correct name. This will be corrected in a future release. 7. In cases where programs are converted and there is more than one syntax error on a line of code, if 'bsearch' is being used to 'search and replace' code, the changes will not be saved. The program '/usr/mbf/bin/SREP' executes a SYNTAX directive on the line of code to be changed and takes an error branch due to the second syntax error on the line. The change is not saved. Line 5297 can be modified to REM out the SYNTAX check and the changes will be saved. Do not leave this modification in the program after the conversion is complete and be aware that any replace patterns will not be checked for proper syntax with the modification. 8. Tapes containing archive data written using the MPx/AS utilities will have to be converted and then archived using GPx tape backup utilities. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB029 Pg005 FIB 00030 03/07/91 *** 'fcopy/fmove' on 1.1A Destroys Program Files [ WPSF 660 A2 ] *** GPx Series 40 Dan Arteritano Addendum 660 fcopy/fmove changes programs to string files Type: Problem Cause: On the 1.1A version of the Operating System, 'fcopy' and 'fmove' change BASIC programs to string files. The original program is the only program that will be able to be run, when copied with 'fcopy'. If a program is moved with 'fmove' the destination program will be a string file with NO original program that will run. Workaround: Use the UNIX 'cp' or 'mv' commands to copy or move programs. Example: cp /usr2/pgm/MENU /usr2/newpgm mv /usr2/pgm/MENU /usr2/newpgm The /usr2/pgm/MENU is the original program, /usr2/newpgm is the destination directory and the new file name will be /usr2/newpgm/MENU. Solution: This has been fixed in 1.1B. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB030 Pg001 FIB 00031 03/27/91 *** Known GPx70 Printer (Spooler) Problems [WPSF 683] *** GPx Series 70 Wally Moore 02/28/91 Printer Issues Type: Problem Purpose: The purpose for this field bulletin is to describe and give fixes/work arounds.for the printer issues that are presently identified on the GPx Series 70. If more problems are identified or other solutions are found this field bulletin will be updated. Symptom Error 255, command level error -4060 when spooled printer is opened. Cause There are four processes for a spooled printer. The ptstart process starts all the spooler processes for a printer. After starting the processes it is.not used again. The upddaemon process is the spooler process that is called each time any printer is open (spooled or non-spooled). If the job is spooled it will pass the job information on to the lpd processes (2 of them). If the job is non-spooled the upddaemon process will handle the printing of the job. In the case of the above error the upddaemon process has lost communication with the lpd processes. Solution The way to sync up the processes and get them re-communicating is to kill the ptstart process for the printer. The ptstart process when killed will be respawned (restarted) by init. ptstart when started will first kill all processes that have to do with the printer. Next it will restart the printer processes, which will resync the processes. To find the ptstart process for the printer that is getting the error, use the command: ps -ef |grep PRINTER_NAME where PRINTER_NAME is the upper case printer name, as LP, P1, P2, etc. This command will list all the processes for the printer, one of which will be 'ptstart PRINTER_NAME'. This is the process that you will need to kill. It will then kill and respawn all the printer processes so the upddaemon process can again communicate with the lpd processes. Symptom Print jobs in the spool queue but jobs not printing. Printer status can be idle or printing. Job status is waiting. Cause The next job that shows in the print queue to be printed is either missing SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB031 Pg001 from the /usr/mbf/etc/_qtemps directory or the queue file has no data in it (0 bytes). Solution Find the job number of the jobs in the print queue (use the lpq command or pqueue utility ). Use the 'ls -l' command to find if the queue file is in the /usr/mbf/etc/_qtemps directory and is larger than 0 bytes. If the file is missing or contains 0 bytes remove it from the print queue by killing the job. If the printer still does not print, check the next file to be printed. Continue this process until all missing or 0 byte files are removed from the print queue. Symptom After a form change the printer status is 'waiting for go'. Cause/Solution The cause and solution for this problem is the same as for the above problem 'print jobs in the spool queue not printing'. Symptom After form change the printer continues to show the old form, not the newly mounted form. Cause This is usually caused by the printer being offline or the printer opened in non-spooled mode. In either case the spooler is unable to load the new form into the printer. Solution If.the printer is offline, put it online. If this is not the problem use lpstat to see if the 'job#' field shows either 'basic' or 'lpr'. If either of these show in the 'job#' field then the printer is opened in non-spooled mode and needs to be closed before the new form will be mounted. The information in the 'job#' field will disappear if the ptstart for the printer has been killed. If there is nothing in that field then you will need to check with the users to see if they have the printer opened in non-spooled mode. As soon as the non-spooled printer is closed the new form should show up as the mounted form. Symptom During a form change the option to use live data is taken and no test data is printed. Cause If the live test data to be printed contains 'print @s' then the data will be skipped and not printed. Any data in the file that doesn't have a 'print @' will be printed. Solution At this time the only solution is to only use data that does not contain 'print @s'. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB031 Pg002 Symptom Print job shows a status of error. Cause This is caused by some error having to do with the printer or print job. To find the cause use the command lpstat printer_name -error From this information you should be able to determine the cause of the error and correct it. Symptom A special form is mounted on a printer. After the a job is printed the stanrd form is remounted automatically. Cause This can occur for one of two reasons. The first reason is that a printer is opened with spooling turned off after a special form is mounted, either using 'class=' or '-off'. After the printer is closed the stanrd form will be automatically remounted. The other reason would be if while doing the form change a test with live data was done and then the utility was exited with a MB IV and not a return. In this case the first job will be printed with the special form then the stanrd form is automatically remounted and all the other jobs with the special form will have a status of fwait. Solution At this time there is no work around other then going back into pformchg and remounting the special form. Symptom A special form is set up for a printer in the printer defaults file and the form is not mounted on the printer at boot time. Cause The spooler is designed to always mount the stanrd form at boot time. The spooler does not check the printer defaults file to determine the form that should be mounted. Solution A shell script can be written that will mount the special forms on the printer. This script can be run at boot time or after the system is booted. For more information on the shell script please see field bulletin 651. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB031 Pg003 FIB 00032 04/01/91 *** Repair lpq.que file without rebooting *** SYMPTOM/TEXT: File /usr/mbf/etc/_queues/lpq.que gets corrupted and spooler becomes unusable. FIX: THe first and quickest solution is to execute the command "lpmaint -fix". This should recreate the /usr/mbf/etc/_queues/lpq.que file. If it does not and an error occurs then you can just delete the /usr/mbf/etc/_queues/lpq.que file, using the rm command. Then go ahead and execute the lpmaint -fix command. A shell script is executed on every boot (/etc/rc2.d/S90PTRQFIX) which recreates this file if it is corrupted. ORIGINATOR: Kim Yaworsky SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB032 Pg001 FIB 00033 04/02/91 *** lpstat -error command [ WPSF 690 ] *** GPx 40/70 Dan Arteritano lpstat -error command Type: Informational Purpose: This is a method of displaying a more detailed explanation of spooler errors. Symptom: The status of a printer is displayed when 'lpstat' or 'pqueue' is run. It is possible that the status will be 'error' but there is no detailed explaination of the error. To determine the the actual system error enter the following: lpstat lp -e This command will display the status of the printer and any errors that occurred while attempting to print. These errors are stored in the /usr/mbf/etc/ directory in .err files. The file can also be displayed with the following command: pg /usr/mbf/etc/lp.err (Either command displays the same messages) The display will be as follows: ________________________________________________________________ | | | ---------- lp error log ---------- | | | | Wed Mar 27 09:08:05 1991 | | Initial check -in. | | | | Wed Mar 27 09:08:15 1991 | | Error -171 loading 'stanrd' form | | | | Wed Mar 27 09:08:15 1991 | | Error -171 opening printer lp | | | |______________________________________________________________| To determine what an error -171 is enter the following: errno 171 !errno 171 if in BASIC The display will be: Errno 171: Printer offline ORIGINATOR: D. Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB033 Pg001 FIB 00034 04/03/91 *** Use of UNIX Commands on Opened Files [ WPSF 679 ] *** BOSS/VX 679 USE OF UNIX COMMANDS ON OPENED FILES DALE JENSEN 3/91 CODE '9' TYPE: Problem PURPOSE: The purpose of this field bulletin is to eliminate possible file corruption by performing UNIX commands on opened files. SYMPTOM: The exact symptom resulting from performing UNIX commands on opened files is unpredictable. Some of the symptoms will include: data files missing records, data files having incorrect record counts, errors reported when 'frepare' is run, unexpected BASIC errors, terminal hangs when accessing corrupt files, or other file related problems. CAUSE: UNIX commands such as 'cp', 'mv', 'dd', 'tar', 'cpio', 'dump' and 'restore' can be used on opened or locked files. When these commands are executed on a file that is in use, the file integrity of the new copy (either on tape or disk) will be unknown. If these files are used to replace the original, such as restored from tape, the file corruption may be compounded by repeating the process. SOLUTION: Although UNIX allows online backups and file copies, these commands should never be used when files are being accessed by users due to the unpredictable results described above. An on-line backup facility is currently being developed which will allow opened files to be backed up to tape using 'cpio'. This facility is expected to be included in the 1.1A release for the GPx Series 70, and a future release for GPx Series 40. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB034 Pg001 FIB 00035 04/04/91 *** 1.1A Software Announcement for GPx40 [ WPSS 191 ] *** GPx SERIES 40 1.1A DAN ARTERITANO 2/91 191 1.0 INTRODUCTION Level 1.1A-40 of BOSS/VX for the GPxTM Series 40 is now available. This is the recommended Operating System for the GPx 240, 340, 440 and is the release required for the GPx 640. The 1.1A Operating System is derived from the 1.0D O/S and contains new features, enhancements and corrections to the 1.0D Operating System release. This Software Announcement contains general information about the Level 1.1A BOSS/VX Operating System. Installation and update procedures are fully documented in this announcement. Also, this document has sections on enhancements/corrections, new features and new/updated manuals. It is recommended that you read this document before installing Level 1.1A. For information on ordering 1.1A refer to Marketing Announcement 1035 for the GPx 2/3/440 and M/A 1010 for the GPx 640, both apply to U.S. and Canada. New Features Include: o Errorlog Watcher o Third Party Software Support Product o Dynamic Serial Port Configuration o GPx 640, 80486 Processor Based System o Multi-Function Card with 2 Parallel Printer Ports for the GPx 640 only o Enhanced NMI & UPS Support o Multi-Volume 'cread' Support o 128 User Connectivity with Terminal Servers o UPD Simple Compiler o File Write Options o CISAM/BFS CAUTION: Improved handling of the NMI and UPS signals has exposed a possible hardware problem on 3/440s. When booting from tape to upgrade to 1.1A, the following message may appear: HALT: DO NOT REBOOT ON BATTERIES! This is caused by incorrect wiring in the NMI/UPS assembly. WORDAROUND: Unplug the cable connected to the NMI/UPS assembly from the CMB. Fix: Order a new 'Reset UPS Assembly', P/N 903845-001. TABLE OF CONTENTS 1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . .Cover SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg001 2.0 BOSS/VX Operating System History. . . . . . . . . . . . . . . . . . 1 3.0 New Products in Level 1.1A. . . . . . . . . . . . . . . . . . . . . 1 3.1 New Software Products. . . . . . . . . . . . . . . . . . . . . 1 3.1.1 UPD Simple Compiler . . . . . . . . . . . . . . . . . . 1 3.1.2 On-Line Configure Utility . . . . . . . . . . . . . . . 2 3.1.3 File Write Options. . . . . . . . . . . . . . . . . . . 2 3.1.4 CISAM/BFS . . . . . . . . . . . . . . . . . . . . . . . 3 3.1.5 User Access of BFS C-Library Functions. . . . . . . . . 3 3.1.6 Third Party Software Product. . . . . . . . . . . . . . 3 3.1.7 Error Log Changes . . . . . . . . . . . . . . . . . . . 4 3.1.7.1 Turning Off Async Errorlogging. . . . . . . . . 4 3.2 New Hardware Products. . . . . . . . . . . . . . . . . . . . . 4 3.2.1 GPx 640, 80486 Processor. . . . . . . . . . . . . . . . 4 3.2.1.1 Supported Parallel Band Printers . . . . . . . 4 3.2.2 VGA Monitor and Keyboard. . . . . . . . . . . . . . . . 5 3.2.2.1 Installation of the VGA Monitor. . . . . . . . 5 3.2.3 525MB 1/4" SCSI Tape Cartridge. . . . . . . . . . . . . 6 3.2.4 8mm, HCC SCSI Tape Drive. . . . . . . . . . . . . . . . 7 3.2.5 GCR 1/2" SCSI Interface Tape Drive. . . . . . . . . . . 7 3.2.5.1 Accessing the GCR through BASIC. . . . . . . . 7 3.2.6 MTS 1/2" Tape Drive Device Files. . . . . . . . . . . . 8 3.2.7 GPx 40 Expansion Chassis. . . . . . . . . . . . . . . . 8 3.2.7.1 Using diskadd for disks on SCSI controller 1 . 8 3.2.8 SCSI Converter (Rancho Card). . . . . . . . . . . . . . 8 4.0 Diagnostics Products . . . . . . . . . . . . . . . . . . . . . 9 4.1 Errorlog Watcher. . . . . . . . . . . . . . . . . . . . . 9 4.1.1 Errorlog Watcher Operating Instructions. . . . . 9 4.1.2 Configuring Errorlog Watcher . . . . . . . . . . 9 4.1.3 Starting Errorlog Watcher. . . . . . . . . . . .11 4.1.4 Seeing the Results from Errorlog Watcher . . . .12 4.2 Memory Parity Error Handling. . . . . . . . . . . . . . .13 4.3 New NMI Interrupt Messages. . . . . . . . . . . . . . . .13 5.0 Installation and Update of the Operating System and Optional Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . .14 5.1 Installation of the BOSS/VX Operating System . . . . . . . . . .14 5.1.1 System Disk Partitioning. . . . . . . . . . . . . . . . .19 5.2 Update of the Operating System . . . . . . . . . . . . . . . . .20 5.3 Installation/Update of the Security Configuration Record . . . .23 5.4 Installation and Update of Optional Software Packages and Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . .25 5.5 Customization of Optional Software Packages. . . . . . . . . . .27 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg002 5.5.1 Presentation Services . . . . . . . . . . . . . . . . . .27 5.5.1.1 Presentation Services Custom Menus. . . . . . . 27 5.5.1.2 Presentation Services Form. . . . . . . . . . . 28 5.5.2 ORIGIN 2.1B GPx Installation Procedure . . . . . . . . . 28 5.5.2.1 Installation Requirements . . . . . . . . . . . 29 5.5.2.2 New Installation of ORIGIN 2.1B . . . . . . . . 30 5.5.2.3 Updating From 2.1A. . . . . . . . . . . . . . . 31 5.5.2.4 Updating From 2.0A. . . . . . . . . . . . . . . 32 5.5.2.5 Updating From 1.3B or 1.3B. . . . . . . . . . . 33 5.5.2.6 Executing ORIGIN on the GPx . . . . . . . . . . 35 5.5.3 ORIGIN Conversion. . . . . . . . . . . . . . . . . . . . 35 5.5.3.1 MPx to GPx Conversion . . . . . . . . . . . . . 36 5.5.3.2 SPx to GPx Conversion . . . . . . . . . . . . . 37 5.5.4 ORIGIN 2.1B New Features . . . . . . . . . . . . . . . . 37 5.5.5 Translation. . . . . . . . . . . . . . . . . . . . . . . 38 5.5.6 Related Documentation. . . . . . . . . . . . . . . . . . 40 5.6 Installation of TCP/IP. . . . . . . . . . . . . . . . . . . . . 41 6.0 Communication Packages . . . . . . . . . . . . . . . . . . . . . . . 41 6.1 27xx/37xx Batch Emulation . . . . . . . . . . . . . . . . . . . 41 6.1.1 Software Requirements and Installation . . . . . . . . . 41 6.1.2 Hardware Requirements and installation . . . . . . . . . 42 6.1.3 General Information. . . . . . . . . . . . . . . . . . . 43 7.0 Notes and Cautions . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.1 ATP Notes and Cautions. . . . . . . . . . . . . . . . . . . . . 48 7.2 PC-Link Notes and Cautions. . . . . . . . . . . . . . . . . . . 48 7.3 TBC Notes and Cautions. . . . . . . . . . . . . . . . . . . . . 49 7.4 TCP/IP Notes and Cautions . . . . . . . . . . . . . . . . . . . 51 7.5 Terminal Server Notes and Cautions. . . . . . . . . . . . . . . 51 8.0 Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . 52 2.0 BOSS/VX OPERATING SYSTEM HISTORY 1.0A First release of BOSS/VX. It was required for the GPx 340 and 440. 1.0B This release introduced the GPx 240 and 27xx/37xx Communication and is needed if mother board part number 916556-004 is installed in a GPx 440. This mother board will cause a PANIC if installed with 1.0A. 1.0C This release introduced the 1/2" MTS tape drive, Ethernet controller, 670 MB disk drive, support of up to 64 users, DOS Read/Write capabilities, PT-4220 serial printer, Slave printing on the DT-4312, TERMCAPS and TERMINFO files on the DT-4312 and DT-4309, displaying dashes when Security Violation PANICs occured the addition of lphold, printversion and bbmap commands. There were a number of bug fixes/enhancements including automatic shutdown when the UPS becomes active, the spooler will only reprint the page it SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg003 failed on rather than restart at the beginning of the print job when there are form feeds in the application and changes to oprinfo. 1.0D Contained PS 3.3B, which had enhancements and corrections to PS 3.3A. There was also a fix for an End of Media problem on the HCC tape drive and the 1/2" tape drives. 3.0 NEW PRODUCTS IN 1.1A 3.1 NEW SOFTWARE PRODUCTS 3.1.1 UPD SIMPLE COMPILER Universal Printer Driver (UPDS) is a software subsystem that . provides printer support for all MAI systems. It is now available on 1.1A and requires a public key for use. UPDS is a product that is installed with mbfinstall. See Section 5.4 for details. o SIMPLE Compiler: Reads driver source code and generates interpretive object code which, when executed, processes a stream of data for delivery to a specific printer. o Printer Definition Files (PDFs): The object code produced. by the SIMPLE compiler. MAI provides one PDF for each model printer it supports, in the /usr/mbf/etc/ptrtbl directory. o UPD Interpreter: Interprets and provides runtime support for PDFs. PDF source code is platform independent, but the interpreter is programmed for a specific host. o DESPOOLER: Part of the host operating system that opens print files, reads data records and delivers them to the UPD Interpreter for processing by the PDF. o TRANSLATION FILE: Translates the data received to what the printer understands. Refer to the Universal Printer Driver Reference Manual, M0053 for detailed instructions. 1.1A GPx 40 3.1.2 ON-LINE CONFIGURE UTILITY The configure utility will now allow configured ports to be changed and non-configured ports to be configured while the system is in multi-user mode. o To run 'configure' the operator must be 'super user' and it can only be run on 1 terminal at a time. o If a device is in use configure will not allow it to be changed. 3.1.3 FILE WRITE OPTIONS Business BASIC data files now can have write-through capabilities similar to BOSS/VS. BOSS/VX implements three different types of write-through as described below. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg004 Buffered Write This is the default method which buffers each write in memory before it is written out to disk. Each buffer is automatically flushed out to disk every 30 seconds or when the file is closed. Writes with the buffered option return immediately to the user after the data has been written to a buffer in memory. WriteThru When file writethru is in affect all writes are written directly to disk. With the writethru option each write operation waits until the write to disk has completed before it returns. Although this method eliminates the small 30 second window of the buffered option, a performance penalty results with its use. WriteAhead The writeahead option is not as costly as the writethru, but not as fast as the buffered write. Writeahead means that on each write operation the memory block is marked for immediate write to disk, but the user does not wait for the write to disk to complete before the write operation returns. Utility Changes The 'fcreate' and 'fchange' utilities have an added option 'Source. File Write:' which allows the user to select which of the three write modes should be used for the file. The 'finfo' utility has an added field 'SOURCE FILE WRITE' to show which of the three write modes the file is using. 3.1.4 CISAM/BFS CISAM/BFS functions are used to create, maintain and manipulate primarily multikeyed files from 'C'. It is also possible to open and manipulate direct and sort files that were previously created. The CISAM/BFS library has to be linked with the user program to perform all tasks necessary for the maintenance and manipulation of a user defined indexed file system. These functions provide for: o the creation of files and associated primary indexes o the addition and deletion of further indexes o the opening, closing and deletion of existing files o the selection of the index to be used for subsequent reading and/or writing of records and the start point within the file o the reading, writing and updating of data records o the random and sequential access of records within a keyed file o locking of individual records, groups of records or whole files SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg005 3.1.5 USER ACCESS OF BFS C-LIBRARY FUNCTIONS BFSINT (BASIC File System INTerface) is a library which provides a set of C-callable procedures for applications which require record level access to BFS files. Access to files may be by KEY or INDEX, and locking/timeout control is performed using options which are similar to those found in Business BASIC. Record level access includes the ability to create, delete, open, close, lock and unlock files. Multi-keyed file create and MAGNET remote access are not supported on the initial release. Refer to the BFSINT Reference Maunal, M0228 for detailed information. 3.1.6 THIRD PARTY SOFTWARE PRODUCT The Third Party Software (TPS) product has been added to the 1.1A Base O/S tape. The contents of this product are the terminal files, install scripts, README files and other files necessary for TPS packages to run on the GPx systems. The TPS product is installed with mbfinstall which is explained in Section 5.4. For instructions to install a specific software package refer to that particular software announcement. The TPS product has files for the following packages: WordPerfect Access 20/20 Uniplex Lotus 1-2-3 Informix Oracle Sybase 3.1.7 ERROR LOG CHANGES The format of the error log report has the following enhancements: o SCSI Tape and Disk format for GPx Series 40 and 70 is the same. o Format is aligned for better readability. o Format is broken into three columns as follows: - Column 1: Field Description - Column 2: Numerical value of error in Hex - Column 3: Description of error if applicable 3.1.7.1 TURN OFF ASYNC ERRORLOGGING The mbf_errlog command has a new option '-noasync'. This option stops the logging of all async terminal error(s) in the error log file. This option will prevent the display of warning message(s) on the system console. The '-noasync' option must be added the error log start command, within the '/etc/rc2.d/S80errlog' file. The command should appear as follows: /etc/mbf_errlog -quiet -noasync & After the change has been made, the system then would need to be rebooted for this new option to take effect. To restart error logging of async errors remove the '-noasync' parameter and reboot the system. 3.2 NEW HARDWARE PRODUCTS 3.2.1 GPx 640 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg006 The GPx 640 is an 80486 based multi-user system which supports up to 128 users, 64 users on 16-ways and 64 via terminal servers. The GPx 640 supports 16MB of RAM using 2MB SIMMs. The 640 will also support up to 7 hard disk drives when used in combination with the Expansion Chassis which can support up to 5 disk drives using a combination of full and half height drives. The system comes standard with a 525 MB 1/4" cartridge tape drive and a Multi-Function Card (MFC) which supports the COM1 (console), COM2 (builtin MODEM) and 2 parallel printer ports. The COM ports on the MFC card have the same capability as 8/16-way ports which means that their use is not restricted as on the 2/3/440s. 3.2.1.1 SUPPORTED PARALLEL BAND PRINTERS The MFC allows the use of parallel band printers, with the option to configure the port for a Data Products or Centronics interface. The supported band printers are the PT-4209, PT-4220, PT4221 and PT-4230 also known as the 900 LPM printer. The PT-4220 serial band printer is still supported also. 3.2.2 VGA MONITOR AND KEYBOARD The MBF VGA color and monochrome monitors are supported on the GPx Series 40 platforms. The monitor is usable as a standard UNIX device with UNIX System V Release 3.2 'C' applications and CANNOT be used as a BFS (BASIC-capable) device. The 240 has a built-in VGA interface, which the monitor is attached to. The 3/4/640 systems needs the optional adapter card, P/N 400078-001. For more information refer to the GPxTM Series 40 Installation and Maintenance Manual Addendum Package, M8215B, pages 15-19. NOTE: To change the CMOS on a system with a monitor, the operator can press ++ any time between the self-test at boot-time and when UNIX boots. 3.2.2.1 INSTALLATION OF THE VGA MONITOR STEP 1: Power down the system, install the VGA controller, plug in the keyboard and monitor and power on the monitor. NOTE: If the operating system is already 1.0C or higher, . it is not necessary to use an Operating System tape in this procedure. Skip to Step 5. STEP 2: Place the 1.0C or higher Base operating system tape in the tape drive and power on the system so that the system boots from the tape. To boot from tape on a GPx 640 refer to Section 5.4, Step 1A. NOTE: If a monitor is being added to a GPx 240, skip to Step 4. STEP 3: All boot messages will appear on the monitor. On the GPx 340/440/640 the following message will appear: EQUIPMENT CONFIGURATION ERROR - RUN SETUP SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg007 PRESS F1 KEY TO CONTINUE OR CTRL-ALT-ESC FOR SETUP Press CTRL-ALT-ESC to display the SETUP menu. Select 7. PRIMARY DISPLAY: The monitor types will be displayed. Select 4. SPECIAL ADAPTER The Hardware Configuration Menu will redisplay Select E. END AND REBOOT The system test will be performed again and the Operating System Installation Menu will be displayed. STEP 4: Select I for Install or U for Upgrade. No additional packages need to be installed for the VGA to work. After the Operating System installation, reboot from the hard disk. STEP 5: While the system is booting, the following message will appear: Configuring monitor, please wait . The configuration files are being changed to allow COM1 to be used as a user port. The installation is complete. Refer to Section 5.1, Step 11 when doing a complete O/S installation or refer to Section 5.2, Step 9 when doing an O/S upgrade. 3.2.3 525 MB 1/4" Cartridge Tape Drive The 525MB tape drive can replace the current 120 MB 1/4" tape drive in the main chassis. Only one internal 1/4" tape drive is allowed in a system. The drive appears the same to the system as the 120MB tape drive and uses the UNIX commands tar and cpio and the MAI utilities tsave and trestore. T 1000 ft. tape 600 ft. tape a Read Write Read Write p +----------+----------+---------+---------+ e 525 MB | Yes | Yes | Yes | Yes | |----------+----------+---------+---------| D 120 MB | No | No | Yes | Yes | r +----------+----------+---------+---------+ i 60 MB | No | No | Yes | Yes | v +----------+----------+---------+---------+ e 45 MB | No | No | No | No | +----------+----------+---------+---------+ NOTE: The 525 MB 1/4" cartridge tape drive can READ 600 ft. tapes written on the 60 MB tape drive but a 60 MB tape drive cannot read a 525 MB tape. The device file used to access the 525 MB cartridge is SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg008 /dev/tape or /dev/tp either one will work. There is the /dev/tpnr which will save files to tape and position after the data written on the tape (no rewind). The SCSI ID for the internal cartridge is 6. 3.2.4 8mm HIGH CAPACITY CARTRIDGE SCSI TAPE DRIVE The 8mm tape drive will provide up to 2.3GB storage capacity for backup purposes. One external 8mm tape drive, P/N 400828-011, will be supported with the GPx 440 and 640 which requires the expansion chassis with the Differential SCSI controller. Information can be copied to this drive by using the UNIX commands tar and cpio. NOTE: The defined major:minor number for the device files of the 8mm tape drive are incorrect. The correct numbers are: /dev/8t 11, 144 /dev/8tnr 11, 145 To change the major:minor do the following steps as 'super user': rm /dev/8t* mknod /dev/8t c 11 144 mknod /dev/8tnr c 11 145 mknod /dev/8t0 c 11 144 mknod /dev/8tnr0 c 11 145 chmod +w /dev/8t* 3.2.5 GCR 1/2" SCSI INTERFACE TAPE DRIVE The primary purpose of this drive is to provide high speed backup plus data interchangeability with other systems. The GCR drive supports 6250 BPI high density recording to provide up to 240 MB tape capacity when 3600 ft. tapes are used. The GCR can also be set from the front panel for 1600 BPI format tapes. The existing MBF GCR 1/2" tape drive (Model 4405) can be field upgraded with the Differential SCSI adapter, P/N 400652-007. One external GCR drive is supported on the GPx 440 and 640 with the Expansion Chassis and SCSI converter. The drive can be accessed with the UNIX command tar, cpio and Business BASIC with READ RECORD and WRITE RECORD for data interchange. The device file for the GCR is /dev/gt0 which has a major:minor of 11, 176 and the no rewind device is /dev/gtnr0 with a major:minor 11,177. The SCSI ID for the GCR is 5. 3.2.5.1 ACCESSING THE GCR THROUGH BASIC If a GCR tape drive is added to a system and it will be OPENed from BASIC the '/etc/bfsdevs' file must be modified with 'vi' so that R0 will access the GCR and not attempt . to access an MTS which is not present. Change R0:/dev/htnr:: to R0:/dev/gtnr0:: After changing the /etc/bfsdevs file you will have to reboot the system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg009 3.2.6 MTS 1/2" TAPE DRIVE DEVICE FILES The device files for the MTS tape drive are /dev/ht or /dev/ht0 which are major:minor 11, 160 and the no rewind files /dev/htnr or /dev/htnr0 which are major:minor 11, 161. The SCSI ID for the MTS tape drive is 5. NOTE: You may have noticed that the SCSI ID for the MTS and GCR are the same, this is because they reside on different controllers. The MTS is attached to SCSI controller 0 and the GCR is attached to SCSI controller 1 through the differential SCSI converter. Since each SCSI controller can have up to 7 devices or IDs there can be 2 devices with the same ID and they are distinguished by the major:minor of their device file. 3.2.7 GPx 440/640 EXPANSION CHASSIS The Expansion Chassis will support additional internal and external SCSI devices. The expansion chassis will support up to 5 half-high devices; or 2 full-high and 1 half-high; or 1 full-high and 3 half-high devices. The maximum number of hard disk drives supported is 5. A total of 7 SCSI devices can be supported per SCSI controller. The Expansion Chassis will be placed vertically next to the GPx 4/640 system to form a twin tower configuration with a SCSI bus from a SECOND SCSI controller in the main chassis. The external SCSI devices supported are the HCC and GCR tape drives with Differential SCSI interfaces. Disk Drives Full-High Half-High 355 MB 115 MB 670 MB 200 MB 3.2.7.1 USING DISKADD FOR DISKS ON SCSI CONTROLLER 1 Disk drives added to the system configuration must be addressed in the software using the diskadd utility. If a drive resides in the expansion chassis it is numbered 0 thru 4 and is connected to SCSI controller 1. 'diskadd' defaults to SCSI controller 0, if adding a disk on SCSI controller 1, '1' plus the disk number must be entered. Example: '12' would be entered to add the third disk to the expansion chassis. 3.2.8 SCSI CONVERTER (RANCHO CARD) The SCSI converter, P/N 400814-001, will convert the Single Ended SCSI Adapter to the Differential SCSI Adapter for external SCSI devices such as GCR and HCC tape drives. The converter card is mounted in the expansion chassis. 4.0 DIAGNOSTICS 4.1 ERRORLOG WATCHER Errorlog Watcher is a program that runs as a background task and monitors the system for excessive disk, tape, printer, and asynchronous port errors. If Errorlog Watcher detects an excessive amount of errors, then a message is broadcast and mailed to specific users. The user then can take immediate action to remedy the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg010 situation. This product is designed to catch errors before they become major problems. 4.1.1 ERRORLOG WATCHER OPERATING INSTRUCTIONS Errorlog Watcher consists of three programs: we - Actual Errorlog Watcher program weconfig - Errorlog Watcher configuration program werep - Errorlog Watcher report program The Errorlog Watcher programs are on the diagnostic tape. To. install, follow "mbfinstall" instruction, installing the WTR package. WTR does require a key to work. To run any of the above programs, the user should be in the directory where Errorlog Watcher is installed. Presently, Errorlog Watcher is under /usr/mbf/diag/watch when installed by "mbfinstall". 4.1.2 CONFIGURING ERRORLOG WATCHER Associated with each item that Errorlog Watcher monitors is an LIMIT and a WARNING LIMIT. The LIMIT is the number of errors. required to flag that particular device in the Errorlog Watcher report program. The WARNING LIMIT is the number of errors required to make Errorlog Watcher broadcast and mail a warning message to the users. Each device has its own configurable LIMIT and WARNING LIMIT. To configure Errorlog Watcher, execute "weconfig" by typing: weconfig "weconfig" will create several configuration files, one for each type of device. These files are used to store the LIMIT and WARNING values of each device. All files created by any program in Errorlog Watcher will have the extension ".f" at the end. If the configuration files already exist, Errorlog Watcher will not create new files to replace old files. Thus, if a device is added or removed from a system, its configuration file needs to be manually removed by the user for the system to create a new configuration file for that device. Running weconfig will cause the following menu to be displayed: ERRORLOG WATCHER CONFIGURATION 1. Change sleep time 2. Change time period 3. Change user mail list 4. Modify limits 5. Exit(MB_IV) Enter option: _ Option #1 "Change sleep time" will change the time that Errorlog Watcher sleeps between checks. The value defaults to 30 minutes. After selecting this option, the prompt: Current sleep time is xx minutes. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg011 Enter new sleep time (1-255) (CR=xx): _ will appear. Pressing CR will leave the value the same. The user can also enter the number of minutes for Errorlog Watcher to sleep between checking the system. The range is 1-255 minutes. Option #2 "Change time period" will change the time that Errorlog Watcher looks back into the errorlog in hours. When Errorlog Watcher awakens, it will scan through the file /etc/error.log for the given time period. That time period is from the current time minus the "time period" hours. So if this value is 24, then Errorlog Watcher will always look at the previous 24 hours for errors. When this option is selected the prompt: Current start check time is xx hours. Enter new start check time (1-720) (CR=xx): _ will appear. Pressing CR will leave the value the same or the user can enter a new value. The default is 24 hours. The range is 1-720 hours. Option #3 "Change broadcast user list" is used to indicate which users will receive the warning message when sent by Errorlog Watcher. When this option is chosen, the prompt: Current user list is: xxxxx Enter new user list (CR=same as current): _ will appear. The values for these are limited to ten characters and can be any valid user login (i.e., root, sa, etc.). Presently, the program doesn't check for validity of the user list input. The default user list is "root". Option #4 "Modify limits" will allow the user to change the limits and warning limits for each device. Once this option is chosen, the following screen will be displayed: 1. Modify disk limits 2. Modify tape limits 3. Modify printer limits 4. Modify async. ports limits 5. Modify 8/16way limits 6. Exit/(MB_IV) Choosing one of these options allows the user to change the values for a given area. For example, when #2 is chosen, a screen will ask which type of tape drive the user wishes to change, 1/4", 1/2", or 8mm. Then all tape drives of that particular type will be displayed along with its limit and warning limit. At the prompt, a tape number can be entered and new limits and warning limits are entered. The changes are always done in pairs, limit and warning limit. If the user wants to keep the current value for any limit, then press when prompted for a new value. If the device is not connected or is incorrectly configured, the user will not be able to set up the LIMIT and WARNING for that device. To exit any screen, press MB-IV. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg012 The disk, printer, async. ports and 8/16-way limits screens work the same. 4.1.3 STARTING ERRORLOG WATCHER Errorlog Watcher is started simply by typing the command as follows: we& The command above will start Errorlog Watcher in background mode. Errorlog Watcher will run continuously until it is stopped by the "kill" command or when the user logs off. To keep Errorlog Watcher running even after the user has logged off, start Errorlog Watcher with the following command: nohup we& To start Errorlog Watcher when the system is booted, use 'vi'. to create the file /etc/rc2.d/S85errwatch'. The file should contain: # TO START ERRORLOG WATCHER AT BOOT echo "Starting Errorlog Watcher" /usr/mbf/diag/watch/we& When Errorlog Watcher is started, it will initialize all configuration files if this has not already been done by first running "weconfig". Then after the amount of time specified in the sleep time has passed, Errorlog Watcher will wake up to run its first active cycle and check for errors in /etc/error.log. 4.1.4 SEEING THE RESULTS FROM ERRORLOG WATCHER While Errorlog Watcher is running and it detects a warning limit has been exceeded, a message will be displayed and mailed to all users specified in the users list. The message will contain the time, the number of the error count and the device that needs attention. Errorlog Watcher activity can also be monitored by the "werep" program. This program displays the information gathered by Errorlog Watcher on its last run. The report will show the number of disk, tape, async. port and 8/16-way card errors. If any value exceeds the limit specified in the watcher configuration, then that value will have an asterisk ("*") next to it indicating that the device requires attention. The current time and the time when Errorlog Watcher was last active will be displayed in the upper left corner of the error report. To run the error report, type in the command as follows: werep Error report will only be available after Errorlog Watcher's first active cycle. If the user attempts to run "werep" before Errorlog Watcher becomes active, the error report will. not be available or will be empty. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg013 All errors are stored in the file "wderror.f". If this file already existed when the user start s"we", then Errorlog Watcher will erase this file and create a new one. Note that Errorlog Watcher only updates the error count of a device when the device reports an error. Therefore, if the device gets 5 errors during Errorlog Watcher's first active cycle and no error in the second active cycle, the error report will still show 5 errors exist. If the device has 5 errors in the first cycle and 2 in the second cycle, the error report will show 2 errors exist. When the faulty device has been fixed, and the user wants to clear the error report, the error file "wderror.f" should be cleared only by re-starting "we". 4.2 MEMORY PARITY ERROR HANDLING Memory parity errors cannot be located by system hardware, therefore, when a memory parity error does occur the O/S generates an NMI, Non- Maskable Interrupt. This interrupt momentarily suspends all processing to test system memory. The memory test may take 15 to 30 seconds to complete, depending on the amount of memory in the system. The memory is scanned in an attempt to regenerate the parity error and thereby determine the address of the error. Memory is scanned for multiple parity errors unlike previous levels which stopped after one parity error was found. The memory scan will have different results depending on the system type and the findings of the memory scan. o The GPx 2/3/4/640 will PANIC and display the parity error address when the scan regenerates the parity error. o The GPx 2/3/440 will NOT PANIC if the memory scan does not regenerate a parity error. The following message will display: NOTICE: Parity address unknown NOTICE: Confirmed i386 unresolved/NMI interrupt Normal processing is resumed. o The GPx 640 will PANIC if the memory scan does NOT regenerate a parity error, the following messages will be displayed on console: NOTICE: Parity address unknown NOTICE: Confirmed i486 unresolved/NMI interrupt PANIC: PANIC reaction to i486 PARITY/NMI interrupt Systems which continue to have unresolved parity errors should have diagnostics run for more rigorous testing. 4.3 NMI INTERRUPT MESSAGES If the system receives an NMI (Non-Maskable Interrupt), all processing will be stopped either temporarily or permanently with a PANIC. If a PANIC occurs, a message will appear explaining the source of the NMI. 1.1A has many new messages which will aid in the determination of the system problem. If the O/S cannot determine the cause of the NMI, the following message will appear: NOTICE: Confirmed unresolved/NMI interrupt SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg014 The system will NOT PANIC, but the condition is serious enough that it will display on the console terminal even if Verbose Kernel Messages is set to 'off'. If the above message continues to occur a complete hardware diagnostic session should be run on the system. 5.0 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM AND DIAGNOSTICS The following are steps to install or upgrade the BOSS/VX Operating System. Before installing or upgrading the system it is recommended that you read these instructions completely. 5.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all files that exist on your system. It first creates partitions on the fixed disk, makes the file system according to default or user input specifications, and then installs the standard BOSS/VX software (BOSS/VX, Business BASIC, and system utilities) on your system. WARNING: Installation of the Operating System will destroy any installed software on the system. If you are doing an OS installation on a system that already contains customer data, ensure you have a verified backup of the data. This backup should not contain any OS files. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record NOTE: During Step 4 you will be required to answer questions pertaining to the system disk partitioning. This information should be decided before the start of the installation, as changing these values will require a re-install of the OS. For information on partitioning see Section 5.1.1. NOTE: Step 1 is for the GPx 2/3/440s, Step 1A is for the GPx 640 and/or systems with the Multi Function Card (MFC). STEP 1: If the system is powered down, power up the system. During the system self-test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 1A: If the system is powered down, power up the system. The system must be powered-up to give the option to boot from tape. After the system self-test the MFC BIOS will takeover and display the MFC Menu seen below: (continued no next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg015 _______________________________________________________ | | | 1) Boot Menu | | | | 2) Setup Menu | | | | 3) Diagnostics Menu | | | | Hit to boot from hard disk (default) | |_____________________________________________________| Put the BASE Operating System tape into the tape drive and Enter 1 to go to the Boot Menu, seen below: _____________________________________________________ | | | H - Boot from hard disk (default) | | | | T - Boot from tape | | | | F - Boot from floppy | | | | Hit to Boot from hard disk (default) | |_____________________________________________________| Enter T and the system will boot from tape. NOTE: Upper or lowercase is accepted when entering the boot selection. If no enter is made on the MFC Menu or the Boot Menu they will timeout and boot from the hard disk or default STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MAI terminal answer 'y' followed by a , if not answer 'n', . The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. STEP 3: Enter option 'f' to do a full installation. A warning message telling you that a full installation will destroy all files on the system will be displayed. You will then be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', to exit the installation procedure. STEP 4: System disk information will now be displayed, including the default system disk partitioning, followed by the prompt: Is this allocation acceptable to you (y/n)? If you answer 'y',, to this prompt, the default partition will be used to partition your system disk. If you answer 'n' to this prompt, you will next be prompted with: Do you wish to have separate root and usr filesystems (y/n)? SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg016 If you answer 'y', to this question your system will contain a root partition and a separate usr partition. Answering 'n',, will put both the root and usr in the same partition. You will next be prompted with the question: Do you want an additional /usr2 filesystem (y/n)? If you answer 'y', to this question a separate usr2 partition will be created on your system disk during the installation. With an 'n',, answer to this question the usr2 partition will not be created. Next, a message will be displayed showing approximately how many bytes a cylinder contains on your disk. You will then be asked: How many cylinders would you like for swap/paging? The minimum size this partition can be is 16MB. Enter the number of cylinders you wish the swap/paging partition to be, followed by a . You will next be prompted for the size you wish for the rest of the partitions to be created. After you give the size for each partition, you will be again asked if the allocation is acceptable. An answer of 'n',, will take you back to the beginning of this step. STEP 5: After you have answered 'y' to the allocation question, messages will be displayed indicating that the file systems are being made. After the file systems are made, the BOSS/VX software will be installed with the name of the files displayed as they are copied to disk. STEP 6: After the BASE system is installed, the Date and Time are displayed. You will be prompted with: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y',, and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. STEP 7: You will next be asked if the Date and Time are correct. If they are correct, answer 'y',; otherwise, answer 'n',, and you will be prompted with the questions to set the Date and Time correctly. STEP 8: You will next be asked to enter the password for the root or super-user. You will be asked for this password twice. Be sure that you remember this password, as it will be required SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg017 when you wish to login as root. STEP 9: The next step is to install the System's Configuration Record. You will be prompted with: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you wish to install this configuration record? Enter 'y',, to install the configuration record. If you enter 'n',, the configuration record will not be installed and you will be returned to the BOSS/VX SOFTWARE INSTALLATION menu. NOTE: You must install a configuration for your system to boot. If you entered 'n',, in the above step, see Section 1.3 "Installation/Upgrade of the Security Configuration Record" to install the configuration record. STEP 10: After the configuration record is installed the installation of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r',, to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 5.4, "Installation and Update of Optional Software Packages" NOTE: Step 11 is for systems 240/340/440's with a VGA monitor. It is necessary to have a terminal on COM1 because utilities such as 'configure' and 'oprinfo' are not legible on the VGA. STEP 11: After the system has rebooted, logon to the terminal connected to COM1 (SERIAL2, the 9 pin port) by entering: install You will be asked to enter a password, enter: chngt0 Then enter it again. Use this password on all 240/340/440's with VGA monitors. Enter: su Enter: init S The system will go into single-user mode and the terminal will now be the system console. We made a terminal the system console because MAI utilities do not display correctly on monitors. At this point you will be able to run configure and oprinfo. After configuring all the ports SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg018 and creating operators, shutdown down the system and reboot. Enter: init 0 The system will do a complete shutdown and will come up with all the ports configured and the VGA monitor will again be the system console. 5.1.1 SYSTEM DISK PARTITIONING The BOSS/VX installation procedure will allow you to define one, two or three partitions containing a file system on the system disk. The swap/paging partition will automatically be on the system disk, but doesn't contain a file system. You will be required in Step 4 of the BOSS/VX installation . procedure to provide information on the number and size of the partitions you wish defined. Before starting an installation, you should have this information. To change this after an OS installation will require backing up the customer's data and doing a complete reinstallation of the OS. The following are different partition options that are available during the installation: 1 partition: root and usr together on the same partition, no usr2 partition. (not recommended) 2 partitions: separate root and usr partition, no usr2 partition. 2 partitions: root/usr partition together and a separate usr2 partition. 3 partitions: separate root, usr and usr2 partitions. During the installation procedure, commands and files required when the system is in single user mode will be installed to the root partition. While in single user mode, the root is the only partition automatically mounted. These commands will allow you to repair or work with one of the other partitions if they are damaged. During the installation procedure, the rest of the standard BOSS/VX software will be installed on the usr partition, if you specified you wanted a separate root and usr partition. Otherwise, the rest of the standard BOSS/VX software will be installed in a directory called '/usr', on the root partition The OS doesn't put any commands, programs or files automatically into the usr2 partition if it is defined. At the minimum it is recommended that you define your system disk with a separate root and usr partition. In this case if a problem occurs on the usr partition, (the partition where the customer's data is located), the system can be booted into single user mode and the usr partition can be worked with from the root partition. If you wish to put the customer's programs and data files on a separate partition or wish to have a separate partition that SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg019 can be easily unmounted for security reasons, then the usr2 partition should be defined. Following is the approximate amount of disk space in Mega Bytes by package for the root and usr partitions: Package Disk Usage BASE* 25.6MB UTERM 1.8MB MANPAGES** 3.1MB ITP .9MB PS 2.9MB For ADS, DSS and OTU see Section 5.5.2.1 * BASE = BASE and UNIX (UNIX is under /usr only) ** MANPAGES = MBFMAN and UMAN NOTE: The amount of disk space required for the above may grow in future releases. 5.2 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the original ones. WARNING: Before attempting any update, it is recommended that you have a verified backup of the customer's data. Ensure that this backup doesn't contain any of the OS files. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record (if you wish to re-install the configuration record) NOTE: Step 1 is for the GPx 2/3/440s, Step 1A is for the GPx 640 and/or systems with the Multi Function Card (MFC). STEP 1: If the system is powered down, power up the system. During the system self-test, put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure that it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. The loading message and proprietary message will be displayed. STEP 1A: If the system is powered down, power up the system. The system must be powered-up to give the option to boot from tape. After the system self-test the MFC BIOS will takeover and display the MFC Menu as shown below: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg020 _________________________________________________________ | | | 1) Boot Menu | | | | 2) Setup Menu | | | | 3) Diagnostics Menu | | | | Hit to Boot from hard disk (default) | |_______________________________________________________| Put the BASE Operating System tape into the tape drive and Enter 1 to go to the Boot Menu, as shown below: _________________________________________________________ | | | H - Boot from hard disk (default) | | | | T - Boot from tape | | | | F - Boot from floppy | | | | Hit to Boot from hard disk (default) | |_______________________________________________________| Enter T and the system will boot from tape. NOTE: Upper or lowercase is accepted when entering the boot selection. If no enter is made on the MFC Menu or the Boot Menu they will timeout and boot from the hard disk or default. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y' followed by a . If not, answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. STEP 3: Enter option 'u', to do an update installation. Messages telling you that the file systems are being checked will be displayed. The file systems must not contain errors for the update to continue. Next, messages telling you the BASE system package is being searched for, followed by a message telling you the BOSS/VX software will be installed, are displayed. This is followed by the OS files being installed, with the names of files displayed as they are installed. STEP 4: After the OS files have been installed you will be given the option to install the OS files that the user can modify. STEP 5: Next, the Date and Time are displayed. You will be prompted with: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to the change time zone answer 'y',, and a list of available time zones will be displayed. Enter the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg021 number of the time zone you wish to use. If the time zone displayed is correct, answer 'n',. If you change the time zone, you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. STEP 6: You will next be prompted with: Install the configuration record (y/n)? If you don't want to install the configuration enter 'n',. The update is now complete. Remove the BASE system tape and enter 'r', to reboot the system. STEP 7: If you wish to install the configuration record, enter 'y', and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. Do you want to install this configuration record? STEP 8: After the configuration record is installed, the update of the BASE system is complete. You will be prompted with: Press to main menu, or "r" to reboot the system: Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 5.4, "Installation and Update of Optional Software Packages". NOTE: Step 9 is for systems 240/340/440's with a VGA monitor. It is necessary to have a terminal on COM1 because utilities such as 'configure' and 'oprinfo' are not legible on the VGA. STEP 9: After the system has rebooted, logon to the terminal connected to COM1 (SERIAL2, the 9 pin port) by entering: install You will be asked to enter a password, enter: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg022 chngt0 Then enter it again. Use this password on all 240/340/440's with VGA monitors. Enter: su Enter: init S The system will go into single-user mode and the terminal will now be the system console. We made a terminal the system console because MBF utilities do not display correctly on monitors. At this point you will be able to run configure and oprinfo. After configuring all the ports and creating operators, shutdown down the system and reboot. Enter: init 0 The system will do a complete shutdown and will come up with all the ports configured and the VGA monitor will again be the system console. 5.3 INSTALLATION/UPDATE OF THE CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration record on a system that doesn't already have one or overwrites the one already on the system. It will display the configuration record. before installing it and give the option to install it or go back to the menu. The following will be required to install the Configuration Record: o BASE Operating System tape o Configuration Record tape STEP 1: If the system is powered down, power up the system. During the system self-test put the tape containing the BASE system in the tape drive. If the system is already powered up, ensure it is shutdown properly before rebooting with the BASE tape in the tape drive. The loading message and proprietary message will be displayed. STEP 2: You will then be prompted with the message: Is this an MBF terminal (y/n)? If the terminal you are using is a supported MBF terminal answer 'y', followed by a . If not, answer 'n',. The BOSS/VX SOFTWARE INSTALLATION menu will now be displayed. STEP 3: Enter option 'i', to install the configuration record. The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg023 drive and put the tape containing the configuration record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record? If you enter 'y',, the configuration record will be installed. If you answer 'n',, the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE INSTALLATION menu. STEP 4: After the configuration record is installed you will be prompted with: Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r',, to reboot the system. The installation of the configuration record is now complete. If a monitor is being installed on the system refer to Section 5.1, Step 11 for O/S installations and Section 5.2, Step 9 for O/S updates. 5.4 INSTALLATION/UPDATE OF OPTIONAL SOFTWARE PACKAGES AND DIAGNOSTICS The following steps outline the procedure to install optional BOSS/VX packages, for example; BASS, DEMON, WatchError ITP, MAI OFFICE, TBC, Presentation Services, tools, ORIGIN and other packages supplied in a BOSS/VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified backup of the customer's data files before attempting the update. The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. STEP 1: If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. STEP 2: Shut the system down to single user mode by using the command 'shutdown -i1'. Do you want to continue (y/n)? enter 'y' When prompted for the password use your root password. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg024 Enter terminal type (default is TERM=dt4313) TERM= or terminal type. STEP 3: At the command mode prompt enter the command 'mbfinstall' . The following messages will be displayed: WARNING: This program should only be executed in single-user mode press to continue. Installing products on / Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. If it is not mounted, type 'mountall' to mount it. STEP 4: Insert the tape containing the package(s) you wish to install in the tape drive and enter . The BASE system tape will display a message that the tape is an operating system tape. The Diagnostic tape message will display that it is a Diagnostic tape. Either are followed by a prompt to continue. Enter . Messages will be displayed telling you the procedure is skipping the product(s) not to be installed. Next, the MAI Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. STEP 5: Enter the number of the package you wish to install followed by a . You can enter them in any order. The procedure will put them in the order they are found on the tape. After you enter a number you will be prompted with: Install product(s) number Are you sure (y/n)? If you answer 'y',, to this question, the number will be added to the list and you will be returned to the menu. If you answer 'n',, the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, . If you wish to abort the procedure and go back to command mode enter 'ab', . SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg025 STEP 6: After you have entered the number of all the products you want to install, enter 's',. The procedure will display the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. STEP 7: If a public id is required a message displaying the current public id and its length will be displayed after the package is installed, followed by: ENTER an 8-character new Public ID (Hit <0> for a Null Public ID or for no change): Enter the public id you received with the package if it is different than the one displayed. STEP 8: If you are installing more than one package, the next package will be installed. This will continue until all the packages you selected have been installed. After all the packages are installed, the procedure will take you back to command mode. You are now done with the installation of your package(s). . If you wish to install additional package(s) from other tape(s) repeat this procedure to install them. STEP 9: Enter ^d and 2 to return to multi-user mode or ^d and 0 to shut the system down. NOTE: After installing TBC the system must be shutdown using ^d and 0' and then powered off and on so the system will recognize the ICC186 board. 5.5 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES The following sections include special instructions or installation procedures when installing the optional software packages. 5.5.1 MAI PRESENTATION SERVICESTM There are no special instructions for installation and customization of Presentation Services. Ensure the user's Path includes the following to access Presentation Services: /usr/mbf/PS /usr/mbf/PS/tools 5.5.1.1 PRESENTATION SERVICES CUSTOM MENUS If the user has created their own menus through PS MENUBUILDER for either their own applications or OFFICE and ORIGIN, they need to transfer those files to the GPx Series 40 system using Intersystem Transport. The files to be transferred are as follows: SPx names would be: ../PS/MSMF and ../PS/MSSF-->MENU FILES ../PS/MSH1 and ../PS/MSH2-->HELP FILES MPx names would be: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg026 .PS.MSMF and .PS.MSSF .PS.MSH1 and .PS.MSH2 5.5.1.2 PRESENTATION SERVICES FORMS When transferring forms to the GPx system, port only the source form files. Do not port the compiled form file. You will need to recompile your forms once you get them on the destination system. If the user has created their own forms through PS FORMSBUILDER, they need to transfer the following using Intersystem Transport. SPx: /PS/FS1.ENG /PS/FS2.ENG /PS/FS3.ENG /PS/FS4.ENG MPx: .PS.FS1.ENG .PS.FS2.ENG .PS.FS3.ENG .PS.FS4.ENG All programs created and associated files must also be transferred. Programs will need to be modified to use only BB90 directives. Bring the files over using cread but do not perform the conversion during porting. Then run BQR to convert the files. After this is done, run MKCONVERT. 5.5.2 MAI ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities *********************************************************************** * WARNING * * *. * o PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING * * THIS PRODUCT. * * *. * o Your system should be in single user mode. This ensures a safe * * product installation without conflicts with active system users.* * *. * o You must be logged on as 'root'. This will avoid security * * conflicts during the product installation. * * *. * o Make a full backup of your product (programs & files) * * before installing this new version. * * *. * o The following Path names used are examples only and will change * * if you install the packages into a directory other than '/usr'. * *********************************************************************** NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg027 5.5.2.1 INSTALLATION REQUIREMENTS: New installations: o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.0A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: ADS or DSS or (ADS + DSS): 8.17 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB Updating: o The same requirements for a new installation, plus the following: o You must port all of your current ORIGIN data files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). WARNING: The only way to keep separate directories is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 5.5.1 Presentation Services. ******************************************************************* * *. * Make a full backup of all ORIGIN program and data files, * * currently located at '/usr/origin/r21b and the directories in * * which your *DC0 files are located BEFORE installing this * * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix or directory. * * *. ******************************************************************* NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 5.5.3.1 for MPx and Section 5.5.3.2 for SPx. 5.5.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.4. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg028 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.4. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, MB-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appears) SECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY > SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg029 You may now go to step 6 or quit and shutdown before rebooting system. 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.5.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B, the program UPDATE does NOT have to be executed. 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 5.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.4. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), for (a default will appear). For example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 5.5.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. NOTE: Use the 'chmod' command to change the file usage rights on all files ported to the GPx from another system. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg030 To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.5.2.4 UPDATING FROM 2.0A 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 5.4. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.4. 4. Go into BASIC and start with 256 pages of memory. basic s=256 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on the root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT: This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg031 E. INSTALL STAND ALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.5.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B. tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 5.5.2.4, "Installations Updating from 2.0A". 5.5.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg032 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic >start 256 >PREFIX "/usr/origin /usr/origin/r21b /usr/mbf/PS /usr/mbf/PS/tools" >RUN "ORIGIN" NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. 3. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. _____ Select User Maintenance, use the password "ADMIN". 4. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities. The password is ADMIN. _____ Select ORIGIN System Parameters Maintenance option. _____ Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this directory is "/usr/origin/work/". 5.5.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 5.5.3.1 MPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 5.5.2.5. 2. Perform a verified backup of the ORIGIN system. 3. Using the DIRectory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg033 For example: .USR.ORIGIN.JKSF01 -> data file .USR.ORIGIN.JKSF02 -> data file .USR.ORIGIN.JKSFM2 -> Application Generated Program .USR.ORIGIN.JKSFM1 -> Application Generated Program .USR.ORIGIN.JKSR01 -> Report Generated Program .USR.ORIGIN.JKSR02 -> Report Generated Program .USR.ORIGIN.xxxDC0 -> Technical Documentation File .ORIGIN.R20A.DATA.IDD000 -> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with IDDxxx and reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From command mode, execute MCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 5.5.3.2 SPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 5.5.2.5. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 -> data file /usr/origin/JKSF02 -> data file /usr/origin/JKSFM2 -> Application Generated Program /usr/origin/JKSFM1 -> Application Generated Program /usr/origin/JKSR01 -> Report Generated Program /usr/origin/JKSR02 -> Report Generated Program /usr/origin/xxxDC0 -> Technical Documentation File /origin/r20a/data/IDD000 -> Integrated Data Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg034 into a single destination, separate tapes must be used for each destination. 4. Using cwrite utility, write BQR filelist to tape. 5. Restore Intersystem tape on GPx machine using cread utility. Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 5.5.4 ORIGIN 2.1B NEW FEATURES o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re-generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity between the 'regenerated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 5.5.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) -and- /pgm/SPA004 - ORIGIN message file in foreign language (*) /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language * SPA will be used as the language code in this document. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg035 o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. Message Translation o Set your prefix to work with ORIGIN 2.1B and perform the following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilities -> -> Password (ADMIN) -> Language Translation Menu -> Languages -> Maintain Languages -> Enter the language code -> -> Done, you may go to console mode at this point. o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file, to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) o Using with system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program directory (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily modified from 2.1A to 2.1B, so a re-translation of this program is recommended: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg036 . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until translation is complete. 5.5.6 DOCUMENTATION Manual Number Part Number Pages Title ------------- ----------- ----- ---------------------- M7511E 007511-012A 170 MAI Business DATATM Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATATM Technical Reference M0058C 910058-002 132 MAI ORIGINTM User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGINTM Application Generator User Guide M7512D 007512-002 112 MAI ORIGINTM Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATATM System Support Manual M7557G 007557-011 74 MAI Business DATATM User Guide M7561E 007561-002A 166 Presentation ServicesTM Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services Forms Management User Guide 5.6 INSTALLATION OF TCP/IP FOR NETWORK SUPPORT Ensure that the system is connected to the network and that the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg037 Ethernet Controller is installed. While in single-user mode follow the the mbfinstall instructions in section 5.4 to install TCP/IP. A public key is necessary to run TCP/IP. After the TCP/IP product is installed and still in single-user mode the system name must be changed with the 'uname' command, enter the following: uname -S mai The system will name will now be 'mai'. If multiple systems are going to be connected to the same network or a terminal server they must have different system names. The network address must be added to the /etc/hosts file. The line added should have the address and the system name as follows: 50.0.0.1 mai 50.0.0.1 is an example address. Reboot the system and the installation is complete. 6.0 COMMUNICATION PACKAGES 6.1 27xx/37xx BATCH EMULATION 6.1.1 SOFTWARE REQUIREMENTS AND INSTALLATION Package Installation: The package requires a minimum of 2296 disk blocks on the /usr partition for the programs. The files will reside in the /usr/mbf/comm, /usr/mbf/magnet, /usr/mbf/tbc and /usr/mbf/etc directories. There are approximately 176 disk blocks required for each data directory defined by the user. You may configure up to 4 ports on the GPx 40 for TBC, but only two communication sessions may run at the same time. If two sessions are run simultaneously, they can be run at 9600 bps. If more than two sessions are attempted at the same time an error -615 will occur. TBC requires a security key to operate. 1. Installation of this package is done using the 'mbfinstall' utility. 2. The name used to select the installation of this package is 'TBC'. 3. A prompt to enter the software key will be given after the files have been restored. If the key is not entered at that time, the command: 'install_key TBC' can be used to install the key. The key must be entered in upper case. Port Configuration: The 'configure' utility has been modified to include communication devices. Option '9' is used to configure communication devices. There are 4 ports SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg038 available per controller (0-3). When you add a device, select 'tbc' as the protocol and any I-device group from IA to IZ. NOTE: You must be in Single User mode to install this package and configure the communication devices. After the install you must enter CTRL D and 0 to shutdown the system. Power the system down and re-boot. 6.1.2 HARDWARE REQUIREMENTS AND INSTALLATION Although it is not required, it may be necessary to increase system memory to keep system performance at an acceptable level. The determination of this should be based on individual system load parameters. ICC186 Part number: The part number for the controller is 916593-001. NOTE: There are 4 ports on one controller which are paired and driven by 2 sync chip drivers. This can be useful for troubleshooting purposes. Cable Part number: The part number for the controller multi-modem cable is 400694-003, the extender cable part number is 907753 with a dash number to indicate length. A connector gender adapter part number 300118-001 is required if the extender cable is used. NOTE: The one multi-modem cable has connections for up to 4 synchronous modems. Board installation: The Board may be installed in any 16 bit slot available on the GPx CMB. (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg039 Switch settings: The following table contains the required controller switch settings: _________________________________________________________ | JUMPER SETTING | DESCRIPTION | |-----------------------------|---------------------------| | JB1 | Interrupt Request Line 10 | | O O O O O |X| O O | | | 1 O O O O |X| O O | | |-----------------------------|---------------------------| | JB2 | Ports 0-3 connected as DTE| | O O |X| |X| | (For normal operation and | | 1 O |X| |X| | all tests except the Loop| |-----------------------------| test. For the Loop test, | | JB3 | all jumpers MUST be | | |X| O O |X| | removed. All DEMON test | | |1| O O |X| | may run with these | | | jumpers removed. | |-----------------------------|---------------------------| | JB4 | Shared memory starts at | | |X| O |X| O |X| |X| | A0000h | | |X| |X| |X| |X| |X| |X| | | | O |X| O |X| O 1 | | |-----------------------------|---------------------------| | JB6 JB7 | Shared Memory size 64KB | | O |X| | | | O |X| | | |_____________________________|___________________________| | SW1 | | | | I/O Address of 240H| | 1 2 3 4 5 6 7 8 9 10 | | | OFF ON ON OFF ON ON ON ON OFF OFF | | |____________________________________|____________________| |X| = Jumper installed O = Jumper not installed 6.1.3 GENERAL INFORMATION - Operation 1. The 27xx/37xx Batch Emulation package may be accessed through the Utility menu and selecting the 'communications' option or by setting the user prefix list to '/usr/mbf/tbc' and then running "BCOM" from BASIC. No start size is required. The program "SBCOM" is also supported. 2. The TBC session menu on the GPx family of products has been changed so that option 1 is now called "TRANSMISSION DEFINITION" and not "TERMINAL DEFINITION" as on previous products. 3. The 'CONTROLLER/PORT' option under 'TRANSMISSION DEFINITION' selection expects numerics from 0 to 3. 4. There are two new entries to the file '/etc/rc2.d/S20sysetup' that performs the necessary operations to load the TBC controller and start the process '/* MAGNET RSM */' for use with TBC. The file is installed with these entries with the installation of the TBC package and is executed during boot. The two new SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg040 entries are "/usr/mbf/magnet/netinit" (starts the MAGNET RSM process) and "/usr/mbf/comm/commload -b0" (loads the TBC board 0 ). If you are not using TBC, you may want to remove these entries from the '/etc/rc2.d/S20sysetup' file so that errors due to missing hardware and non configured devices will not be displayed during boot. 5. At system load time, a message 'resetting ISCC board number 0' will be displayed. 'ICC 186 sync. comm. board - rom version 20' will be displayed during the system hardware self tests at load time. 6. A complete system shutdown (power off) and startup should be done after the software and hardware have been installed and configured for the first time. You may see errors during the load process indicating 'error' resetting controller '0' if this is not done. 7. Run "BCOMPFX" the first time communications is installed on the system. 8. The software supports a serial interface autodialer and will require a dedicated terminal port per autodialer. The Ark 2400 Plus Modem (Paradyne) and UDS 801 A/C Direct Connect Automatic Calling Unit with RS-232 input are both supported. The ARK DM424 modems only contain a synchronous port and will require a dedicated external autodialer to work with TBC. The terminal port should be configured as: Device type: terminal Terminal type: other There should be no start process and the baud rate, parity and character length should match that of the setting for the modem. The default settings are used for the remaining fields. A serial modem cable is required (P/N 916073) for the ACU. - Diagnostics 1. A synchronous modem eliminator may be used to test the software and controller since there are 4 ports available 2. DEMON has been updated to include tests for the ICC186 controller. 3. A loopback connector number 905718-001 is available for DEMON loopback testing. 7.0 NOTES AND CAUTIONS CAUTION: Saving '/dev' files to tape may casue a system PANIC. Only save user applications programs, data files, the /usr/mbf/etc and /etc directories when doing a full system backup. CAUTION: bbmap can not be run on multiple terminals. If multiple copies are run the system may PANIC. CAUTION: DT-4309 and older terminals do not work on the console port (COM1) with the standard cable P/N 916484-xxx. NOTE: The error messages "NVRAM error" and "Keyboard error" are SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg041 displayed because the system has a SCSI controller which can only access up to 16 MB of main memory. These errors have no affect on the system. CAUTION: The address of the SCSI controller must be changed on the 1542A and 1542B when a system is upgraded from a 2/3/440 to a GPx 640. The changes are as follows: 1542A (long controller): GPx 2/3/440 Jumper J10 has no jumpers. GPx 640 has both jumpers installed on J10. 1542B (short controller): GPx 2/3/440 Jumper J7, pairs 7 & 8 have no jumpers. GPx 640 Jumper J7, pairs 7 & 8 have jumpers installed. This changes the address of the SCSI controller from DC000 to C8000 because the address of the MFC (D8000-DFFFF) overlaps the old SCSI controller address. CAUTION: To boot the GPx 640 from tape the system must be correctly shutdown, powered-off and rebooted. A tape boot cannot be performed by doing a shutdown and rebooting only. NOTE: When using cpio to backup files to the HCC tape drive, it is recommended to use the 'B' option to write to tape with a block size of 5120. When using a non-default blocksize, the blocksize should be written on the tape. Example: cpio -ocvmudB > /dev/8t CAUTION: The major:minor number for the device files of the 8mm tape drive are incorrect. The correct numbers are: /dev/8t 11, 144 /dev/8tnr 11, 145 To change the major:minor do the following steps as 'super user': rm /dev/8t* mknod /dev/8t c 11 144 mknod /dev/8tnr c 11 145 mknod /dev/8t0 c 11 144 mknod /dev/8tnr0 c 11 145 chmod +w /dev/8t* WARNING: Do not configure more than 2 terminal ports at 19.2 baud with XON/XOFF flow control, data will be lost at that speed. CAUTION: After upgrading to 1.1A, the following message may appear on the BOSS/VX screen twice: --- Press 'CTRL' + 'C' or 'ESCAPE' --- if so, 'vi' /etc/exem and remove the above line so the message will only display once. CAUTION: The floppy diskette device /dev/dsk/f015d cannot be used to make a floppy based filesystem. The mkfs command will not return an error but mount will fail. CAUTION: Password aging using MINWEEK and MAXWEEK does not work. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg042 Workaround: Use the 'passwd' command to turn off password aging. Only 'super user' can change password aging. Enter: passwd -x -1 user (-1 as in the number one) The '-1' parameter turns off password aging immediately. WARNING: When upgrading from 1.0A or 1.0B to 1.0C, 1.0D or 1.1A you MUST delete /usr/mbf/etc/_queues/lpq.que, the printer queue file. The format has changed from previous levels. WARNING: 'pformchg' does not print a live data form alignment test if the report uses @ for positioning. If @s are not used a live data form alignment will print. The static data alignment works with or without @s. WARNING: The 1/2" MTS and HCC tape drives do NOT detect the End-of-Tape mark when writing to the tape with BASIC, tar or cpio. *This has been fixed in 1.0D. WARNING: If /etc/bfsdevs is installed during an O/S upgrade the port configuration will be corrupted. To fix the corruption go into the 'configure' utility and perform a Save and Exit. WARNING: After upgrading to 1.0C and 1.0D the internal MODEM port settings may change, so check the port configuration for the internal MODEM in configure. WARNING: 'pqueue' will display a status of 'unknown' instead of 'formchange' when waiting for a form change. *This has been fixed in 1.1A. WARNING: After upgrading to 1.0C you may need to do a chmod 777 /tmp because non-root operators will not be able to logon. WARNING: DO NOT configure ports for 38.4K baud rate. This can cause the system to hang. WARNING: The PT-4220 serial printer defaults are set incorrectly in the configure utility. The defaults should be: Baud: 9600 Data Bits: 7 Stop Bits: 1 Parity: Odd The PT-4220 serial printer should also have 'despool wait' set to 'yes'. WARNING: The mnemonics for START BOLD and END BOLD are not supported on the PT-4220 serial printer. PROBLEM: Error 31's in CALLed programs. If a CALLed program has an ENTER A$ and within the program A$ is reassigned A$=A$+B$ then an error 31 is possible. WORKAROUND: After the ENTER A$, set A$ equal to another variable and use that variable throughout the CALLed program, e.g., B$. Then before EXITing set A$=B$. WARNING: It is possible to have 2 printers named LP. If a serial printer is named LP and a parallel printer is added it can ONLY be LP. The result will be 2 printers being named LP. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg043 *This has been fixed in 1.1A. WARNING: When installing WordPerfect, a prompt askes for 'Y/N'. The only input accepted is 'y' (lower case). NOTE: DEMON cannot recover from a media error on the 8mm tape drive. NOTE: All files being transported to a 1.0C and above O/S levels, with cread, will have their permissions set to rw-rw-rw-, regardless of the permissions that existed on the previous system. NOTE: DT-4314 terminals configured as a DT-4313 will NOT take advantage of software capabilities designed for the DT-4314, such as boxes. NOTE: The UNX Product on the Operating System tape is included in the Base portion of the O/S on levels 1.0C and higher and will not have to be installed with 'mbfinstall' to run UNIX packages. NOTE: To convert the number of blocks into number of MB do the following equation: (# blocks * 512)/1,048,576. Example: 8670 blocks * 512 / 1,048,576 = 4.23 MB 7.1 ATP NOTES AND CAUTIONS: A. A BASIC program being transferred with ATP from a GPx to a 1500 system will error on multi-line statements in BASIC. Workaround: Edit the BASIC program on the 1500 after the transfer. B. When using ATP over a modem between an SPx and a GPx, the SPx side must start communications first. C. A STRING file with certain unprintable characters, between $00$ and $1F$, could become corrupt when transferred with ATP from a BOSS/VX system to a BOSS/IX system. Change the following programs on the BOSS/IX system: /util/ARP 4205 IF F4<>7 THEN GOTO 4210 ELSE LET R9=0; IF S1=1 THEN WRITERECORD(6,TBL=6900,ERR=4500)R0$(3,S9-2) ELSE WRITERECORD(6,ERR=4500)R0$(3,S9-2) /util/ATP1 5135 IF F4=7 THEN LET R9=0; READRECORD(6,ERR=6000,END=5700)X9$;. GOTO 5150 D. ATP cannot be started on 2 terminals at 1 time. E. Using ATP to transfer a string file to a system that does not support string files will cause the BOSS/VX system to skip the string file and the destination system to report "Invalid receive file type". F. STRING files will be changed to SERIAL files on a BOSS/VS system with M.6G Operating system or higher. G. Using ATP to attempt to transfer Multi-keyed files to a SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg044 system that does not support MK files will cause the MK file and the following file to be skipped. H. Because SERIAL files are not supported on the MAI-1500, they will be skipped when attempting to use ATP to transfer them to the MAI-1500. I. Avoid giving BQR filelists similar names. If the first 3 characters are similar BQR may become confused and delete some of the BQR filelist names. 7.2 PC-LINK NOTES AND CAUTIONS A. PC-Link does NOT support slave printing on the GPx 40, because PC-Link requires an MBF interface. Slave printing will be available on a future release of PC-Link. B. Use BOSS/IX as the system type when running PC-Link on a BOSS/VX system. C. The PC-Link file transfer programs on the GPx 40 must be in UPPERCASE. D. To use "vi" via PC-Link requires that the terminal configuration be at least a DT-4309. The operator can set the terminal by using the following steps: TERM=4309 export TERM E. CTRL+S will hang the PC port when running PC-Link over a modem. To resume operation, hang-up the modem and redial. F. Pressing at the "$" prompt will hang the PC for 30 seconds. 7.3 TBC NOTES AND CAUTIONS: A. TBC should not be run with less than 8MB of memory. When running with 4MB of memory a BASIC qcode error is reported. B. Do NOT create a /debug directory. If TBC sees that directory it will create files which may fill the /root partition. *This has been fixed in 1.1A. C. ESCAPE during a TBC communication may hang the ICC186 controller on 1.0D and lower levels. If an ESCAPE causes a hang or the controller becomes hung, the following steps will free it: cd /usr/mbf/comm ./commload -b0 If the controller remains hung the system must be shutdown and powered off and on to free the controller. D. If MAGNET is stopped by removing the RSM process, TBC will also stop running. E. TBC may report an error 26 during a file transfer in transparent mode from GPx to MPx or SPx. The following program changes will prevent this: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg045 MPx: .PGMTBC.BRCV 1455 IF T2=1 THEN A9=0; GOTO 1513 SPx: /tbc/BCOM/BRCV 1456 IF T2=1 THEN GOTO 1525 F. TBC now supports 2 ports communicating at 9600 bps or 1 port at 19.2K bps. Previous to 1.1A, TBC supported only 1 port communicating at 9600 baud. If 2 TBC ports were running simultaneously they had to communicate at 4800 bps. G. Data in received files should be verified if an Auto-Restart or RVI occurred during a BCOM session. H. A premature termination of a TBC session may be caused by a "TIMEOUT TERMINATION" occurring without waiting for the length of time specified in the TIMEOUT value. I. If a remote system fails because of a dump or power failure or some other catastrophic failure the local system may terminate communication by hitting . J. Device T000 should be removed from the /etc/bfsdevs file because it can cause screen display problems in BCOM. K. If a BASIC program is in a BQR filelist that is to be transmitted by TBC, an error 67 and "sh: checksum : not found" will occur. *This has been fixed in 1.1A. L. The ITP product must be installed with "mbfinstall" if the user wants to use BQR utilities to create TBC transmit queues. M. BASIC error 59 with a system error -657 occurs when attempting to open a TBC comm port and the incorrect TBC public key is installed. N. The full path name must be entered for the destination file when modifying the TBC Transmit Queue for File Transfer. O. TBC may report a BASIC error 95 with a system error -614 and a message "unknown I-Device open error", which is caused by insufficient disk space. P. When the LSLOG is full, the LSLOG program may go into an infinite loop to locate the last TBC session. Q. The termination sequence ETX/DLE-EOT, which is normal for non-MAI, TBC is treated as abnormal by MAI TBC. 7.4 TCP/IP NOTES AND CAUTIONS WARNING: The FTP application is NOT certified and NOT supported on the 1.1A release for the GPx Series 40. NOTE: Systems that run TCP/IP will display the following messages when the system boots: lo0: flags=29 (UP, LOOPBACK, NOTRAILERS) inet 127.0.0.1 netmask 0xFF000000 dlk flags=63 (UP, LOOPBACK, NOTRAILERS, RUNNING) inet aa.bb.cc.dd netmask 0xFF000000 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg046 broadcast aa.255.255.255 The messages originate from 'ifconfig' which runs when the system boots and checks the network configuration. The first line of the message is the optional flags for the interface and the second line is the internet address, the mask and the address for broadcasts to the network. The aa.bb.cc.dd will vary from machine to machine and is the internet address assigned to the system. For more detail see the 'ifconfig' section in the TCP/IP User Guide. 7.5 TERMINAL SERVER NOTES AND CAUTIONS NOTE: Control codes, the CTL-I thru IV and combinations of the CTRL key and another key may be trapped by the terminal server. WORKAROUND: Set the teminals server control codes by using the CLI stty command or the NA "set port" command so the codes do not match. Control codes to be aware of are: - Input start/stop characters - Ouput start/stop characters - Attention character - Telnet ESCAPE character - Erase character/word/line characters WARNING: Macros defined in the /usr/spool/ercpd/bfs/macros file will not be recognized. NOTE: The rtelnet and aprint commands are not supported on the GPx Series 40 in the 1.1A release. WARNING: The table of contents does not match the order of the Sections of the MAI-NET Terminal Server Network Administrator's Guide, M0221. 8.0 RELATED DOCUMENTATION Manual Number Title ------------- --------------------------------------------- M8215A GPxTM Series 40 Installation and Maintenance Manual M8215B GPxTM Series 40 Installation and Maintenance Manual Addendum Package M8224A GPxTM 240 Installation and Maintenance Manual M8224B GPxTM 240 Installation and Maintenance Manual Addendum Package M0186A GPxTM Series 40 Software Installation and Configuration Manual M0187A BOSS/VXTM System Administrator Guide M0188A BOSS/VXTM Reference Manual M1089A BOSS/VXTM User Guide M0190B BOSS/VXTM Diagnostics Manual for GPx Series 40 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg047 M0217A BOSS/VXTM Transportable Batch Communications (27xx/37xx) User Guide M0228A BFSINT Reference Manual M0053B Universal Printer Driver Reference Manual M0229 MT-4409 High Capacity Tape Drive User Guide M5163B MT-4405 (GCR) Tape Drive Installation and Operation Manual M0273A BOSS/VX 1.1A Update Manual M0221 MAI-NET Terminal Server Network Administrator's Guide 3.2.9 5 1/4" FLOPPY DISK DRIVE The 340/440 will support the existing 5 1/4", 1.2 MB floppy disk drive, P/N 514127-311. The GPx 40 Series allows a maximum of 1 floppy disk drive per system. 3.2.12 UPS REQUIREMENTS FOR GPx 440 WITH THE EXPANSION CHASSIS. The main chassis, expansion chassis and a terminal can run on a single uninterruptable power supply that is provided by MBF. 3.1.3 On-Line Backup On-Line Backup provides the ability to backup one or more the files continue to be accessed by users. This is performed in such a way that the integrity of the backup copy is maintained. The backup may be made to any tape device or to another disk. The cpio command includes a new option, -J. A new utility, olb, provides support for cross-file integrity (explained below). On-line backup is made possible by the use of a technique called journaling. Journaling is used when a file is being backed up and modified at the same time. The original data in the file is "shadowed" or set aside for use by the backup utilities. Thus, an application has the new records available to it while the backup utility accesses the shadow records. When the shadow copy is no longer needed, it is deleted. File Integrity A group of files can be backed up using one of three methods. The first two methods, File Integrity and Extended File Integrity, allow the files to change in relationship to each other. The third method, Cross-file Integrity, backs up a group of files in such a way that they are unchanged relative to each other. Simple File Integrity is preserved by the cpio command. The cpio command can be used to backup one or more files using the journaling technique. Since cpio processes one file at a time, journaling is used on each file in turn, guaranteeing the integrity of each SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg048 file as it is backed up. The effective time of the "snapshot" of each file in the filelist will be different, and depends on the position of the file in the filelist. Thus, it is possible to make a multi- file update, and have a backup which includes the change made to one file but not to the others. For example, suppose a client data base consists of three interrelated files. The first may contain the client name, the second the client address, and the third the client phone number. An on-line backup is started by invoking cpio on the three files with the journaling option. After the name file is backed up, while the address file backed up, and before the phone number file is backed up, a client is deleted from the data base, removing a record from each of the three files. The backup will have the client's name and address, but not the phone number. The data in the backup is therefore inconsistent. The olb utility provides Extended File Integrity, which narrows the window when the data is inconsistent. Olb starts journaling on all of the files in the file list, then starts the specified backup process. Journaling is stopped after the backup process is complete. Changes made to a file before olb starts journaling will be backed up, while those made after olb starts journaling will not be. A window exists from the time olb is started on the first file to the time journaling is started on the last file. This window is much smaller than in the previous example. Cross-file integrity exists when the user guarantees that there will be no multi-file updates to the data during the time olb starts journaling on a group of files. Since the BOSS/VX Operating System has no method of determining when all files are in synchronization, guaranteeing file synchronization is the user's responsibility. Some suggestions on how to achieve file synchronization follow. To create a backup with cross-file integrity requires several steps: 1. Stop the application from making changes to the files being backed up, 2. Invoke olb to start journaling on all files "simultaneously," 3. Wait until olb starts the backup using cpio with journaling, 4. Release the application so that modifications may continue, The first step of synchronizing the application is done prior to invoking olb. The actual method used will be tailored to the application. Some possibilities are: o User logoff - the simplest method, all users would be voluntarily or forcibly logged off the system until journaling has been started on all files. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg049 o Menu lock - prevent operators from starting new transactions by locking them in a high level menu. The synchronization program would wait until all operators were locked in a safe menu. o Transaction boundaries - similar to menu lock, but could involve massive application changes. This technique amounts to making the application perform rudimentary transaction processing. At the beginning of each "transaction," the application would check for an "olb synchronization request" and wait until authorized to continue, and then register "in transaction." At the end of the transaction, it would change its status to "not in transaction." o Batched updates - file modifications would be made to a special set of temporary files during synchronization. The application would have to be modified to switch over and back. This method is practical only if file I/O is centralized. The second, third and fourth steps of guaranteeing crossfile integrity would be performed by invoking olb on a shell script instead of an individual cpio command. The shell script would be executed after olb had started journaling on all files to be backed up. The shell script would restart the application, reversing whatever technique was used to synchronize the application, before invoking cpio with journaling. An example, using a synchronization program called SYNCH.PGM, a restart program called RESTART.PGM, a filelist called bklist and an on-line backup shell script called bk.sh would look like this: > SYNCH.PGM > cat bklist | olb bk.sh where bk.sh contains: # On-Line Backup Script RESTART.PGM cpio -J < bklist > /dev/tape Journaling is employed by using the -J option, which has been added to the standard UNIX backup utilities. This option is initially provided for cpio only; future release will provide it for tar and dump. The -J option causes the file system to start journaling and access the shadow records. If journaling was already in effect, the program "sees" the file as it was when journaling was first started. When cpio is used with -J but without olb, journaling for each file is started when it is first accessed by cpio, and is stopped when cpio moves to the next file. Backing up with Extended File Integrity is provided by using the new olb utility in conjunction with cpio. Olb accepts a list of files requiring journaling from standard input, then executes a user specified command. The command is responsible for performing the backup. System Performance The impact of On-Line Backup on the system is a function of the amount of data being backed up, the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg050 degree of cross-file integrity requested, and the amount of file modifications made to the files which are in journaling mode. The impact of using OLB may include reduced system throughput, using large amounts of additional disk space and using up inodes. To minimize the impact on system performance, olb, like any other backup utility, is best used during non-peak hours. In addition, the use of the cross-file integrity feature should be minimized by choosing the smallest set of files that must be synchronized for backup. Backing up large sets of files with the olb utility will result in all files being opened simultaneously in journaling mode which may exhaust some system resources. olb uses a file pointer for each file with journaling turned on. Until journaling is turned off that file pointer is not available for other use. Therefore, the DCT maximum number of open files parameter may need adjusting in environments where file use approaches the maximum number of open files. For further information, see the manpages for cpio(1) and olb(1). 3.1.6 Auditor's Log Book ALB is a new feature, for the GPx Series 40/70, that provides automatic audit information recording capability. It is a means of storing the modification history of a data file, and is based on the MPx ALB feature. (A list of the differences between MPx and GPx is provided in section 6.) The Auditor's Log Book supports the following data file types: Indexed, Direct, Sort and Multi-keyed. ALB does not support Serial, String or Business BASIC program file types. 3.1.6.1 What ALB logs Audit logging is selected on a file by file basis. Two separate log files, primary and backup, are maintained for each source data file for which logging is requested. The primary log file is where all record updates to the source file are recorded. The backup log file is used occasionally to hold the primary log file's data for archiving when the primary log file becomes full. The types of file/record operations that are logged by ALB are: o Addition of a record. o Rewriting of a record. o Deleting a record. o Turning Audit logging ON or OFF. o Turning Audit WriteThru ON or OFF. o Turning Audit WriteAhead ON or OFF. o Renaming the data file. o Erasing the data file. o Switching the primary and backup log files The types of file/record operations that are NOT logged by ALB are: o Reads/extracts of a record. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg051 o Addition of key sets to a multi-keyed file. o Changes to the number of records in a file. There are two types of log entries that can be made to a log file. They are based on the type of modification being made. Information that is logged on a record basis includes: o A code denoting the type of operation. o The user ID number of the person who made the modification. o The group ID number of the person who made the modification. o The process ID number of the process that made the modification. o A date stamp denoting the date and time the modification occurred. The date recorded on the GPx systems is the systems Greenwich Mean Time (GMT). o On indexed files, the index number of the record being modified. On a direct or sort file this field will be null. On a multi-keyed file this field will contain the record length. o On write or rewrite operations, a copy of the new data that is being written to that record, and on remove operations, a copy of the old data being deleted, are appended to the end of the log entry. Information that is logged on a file basis includes: o A code denoting the type of operation. o The user ID number of the person who made the modification. o The group ID number of the person who made the modification. o The process ID number of the process that made the modification. o A date stamp denoting the date and time the modification occurred. The GPX systems is the systems Greenwich Mean Time (GMT). ALB environment The ALB features can be used on the GPx70/GPx40 series systems from: o BASIC - Audit logging from BASIC is transparent to the user. If logging is started for a file and turned on, all writes to that file will automatically be logged. There is one exception, if the source file is opened with an 'isz=' clause an error will be returned. There are no changes to syntax in any of the BASIC commands to support the ALB feature. o GPx MBF System Utilities - All Audit logging facilities, e.g. start/stop audit logging, are SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg052 modified from the System Utilities. NOTE: ALB is only supported by commands that utilize the bfs file system, as with BUSINESS BASIC and the system utilities. Modifications made outside of the bfs environment to the data or log files, such as the UNIX commands 'cp', 'mv', 'rm' etc., are not logged in the log file and may cause problems in later operations of the ALB features. 3.1.6.2 Write Options Available with ALB ALB log files have the same three write options that are available for other Business BASIC files: Buffered Write, WriteThru and WriteAhead. Refer to Section 3.1.3 3.1.6.3 Utilities Changed for ALB File level modifications are made for ALB via the MBF system utilities. Each of the following utilities were changed to include options that support audit logging for a data file. fcreate The 'fcreate' utility provides 4 additional parameters for logging: Audit Logging: This allows the user to specify if record updates to the source data file need to be logged. Turn logging ON or OFF. If logging is turned on the next 3 options will be displayed. Audit File Name: This option allows the user to specify in which directory the log file is to be created. Once the directory name is entered or CR for the current working directory, the primary auditlog file is created. The new log file will be the same name as the data file with the addition of a suffix '.aud'. Audit File Write: This option allows the user to select which of the three write modes should be used for the log file. Audit Log Records: This option allows the user to specify the maximum number of records in the primary log file. The defaults is 2 times the number of records in the source data file. If logging is started from 'fcreate' a log entry will be added to the log file. fchange The 'fchange' utility provides the same 4 additional parameters as above and one more parameter: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg053 File Switch: If a backup log file exists a YES value will display, if a backup log file does not exist then a NO value will be displayed. If a NO value is displayed the user can select to switchlog files. Once the switch is complete a Yes will be displayed. After each change has been made to the source or log file a log entry is added to the log file to record the change that has taken place. There are no log entries for changes to source file write options or changes to the number of log records. finfo 'finfo' has been enhanced to display the audit log information of the data file. The following display lines have been added: AUDIT LOGGING.... AUDIT FILE WRITE. AUDIT FILE NAME.. AUDIT LOG RECORDS fcopy If an audited file is copied, its log files will not be copied to the destination directory, only the default log file name will be defined within the file header. The copy operation will not be logged. Any updates to the destination file will be logged within a newly created log file, or in an existing audit log file. If the log file is copied, the default source file name will be defined within the log file header even in the case that the source file does not exist. ddisplay A new column, AUDIT/WRITE, has been added to the 'ddisplay' utility display. AUDIT/WRITE column contains 2 items: o The 1st will denote if auditing is started or not. If auditing is started an 'A' will display otherwise the space will be blank. o The 2nd will denote the type of write mode assigned to the file, WT for WriteThru, BW for Buffered Write and AW for WriteAhead. An additional file type of 'aud' will be displayed for audit log files. fdelete The deletion of a source data file does not automatically delete its log files. The deletion of a source data file which has logging enabled causes a log entry to be written to the log file. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg054 frename 'frename' utility automatically renames the source date file and its primary and secondary log files. The file name pointers within the header are Explicit renames of individual log files are allowed. If a log file is explicitly renamed, no change is made to the file name pointer within the file header of the source file or log file. fmove 'fmove' utility automatically renames the source date file and its primary and secondary log files. The file name pointers within the header are also updated. Explicit moves of individual log files are allowed. If a log file is explicitly moved, no change is made to the file name pointer within the file header of the source file or log file. 3.1.6.4 Switching Log Files In the event that the primary log file becomes full and cannot grow, or it is desired to backup the log file, a switch operation may be performed. The actual switch is done in the bfs file system by the following series of operations: link of the primary file name to the backup file name, delete the primary file then create a new primary file. The backup log file will be the same name as the log file, but will have a '.audbak' suffix similar to the primary log files '.aud' suffix. Example: primary log file name '/usr/alb/logfilename.aud' backup log file name '/usr/alb/logfilename.audbak' There are two types of switch operations, manual and automatic. Manual Switch A manual switch operation is done via the 'fchange' utility. This is done by selecting the File Switch option from the fchange utility menu. If the parameter to the right of this option is NO, a manual switch can be done by answering yes to the prompt. After the switch is complete a YES will appear to the right of the File Switch option. If the parameter to the right of this option is YES, this means that there is already an active backup log file for that source file. In order to continue with the manual switch the backup log file must be either backed-up to tape and then deleted or moved to another directory. Once the backup log no longer exists in that directory the manual switch can proceed as in the above paragraph. Automatic Switch SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg055 The automatic switch is performed by the filesystem to switch the primary log file with the backup log file. An automatic switch is done automatically by the file system when the primary log file is full so that the user can proceed with normal file operations without having to run the fchange utility. An automatic switch takes place when the primary log file is full and another operation is performed on the source file which requires a log file entry. As with the manual switch the backup log file must not exist in the primary log file directory. Notification of Switch Operation For every manual or automatic switch operation an 'mail' message will be automatically sent to the 'root' system administrator. The mail message will contain the time, date, user ID, type of switch operation (manual or automatic) and the complete filename of the source data file. 3.1.6.5 Technical Aspects of ALB Format of the Log File The ALB log files, both primary and backup, are indexed file types. An indexed file was chosen because it has a fixed record length and it is easy for user applications or Origin to generate reports. The following is the format of the log entry: +---------------------------------------------------------------+ |Format|Op|Filler| User|GrpID|Proc| Date | Time |Misc|Data | | | | | ID | | ID | | (GMT) | | | +---------------------------------------------------------------+ | | | | | | | | | | | | 0 |A | Nil |123 |101 |2345|01/23/90|05:07:45| 4 |Rec 4 |. | | | | | | | | | | | +---------------------------------------------------------------+ Format level: 1-byte character; The format level for the log record. Its value will be 0 for 1.1A. Operation: 1-byte character; Type of operation performed on the data file. 'A' Addition of a record. 'W' Rewriting of a record. 'D' Deleting a record. '1' Turn Audit logging ON. '0' Turn Audit logging OFF. 'Y' Turn Audit WriteThru ON. 'N' Turn Audit WriteThru OFF. 'a' Turn Audit WriteAhead ON. 'd' Turn Audit WriteAhead OFF. 'R' Rename the data file. 'E' Erase the data file. 'S' Switch the primary and backup log files. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg056 Filler: 6-byte filler; This field is used to accommodate potential log expansion in the future. User ID: 16-byte string; Owner's user identification number. Group ID: 16-byte string; Owner's group identification number. Process ID: 8-byte string; Process identification number. Date: 8-byte string; This field is used to record the date the event occurred. The format will be the current system date format, which is either 'MM/DD/YY', 'YY/MM/DD' or 'DD/MM/YY'. Time: 8-byte string; This field records the time the event occurred. The time used is the system's Greenwich Mean Time (GMT). This was done to save the time it took to convert from GMT to local time. The format is 'hh:mm:ss'. Misc: Short integer(binary); For multi-keyed files, this field will indicate the record length. For indexed files, this field contains the record index number. For direct or sort files,this field will be null. Data Record: Variable length: This field contains the recordimage. For an indexed file, the record image will be the data record. For a direct file, the record image will contain the key value followed by the data record. For a sort file, the record image will be simply the key value since sort files are direct files with the record size equal to zero. For a multi-keyed file, the record image will be the data record. 3.1.6.6 ALB Differences GPx70 and GPx40 are fully compatible. GPx40/GPx70 and MPx differences: o GPx supports source and log file WriteAhead, MPx does not support Write Ahead. o MPx supports auto and manual switch of an open file, GPx will not support this feature on the 1st release. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg057 o DIR utility on MPx displays the audit log file as type indexed, where the 'ddisplay' lists the file type as 'aud'. o CREATE utility on MPx will define both the primary and backup log files at the time the source file is created and logging is started. 'fcreate' on GPx will only define the primary log file, the backup log file will be defined during a switch operation. The same situation occurs when audit logging is started from UPDATE and 'fchange'. o Save/Restore: MPx has special handling of source and log files during the save/restore processes. GPx has no special procedures for ALB files. All files to be backed-up must be specified in the proper backup file list. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB035 Pg058 FIB 00036 04/15/91 *** Release 1.1A Notes & Cautions *** GPx Series 70 Wally Moore 02/27/91 Release of 1.1A Type: Informational Level 1.1A of BOSS/VX for the GPx Series 70 is now available. This release is the recommended Operating System for the GPx Series 70 Systems. The 1.1A Operating System is derived from the 1.0A O.S, and contains the following new features and enhancements: UPD Simple Compiler On-Line Backup CISAM/BFS User Access of BFS C-Library Functions New File Write Options Auditor's Log Book Errorlog Monitor Bad Block Mapping lphold Command New dct scripts Ethernet and TCP/IP 2780/3780 Batch Communication SMD 8" Disk Drives 8MM HCC Tape Drive 1/2" MTS Tape Drive New Parallel Printer Controller On Line Configure The Software Announcement No. 190 contains general information about the Level 1.1A BOSS/VX Operating System. For information on ordering new Software and Hardware in 1.1A see Marketing Announcements 1006 and 1015. Following are the Notes and Cautions for the Operating System level 1.1A on the GPx Series 70. It is recommended that you read these Notes and Cautions before install or updating the OS. I. GENERAL OPERATING SYSTEM AND HARDWARE NOTES AND CAUITONS 1. CAUTION: The new SSM firmware (rev 2.0.9) is required for correct operation of the 1.1A release and therefore must be installed as part of either an update or full installation. One of the new features in this release is the simplified installation procedure. For typical update and full installations, this simplification eliminates all of the device specific boot commands previously required. Changes have been made to the SSM firmware to support an "install" command which will present a menu and also eliminate several of the install steps. To take advantage of this feature, the SSM firmware must be updated first. To do this, boot the existing miniroot, insert the new 1.1A release tape and run the ./INSTALL program. Select the "S" option to install the new SSM firmware and then shutdown the system, first to operation firmware and then to poweroff or perform the "zap" SSM command to execute the new firmware. Once the system has rebooted to the operational firmware level (prompt: --->), enter "install" and answer the prompts of the menus. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg001 2. CAUTION: When doing an update install from 1.0A to 1.1A you must request re-installation of the dct. The default is "no," so you must respond "yes" to get the new dct values. dct installation is automatic on a full installation. Failure to update the dct will probably cause the system to hang later during boot. In addition, there is a new command called newdct which can give a better estimation of system resource requirements based on more information. NOTE: If the currently installed dct has been customized, these modifications should be integrated into the new dct files. Since the dct files may change from release to release, it is not correct to carry an existing ascii file forward or to use an ascii file created from the currently running kernel. If the actual customizations are not known, they may be determined by comparing the currently running dct (mkdct -x -) to the ascii file for the current memory size (e.g. dct32.asc). 3. There are initialization files that reside in the rc0.d and rc2.d directories which have had name changes between the 1.0A release and the 1.1A release. For proper operation of the system, the old files must be eliminated so that there are not duplicate files. However, an update install normally doesn't delete files. In addition, some of these files may be modified by the administrator of a site to customize the initialization of the system. Therefore, the installation process creates a directory called v1.0a in each of the affected directories and moves each of the files that will be deleted by the installation into the new directory. A warning is then displayed on the screen to alert the installer that any customization done previously to these files must be done again to the new files (with their new filenames). CAUTION: There are 4 files which have been changed since the initial beta release of 1.1A and require special installation handling. These files exist in the /etc/rc2.d directory and, because the default list of files to retain from the previous release includes these files, the update install will overwrite the new files. The files are: /etc/rc2.d/S25savecore /etc/rc2.d/S30autoconfig /etc/rc2.d/S87initbd /etc/rc2.d/S90disable.ports If any of these files have been modified or customized by the user, those files should be renamed prior to the update installation and the changes merged into the new files after the installation. If the files have not been customized they may simply be deleted prior to the installation. 4. This release introduces the Parallel Printer Controller. At this time only 1 PPC may be installed in a system. One PPC will support up to 4 parallel printers. 5. This release introduces the Synchronous Communications Controller (SCC) to support 2780/3870 Transportable Batch Communications (TBC). At this time, only one SCC board may be installed on the system and only 1 of its 4 ports may be used. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg002 6. Irregular performance has been observed when running very large configurations. This problem is under investigation at this time. When other potential reasons for performance problems have been eliminated (for example, io bandwidth, disk balance, streams buffer allocation,etc.), check for swapping activity. A small amount of free memory (obtained from sar -r under "freemem") is one indication of swapping activity. The amount of freemem should stay above 70. Another indication of swapping is the swap queue size (obtained from sar -q under "swpq-sz"). When no swapping is taking place, swpq-sz will not display any value; values larger than two are reason for concern. A third indication of swapping is the number of swaps per second which can be obtained from sar -w. If swapping is taking place, the solution is to add additional swap space using the swap command (see the manpage). It appears that spreading the swap space out over additional disks may be as important as the amount of swap space in some circumstances. 7. The 4315 terminal is supported on this release with the 4314 terminfo file. 8. The internal firmware of the 4313 and 4314 terminals is configured by default to have uni-directional X-on/X-off flow control; this generally occurs when the terminals are powered on. If you notice characters dropped (especially during heavy 16-way usage, and possibly during "transmit screen" operations), the terminal should be reconfigured for bidirectional X-on/X-off flow control. 9. Terminal and slave printer names are assigned in the range 0..999 (e.g. T0 - T999; L0 - L999). In previous releases, if a BASIC open of a file in this range was attempted and there was no configured port with the given device name, then the file was assumed to be a disk file. Now, all files within this range will be assumed to be device names. Therefore, it will not be possible to access a disk file in that range unless the fully specified path name of the disk file is given. 10. The /etc/dump command for backing up filesystems supports several new devices and has a new parameter, "C" for capacity, which simplifies the specification of tape size and density. 11. In order to use more than one 1/2" tape drive (including 8mm drives) with corresponding logical names, you must manually edit the file /etc/bfsdevs to add the new devices. By default, the logical names R0 and R1 are assigned for the non-rewind and rewind versions of the first 1/2" tape drive, tg0: R0:/dev/rmt/tg0n:: R1:/dev/rmt/tg0:: Additional drives should be numbered in a like manner: R2:/dev/rmt/tg1n:: R3:/dev/rmt/tg1:: 12. When compiling C programs on the GPx-70 series, the define flag ATT should not be set since using this define will require some include files which are only available on the Unix System V based GPx-40 series. To undefine the ATT flag, remove the -DATT option from the compiler option list (normally under the CFLAGS define in the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg003 Makefiles). Also, if using the bfs library, you must also use the seq library. 13. The Auditor's Logbook feature provides for automatic switching of log files when the primary log file fills up. At present, there is no support for manually switching the log files while the primary file is in use. 14. NOTE: When the Basic INITFILE directive is used on a file that has Audit logging enabled, two entries will be made in the log. The first entry will record an erase ("E") of the old file; the second entry records the initfile ("I"). 15. A new program, bbmap, maps physical disk block numbers to the corresponding areas on disk and, if possible, identifies the affected files by name. This program works correctly in most instances. However, there are two known problems: + Some sectors are in a range which bbmap does not understand and will report a garbage file name. Known sectors with this problem are 22023 and 22024. + bbmap will not work correctly on systems with SMD disks (device name: /dev/dsk/zd#). bbmap will confuse partitions of the wd and zd disks. For example, when bbmap is invoked with device wd0 it may return information about zd0. The failure will be easy to recognize because the filename reported will not exist on the device requested. As a result, bbmap SHOULD NOT BE USED on systems with SMD disks. 16. Three problems have been identified regarding the GCR 1/2" tape drive. + CAUTION: Turning off the power to the GCR while the system is running and the GCR is in use can hang the system. + NOTE: The GCR tape may hang when running certain patterns of short I/O reads and writes to the tape. This problem has only been seen when running NITRO. + NOTE: The GCR tape may hang when running the DEMON diagnostic test 14 (stream start/stop write test). 17. The 4230 printer is supported with the 4224 PDF. To do this, copy the printer definition file (as root): # cd /usr/mbf/etc/ptrtbl # cp 4224 4230 18. The PDF for the HP laserjet printer is called 4231 in this release. In GPx Series 40 systems the PDF is called hpljet. 19. After using pqueue to stop a multi-page print job in the middle, a restart will cause the job to resume printing at page 1, not at the page at which printing was stopped. To work around this problem, use the lpmaint command to specify the beginning page number when instructing the spooler to resume printing: # lpmaint job# begin=n -resume where job# is replaced with the spooler job number and n is the beginning page number. This technique will not work for jobs SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg004 printed in raw mode. 20. If the printer port of the SSM is configured as a DataProducts printer but there is no printer connected to the port, the system will continually poll the printer port for a response during the next boot cycle. Symptoms include reduced performance and a steady indication of processor usage on the front panel even if no other work is being done on the system. Work-arounds are to (1) plug the printer cable back in or (2) if no printer exists, deconfigure the port and reboot the system. If the cable falls out after the boot the problem will manifest itself when a job is submitted to that printer. Again, the problem may be resolved by plugging the cable back in. 21. The sdate utility will not change the date format as it is supposed to if it is invoked directly from the command line or shell. If sdate is invoked by entering the menu system it will change the date format as expected. 22. A change has been made to allow the dynamic configuration value BUFPCT to be set to 90 percent (old limit was 50 percent). Increasing BUFPCT to a value higher than 50% may increase performance of IO intensive tasks that do not require a large number of processes. However, running a large number of interactive tasks with a BUFPCT value of greater than 50% may cause excessive swapping and a resultant loss of performance. II. ETHERNET/LAN NOTES AND CAUTIONS 1. A major new feature available on this release is the Ethernet Lan communications protocol called TCP/IP. It is installed during the product installation phase by running mbfinstall. Two products are required, LAN and TCP. Additional information is requested of the operator during the installation. Once these products are installed it is essential to reboot the system to switch over to the new kernel which has just been installed. CAUTION: YOU MUST SHUTDOWN TO LEVEL 0 after installation of the TCP product. 2. The rwho daemon WILL be supported for the FCS release of 1.1A. However, the rwho command will display only GPx Series 70 machines. GPx Series 40 machines use a different address protocol which is not recognized by the GPx 70 operating system. This restriction in no way limits the ability to use other TCP/IP functions such as rcp and rlogin. 3. When accessing a GPx 70 from a terminal connected to a terminal server there is a possibility that characters typed and intended for the application may be intercepted by the terminal server. Keys likely to have this problem include the programmable function keys, motor bar keys (MB-I .. MB-IV), and combinations of the CTRL key plus another key or keys. If any of these keys match the five or so control codes configured for use by the terminal server they will be trapped by the terminal server and not passed on to the host. The workaround is to set the terminal server control codes using the Unix stty command or the Network Administration (NA) "set port" command, so that they do not match any control codes you intend to pass to the host. The Control codes are: - Input start/stop characters - Output start/stop characters SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg005 - Attention character - Telnet escape character - Erase character/word/line characters See the man page for stty(1) or the NA Guide (M0221) for more information. 4. Macros defined in the /usr/spool/erpcd/bfs/macros file are not recognized by the terminal server. 5. The rtelnet command is not supported in the 1.1A release. Also, the 'start' command cannot start up tasks on terminals connected via terminal servers. 6. Normally, when accessing a host GPx70 system from a terminal server, the terminal device name (e.g. /dev/ttyXA/XAAF) and the b-device name (e.g. T341) will be assigned randomly. There is a mechanism for establishing static tty names using telnet and a user-provided file, /etc/remote.in. This feature is documented in the BOSS/VX Release 1.1A Update Manual (M0237) and will also be documented in the Software Announcement. 7. Slave printers may be connected to terminals which are connected to terminal servers and may be accessed from the terminals to which they are attached. However, slave printers on remote terminals may not be accessed from other terminals or tasks. III. TBC NOTES AND CAUTIONS 1. For systems with configurations of 75 terminals/ghosts or greater will experience problems with BCOMPFX. BCOMPFX prints the header information then aborts with no error messages. Change statements 2020/2025 and set MAXTERM/MAXGHOST = 512. 2. TBC should run on port 0 of the SCC board only. No other ports are supported. 3. Only one SCC board is supported on each GPx 70 system. 4. The maximum supported baud rate on GPx 70 is 9600. 5. If the user wants to use BQR utilities to create TBC transmit queues or to convert received files, the "ITP" product must be installed also during "mbfinstall". 6. When an incorrect TBC public key is installed, a system error -657 and a BASIC error 59 may be returned during opening the TBC Comm port. 7. When the SCC controller board is hung, please do the following steps to bring the controller back: (1) The task that is running BCOM must exit from BASIC. (2) cd /usr/mbf/comm (3) ./commload -b0 (4) Check to see if the load is successful. (5) If the load is not successful or the controller remains hung, the user must shutdown and power off and on the system. 8. BCOM may report open errors in LSLOG. BCOM will retry the session, and this error will not affect the user. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg006 9. Without sufficient disk space in the root partition, TBC may report BASIC error 95 with system error -614 "Unknown I-Device open error" at the OPEN command. After resolving the disk space problem, perform "kill -2 pidnum" where pidnum is the process id of the tbcstub. 10. If the line is kept active by sending/receiving temporary text delays or continuous WACK conditions without actually sending data blocks for an extended amount of time (one hour) the local TBC task may "hang" for 5 or 10 hours before posting a "CONTROLLER PORT BUSY" error. If this situation occurs, the user can anytime before or after the error message is posted to terminate the session. 11. TBC may report an error 26 during a file transfer in transparent mode from GPx to SPx systems. The following programs need to be changed on SPx systems: - In program /tbc/BCOM/BRCV: 1456 IF T2=1 THEN GOTO 1525 12. TBC treats valid termination sequence ETX/DLE-EOT as abnormal. 13. A "TIMEOUT TERMINATION" may occur without actually waiting for the length of time specified in the TIMEOUT value. This will cause a premature termination of a TBC session. 14. A device T000 present in the /etc/bfsdevs file can cause BCOM screen display problems. This T000 device should be removed from the file. 15. TBC may report "ENQ RETRIES EXCEEDED" error in LSLOG during TBC communications with a heavily loaded system. 16. Due to a timing problem at closing the I ports, TBC may report "RETRY RECOVERY" error in the LSLOG. This should not affect TBC operation. 17. BCOM fails to Auto-Restart after reporting "TERMINATING FILE XFER DUE TO RECEIVER" error in the LSLOG. 18. Wrong error message was reported when saving the receive queue with the name "DEFAULT". We recommend that the user not save the receive queue with the name "DEFAULT". 19. When modifying a TBC transmit queue for file transfer, the user needs to enter full path name for the destination file name. 20. BCOM incorrectly bids for the line instead of re-dialing when the connection has not been established (such as line busy) during the autodial operation. IV. DIAGNOSTIC NOTES AND CAUTIONS 1. The DEMON diagnostic displays the time it reads from the hardware. This is "UTC" time and not the local time. Do not change the time with DEMON, as this will cause the OS time to be incorrect when the OS is rebooted. 2. In the multiple 16-way interaction test of DEMON, the "output a ripple pattern" to 43xx terminals will fail when run with loopback SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg007 cables. 3. CAUTION: Some of the DEMON disk tests can write over the entire disk surface, including the file system areas. These tests must be manually selected since they are not in the default selections. Do not select any of the nondefault disk tests if the disk being tested has customer data on it. Please read the DEMON functional specification (or equivalent user documentation) before using the DEMON diagnostic. 4. When testing the Parallel Printer Controller with DEMON, if an error occurs it is necessary to reconfigure the printer with option 5 (configure printer). 5. If the DEMON Ethernet Controller test is run immediately following the DEMON VME 16-way Interaction test the following error will be reported: eg 6.2.1, error number 108, pass 0 Failing unit: EG 0X5000 on VME 0 on SSM (slot0, SLIC 0) VMEbus BERR interrupt detected The Ethernet Controller board may be tested by running the test by itself. If errors are reported when the Ethernet Controller is run alone then the hardware may have an actual failure. V. ATP NOTES AND CAUTIONS 1. A BASIC program file transferred by ATP from a GPx system to a 1500 system will error on all multi-line statements at the receiving side. The work-around is to edit the BASIC program file on the 1500 system after file transfer. 2. The user must start ATP on an SPx system first during ATP modem connection between a GPx and a SPx. 3. An error 18 (Illegal operation) will be returned if an ATP user attempts to transfer a file to which he/she does not have write permission. 4. A STRING file with certain unprintable characters (between $00$ and $1F$) could be corrupted if the file was transferred via ATP from a BOSS/VX system to a BOSS/IX system. The workaround is to change the following programs on the BOSS/IX system: Program "ARP": 4205 IF F4<>7 THEN GOTO 4210 ELSE LET R9=0; IF S1-1 THEN WRITE RECORD (6,TBL=6900,ERR=4500)R0$(3,S9-2) ELSE WRITE RECORD (6,ERR=4500)R0$(3,S9-2) Program "ATP1": 5135 IF F$=7 THEN LET R9=0; READ RECORD (6,ERR=6000, END=5700) X9$; GOTO 5150 5. ATP will report errors when the user attempts to transfer files to systems which do not support the particular file types. 6. ATP can not be started on 2 terminals at the same time. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg008 7. Using ATP to transfer a string file to a system that does not support string files will cause the BOSS/VX system to skip the string file and the destination system to report "Invalid receive file type". 8. String files will be changed into Serial files on a BOSS/VS system which has OS version M.6G or later when the String files are transferred via ATP to the BOSS/VS system. 9. Using ATP to transfer a Multi-keyed file to a system that does not support Multi-Keyed files will cause the BOSS/VX system to skip the Multi-keyed file and the file that follows the Multi-keyed file. 10. Using ATP to transfer a Serial file to a MAI-1500 system, which does not support the Serial file type, will cause the BOSS/VX system to skip the Serial file. 11. When the user defines too many similar BQR filelist names, BQR may get confused about them and cause some of the filelists to be wiped out. We recommend not to define too many BQR filelists that have the same first three letters. 12. ATP Scheduler may report "IMPROPER ACCESS CODE" error sometimes even though the ATP Public Key is correct. V. ATP NOTES AND CAUTIONS 1. A BASIC program file transferred by ATP from a GPx system to a 1500 system will error on all multi-line statements at the receiving side. The work-around is to edit the BASIC program file on the 1500 system after file transfer. 2. The user must start ATP on an SPx system first during ATP modem connection between a GPx and a SPx. 3. An error 18 (Illegal operation) will be returned if an ATP user attempts to transfer a file to which he/she does not have write permission. 4. A STRING file with certain unprintable characters (between $00$ and $1F$) could be corrupted if the file was transferred via ATP from a BOSS/VX system to a BOSS/IX system. The workaround is to change the following programs on the BOSS/IX system: Program "ARP": 4205 IF F4<>7 THEN GOTO 4210 ELSE LET R9=0; IF S1-1 THEN WRITE RECORD (6,TBL=6900,ERR=4500)R0$(3,S9-2) ELSE WRITE RECORD (6,ERR=4500)R0$(3,S9-2) Program "ATP1": 5135 IF F$=7 THEN LET R9=0; READ RECORD (6,ERR=6000, END=5700) X9$; GOTO 5150 5. ATP will report errors when the user attempts to transfer files to systems which do not support the particular file types. 6. ATP can not be started on 2 terminals at the same time. 7. Using ATP to transfer a string file to a system that does not SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg009 support string files will cause the BOSS/VX system to skip the string file and the destination system to report "Invalid receive file type". 8. String files will be changed into Serial files on a BOSS/VS system which has OS version M.6G or later when the String files are transferred via ATP to the BOSS/VS system. 9. Using ATP to transfer a Multi-keyed file to a system that does not support Multi-Keyed files will cause the BOSS/VX system to skip the Multi-keyed file and the file that follows the Multi-keyed file. 10. Using ATP to transfer a Serial file to a MAI-1500 system, which does not support the Serial file type, will cause the BOSS/VX system to skip the Serial file. 11. When the user defines too many similar BQR filelist names, BQR may get confused about them and cause some of the filelists to be wiped out. We recommend not to define too many BQR filelists that have the same first three letters. 12. ATP Scheduler may report "IMPROPER ACCESS CODE" error sometimes even though the ATP Public Key is correct. 13. ATP Scheduler may skip files if NAKs occur between file transfers or during Line Turnaround. 14. Normal modem carrier drops (DCD) are reported in the mbf_errorlog. When the errorlog is filled, the message will be reported on Console. 15. When the ATP port reports "framing error", mbf_errorlog increments the port number everytime the "framing error" was reported. 16. ATP may report a task hang situation during communication sessions between GPx 70 systems in scheduler mode or in batch mode. Reboot may be able to clear this problem. If the problem persists, the user should replace the 16-way controller involved in the communications. VI. PCLINK NOTES AND CAUTIONS 1. PCLink 3.0*21 and below on BOSS/VX does not support slave printer functionality nor Industry Standard Printers. 2. For PCLink file transfer operations between PC and BOSS/VX systems, the system type should be set to BOSS/IX for BOSS/VX when using PCLink verison 3.0*20 and below. 3. The PCLink file transfer programs on BOSS/VX host systems must be in upper case characters. 4. To use "vi" via PCLink version 3.0*20 and below requires at least 4309 configuration at the connecting terminal port, and TERM value must set to "falco" for GPx 70. 5. When running PCLink via Modem, Control-S will hang the PC port. To resume operation, please hang up the modem and re-dial. ORIGINATOR: W. MOORE SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB036 Pg010 FIB 00037 04/25/91 *** GPX 70 Semaphore Deallocation problem [ WPSF 694 ] *** GPx SERIES 70 694 SEMAPHORE DEALLOCATION PROBLEM DALE JENSEN 4/91 CODE '9' TYPE: Problem/Informational PURPOSE: To inform the field of a problem that occurs when ghost tasks are killed from command mode. SYMPTOM: When the system has run out of semaphores the following symptoms may occur: 1. Starting up a new ghost task can result in a BASIC error 15 with a system error of -28. 2. If performing a system backup using the /etc/dump command, an error message saying 'DUMP: Getting new semaphores failed: semget: No space left on device ' may be reported. CAUSE: When a ghost task is started, one system semaphore is allocated for that process. Using the 'kill -9', 'killall', 'init 1' or 'shutdown -i1' will kill the ghost process but will not release the semaphore. The maximum number of semaphores configured on any GPx Series System is 64 and when they are all used, the errors may occur. The /etc/dump command also allocates a semaphore when running. If the process running the /etc/dump command is killed, the semaphore is not released. SOLUTION: Use the 'RELEASE' directive in BASIC to release ghost tasks. A 'RELEASE' will deallocate the semaphore. Use the escape key to abort the /etc/dump command if required. Another way to free up all semaphores is to do a system shutdown to a level 0 or level 6. The command 'ipcs -s' will display the semaphores which are currently allocated. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB037 Pg001 FIB 00038 04/24/91 *** 4222 Pitch Change, Configurable Parallel Printers [ WPSF 660 A3 ] *** GPx SERIES 40 - PRINTER INFORMATION FOR 1.1A CONDENSED PRINT ON PT-4222 660 CONFIGURABLE PARALLEL PRINTERS DAN ARTERITANO 4/91 ADDENDUM-3 TYPE: Problem SYMPTOM: If the Pitch on a PT-4222 is set to a value other than 10 and the form for that printer has a Pitch with a null value or 0, the printer will NOT print the pitch that the printer is set to. WORKAROUND: Configure the PT-4222 printer as a PT-4214 or set the pitch on the printer and in a form to the SAME value. NOTE: If the pitch is 16 in a form and 17 on the printer the printer will print 17 CPI. FIX: This will be fixed in 1.1B. ---------------------------------------------------------------------- TYPE: Informational PURPOSE: The GPx 240/340/440 erroneously have more configurable parallel printers in the 1.1A release of the Operating System. These printers can be configured because the GPx 640 supports Data Products interface printers but they are NOT supported as parallel printers on the GPx 240/340/440. The printers are: PT-4209 PT-4220 PT-4221 PT-4230 The PT-4220 and PT-4230 are configurable as serial printers on all of the GPx Series 40 systems. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB038 Pg001 FIB 00039 05/15/91 *** 13xx to GPx 40 ITP files conversion problem [ WPSF 708 ] *** ITP, 1.1A-40 Dan Arteritano Files do not convert from 13xx using cartridge transfer. Type: Problem Symptom: When using the cartridge transfer of ITP from a 13xx to a GPx 40 on 1.1A, the data will NOT convert when the data is being restored from . tape. Workaround: Instead of converting data as it is restoring, convert the data after it has been restored using the BQR utility. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB039 Pg001 FIB 00040 01/20/94 *** GPX 40 dosformat problems & sample dos commands [ WPSF 710 ] *** GPx Series 40 Dan Arteritano dosformat will not format Type: Problem Symptom: The 'dosformat' command will not format unformatted floppy diskettes on the GPx Series 40 systems. Workaround: The floppy diskette can be formatted using the UNIX 'format' command or the diskette can be formatted on another DOS system. If a diskette was formatted previously 'dosformat' will format the diskette. Do the following steps to format a diskette: format /dev/rdsk/f03ht (3 1/2", 1.44MB, drive 0) dosformat -f3 (formats floppy 0 3 1/2" 1.44) format /dev/rdsk/f13dt (3 1/2", 760KB, drive 1) dosformat /dev/fd1 (may have to use /dev/dsk/f13ht for 3 1/2 1.44mb) Examples of DOS commands: dosdir - DOS directory listing: ex. #dosdir /dev/fd0: doscopy - file copy to or from a DOS floppy ex. #doscopy /etc/passwd /dev/fd0:passwd dosrm - remove a file from a DOS floppy ex. #dosrm /dev/fd0:passwd dosformat - format a DOS diskette (high level format) ex. #dosformat -f3 (3 1/2" 1.44MB floppy 0) #dosformat -f3d (3 1/2" 720 KB floppy 0) #dosformat -f5 (5 1/4" 1.2 MB floppy 0) #dosformat -f5d (5 1/4" 360 KB floppy 0) dosmkdir - create a directory on a DOS floppy ex. #dosmkdir /dev/fd0:\test dosrmdir - remove a directory from a DOS floppy ex. #dosrmdir /dev/fd0:\test Refer to man pages for more information on DOS commands. ORIGINATOR: D. ARTERITANO MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB040 Pg001 FIB 00041 05/21/91 *** 1.1A*24 Update Release [ WPSF 709 ] *** Preliminary Field Bulletin Subject Author Date No. GPx Series 70 Dale Jensen 05/17/91 **** 1.1A*24 Update Release Type: Informational Purpose: To provide the field with market codes for ordering the 1.1A*24 release level. This release contains fixes for three problems seen in the 1.1A*23 release. The specific problems corrected are: 1. Terminal Server hangs due to a TCP/IP problem that can cause the telnetd process to spin in an indefinite loop. 2. Erratic terminal I/O behavior which appears as a slight delay when characters are being echoed to the screen. 3. A terminal hang condition by using commands such as 'write' to display data on one terminal from another and the receiving terminal has an active slave printer. When this occurs, both terminals will hang. Procedure: Although this release is not mandatory for all customer sites, it must be ordered for sites experiencing any of the above mentioned problems. Use the N/C 1.1A Update Market Code; WG358AA when ordering for a 5070 Series system and WG358AB for the 6070 Series system. Reference the original Sales Order number for 1.1A on this N/C order. A new configuration record is not required when updating from the 1.1A*23 to 1.1A*24 release. Related Documentation: Refer to the 1.1A Software Announcement, number 190, for update instructions. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB041 Pg001 FIB 00042 08/16/91 *** 1.1B OS Release Notice for GPx40 [ WPSF 727 ] *** GPx Series 40 Author: Dan Arteritano 1.1B Operating System Release Notice Type: Informational Purpose: To announce that 1.1B is available for shipment for GPx Series 40 systems. 1.1B contains new features, enhancements and fixes, including: o GPx 640 can access up to 64MB of main memory. o backup of /dev files will not cause a PANIC o Empty spool files do not remain in the /usr/mbf/etc/_qtemps directory after non-spooled, non-root print jobs o Printers can be modified in 'configure' in multi-user mode . Warning: This level of Operating System has additional functionally which has increased the kernel size approximately 300 KB. Because of this increase, systems which are close to the maximum number of users for . the amount of memory installed may have poor performance and may require additional memory to run 1.1B with the same response time as on previous levels. This same type of increase occurred in the 1.0C release. Therefore, if upgrading from 1.0B or lower the kernel will . increase a total of 600 KB which should be taken into account when calculating the number of users. Warning: Spooled printers may show errors in the spooler, stopping printing for that printer. If an lpstat -e displays an error 958 the 'ptstart' process for the printer must be killed to restart the despooler. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB042 Pg001 FIB 00043 10/18/91 *** Reduce Number of 'sh' Processes *** PRELIMINARY GPx Series 40 and 70 Dan Arteritano Reducing # of Processes for each BASIC Login Type: Informational Purpose: To reduce the number of processes started by an operator that runs a BASIC program. Solution: Operator ids that run a BASIC program as the initial program create 3 to 5 processes, 2 to 3 of them are 'sh' processes. The first 'sh' process is the login shell, which then runs '/bin/execsh' which creates another shell. To eliminate the process started by /bin/execsh vi the /usr/mbf/etc/mbfprofile before creating any operators, otherwise each operator's profile will have to be changed. THe change to make is: Add a period and a space in front of the /bin/execsh line. . /bin/execsh On larger systems this will greatly reduce the number of active processes and make available system resources to other processes. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB043 Pg001 FIB 00044 01/25/95 *** GPx Dump Procedure [ WPSF 747 ] *** Product: GPx Series 40 Author: Chuck Zimmerman Issue: GPx Dump/Panic Procedure (US & Canada) Type: Informational Purpose: To solve GPx dumps in the field as soon as possible without having to send the dump tape into corporate. This procedure saves valuable time in determining the cause of most GPx system dumps. This field bulletin is divided into several sections. They are: A. Recovering from a Panic and writing the dump to tape. B. Setting up a "in-house" system to process dumps. C. Downloading a dump tape. D. Reading a dump file using 'crash'. E. Notes and Cautions. F. Procedures for Sending a Dump to NSC. A. Recovering from a Panic and writing the dump to tape. When a panic or crash occurs, follow the steps below to recover from the panic and determine the reason why. 1. Write down the information that is displayed on the console screen. When a system crash/panic occurs, the error information displayed on the console terminal can be useful in determining the reason. 2. Reboot the system when prompted. 3. When the system reboots it automatically writes the contents of system memory to the swap partition on disk. 4. The system runs the file system repair program (fsck) on all disk partitions that were left mounted. This takes several minutes to complete depending on a quantity and size of the drives, the number and size of the files, etc. 5. When the file system repair is complete, the system continues to boot into multi-user mode. The system then checks for a panic dump in the swap device (partition): Checking for a system panic dump in the swap device. Standby. Dump found in the swap partition. Do you want to save it ? (y/n)> y 6. After entering "y" followed by a carriage return, you are asked to save the dump to tape or disk. Answer "t" for tape: Save to tape or disk ? (CR=t/d)> t Insert tape cartridge and press any key, or enter q to quit.> 7. The system displays a series of messages (shown below) and then you are asked to press any key. After pressing any key, the the system completes the boot procedure into multi-user. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB044 Pg001 WARNING ! DO NOT remove the tape while dump is in progress. Initiating dump to tape; Standby. Dump saved successfully. Saving /unix to tape; Standby. /unix saved successfully. Saving /etc/crash to tape; Standby. /etc/crash saved successfully. Press any key to continue 8. Before any users attempt to log on to the system, the file repair procedure MUST be performed. The procedure is shown in a separate document available from the National Support Center. There is a similar procedure in the GPx Software Announcement, #168, pages 79 - 80. B. Setting up an "in-house" system to process dump tapes. If an "in-house" GPx Series 40 system is used to process dumps, it . is recommended that the operating system level be 1.1B. Therefore, in this document it is assumed the "in-house" system is on the 1.1B operating system. Note: Refer to the Notes and Cautions section for information on the size of system dumps on disk and how to retrieve kernels from other operating systems. C. Downloading a dump tape. The amount of disk space required to download a single dump tape is equal to the amount of memory in the "problem system" plus an additional ten percent. This section gives two methods for downloading a dump tape. 1. Downloading the GPx dump tape at the problem site: a. Login as "root" (or 'su' to root on another terminal). b. Create a directory in a disk partition that is big enough to contain the memory image. If there is not enough disk space either clear off enough space, process the tape on the "in-house" system created in section B or send in the tape to corporate (See Section D). c. Using the 'cd' command change your current working directory to the directory created in step 'b' above. d. Enter the following command: # ldsysdump -d dumpname -u UNIXVersion where: 'dumpname' is any arbitrary file name where the dump will be restored on disk. 'UNIXVersion' is the version of the UNIX kernel from the problem system. 2. Downloading the GPx dump tape on the "in-house" system. a. Login as "root" (or 'su' to root on another terminal). SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB044 Pg002 b. Change your current working directory to the directory that was created in Section B of this document. c. The version of the UNIX kernel should already be on disk in your current directory. If not, restore the kernel now. d. Enter the following command: # ldsysdump -d dumpname -u UnixVersion where: 'dumpname' is any arbitrary file name where the dump will be restored to. 'UnixVersion' is the version of the UNIX kernel from the problem system. D. Reading a dump file using 'crash'. After the dump has been written to disk, the program '/etc/crash' is used to read the dump file. The file contains all the start up messages (or errors) that were displayed on the console when the system was booted and the panic error message. This section gives two methods for reading the dump file. 1. Processing the panic dump file at the problem site: a. Login in as "root" (or 'su' to root on another terminal). b. Change your current working directory to the directory where the dump file was downloaded to using the 'cd' command. c. Enter the following command: # crash -d dumpname -n /unix where: 'dumpname' was the name of the file assigned to the file in Section C-1-d. d. Go to Section D-3 of this document. 2. Processing the panic dump on the "in-house" system: a. Login as "root" (or 'su' to root from another terminal). b. Change your current working directory to the directory that was created in Section B of this document. c. Enter the following command: # crash -d dumpname -n UnixVersion where: 'dumpname' was the name of the file assigned to the file in Section C-2-d. 'UnixVersion' is the version of the UNIX kernel from the problem system. 3. After the crash command has been entered, the following output is displayed on the terminal screen: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB044 Pg003 dumpfile=,namelist=,outfile=stdout > To display the panic information to the terminal screen, enter the following command at the ">" prompt: > panic ! pg The information displayed on the screen contains both the information that was displayed when the system was last booted and the panic information. To obtain a printout of the information enter the following command at the ">" prompt: > panic ! lpr list= D. Reading a dump file using 'crash' (Cont.) If the information that is output from the crash utility is not "self explanatory" as to why the system dumped refer to the manual, "BOSS/VX System Administrators Guide" (M0187). Appendix B, Panic Messages, contains a list of the panic message and the possible reason(s) for why the system may have dumped. E. Notes and Cautions. 1. There is a known problem with the crash utility on the 1.1A release. Only dumps from 1.1A systems can be "fully" processed under this release. If the system being used to process dumps is on the 1.1A release, the 'strings' command is used in place of the 'crash' command. The syntax is: # strings dumpname | more 2. If a customer has a 525 MB tape drive and the dump is written to a 525 MB tape (DC 6525), only a system that has a 525 MB tape drive can download the dump file. If the dump is written to a 120 MB tape (DC 600A), the 525 MB drive writes the dump in 120 MB format. This way, the tape can be downloaded on any system. F. Procedures for sending a Dump to NSC (National Support Center) 1. BEFORE sending in a dump tape, process the dump using this procedure. If you are unable to process the dump, then send in the tape with the error log print out. 2. A Dump Report form IS REQUIRED and it MUST be COMPLETELY filled out (System Type, O/S Level, etc). If the dump report form is not completely filled out with all the necessary information, the tape will not be processed and the tape will be returned to the CSM location nearest the customer. 3. A System Alert should be filed prior to sending in the dump tape SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB044 Pg004 4. If a print out of the panic has been obtained and you are unable to determine the cause of the dump, the printout can be faxed to NSC along with the dump form (in place of sending the tape). The phone number is: (714) - 580 - 2382 ORIGINATOR: Chuck Zimmerman MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB044 Pg005 FIB 00045 12/24/91 *** File Corruption (ERR 14, -103) in Keyed Files *** FIELD BULLETIN SUBJECT AUTHOR DATE NUMBER -------------------- ----------- ------- ------ BOSS/VX & Open/BASIC Dale Jensen 8/21/91 **** File Corruption Error 14 With System Error -103 Purpose A difference in the way that BOSS/VX and Open/Basic interface with the file system can result in file corruption when certain file operations . are executed. The same file operations will not cause this file corruption to occur on other system platforms. Symptom A BASIC error 14 with system error -103 may occur during a the execution of a WRITE directive with a 'key=' option to a keyed file. The 'frepair' utility will report that the file is corrupted. Cause This problem will occur when records are written to a keyed file using the 'ind=' option to a record that had been previously removed. Each file has a Free Record Chain (FRC) that is updated each time a record is removed. The data for this FRC is in the data area of the record. Once a WRITE with an 'ind=' option is done to a record that is part of the FRC, the file becomes corrupted. Solution Application should be written so that WRITEs to a keyed file are never done using the 'ind=' unless the record had not been previously removed. In a future release, if a WRITE with an 'ind=' option is done to a record that had been removed, an error will be returned and the operation will not be performed. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB045 Pg001 FIB 00046 12/27/91 *** GPX40 & 70 File Check & Repair Procedure *** GPx 40 and 70 File Check and Repair Procedure This procedure is recommended for use by the system administrator. A qualified system's administrator should have completed MAI's "Managing Your BOSS/VX System", taught at MAI education centers. PLEASE MAKE SURE YOU HAVE A CURRENT BACKUP. If you do not have a current backup, please do one before executing this procedure. Note: Use a different set of tapes from your previous backup! You may need to restore your backup if the file repair utility is not able to fix all the data files. 1. Login as "root" on the system console "T0". 2. Have all users completely log off the system prior to repairing the data files. You can check which users are still logged on the system by using the "who" command at the system prompt. # who 3. After all users have logged off the system, shut the system down into single-user mode by entering the following command: # shutdown -i1 -g0 -y It takes several minutes for the system to completely shutdown into single-user mode. If the user "root" has a password attached, you will be required to enter the password when asked. If "root" does not have a password attached, enter when prompted. You will also be prompted for your terminal type. Press when prompted for terminal type. 4. Mount all file systems that are configured, by entering: # mountall 5. Change your working directory to '/etc/tmp', by entering: # cd /etc/tmp 6. List the contents of the directory, by entering: # ls -l 7. The command is step 6 displays output similar to the following: ________________________________________________________________________ | total 1 | | -rw-rw-rw 1 root root 0 Jul 1 12:45 0s3.1 | | -rw-rw-rw 1 root root 20 Jul 1 12:49 0s4.1 | | -rw-rw-rw 1 root root 0 Jul 1 12:43 root.1 | |________________________________________________________________________| NOTE: The command above assumes the system is a GPx Series 40, there is only one disk drive and that it contains three partitions. The names and SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB046 Pg001 number of files listed can vary from system to system. 8. The field which reflects the size of each file listed in step 7, appears to the left of the month field. If any of the file's sizes ARE NOT ZERO, file repair is required. If all files are zero, file repair is not needed and you may skip to step 17 of this document. 9. Enter the following command for each file in step 7 that is NOT ZERO: # fscklist where = one of the files listed in step 7. (i.e., 0s3.1, 0s4.1, etc.) After the above command is entered, a filelist of the files that need to be repaired is created. It takes several minutes for the list to be created for. each file partition that lacks integrity. After the list is created, the following message is displayed: _______________________________________________________________________ | /usr/mbf/bin/fl/fsck..f contains the names of the BFS | | ----------------- | files under /usr filesystem which lack integrity | |_______________________________________________________________________| Write down the name of the file that contains the list of the files which lack file integrity. It is only necessary to write the last section of the file name. In the example above, the last section is underlined. 10. After the last filelist has been created using the procedure in Step 9, run the file repair utility by entering: # frepair 11. The utility begins with a multiple choise menu containing the parameters for the utility to use during the analyze and repair process. To change the selection of an item, type the item number (without RETURN). An asterisk next to an item, indicates that the item has been selected. Please select the following items: _______________________________________________________________________ | File Analysis and Repair Utility | |-----------------------------------------------------------------------| | 1. REPAIR MODE 2. FILE SELECTION | | analyze single file | | *repair *selected files | | bad blocks | | | . | 3. REPORT DEVICE 4. INTERACTIVE | | terminal yes | | printer *no | | *file | . | | . | Type number to change selection, when all are correct | |_______________________________________________________________________| 12. A warning message is displayed on the screen: _______________________________________________________________________ |WARNING: Files or data might be lost, Proceed?? (yes/no): yes | |_______________________________________________________________________| 13. The screen is cleared and you are prompted to enter the report file name. Enter the name in the following format: repair.MMDDYY SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB046 Pg002 where MM = month DD = day YY = year _______________________________________________________________________ | Working directory: /etc/tmp | | | . | Type report file name: repair.MMDDYY | |_______________________________________________________________________| 14. The screen is cleared and you are prompted to enter the filelist(s) that contain the file or files to be repaired. Enter the name of the filelist(s) recorded in Step 9 of this document: _______________________________________________________________________ | Working directory: /etc/tmp | | | . | Type a file or filelist name to add, | | when done: fsck..f | | ----------------- | |_______________________________________________________________________| 15. Press when the last filelist name has been entered. The screen is then cleared and you are prompted to edit the list of filenames. At this point, press . _______________________________________________________________________ | Type number of selection, to end: | |_______________________________________________________________________| 16. The screen is cleared and you are asked if you want to specify template files. Answer "no" then . _______________________________________________________________________ | Do you want to specify template file(s)? (yes/no): no | |_______________________________________________________________________| 17. After the last file has been repaired, the message "PROGRAM DONE" is displayed. To bring the system back into multi-user mode, enter the following: # init 2 18. You are now ready to continue processing! ORIGINATOR: NSC SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB046 Pg003 FIB 00047 12/31/91 *** Patch Tape 49 for Printer Hangs on 1.1B is Available *** There is a patch tape available (Patch 49) from the National Support Center to cure printer hangs on BOSS/VX level 1.1B. The hung printer may show a status of "ERROR" in 'pstatus'. # lpstat -e (printer name) - may show -958 errors To obtain this patch tape, contact the National Support Center in Tustin and request Patch 49. ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB047 Pg001 FIB 00048 MAI COMPANY CONFIDENTIAL 05/22/92 *** "fuser' Command on 1.1B-40/1.1A-70 works differently [ WPSF 749 ] *** TYPE" Informational PURPOSE: To warn that the 'fuser' command does not work as on previous levels. SYMPTOM: 'fuser' is used to show the account and prosess number which currently has a file opened. The operating systems listed above only return the file name. WORKAROUND: None. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB048 Pg001 FIB 00049 MAI COMPANY CONFIDENTIAL 06/25/92 *** GPx Series 40 1.1B Software Announcement [ WPSS 194 ] *** 1.0 INTRODUCTION Level 1.1B of BOSS/vx for the GPx Series 40 is now available. It is the recommended Operating System for the GPx 240, 340, 440 and is the minimum level for the GPx 640 with EISA (BusTek) controllers and/or systems with greater than 16MB of main memory. The 1.1B Operating System is derived from 1.1A O/S and contains the capability to access above 16MB of RAM in the GPx 640 and bug fixes. This Software Announcement contains general information about the 1.1B BOSS/VX Operating System. Installation and update procedures can be found in the GPx Series 40 1.1A Software Announcement, #191. It is recommended that you read this document and the 1.1A Software Announcement, #191 before installing level 1.1B. For information to order 1.1B refer to Marketing Announcement 1054 for the United States and Canada or 1054I for International. WARNING: The 1.1B Operating System has increased funcionality which in turn has increased the kernal size approximately 300 kb in size. Because of this increase, systems which are close to the maximum number of users for the amount of memory installed have poor performance and may require additional memory to run 1.1B with the same responce time. WARNING: 1.1B has new parameters in the dct files, which will require that you install a new dct file when doing an O/S update. If any customization has been done to the dct file a copy should be made so that the customization can be incorporated into the new dct file. Before starting this, refer to Section 3.1 for the sets to copy the dct file. TABLE OF CONTENTS 1.0 Introduction........................................Cover 2.0 BOSS/VX Operating System History....................3 3.0 New Software Items..................................3 3.1 /etc/dct file changes...........................3 3.1.1 Copying the /etc/dct file.................3 3.1.2 /etc/dct file changes.....................4 3.2 'configdct' changes.............................4 3.3 'floppy' command................................5 3.4 'ldsysdump' command enhancements................6 4.0 Swap Space Recommendations..........................6 5.0 Notes and Cautions..................................7 6.0 Related Documentation...............................8 2.0 BOSS/VX OPERATING SYSTEM HISTORY 1.1A This release was the minimum level for the GPx 640. New features were Errorlog Watcher, TPS Product on the O/S tape, On-line configure, UPD Simple Compiler, Enhanced NMI & UPS support and up to 128 user SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB049 Pg001 connectivity on the GPx 640. 1.0D Contained PS 3.3B, which had enhancements and corrections to PS 3.3A. There was also a fix for an End-of-Media problem on the HCC tape drive and the 1/2" tape drives. 1.0C This release introduced the 1/2" MTS tape drive, Ethernet controller, 670 MB disk drive, support of up to 64 users, DOS Read/Write capabilities, PT-4220 serial printer, Slave printing on the DT-4312, TERMCAPS and TERMINFO files on the DT-4312 and DT-4309, displaying dashes when Security Violation PANICs occurred, the addition of lphold, printversion and bbmap commands. There were a number of bug fixes/enhancements including automatic shutdown when the UPS becomes active, the spooler will only reprint the page it failed on rather than restart at the beginning of the print job when there are form feeds in the application and changes to oprinfo. 1.0B This release introduced the GPx 240 and 27xx/37xx Communication and is needed if motherboard, part number 916556-004, is installed in a GPx 440. This motherboard will cause a PANIC if installed with 1.0A. 1.0A First release of BOSS/VX. It was required for the GPx 340 and 440. 3.0 NEW SOFTWARE ITEMS 3.1 /etc/dct file 3.1.1 Copying the /etc/dct file If the /etc/dct file has been customized it should be copied before upgrading to 1.1B because the customization could be lost. Below are the staps to copy the file: mkdct -x - -f /etc/dctlive.asc The mkdct command above will put the dct parameters in a file that will not be deleted by the O/S update. After the update has been performed /etc/dctlive.asc can be displayed and any changes there can be put into the new dct file. 3.1.2 Updating the /etc/dct file When a system is upgraded to 1.1B, a new dct file MUST be installed. The Upgrade procedure from tape will prompt as follows: ______________________________________________________ | Install the DCT file (y/n)? =N: | |______________________________________________________| If 'y' is entered the new file will be installed. If 'n' or is entered the following message will display: _______________________________________________________________ | Your DCT file is no longer system compatible. | | DCT file will be automatically updated and old files saved as:| | /etc/dctxx and /etc/dct.ascxx | | Enter Return to continue: | |_______________________________________________________________| If your new dct file needs customization the operator will be able to display the /etc/dct.ascxx to see the parameter values . used on the previous O/S. The 'xx' is a number generated by the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB049 Pg002 upgrade, it will be different for each system. 3.2 configdct changes The 'configdct' utility now has an option for number of LAN ports. This option is for the number of users connected via terminal servers amd/or direct connected via LAN. Enter only the number of ports that will have actual users, not the total number of ports available, because the dct parameters will be calculated according to this number and should not be overconfigured. The menu will appear as below; Option 6 is for LAN ports: ______________________________________________________________ | The following parameters are configurable: | | Option curr value range | | [1] Number of system buffers 1000 200-4000 | | [2] Number of inodes 900 100-4556 | | [3] Number of System V inodes 900 100-4556 | | [4] Number of open files 900 100-4556 | | [5] Number of processes 200 50- 600 | | [6] Number of LAN ports 16 0- 64 | | [7] Verbose kernal messages 0 0- 1 | | [8] Exit, writing DCT file | | [9] Exit, without writing DCT file | | | | Enter selection: | |______________________________________________________________| 3.3 floppy command Operation of the floppy drive is prohibited on systems with more than 16MB of memory. The 'floppy' command is used on such systems to allow floppy operation by reconfiguring system memory down to 16MB and rebooting the system. The 'floppy' command can be used to turn on, turn off or display the status of the floppy drive; status being enabled or disabled. NOTE: 'floppy' MUST be executed by root and should be run from console and ALL OPERATORS SHOULD BE LOGGED OFF because a system shutdown will be executed. Below are some examples: Enter: floppy floppy acces is DISABLED will display To turn on floppy access: Enter: floppy on (from console logged in as root) WARNING: This command will shut down the system! OK to proceed (y/n)? Enter: y floppy access is ENABLED The system will proceed to shutdown and reboot in multi-user mode using ONLY 16MB of memory. NOTE: The 'floppy' command must be used to regain access of memory SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB049 Pg003 above 16MB. A shutdown and reboot will NOT allow access above 16MB after 'floppy on' has been used. When the system boots it looks at the /etc/default/boot file to determine the maximum amount of memory. The floppy command will link /etc/default/boot to /etc/default/boot16 or boot64 to turn on or off floppy drive access. The 'boot16' file allows floppy use, and the 'boot64' file does not. WARNING: The 'dosformat' command will NOT format a floppy diskette that has not been formatted. The diskette can be formatted with the UNIX format command, or on another UNIX or DOS machine. This must be done before it can be written to or formatted on a GPx Series 40. 3.4 'ldsysdump' COMMAND ENHANCEMENTS The 'ldsysdump' command has been enhanced to copy the UNIX kernal and the '/etc/crash' command to a GPx Series PANIC tape. These enhancements have also been made to the PANIC procedure. All three files may be needed to analyze a system PANIC. To restore all three files enter the following: ldsysdump This will restore the files with the following names into the current working directory: dmpDyydddThhmm is the PANIC file unxDyydddThhmm is the UNIX file craDyydddThhmm is the /etc/crash file The 'DyydddThhmm' portion of the file name is the date and time stamp assigned by ldsysdump. An operator may also name the PANIC file and the corresponding files when restoring files by using the '-d', '-u' and '-c' options. Enter the following: ldsysdump -d custdmp -u custunx -c custcrash After all three files have been restored the following steps are necessary to analyze a PANIC with the correct levels of UNIX and /etc/crash: ./craDyydddThhmm -d dmpDyydddThhmm -u unxDyydddThhmm or ./custcrash -d custdmp -u custunx 4.0 SWAP SPACE RECOMMENDATIONS The minimum swap space for the GPx Series 40 systems is 16MB. GPx 640's with greater than 16MB of memory, new installations and systems which are indicating that they are running out of swap space, should have the swap area size increased. If a GPx 640 is going to have more than 16MB of memory, it is recommended that the swap size be a minimum of 64MB. There are two methods for calculating the swap size. 1. Multiply the capacity of drive 0 by .12. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB049 Pg004 2. Multiply 2 times the amount of RAM. (Minimum amount of 64MB on GPx 640's with RAM>16MB.) Use the calculated swap size which is the greater of the two requirements. This formula can also be used on 3/440's with large capacity disk drives. NOTE: If a system with 16MB or less of RAM is running well with a swap size of 16MB, it is NOT NECESSARY to increase the swap size. 5.0 NOTES AND CAUTIONS WARNING: 1.1B is the minimum operating system level for the GPx 640 with EISA controllers, and greater than 16MB of memory. 1.1A cannot access above 16MB of memory. WARNING: For 640 systems ONLY: The floppy disk driver for the GPx Series 40 system will not work above 16MB of memory, therefore, if a GPx 640 has more than 16MB of RAM the command 'floppy' must be used to access the floppy drive. For more details refer to Section 3.3 NOTE: The PT-4201 can be connected to the parallel ports of the MFC card of the GPx 640 only. The PT-4201 will not run on the parallel ports of the GPx 240/340/440s. Make sure that the form assigned to the PT-4201 uses a translation table of 'S8'. WARNING: The recommended disk space needed for the swap partition has changed. It is not necessary to change existing systems, but new installations should follow the guidleines in Section 4.0. GPx 640s with greater than 16MB of memory should have a swap space of 64MB. 6.0 RELATED DOCUMENTATION MANUAL # TITLE -------- -------------------------------------------------- M8215 GPx Series 40 Installation and Maintenance Manual M8224 GPx Series 240 Installation and Maintenance MAnual M0186 GPx Series 40 Software Installation and Configuration Manual M0187 BOSS/VX System Administrator Guide M0188 BOSS/VX Reference Manual M0189 BOSS/VX User Guide M0190 BOSS/VX Diagnostics Manual for GPx Series 40 M0217 BOSS/VX Transportable Batch Communications (27xx/37xx) User Guide M0288 BFSINT Reference Manual M0053 Universal Printer Driver Reference Manual M0229 MT-4409 High Capacity Tape Drive User Guide M5163 MT-4405 (GCR) Tape Drive Installation and Operation Manual M0237 BOSS/VX 1.1B Update Manual ORIGINATOR: Dan Arteritano Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB049 Pg005 FIB 00050 MAI COMPANY CONFIDENTIAL 12/14/94 *** GPx 70 1.2A Release Notes and Cautions [ WPSF 782 ] *** Type: Informational Purpose: These Notes and Cautions are applicable to release level 1.2A for the GPx Series 70 Systems. I. NEW NOTES AND CAUTIONS FOR THE 1.2 RELEASE A. PRE-INSTALLATlON CAUTIONS 1. CAUTION: Required SSM firmware level The new SSM firmware (rev 2.0.1 I) is required for correct operation of the I.2A release and therefore must be installed as part of either an update or full installation. After updating the SSM firmware, the system must be shutdown to a level 0 and powered off and on for the new firmware to be loaded into the SSM. You could also use the `zap' command from the level 3 prompt (--->) to reload the SSM. The following is a sample of what `showcfg' should display if the proper level of SSM is installed: SSM 0 0 00000000 00.05.04 sysid=0x621 ver2.0.B 2. CAUTION: Changes to dct since 1.0A release When doing an update install from 1.0A to 1.2A you must request reinstallation of the dct. The default is "no", so you must respond "yes" to get the new dct values. dct installation is automatic during a full installation. Failure to update the dct may cause the system to hang later during boot. Updating from 1.1A to 1.2A does not require re-installation of the dct. Note: Make sure any custom changes made to the original dct file are identified before installing a new dct file. 3. CAUTION: More swap space may be required. BASIC on 1.2A requires an additional 4k per user. If the users swap space is below the minimum suggested size (2.5 times main memory), it may be necessary to increase it after installing 1.2A. Use `sar -r' to check freeswap to monitor this. Processes may be released by the Operating System if it runs out of swap space. 4. CAUTION: Root requires free space for updates. If an update to 1.2A is done and optional products such as LAN and TCP are installed, several versions of the UNIX kemal will be installed. If customer files are stored on the root partition, it is possible for the root to become full during the installation which can cause problems. There should be at least 5MB of free disk space on the root partition before the update is done. B. NETWORK COMMUNICATIONS NOTES AND CAUTIONS 1. NOTE: The Magnet product is not certified for GPx 70 1.2A and SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg001 should not be installed. 2. CAUTION: Problem with FTP `user' command Once logged into a remote system under `ftp' using the `user' command, further `user' commands will cause a disconnect. This should not pose a problem since once logged in there is no reason to execute another `user' command. 3. CAUTION: SSM internal modem problem There may be a problem using the internal modem (1dev/altcon) which is connected to the SSM. This occurs when the remote console is disabled and it is used as a separate login port. You can dial into the system, work, and logout but on a subsequent login attempt the port will be hung and will require a reboot of the system to clear. The problem is caused by a string of data which is sent by the modem when it disconnects. This does not occur with all modems but was observed most prevalent with Paradyne modems. The workaround, if this occurs, is either to use a modem other than Paradyne to connect to this port or dial into a modem that is connected to a serial port. This problem is fairly consistent with an individual modem but not necessarily with a particular manufacturer (i.e. Paradyne). C. PRINTER NOTES AND CAUTIONS 1. NOTE: The PDF for the Okidata Laser printer is called `okiled' in this release. 2. CAUTION: Use of slave printers may cause serial port hangs. The use of slave printers, as an output device for many of system utilities, can cause the port to hang. This may occur when using the slave printer from BASIC as well. The work-around for this problem is to use an async version of the . slave printer driver. To do this, you must edit the file `/etc/inittab' and specify the async version of the printer driver. A before and after example of the file is given below: Before: SAAJ:23:respawn:/usr/mbf/bin/upddaemon dev=L11 After: SAAJ:23:respawn:/usr/mbf/bin/upddaemon.asyn dev=L11 After these changes have been made, you should either reboot the system or kill the upddaemon process for the slave printer. D. BASIC NOTES AND CAUTIONS 1.CAUTION:Reading /dev/kmem Reading /dev/kmem through BASIC when logged in as the root user will crash the system. For example: OPEN(l,ISZ=16)"/dev/kmem" READRECORD(l)A$ This problem will not be fixed, since no BASIC user has any SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg002 need to access /dev/kmem. 2. CAUTION: Killing ghost tasks Killing a ghost task does not release its semaphore. UNIX does not free semaphores when the process that allocated them is killed. Try to avoid killing ghost tasks. Use RELEASE from BASIC instead. When this is not possible, the semaphore can be identified with the. `ipcs' command, and freed via `ipcrm -s '. E. DIAGNOSTIC NOTES AND CAUTIONS 1. NOTE: DEMON does not report drive ID The DEMON test for DCC drives does not report the failing drive ID. This test is actually a set of controller subtests, several of which access a disk unit to test controller/disk interface logic. These subtests access the first available disk but they do not test the disk itself This is why the error messages do not report the disk unit number. 2. NOTE: SSM 1/2" tape test aborts If subtest 2.6. I of the SSM 1/2" tape test (tg) detects an error, it will abort rather than continue looping (and generating further errors). 3. NOTE: DIVE disk formatter drive access problems There are occasions where the disk formatter (DIVE) cannot access an unformatted SCSI disk which is connected to the SCSI Bus Adapter. This can often be solved by using the DEMON VME SCSI Bus Adapter test (#1. Function Select) to issue a format unit command. 4. NOTE: SSM firmware boot problem The number "247" appears on the console screen during the system boot. This is sometimes seen by the boot firmware as a command. The following example was observed following the loading of the Level 3 firmware: SSM Firmware (Operational) version 2.0.11 ---> --->247 No commands match `247' The `help' command will give you a list of commands. ---> ---> This number is coming from the internal modem. The later versions of the firmware have changed the functionality of the console and remote ports. When the "REMOTE" is "ENABLED" then all the information messages displayed on the console screen are also sent to the remote port. The modem is apparently confused by the data stream and responds with the number "247". This condition may be prevented by placing the "REMOTE" key switch to "DISABLE" during system boot. If service personnel must observe the boot messages for diagnostic purposes then the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg003 "247" can be ignored. The boot process can be resumed by entering "bh" at the Level 3 prompt. 5. CAUTION: Disconnecting printer cable during PPC test Disconnecting the cable to a corfigured printer during the DEMON PPC test may result in an error and the need to reconfigure the printer. This is a situation caused by the hardware design. 6. NOTE: Maxtor I .6 GB drive mode sense parameters Following are the recommended critical mode sense parameter values for the Maxtor 1.6 Gigabyte SCSI disk drive. In order to ensure the proper operation of a system with a Maxtor P1-17 drive (the 1.6 Gigabyte SCSI drive), several fields located in the Page 1 and Page 3 (the Error Recover Parameters Page and the Format Parameters Page respectively) should be set to predetermined values. The following table lists the fields that need to be modified and their recommended values : Error Recovery Parameters Page FIELD VALUE (decimal) Write Reallocation Bit...................0 Read Reallocation Bit....................0 Transfer Block Bit.......................1 Read Continuous Bit......................0 Early Error Correction Bit...............0 Post Error Bit...........................1 Disable Transfer on Error Bit............0 Disable Correction Bit...................0 RetryCount...............................14 Format Parameters Page FIELD VALUE (decimal) Sectors per Track................101 Data Bytes per Physical Sector...512 The following steps should be taken in order to ensure that the above listed fields have the proper values : Step 1 - Boot DIVE. Step 2 - Select the "FORMAT" option Step 3 - Select the "NON-STANDARD FORMAT" option. Step 4 - Select the "EDIT MODE SENSE DATA" option. Step 5 - Change byte 14 to 24 hex, byte 15 to 0e hex and so on according to the following table : BYTE NUMBER VALUE 14........24 15........0e 50........00 51........65 52........02 53........00 Step 6- Select the "BEGIN FORMATTING THE DISK" option. The disk will now be formatted with the correct mode SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg004 sense values. F. MISCELLANEOUS NOTES AND CAUTIONS 1. CAUTION: Mail program problem The `mail' program does not send to names which include a period (e.g. aaa.bbb). To circumvent this problem, place a backslash before the period and enclose the name in single quotes (e.g. `aaa\.bbb'). II. NOTES AND CAUTIONS CARRIED FORWARD FROM THE 1.1A RELEASE The following Notes and Cautions were reported in the 1.1A release and still apply to the 1.2A release. 1. NOTE: Simplified installation procedure Changes were made between 1.0A and 1.1A to simplify the installation procedure. For typical update and full installations, this simplification eliminates all of the device specific boot commands previously required. Changes were also made to the SSM firmware to support an "install" command which presents a menu and also eliminates several of the install steps. To take advantage of this feature, the SSM firmware must be updated first. To do this, boot the existing miniroot, insert the new 1.2A release tape and run the ./INSTALL program. Select the "S" option to install the new SSM firmware and then shutdown the system, first to operation firmware and then to poweroff or perform the "zap" SSM command to execute the new firmware. Once the system has rebooted to the operational firmware level (prompt: --->), enter "install" and answer the prompts of the menus. 2. NOTE: Newdct command - mkdct There is a new dct command called newdct which will give a better estimation of system resource requirements based on more information than was previously available. See appendix B for a complete description. NOTE: If the currently installed dct has been customized, these modifications should be integrated into the new dct files. Since the dct files may change from release to release, it is not correct to carry an existing ascii file forward or to use an ascii file created from the currently running kernel. If the actual customizations are not known, they may be determined by comparing the currently running dct (mkdct -x -) to the ascii file for the current memory size (e.g. dct32.asc). 3. CAUTION: File name changes There are initialization files that residein the rc0.d and rc2.d directories which have had name changes between the 1.0A release and the 1.1A release. For proper operation of the system, the old files must be eliminated so that there are not duplicate files. However, an update install normally doesn't delete files. In addition, some of these files may be modified by the administrator of a site to customize the initialization of the system. Therefore, the installation process creates a directory called v1.0a in each of the affected directories and moves each of the files that will be deleted by the installation into the new directory. A warning is then displayed on the screen to alert the installer that any SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg005 customization done previously to these files must be done again to the new files (with their new filenames). There are 4 files which have been changed since the initial beta release of 1.1A and require special installation handling. These files exist in the /etc/rc2.d directory and, because the default list of files to retain from the previous release includes these files, the update install will overwrite the new files. The files are: /etc/rc2.d/S25savecore /etc/rc2.d/S30autoconfig /etc/rc2.d/S87initbd /etc/rc2.d/S90disable.ports If any of these files have been modified or customized by the user, those files should be renamed prior to the update installation and the changes merged into the new files after the installation. If the files have not been customized they may simply be deleted prior to the installation. 4. CAUTION: ISCC board installation The 1.1A release introduced the Synchronous Communications Controller (ISCC) to support 2780/3870 Transportable Batch Communications (TBC). At this time, only one ISCC board may be installed on the system and only 1 of its 4 ports may be used. More information regarding TBC is included in a separate section following the Ethernet notes. 5. CAUTION: Large configuration performance issues Irregular performance has been observed when running very large configurations. When other potential reasons for performance problems have been eliminated (for example, 1/0 bandwidth, disk balance, streams buffer allocation, etc.), check for swapping activity. A small amount of free memory (obtamed from sar -r under "freemem") is one indication of swapping activity. The amount of freemem should stay above 70. Another indication of swapping is the swap queue size (obtained from sar -q under "swpq-sz"). When no swapping is taking place, swpq-sz will not display any value; values larger than two are reason for concern. A third indication of swapping is the number of swaps per second which can be obtained from sar -w. If swapping is taking place, the solution is to add additional swap space using the swap command (see the manpage). It appears that spreading the swap space out over additional disks may be as important as the amount of swap space in some circumstances. 6. NOTE: The 4315 terminal is supported on this release with the 4314 terminfo file. 7. CAUTION: Dropped characters on terminals The internal firmware of the 4313 and 4314 terminals is configured by default to have uni-directional X-on/X-off flow control; this generally occurs when the terminals are powered on. If you notice characters dropped (especially during heavy 16-way usage, and possibly during "transmit screen" operations), the terminal should be reconfigured for bidirectional X-on/X-off flow control. 8. NOTE: Change in BASIC device name ranges SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg006 Terminal and slave printer names are assigned in the range 0..999 (e.g. TO - T999; LO - L999). In previous releases, if a BASIC open of a file in this range was attempted and there was no configured port with the given device name, then the file was assumed to be a disk file. Now, all files within this range will be assumed to be device names. Therefore, it will not be possible to access a disk file in that range unless the fully specified path name of the disk file is given. 9. NOTE: Changes to dump command The /etc/dump command for backing up filesystems supports several new devices and has a new parameter, "C" for capacity, which simplifies the specification of tape size and density. See appendix C for more information. 10. NOTE: Configuring multiple 1/2" tape drives In order to use more than one 1/2" tape drive (including 8mm drives) with corresponding logical names, you must manually edit the file /etc/bfsdevs to add the new devices. By default, the logical names R0 and R1 are assigned for the non-rewind and rewind versions of the first 1/2" tape drive, tg0: R0:/dev/rmt/tg0n:: R1:/dev/rmt/tg0:: Additional drives should be numbered in a like manner: R2:/dev/rmt/tg1n:: R3:/dev/rmt/tg1:: R4:/dev/rmt/vg5:: 11. CAUTION:Problems with ATT define in C programs When compiling C programs on the GPx70 systems, the define flag ATT should not be set since using this define will require some include files which are only available on the Unix System V based GPx40 series systems. To undefine the ATT fiag, remove the -DATT option from the compiler . option list (normally under the CFLAGS define in the Makefiles). Also, if using the bfs library, you must also use the seq library. 12. NOTE: ALBautomatic log file switching The Auditor's Logbook feature provides for automatic switching of log files when the primary log file fills up. At present, there is no support for manually switching the log files while the primary file is in use. 13. CAUTION: ALB with BASIC INITFILE When the BASIC INITFILE directive is used on a file that has Audit logging enabled, two entries will be made in the log. The first entry will record an erase ("E") of the old file; the second entry records the initfile ("I"). 14. NOTE: New bbmap program A new program, bbmap, maps physical disk block numbers to the corresponding areas on disk and, if possible, identifies the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg007 affected files by name. This program works correctly in most instances. However, there are two known problems: o Some sectors are in a range which bbmap does not understand and will report a garbage file name. Known sectors with this problem are 22023 and 22024. o bbmap will not work correctly on systems with SMD disks (device name: /dev/dsk/zd#). bbmap will confuse partitions of the wd and zd disks. For example, when bbmap is invoked with device wd0 it may return information about zd0. The failure will be easy to recognize because the filename reported will not exist on the device requested. As a result, bbmap SHOULD NOT BE USED on systems with SMD disks. 15. CAUTION: Problems with GCR 1/2" tape drive Two problems have been identified regarding the GCR 1/2" tape drive. o CAUTION: Turning off the power to the GCR while the system is running and the GCR is in use can hang the system. A hardware ECN that fixes this problem has been received but it is not production released. o NOTE: The GCR tape may hang when running certain patterns of short 1/0 reads and writes to the tape. This problem has only been seen when running NITRO. Should this occur, pressing on the GCR will usually clear the hang condition sufficiently such that the system can be shut down and rebooted. 16. CAUTION: Stopping multi-page print jobs After using pqueue to stop a multi-page print job in the middle, a restart will cause the job to resume printing at page 1, not at the page at which printing was stopped. To work around this problem, use the lpmaint command to specify the beginning page number when instructing the spooler to resume printing: lpmaint job# begin=n -resume wherejob# is replaced with the spooler job number and n is the beginning page number. This technique will not work for jobs printed in raw mode. 17. CAUTION: Missing configured SSM DataProducts printers If the printer port of the SSM is configured as a DataProducts printer but there is no printer connected to the port, the system will continually poll the printer port for a response during the next boot cycle. Symptoms include reduced performance and a steady indication of processor usage on the front panel even if no other work is being done on the system. Work arounds are to (1) plug the printer cable back in or (2) if no printer exists, deconfigure the port and reboot the system. If the cable falls out after the boot the problem will manifest itself when a job is submitted to that printer. Again, the problem may be resolved by plugging the cable back in. 18. CAUTION: Using sdate to change date format The sdate utility will not change the date format as it is supposed to if it is invoked directly from the command line or shell. If SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg008 sdate is invoked by entering the menu system it will change the date format as expected. A. ETHERNET/LAN NOTES AND CAUTIONS FOR 1.1A 1. A major new feature available on this release is the Ethernet Lan communications protocol called TCP/IP. It is installed during the product installation phase by running mbfinstall. Two products are required, LAN and TCP. Additional information is requested of the operator during the installation. A full description of the installation procedure is attached as appendix D. Once these products are installed it is essential to reboot the system to switch over to the new kernel which has just been installed. CAUTION: YOU MUST SHUTDOWN TO LEVEL 0 and reboot after installation of the TCP product, 2. Documentation for the Ethernet Lan subsystem includes: TCP/IP: M0236A - MAI-NET TCP/IP User Guide for the GPx 70 SMB: M0222 - MAI-NET SMB Server User Guide Terminal Server: M0219 - MAI-NET Terminal Server User Guide, M0221 - MAI-NET Terminal Server Network Administrator's Guide, M0225 - MAI-NET Terminal Server Hardware Installation Guide 3. The rwho daemon WILL be supported for the FCS release of 1.1A. However, the rwho command will display only GPx Series 70 machines. GPx Series 40 machines use a different address protocol which is not recognized by the GPx 70 operating system. This restriction in no way limits the ability to use other TCP/IP functions such as rcp and rlogin. 4. When accessing a GPx 70 from a terminal connected to a terminal server there is a possibility that characters typed and intended for the application may be intercepted by the terminal server. Keys likely to have this problem include the programmable function keys, motor bar keys (MB-I IV), and combinations of the CTRL key plus another key or keys. If any of these keys match the five or so control codes configured for use by the terminal server they will be trapped by the terminal server and not passed on to the host. The workaround is to set the terminal server control codes using the Unix stty command or the Network Administration (NA) "set port" command, so that they do not match any control codes you intend to pass to the host. The Control codes are: - Input start/stop characters - Output start/stop characters - Attention character - Telnet escape character - Erase character/word/line characters See the man page for stty(1) or the NA Guide (M0221) for more information. 5. Macros defined in the /usr/spool/erpcd/bfs/macros file are not recognized by the terminal server. 6. The rtelnet command is not supported in the 1.1A release. Also, the `start' command cannot start up tasks on terminals connected via SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg009 terminal servers. 7. Normally, when accessing a host GPx70 system from a terminal server, the terminal device name (e.g. /dev/tty/XA/XAAF) and the b-device name,(e.g. T34l) will be assigned randomly. There is a mechanism for establishing static tty names using telnet and a user-provided file, /etc/remote.in. This feature is documented in the BOSS/VX Release 1.1A Update Manual (M0237) and will also be documented in the Software Announcement. 8. Slave printers may be connected to terminals which are connected to terminal servers and may be accessed from the terminals to which they are attached. However, slave printers on remote terminals may not be accessed from other terminals or tasks. B. TBC NOTES & CAUTIONS FROM 1.1A 1. Systems with configurations of 75 terminals/ghosts or greater will experience problems with BCOMPFX. BCOMPFX prints the header information then aborts with no error messages. Change statements 2020/2025 and set MAXTERM/MAXGHOST=512. 2. TBC should run on port 0 of the ISCC board only. No other ports are supported. 3. Only one ISCC board is supported on each GPx 70 system. 4. The maximum supported baud rate on GPx 70 is 9600. 5. If the user wants to use BQR utilities to create TBC transmit queues or to convert received files, the "ITP" product must be installed also during "mbfinstall". 6. When an incorrect TBC public key is installed, a system error -657 and a BASIC error 59 may be returned during opening the TBC Comm port. 7. When the ISCC controller board is hung, please do the following steps to bring the controller back: (1) The task that is running BCOM must exit from BASIC. (2) cd /usr/mbf/comm (3) ./commload -b0 (4) Check to see if the load is successful. (5) If the load is not successful or the controller remains hung,. the user must shutdown and power off and on the system. 8. BCOM may report open errors in LSLOG. BCOM will retry the session, and this error will not affect the user. 9. Without sufficient disk space in the root partition, TBC may report BASIC error 95 with system error -614 "Unknown I-Device open error" at the OPEN command. Atter resolving the disk space problem, perform "kill -2 pidnum" where pidnum is the process id of the tbcstub. 10. If the line is kept active by sending/receiving temporary text delays or continuous WACK conditions without actually sending data blocks for an extended amount of time (one hour) the local TBC task may "hang" for 5 or 10 hours before posting a "CONTROLLER PORT BUSY" error. If this situation occurs, the user can any time before or after the error message is posted to terminate the session. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg010 11. TBC may report an error 26 during a file transfer in transparent mode from GPx to SPx systems. The following programs need to be changed on SPx systems: Program /tbc/BCOM/BRCV: 1456 IF T2=1 TIlEN GOTO 1525 12. TBC treats valid termination sequence ETX/DLE-EOT as abnormal. 13. A "TIMEOUT TERMINATION" may occur without actually waiting for the length of time specified in the TIMEOUT value. This will cause a premature termination of a TBC session. 14. A device T000 present in the /etc/bfsdevs file can cause BCOM screen display problems. This T000 device should be removed from the file. 15. TBC may report "ENQ RETRIES EXCEEDED" error in LSLOG during TBC communications with a heavily loaded system. 16. Due to a timing problem when closing the I ports, TBC may report a "RETRY RECOVERY" error in the LSLOG. This should not affect TBC operation. 17. BCOM fails to Auto-Restart after reporting "TERMINATING FILE XFER DUE TO RECEIVER" error in the LSLOG. 18. Wrong error message was reported when saving the receive queue with the name "DEFAULT". We recommend that the user not save the receive queue with the name "DEFAULT". 19. When modifying a TBC transmit queue for file transfer, the user needs to enter the full path name for the destination file name. 20. BCOM incorrectly bids for the line instead of re-dialing when the connection has not been established (such as line busy) during the autodial operation. III. NOTES AND CAUTIONS CARRIED FORWARD FROM THE RELEASE The following Notes & Cautions were reported in the 1.0A release and still apply to the 1.2A release. 1. The internal modem on the GPx 70 must be initialized when it is first installed. Normally this is done in the factory, but if a modern has to be replaced in the field, it must be initialized at that time. To initialize the modern, use the DEMON menu option provided for this purpose. 2. The operating system installation procedure (either full or update) should be allowed to complete without interruption. If the process does not complete due to tape errors or operator intervention, restart the installation from the beginning. 3. A large number of terminal definition files exist to describe various default mode settings for the 4313, 4314 and 4315 terminals. The standard terminal definition, dt4313, defines a terminal that has black letters on a white background in a 24 x 80 format. Other terminal definition files describe optional features such as 35 x 120 compressed format. The desired terminal definition file should be specified as the "TERM=" value at login. The file: /usr/lib/terminfo/mbf.ti SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg011 contains descriptions of all the variants. 4. The vi editor will flash the screen when an erroneous command is given. If this causes the screen mode to change from white letters on black background to black on white, it is because the video mode of the terminal does not match the TERM type entered at login. If white on black format is desired, the TERM value should be dt43l4-rv. 5. "C" programs which are called from Business BASIC programs should be relinked whenever a new BASIC is installed (as part of a full or update installation). 6. The installation process automatically establishes a partitioning of the primary disk that allocates a swap partition that is 2.5 times as large as the physical memory on the system. This ratio has. proven to be a minimal but safe allocation. 7. The capacity of disks indicated in the Installation Procedures Document or refer to megabytes which are 10^6(million), not 2^10(1024*1024). 8. The sizes of the file systems and swap partitions are dependent on system memory size and disk type. The root, usr, and miniroot partitions are the same size on all systems. The other partitions vary in size. Fixed partitions, regardless of system memory size: root partition: 33 MB usr partition: 97 MB miniroot partition: 8 MB Systems with 8 or 16 MB: swap partition: 52 MB Systems with 24 or 32 MB: swap partition: 80 MB For larger configurations the swap partition size is set to 2.5 times the physical memory size (rounded up to the nearest 16 MB). The remainder of the primary disk is allocated to the usr2 partition. 9. Partitioning of additional disks is facilitated by the diskadd utility. This utility may be run from single- or multi-user mode. See the man page for more information. 10. The overhead associated with each partition may be modified either when a file system is created on the partition (with newfs) or dynamically after the file system has been created (with tunefs). Read the manpages for these commands, specifically the -i option in newfs and the -m option in tunefs. 11. The UNIX printer services are also included in the release. The status command for UNIX is the same as the one for MBF `lpstat'. If you just type lpstat you will get the UNIX command and not the MBF command. You can either move the UNIX command or use the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg012 extended path name for the MBF command, i.e. `/usr/mbf/bin/lpstat', or change the search path in your environment variable PATH. 12. The system console is not intended to be a data entry device. In general, it should be reserved for operator functions and to record. system messages. Specifically, applications that require the use of Ctl-p should not be run on the system console. 13. A change has been made to allow the dynamic configuration value BUFPCT to be set to 90 percent (old limit was 50 percent). Increasing BUFPCT to a value higher than 50% may increase performance of I/O intensive tasks that do not require a large number of processes. However, running a large number of interactive tasks with a BUFPCT value of greater than 50% may cause excessive swapping and a resultant loss of performance. 14. The mbf_errlog utility may be used to display recent device errors. Additional functions are also available - see the manpage for more details. IV. GPX 40/70 DIFFERENCES General Notes 1. Device Names: o. Tape drives: /dev/rmt/tm0.......1/4" tape drive Note: /dev/tape and /dev/tp link to this device /dev/rmt/tm0n......1/4" tape drive, no rewind device Note: /dev/tpnr links to this device /dev/rmt/tg0.......1/2" tape drive Note: This device can be 1/2" GCR, 1/2" MTS or 8mm HCC /dev/rmt/tg0h......1/2" tape drive, high density o Disk drives: /dev/dsk/wd0s0...SCSI disk 0, partition 0 /dev/dsk/vd0s0...VME SCSI disk 0,... o Printers: /dev/printer/wp0...parallel printer o The console is called syscon o tty01 is called altcon 2. Up to sixteen 16-ways are supported. 3. The serial devices are split ihto 4 subdirectories: /dev/ttyXA, /dev/ttyXB, /dev/ttyXC, /dev/ttyXD. 4. The mt program is located in the /etc directory rather than the /bin directory as in GPx40. 5. Both Centronics and DataProducts parallel printers are supported on both the SSM and PPC parallel printer ports. 6. GPx70 does not support the t* utilities (tsave, trestore, tcompare, SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg013 etc.). 7. GPx70 file names may be 255/256 characters long. GPx40 has a 14 character limit. V. GENERIC GPx NOTES AND CAUTIONS 1. NOTE: Difference between SPx and GPx: a ^D will not abort the login sequence on GPx as it does on SPx, although a will. This is to preserve UNIX compatibility on GPx 2. NOTE: oprinfo will not allow usemames which are all uppercase. This is because if login sees an all uppercase usemame, login will force the login session to use all uppercase letters.(aka, stty olcuc.) This semantic is a historical relic from the days where teletypes only had uppercase. So, use oprinfo and lowercase user names to by-pass the problem entirely. 3. NOTE: While at the shell prompt, if you enter characters, then enter escape, backspace, backspace to remove characters on the screen, you will lose a character. For example, typing in configure will appear as `configure' on the screen, but the system will actually see 'confiure'. 4. NOTE: If a UNIX command which is issued to the shell using variable or filename substitution, such as cp, gives an `Arg list too long' error when full path names are used, use xargs to shorten the list. For example: cp /usr/mbf/atp/isys/* /usr2/PGM/WEEKDAY can generate the error if there are a substantial number of files in the /usr/mbf/atp/isys directory. Instead, do the following: ls /usr/mbf/atp/isys/* | xargs -i -t cp {} /usr2/PGM/WEEKDAY For turther details, see `man xargs'. 5. NOTE: The ATTR tunction in BASIC will return SORT files as DIRECT files with 0 record length. 6. NOTE: In order to have full access to and utilization of the online man (manual) pages, the MBFMAN and UMAN products must be installed. 7. NOTE: There are certain times that a UNIX shell will be running in "sane" mode. (aka, stty sane; also, stty ek.) While in "sane" mode, the tty device will be configured to use the number sign (i.e. "#") for backspace and the at sign (i.e. "*") for line kill. Sane mode is another feature based historically on the teletype, and is typically used during password entry. 8. NOTE: The UNIX System V filesystem (as well as UNIX/BSD) fragments files, and with normal usage, the system performance, will suffer from fragmentation. For example, file (system) backups times will increase with increasing file system disorder. (For further reading, try Bell Labs Technical Journal, July/Aug `78, "UNIX Implementation," K. Thompson.) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg014 To reduce the fragmentation of files and free space use the dump/newfs/restore sequence to create a filesystem ofcontiguous files. Contiguous files will result after: a. full filesystem backup. b. newfs to erase and re-create the volume. c. full restore to the erased volume. BUT, as files are subsequently re-written, created, and destroyed, the file system again becomes fragmented, and tape backup performance will degrade. 9. CAUTION: If a tape drive is used to access a tape which is physically damaged, it may cause the drive to go into an error state. To recover from this error state, the drive must be powered down and then powered back up. To do this safely, the system must be shutdown and powered down and then back up. Unpredictable results may occur if the tape drive has its power cycled while the machine is up. 10. When a serial file is created on GPx using cread the maximum number of records is automatically set to 0, which tells the GPx file system that the file can grow without limit. This is incompatible with the MPx file system, and will result in an error message when the files are transported from GPx to MPx. If the user wishes to move these files to MPx he should first run fchange and modify the Max. records parameter (e.g., to match the actual number of records) before saving the file via cwrite. VI. GENERAL PRINTER NOTES 1. NOTE: The ISP PDF does not support pitch or lpi in forms. 2. NOTE: The Pstatus utility does not reinitialize the page count when the job is interrupted and restarted. A. GENERAL SLAVE PRINTER NOTES 1. If you are using a 4313 terminal the firmware must be Rev. E or higher. 2. If you are using a 4314 terminal the firmware must be Rev. L or higher. 3. If a slave printer goes offline while printing, and the data to be printed fits in the terminal buffer (128 for 4313 and 1024 for the 4314) no error is issued. The user must manually reset the terminal or turn on the printer. 4. When using a slave printer, the terminal should be configured for bidirectional software (XOFF/XON) flow control. The printer port on the terminal and the printer should be conflgured for DTR/CTS flow control. 5. On a write timeout to a slave printer, 3 ESCAPE B's are written by upd to the port. This sequence resets the terminal. For 4313's it causes the screen to flash and the function key settings to be lost. It is necessary to do this to get the terminal out of bypass mode so that an error message can be written to the terminal. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg015 This will only happen if the terminal is configured for software flow control, as recommended above. Hardware flow control is not recommended for terminals with slave printers. If the terminal is configured for DTR/CTS flow control, the 3 ESCAPE B's will not be written to the terminal because CTS is low and this cannot be overridden as we do for the XOFF condition. This may result in data printed on the printer that was not intended to go to the printer. 6. If the printer port on the terminal is configured for XOFF/XON flow control, data could be lost after a printer timeout. This is because the terminal has been reset and will start sending data to the printer even though the printer has not sent an XON. With DTR/CTS flow control, the terminal will still recognize the CTS low condition as a signal not to send data. 7. NOTE: If a slave printer is opened from a ghost, and the ghost is released from another process, then the terminal modes may be improperly set. This will not happen if the ghost releases itself. VII. GENERAL DIAGNOSTIC NOTES AND CAUTIONS 1. When DIVE is performing a format or a surface analysis the system should not be powered down to exit either of these operations. Doing so will destroy the format on the drive and render the drive un-usable. 2. The 1/4" MCS tests 3.8 and 3.9 fail. The problem is under investigation. 3. The off-line DIVE program is file number 30 on the diagnostic tape. 4. The DEMON diagnostic displays the time it reads from the hardware. This is "UTC" time and not the local time. Do not change the time with DEMON as this will cause the OS time to be incorrect when the OS is rebooted. 5. In the multiple 16-way interaction test of DEMON, the "output a ripple pattern" to 43xx terminals will fail when run with loopback cables. 6. CAUTION: Some of the DEMON disk tests can write over the entire disk surface, including the file system areas. These tests must be manually selected since they are not in the default selections. Do not select any of the non-default disk tests if the disk being tested has customer data on it. Please read user documentation before using the DEMON diagnostic. 7. When testing the Parallel Printer Controller with DEMON, if an error occurs it is necessary to reconfigure the printer with option 5 (configure printer). 8. If the DEMON Ethernet Controller test is run immediately following the DEMON VME 16-way Interaction test the following error will be reported: eg 6.2.1, error number 108, pass 0 Failing unit: EG 0X5000 on VME 0 on SSM (slot0, SLIC 0) VMEbus BERR interrupt detected The Ethernet Controller board may be tested by running the test by itself. If errors are reported when the Ethernet Controller is run SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg016 alone then the hardware may have an actual failure. VIII. BASIC NOTES AND CAUTIONS 1. CAUTION: BASIC sometimes ignores Escapes when executing in very tight loops. 2. CAUTION: Executing a system command from BASIC reports a non-zero exit status code as a system error. 3. NOTE: There is a difference between `start' and `START'. `start' is a stand alone program to start a task on another terminal. Such a task is terminated by release'. `START' is a BASIC directive which starts a ghost task. A ghost task is terminated by `QUIT', `END', or `RELEASE'. IX. COMMUNICATIONS PRODUCTS NOTES AND CAUTIONS ATP 1. A BASIC program file transferred by ATP from a GPx system to a 1500 system will error on all multi-line statements at the receiving side. The workaround is to edit the BASIC program file on the 1500 system after file transfer. 2. The user must start ATP on an SPx system first during ATP modem connection between a GPx and a SPx. 3. An error 18 (Illegal operation) will be returned if an ATP user attempts to transfer a file to which he/she does not have write permission. 4. A STRING file with certain unprintable characters (between $00$ and $lF$) could be corrupted if the file was transferred via ATP from a BOSS/VX ystem to a BOSS/IX system. The workaround is to change the following programs on the BOSS/IX system: Program "ARP": 4205 IF F4<>7 THEN GOTO 4210 ELSE LET R9=0; IF S1=1 THEN WRITE RECORD (6,TBL=6900,ERR=4500)R0$(3,S9-2) ELSE WRITE RECORD (6,ERR=4500)R0$(3,S9-2) Program "ATP1": 5135 IF F4=7 THEN LET R9=0;READ RECORD (6,ERR=6000,END=5700) X9$; GOTO 5150 5. ATP will report errors when the user attempts to transfer files to systems which do not support the particular file types. 6. ATP can not be started on 2 terminals at the same time. 7. Using ATP to transfer a string file to a system that does not support string files will cause the BOSS/VX system to skip the string file and the destination system to report "Invalid receive file type". 8. String files will be changed into Serial files on a BOSS/VS system which has OS version M.6G or later when the String files are transferred via ATP to the BOSS/VS system. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg017 9. Using ATP to transfer a Multi-keyed file to a system that does not support Multi-Keyed files will cause the BOSS-VX system to skip the Multi-keyed file and the file that follows the Multi-keyed file. 10. Using ATP to transfer a Serial file to an MAI-1500 system, which does not support the Serial file type, will cause the BOSS/VX system to skip the Serial file. 11. When the user defines too many similar BQR filelist names, BQR may get confused about them and cause some of the filelists to be wiped out. We recommend not to define too many BQR filelists that have the same first three letters. 12. ATP Scheduler may report "IMPROPER ACCESS CODE" error sometimes even though the ATP Public Key is correct. 13. ATP Scheduler may skip files if NAKs occur between file transfers or during Line Turnaround. 14. Normal modem carrier drops (DCD) are reported in the mbf_errorlog. When the errorlog is filled, the message will be reported on Console. 15. When the ATP port reports "framing error", mbf_errorlog increments the port number every time the "framing error" was reported. 16. ATP may report a task hang situation during communication sessions between GPx 70 systems in scheduler mode or in batch mode. Reboot may be able to clear this problem. If the problem persists, the user should replace the 16-way controller involved in the communications. PC-LINK 1. PCLink on BOSS/VX does not support slave printer functionality nor Industry Standard Printers. 2. For PCLink file transfer operations between PC and BOSS/VX systems, the system type should be set to BOSS/IX for BOSS/VX. 3. The PCLink file transfer programs on BOSS/VX host systems must be in upper case characters. 4. The CAPS LOCK key is always set when connecting to a BOSS/VX system via PCLink. 5. To use "vi" via PCLink requires at least 4309 configuration at the connecting terminal port, and TEPM value must set to "falco" for GPx 70. 6 When running PCLink via Modem, Control-S will hang the PC port. To resume operation, please hang up the modem and re-dial. 7. at the "$" prompt will hang the PC for 30 seconds. APPENDIX A PROCEDURE TO CHANGE WORD SIZE AND PARITY ON SYSTEM CONSOLE AND ALTCON 1. Turn the remote console key on the front panel from disable to enable. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg018 2. Get into operational firmware mode by shutting down, booting or entering Ctl-p on the system console. The operational firmware prompts with --->. 3. With system console plugged into console port, enter the following commands. Note: In the next examples, "--->" is the prompt, and is followed by the command to be entered (e.g. "pr local"), after which are displayed the results of the operation. ---> prlocal baud=9600 stop= 1 size=8 parity =none flow=xoff ---> pr remote baud=9600 stop= 1 size=8 parity =none flow=xoff ---> remote size=7 ---> remote parity=odd ---> remote baud=2400 ---> pr remote baud=2400 stop= 1 size=7 parity =odd flow=xoff ---> remote console 4. Change setting on terminal to 7, 1, Odd, 2400 baud. 5. Move the console cable to the remote console plug on the GPx-70 6. With system console plugged into remote console port, enter the following commands: ---> pr local baud=9600 stop= 1 size=8 parity =none flow=xoff ---> local size=7 ---> local parity=odd --->prlocal baud=9600 stop= 1 size=7 parity =odd flow=xoff ---> pr remote baud=2400 stop 1 size=7 parity odd SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg019 flow=xoff ---> local console 7. Change the setting on the terminal back to 9600 baud. 8. Move console plug back to console port. 9. Done. If this process does not work, or if the console hangs: Note: Properly ground yourself when handling the SSM. 1) power-off the system 2) jumper the pins on the SSM board which reset the NV Ram 3) power-up the system 4) Repeat the process to change the console settings 5) Remove the SSM jumper. APPENDIX B HOW TO USE newdct FOR BETTER RESOURCE UTILIZATION During system installation the system sets up resource allocation limits (called the Dynamic Configuration Table or dct) based on the physical memory size of the system. The process of making the dct is automatic during a full install, optional during an update install and may also be run manually by the system administrator to tune the system parameters. A new tool, called newdct, was first provided in release 1.1A which produces a dct which more accurately reflects the configuration of the system. newdct can take as input information about the hardware configuration of the system, soflware package installation and user-specified system utilization information. Also provided in this release are the tools "prtcfg" and "packages" which will generate the hardware configuration information and the software package installation information. newdct should be run after all hardware has been installed, optional sofiware packages have been installed, and user accounts have been created. The system administrator (as super-user) should run prtcfg by itself to inspect the assumptions being used to configure the dct. If corrections are called for, the administrator should direct the output of prtcfg to a file and edit the file. Fields which may need correction include: slave (the number of slave printers reported by prtcfg is simply a calculation based on the number of terminals), users (prtcfg estimates this field from the passwd file, but if multiple people use one account then the estimate will be low), ghost (prtcfg also estimates this). The next step in tuning the dct is to feed the output of prtcfg (modified if necessary) and packages into the newdct program which will, in turn, output an ascii file (on standard out) which can be directed to the mkdct program. For example, to configure the dct taking into account the hardware and software configuration as well as user-provided information, do the following: prtcfg> ourconfig SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg020 packages> ourpackages vi ourconfig (to fine-tune the configuration) newdct -f ourconfig -f ourpackages mkdct -o /etc/dct -f - shutdown -i0 (make sure it's safe to reboot, of course) Other options are available for use with newdct. Please read the manpage for more information. After creating the new dct information and "installing" it with mkdct the system must be rebooted to allow the new dct values to take affect. APPENDIX C PARAMETERS TO USE WITH THE /etc/dump COMMAND Each row of the following table represents one permutation of tape device type, media size and density setting. Also indicated is the approximate capacity in MegaBytes (10^6). The dump utility now supports a new optional parameter (option "C") which may be used in lieu of the density and media size options. The density and size options are still supported. The C option, if specified, overrides the density and media size. Only the capacities listed may be used with the dump command. Each capacity is unique and corresponds to a specific device type, media size and density. Entering an invalid capacity will cause an error message to be displayed. For example, instead of typing: dump 0nufsd /dev/rmt/tg2h 3500 6250 /usr4 (meaning GCR tg2 with 3500 ft reel at high density) you may enter: dump 0nufC /dev/rmt/tg2h 240 /usr4 (meaning GCR tg2 with capacity 240 MBytes) Important notes: 1. If no device name is specified the default will be /dev/rmt/tg0h, with 2300 for media size and 6250 density. 2. Using dump 0uc /usr2, will set the device name to /dev/rmt/tm0, with. 9000 for media size and 1250 for density. 3. Any time a high density GCR (6250) is selected, a high density tape drive should be specified too (tg0h). 4. "f' option should be used with "C" or "d" and "s" options. The device name specified for the "f' option should be the full device name such as /dev/rmt/tm0 rather than link names such as /dev/tape. 5. "c" option cannot be used with "f" option. 6. The default setting for b option is set to 32, as opposed to 10 (old default), in both dump and restore. Any 1/4" cartridge tapes backed up with the old releases should now be restored with the b option set to 10. 7. To use dump for backing up multiple partitions, SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg021 a) Rewind the tape b) Dump with no rewind (dump 0ufC /dev/rmt/tg0hn...) c) Dump the next partition with no rewind 8. To restore a partition from a tape with multiple backups: a) Rewind the tape b) Bring the tape to the start of a particular partition (mt -f /dev/rmt/tg0hn fsf 1 ... for the second dump session on the tape) c) Run restore. Another way to do this is use the s option with restore command. Device Media Size Density Capacity Type (feet) (cpi) (MBytes) ------- ---------- -------- -------- 1/4" 5400 1000 60 1/4" 9000 1250 120(1) 1/4" 25000(2) 2000 525 GCR 1/2" 500 1600 11 GCR 1/2" 1100 1600 21 GCR 1/2" 2300 1600 41 (3) GCR 1/2" 3500 1600 61 GCR 1/2" 500 6250 40 GCR 1/2" 1100 6250 80 GCR 1/2" 2300 6250 160(4) GCR 1/2" 3500 6250 240 MTS 1/2" 500 1600 12 MTS 1/2" 1100 1600 22 MTS 1/2" 2300 1600 42 MTS 1/2" 3500 1600 62 HCC 8mm 19300(5) 5400 1100 HCC 8mm 38400(5) 5400 2200 (1) Default using c option. (2) This value is less than 1020*26, in order to account for ECC overhead in QIC-320 format. (3) This value of 41 instead of 40MB is used in order to differentiate 1600 cpi from 6250 cpi. This was done to avoid introducing another option for high/low density level. (4) Default. (5) This value is not the same as the physical length of the tape. This is due to Helical scan recording format. APPENDIX D INSTALLATION PROCEDURE FOR LAN and TCP on GPx 70 The Local Area Network and Transmission Control Protocol are released as products in the names LAN and TCP, respectively. Following is the installation procedure for LAN and TCP 1. Shutdown the system to single user mode and execute /etc/mbfinstall SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg022 2. Select products LAN and TCP respectively to install. NOTE: LAN should be installed before TCP. 3. During the installation, the system menu will prompt for the following information. Enter Local Area Network Controller installed 1. Eagle Ethernet Controller 2. SCED Ethernet Controller 3. Eagle and SCED Ethernet Controllers 4. None Enter : As of now, GPx 70 will support only the first one, i.e. Eagle Ethernet Controller, so enter choice as `1'. The menu will now prompt for How many Eagle Ethernet Controllers are configured? Enter the number of Controllers configured. The system menu will confirm and display another menu, which prompts for the Internet Address, for the different controllers configured. The Internet Address must be assigned by the System Administrator. 4. At the end of the TCP install, mbfinstall will prompt for the public key. This key must be obtained from MAl Systems Corp. 5. Shut the system down (to the operational firmware level or level 0) using the command "shutdown -i0 -g0 -y". CAUTION: Do NOT go directly to multi-user mode from single-user mode. To do so will cause devices to be deleted from the /dev directory. These must be recovered by performing the following steps: 1. Shutdown to level 0 2. bh `wd(0,8)unix -M -r wd0s8 -s wd0s8' 3. fsck -y /dev/rdsk/wd0s0 4. mount /dev/dsk/wd0s0 /mnt 5. cd /mnt/dev 6. ./MAKEDEV auto 7. cd/ 8. umount /mnt 9. fsck -y /dev/rdsk/wd0s2 10. fsck -y /dev/rdsk/wd0s3 11. init 0 12. 13. bh doOs ORIGINATOR: Dale Jensen MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB050 Pg023 FIB 00051 MAI COMPANY CONFIDENTIAL 11/23/92 *** Release 1.1C available for GPx 2/3/4/640 Systems *** BOSS/VX Dan Arteritano Release of 1.1C Operating System for GPx 2/3/4/640 Systems Type: Informational Purpose: To inform that 1.1C is available for shipment and bug fixes and enhancements. Enhancements: o 535MB SCSI disk drive support o D-Link Revision F support. The O/S stills supports earlier revision controllers, but if a revision F controller is installed in a system 1.1C MUST be installed. o On-Line Backup is now supported with "olb" using "cpio" with "Journaling". OLB works the same as OLB on the GPx 70. o Patch 46, WordPerfect 5.0 termdef files, Patch 49, error 958 in the spooler and Patch 53, TCP/IP fix all have been incorporated into the O/S. o "hpljet" and "okiled" are now options for configuration. Fixes: o pformchg can print a test pattern with live data containing @ signs o PT-4217/18 prints the last line of the job. o The assigned form in "Printer Control Defaults" will be loaded at boot time. o /tmp/.execsh#### files will be deleted. o INITFILE will not break filelinks. o "fuser" will return the operator of an OPENed file. o "frepair" will not exit if a file is unrepairable and will not shrink serial files when badly corrupted. o "cread" will restore all files from tape rather than have files with "NF" status in BQR. Market Codes for 1.1C for the GPx Series 40 Base Domestic W514129-214 1.1C*08 Base International W514129-215 1.1C*08 BOSS/VX Diagnostics W514751-210 BASS 1.1B*03 DIVE 1.1C*01 SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB051 Pg001 DEMON 1.1C*2.01 WTR 1.1A*08 CDEV W514764-210 1.1C*08 Configuration Record W514129-101 ORIGIN 2.1B*26 W514941-054 Presentation Services W514749-034 ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB051 Pg002 FIB 00052 MAI COMPANY CONFIDENTIAL 12/28/92 *** ERR -307 attempting to use any MBF utility *** SYMPTOM: ERR -307 when attempting to use any MBF utility. PROBLEM DETERMINATION: Only "root" can log-in to the system. FIX: There is a problem with the /tmp directory or filesystem. If there is a /tmp filesystem you will have to delete the files manually, a few at a time due to excessive files in the root directory of the /tmp filesystem. Reboot after all the files are deleted. The /tmp filesystem is unmounted at the time /tmp is cleaned-up during boot. The customer will have to delete these files regularly and reboot to prevent this problem from re-ocurring. ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB052 Pg001 FIB 00053 MAI COMPANY CONFIDENTIAL 12/30/92 *** 1/2" tape BASIC READ command requires SIZ= at 1.1C/1.2A [WPS 807] *** BOSS/VX 1.1C-40 and 1.2A-70 Dan Arteritano 1/93 807 1/2" Tape READ Requires SIZ= with Tape Block Larger than 1024 Bytes Type: Informational Purpose: To warn that a SIZ= clause must be used when READing a tape block larger than 1024 bytes from 1/2" tape with BOSS/VX 1.1C. Earlier versions allowed a variable to be dimensioned for the size of the record. Below are examples of the old and new methods of reading: OLD: 10 OPEN(1)"/dev/gt0" (/dev/rmt/gt1 for GPx 70) 20 DIM A$(2000) 30 READRECORD(1)A$ NEW: 10 OPEN(1)"/dev/gt0" 20 READRECORD (1,SIZ=2010)A$ Note that the SIZ= can be larger than the tape block and still read tape blocks within the specified SIZ. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB053 Pg001 FIB 00054 MAI COMPANY CONFIDENTIAL 01/20/93 *** Release 1.1C Software Announcement for GPx Series 40 [ WPSS 202 ] *** Level 1.1C of BOSS/VX for the GPx Series 40 computer systems is now available. This Operating System is derived from the 1.1B O/S and contains the capability . to use 535 MB disk drives and the Revision F D-Link controller. Also included in this release are Patches 46 (Wordperfect 5.0 termdef files), 49 (despooler lpd . fix) and 53 (TCP/IP). This Software Announcement contains general information about the 1.1C BOSS/VX Operating System. Installation and update procedures can be found in the GPx Series 40 1.1A Software Announcement, #191 (FIB 35). It is recommended that this document and the 1.1A Software Announcement, #191 (FIB 35) be read before installing 1.1C. For information on ordering 1.1C refer to Marketing Announcement 1140. TABLE OF CONTENTS 1.0 BOSS/VX Operating System History 2.0 Enhancements 3.0 Performing On-Line Backup 1.0 BOSS/VX Operating System History 1.1B Added the capability to access above 16 MB of memory in the GPx 640. 1.1A Was the minimum release for the GPx 640. New features were Errorlog Watcher, TPS Product on the O/S tape, On-Line Configure Utility, UPD Simple Compiler, Enhanced NMI and UPS support and up to 128 user connectivity on the GPx 640. 1.0D Contained PS 3.3B, which had enhancements and corrections to PS 3.3A. There was also a fix for an Enf-of-Media problem on the HCC tape drive and the 1/2" tape drive. 1.0C This release introduced the 1/2" MTS tape drive, Ethernet controller, 670 MB disk drive, 64 user connectivity, DOS read/write capabilities, PT4220 serial printer, slave printing on DT-4213, TERMCAPS and TERMINFO files on the DT-4312 and DT-4309, displaying dashes when Security Violation PANICS occur, the addition of lphold, printversion and bbmap commands. There were a number of bug fixes/enhancements including automatic shutdown when the UPS becomes active, changes to oprinfo, and the spooler will only reprint the page it failed on rather than restart at the beginning of the job when a printer time out occurs on a print job that has form feeds. 1.0B This release introduced the GPx 240 and 27xx/37xx Communications and is needed if motherboard P/N 916556-004 is installed in a GPx 3/440. This. motherboard will cause a PANIC if installed with 1.0A. 1.0A First release of BOSS/VX. Required for the GPx 3/440 systems. 2.0 Enhancements Operating System: ________________ SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB054 Pg001 D-Link controller - Revision F is the latest version of the controller and the only version now available from the manufacturer. Because of this, the new driver required for the Rev F controller has been incorporated into the 1.1C Operating System. 535 MB disk drive is now available for the GPx Series 40. To format the drive a new version of DIVE must be ordered. Patch 46 - Correction to the TPS Product which fixed the Wordperfect terminal definition files for the DT-4315, specifically for the F1 through F4 function keys. Patch 53 - TCP/IP. PANICs would occur when large blocks of data were attempted to be transferred. On-Line Backup - On-line backup, using cpio, is now supported on BOSS/VX. The -J option is used with the cpio command. This option allows files to be in use while a cpio command is being performed on that file. Journaling allows changes to be made to the files but copies the files to tape as they existed when the backup was started. PANIC will now save the 16-way portion of the dump to tape. It will also provide an option to save to disk. MAI SPOOLER: ___________ Patch 49 - Fix to the lpd procedure of the despooler. Before the fix, an error would display in the printer queue and an error -958 would appear in the printer errorlog (lpstat -e). hpljet and okiled are now options as configurable printers within the configure utility. 'hpljet' is for Hewlett Packard Laser Jet Printers and 'okiled' is for the Okidata OL400/OL800/OL810/OL840 page printers in HP Laserjet emulation. pformchg can print test patterns with live data containing @ signs. PT-4217/18 will not need a form feed to print the last line of a print job. Spooler - the correct form will be loaded at boot time. BASIC: ----- /tmp.execsh#### files were not always deleted after a user exited BASIC (BB90). Now the files are deleted immediately after the user signs on. Error 32 will occur instead of error 21 and a core dump. Error 20 will be returned instead of error 21 for ">1600 1abc=10" INITFILE will not break file links. UTILITIES: --------- fuser will now display the operator that has a file OPENed. frepair will not exit if a file is unrepairable. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB054 Pg002 frepair will not shrink the serial file size when the file is badly corrupted. cread will restore all files on tape. configure; the option to switch 2 devices will not change LP to a terminal when the procedure is performed. mbfinstall returns the correct SSN when /usr/ob/bin is the first prefix in the PATH. 3.0 PERFORMING ON-LINE BACKUP On-line backup provides the ability to backup one or more files while the files continue to be accessed by users. This is performed in such a way that the integrity of the backup copy is maintained. The backup may be made to any tape device or to another disk. On-line backup is made possible by the use of a technique called journaling. Journaling is used when a file is being backed up and possibly being modified at the same time. The original data in the file is "shadowed" or set aside for use by the backup utilities. Thus, an application has the new. records available to it while the backup utility accesses the shadow records. When the shadow copy is no longer needed, it is deleted. FILE INTEGRITY Agroup of files can be backed up using one of three methods. The first two methods, FILE INTEGRITY and EXTENDED FILE INTEGRITY, allows the files to change relationships to each other. The third method, CROSS-FILE INTEGRITY,. backs up a group of files in such a way that they are unchanged relative to each other. File integrity is preserved by the cpio command. The cpio command can be used to backup one or more files using the journaling technique. Since cpio. processes one file at a time, journaling is used on each file in turn, guaranteeing the integrity of each file as it is backed up. The effective time of the "snapshot" of each file in the filelist will be different and depends on the position of the file on the filelist. Thus, it is possible to make a multi-file update, and have a backup which includes the changes made to one file and not to others. For example, suppose a data base consists of three interrelated files. The first may contain the client name, the second. client address and the third client phone number. An on-line backup is started by invoking cpio on the three files with the journaling option. After the file name is backed up and before the phone number file is backed up, a client is deleted from the database, removing a record from each of the three files. The backup will have the client's name and address but not the phone number. The data in the backup is therefore inconsistant. The olb utility provides EXTENDED FILE INTEGRITY, which narrows the window thus reducing data inconsistancy. olb starts journaling on all the files in the filelist list, then starts the specified backup process. Journaling is stopped after the backup process is complete. Once olb is started, changes made to files will NOT be backed up. A backup that did not use olb would backup changes made to files after the backup was started, therefore the files would be inconsistant.A small window does exist from the start of the journaling of the first file to the start of journaling of the last file. This window is smaller than the window on a backup that journals one file at a time. CROSS-FILE INTEGRITY exists when the uer guarantees that there will be no multi-file updates to the data during the time olb starts journaling on a SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB054 Pg003 group of files. Since the BOSS/VX Operating System has no method of determining when all files are in synchronization, guaranteeing file synchronization is the user's responsibility. Some suggestions on how to achieve file synchronization follow. To create a backup with Cross-file integrity requires several steps listed below: 1. Stop all applications from making changes to the files being backed up. 2. Invoke olb to start journaling on all files "simultaneously". 3. Wait until olb starts the backup, using cpio with journaling. 4. Release the application so that modifications may continue. The first step of synchronizing the application is done prior to invoking olb. The actual method used will be tailored for the application. Some possibilities are: o Users logoff - the simplest method; all users would be voluntarily or forcibly logged off the system until journaling has been started on all files. o Menu-lock - prevent operators from starting new transactions by locking them in a high level menu. The synchronization program would wait until all operators were locked in a safe menu. o Transaction boundaries - similar to menu lock, but could involve extensive application changes. This technique ammounts to making the application perform rudimentary transaction processing. At the beginning of each transaction the application would check for an olb "synchronization request" and wait until authorized to continue, and then register "in transaction". At the end of the transaction, it would change the status to "not in transaction". o Bached updates - file modification would be mde to a special set of temporary files during synchronization. The application would have to be modified to switch over and back. This method is practical only if file I/O is centralized. o The second, third and fourth steps of guaranteeing Cross-file Integrity would be performed by invoking olb on a shell script instead of an individual cpio command. The shell script would be executed after olb had started journaling on all files to be backedup. The shell script would restart the application, reversing whatever technique was used to synchronize the application before invoking cpio with journaling. cpio -J o Journaling is employed by using the -J option, which has been added to the standard UNIX cpio utility. Journaling creates "shadow records", which are original records in the file that have changed since journaling has started. Once journaling for a file has completed the shadow records are deleted. If journaling was already in effect, the program "sees" the file as it was when journaling was first started. When cpio is used with -J and without olb, journaling is started just before cpio copies the file to tape and stops when cpio moves to the next file. Backing up with Extended File Integrity is provided by using the new olb utility in conjuction with cpio. olb accepts a list of files, requiring SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB054 Pg004 journaling from a standard input, then executes a user specified command. The command is responsible for performing the backup. SYSTEM PERFORMANCE The impact of On-Line Backup on the system is a function of the amount of data being backed up, the degree Cross-File Integrity is requested and the amount of file modifications made to the files which are being journaled. The impact of using olb may include reduced system throughput, using larger amounts of disk space and using inodes. To minimize the impact on system performance, olb like any other backup utility, is best used during non-oeak hours. In addition, the use of the Cross-File Integrity feature should be minimized by choosing the smallest set of files that must be synchronized for backup. Backing up large sets of files with olb will result in all files being opened simultaneously with journal mode which may exhaust some system resources. olb uses a file pointer for each file while journaling is turned on. The pointer is not available until journaling is turned off. To prevent a resource problem, the maximum number of open files, under the DCT parameters, may need to be adjusted. Refer to man pages for cpio and olb for more information. ORIGINATOR: Dan Arteritano SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB054 Pg005 FIB 00055 MAI COMPANY CONFIDENTIAL 08/12/93 *** Release 1.2A Software Announcement for GPx70 [WPSS 201] *** 1.0 INTRODUCTION Level 1.2A of BOSS/VX for the GPx Series 70 is now available. This release is the recommended Operating System for the GPx Series 70 Systems. The 1.2A Operating System is derived from the 1.1A Operating System and contains the following new features and enhancements. 'BCS', System V Binary Compatible Specification support. Printer support through terminal servers. Up to two VME Auxiliary SCSI Controllers, each supporting up to 6 drives 5.25" VME SCSI Disk Expansion Chassis which supports up to 12 SCSI disk drives and 1 differential SCSI external GCR tape drive. 1.6GB disk drive support. Support for multiple Parallel Printer Controllers. 128KB instruction/data cache Dual Processor Unit This Software Announcement contains general information about the Level 1.2A BOSS/VX Operating System. Installation and update procedures are fully documented in this announcement. Also, this document has sections on new features and enhancements. It is recommended that you read this document before installing Level 1.2A. For information on ordering new Software and Hardware in 1.2A, see Marketing Announcements. TABLE OF CONTENTS 1.O INTRODUCTION. . . . . . . . . . . . . . . . . . . . . Cover 2.0 BOSS/VX OPERATING SYSTEM HISTORY. . . . . . . . . . . . 1 3.0 NEW SOFTWARE PRODUCTS IN LEVEL 1.2A . . . . . . . . . . 1 3.1 'BCS' SUPPORT. . . . . . . . . . . . . . . . . . . 3.2 PRINTER SUPPORT THROUGH TERMINAL SERVERS . . . . . 3.2.1 DESCRIPTION . . . . . . . . . . . . . . . . . . 3.2.2 SETUP AND CONFIGURATION FILES . . . . . . . . . 3.2.3 LIMITATIONS AND RESTRICTIONS. . . . . . . . . . 4.0 NEW HARDWARE PRODUCTS SUPPORTED IN 1.2A . . . . . . . . 4.1 AUXILIARY SCSI CONTROLLERS . . . . . . . . . . . . 4.2 5.25" DISK EXPANSION CHASSIS . . . . . . . . . . . 4.3 1.6GB DISK DRIVE SUPPORT . . . . . . . . . . . . . 4.3.1 DEVICE ADDRESS SELECTION. . . . . . . . . . 4.4 MULTIPLE PARALLEL PRINTER CONTROLLERS. . . . . . . 4.5 128KB Instruction/Data cache DPU . . . . . . . . . 5.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg001 OPTIONAL SOFTWARE PACKAGES. . . . . . . . . . . . . . . 5.1 BOOTING THE SSM FIRMWARE FROM TAPE . . . . . . . . 5.2 WRITING A NEW VTOC . . . . . . . . . . . . . . . . 5.3 INSTALLATION AND UPDATE OF THE BOSS/VX O.S.. . . . 5.3.2 UPDATE OF THE OPERATING SYSTEM. . . . . . . 5.3.3 UPDATE OF THE SSM FIRMWARE. . . . . . . . . 5.4 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD . . . . . . . . . . . . . . . . . . . . . . 5.5 INSTALLATION AND UPDATE OF THE OPTIONAL SOFTWARE PACKAGES . . . . . . . . . . . . . . . . . . . . . 5.6 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES . . . . 5.6.1 MAI PRESENTATION SERVICES. . . . . . . . . . 5.6.1.1 PRESENTATION SERVICES CUSTOM MENUS . 5.6.1.2 PRESENTATION SERVICES FORMS. . . . . 5.6.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE . . . 5.6.2.1 INSTALLATION REQUIREMENTS. . . . . . 5.6.2.2 NEW INSTALLATION OF ORIGIN 2.1B. . . 5.6.2.3 UPDATING FROM 2.1A . . . . . . . . . 5.6.2.4 UPDATING FROM 2.0A . . . . . . . . . 5.6.2.5 INSTALLATIONS UPDATING 1.3B OR 1.3A. 5.6.2.6 EXECUTING ORIGIN ON THE GPx. . . . . 5.6.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx. . . . . . . . . . . . . . 5.6.3.1 MPx TO GPx CONVERSION. . . . . . . . 5.6.3.2 SPx TO GPx CONVERSION. . . . . . . . 5.6.4 ORIGIN 2.1B NEW FEATURES . . . . . . . . . . 5.6.5 TRANSLATION. . . . . . . . . . . . . . . . . 5.6.6 DOCUMENTATION. . . . . . . . . . . . . . . . 5.7 ETHERNET AND TCP/IP . . . . . . . . . . . . . . . . 6.0 PROBLEMS CORRECTED IN THIS RELEASE . . . . . . .. 6.1 BASIC . . . . . . . . . . . . . . . . . . . . . . . 6.2 OPERATING SYSTEM . . . . . . . . . . . . . . . . . . 6.3 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . 6.4 COMMUNICATIONS . . . . . . . . . . . . . . . . . . . 6.5 UTILITIES . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 PRINTERS . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 PATCHE INCORPORATED INTO THIS RELEASE 2.0 BOSS/VX OPERATING SYSTEM HISTORY 1.0A First release of the Operating System for the GPx Series 70. Supported the 5070 and 6070. 1.1A Second release of the Operating System for the GPx Series 70. New features and enhancements included : UPD Simple Compiler, On-Line Backup, CISAM/BFS, User Access of BFS C-Library Functions, New File Write Options, Auditor's Log Book, Errorlog Monitor, Bad Block Mapping, lphold Command, New dct Scripts, Ethernet and TCP/IP, 2780/3780 Batch Communications, SMD 8" Disk Drives, 8mm HCC Tape Drive, 1/2" MTS Tape Drive, New Parallel Printer Controller and On-Line Configure. 3.0 NEW SOFTWARE PRODUCTS 3.1 'BCS', SYSTEM V BINARY COMPATIBLE SPECIFICATION SUPPORT 'BCS' is a standard developed by Intel and other manufactures to provide binary compatibility between various Intel 386/486 based UNIX machines. The 'BCS' support on BOSS/VX allows, with certain exceptions, programs such as Lotus 123 and WordPerfect to run under BOSS/VX SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg002 unchanged. Most programs written to run under AT&T and SCO UNIX environments will now run under BOSS/VX. Programs requiring shared libraries are not supported. 3.2 PRINTER SUPPORT THROUGH TERMINAL SERVERS It is now possible to connect serial printers on terminal servers and to activate terminal ports on a server via a system command. 3.2.1 Description Rtelnet spooling is designed like the BOSS/VX spooler with a serial printer attached to a terminal server. Unfortunately, TCP/IP does not allow synchronous I/O, but only asynchronous I/O is allowed to communicate between the spooler daemon and the printer. Because of this, the spooler daemon cannot know the status of the printer, which can only be controlled via XON/XOFF between the printer and the upc daemon. Rtelnet spooling is functionally identical to spooling of serial printers attached to 16-ways. The differences are that 16-way printers are configured via the 'configure' utility and use synchronous I/O, whereas rtelnet spooled printers are configured by special shell scripts which are designed to start up and shutdown the connection between the spooler daemon and the terminal server, and asynchronous I/O is used. 3.2.2 Setup and System Configuration Files There are two shell scripts which connect and disconnect a specific printer attached to a terminal server, to the BOSS/VX spooler via ethernet. These two shell scripts are called /bin/rtelstart and /bin/rtelstop. rtelstart will connect and configure a printer, while rtelstop will disconnect and deconfigure a printer. The same two programs are also used to connect and disconnect specific terminals attached to a terminal server. The interface between the user and rtelstart is through a file called /etc/rtelnettab. The user is required to add printer or terminal information to this file as follows: # -- Use char '#' for remarks #IP-ADDR PORT BFS-NUM PRINTER? PRT TYPE 139.0.0.1 1 200 P 4229 139.0.0.4 3 201 T 4314 IP-ADDRESS : Terminal Server IP address PORT : Terminal Server port number where the device is attached (between 1-16) BFS-NUM : BASIC port number for specific printer or terminal (bfsdev number) PRINTER? : P for configured printer; T for terminal PRT-TYPE : Printer type from /usr/mbf/etc/prttbl directory or terminal type. Use 'vi' to update the file /etc/rtelnettab. Once it is updated to describe the relevant printer(s) and terminal(s), the user runs 'rtelstart' to connect the device and 'rtelstop' to disconnect the device. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg003 Rtelstart will read /etc/rtelnettab and call rtelnet with the appropriate parameters. It should be noted that /etc/bfsdevs, /etc/printers, /etc/defaults and /etc/gettydefs are all updated by both rtelstart and rtelstop. . Rtelstart is required to run after each system load and rtelstop should be run prior to each system shutdown. These shell scripts can be executed from command mode or automatically by creating entries to the system start up and shutdown routines in the /etc/rc2.d and /etc/rc0.d directories. A start up example is shown below : File named /etc/rc2.d/S99rtelstart with entries: echo "Now Starting Terminal Server Ports" /usr/bin/rtelstart File named /etc/rc0.d/K99rtelstop with entries: echo "Now stopping Terminal Server Ports" /usr/bin/rtelstop 3.2.3 Limitations and Restrictions The user must correctly configure the printer and terminal ports on the terminal servers. A printer should not be powered off while it is connected. Data may be lost due to the asynchronous I/O. It the 'configure' utility is to be run, the user must first shutdown remote devices via rtelstop. Once 'configure' is completed, the user may restart remote devices via rtelstart. If rtelstop is not run, the 'configure' utility will wipe out all of the remote device configuration information. The user should not run rtelstart and the rtelstop in quick succession. A short delay (e.g. 60 seconds ) should be allowed so that the interrupt signal and the file updates are all correctly handled. Limitations also exists in the amount of configurable parameters supported. All devices use standard default configuration parameters which can not be changed. 4.0 NEW HARDWARE PRODUCTS SUPPORTED IN 1.2A 4.1 AUXILIARY SCSI CONTROLLERS Up to two Auxiliary SCSI Controllers (ASC) can be installed in the VME (I/O) Bus card cage. Each ASC can support up to six 5-1/4 inch disk drives in the optional SCSI Expansion Cabinet Assemblies. The jumper settings, board layout and description of the ASC is provided in the GPx Series 70 Installation and Maintenance Manual (M8226B). The ASC may be used to connect directly to the internal system differential SCSI adapter. This configuration requires another SCSI Bus daisy chain cable (P/N 916547-001 - 5X70 or P/N 916661-001 - 6X70) and allows for an additional SCSI tape device without having to use the disk expansion chassis. This is only for when all SCSI device addresses are used and an additional 1/2" tape drive is needed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg004 These controllers should be manufacture top assembly part number 82027807 revision B' or higher. The MAI part number is 400740-001. The firmware at location D14 (odd) is part number 79184010 Rev. R22.0 and at location D16 (even) is part number 79184020 Rev. R22.0. 4.2 5.25" DISK EXPANSION CHASSIS The SCSI Expansion Cabinet Assembly (ECA) is required for the expansion of 5.25" SCSI disks beyond the five that are housed in the base cabinet. One ECA is supported which will allow up to 12 SCSI disks. In addition, the ECA can include one Differential SCSI Adapter which provides support for one GCR tape drive. This differential SCSI adapter is an optional addition for this chassis. The GPx 70 Installation and Maintenance Manual (M8226B) provides installation details for the ECA. 4.3 1.4GB DISK DRIVE SUPPORT 1.2A now supports two additional drives types. The model number for these drives are Maxtor P1-17S and Seagate ST4165ON. These drives have a 1.6GB unformatted capacity and can be connected to the system SCSI bus (the SSM) or the new VME SCSI controller. The physical installation of these drives is identical to that of the M380/M760 drives which is documented in the GPx Series 70 Installation and Maintenance Manual (M8226B). 4.3.1 Device Address Selection for the P1-17S and the ST41650N Disk Drive The following provides the procedures for preparation of the 1.4GB disk drives. The logic board on the disk drive contains three jumpers, which are used to select the device address. Table 4-1 lists the device address jumper settings for SCSI Disks 0 thru 5. Figure 4-1 shows the location of all jumpers and lists the required settings for jumpers. (Refer to the notes following Table 4-1.) Table 4-1A - Device Address Jumper Settings, Maxtor P1-17S Disk Drive JUMPERS J2-1,2 J2-3,4 J2-5,6 Binary Weight Device Address Installed Installed Installed 1 1 1 07 (Reserved) Installed Installed Removed 1 1 0 06 (Reserved CCA/ECA) Installed Removed Installed 1 0 1 05 (Reserved in CCA) Installed Removed Removed 1 0 0 04 (Disk 4) Removed Installed Installed 0 1 1 03 (Disk 3) Removed Installed Removed 0 1 0 02 (Disk 2) Removed Removed Installed 0 0 1 01 (Disk 1) Removed Removed Removed 0 0 0 00 (Disk 0) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg005 Table 4-1B - Device Address Jumper Settings, ST41650N Disk Drive JUMPERS J4-5,6 J4-7,8 J4-9,10 Binary Weight Device Address Installed Installed Installed 1 1 1 07 (Reserved) Installed Installed Removed 1 1 0 06 (Reserved CCA/ECA) Installed Removed Installed 1 0 1 05 (Reserved in CCA) Installed Removed Removed 1 0 0 04 (Disk 4) Removed Installed Installed 0 1 1 03 (Disk 3) Removed Installed Removed 0 1 0 02 (Disk 2) Removed Removed Installed 0 0 1 01 (Disk 1) Removed Removed Removed 0 0 0 00 (Disk 0) NOTES: CCA disk drives are normally set for device addresses 00 thru 04. Device address 05 is reserved for an optional tape drive, configured on the CCA's rear-panel DIFFERENTIAL SCSI port. When two or three tape drives are configured, the additional drives are assigned device addresses 03 and/or 04, thus reducing the number of CCA disks. The CCA's integral 1/4-inch SCSI tape drive is always set for a device address of 06 and is terminated. Device address 07 is reserved for the SSM PCBA. Terminators are not installed on CCA disk drives; remove any terminators present on disk drive PCBAs (see Figure 4-1). When SCSI ECAs are configured, the last device on the SCSI bus, either a disk drive or the Differential SCSI Adapter, is terminated. SCSI ECA disk drives are normally set for device addresses 00 thru 05. Device address 06 is reserved for an optional tape drive, configured on the ECA's rear-panel DIFFERENTIAL SCSI port. Device address 07 is reserved for the ASC PCBA. ..................................................................... Maxtor P1-17S ______________________________________________________________ ____| _ _ | | | JP1|_| |_|JP2 | | J3 | | _|____| _ _ ___ | | _ |_|JP5 |_|JP7 | | | | -| |J _ |J5 | | | -|_|2 |_|JP13 | | | | --J6 _ |___| | |__ |_|JP6 _ | _/ | [] |_|JP3 | |_ | [] | | | [] T _ _ | | | [] E |_|JP4 |_|JP8 | | J1 | [] R | | | [] M | | | [] | |_ | [] _ _________ | |\___| _ _ |_|JP9 | J4 | | | |_|JP10 |_|JP11 |_________| | |_______________________________________________________________________| SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg006 Maxtor P1-17S JUMPER SETTING JUMPER SETTING JP1 Installed JP9 Installed 1,2 JP3 Removed JP10 Removed JP4 Installed 1,2 JP11 Installed JP5 Removed JP12 Installed JP6 Removed JP13 Removed JP7 Installed J2-7,8 Removed (P disable) JP8 Installed 1,2 J2-9,10 Removed (LED) Figure 4-1A. Jumper Locations/Settings. Maxtor P1-17S .......................................................................... Seagate ST41650N ------------------------------------------------------------------- | |Power BOTTOM VIEW | | |Connector | | | | |_| | |__Pin 1 | | | [] Pin 1 | |J3| [] | |S | [] Terminator | |C | [] | |S | | |I | [] | | | [] | |C | [] | |O | [] | |N | | |N | [] | | | [] | | | [] | | | [] | |__| | |* * Jumper Pair 19,20 | |* * J4 | |* * JUMPERS | |* * Jumper Pair 1,2 | |_________________________________________________________________| REAR VIEW . |--------------------------------------------------------| Pin 2 |* * * * J4 * * * * | J3 SCSI CONN Pin 1| | POWER | Pin 1 |* * * * * * * * * * |_________________________| --------| (continued on next page) SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg007 Jumper Settings for Seagate ST41650 (1650 MB Drive) ------------------------------------------------------------------------ | FACTORY | MAI | JUMPER | SETTINGS | SETTINGS | DESCRIPTION ------------------------------------------------------------------------ J4-9,10 | OFF | OFF Note: All | Drive Select (1) J4-7,8 | ON | OFF off drive | Drive Select (2) J4-5,6 | ON | OFF select 0 | Drive Select (4) | | | J4-17,18 | OFF | OFF | Sync Select J4-19,20 | ON | OFF | Sync Select | | | J4-11,12 | OFF | OFF | Motor Start Option J4-13,14 | ON | ON | Parity Checking J4-15,16 | OFF | OFF | Motor Delay | | | J4-1,3 | ON | ON | Termination Power to Pin 26 | | | J6-1 | OFF | OFF | +5 LED Remote J6-2 | OFF | OFF | LED Driver ------------------------------------------------------------------------ Figure 4-1B. Jumper Locations/Settings ST41650N ................................................................... 4.4 MULTIPLE PARALLEL PRINTER CONTROLLERS Multiple Parallel Printer Controllers (PPC) are supported to a maximum of two per system. Each PPC will provide support for up to four Centronics or DataProducts compatible parallel printers. The minimum revision level required for the PPC is 'B'. The part number for the Rev. 'B' is 903841-002. If an existing PPC is installed and a second PPC is added, the existing PPC may require an update to meet the minimum revision level requirements. Refer to the GPx 70 Installation and Maintenance Manual (M8226B) for installation instructions. 4.5 128Kbyte INSTRUCTION/DATA CACHE DPU A new 128Kbyte instruction/data cache Dual Processing Unit is now available. Increasing the processor cache size on a GPx70 to 128KB adds up to 39% to user level performance. The benefit is greatest with compute-intensive applications and large-memory configurations. There will be no noticeable user level performance increase when disk or memory saturation is a limiting factor. The part number for this DPU is 903853-001 and the current revision level is 'A'. There are no jumper or switches on this board. The installation is identical to that of the 32KB DPU which is documented in the GPx70 Installation and Maintenance Manual (M8226B). The boards may be installed along with the 32KB DPU boards if it becomes necessary to do so. 5.0 INSTALLATION AND UPDATE OF THE OPERATING SYSTEM AND OPTIONAL SOFTWARE PACKAGES This procedure gives the steps required to install or update the BOSS/VX operating system on the GPx Series 70 hardware platform. It is divided up into seven sections: SECTION 5.1 provides the information required to load the system to the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg008 third level prompt from tape; normally called loading the SSM firmware. This step is required for all new installs where the OS is not already on the disk and for all systems on OS level 1.0A. SECTION 5.2 details the steps required to install a new VTOC (volume table of contents). This step is required for all new installs or for a primary disk (the disk the OS will be boot from) after a format. SECTION 5.3 provides the steps for installation and update of the OS. SECTION 5.4 details the steps to install or update the system security record. SECTION 5.5 provides the steps to install or update optional software packages. SECTION 5.6 gives the steps to customize the optional software packages. SECTION 5.7 gives the steps to install the LAN and TCP/IP packages. WARNING: OS updates from 1.0A to 1.2A require that a new dct file be installed. Before attempting an update, make a copy of your current dct file and save it in another directory. At the prompt to reinstall dct enter 'Y'. Make sure any changes done to the original dct file are carried over into the new one. NOTE: O.S. updates from 1.1A to 1.2A do not require re-installation of the dct. NOTE: The mini-root is automatically installed during the OS installation update. NOTE: During the installation/update procedure the system will be booted and programs loaded from tape and/or hard disk. The command 'tm(48,x)',(where x=file number on the tape) will be used to boot or load a program from tape. For hard disk access 'wd(0,x)', (where x=block offset) or 'wd0sx', (where x= partition on disk) will be used. NOTE: The following procedure uses the install script loaded in the SSM firmware to install a new mini-root and then boot to it. This is the recommended procedure as the latest programs and files will be loaded on the mini-root. If for troubleshooting reasons you need to load the mini-root, not re-installing it first, from level 3 '--->' enter: bh 'wd(0,8)unix -M -r wd0s8 -s wd0s8' NOTE: Prior to giving the system back to the customer after upgrading to 1.2A, all keyed files should be analyzed to verify there is no data corruption. The 'frepair' utility in 1.2A has been improved and may find problems not seen on previous levels. NOTE: If you are upgrading a system that has LAN and TCP installed, you will need to reinstall these products using the 1.2A tape. 5.1 BOOTING THE SSM FIRMWARE FROM TAPE The following section outlines the steps to load the SSM to the third level prompt from tape. The SSM firmware will need to be loaded from SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg009 tape if this is a new installation, the primary disk does not contain a operating system or the operating system on the disk is a 1.0A release. If the primary disk contains a OS release of 1.1A or greater the SSM can be booted from the primary disk and this section skipped. The BASE OS tape is used to boot the SSM firmware into SSM memory. The SSM has three states that it goes through during the boot process. On a new system with the BASE OS tape inserted and the machine powered on, the system will come up in level 1 indicated by a single dash followed by a greater-than symbol '->'. The user enters a boot command to bring the system to level 2 indicated by the prompt '-->'. Then another command is typed in to bring it to level 3 operational firmware, indicated by the prompt '--->'. 1) If the system is already running, shut it down with the shutdown command ('shutdown -i0 -g# -y' where # is the number of seconds to wait). The '--->' prompt will be displayed when the shutdown is complete. Go to Step 3. 2) If the system is not running, power the system on. If during the load, after the self test the following message is displayed '5 seconds to boot, press any key to stop:' enter a to stop . the auto-boot. The system will respond with the level prompt. Continue on to Step 3. If the system boots to single or multi user mode, shut it down as in step 1 above. 3) Put the BASE OS tape in the tape drive and enter: bs tm(48,2) This reads and runs the boot program from tape. This is called level 2 (system prompts '-->'). If the system displays the message '5 seconds to boot, press any key to stop:' enter to stop the auto-boot. 4) Enter bs tm(48,3) This brings the system to the operational firmware level (level 3). The system prompts with '--->'. If the system displays the message '5 seconds to boot, press any key to stop:' enter to stop the auto-boot. At this time the SSM is booted with the latest FIRMWARE level and the system is at the level 3 prompt. From here go to the VTOC or OPERATING SYSTEM INSTALLATION AND UPDATE section depending on the installation requirements. 5.2 WRITING A NEW VTOC If hardware failure or installation instructions require writing of a minimal vtoc, proceed with the following steps. Writing of a minimal vtoc is required when the disk partitioning of the primary disk is unknown or is changing from one release to the next. Writing a minimal vtoc writes a volume table of contents that describes a single partition on the disk. In this case, the partition SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg010 being described is partition 8 for the miniroot. WARNING: THIS PROCEDURE WILL ERASE YOUR DISK. IF THERE IS CUSTOMER DATA ON THE DISK, ENSURE THERE IS A BACKUP BEFORE CONTINUING To write a minimal VTOC perform the following steps: 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt '--->', if not go to Section 1.1 to boot the SSM firmware to the level 3 prompt. 2) At the '--->' prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS tape is in the tape drive before entering 'y' . This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 3 'Special Installation' to install the minimal VTOC. 4) At the prompt : enter tm(48,5) 5) A menu of disk drives the VTOC can be installed on is displayed. Enter the drive number that the minimal VTOC is to be installed on. will cause the VTOC to be written to the primary disk drive (wd0). 6) Next disk drive and minimal VTOC information is displayed. Followed by the prompt 'Use this layout (y/n)?'. Enter y at this prompt. A minimal VTOC will now be written to the disk drive. After it is complete the system will prompt with the level 3 prompt '--->'. 5.3 INSTALLATION AND UPDATE OF THE BOSS/VX OPERATING SYSTEM The following section outlines the steps to install or update the BOSS/VX Operating System. NOTE: Installation or Updating the OS will write a new mini-root. There is no need for a special step to install the mini-root. 5.3.1 INSTALLATION OF THE BOSS/VX OPERATING SYSTEM The following steps outline the BOSS/VX installation procedure. This procedure will erase all the files on the 'root' and 'usr' file systems. It makes a new vtoc for the disk, makes the file system for the 'root' and 'usr' partitions and installs the standard BOSS/VX software (BOSS/VX, Business BASIC and system utilities) on the disk. WARNING: A full installation completely destroys the contents of the root and usr partitions. Other partitions may not be affected, but they must be backed up as a precaution. Other partitions will definitely be destroyed if the disk partitioning changes as a result SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg011 of the installation. The following will be required to install the OS: o BASE Operating System Tape o Configuration Record tape for the target system Do the following steps to Install the BOSS/VX Operating System 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt '--->', if not go to Section 1.1 to boot the SSM firmware to the level 3 prompt. 2) At the '--->' prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS tape is in the tape drive before entering 'y' . This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 1 'Full Installation'. 4) A menu of disk drives the OS can be installed on will be displayed. Enter the drive number that the OS is to be installed on. CR will cause the OS to be installed on the primary disk drive (wd0). 5) Next disk drive and minimal VTOC information is displayed. Followed by the prompt 'Use this layout (y/n)?'. Enter y for this prompt. A new mini-root will be installed on the target disk. After the new mini-root is installed the system will be booted on to the mini-root. 6) After the boot process is complete the '#' will be displayed. From this prompt enter: ./INSTALL This will bring up the BOSS/VX SOFTWARE INSTALLATION menu. 7) From the BOSS/VX SOFTWARE INSTALLATION menu enter option 'f' for Full Install. 8) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 9) A warning message is displayed telling you that a full installation will destroy all files on the primary disk. You will be prompted with: Do you wish to continue (y/n)? Enter 'y', , to continue with the installation or 'n', SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg012 to exit the installation procedure. 10) A message is displayed saying Extracting data, after which a table will be displayed giving present system disk partitioning information. This information will be used to update the system disk's vtoc (volume table of contents) and contains the following information: Partition number, partition label(name), size in MBs, mount point (directory to mount the partition to if it's to be mounted automatically at boot), auto mount flag (this tells the system if the partition should be mounted at boot time or not), and swap (this tells the system if this is a swap partition or not). At the bottom of the table is the prompt: Enter selection (0-11, h=help, i=install) to modify: If you wish to use the disk partitioning information in the table to set up the system disk enter i and proceed to Step 11. If you wish to modify the disk partitioning information enter the partition number you wish to modify. NOTE: Partitions 8,12,13,14 and 15 are reserved for the OS and cannot be modified. After entering a partition number to modify you will be given the following options: Label - This will allow you to label (name) the partition. This field can be 1 to 6 characters long. Size - This will allow you to give the size for the partition. This option is used to increase or decrease the size of a partition. The size can be changed in increments of 1 megabyte. NOTE: A partition's size cannot be increased if there is no available disk, so decrease other partitions before increasing any. Mount - The mount point is the directory the Point partition will be mounted on. The root and usr mount points cannot be changed. An entry of a . (period) removes a mount point. If a partition is not auto-mounted, it doesn't HAVE to have a mount point. Automount - If this option is set to yes, the partition will be mounted at boot time. A partition option requires a mount point. A partition cannot have swap and auto-mount both set to yes. Swap - If a partition is to be used as swap when the system is in multi-user mode, set swap to yes. If it is not to be used as a swap partition then set swap to no. redisPlay - As updates are made to the table the screen information in the table will not be displayed until you are done with that SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg013 partition update or this option is used. Help - The help messages will be displayed. Remove - Removes a partition from the disk. The root, swap, usr, firmware, vtoc, boot, and miniroot partitions cannot be removed. Done - Indicates that changes to this partition are complete. Final verification for this partition takes place. The screen and main menu is displayed. This partition can be selected again for editing. Enter the capital letter in each option to select that option. When you are done with the update of the system disk partitioning, enter i to install this information into the system disk's vtoc. 11) Messages will now be displayed indicating that the file systems are being made and mounted. After the file systems are made, the BOSS/VX software will be copied from tape to disk. 12) After the BOSS/VX software is copied to disk, messages will be displayed telling you that the SSM firmware is being copied to disk, that the /dev devices are being made and that /etc/versionlog is being created, followed by a message giving the current system name. You will be prompted with: Do you wish to change it (y/n)? If you wish to change the name enter 'y', and you will be allowed to enter a 8 character name. If you don't wish to change it enter 'n', . 13) The Date and Time are displayed. You will be prompted with: Would you like to set date and time (y/n)? To set date, time and timezone enter 'y', , and the following will be displayed: Current time and time zone is: HH:MM EDT Change the time zone (y/n)? If you wish to change the time zone, answer 'y', , and a list of available time zones will be displayed. Enter the number of the time zone you wish to use. If the time zone displayed is correct, answer 'n', . If you change the time zone you will next be prompted with: Does your time zone use Daylight Savings Time during the year (y/n)? Answer the question as it pertains to your time zone. Next the current date and time are displayed followed with the prompt: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg014 Change the date and time (y/n)? If they are correct, answer 'n', ; otherwise, answer 'y', , and you will be prompted with the questions to set the Date and Time correctly. After the date and time are changed you will be prompted with: Date and time will be set to: MM/DD/YY HH:MM (y/n)? If the date and time is correct enter 'y', . If you need to go back and change the date or time enter 'n', . 14) You will next be prompted with: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? Enter 'y', , to install the configuration record. If you enter 'n', , the configuration record will not be installed. NOTE: You must install a configuration for your system to boot. If you entered 'n', , in the above step, see Section 5.4, "Installation/Upgrade of the Security Configuration Record" to install the configuration record. 15) After the configuration record is installed, the installation of the BASE system is complete. You will be prompted with: Remove the configuration record tape from the tape drive and enter 'r', , to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 5.5, "Installation and Update of Optional Software Packages" 5.3.2 UPDATE OF THE OPERATING SYSTEM The following steps outline the BOSS/VX update procedure. This procedure keeps the current partitions and updates the standard BOSS/VX software files that already exist on the system's fixed disk. The customer's files, as well as any partitions that have been defined, are kept intact by this procedure. The OS files on the system that can be modified by the user will be automatically installed if they do not exist. Otherwise, you will be prompted to install user defined OS files or keep the SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg015 original ones. WARNING: Before attempting any update, it is recommended you have a verified backup of the customer's data. Ensure that this backup doesn't contain any of the OS files. WARNING: OS updates from 1.0A to 1.2A requires that a new dct file be installed. Before attempting an update make a copy of your . current dct file and save it in another directory. At the prompt to reinstall dct enter 'Y'. After the system comes back up compare the 1.0A dct to the 1.2A dct and make the required changes. The following will be required to upgrade the OS: o BASE Operating System Tape o Configuration Record for the target system (if you wish to re-install the configuration record) 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt '--->', if not go to Section 1.1 to boot the SSM firmware to the level 3 prompt. 2) At the '--->' prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS tape is in the tape drive before entering 'y' . This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 2 'Update Installation'. 4) A menu of disk drives the OS can be updated on will be displayed. Enter the drive number that the OS is to be updated on. CR will cause the OS to be updated on the primary disk drive (wd0). A new mini-root will be installed on the target disk. After the new mini-root is installed the system will be booted on to the mini-root. 5) After the boot process is complete the '#' will be displayed. From this prompt enter ./INSTALL This will bring up the BOSS/VX SOFTWARE INSTALLATION menu. 6) From the BOSS/VX SOFTWARE INSTALLATION menu enter option 'u' for Update Install. Messages will be displayed telling that the file systems are being checked and mounted. The target disk must contain a valid BOSS/VX file system for the update to continue. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg016 7) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 8) A list of files that will not be updated will be displayed with the prompt: Would you like to change the list (y/n)? Enter 'n', if this list is correct. If you wish to modify the list enter 'y', and you will be prompted to add or delete files from the list. 9) The BOSS/VX software will be copied from tape to disk. After which the files that were marked not to be changed will be copied back to their proper place from the gap partition. 10) After the BOSS/VX software is installed you will be prompted with: Would you like to re-install dct (y/n)? NOTE: Updates from 1.0A to 1.2A require this prompt to be answered 'Y' If the system's configuration has changed and the DCT file needs to be changed, updated with the correct DCT file, or you want to put down a default DCT file enter 'y', . Otherwise, enter 'n', . 11) You will next be prompted with: Install the configuration record (y/n)? If you don't wish to install the configuration record, enter 'n', and you will be done with the O.S. update. If the system's configuration has changed so that it requires a new configuration record or you want to re-install the old configuration record, enter 'y', and you will be prompted with the following: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Take the tape containing the BASE system out of the tape drive and put the tape containing the Configuration Record in the tape drive and enter . The configuration record will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? If you enter 'y', , the configuration record will be installed. If you answer 'n', , the configuration record will not be installed. 12) After the configuration record is installed, the update of the BASE system is complete. You will be prompted with: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg017 Press to main menu, or "r" to reboot the system: NOTE: At this time go to Section 5.3.3 'Update of the SSM Firmware' before rebooting the system. Remove the configuration record tape from the tape drive and enter 'r', to reboot the system. You will now be booting off of your system disk. To install additional packages see Section 5.5 "Installation and Update of Optional Software Packages". 5.3.3 UPDATE OF THE SSM FIRMWARE The following steps outline the procedure to update the SSM firmware on disk. This procedure overwrites the SSM firmware already on the disk. This procedure would be required if on an OS Installation the steps to install the SSM firmware were skipped, new firmware was released and needed to be installed on the disk, or the SSM firmware on disk became corrupt. 1.2A includes a new version of the SSM firmware which needs to be installed. The following will be required to update the SSM firmware: o BASE Operating System Tape 1) From the standalone installation program menu choose option 's', for SSM firmware install. 2) You will be prompted to put the OS Release tape in the tape drive and enter to continue. Enter after the BASE OS tape is in the tape drive. 3) The SSM Firmware will now be copied to disk. 4) After the SSM Firmware is copied to disk you will be prompted with: Press to main menu, or "r" to reboot the system. Note: You must go all the way down so the new version of operational SSM firmware is loaded. Use 'ZAP' or power the system off/on from level 3 (--->). Remove the BASE OS tape from the tape drive and enter 'r', , to reboot the system. The installation of the SSM Firmware is now complete. 5.4 INSTALLATION/UPDATE OF THE SECURITY CONFIGURATION RECORD The following steps outline the procedure to install the BOSS/VX Configuration Record. This procedure installs a new configuration record on a system that doesn't already have one or overwrites the one already on the system. This procedure is used to install a configuration record on a new system if that step was skipped on the . OS Installation, put down a new configuration record if hardware changes require a new configuration record or over-write using the same configuration record if the configuration record on disk is corrupt. It will display the configuration record before installing it and give the option to install it or go back to the menu. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg018 The following will be required to install the Configuration Record: o BASE Operating System Tape (optional if booting off disk) o Configuration Record tape for the target system 1) It is assumed that the BASE OS tape is in the tape drive and that the system is at the level 3 prompt '--->', if not go to section 1.1 to boot the SSM firmware to the level 3 prompt. 2) At the '--->' prompt enter: install The following message will be displayed: 'Are you sure the installation tape is inserted (y/n)?'. Make sure the BASE OS tape is in the tape drive before entering 'y' . This will bring up the Standalone installation program menu. 3) From the Standalone installation program menu choose option 2 'Update Installation'. 4) A menu of disk drives the OS can be updated on will be displayed. Enter the drive number that the configure record is to be installed on. will cause the OS to be updated on the primary disk drive (wd0). A new mini-root will be installed on the target disk. After the new mini-root is installed the system will be booted on to the mini-root. 5) After the boot process is complete the '#' will be displayed. From this prompt enter: ./INSTALL This will bring up the BOSS/VX SOFTWARE INSTALLATION menu. 6) Enter option 'i', for Configuration Record install. The following message will be displayed: Please remove the release tape and insert the tape containing the configuration record. Press to continue: Put the tape containing the System's Configuration Record in the tape drive and enter . The configuration record on tape will be displayed and you will be prompted with: Do you want to install this configuration record (y/n)? If you enter 'y', , the configuration record will be installed. If you answer 'n', , the configuration record will not be installed and you will be taken back to the BOSS/VX SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg019 SOFTWARE INSTALLATION menu. 7) After the configuration record is installed you will be prompted with: Press to main menu, or "r" to reboot the system. Remove the configuration tape from the tape drive and enter 'r', , to reboot the system. The installation of the configuration record is now complete. 5.5 INSTALLATION AND UPDATE OF OPTIONAL SOFTWARE PACKAGES The following steps outline the procedure to install optional BOSS/VX packages, for example, ITP, MAI OFFICE, Presentation Services, tools, ORIGIN and other packages supplied in a BOSS/VX install format. The program lists the package(s) available for installation from the tape and allows you to install one or more of these packages at a time. It will install all programs required and prompt for a public key if one is needed. NOTE: If you are not sure if the package(s) you have received can be installed using this procedure, read the installation instructions that come with the package(s). All packages supplied on the BASE system tape can be installed by following this procedure. WARNING: If you are using this procedure to update an existing package, ensure you have a verified back-up of the customer's data files before attempting the update. The following will be required to install additional packages: o Tape containing the package(s) o Public key for the package(s), if required NOTE: INTERNATIONAL ONLY: Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 1) If the system is powered down, power it up and login as root/super-user in command mode. If the system is booted login as root/super-user in command mode. 2) Shut the system down to single user mode by using the command 'shutdown -i1 -gx' (where x= the number of seconds to wait). After the number seconds you gave the command has passed you will be prompted with: Type Ctrl-d to proceed with normal startup. (or give root password for system maintenance): enter the password for the root user. Next you may prompted with: Enter terminal type (default is TERM=dt4313) TERM= Enter your terminal type or . 3) At the command mode prompt enter the command mbfinstall . The following messages will be displayed: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg020 Installing products on / Insert tape and press when ready . NOTE: If you wish to install the package to a different directory other than '/' use the command 'mbfinstall /target_directory'. If the directory you wish to install the optional packages on has a different partition mounted to it, type the command 'mount' to ensure it is mounted before entering the mbfinstall command. 4) Insert the tape containing the package(s) you wish to install in the tape drive and enter . If the BASE system tape is being used for the installation, a message telling you that the tape is an operating system tape, followed by a prompt to continue is displayed. Enter . Messages will be displayed telling you the procedure is skipping to the product directory. Next, the MAI Product Installation Procedure menu is displayed. Each page of the display will contain up to 15 packages for installation. The display will have the package name and a short description of the package. The bottom of the display gives the installation procedure options. 5) Enter the number of the package(s) you wish to install followed by a . You can enter them in any order. If entering more than one package on a line follow each entry with a comma. The procedure will put them in the order they are found on the tape. After you enter a number you will be prompted with: Install Product(s) # Are you sure (y/n)? If you answer 'y', , to this question, the number will be added to the list and you will be returned to the menu. If you answer 'n', , the number will not be added and you will be returned to the menu. If you wish to install all the packages displayed, enter 'all' for all, . The installation of the packages will begin after you enter , you will not have to enter 'S'. If you wish to see the next page of the display, enter 'n' for next, . If you wish to see the previous page enter 'p' for previous, If you wish to abort the procedure and go back to command mode enter 'ab', . 6) After you have entered the number of all the products you want to install, enter 's', . The procedure will display the number and name of the package being installed. It will next install the package, displaying the files as they are being written to disk. 7) If a public id is required a message displaying the current public id and its length will be displayed after the package is installed, followed by: Enter an 8-char. new Public ID (Hit <0> for a Null Public ID or SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg021 for no change): Enter the public id you received with the package if it is different than the one displayed. 8) If you are installing more than one package, the next package will be installed. This will continue until all the packages you selected have been installed. After all the packages are installed, the procedure will take you back to command mode. You are now done with the installation of your package(s). If you wish to install additional package(s) from other tape(s) repeat this procedure to install them. 9) Enter '^d and 2' to return to multi-user mode or '^d and 0' to shut the system down. 5.6 CUSTOMIZATION OF OPTIONAL SOFTWARE PACKAGES The following sections include special instructions or installation procedures when installing the optional software packages. 5.6.1 MAI PRESENTATION SERVICES symbol 212 \f "Symbol" There are no special instructions for installation and customization of Presentation Services. Ensure the users Path includes the following to access Presentation Services: /usr/mbf/PS /usr/mbf/PS/tools 5.6.1.1 PRESENTATION SERVICES CUSTOM MENUS If the user has created their own menus through PS MENUBUILDER for either their own applications or OFFICE and ORIGIN, they need to transfer those files to the GPx Series 40 and 70 system using Intersystem Transport. The files to be transferred are as follows: SPx: names would be: ../PS/MSMF and ../PS/MSSF-->MENU FILES ../PS/MSH1 and ../PS/MSH2-->HELP FILES MPx names would be: .PS.MSMF and .PS.MSSF .PS.MSH1 and .PS.MSH2 5.6.1.2 PRESENTATION SERVICES FORMS When transferring forms to the GPx system, port only the source form files. Do not port the compiled form file. You will need to recompile your forms once you get them on the destination system. If the user has created their own forms through PS FORMSBUILDER, they need to transfer the following using Intersystem Transport. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg022 SPX: /PS/FS1.ENG /PS/FS2.ENG /PS/FS3.ENG /PS/FS4.ENG MPX: .PS.FS1.ENG .PS.FS2.ENG .PS.FS3.ENG .PS.FS4.ENG All programs created and associated files must also be transferred. Programs will need to be modified to use only BB90 directives. Bring the files over using cread but not doing the conversion during porting. Then run BQR to convert the files. After this is done, run MKCONVERT. 5.6.2 ORIGIN 2.1B GPx INSTALLATION PROCEDURE MODULES: ADS - Application Development Software DSS - Decision Support Software (MAI Business DATA) OTU - ORIGIN Translation Utilities WARNING: PLEASE, READ THESE INSTRUCTIONS CAREFULLY BEFORE INSTALLING THIS PRODUCT. Your system should be in single user mode. This ensures a safe product installation without conflicts with active systems users. You must be logged on as 'root'. This will avoid security conflicts during the product installation. Make a full backup of your product (programs & files) before installing this new version. The following Path names used are examples only and will change if you install the packages into a directory other than '/usr'. NOTE: INTERNATIONAL ONLY: MAI Presentation Services and ORIGIN 2.1B will not be included on the operating system tape, but will be delivered on separate tapes. 5.6.2.1 INSTALLATION REQUIREMENTS: New installations: o ORIGIN product tape. o The ADS public key, only if you are installing this module. o Minimum OS release level 1.2A o Presentation Services must be installed in the '/usr/mbf/PS' directory. o Disk space allocation for: ADS or DSS or (ADS + DSS): 8.16 MB OTU : 0.45 MB Each new user : 1.01 MB Each new project : 0.31 MB Updating: o The same requirements for a new installation, plus the following: o You must port all of your current ORIGIN data SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg023 files with any of the port tools available on your system. You must keep the directory distribution of those data files. (example: 'r20a/', 'r20a/data/', 'r20a/rt/' and 'r20a/pgm/'). WARNING: The only way to keep separate directories is to use a separate tape for each. cread will only restore to a single directory. o If you have a foreign language running with your prior ORIGIN level, port the files 'LLL003, 'LLL004' and 'LLL005' keeping their original location. 'LLL' means the selected language code used. o Copy any Menu Service File created to run within ORIGIN. (EXAMPLE: Menus in foreign language or your generated application menus). See Section 5.6.1 Presentation Services. Make a full backup of all ORIGIN program and data files, currently located at '/usr/origin/r21b and the directories in which your *DC0 files are located BEFORE installing this release. The *DC0 files (the technical documentation files) are normally located in your primary prefix or directory. NOTE: See appropriate sections in this document for backup procedures to use when converting from SPx or MPx. See Section 5.6.3.1 for MPx and Section 5.6.3.2 for SPx. 5.6.2.2 NEW INSTALLATION OF ORIGIN 2.1B 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 5.5. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 1.5. 4. Go into BASIC and start with 256 pages of memory basic s=256 5. RUN "UPDATE" from BASIC. During a new installation this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR .ORIGIN 2.1B, (CR IF NONE): If ORIGIN is to be installed on root SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg024 partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* directory. Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx D. If ADS is being installed, the prompt will appear for installing the security key. If not installing ADS skip to 'E'. SYSTEM SERIAL NUMBER: ####-######## CURRENT SECURITY KEY: ######## NEW SECURITY KEY: ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) NOTE: (fast message appears) SECURITY KEY INSTALLATION COMPLETE E. ORIGIN INSTALLATION COMPLETE. READY > You may now go to Step 6 or quit and shutdown before rebooting system. 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.6.2.3 UPDATING FROM 2.1A If you are updating from ORIGIN 2.1A to ORIGIN 2.1B,. the program UPDATE does NOT have to be executed. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg025 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.5. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 5.5. 4. Restore all your current Data Dictionary files from ORIGIN 2.1A to 2.1B, using the command cread. When the following prompt appears: Type the destination directory (max. 79 characters), (a default will appear) Example: Enter destination directory: /usr/origin/r21b. See WARNING in Section 5.5.2.1. Restore the cross reference files ORIPS4 and ORIPS6 using the same procedure. 5. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.6.2.4 UPDATING FROM 2.0A 1. Restore all files from tape following the directions for Installation of Optional Software Packages under Section 1.5. 2. Set your PREFIX to /usr/origin/r21b. From command mode: cd /usr/origin/r21b. 3. If not already installed, Presentation Services (PS) must be installed on your system using the directions for Installation of Optional Software Packages under Section 1.5. 4. Go into BASIC and start with 256 pages of memory SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg026 basic s=256 5. RUN "UPDATE" from BASIC. When updating from 2.0A, this program will convert your 2.0A dictionary files and user files into the corresponding 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) If ORIGIN is installed on root partition; else, enter the partition name (i.e., '/usr2') and press . B. ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION : /usr/origin/r20a C. CR TO PROCEED WITH UPDATE, CTL-IV = EXIT : This will copy the following files from the R20A directory into the /usr/origin/r21b/data directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC D. IDD CONVERSION COMPLETE TO CONTINUE: This continues the installation of the R21B Runtime files. E. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /usr/mbf/bin CR TO PROCEED, CTL-IV TO END: This will copy the files contained in the runtime directory, /usr/origin/r21b/rt/* into the /usr/mbf/bin/rt/* Example: /usr/origin/r21b/rt/ENGxxx --> /usr/mbf/bin/rt/ENGxxx 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the /usr/origin/r21b/language directory. These utilities are used primarily by international sites to translate ORIGIN from English to a SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg027 different language. To delete this node, enter the following from command mode: cd /usr/origin/r21b/language rm * 5.6.2.5 INSTALLATIONS UPDATING FROM 1.3B OR 1.3A NOTE: The update from 1.3B to 2.0A ORIGIN must be done on the. MPx or SPx machine that it resides on before moving it to the GPx machine to update to 2.1B. 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the /usr/origin/r21b/util directory. 1.3A Users: Follow the 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on Page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 5.6.2.3, "Installations Updating from 2.0A". 5.6.2.6 EXECUTING ORIGIN ON THE GPx Here are the steps for executing 2.1B on the GPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. From basic >start 256 >PREFIX "/usr/origin /usr/origin/r21b /usr/mbf/PS /usr/mbf/PS/tools" >run "ORIGIN" NOTE: Each path may require a prefix indicating the partition it resides on. 2. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Login. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg028 3. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. _____ Select User Maintenance, use the password "ADMIN". 4. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities. The password is ADMIN. _____ Select ORIGIN System Parameters Maintenance option. _____ Enter a Work Files directory by selecting Option 11. This directory will be the directory in which all of your temporary ORIGIN files will be created. Normally, this directory is "/usr/origin/work/". 5.6.3 CONVERTING ORIGIN GENERATED PROGRAMS FROM MPx OR SPx TO GPx It is possible to convert ORIGIN generated programs and data files from an MPx or SPx machine to a GPx machine. Before performing the transport, ORIGIN should be at a minimum level of 2.0A and a backup of the ORIGIN generated applications should be performed. 5.6.3.1 MPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 5.6.2.4. 2. Perform a verified backup of the ORIGIN system. 3. Using the Directory utility, create a filelist containing all generated programs, data files, technical documentation files, and Integrated Data Dictionary files. Example: .USR.ORIGIN.JKSF01 ---> data file .USR.ORIGIN.JKSF02 ---> data file .USR.ORIGIN.JKSFM2 ---> Application Generated Program .USR.ORIGIN.JKSFM1 ---> Application Generated Program .USR.ORIGIN.JKSR01 ---> Report Generated Program .USR.ORIGIN.JKSR02 ---> Report Generated Program .USR.ORIGIN.xxxDC0 ---> Technical Documentation File .ORIGIN.R20A.DATA.IDD000 ---> Integrated Data Dictionary Files NOTE: The Data Dictionary Files all begin with IDDxxx and reside in the .ORIGIN.R20A.DATA. node. xxxDC0 is the technical documentation file where xxx represents user code. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg029 NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Run "BQR" utility and create a BQR filelist from system filelist created with directory utility. 5. From commaMCSI to initiate Intersystem Transfer and save files to tape. 6. Restore Intersystem tape to GPx system using cread utility. Set cread utility to convert and log errors during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 5.6.3.2 SPx TO GPx CONVERSION 1. Convert ORIGIN generated applications to 2.0A (minimum release level) if not already done. For information on how to convert to 2.0A, please refer to Section 5.6.2.4. 2. Perform a verified backup of ORIGIN system. 3. Create BQR filelist for transport. For example: /usr/origin/JKSF01 ---> data file /usr/origin/JKSF02 ---> data file /usr/origin/JKSFM2 ---> Application Generated Program /usr/origin/JKSFM1 ---> Application Generated Program /usr/origin/JKSR01 ---> Report Generated Program /usr/origin/JKSR02 ---> Report Generated Program /usr/origin/xxxDC0 ---> Technical Documentation File /origin/r20a/data/IDD000 ---> Integrated Data Dictionary Files NOTE: The path used on the source system must be maintained on the destination system. Because cread will only allow you to rename or restore into a single destination, separate tapes must be used for each destination. 4. Using cwrite utility, write BQR filelist to tape. 5. Restore Intersystem tape on GPx machine using cread utility. Set cread utility to log and convert during the transport. NOTE: Multi-keyed files are not supported for Intersystem Transport on OS levels prior to BOSS/VS x.6G or BOSS/IX 7.5B. 5.6.4 ORIGIN 2.1B NEW FEATURES o Mask overflow control on report: Any ORIGIN generated report will print asterisks on numeric items with mask overflow. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg030 o 132-column support on terminals: If you are printing a 132-column report on a terminal that supports 132 columns, the report will be displayed in 132-column format. o Footnotes logic: You may define footnotes to be printed by your ORIGIN generated reports. o Generated report options file linked for re- generations: If you select to regenerate an existing report, and the options file for that report happens to be on-line in the current user prefix list, ORIGIN will 'compile' that option file to avoid lack of integrity between the 're-generated report' and the 'old option file'. o Derived items condition: You may define one condition within the derived item expression to assign two possible values to the same derived item upon the condition evaluation. o Usage rights: ORIGIN will define any file with 'free' usage rights. (MPx: W(*.*), SPx: -rw -rw, GPx: -rw-rw-rw). This will avoid security conflicts. o Spool attributes: Any ORIGIN report will prompt you for system spooling attributes, like class, copies and priority. 5.6.5 TRANSLATION These translation instructions assume you will be using a previously translated version of ORIGIN 2.1B. o You must have the ORIGIN 2.1A files listed below. /pgm/ENG004 - ORIGIN message file (English) /pgm/ENG005 - ORIGIN screen file (English) /rt/ENG* - ORIGIN runtime programs (English) /pgm/ENG* - ORIGIN shells (English) -and- /pgm/SPA004 - ORIGIN message file in foreign language (**) /pgm/SPA005 - ORIGIN screen file in foreign language /rt/SPA* - ORIGIN runtime programs in foreign language /pgm/SPA* - ORIGIN shells in foreign language ** SPA will be used as the language code in this document. o You must have ORIGIN 2.1B installed on your system. Please be sure the /usr/origin/r21b/language/* directory is installed to provide all the needed tools to translate ORIGIN. MESSAGE TRANSLATION o Set your prefix to work with ORIGIN 2.1B and perform the following procedure to define your language code: RUN "ORIGIN" -> (perform log-on if necessary) -> Main MENU -> Utilities menu -> System Administration Utilities -> -> Password (ADMIN) -> Language Translation Menu -> SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg031 Language -> Maintain Language -> Enter the language code -> -> Done, you may go to console mode at this point. o You must copy the 'SPA004' and 'SPA005' DATA files from their ORIGIN 2.1A location into the ORIGIN 2.1B. If they. already exist on 2.1B you should delete the existing 2.1B files. o You must compare (with the system compare utility, bcompare) the ORIGIN 2.1A ENG004 files with the ORIGIN 2.1B ENG004 file, to get a report with the new, modified and deleted messages on ORIGIN 2.1B. The file ENG004 has 1800 records and only 36 new records in 2.1B, so expect around 100 messages (new and modified) to be translated in order to have the 2.1B message files. o You must compare (with the same utility) the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 files, to get a report with the new, modified and deleted screens on ORIGIN 2.1B. o You may use the ORIGIN language translation utilities to update the messages and screens reported with differences in the compare report. PROGRAM TRANSLATION (RUNTIME AND SHELL) o Using with the system compare utility (bcompare), compare all the programs that start with 'ENG', located under the ORIGIN 2.1A runtime directory (/rt) and program directory (/pgm) with its similar program located under the same node on ORIGIN 2.1B. This compare will help us to decide translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B, which will allow us to use the current translated version of this program: . Copy into ORIGIN 2.1B the current 2.1A SPA version of the program. . Update the new 2.1B version of the program with the statements shown in the compare report. - A large message report means that the program was heavily modified from 2.1A to 2.1B, so a re-translation of this program is recommended: . Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with SPA*. (EXAMPLE: the program /rt/ENGNNR has to be copied to /rt/SPANNR within ORIGIN.R21B.) . You must get a report with all the MESSAGES used in this program, everything within quotes ("). You need to translate all these messages by editing each statement. NOTE: There are few message changes within the runtime and shell programs, so the same messages report from your old SPA program will help with this task. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg032 WARNING: Take care about translation impact in the program flow. The translation could affect the program flow, so users should not use the product until translation is complete. 5.6.6 DOCUMENTATION Manual Number Part Number Pages Title M7511E 007511-012A 170 MAI Business DATA Report Program Generator User Guide M7573C 007573-002A 118 MAI Business DATA Technical Reference M0058C 910058-002 132 MAI ORIGIN User Guide for Running Reports and Programs M0060C 910060-002 228 MAI ORIGIN Application Generator User Guide M7512D 007512-002 112 MAI ORIGIN Application Generator Technical Reference Manual M7510E 007510-002A 214 MAI Business DATA System Support Manual M7557G 007557-011 74 MAI Business DATA User Guide . M7561E 007561-002A 166 Presentation Services Menu and Help Management User Guide M0144B 910144-002 328 Presentation Services Forms Management User Guide 5.7 ETHERNET AND TCP/IP For those systems where TCP/IP is not already installed, the following is the installation procedure for Local Area Network (LAN) and Transmission Control Protocol (TCP). 1. Ensure that your system is properly connected to the network, and that you have installed the Eagle Ethernet Controller (refer to the GPx Series 70 Installation and Maintenance Manual, M8226). 2. Mount the operating system release tape that contains the TCP/IP files. 3. Shutdown the system to single-user mode. At the command prompt, enter mbfinstall. From the list on your screen, select both the LAN and TCP products to install. NOTE: Select LAN first, as LAN should be installed before TCP. The system prompts you to confirm your selections. Files are restored from the tape, and you are prompted for controller and public key information, as explained in the next steps. 4. ENTER LOCAL AREA NETWORK CONTROLLER INSTALLED: o Eagle Ethernet Controller o SCED Ethernet Controller o Eagle and SCED Ethernet Controllers o None Enter the option number for the Eagle Ethernet Controller, which is the only controller presently supported on GPx 70. 5. HOW MANY EAGLE ETHERNET CONTROLLERS ARE CONFIGURED?: SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg033 Enter the number of controllers configured. 6. Changing network configuration will update the following files /etc/hosts, /etc/hosts.equiv, /etc/netconf, /etc/inetd.conf, /etc/services and destroy the previous configuration. Do you want to change network configuration (y/n)? (CR=no) NOTE: You must enter 'y' to install the product. NOTE: Answer 'n' if doing an operating system update. 7. ENTER THE INTERNET ADDRESS: Enter the Internet Address. Assuming you are installing the network for the first time, you must assign a series of Internet addresses to the various devices on the network. It is highly recommended that an address of 97.0.0.1 be used as a starting point. The additional devices on the network can be set up as 97.0.0.2, 97.0.0.3, etc. 8. ENTER PUBLIC KEY (8 CHARACTERS): Enter the public key. The system prompts you to enter the key a . second time for verification. Because TCP/IP is an optional, chargeable feature, a public key unique for your system serial number must be installed. If you do not have a public key, contact your MAI representative. You may enter the key later by using the install_key command. 9. You must assign a unique name to the system using this command: #uname -S . 10. After installing TCP/IP and a public key, shut the system down (to the firmware level), and reboot the new TCP kernel to enable Ethernet operations. 11. Edit the /etc/hosts file. Add the name and IP address of your system; then add the name and IP address of a second system on the same network. For example, the /etc/hosts file for a system named mfg1 contains the following entries: # # Host Database # This file should contain the names and addresses # for local hosts that share this file # # If the name server is running this file is not consulted # # Choose a distinguished local network address for local host. # 127.0.0.1 loopback lb localhost # #Imaginary network 97.0.0.1 mfg1 #this host 97.0.0.2 mfg2 #second system 12. You can now communicate with the selected system using SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg034 applications such as rlogin, rcp, or ftp. NOTE: If terminal servers are going to be used, the ntcp parameter in a dct file will need to be set to at least 1-1/2 times the number of terminal server ports. 6.0 PROBLEMS FIXED IN THIS RELEASE This section provides a list of some of the problems that have been corrected in 1.2A. 6.1 BASIC -'INITFILE' no longer breaks links to other file names. . -Writes to KEYed files using the IND= option will no generate an error if the index value is that of a deleted record (part of the free record chain). An error 13, system error -109 will now be returned. -User prefix is no longer changed after doing a START. -'LIST PROGRAM' now works as designed from a CALLed program. 6.2 OPERATING SYSTEM -Change user profile script to ask if terminal support upper case characters only when user logs on using upper case characters. -A CPU is no longer constanly busy if a printer is configured on the SSM but not actually connected. -Disconnect on break now works properly when logged in to a system over a modem. -An I/O error is no longer produced the first time a HCC tape drive is accessed. -A SSM hang will no longer occur if a DataProduct printer connected to the SSM is powered off while a job was printing. 6.3 DIAGNOSTICS -Diagnostics now run when '/usr/ob/bin' is the first part of the user's path. The system serial number is used to validate the key. -'bbmap' has been corrected to return correct information in some cases that it did not 6.4 COMMUNICATIONS -TCP/IP no longer slows down after a couple of days if the system is not rebooted. -'rtelnet' and 'aprint' have been added to the TCP product. -'rlogin' no longer invokes unidiretional software flow control. 6.5 UTILITIES -man pages 'lpr' now indicates that forms do not work with non-spooled printers 'cpio' now states that temporary space for journaling is allocated on the file system containing the current working directory when cpio is started. . 'olb' now states that temporary space for journaling is allocated on . the file system containing the current working directory when olb is started. -'configure' no longer allows a slave printer to be defined on the system console. -'configure' will no longer supports the option to switch two devices which caused the LP port to change to a terminal device type. -'fcreate' no longer clears header and working directory when going into the utility. -Output from utilities to a slave printer will no longer cause the port to hang under certain situations. SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg035 -'frepair' no longer exits if a file is found un-repairable when using a filelist. -'frepair' now fixes more types of file corruption problems. -'sar' no longer reports more jobs waiting for I/O than actually waiting. -Backups using cpio no longer gets the error message "Encountered an error on output, errno 22, Invalid argument - cat: output error (-1/8192 charactes written) - Broken pipe" when the cat command with huge filelists. -'cread' no longer skips files during the restore. -'mbfinstall' now works if '/usr/ob/bin' is the first part of the root user's path. -'bsearch' will now find search patterns at end of statements when BASIC CODE ONLY and VARIABLES ONLY are selected. -'pqueue' now displays 8 characters of the users name. 6.6 PRINTERS -Jobs sent to offline 4229 printer no longer results in multiple form feeds and garbled output. -Slave printer are no longer displayed in certain spooler utilties such a 'pformchg'. -With initial form feed set to 'yes' and a job is waiting for a printer that is off-line, the data on the first page is no longer printed twice once the printer is put back on-line. -Doing a 'pformchg' will now print tial forms using live data when the @ positioning is used in the print job. -The 4224 now correctly initializes at open with correct VFU and pitch. -4217/4218 printers will now print last line without having to issue a form feed. 6.7 PATCHES INCORPORATED INTO THIS RELEASE -Patch 43: Fix for garbage data and form misalignment when the printer was off-line. -Patch 45: Origin patch for Level 2.1B*23. -Patch 48: Allows printers to work through terminal servers. -Patch 52: System hangs due to bug in streamio.c module. -Patch 57: VME interrupt fix. ORIGINATOR: Dale Jensen MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB055 Pg036 FIB 00056 MAI COMPANY CONFIDENTIAL 08/17/93 *** 1.2A*07 available for GPx70 *** PRODUCT : GPx SERIES 70 TYPE : INFORMATIONAL SUBJECT : 1.2A*07 RELEASE A new version of 1.2A is now being shipped. The new version is 1.2A*07 and it replaces the 1.2A*05 version. Below is a list of the major enhancements to this version release. 1. Fix to 'tar' To allow multi-tape backups. 2. Added statements to 'OLB' man pages regarding temporary disk space allocation. 3. Added files to tps software for WORD PERFECT, 2020, LOTUS123 and SYBASE for enhanced terminal definitions. 4. System hang caused by 'BDFLUSH' looping forever. 5. Fix to 'pqueue' of an erroneous error message when modifying a job. 6. Speed up of basic in handling slave printer closes. 7. Fix to 'fchange' which corrects possible file corruption when maximum number of records is reduced on keyed files. 8. Fix to 'frepair' to continue if next record pointer is beyond max records. 9. Added checks to avoid system crash with certain types of file corruption. 10. Corrected cause of system crash when '/dev/kmem' was opened. 11. Corrected cause of system hang when the error log process was swapped out with a file system lock in use. This is the recommended release of 1.2a. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB056 Pg001 FIB 00057 MAI COMPANY CONFIDENTIAL 04/05/94 *** Release 1.2A*08 available for GPx70 systems *** There is a new release for the GPx70. It is 1.2A*08. This release will be sent to all of our GPx70 customers that have service. To upgrade the system with this release use the 1.2A upgrade instructions. Following is a list of fixes/enhancements: 1. A dct file was created for a 128MB system. 2. A problem was found that if a printer was set-up with despool wait, the despooler would tie up a cpu while the printer was open. This was only seen using OpenBASIC. This problem has been fixed. 3. A problem was found were keyed files would get corruption when using rfa. This problem was been fixed. 4. The following disk drives are now supported: Seagate ST11200, Seagate ST11900, and Fujitsu F2694. 5. There is now support for the Exabyte 8500 8MM tape with compression. 6. Directory cache sizing is now looked at in the dct file. It was ignored before. 7. A fix was put in to correct a directory lookup problem that would cause a system hang. 8. A warning message will now be displayed on the console if a streams buffer or message buffer overflows. After this warning is displayed the problem needs to be corrected as soon as possible to avoid a system hang. 9. The 'sync' command was improved to provide better integrity of the files. Again please upgrade your customer's systems as soon as possible. ORIGINATOR: Wally Moore SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB057 Pg001 FIB 00058 MAI COMPANY CONFIDENTIAL 12/02/94 *** DON'T use OS level 1.1C*9 on GPx240 systems! *** SUBJECT: NEW RELEASE OF OPERATING SYSTEM 1.1C *9 PROBLEM: DOES NOT SUPPORT THE GPx 240 SYSTEM. PURPOSE: TO INFORM FIELD NOT TO INSTALL THIS OPERATING SYSTEM ON ANY GPx 240 SYSTEM. SYMPTON: SYSTEM WON'T BOOT. THE O.S. UPDATE WILL PROCEED AS NORMAL BUT WHEN REBOOTING THE SYSTEM WILL NOT BOOT. SOLUTION: A NEW OPERATING SYSTEM RELEASE WILL BE ISSUED SPECIFICALLY FOR THE GPx 240 SYSTEM SHORTLY, SO DO NOT INSTALL THE CURRENT ONE BEING SHIPPED TO CUSTOMERS. ORIGINATOR: Fred Chiuppi SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB058 Pg001 FIB 00059 MAI COMPANY CONFIDENTIAL 12/13/94 *** TCP/IP installation instructions for GPx40 *** Subj.: Installation of TCP/IP on GPX40 running BOSS/VX OS TYPE: INFORMATIONAL Here is a brief procedure for installing the TCP/IP product on GPx40 systems running BOSS/VX operating system. Requirements: Hardware: GPx40 system with Ethernet Controller (jumpered properly) Software: BOSS/VX 1.1A min.(recommend 1.1C*08 or >) with TCP/IP product Other: IP addresses for the GPx40 system and any other hosts to be connected. Public key for TCP/IP product for GPx40 system Method: 1. Log in as root (preferrable in single-user mode) (If in multi-user mode, ignore warning about being in sigle-user) 2. Invoke "mbfinstall" to install the product. #mbfinstall ... press return when prompted to insert tape ... Operating System tape format. press to continue . Skipping boot section . Skipping base section . 11 ... Select product # -11:TCP (Unix Networking & Term. Serv.) y ... Install product 11. Are you sure (y/n)? s ... Press 's' to start installation of product The system will display Skipping product #n ... until it gets to the desired product number (11) The screen will clear and display Installing TCP/IP and the files. (public-id) ... Enter TCP/IP public key supplied by MAI The installation will then commence until you see: Product Installation Complete. Rewinding tape . 3. Change the system name using the 'uname' command: #uname -S # is your choice The system name will be changed to the you typed in above 4. Add network addresses to the /etc/hosts file: #vi /etc/hosts (insert IP address and name of system) 129.64.100.1 #IP for your host 5. The IP addresses of any other systems which will communicate with the host must be entered in the /etc/hosts file. 6. Reboot system in multi-user mode and log in as root. 7. Test to ascertain that the installation succeeded by 'pinging' host # ping If you see something similar to the message below repeating, you are communicating. PING : icmp-seq=nn time=nn ms SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB059 Pg001 8. You may then terminate ping by typing . You will see a summary message as follows: ---- PING Statistics nn packets transmitted, nn packets received, 0% packet loss round-trip (ms) min/avg/max = nn/nn/nn ORIGINATOR: Eugene Okafor SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB059 Pg002 FIB 00060 MAI COMPANY CONFIDENTIAL 02/10/95 *** BOSS/VX 1.1C*10 reguired for all GPx40 Sytems *** SUBJECT: New release of BOSS/VX 1.1C*10 operating system and diagnostics for all gpx 40 series systems. TYPE: Problem PURPOSE: Inform field that this new O.S. is a required upgrade for all prior boss levels to resolve existing O.S. and SSN module problems. PREREQUISITE: This operating system requires a minimum of 8 megabytes of memory. A configuration record is required if upgrading from operating system level 1.0. If customer is on operating system level 1.0 and is configured for 4 mb of memory it is recommended to upgrade to 8 mb of memory before upgrade is done. MODIFICATIONS: * IMPROVED SYSTEM CHECKS TO DETECT KEYED FILE CORRUPTION TO PREVENT ERROR 7'S. * IMPROVE KEYED FILE INTEGRITY BY SYNCING BUFFER CACHE BEFORE UPDATING KEYED FILE HEADERS. * CHANGES TO DESPOOLER TO PREVENT SYSTEM PROCESSES FROM LOOPING THAT CAN CAUSE PERFORMANCE PROBLEMS. * IMPROVED CHECK FOR MBF SYSTEM CALLS TO ALLOW XENIX EMULATION CALLS ABOVE 4096. * ENHANCED SYSTEM SERIAL NUMBER CHECKING. PROCEDURE: Installation and update procedures can be found in the GPx series 40 1.1A sofware announcment #191 (FIB 35). NOTES: This release of the operating system will be required to prevent security panics due to defective SSN modules. The 1.1C*09 release will NOT work on the GPx240 systems, use the 1.1C*10 release for ALL GPx40 systems. Order 1/4" tape media from software distribution: W514129-217 - BOSS/VX 1.1C*10 BASE DOMESTIC W514751-311 - BOSS/VX 1.1C Diagnostics ORIGINATOR: Fred Chiuppi MODIFIED by: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB060 Pg001 FIB 00061 MAI COMPANY CONFIDENTIAL 03/20/95 *** Large filesystems fail to repair automatically - modify mountall *** Large filesystems (typically over 1MB) fail to repair automatically after a panic, powerfail, hang, etc. There is a message asking for a scratch file name but the system continues on without repairing the large filesystem. After the system is up the large file system has to be repaired manually using fsck, then when fsck asks for a scratch file name it can be entered. The following modification to /etc/mountall adds the option (-t /tmp/fix) to fsck allowing fsck to use a /tmp file as scratch area if memory is insufficient to hold its tables. NOTE: Make a backup copy of /etc/mountall first. vi /etc/mountall Locate the following line: (to search: /fsck) /etc/fsck -y -D -l ${dev} # -l option added by MBF Insert the -t /tmp/fix option (let line wrap around, don't CR in the line): /etc/fsck -y -D -t /tmp/fix -l ${dev} # -l option added by MBF. The scratch file (/tmp/fix) will be deleted automatically when fsck completes. ORIGINATOR: Norm Jones SOFTWARE-BASIC FOUR-BOSS/VX BB90--------------------FIB061 Pg001