Open System Services Installation Guide HP Part Number: 429954-007 Published: August 2013 Edition: J06.05 and subsequent J-series RVUs and H06.
© Copyright 2002, 2013 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document.....................................................................................6 Supported Release Version Updates (RVUs)..................................................................................6 Intended Audience....................................................................................................................6 New and Changed Information in the 429954-007 Edition............................................................
C OSS EasySetup Error Messages.................................................................49 Validation Check Errors...........................................................................................................49 Software RVU Check Error...................................................................................................49 Remote Execution Check Error.............................................................................................49 Home Terminal Check Error......
Tables 1 2 3 4 5 6 7 8 9 10 OSS EasySetup Utilities.....................................................................................................13 OSS EasySetup Files.........................................................................................................14 TACL PARAM Declarations for EasySetup Utilities.................................................................15 Default Configuration for OSS Server Processes....................................................................
About This Document This guide explains how to use OSS EasySetup to install and configure a minimal OSS subsystem on a system that does not already have an OSS subsystem. The OSS environment enables you to integrate an operating system similar to the UNIX operating system into your work environment. Supported Release Version Updates (RVUs) This manual supports J06.05 and all subsequent J-series RVUs and H06.16 and all subsequent H-series RVUs until otherwise indicated in a replacement publication.
Chapter 2: OSSSETUP Utility Describes the OSSSETUP utility, which configures and installs a minimal OSS subsystem. Chapter 3: OSSREMOV Utility Describes the OSSREMOV utility, which removes the components of an OSS subsystem. Chapter 4: STARTOSS Utility Describes the STARTOSS utility, which starts the OSS processes, servers, and filesets. Chapter 5: STOPOSS Utility Describes the STOPOSS utility, which stops the OSS filesets (but not the OSS processes).
?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. [ ] Brackets Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
| Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK | Failed } % Percent Sign A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
Publication Tasks Described SCF Reference Manual for the Kernel Subsystem Describes how to configure and start generic processes. You might use this manual if you do not use the EASYSETUP^STARTUP param to configure and start $NULL and/or $ZSMP and you want to configure these as generic processes. Safeguard Reference Manual In addition to other tasks related to system security, describes how to install, modify, or remove the INITIAL-DIRECTORY settings for all users.
Part Number Product Version Publication Date 429954-005 OSSMON H03, OSS EasySetup H01 November 2008 429954-006 OSSMON H03, OSS EasySetup H01 February 2010 429954-007 OSSMON H07, OSS EasySetup H01^AAF August 2013 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com.
1 OSS EasySetup Quickstart OSS EasySetup includes the OSSSETUP utility, which installs a minimal OSS subsystem on a system that does not have an OSS subsystem. (A minimal OSS subsystem does not include OSS subcomponents such as HP NonStop SQL/MX or the HP NonStop TUXEDO product.) You must not use the OSSSETUP utility when an OSS configuration already exists on your node. For example, you cannot use OSSSETUP when: • Your system was preconfigured by HP, but OSSREMOV has not been run.
1 2 HP recommends that you log on with the super ID to run this utility; otherwise, you must first ensure that the NULL, OSMP, and OSSMON objects have the correct security settings (see the Open System Services Management and Operations Guide). For G06.17 and later RVUs, NULL and OSMP are not required. HP recommends that you log on with a user ID in the SUPER group ID to run this utility. To stop an OSS EasySetup utility before it finishes, press the Break key (see “Break Key Message” (page 52)).
Example 1 OSSINF File Contents * File: OSS Monitor in-file ( Version 1.0 ) {<--MUST BE FIRST LINE OF FILE } * This is an in-file for the OSS T0585 utilities STARTOSS and OSSSETUP. The * OSS Monitor process manages all entries in this file. * * * * There is no need to refer to any name server or transport agent server. Name servers are automatically started when their corresponding filesets are started. Transport agent servers are started when a processor is reloaded.
Table 3 TACL PARAM Declarations for EasySetup Utilities (continued) PARAM Name PARAM value Used by Specifying this volume name enables EMS message logging by OSSREMOV the utilities and specifies the location of the required SPI definition files. If you do not specify a volume name using this param, the EMS subvolume is assumed to be on $SYSTEM. If the SPI definition files are installed on $SYSTEM, the OSS utilities generate EMS messages.
NOTE: The security process $ZSMP shoud be started only if the Safeguard product is installed. If the Safeguard product is not installed and $ZSMP is not running, security auditing, user aliases, and supplementary groups are not available for the OSS environment. • The Safeguard product.
EASYSETUP^EMSVOL param is set with a volume name that does not contain SPI files, warnings are generated, else only the notice message is generated. Example 3 Running STOPOSS With the EASYSETUP^EMSVOL Param TACL> param easysetup^emsvol $system TACL> stoposs STOPOSS - T0585H01 (01DEC2008) - December 9, 2008 15:49:05 System \NODE1 (C)2002 Compaq (C)2003, 2004 Hewlett-Packard Development Company, L.P.
5. Run DSM/SCM to install converted product files in the OSS file system. (For instructions, see the DSM/SCM User’s Guide.) This step: • Repopulates part of the OSS filesets from the ZOSSUTL archives described in the A7CINFO file, preserving file modes • Updates the DSM/SCM database with OSS file information for future maintenance NOTE: Do not use COPYOSS to install OSS files that DSM/SCM manages.
2 OSSSETUP Utility Overview The OSSSETUP utility performs various tasks involved in setting up the OSS environment. It: • Performs validation checks (see “Validation Check Errors” (page 49)) • Configures and starts necessary OSS processes as NonStop Kernel generic processes Unless the EASYSETUP^STARTUP param is set with either $NULL, $ZSMP or both of these processes prior to executing the OSSSETUP utility, $NULL and $ZSMP will not be configured as generic processes.
symbolic links to TCP/IP configuration files installed in that alternate subvolume. The following symbolic links are created. • Symbolic Link Source File from TCP/IP Installation Location /etc/hosts hosts /etc/inetd.conf inetconf /etc/protocols protocol /etc/services services /etc/resolv.
command. To stop $ZSMP, use the SAFECOM STOP command. If you are not using the EASYSETUP^STARTUP param to specify either of these processes, these processes are ignored. • If you have installed the SPI definition files in a volume other than $SYSTEM, you must use the EASYSETUP^EMSVOL param to specify the volume on which these files are installed. The default value for this param is $SYSTEM.
For information about default configuration, see Appendix A (page 44). • Interactive Mode, which: ◦ Asks you questions ◦ Gives you more control over installation parameters ◦ Might require more than one storage resource ◦ Allows the ZOSSUTL subvolume to be on any volume, which you can specify using the EASYSETUP^UTILVOL param (you confirm your choice in the interactive session). The default value for this param is $SYSTEM.
3. If you have installed the SPI definition files on a volume other than $SYSTEM, enter this command at the TACL prompt: PARAM EASYSETUP^EMSVOL $vol-name where vol-name is the name of the volume on which Event Management Service (EMS) subvolume (ZSPIDEF) resides. This subvolume must contain the event definition files ZOSSTACL and ZEMSTACL. The default value for this param is $SYSTEM.
Example 5 Subsystem Settings Table: Servers, Subsystem Processes, and Other Information Using EASYSETUP^STARTUP param Set With $NULL and $ZSMP OSS CONFIGURATION SUMMARY Subsystem Settings for \NODE1 Servers, Subsystem Processes and other Information Process $ZPMON $ZSMP $NULL $ZLSxx $ZMSGQ $ZPNS $ZPNH $ZTAxx Subsystem/Server *OSS Monitor *Security Manager *NULL Monitor *Local Servers Message Queue Server ROOT's Name Server HOME's Name Server *Transport Agents Processors (-1 = N/A) System load processor 0
where vol-name is the name of the volume on which Event Management Service (EMS) subvolume (ZSPIDEF) resides. This subvolume must contain the event definition files ZOSSTACL and ZEMSTACL. The default value for this param is $SYSTEM. You are not required to have installed SPI definition files, but if the SPI definition files are not installed in the specified location, this utility will not generate EMS events. For more information about this param and about enabling EMS event logging, see Table 3 (page 15).
In which pair of processors would you like the primary name server ($ZPNS) to execute? [0 1]: Either enter two different processor numbers separated by a space or press Return to accept the default processor numbers, shown in the brackets [ ]. The first processor number (for the primary processor) must be an integer in the range 0 through 15. The second processor number (for the backup processor) must be an integer in the range -1 through 15. At least one of these processors must be active.
results if a fileset’s catalog volume is not a member of the fileset’s pool space. Enter a disk volume. [$WORK]: Enter the name of a disk volume. 17. OSSSETUP displays a table like the one shown in Example 7 followed by this prompt: The $SYSTEM.ZXOSSMON.HOMEPOOL file is used for the HOME fileset creation pool volume list. This file can store up to nineteen disk volumes used to store OSS regular files (disk files).
Example 8 Interactive-Mode OSSSETUP Session TACL> param EASYSETUP^STARTUP "$ZSMP $NULL" TACL> param EASYSETUP^TCPIP^SUBVOL $ALTSYS.TCPLOC TACL> osssetup OSSSETUP - T0585H01 (01DEC2008) - December 9, 2008 15:49:05 System \NODE1 (C)2002 Compaq (C)2003, 2004 Hewlett-Packard Development Company, L.P.
OSS monitor process ($ZPMON) startup: STARTING SCF-> START PROCESS $ZZKRN.
Startup of servers and filesets managed by the OSS monitor: COMPLETED Creation of the /etc/profile file: STARTING /bin/cp /etc/profile.sample /etc/profile Creation of the /etc/profile file: COMPLETED OSS merge_whatis execution: STARTING /bin/merge_whatis OSS merge_whatis execution: COMPLETED NOTICE - TCP/IP installation location is $ALTSYS.TCPLOC.
NOTICE - Additional steps to consider now that this utility has completed: - Consider altering the default FsckCPU and Report settings values. Use 'SCF INFO SUBSYS $ZPMON' to find the current default values and refer to the OSS Management and Operations Guide to alter these settings. - Consider creating the system's default /etc/printcap file for the lp, lpstat and cancel commands. Refer to the /etc/printcap.sample file and to the OSS Management and Operations Guide.
After OSSSETUP Completes 1. 2. 3. Finish configuring the OSS environment as described in “Completing a Preconfigured Basic OSS Environment” in “Manually Setting Up an OSS Environment” in the Open System Services Management and Operations Guide.
3 OSSREMOV Utility The OSSREMOV utility removes the components of an OSS subsystem; that is, it removes the server processes and filesets that the OSS Monitor ($ZPMON) manages. OSSREMOV does not remove the INITIAL-DIRECTORY settings for the users, which the security manager ($ZSMP) manages. Usage Considerations: • HP recommends that you log on with the super ID to run OSSREMOV.
NOTE: The examples in this procedure show the prompts that OSSREMOV displays but not the status messages. Example 9 (page 37) shows an OSSREMOV session with status messages. 1. Find any executing OSS processes by entering this command at the OSS shell prompt: ps -ea If any OSS processes are executing, stop them. (For instructions, see the Open System Services Management and Operations Guide.) 2. Ensure that the INITIAL-DIRECTORY settings for all users have been removed.
Continue? : Respond either Yes or No (case is ignored) or by pressing Return (which is equivalent to responding No). If unsure, respond No. 8. If you responded No, OSSREMOV terminates. If you responded Yes, OSSREMOV displays this prompt: Confirm? : Respond either Yes or No (case is ignored) or by pressing Return (which is equivalent to responding No). If unsure, respond No. 9. If you respond No, OSSREMOV terminates.
Example 9 OSSREMOV Session $SYSTEM ZOSSINS 24> ossremov OSSREMOV - T0585H01 (01DEC2008) - December 10, 2008 15:45:05 System \NODE1 (C)2002 Compaq (C)2003, 2004 Hewlett-Packard Development Company, L.P. Removal of the OSS subsystem on \NODE1: STARTING ***************************************************************** WARNING -- You are about to remove OSS from this system. This entails removing ALL OSS data files on this system. This may have grave consequences.
TACL> FUP PURGE $SYSTEM.ZXOSSMON.TEMPPOOL ! Removal of all OSS configuration database files: COMPLETED Validation that the OSS subsystem is removed: STARTING Validation that the OSS subsystem is removed: COMPLETED Removal of the OSS subsystem on \NODE1: COMPLETED OSSREMOV finished.
4 STARTOSS Utility The STARTOSS utility starts the OSS processes, servers, and filesets named in the OSSINFIL file. If the OSSINFIL file does not exist, STARTOSS creates it by copying the OSSINF file (for a description of the OSSINF file, see Table 2 (page 14)). STARTOSS is intended for use after a system load or after the STOPOSS utility has been used. Usage Considerations: • HP recommends that you log on with a user ID in the SUPER group ID to run STARTOSS.
If these processes are not running, STARTOSS starts them from TACL: Process 1 $ZSMP 1 Name Security manager $NULL NULL $ZPMON OSS Monitor 1 $ZSMP and $NULL are only started if the EASYSETUP^STARTUP param specifies that process. If these processes and filesets specified by the OSSINFIL file are not running, STARTOSS starts them. • $ZMSGQ • ROOT • HOME • TEMP You can add files to the OSSINFIL file. For instructions, see the Open System Services Management and Operations Guide).
5 STOPOSS Utility The STOPOSS utility stops the OSS filesets (but not the OSS processes). Usage Considerations: • HP recommends that you log on with a user ID in the SUPER group ID to run STOPOSS. • The STOPOSS utility, the files it accesses, and the processes it stops must be appropriately secured for access by users other than the super ID, according to your site’s security guidelines.
3. Run STOPOSS either by entering this command at a TACL prompt or by putting this command in the operating system’s shutdown file: [RUN] STOPOSS If these processes are not running, STOPOSS starts them from TACL so that STOPOSS can complete its function, and then stops them again before completing: Process Name $ZSMP1 Security manager $NULL1 NULL $ZPMON OSS Monitor 1 $ZSMP and $NULL are only stopped if the EASYSETUP^STARTUP param specifies that process.
Example 11 STOPOSS Session With EASYSETUP^STARTUP param Set With $NULL and $ZSMP TACL> param EASYSETUP^STARTUP "$ZSMP $NULL" TACL> stoposs NOTICE - No EasySetup EMS events will be generated. STOPOSS - T0585H01 (01DEC2008) - December 10, 2008 17:47:05 System \NODE1 (C)2002 Compaq (C)2003, 2004 Hewlett-Packard Development Company, L.P. Shutdown of the OSS subsystem on \NODE1: STARTING Process missing.
A Default OSS Configurations For more detailed information about the default configurations and preconfigured OSS environments, see the OpenSystem Services Management and Operations Guide.
Table 8 Default Configuration for OSS Fileset Catalogs and Storage Pools (Interactive Mode) Fileset 1 Volume 2 Volumes 3 or More Volumes Catalog Volume Pool Volume Catalog Volume Pool Volumes Catalog Volume Pool Volumes ROOT $DISK1 $DISK1 $DISK1 $DISK1 $DISK1 Up to 20 volumes HOME $DISK1 $DISK1 $DISK2 $DISK2 $DISK2 Up to 20 volumes TEMP $DISK1 $DISK1 $DISK2 $DISK2 $DISK3 $DISK3 45
B OSS EasySetup Status Messages The OSS EasySetup utilities display status messages on these devices: • Your home terminal • The $0 and $ZLOG processes, which collect Event Management Service (EMS) events, provided the EASYSETUP^EMSVOL param is set OSSSETUP also writes status messages to OSSJOURN, a journal file that it creates on the volume and subvolume from which you invoke OSSSETUP.
\node is the node name of the system that utility is running on. Example 14 Start-Up Message OSSREMOV - T0585G07 (07NOV2003) - February 23, 2004 19:34:34 System \NODE1 (C)2002 Compaq (C)2003 Hewlett-Packard Development Company, L.P. Example 15 Finished Message OSSSETUP finished Other Status Messages All other OSS EasySetup status messages have the form: text: status text describes the operation that the utility is performing. The contents of text depend on the utility: Utility See ...
Table 9 Status Message Texts for OSSSETUP and STARTOSS Utilities (continued) Text OSS monitor process defined as an NSK generic process OSS monitor process ($ZPMON) startup Configuration of OSS servers Configuration of the ROOT fileset Startup of the ROOT fileset Installation of OSS archive files from $volume.
C OSS EasySetup Error Messages The OSS EasySetup utilities can display these types of error messages: • “Validation Check Errors” • “Dialog Errors and Warnings” (page 50) • “Break Key Message” (page 52) Validation Check Errors The utilities perform validation checks before doing anything else.
$OSS Disk Volume Check Error ERROR - While in defaults (Non-Interactive) mode, there must be a usable $OSS disk storage volume. Fix the problem and re-execute this utility. Break or error terminated operation. Installation of the OSS subsystem on \NODE1: FAILED OSSSETUP terminated unexpectedly or encountered errors. Cause You tried to run OSSSETUP in DEFAULTS (noninteractive) mode and the $OSS disk volume was either missing or unusable.
Example 16 Nonfatal Dialog Error Message ERROR - Invalid disk volume specified: $JOKER - Enter a space-separated list of up to nineteen disk volumes to be written to the file $SYSTEM.ZXOSSMON.ROOTPOOL. The $SYSTEM.ZXOSSMON.ROOTPOOL file is used for the ROOT fileset creation pool volume list. This file can store up to nineteen disk volumes used to store OSS regular files (disk files). Better performance generally results if a fileset's catalog volume is not a member of the fileset's pool space.
Example 20 Fatal Dialog Error Message ERROR - Remote execution not supported... Break or error terminated operation. Startup of the OSS subsystem on \NODE1: FAILED STARTOSS terminated unexpectedly or encountered errors. Break Key Message You can terminate any of these utilities by pressing the Break key while it is running. The utility displays this message: [ERROR - additional-error-text] Break or error terminated operation. Stopping utility.
Glossary A7CINFO file A configuration file distributed with OSS products that contains information about the contents of all PAX (archive) files of an OSS DSV. administrator 1. For an HP NonStop™ system, the person responsible for the installation and configuration of a software subsystem on a NonStop node. Contrast with operator. 2. For an IBM system, the person responsible for the day-to-day monitoring and maintenance tasks associated with a software subsystem on an IBM node. 3.
file An object to which data can be written or from which data can be read. A file has attributes such as access permissions and a file type. In the OSS environment, file types include regular file, character special file, block special file, FIFO, and directory. In the Guardian environment, file types include disk files, processes, and subdevices. file name A string of characters that uniquely identifies a file.
the group-name.user-name pair of values. For example, the structured view of the super ID is (255, 255). The OSS environment normally uses the scalar view of this user ID, also known as the UID, which is the value (group-number * 256) + user-number. For example, the scalar view of the super ID is (255 * 256) + 255 = 65535. HP NonStop™ ServerNet Cluster (ServerNet Cluster). The product name for the collection of hardware and software components that constitute a storage pool.
OSSMON See Open System Services (OSS) Monitor. pathname In the OSS file system and Network File System (NFS), the string of characters that uniquely identifies a file within its file system. A pathname can be either relative or absolute. See also ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990 or POSIX.1), Clause 2.2.2.57. regular file In the OSS file system, a file that is a randomly accessible sequence of bytes.
UID A nonnegative integer that uniquely identifies a user within a node. In the OSS environment, the UID is the scalar view of the HP NonStop™ ServerNet Cluster (ServerNet Cluster). The UID is used in the OSS environment for functions normally associated with a UNIX user ID. unmount To make a fileset inaccessible to the users of a node. user ID The unique identification of a user within a node.
Index Symbols A $0 See Event Management Service (EMS) collector ($0), 51 $NULL default configuration for, 44 OSSREMOV utility and, 36 required for OSS EasySetup utilities, 16 STARTOSS utility and, 40, 42 $OSS disk volume default configuration and, 44 OSSSETUP utility and, 22 validation check for, 50 $YMIOP.
catalog, 28 created by OSSSETUP utility, 21 EDIT, 14 OSS EasySetup, 14 OSSINF see OSSINF file OSSINFIL see OSSINFIL file OSSINSTL, 14 OSSJOURN See OSSJOURN file, 21 OSSLIB, 14 OSSTREE, 21 product, installing, 19 shutdown, 42 SOFTDOC, 14 SPI definition, 17 STOPOSS, 14 STRTOSS, 14 Fileset catalogs, default configuration for, 44, 45 Filesets HOME see HOME fileset removed by OSSREMOV utility, 34 ROOT see ROOT fileset started by STARTOSS utility, 39 stopped by STOPOSS utility, 41 TEMP see TEMP fileset Finished m
STARTOSS utility and, 39 OSSINFIL file description of, 14 STARTOSS utility and, 39 OSSINSTL file, 14 OSSJOURN file OSSSETUP utility and, 21 status messages and, 46 OSSLIB file, 14 OSSREMOV utility error messages for, 49 running, 34 session example, 37 status messages for, 47 OSSSETUP utility $OSS disk volume and, 22 ? command, 23 actions of, 20 archive files and, 20 error messages for, 49 files created by, 21 HELP (?) command, 23 OSSINF file and, 20 running in DEFAULTS (noninteractive) mode, 22, 23 in inter
catalog files for, 28 default configuration for, 44, 45 OSSINF file and, 15 OSSSETUP utility and, 20 subsystem setting for, 27 Terminal emulator, required, 15, 16 Terminal helper server ($ZTTxx), 20 Terminal, home see Home terminal Transport agent server ($ZTAxx), 20 TUXEDO See NonStop TUXEDO, 13 U Updating software, 18 Utilities merge_whatis, 20 OSS EasySetup see OSS EasySetup utilities OSSREMOV see OSSREMOV utility OSSSETUP see OSSSETUP utility pax, 19, 33 STARTOSS see STARTOSS utility STOPOSS see STOPOS
