MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MICRO,MINI,LARGE MFG: HEWLETT PACKARD NACS TYPE(S): N021 MFG. MODEL(S): HP -UX OPERATING SYSTEM CATEGORY: SOFTWARE DESC: HP *** TABLE OF CONTENTS AS OF 11/10/95 *** FIB 00001.BACKUP PROBLEMS.............................................05/28/92 FIB 00002.MAI Printers Running under HP OpenSpool.....................06/17/92 FIB 00003.How to configure HP DTC 16 [ WPSF 776 ]....................02/02/93 FIB 00004.C ANSI C problems when upgrading to HP-UX 9.0...............03/08/93 FIB 00005.HP-UX 8.0 to 9.0 Upgrade....................................03/09/93 FIB 00006.Core Dumps..................................................03/09/93 FIB 00007.Uniplex not certified on HP-UX 9.0..........................03/15/93 FIB 00008.Terminals on DTC servers hang after using CTL+S.............05/28/93 FIB 00009.Problems restoring files from 'tar' backup tape.............05/28/93 FIB 00010.HP OpenSpool upgrade from A.01/A.02 to A.03.................06/10/93 FIB 00011.fbackup or automated SAM backup probs after upgrade to 9.0..08/17/93 FIB 00012.sysdiag problems after upgrading/installing HP-UX 9.0.......08/17/93 FIB 00013.patch PHNE_2631 needed when upgrading/installing HP-UX 9.0..08/17/93 FIB 00014.MAI printer problem after upgrade to HP-UX 9.0..............08/30/93 FIB 00015.DATE and TIME problems [WPSF 786]...........................10/01/93 FIB 00016.HP DTC "NAIL" Ports Patch [ WPSF 787 ].....................10/01/93 FIB 00017.How to start sar [ WPSF 779 ]..............................10/05/93 FIB 00018.HP.Notes & Special Considerations [ WPSF 751 ].............10/08/93 FIB 00019.'fuser' problem on HP-UX 9.0................................10/14/93 FIB 00020.HP-UX 9.04 release notes....................................01/28/94 FIB 00021.Problem with SAM displaying serial printers on HP-UX 9.04...02/21/94 FIB 00022.HP-UX 9.0 & 9.04 error 62 -46 (NFLOCKS).....................04/27/94 FIB 00023.ERROR "SAM EXPECTS (NCALLOUT >= NPROC) AFTER 9.04 UPGRADE...05/13/94 FIB 00024.new tool 'FreeDisk' available on HP-UX 9.x..................05/18/94 FIB 00025.SAM error in 9.04...........................................09/09/94 FIB 00026.SAM bug in HP-UX 9.04 - password visible during user reation09/27/94 FIB 00027.How to add a disk drive using colume manager................08/24/95 FIB 00028.errno script for getting description of system errors.......10/26/95 SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----Table Of Contents Pg01 of 01 FIB 00001 MAI COMPANY CONFIDENTIAL 05/28/92 *** BACKUP PROBLEMS *** HP Automated Backup created in SAM TYPE: Informational This is to inform the field of possible complaints from a customer who has created an automated backup through the SAM utility. The complaint may be one, both, or some variation of the following. 1. My automated backup takes more tape, eg: requires a second tape, than the same "fbackup" in single user mode. 2. My automated backup takes longer than a single user "fbackup". Basiclly SAM creates a "cron" entry, which kicks off an "fbackup" of a selected file system(s) at a predetermined time of day(s). This is the same "fbackup" one would use doing "fbackup" in single user mode, in that a retry means (skip . forward and start over). Both backups are of the whole system, but the mode of the system is the difference. If the "/etc/wtmp" gets modified during back- up, "fbackup will do a retry (start over). The "/etc/wtmp file is used in System Accounting in that it records all logins and logouts. This file would not get modified in single user mode, but in multiuser mode a login or out any- where on the system could make the backup take more tape and time. The solutions to this problem are any one of three. 1. Do the backup in single user mode. 2. Do a selective automated backup, where this file is excluded. 3. If not using System Accounting, delete this file. ORIGINATOR: M SHEHAN SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB001 Pg001 FIB 00002 MAI COMPANY CONFIDENTIAL 06/17/92 *** MAI Printers Running under HP OpenSpool *** PRELIMINARY FIELD BULLETIN HP OPENSPOOL with MAI Printers Joe Melendez TYPE : Informational The purpose of this Field Bulletin is to show how to make MAI printers work with HP OpenSpool software. It is assumed that the user has HP OpenSpool installed and has been trained on how to use this software. NOTE : HP and MAI recommends that the user contract at least 8 hours of consultation with HP in regards to training and installation of this product. OpenSpool uses HP printer drivers to support their printers and these drivers are not compatible with MAI printers. Also HP printers are configured with 8 bit no parity, while MAI printers are usually configured as 7 bit odd parity. The following steps will correct the driver and configuration setup problems : A) Set dumb as the MAI printer driver for MAI printers. 1. Log-on as spooladm 2. Change to superuser (su) 3. Copy (cp) /usr/spool/lp/model/dumb /usr/lib/openspool/sw-master/customer-sw. /interface/s800/dumb 4. cd /usr/lib/openspool/sw-master/customer-sw/interface/s800 5. Modify dumb so that there will be no banner printed (Openspool can print it's own banner) and there will be no extra formfeed performed. vi dumb look for first banner entry it will show : banner="yes" and changed it to banner="" (which means no banner) look for the last echo "\014\c" and add a "#" in front of this entry (this is the formfeed) Save the vi changes. 6. Openspool files must have owner set to "spooladm" and group set to "bin" chown spooladm dumb chgrp bin dumb 7. Users rights of dumb must also be changed to "555" chmod 555 dumb B) To set PRINTER configuration to 9600, 7 bits, odd parity : 1. Same as steps 1,2 from above (if necessary) 2. cd /usr/lib/openspool/sw-master/hp-sw/linesetting 3. Copy the HP printer settings to a mai printer setting : cp printer.9600 printer.mai SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB002 Pg001 4. Modify the /bin/stty entry in printer.mai file : vi printer.mai change the /bin/stty entry to : /bin/stty raw 9600 opost parenb parodd cs7 ixon -istrip clocal tab0 <&1 >/ dev/null save the vi changes. 5. Make sure that User rights, owner and group are set correctly (see steps 6, 7 from step A) for the printer.mai file. This will setup the printer cofiguration settings to 9600, 7bits, oddparity. When configurating the MAI printer in OpenSpool (Adding a DEVICE) in the option "Interface program " specify dumb and in the option "Linesetting program " specify printer.mai. After adding the device chose the "ACTIVATE" option and when this is completed you will be able to use the MAI printer in OpenSpool. OpenBASIC with OpenSpool notes : When installing OpenSpool the unix spooler is deactivated (lp commands) and in its place the OpenSpool commands are activated (np commands). OpenBASIC was designed to use the standard unix spooler commands and OpenBASIC commands such as dedicate_p, free_p cannot be used. You can not use OpenBASIC "CONFIG" to configure printers and you will have to modify OpenBASIC configuration files in order use printers already configured before OpenSpool was installed. Please refer to Field Bulletin 737 (OpenBASIC / OpenSpool Configuration Notes) for info on how to modify these files. With OpenBASIC 3.0 you can use the OPTS= option when opening the printer. With the "OPTS=" option you can specify OpenSpool commands as well as OpenBASIC UPDFILTER commands to control mnemonics, character translations and forms option (# of copies, queues, banner, etc). By just changing the statement that opens the printer you can control most functions of the spooler. For example if you want a print job to go to a queue called MAI with a form called CHECKS and print in 8LPI on a printer called LP you can do the following: 10 OPEN(1,OPTS="-q MAI -P CHECKS -ul 8")"LP" The -q -P options are OpenSpool np commands and the -ul 8 is a OpenBASIC UPDFILTER command. You can combined both commands to handle any kind of print request. For more info regarding UPDFILTER you can do : more /usr/ob/docs/man/updfilter (OpenBASIC 3.0) For more info regarding np commands you can do : man np (on systems that have OpenSpool installed). IMPORTANT NOTE : This Field Bulletin is to help the field install MAI printers on a HP system that have OpenSpool installed. MAI Engineering or MAI NSC have NOT done any extensive testing with our printers using OpenSpool. We do not make any claims that all our printers will work with OpenSpool. However we will continue SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB002 Pg002 to work with OpenSpool and send information out to the field when we have more information available. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB002 Pg003 FIB 00003 MAI COMPANY CONFIDENTIAL 02/02/93 *** How to configure HP DTC 16 [ WPSF 776 ] *** In order to configure an HP DTC 16 you must first have the following: 1. Openview DTC manager/UX software installed 2. LAN device name (default name is : /dev/lan0) 3. LAN board installed and configured on the HP system 4. Know the IP addresses for the HOST system and the DTC (These arE user assigned). You must add these IP addresses (HOST and DTC name) in the /etc/hosts file. ex. 139.64.33.21 host system name 139.64.33.23 ditch (DTC name) To configure the DTC 16 you must perform the following (as root and on a HP terminal (use the 700/92 console terminal )). 1. Execute: dtcconfig 2. Select the option for adding a DTC and enter the DTC name. Example: dtc1 (same name used in the /etc/hosts file for the DTC name). select DTC 16("x" in this option) Press function key labeled "DONE" You will get the following screen: 3. Configure CPU Enter "c" and press function key "ACTION MENU" select "configure" option. Enter the following information: DTC nodename(ex. dct1.lab.MAI) lan address: see back of DTC for this Lan address. ex. 08-00-09-28-45-08. DTC IP address (same as the /etc/hosts file for dtcl). ex. 139.64.33.023 Destination IP address (same as /etc/hosts for HOST name) Example: 139.064.033.021 Event logging: should have an "x" next to number 1. Press function key "PERFORM TASK" The following screen will display to configure board 0 and board 1. o Enter 0 for board 0 and press the function key "ACTION MENU" o Select the "configure" option o Enter "x" for six modem port and press function key "DONE" o Enter 1 for board 1 and press the function key "ACTION MENU" o Select "configure" option o Enter "x" for eight direct port option and press function key "DONE" Now configure the ports for board 0 (six modem ports) and the ports for board 1 (8 direct ports). SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB003 Pg001 4. Config ports: o select board number for port configuration (ex. 1 (for 8 direct ports)) and using the right arrow key move it to the "port on board" option. o Select port number and press the function key "ACTION MENU" o Select "configure" option. o Change the baud rate and parity options to match your terminal. Other options should have default values . o Press function key "PERFORM TASK" o Screen returns to select the next port number and repeat the above steps. o After all ports are configured press function key "EXIT". You will get a message to save the current changes, answer "y". To download the configuration to the HP DTC 16 servers you must execute the following: o Execute /etc/rbootd /dev/lan0 (lan device name) o Execute /etc/dtcnmd /dev/lan0 (lan device name) (add the above in /etc/rc so that the DTC is downloaded at boot time). o Power up the HP DTC 16. Display leds will flash until it displays "F2" which means the DTC has been downloaded sucessfully. NOTE: Installation of DTC's is a billable option. ORIGINATOR: J MELENDEZ SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB003 Pg002 FIB 00004 MAI COMPANY CONFIDENTIAL 03/08/93 *** C ANSI C problems when upgrading to HP-UX 9.0 *** Subject: C ANSI C problems when upgrading to HP-UX 9.0 Author : Joe Melendez Type : Problem Purpose: To inform the field of a possible problem to customers that have the C ANSI C HP-UX product and are upgrading from HP-UX 8.0 to HP-UX 9.0 Symptom: When updating HP-UX 8.0 to HP-UX 9.0 the version of /bin/cc corresponding to the C Compiler that is bundled with the operating system is incorrect. The version string for /bin/cc is A.08.17 and it should be A.09.19. When compiling any source code, some or all of the following four messages will be displayed: $cc hello.c cc: warning 422: Unknown option "O" ignored. cc: warning 422: Unknown option "o" ignored. cc: warning 422: Unknown option "A" ignored. cc: warning 422: Unknown option "c" ignored. $ Solution: If you HAVE NOT updated your system to HP-UX 9.0: Before running update, type : rm /bin/c89 and then proceed with your standard "update" procedure. If you HAVE already updated your system to HP-UX 9.0: Login as root and type the following three commands: cd /bin mv cc cc.orig cp /system/C-MIN/scc /bin/cc NOTE: The second command (mv cc cc.orig) is to create a backup of the system's current driver. This is only a safeguard in case any problem were to occur while you are performing the above listed steps. You can remove cc.orig after you have run a test program and verified that your compiler and driver are the correct A.09.19 versions The above problem will occur only if you are performing an update to HP-UX 9.0 and will not occur if you are performing a new INSTALL of HP-UX 9.0. If you have any problems or questions please contact us at the MAI NSC. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB004 Pg001 FIB 00005 MAI COMPANY CONFIDENTIAL 03/09/93 *** HP-UX 8.0 to 9.0 Upgrade *** Subject : HP-UX upgrade from 8.0 to 9.0 Author : Joe Melendez Type : Informational Purpose : Help the field upgrade HP-UX 8.0 to 9.0 There are two ways of upgrading HP-UX 9.0 : 1. Update your system from HP-UX 8.0 to 9.0 staying with the same hard partitions (FILE SYSTEMS) that you had with HP-UX 8.0 2. Update your system from HP-UX 8.0 to 9.0 changing the hard partitions (FILES SYSTEMS) or convert these partitions to LOGICAL VOLUME MANAGER (LVM) With the HP-UX 9.0 tapes you will also receive a new set of documentation. Please have the "INSTALLING and UPDATING" HP-UX 9.0 manual available (we will reference this manual by sections) while performing this upgrade. Example : For more info regarding LVM please see refer to section 1-3. Steps for option 1 (maintaining hard partitions) are as follows : NOTE 1 : Before proceeding with the update procedure please make sure that the customer has a full backup of the system. (Backup should include : User's application software, Important HP-UX files (see section 3-8 to 3-11 for info) You should also include /etc/gettydefs as part of these files, also .profile for all users defined on the system) and the OpenBASIC files /usr/ob/etc/devices and /usr/ob/etc/bfsdevs). 1. Locate the HP-UX tape labeled "CUSTOMIZED SOFTWARE RELEASE 9.0). 2. Make sure that all products that the customer had with HP-UX 8.0 are on the HP-UX 9.0 customized tape (Please call the MAI NSC if you need help). Example : The number of license user's are the same number that HP-UX 8.0 had. NOTE 2: If the customer has OpenSPOOL he will need to have version A.03 (Previous versions of OpenSPOOL are NOT compatible with HP-UX 9.0. Please call the MAI NSC if the customer does not have OpenSPOOL version A.03. It's recommended that this version be first installed and running with HP-UX 8.0 before upgrading to HP-UX 9.0. 3. Log-on as root and make sure your are in the root directory and that you are. the only person logged on to the system. Shutdown the system and reboot in single user mode (shutdown -y 0). 4. Mount the CUSTOMIZE SOFTWARE 9.0 tape in the tape drive and perform : tar -xvf /dev/rmt/0m TOOL (0m should be the device name for the dat drive) This will restore the fileset TOOL (see section 7-15). This fileset contains the new version of the /etc/update utility. The HP-UX 8.0 version of /etc/update can not read a HP-UX 9.0 tape (you will get the following message : "Update requires A.B8.05. Version is A.B8.00"). 5. Run /etc/update. Select Filesets to be restored (please refer to section J for info on PRODUCTS and FILESETS). You can restore all FILESETS on tape and later if you want to remove any FILESETS (like ARABIC language) you can run the /etc/rmfn utility (see section 8-17 for info). After selecting the SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB005 Pg001 FILESETS to be restored select the "START LOADING" function key to start loading down these file sets. Please refer to sections 7-17 and 7-18 and sections 7-21 and 22 for more info. After restoring these filesets the system might have to reconfigure the kernel and it will reboot the system. After the system reboots, the update has been completed. You can check the /tmp/update.log file for info regarding any problems found during this update You can also check the /etc/newconfig/90RelNotes/hpuxsystem file for info regarding new, changed, or removed 9.0 features. 6. You have completed the update to HP-UX 9.0. You can restore any non-core software that the customer might have (like new version of GLANCEPLUS) if this applies to this user. All previous log-ons (password, .profile, etc) should still be on the system and you should have no need to restore any information from the backups that you made (see right above step 1). HP-UX 9.0 is totally compatible with OpenBASIC 3.0 and OpenBASIC 4.0. Installing or Upgrading HP-UX 9.0 is the user's responsibility (As per HP). MAI/HP on site support should be billable. If you have any problems with this update please refer to section K "Troubleshootings an Update" or contact us at the MAI NSC. See attached OMS for instructions on option 2 (HP-UX 9.0 upgrade to LVM). Steps for option 2 (Changing Hard Partitions to LVM) are as follows : Since changing hard partitions (FILE SYSTEMS) will delete the information on these partitions you will have to make a full backup of the system. Please refer to NOTE 1 in option 1 for info regarding what files to backup. The customer should also have the OpenBASIC tapes on site (all products) and also have the proper registration keys for these OpenBASIC products. 1. Follow Steps 1 and 2 and NOTE 2 in option 1. 2. Restore lvmmigrate tool from the CUSTOMIZE SOFTWARE 9.0 tape (Please refer to section 3-15) or see step 4 in option 1. 3. Run /etc/lvmmigrate (refer to section 3-16 to 3-20 for info). This will printout your current FILE SYSTEMS that need to be migrated to LVM. Also it will provide you with the hpux install path (Example : hpux install to (52.6.0;2) (52.0.0;0):INSTALL). Please copy all info displayed by lvmmigrate. You will need this later in the install process. 4. Mount the HP-UX 9.0 INSTALL tape in the tape drive. 5. Follow step by step process in section 4-1 to 4-7. In step 4 (section 4-6) at the ISL prompt enter hpux install to (boot_path). enter the info that lvmmigrate gave you as the boot path (step 3 option 2) Example : hpux install to (52.6.0;2). DO NOT include (52.0.0;0:INSTALL). Here is the recommended info to enter for step 5 section 4-7. Do you want a full install (y/n/) ? SELECT y Do you want to install a Logical Volume System (y/n)? SELECT y (for LVM) Enter Root Size in Mega Bytes, range 104-592 : See info from lvmmigrate. (note that entering a size greater than 200 will prevent LVM from creating logical volumes for file systems such as /usr) Enter Swap size in Mega bytes, range 48-138: see info from lvmmigrate. Enter file system filenames type, long or short : SELECT s System will start downloading files. After completing downloading of files the system will reboot. SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB005 Pg002 6. System reboot and Initial loading. Follow step by step process in step 6 of section 4-8 and 4-9. At the prompt to change media (section 4-9) remove the INSTALL 9.0 tape and mount the CUSTOMIZED SOFTWARE 9.0 tape. 7. If you selected "y" for lvm in step 5 continue with chapter 5. If you want to repartition the File System without lvm see chapter 6. 8. Create LVM Volume group. (Chapter 5). Create /, swap and /usr partitions as LVM (you can also recreate your other volume groups here also or you can do this using the SAM utilities after the update has been completed). Follow step by step process (section 5-1 to 5-10). You should select the option to restore all FILESETS from the CUSTOMIZE SOFTWARE 9.0 tape. (see step 5 option 1 for info). After the filesets completes loading it will run customization scripts and it will asked you to enter info (Time Zone, Time/Date, Networking (if applicable)). Please refer to section 5-6, 5-7 for info. You can continue with Chapter 8 (Post Install) and skip step 9 (Hard Partitions without lvm) 9. Chapter 6 is to install HP-UX 9.0 without lvm and changing the File System partitions. Please refer to section 6-1 to 6-11 for info. 10. System will reboot. If the system does not do a autoboot (asks you if you want to boot from primary path) you will can set the autoboot by doing the following : At the Primary boot prompt type : n At the Alternate boot prompt type : n At the Interact with IPL prompt type : y At the ISL prompt type : autoboot on At the ISL prompt type : autosearch on At the ISL prompt type : reboot The system will reboot and should not ask you for primary boot path. After rebooting you have completed with the update and install of lvm on HP-UX 9.0. Customer should then proceed to create their other lvm groups (see step 8) if necessary or restore backups of the necessary O/S files (like /etc/passwd, /etc/hosts, /etc/inittab, /etc/gettydefs, /etc/conf/gen/S800 (if cust. had modify the 8.0 HP-UX kernel you should restore this file and compare it to the . new 9.0 kernel and modify the new one), user application software and OpenBASIC and re-install activation keys (if on OpenBASIC 4.0) or registration keys (if on OpenBASIC 3.0). After restoring OpenBASIC restore the /usr/ob/etc/devices and /usr/ob/etc/gettydefs. (You should not have to reconfigured any devices in OpenBASIC). Please refer to section 8 for more info on Post Install tasks. You can check /tmp/update.log for any problems found with this upgrade. You can also check /etc/newconfig/90RelNotes for info regarding new, changed or removed 9.0 features. NOTE : After restoring /etc/inittab and /etc/gettdefs if you get any getty errors (like for modem ports) you can go into SAM and remove and re-configure these ports. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB005 Pg003 FIB 00006 MAI COMPANY CONFIDENTIAL 03/09/93 *** Core Dumps *** SUBJECT : HP-UX & OPENBASIC CORE DUMPS AUTHOR : JOE MELENDEZ TYPE : PROBLEM PURPOSE : INFORM THE FIELD OF CORE DUMPS ON HP-UX SYSTEMS SYMPTOM : Core Dump, Terminal releases BASIC and displays "$" prompt (sometimes terminal will hang at "$" prompt) CAUSE : Logging on and the user .profile is executing the /usr/ob/bin/basic pgm=xx command, pressing MB I before being in OpenBASIC will cause a CORE dump. SOLUTION: Add at the beginning of the user .profile the following : trap "" 3 SYMPTOM : Memory Fault Core Dump, Terminal releases BASIC and displays "$" prompt (sometimes terminal will hang at the "$" prompt) CAUSE : Loading a basic program from a called BASIC prompt (Example : >>load"joe" ) will cause a Memory Fault Core dump. SOLUTION: Fixed on OpenBASIC 4.0. SYMPTOM : Memory core dump, Terminal releases BASIC and display "$" prompt. Or there will be no CORE dump but terminal will hang. CAUSE : Using hex codes in high order basic. SOLUTION: Replace hex codes for OpenBASIC Mnemonics or change hex codes to low order basic. These CORE dumps will be created in the user's directory. Please remove these core dump files from the system (Core dump files need a lot of disk space). ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB006 Pg001 FIB 00007 MAI COMPANY CONFIDENTIAL 03/15/93 *** Uniplex not certified on HP-UX 9.0 *** Subject : Uniplex not certified on HP-UX 9.0 Author : Joe Melendez Type : Informational Purpose : Inform the Field of UNIPLEX problems on HP-UX 9.0 HP has not certified Uniplex on HP-UX 9.0. Customers that are on HP-UX 8.0 and have Uniplex should not upgrade to HP-UX 9.0 (Some customer have upgraded to HP-UX 9.0 and have not seen any problems with UNIPLEX but if they do find problems HP will not support them). HP does not know if they will certify this product to run on HP-UX 9.0. Customers that have other software running on HP-UX 8.0 (Lotus, Sybase, etc ) should contact the NSC (if they have an HP-UX support contract with MAI) so that we can verify with HP if they have problems with this software on HP-UX 9.0. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB007 Pg001 FIB 00008 MAI COMPANY CONFIDENTIAL 05/28/93 *** Terminals on DTC servers hang after using CTL+S *** Subject : Terminals hang on HP DTC servers when pressing "ctrl" + "s" (x/off) key. Pressing "ctrl" +"q" (x/on) does not unhang terminals. This is on HP-UX using HP DTC servers. Type : Informational Purpose : Inform the field of why terminals hang when trying to do (x/off, x/on, (Ctrl +"s", Ctrl +"q" keys)) This problem is caused when your DTC port and your terminal setup does not match. The main problem is with parity mis-match between your terminal setup and your DTC port. Modify you DTC or TERMINAL setup so that they do match. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB008 Pg001 FIB 00009 MAI COMPANY CONFIDENTIAL 05/28/93 *** Problems restoring files from 'tar' backup tape *** Subject : Using "tar" on HP-UX systems Type : Problem Purpose : Inform the field of restore problems when using "tar" on HP-UX systems. Symptom : Can not restore a file on a tape that was backed up using "tar" If you list all files on tape you can see the file you want to restore but you can not restore this file. Solution: In order to not run into this problem you must use the "tar" option -O when backing up files to tape. For example : tar -cvfO /dev/rmt/0m /filenames To restore a file you use : tar -xvfO /dev/rmt/0m /filename You must use the tar -O option when backing up and you must use the tar -O option when restoring files. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB009 Pg001 FIB 00010 MAI COMPANY CONFIDENTIAL 06/10/93 *** HP OpenSpool upgrade from A.01/A.02 to A.03 *** Type : Informational Purpose : Inform the field on how to perform an upgrade to HP OpenSpool A.03. NOTE : If customer has OpenSpool A.00 they must upgrade to OpenSpool A.01 or A.02 before upgrading to OpenSpool A.03 OpenSpool A.03 is the REQUIRED release for HP-UX 9.0. Before upgrading to HP-UX 9.0 it is recommended that the customer upgrade to OpenSpool A.03 while still on HP-UX 8.0. With the tape that contains the OpenSpool A.03 software you should also receive. the HP OpenSpool Version A.03.00 Software Release Notes. Please read this document and have it on hand for reference. After restoring this software you will also need to have the README notes as reference (see below on how to print the README notes) To upgrade to OpenSpool A.03 from OpenSpool A.01/A.02 please perform the following steps : 1. Mount the tape that contains the OpenSpool A.03 release in the tape drive. . 2. Log-on as "root" and change your directory to / 3. Perform tar -xvf /dev/rmt/0m TOOL (0m : First dat tape drive) This restores files that are needed to perform /etc/update that is compatible with OpenSpool A.03. 4. Before performing /etc/update to restore OpenSpool A.03 please check the the following : A). If you modified some of the HP delivered scripts in the directory /usr/lib/openspool/sw-master/hp-sw, you should copy these to : /usr/lib/openspool/sw-master/customer-sw before starting /etc/update. Otherwise your changes will be overwritten. B). Save your OpenSpool configuration and device bindings for backup purposes. Perform the following two commands as user "spooladm" on the realm master while all OpenSpool servers are running : 1. Perform the command : npstat -E >/tmp/bindings. This will generate a script with which you can recreate the current spooler state regarding devices bound and paper loaded. 2. Perform the command : npcshow -E>/tmp/config. This will save the current configuration in this file. The above files can be used to recreate the current OpenSpool configuration and device binding if anything goes wrong. You will also use these after restoring OpenSpool A.03. C). Stop all OpenSpool servers in the entire realm. As user "spooladm" perform the command : npadmin -s -A. This will stop all spooler services on all systems in the realm. If some processes cannot be killed by npadmin -s for some reason, then kill them manually (use "ps -ef" to find processes to kill). D). Stop all npui and npuix processes and OpenSpool commands. (use "ps -ef|grep np") to search for OpenSpool processes. In order to kill any processes of other users, you must logged on as user "root". E). Install OpenSpool A.03 tape on the realm master. Use /etc/update to install the A.03 software from tape. You must be logged on as user "root". Please refer to the "HP OpenSpool version A.03 Software Release Notes" for information on how to restore these files. After restoring, review the file /tmp/update.log file to verify that all filesets have been successfully installed. Also please printout the file called "/usr/lib/openspool/sw-master/hp-sw/readme/readme.A0300. This is the SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB010 Pg001 README that contains more information on how to continue the installation of OpenSpool A.03. Please follow section 2.2 step 5 thru step 8 of the README file to complete the installation of this software. After completing the above steps and if the customer had MAI printers on OpenSpool and followed Field Bulletin 760 to install these printer you will have to copy /usr/lib/openspool/sw-master/hp-sw/linesetting/printer.9600 to /usr/lib/openspool/sw-master/hp-sw/linesetting/printer.mai. Modify printer.mai to change the stty (second stty entry) and change it as per Field Bulletin 760. Also remember to make sure that user rights, owner and group are set correctly (also in F.B. 760). NOTE: Field Bulletin 760 is FIB 2 in this FIB group. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB010 Pg002 FIB 00011 MAI COMPANY CONFIDENTIAL 08/17/93 *** fbackup or automated SAM backup probs after upgrade to 9.0 *** After an upgrade to HP-UX 9.0 fbackup or the automated SAM backup will not accept new tapes. This is a known bug in HP-UX 9.0 to which there has been no patch addressed as yet. The temporary work around is to use 'tar' to save some small directory to the new unused tape; eg: 'tar cvf /dev/rmt/0m /etc/newconfig'. Once this has been done the tape is usable in 'fbackup' or the automated backup in SAM. Another Field Bulletin will announce the patch to correct this problem properly. ORIGINATOR: Marty Shehan SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB011 Pg001 FIB 00012 MAI COMPANY CONFIDENTIAL 08/17/93 *** sysdiag problems after upgrading/installing HP-UX 9.0 *** Subject :"sysdiag" problems after upgrading or installing HP-UX 9.0. Author : Joe Melendez Type : Informational This is to inform the field that after upgrading or installing HP-UX 9.0 the utility "sysdiag" might not be running. To correct this problem please have the customer call the MAI NSC and after verifying the support contract (must have an MAI HP-UX support contract) we will fax the customer the fix. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB012 Pg001 FIB 00013 MAI COMPANY CONFIDENTIAL 08/17/93 *** patch PHNE_2631 needed when upgrading/installing HP-UX 9.0 *** SUBJECT : HP-UX 9.0 PHNE_2631 PATCH TYPE : INFORMATIONAL PURPOSE : To inform the field of a problem when installing or upgrading to HP-UX 9.0 Before a customer upgrades or installs HP-UX 9.0 they should also have patch PHNE_2631 and install this patch after the upgrade/install of HP-UX 9.0. This is a mandatory patch. In order to receive this patch please ask the customer to call the MAI NSC. We will verify that the customer has an MAI HP-UX support contract and if so we will send this patch with installation instructions (free of charge). If you already know of customers that have upgraded/installed HP-UX 9.0 please have them contact the MAI NSC and after verifying support contracts we will ship this patch to them. Failure to install this patch might cause system hangs or core dumps. This is a mandatory patch for all HP-UX 9.0 systems. The mai NSC also has other patches available for HP-UX 9.0. We will also send these patches wth the above patch in order to avoid problems after the upgrade to HP-UX 9.0. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB013 Pg001 FIB 00014 MAI COMPANY CONFIDENTIAL 08/30/93 *** MAI printer problem after upgrade to HP-UX 9.0 *** Type : Problem Purpose : Inform the field of MAI printer problem after upgrading to HP-UX 9.0. Symptom : At the beginning of a print job the following message prints :" getconf SECURITY_CLASS : Invalid argument" Solution: This message occurs on MAI printers that are using "dumb" as the printer model (when they configured the printer in SAM). Reconfigure the printer using "maiprinter" as the printer model. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB014 Pg001 FIB 00015 MAI COMPANY CONFIDENTIAL 10/01/93 *** DATE and TIME problems [WPSF 786] *** TYPE: Problem PURPOSE: Inform the field of DATE and TIME problems on HP Systems SYMPTOM:.Starting in the middle of July, 1992 some HP systems will not keep DATE and TIME after system shutdown or power off. When you reboot the system the DATE and TIME is incorrect and you will have to re-enter DATE and TIME. SOLUTION: Customers that have an MAI/HP support contract should call the MAI NCS dispatch and place an HP/MAI support call. The MAI support team will contact the customer and send them a patch (DAT tape) which will correct this problem ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB015 Pg001 FIB 00016 MAI COMPANY CONFIDENTIAL 10/01/93 *** HP DTC "NAIL" Ports Patch [ WPSF 787 ] *** TYPE: Informational PURPOSE: Inform the field of HP DTC "NAIL" ports patch. HP/MAI customers that have HP DTC's can now "nail" ports on these DTC's. To "NAIL" ports means that everytime you log-on to this DTC port you will always have the same device name. You can then add this device name in the OpenBASIC CONFIG utility and your terminal will always have the same terminal number (ex. T15). In order to "NAIL" ports on an HP DTC the customer will need to obtain. two patches; DDFA (DTC Device File Access) utility and OpenView 2.0. A customer MUST also have an HP/MAI support contract in order to receive these patches (customer should call MAI NSC and place an MAI/HP support call). With these patches (two DAT tapes) they will receive installation instructions on how to install these patches and on how to configure the "NAIL" ports. NOTE: You will have to make the following correction in the Installation section of the "Basic Configuration Procedure". Step 6 instructs you to execute: /etc/ddfa/dpp -k /etc/ddfa/dp This is INCORRECT. It should be: /etc/dpp /etc/ddfa/ddp -k OpenBASIC CONFIG utility NOTE: The port device name gets created when you LOG-ON to this port. When you log off this device name will no longer exist. If you try adding the port device name in the OpenBSIC CONFIG utility and you have not logged-on to this port, the OpenBASIC CONFIG utility will not add this device port name and will give you a message saying . Port device not found. Workaround #1: First log-in to all the DTC "NAIL" ports, which will create the port device name, and then run the OpenBACIC CONFIG utility and add these port device names. Workaround #2 (for OpenBASIC experts only) Manually modify the OpenBASIC /usr/ob/etc/devices and bfsdevs files to include the Terminal names for these port devices. (No need to log-on to "NAIL" ports first). NOTE: The installation instructions will also inform you on how to "NAIL" a printer device (it assumes that you already know how to install a printer on the HP DTC). For information (HP write up) on how to install printers on an HP DTC please contact the MAI NSC and place anMAI/HP support call. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB016 Pg001 FIB 00017 MAI COMPANY CONFIDENTIAL 10/05/93 *** How to start sar [ WPSF 779 ] *** TYPE: Informational PURPOSE: Inform the field on how to start collecting SAR information on an HP-UX system. PROCEDURE: The following instructions will start and collect "sar" information on HP systems. It assumes that the user understands the basic unix "cron" commands. Steps for starting and collecting "sar" information on HP syatems. 1. mkdir /usr/adm/sa 2. cd /usr/spool/cron/crontabs 3. Create file (vi) to collect data vi sys (add the following) 0 * * * 0-6 /usr/lib/sa/sa1 20,40 8-17 * * 1-5 /usr/lib/sa/sa1 5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A save sys file 4. crontab sys (will submit the above file in cron) NOTE: If you already have a cron file (like for fbackup) the above will delete the previous file and replace it with this new file. To prevent this yyou must first: a. List the contents of the existing cronfile (first move to the directory where your cronfile resides). crontab -l >cronfile b. Add the instructions in Step 3 above to this cronfile. c. Re-submit your cronfile to cron crontab cronfile SAR will start collecting information after the first 20 minutes. If you reboot the system while cron is collecting sar information, after the reboot sar might stop collecting (HP-UX problem). To correct this you must add the following in /etc/rc: /usr/lib/sa/sadc /usr/adm/sa/sa'date + %d' ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB017 Pg001 FIB 00018 MAI COMPANY CONFIDENTIAL 10/08/93 *** HP Notes & Special Considerations [ WPSF 751 ] *** TYPE: Informational PURPOSE: Help the field with installations of MAI Hardware/Software on HP systems. Enclosed you will find answers to questions asked by the field on how to install MAI hardware/software on HP systems. TERMINALS 1. What are the defaults that SAM uses when configuring terminals? The SYSTEM CONSOLE which must be an HP Terminal 700/92, defaults to 8-bits, no parity, 1 stop bit and 9600 baud rate. The rest of the terminals, including MAI terminals, defaults to 7-bits, even parity, 1 stop bit (baud rate is user selectable). If you want a terminal to work with values other than the default: Example: change /dev/tty0p5 to 7-bits, odd parity, 1 stop bit and 19200 baud rate, you will have to do the following: a. vi /etc/inittab and look for the port entry of the terminal /dev/tty0p5, and at the end of this entry you will see a label, the label will be the baud rate that you selected when configuring the terminal in SAM. Example: 9600. Replace the label with a new label (NSC recommends mai). b. vi /etc/gettydefs and add a new entry at the end of the file: mai #B19200 SANE CLOCAL CS7 PARENB PARODD ISTRIP IXANY TAB3 #B19200 SANE CLOCAL CS7 PARENB PARODD ISTRIP IXANY TAB3 #login: #mai Match the terminal settings (terminal setup) for 19200 and 7/odd/1 if you want all MAI terminals to work with 19200 and 7/odd/1 you only have to change the label in /etc/inittab for these devices, look for the /etc/tty entry for these ports, and replace the label with mai. 2. How to remove configured terminals since SAM does not have an option to remove terminals? Example: /dev/tty0p5 a. vi the /etc/inittab file and remove or comment, (# in front of . entry) the port you want to remove. (look for entry /dev/tty0p5) b. Kill getty process (you can find process using: ps -ef |grep /dev/tty0p5) kill -9 process id. c. Delete /dev/tty0p5 (using rm /dev/tty0p5) Explanation of what /dev/tty0p5 means: 0 : indicates the mux number. p5: indicates the port number on the mux. 3. What are the terminal emulation for HP terminals? HP 700/44 TERM=vt200, HP 700/43 TERM=wy30- in UNIX but in SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB018 Pg001 OpenBASIC you should set the TERM=wy30 (this terminal is not recommended for use with OpenBASIC please refer to Field Bulletin 729 - OpenBASIC FIB 1, for more information) and the HP 700/92 TERM=2392. After setting TERM= to correct emulation do the export. Example: TERM=wy30;export TERM. 4. How do I set up my terminal so that at login it will set the correct emulation of this terminal? a. vi /etc/ttytype (this file has an entry for each terminal type and the device name, Example: 4314 tty0p5). Make sure that the entries are correct. b. vi .profile (under user node) and after the entry #Set up the terminal: change the eval entry to: eval 'tset -s -Q -h' add new entry after eval: echo "TERM value=:\"$TERM\" " add new entry after the above: export TERM When logging in, the .profile will look at the TERM value of the /etc/ttytype and set the terminal to this value. If you see an unknown value for TERM then you should check the /etc/ttytype file to see if you have an entry for this terminal. Also when configuring your terminal in OpenBASIC you must select the default for the environment for the TERMINAL TYPE option. 5. ESCAPE key does not work in OpenBASIC? That is by design. Use the CTL key + C for ESCAPE. If a user wants to change this they must vi .profile (user node) and change the stty entry: a. Look for stty erase entry and change the entry from CTRL C to CTRL V CTRL [(press CTRL key and press V, press CTRL key and press [). This will setup the ESCAPE key but you CANNOT load the function keys for the terminal because OpenBASIC uses the ESCAPE sequence to load the function keys and when it tries to load the function key it will ESCAPE out. 6. System was rebooting fine now it will not reboot and it hangs? a. Check the console terminal and make sure it has the correct setups (see default sections of this bulletin). b. Check that the console terminal has REMOTE MODE set with "*". If you do not have a status line (bottom of terminal screen) press Menu key then press setup key. Function-4 key is the mode key. Press Function-4 and see if REMOTE MODE is set with an "*" if not press REMOTE MODE (Function-4 key). Try rebooting system if problem continues please call NSC. 7. How do I load my Function keys on my DT-4315 from UNIX? Create a file using vi and enter the following: echo ctlrv ctrl[ Xm0148454c4cf# (ctrlv=ctrl key + v) Execute this file and Function key 01 should display HELLO. 8. After powering my terminal off it loses its baud rate. Powering a terminal off/on causes a 'break' on the port. Check SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB018 Pg002 /etc/gettydefs and look at the entry labeled 9600. At the end of the entry (login:) you will see that it has a label of 300. When you press the 'break' key (or power off/on) the system checks the /etc/gettydefs and loops to the next label (in our case 300). You must continue pressing the 'break' key until it gets back to the correct label (9600). This is the way HP-UX works. To correct this you can: a. Modify /etc/gettydefs and change the label to loop to itself (login: #300 to #9600). This is the easy way of doing it but it is not recommended by HP to do it this way. The recommended way is option b. b. Modify the /etc/inittab entries for terminals and change the label (9600 to mai). Create an entry in the /etc/gettydefs to add mai (duplicate the 9600 entry (changing the label name from 9600 to mai) and only change the #300 to #mai). PRINTERS 1. How do I configure MAI serial printers on HP systems? a. Copy file /usr/spool/lp/model/dumb to /usr/spool/lp/model/mai EXAMPLE: cp /usr/spool/lp/model/dumb /usr/spool/lp/model/mai b. vi /usr/spool/lp/model/mai and add the following entry above the entry that says: #Print the standard header stty 9600 opost onlcr parenb parodd cs7 ixon -istrip clocal tab3 <&1 2> /dev/null This will set up the printer to 9600 baud, 7 bits and odd parity. c. Configure the printer using SAM and at the option for printer. model/interface enter mai. d. Configure the printer in OpenBASIC. The above will work for spooled printers. If you want to print to non-spooled printers you will have to do the following: a. vi /etc/inittab b. add the following at the end of the last entry of inittab: c2:2:respawn:/usr/ob/bin/setport tty0p5 9600 cs7 parenb parodd ixon clocal The first two characters (Ex. c2) must be unique in the inittab file, the tty0p5 will be the port number that this printer is configured on, and it will set this port to 9600 baud, 7 bits, odd parity. 2. How can you find out what baud and bits the printer is set up for? Send a large job to a printer (ex. 11 /etc>joe) lp -dp5 joe (p5=printer name) SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB018 Pg003 While the job is being printed type: stty -a < /dev/tty0p5 (serial printer port). This will display the port configuration of this printer and it should match the printer setup. 3. How can I find out what port the printers are configured on? You can do this in different ways: a. lpstat -t will display the printer name and the device port. Example: device for lp: /dev/tty0p5 - serial printer device for joe: /dev/lp0 - parallel printer b. Under the /usr/spool/lp/member directory you will find a file for each printer configured. Do a "more" of these files and it will display the device name. Example: more /usr/spool/lp/member/joe will display /dev/tty0p5. c. When printers are configured in OpenBASIC you can do a "more" of /usr/ob/etc/devices. This will display all devices configured in OpenBASIC. The parallel printers will be piped to /usr/bin/lp and the serial printer will be assigned to a /dev/tty device. 4. How can I modify the mai driver (see printer question #1) so that on one printer it does a 'Form Feed' after the print job but on another printer it does not perform a 'Form Feed'? When you configure a printer via the HP sam utility the /usr/spool/lp/model/mai driver gets copied to the /usr/spool/lp/interface directory and creates a file with the printer name. You can vi this file and it will only affect that printer. Example: You have configured two printers named joe and lp and you want lp to not perform a 'Form Feed' after a print job. vi /usr/spool/lp/interface/lp Look for entry, near end of file, that says: cat "$file" 2>&1 Next entry is:echo "\014\c" (This is the Form Feed command) put a # (comment) in front of this entry and this printer (lp) will not perform the Form Feed). 5. PT-4221 parallel printer converted to centronics interface does not perform Form Feeds and loses first character after the Form Feed command. We have discovered a timing problem with this printer. Engineering now has a new prom that will correct this problem. We are in the process of documenting the problem. If yyou have this problem please call NSC and we will ship this new prom with documentation on how to install it. When the official OpenBASIC 3.0 level is released it will include a new printer driver for MAI printers. This driver is named maiprinter (it will be under /usr/spool/lp/model directory). Please use this driver when configuring MAI printers in the HP SAM utility. This driver contains the stty command (so you do not have to do any changes as you would have to do if you used the dumb driver). OpenBASIC SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB018 Pg004 1. Sometimes I get error 7 when trying to open a file. If you killed the BASIC process via the UNIX command kill -9 process ID., the integrity bit for the OpenBASIC files remains set. You must release the terminal or close all files so that this integrity bit is turned off. You must run the Basic utility 'fichk' to correct the error 7. Please refer to the OpenBASIC Administration Manual (Section 5) for more information regarding. 'fichk' and 'kychk'. 2. How can I read a tape (1/2") that I wrote from BASIC on my MAI system? When reading the tape on HP-UX use the SIZ=option. SIZ= must be greater or equal to the number of bytes of the record that you wrote to the tape; Example: READRECORD(1,SIZ=1800)A$ GENERAL HP & O/S QUESTIONS 1. Where can I find the meaning of system errors? For system errors below 100: /usr/include/sys/errno.h For system errors above 100: /usr/ob/etc/comerr.list Errors below 100 most of the time (not always) are UNIX errors. Errors above 100 are OpenBASIC system errors. When an error occurs you should type 'error' to get the system error number. The error will report two kinds of errors: system error (use the above to find out the meaning of the error), Basic error (use the OpenBASIC reference manual for the meaning of the error). 2. When creating users (via sam) and it creates a user .profile from what master profile does the system use to create the user .profile? It uses the /etc/d.profile (You can customize this profile). 3. I used sam to modify my Kernal Parameters, but it did not change the parameters? When using sam to modify KERNAL Parameters before exiting, the utility asks you if you want to reboot the system. You must say yes (so make sure you are the only person logged on to the system when modifying the kernal) if you want these parameters changed. If you say no and later reboot the system it will not change the parameters. You must perform uxgen manually (man pages for uxgen includes step-by-step procedure) if you did not say 'yes' to the option to reboot in order to get the new Kernal parameters. 4. WHAT Kernal parameters should I modify after installing OpenBASIC? Software Announcement for OpenBASIC 3.0 will contain a section regarding recommended KERNAL CONFIGURATIONS. Most of the time an ERROR 62 indicates that the system has reached the Kernal limits. After receiving this error you should type 'ERROR' to get the SYSTEM and BASIC error numbers. Based on these numbers you will . know what kernal parameters to modify. SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB018 Pg005 5. Do external SCSI devices have to be turned on before booting up the system? External SCSI devices, like Mag Tape Drives, must be turned on before booting up the system. Failure to do so will cause system hangs on the devices connected to the SCSI controller. A workaround to avoid these system hangs is to connect the external devices to its own SCSI controller. 6. When performing a Usr License upgrade I got the following message: "License Level File Set Problem. License FILE SET 64 USER is selected for load but does not match 8 User system". This is just a warning. You should just ignore this message and continue with the upgrade. 7. How can I correct an OPENSPOOL 'Suspended' problem? You must check the ownership and privilege of the device files for the printer. Owner needs to be set to 'spooladm' and privilege should be set to '666'. a. To find the names of the device file you should use the HP utility 'npui'. select the option for configuration and in this option select devices. b. Cancel print jobs from HP spooler. c. Do chmod and chown to change owner and privilege. Resubmit the print job and it should start printing. For more information regarding HP and OpenBASIC please refer to the following documentation: M.A. 1067 HP 8x7 Systems M.A. 1068 Software Support Program for HP Systems M.A. 1071 MAI to HP Serial Device Cable Adapters M.A. 1077 PT-4221 Dataproducts to Centronics Conversion Kits M.A. 1085 HARDWARE Support Program for HP Systems S.A. 196 OpenBASIC 2.0 S.A. 197 OpenBASIC 2.1 S.A. 198 OpenBASIC 3.0 F.B. 721 HP Peripheral Cabling Information F.B. 743 OpenBASIC Installation on HP Systems HP-UX Handbook (2 copies were sent to all branches) The following documentation are in progress: F.B. Software Conversions from MAI to HP Systems F.B. PC-LINK and OpenBASIC Also, as we become more familiar with HP products, such as OpenSpool, Glance Plus, DTC, etc., we will be writing addendums to these Field Bulletins. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB018 Pg006 FIB 00019 MAI COMPANY CONFIDENTIAL 10/14/93 *** 'fuser' problem on HP-UX 9.0 *** Type : Problem Purpose : Inform the field of a problem with fuser on HP-UX 9.0. Symptom : Will display the following message : " Read error for file # . Bad address.". When using fuser command on HP-UX 9.0. This is a intermittent bug with the fuser command. The command will continue to run and will not cause any problems. HP has not corrected the problem. If you have this problem and have an MAI HP-UX support contract please call the MAI National support and we will check to see if HP has corrected the problem (patch available). ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB019 Pg001 FIB 00020 MAI COMPANY CONFIDENTIAL 01/28/94 *** HP-UX 9.04 release notes *** Subject : HP-UX 9.04 upgrade Type : Informational Purpose : Inform the field of new HP-UX 9.04 O/S release HP has just released HP-UX 9.04 O/S. This release is the recommended O/S release for HP systems and it contains all O/S patches released for HP-UX 9.0 and fixes for Software Reported (SR) problems or bugs. A detailed list of theses patches/problems can be found in a file named : /etc/newconfig/904RelNotes/hpuxsystem, which will be restored after the update to this new release. This release will also support the EXABYTE 8 mm Tape drive (note : we have not yet tried to connect this drive to the HP System). Important Notes : MAI HP-UX customers (have HP-UX support contracts with MAI) should contact the MAI NSC before updating to this new release so that we can provide them with any additional information that we might have at that time. (As per HP, Users are responsible for installation and upgrading O/S releases, if they want on-site support this support should be billable). With each shipment of HP-UX 9.04 the customer will receive at least three tapes : 1. HP-UX 9.04 INSTALL 2. HP-PA SUPPORT 3. CUSTOMIZED SOFTWARE If the User already is on HP-UX 9.0 he will perform the update to HP-UX 9.04 using the CUSTOMIZED SOFTWARE. (For more information on how to UPDATE to HP-UX 9.0 please refer to a previous Field Bulletin that documented this procedure) Before upgrading/installing HP-UX 9.04 the user MUST verify that all software products that he already has are included in the CUSTOMIZED SOFTWARE tape. The User will also receive a manual named : "Notes for HP-UX Release 9.04", the User should read this manual before trying to upgrade/install this release. Some of the important information in this manual are : For Tunable Kernel Parameters please refer to page 1-14. For HP OPENSPOOL users please refer to page 1-19. For TELNET/rlogins Connections please refer to page 1-22 For GLANCEPLUS users please refer to page 1-30 (They will need to order a patch which we will send to them (if they have an MAI HP-UX support contract) when they call to let us know that will be upgrading to this new release. For LAN MANAGER v2.2 please refer to pages 1-34 & 1-35. If you or our customers have any questions or problems with the above information please contact us at the MAI NSC. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB020 Pg001 FIB 00021 MAI COMPANY CONFIDENTIAL 02/21/94 *** Problem with SAM displaying serial printers on HP-UX 9.04 *** Subject : HP-UX 9.04 Displaying printer model interface problem. Type : Problem Purpose : Inform the field about a problem with HP-UX 9.04. Symptom : When using SAM to configure a serial printer, the option to select Printer Model Interfaces will not allow you to select a displayed model nor scroll thru the different printer models (you can not position the cursor to this displayed list). You must know the name of the printer model interface that you want to use. (like maiprinter or dumb). You can find out the valid list of printer model interfaces by doing a list of the `/usr/spool/lp/model' directory. This will be fixed in a future patch or release of HP-UX. Please contact the MAI NSC if you have a customer that needs the patch and we will send this out to the customer as soon as the fix becomes available (if the customer has a MAI NSC HP-UX support contract). This only fails on HP-UX 9.04. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB021 Pg001 FIB 00022 MAI COMPANY CONFIDENTIAL 04/27/94 *** HP-UX 9.0 & 9.04 error 62 -46 (NFLOCKS) *** Subject : HP-UX 9.0 & 9.04 error 62 -46 (NFLOCKS) Type : Problem Purpose : Inform the field of HP-UX 9.x kernel problem Symptom : Applications reporting Error 62 - 46 (running out of NFLOCKS) but GLANCE is showing that there are NFLOCKS available. Example : Glance shows that system has 200 NFLOCKS defined and only 117 used but system is reporting that there are no more NFLOCKS available. The problem is that there is a kernel problem that only allows the system to use about 58-60 % of the defined NFLOCKS. Solution : HP has not corrected problem (no patch available yet). Customer should increase the number of NFLOCKS. Customers that have an MAI HP-UX support contract should call MAI NSC and when a patch becomes available we will send this out to them. NOTE : This is a problem on HP-UX 9.x systems, this does not fail on HP-UX 8.x O/S. This problem is reported on systems that are not running NFS. If customer has NFS running and are trying to access files on a mounted NFS disk and report errors 62 -46 they will need a couple of patches that are available for NFS on HP-UX 9.x. (this is not the same problem as reported above). ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB022 Pg001 FIB 00023 MAI COMPANY CONFIDENTIAL 05/13/94 *** ERROR "SAM EXPECTS (NCALLOUT >= NPROC) AFTER 9.04 UPGRADE *** PURPOSE: To inform the field of a possible problem after upgrade of HP-UX 8.02 to HP-UX 9.04. PROBLEM: After upgrading from HP-UX 8.02 to HP-UX 9.04 the customer may get error: "A tunable parameter violates an interdependancy: SAM expects the following to be true: ncallout >= nproc: errorcode -114" during any attempt to use the SAM utility. SOLUTION: Use "more" to observe how the two parameters "ncallout" and "nproc" are currently set in the file "/etc/conf/gen/S800". Using the instructions under "uxgen" in the HP-UX manual section 1M, edit the S800 file and reconfigure the kernel increasing "ncallout" to equal the value observed in "nproc". After the re- boot of the system called for in the "uxgen" instructions, SAM should no longer give the afore mentioned error. ORIGINATOR: M. SHEHAN SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB023 Pg001 FIB 00024 MAI COMPANY CONFIDENTIAL 05/18/94 *** new tool 'FreeDisk' available on HP-UX 9.x *** Subject : FreeDisk tool on HP-UX 9.x Type : Informational Purpose : Inform the field of a new tool released on HP-UX 9.x. Since upgrading to HP-UX 9.x might require more disk space than a previous release, HP has created a tool called FreeDisk that will help a user liberate additional disk space. The FreeDisk tool uses a three phase review of your system to identify unused or excessively large files that may be deleted : Phase one : Identify unused system filesets Phase two : Inspect for runaway Log files Phase three : Inspect for core files and identify big/old user files The FreeDisk tool can be found under the /system/TOOL directory. There is a README file called FreeDiskREADME that documents how this tool works. Before deleting any files from the system we recommend that our customers (those that have a MAI HP-UX support contract) call the MAI NSC to verify these files before deleting them. If the customer is on HP-UX 8.x and has the upgrade tape for HP-UX 9.x he can call the MAI NSC for information on how to restore the tool on HP-UX 8.x. ORIGINATOR: Joe Melendez SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB024 Pg001 FIB 00025 MAI COMPANY CONFIDENTIAL 09/09/94 *** SAM error in 9.04 *** PURPOSE: To inform the field of a possible problem in HP-UX 9.04 getting beyond the first screen (the one that informs you of movement keys). SYMTOM: Depression of "CR to continue" beyond first screen of SAM gets the following error: ***Commandline Argument Error: Option 'IDMerrfile' unknown to IDM ***Error in file '/etc/interface.lib/obamidm',line 1629 FOUND token:>timer<, expecting: -dialog -an object class name -an object identifier sam: error connot find config file /etc/interface.lib/obamidm sam IDM-E-ParseError: error parsing dialogfile CAUSE: Reloading of TOOLS fileset after the install or upgrade to HP-UX 9.04. SOLUTION: Reload from the 9.04 OS Customized Software tape or CD ROM the SAM fileset via the UPDATE utility. ORIGINATOR: Marty Shehan SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB025 Pg001 FIB 00026 MAI COMPANY CONFIDENTIAL 09/27/94 *** SAM bug in HP-UX 9.04 - password visible during user reation *** SUBJECT: Known problem in HP-UX utility SAM TYPE: Informational PURPOSE: Inform field of a known problem in HP-UX There is a known problem in HP-UX 9.04's SAM utility. When creating a user in the SAM utility, the password is visible while being entered. This is a problem already reported to HP in SR (Software Report) # 5003174144. There is currently no patch available for this problem, when a patch is available another field bulletin detailing a way to get the patch will be generated. Currently HP is saying the fix will be in release 10.0. When that is,.there is no commitment. The present workaround is to set no passord in SAM, get out of SAM immediately, log in as that user and run 'passwd'. ORIGINATOR: Marty Shehan SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB026 Pg001 FIB 00027 MAI COMPANY CONFIDENTIAL 08/24/95 *** How to add a disk drive using colume manager *** Adding a disk drive to an HP system with volume manager. Type: Informational Purpose: To show the steps used to add a diks drive to an existing filesystem that is using Volume Manager. To display the mounted filesystems Enter: mount / on /dev/vg00lvol1.. /usr on /dev/vg00/lvol /users on /dev/vg00/lvol5 To determine the drive type Enter: diskinfo /dev/rdsk/c1d0s2 will display: SCSI describe of c1d0s2: vendor: SEAGATE Product id: ST12400N size: 1027431 Kbytes bytes per sector: 512 Make sure the logical volume that the drive is going to be added is NOT mounted. Enter: umount /dev/vg00/lvol5 To create the filesystem on the disk driver you need to know the corresponding devicefile, and the drive type as displayed with the diskinfo command. Enter: newfs /dev/rdsk/c1d0s2 ST12400N (works for Seagate ST31200N also) After the filesystem has been created then a physical volume has to be created so Volume Manager can use the drive: Enter: pvcreate -f /dev/rdsk/c1d0s2 The drive is now available for VM, it can now be added a volume group to do so: Enter: vgextend /dev/vg00 /dev/dsk/c1d0s2 When a volume is created its default configuration is to have the filesystem reside on contiguous disk space. The command below removes that restriction, therefore the filesystem can reside on multiple disks. Enter: lvchange -C -n /dev/dsk/lvol5 The command below adds 1GB (100 MB, the size of the disk drive) to the file system, using the disk c2d0s2 for the space. Enter: lvextend -L 1000 /dev/vg00/lvol5 /dev/dsk/c2d0s2 To do the final increase of the fileysystem size: Enter: extendfs /dev/vg00/rlvol5 To remount the file system Enter: mount /dev/vg00/lvol5 /users To display the available file space Enter: bdf SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB027 Pg001 ORIGINATOR: Dan Arteritano SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB027 Pg002 FIB 00028 MAI COMPANY CONFIDENTIAL 10/26/95 *** errno script for getting description of system errors *** Subject: errno on non-BOSS/VX system Below is a script that will give the same ouput as the BOSS/VX command errno. The example below works on SCO, HP and Solaris. It does NOT work on AIX. Do the following: vi /usr/bin/errno Press to insert Enter: <:> grep "$1" /usr/include/sys/errno.h Press: Press: ZZ Enter: chmod +x /usr/bin/errno Enter: errno 5 Should display the following: #define EIO 5 /* I/O error */ ORIGINATOR: Dan Arteritano SOFTWARE-HEWLETT PACKARD-HP -UX OPERATING SYSTEM----FIB028 Pg001