Open System Services Installation Guide Abstract This guide explains how to install and configure a minimal HP NonStop™ Open System Services (OSS) subsystem using OSS EasySetup. It assumes that the reader is an experienced operator or system manager for NonStop systems. Product Version OSS Monitor T8622G10 OSS EasySetup G07 Supported Release Version Updates (RVUs) This manual supports G06.17 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 426805-001 OSSMON G09 April 2001 429954-001 OSSMON G09, OSS EasySetup G07 February 2002 429954-002 OSSMON G10, OSS EasySetup G07 December 2002 429954-003 OSSMON G10, OSS EasySetup G07 April 2004 429954-004 OSSMON G10, OSS EasySetup G07 December 2004
Open System Services Installation Guide Glossary Index Examples What’s New in This Guide v Guide Information v New and Changed Information Figures Tables v About This Guide vii Who Should Read This Guide vii What Is in This Guide viii What This Guide Does Not Cover ix Related Reading and Training ix Unsupported Utilities xi Notation Conventions xii Abbreviations xvi 1.
. STARTOSS Utility Contents 4. STARTOSS Utility Running STARTOSS 4-1 Status and Error Messages 4-2 5. STOPOSS Utility Running STOPOSS 5-1 Status and Error Messages 5-1 A. Default OSS Configurations B. OSS EasySetup Status Messages Event Management Service (EMS) Events Start-Up and Finished Messages B-2 Other Status Messages B-3 B-1 C.
Examples (continued) Contents Examples (continued) Example B-2. Example B-3. Example C-1. Example C-2. Example C-3. Example C-4. Example C-5. Start-Up Message B-2 Finished Message B-2 Nonfatal Dialog Error Message C-3 Dialog Warning Message C-3 Warning Message for EASYSETUP^STARTUP C-3 Warning Message for EASYSETUP^UTILVOL C-4 Fatal Dialog Error Message C-4 Figures Figure 1-1. OSSINF File Contents 1-3 Tables Table 1-1. Table 1-2. Table A-1. Table A-2. Table A-3. Table A-4. Table A-5. Table B-1.
Contents Open System Services Installation Guide —429954-004 iv
What’s New in This Guide Guide Information Open System Services Installation Guide Abstract This guide explains how to install and configure a minimal HP NonStop™ Open System Services (OSS) subsystem using OSS EasySetup. It assumes that the reader is an experienced operator or system manager for NonStop systems. Product Version OSS Monitor T8622G10 OSS EasySetup G07 Supported Release Version Updates (RVUs) This manual supports G06.
What’s New in This Guide New and Changed Information Open System Services Installation Guide —429954-004 vi
About This Guide 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.
What Is in This Guide About This Guide What Is in This Guide Section or Appendix Title Description 1 OSS EasySetup Quickstart Describes OSS EasySetup and explains how to use its OSSSETUP utility to install and configure a minimal OSS subsystem. 2 OSSSETUP Utility Describes the OSSSETUP utility, which configures and installs a minimal OSS subsystem. 3 OSSREMOV Utility Describes the OSSREMOV utility, which removes the components of an OSS subsystem.
What This Guide Does Not Cover About This Guide What This Guide Does Not Cover Topic For information, see ...
Prerequisite Reading and Training About This Guide • DSM/SCM User’s Guide Migration Prerequisites • • G06.
Additional Reading About This Guide Additional Reading The following publications provide information about installing the operating system and configuring peripheral devices: Publication Description Guardian Procedure Errors and Messages Manual Describes the procedure errors and messages you can receive from Guardian. Operator Messages Manual Describes the operator messages distributed by the Event Management Service (EMS).
Notation Conventions About This Guide Notation Conventions • • • • Hypertext Links on page xii General Syntax Notation on page xii Notation for Messages on page xiv Change Bar Notation on page xv Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2.
General Syntax Notation About This Guide A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may 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. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item.
Notation for Messages About This Guide If there is no space between two items, spaces are not permitted. In the following example, there are no spaces 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.
Change Bar Notation About This Guide { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Abbreviations About This Guide Abbreviations DSM/SCM. Distributed Systems Management/Software Configuration Manager EMS. Event Management Service OSS. Open System Services PVU. product version update RVU. release version update SCF. Subsystem Control Facility SPI. Subsystem Programmatic Interface SPR. Software Product Revision TACL. HP Tandem Advanced Command Language TCP/IP.
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.) HP recommends that you use the Procedure to Install and Configure a Minimal OSS Subsystem on page 1-6 to install the OSS subsystem.
OSS EasySetup Components OSS EasySetup Quickstart Table 1-1. OSS EasySetup Utilities Name Description For information, see ... OSSSETUP1 Configures and installs a minimal OSS subsystem. Runs either interactively or noninteractively. Section 2, OSSSETUP Utility OSSREMOV1 Removes the components of the OSS subsystem—that is, the processes and filesets that the OSS Monitor ($ZPMON) manages. Does not remove the users’ initial directories, which the security manager ($ZSMP) manages.
Required Terminal Emulator OSS EasySetup Quickstart Caution. The files in Table 1-1 on page 1-2 and Table 1-2 on page 1-2 are EDIT files (file code 101), not object files. Nothing prevents you from changing these files; however, HP recommends that you change only the OSSINFIL file (for instructions, see the Open System Services Management and Operations Guide). Avoid changing the OSSINF file, because the changes might be overwritten by future software updates. Figure 1-1.
Utility PARAMs OSS EasySetup Quickstart Utility PARAMs Beginning with the T0585AAB version, the EasySetup utilities support these TACL PARAM declarations: PARAM NAME PARAM value Used by EASYSETUP^EMSVOL A valid disk volume name that identifies the disk on which the Event Management Service (EMS) subvolume (ZSPIDEF) resides. This subvolume must contain the event definition files ZOSSTACL and ZEMSTACL. Specifying this subvolume enables EMS message logging by the utilities.
Required Software OSS EasySetup Quickstart Required Software On G06.17 and later RVUs, all OSS EasySetup utilities recommend but do not require the following: • • EASYSETUP^STARTUP (this param can be used to run $NULL and $ZSMP) The Safeguard product.
SPI Definition Files OSS EasySetup Quickstart SPI Definition Files The Subsystem Programmatic Interface (SPI) definition files allow each of the OSS EasySetup utilities to generate EMS events. Warning messages will be generated if SPI definition files ZOSSTACL and ZEMSTACL are missing. This does not affect the execution of any utility. T0585AAA expects the SPI definition files to be installed on the $SYSTEM disk volume, and generates the warning messages when these files are not found.
OSS EasySetup Quickstart Procedure to Install and Configure a Minimal OSS Subsystem 3. Run DSM/SCM to update DSM/SCM (product T6031) to D46 PVU. (For instructions, see the DSM/SCM User’s Guide.) The D46 PVU can process A7CINFO files that contain OSS file information for all DSM/SCM-enabled OSS products in the RVU. 4. Run DSM/SCM to update your system's software with the files in the RVU (G06.17 or later). (For instructions, see the DSM/SCM User’s Guide.
OSS EasySetup Quickstart Procedure to Install and Configure a Minimal OSS Subsystem 12. Fileset mount points should be checked after installation to ensure that they have security permissions consistent with your site’s security policies. To modify permissions, use the OSS shell chmod command. For more information, see the Open System Services Management and Operations Guide.
2 OSSSETUP Utility The OSSSETUP utility: • • Performs validation checks (see Validation Check Errors on page C-1) 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.
OSSSETUP Utility • Creates these files: Filename File System File Type OSSJOURN Guardian EDIT (file code 101) Status messages (see Appendix B, OSS EasySetup Status Messages) OSSTREE Guardian EDIT (file code 101) Directory tree showing entire OSS subsystem /tmp/oss.tree.ddmmmyyyy.system-name OSS ASCII Directory tree showing entire OSS subsystem Contents The files OSSTREE and /tmp/oss.tree.ddmmmyyyy.system-name have identical contents.
Modes of Running OSSSETUP OSSSETUP Utility Modes of Running OSSSETUP You can run OSSSETUP in either of these modes: • DEFAULTS (Noninteractive) Mode, which: ° ° ° ° Asks you no questions Gives your OSS subsystem the default configuration Requires only one storage resource (a disk volume named $OSS) No longer requires the ZOSSUTL subvolume to be on the $SYSTEM volume if the EASYSETUP^EMSVOL param is used For more information, see Running in DEFAULTS (Noninteractive) Mode on page 2-4.
Running in DEFAULTS (Noninteractive) Mode OSSSETUP Utility If OSSSETUP displays error messages, see Appendix C, OSS EasySetup Error Messages. Running in DEFAULTS (Noninteractive) Mode To run OSSSETUP in DEFAULTS (noninteractive) mode: 1. Ensure that the $OSS disk volume exists and is usable. 2. The ZOSSUTL subvolume is no longer required to be on $SYSTEM if the EASYSETUP^EMSVOL param is used. 3.
Running in Interactive Mode OSSSETUP Utility Example 2-1.
Running in Interactive Mode OSSSETUP Utility 2. OSSSETUP responds with its start-up message and the following prompt: Do you want to configure an independent name server ($ZPNH) for the HOME fileset? Choosing "No" will configure all filesets using only the primary name server ($ZPNS). <[YES]/no>: Respond either Yes or No (case is ignored) or by pressing Return (which is equivalent to responding Yes). If unsure, respond Yes. 3.
Running in Interactive Mode OSSSETUP Utility Assigning the value -1 to the second processor tells the system not to configure a backup processor. 8. If you responded No in Step 2, go to Step 10. 9. If you responded Yes in Step 2, OSSSETUP displays this prompt: In which pair of processors would you like the HOME fileset name server ($ZPNH) to execute? [2 3]: Either enter two different processor numbers separated by a space or press Return to accept the default processor numbers, shown in the brackets [ ].
Running in Interactive Mode OSSSETUP Utility 12. If you responded Yes in Step 11, go to Step 14. 13. If you responded No in Step 11, OSSSETUP displays this prompt: The catalog files to maintain and manage the ROOT fileset reside on a single disk volume. Better performance generally 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. 14.
Running in Interactive Mode OSSSETUP Utility Enter the name of a disk volume. 18. OSSSETUP installs and configures the OSS subsystem. If EASYSETUP^STARTUP param is set with $NULL and $ZSMP, the display is as shown in Example 2-4 on page 2-10. This shows an interactive-mode OSSSETUP session, including the prompts, tables, and status messages. User input is shown in bold. 19.
Running in Interactive Mode OSSSETUP Utility Example 2-4.
Running in Interactive Mode OSSSETUP Utility Example 2-4. Interactive-Mode OSSSETUP Session (page 2 of 4) OSS monitor process ($ZPMON) startup: STARTING SCF-> START PROCESS $ZZKRN.
Running in Interactive Mode OSSSETUP Utility Example 2-4. Interactive-Mode OSSSETUP Session (page 3 of 4) Startup of servers and filesets managed by the OSS monitor: STARTING SCF-> ASSUME PROCESS $ZPMON SCF-> START SERVER #ZMSGQ SCF-> START SERVER #ZPLS SCF-> START FILESET HOME SCF-> START FILESET TEMP Startup of servers and filesets managed by the OSS monitor: COMPLETED Creation of the /etc/profile file: STARTING /bin/cp /etc/profile.
Running in Interactive Mode OSSSETUP Utility Example 2-4. Interactive-Mode OSSSETUP Session (page 4 of 4) 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.
OSSSETUP Utility Running in Interactive Mode Open System Services Installation Guide —429954-004 2- 14
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. Note. OSSREMOV requires the Safeguard product (see Required Software on page 1-5).
Running OSSREMOV OSSREMOV Utility 2. Ensure that the INITIAL-DIRECTORY settings for all users have been removed. (For instructions, see the Safeguard Reference Manual.) If not all users’ INITIAL-DIRECTORY settings have been removed, and you tell OSSREMOV to remove the security manager ($ZSMP), then you must do the following after you run OSSREMOV: a. Restart $ZSMP manually. b. Remove all users’ INITIAL-DIRECTORY settings. 3.
Running OSSREMOV OSSREMOV Utility 7. If you respond No, OSSREMOV terminates. If you respond Yes, OSSREMOV may display this prompt: Do you want the NULL process ($NULL) completely removed? : Caution. It is no longer required to start $NULL before starting the OSS Monitor; however, many applications use $NULL, and they might not work correctly if OSSREMOV removes it. Respond either Yes or No (case is ignored) or by pressing Return (which is equivalent to responding No). If unsure, respond No. 8.
Running OSSREMOV OSSREMOV Utility Example 3-1. OSSREMOV Session (page 1 of 2) $SYSTEM ZOSSINS 24> ossremov OSSREMOV - T0585G07 (08OCT2001) - January 17, 2001 14:38:54 System \NODE1 Copyright Compaq Computer Corporation 2001 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.
Running OSSREMOV OSSREMOV Utility Example 3-1. OSSREMOV Session (page 2 of 2) Removal of TACL> FUP TACL> FUP TACL> FUP TACL> FUP Removal of all OSS configuration database files: STARTING PURGE $SYSTEM.ZXOSSMON.ZOSS* ! PURGE $SYSTEM.ZXOSSMON.ROOTPOOL ! PURGE $SYSTEM.ZXOSSMON.HOMEPOOL ! PURGE $SYSTEM.ZXOSSMON.
Running OSSREMOV OSSREMOV Utility Open System Services Installation Guide —429954-004 3 -6
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 1-2 on page 1-2). Usage Considerations: • • • HP recommends that you log on with a user ID in the SUPER group ID to run STARTOSS. STARTOSS is on the installation subvolume ZOSSINS. You must run STARTOSS from ZOSSINS.
Status and Error Messages STARTOSS Utility configured as NonStop Kernel generic processes, the persistence manager ($ZPM) started them when the operating system was system loaded. Status and Error Messages The status messages that STARTOSS displays are described in Appendix B, OSS EasySetup Status Messages. The error messages that STARTOSS displays are described in Appendix C, OSS EasySetup Error Messages. Example 4-1 shows a STARTOSS session, including the status messages. User input is shown in bold.
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. STOPOSS is on the installation subvolume ZOSSINS. You must run STOPOSS from ZOSSINS. STOPOSS no longer expects the SPI definition files to be installed on $SYSTEM if the EASYSETUP^EMSVOL param is used (see SPI Definition Files on page 1-6).
Status and Error Messages STOPOSS Utility Example 5-1. 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 - T0585G07 (07NOV2003) - December 10, 2003 15:38:21 System \NODE (C)2002 Compaq (C)2003 Hewlett-Packard Development Company, L.P. Shutdown of the OSS subsystem on \NODE: STARTING Process missing.
Status and Error Messages STOPOSS Utility STOPOSS will start that missing process. With the param set, the 3 utilities act like AAA.
Status and Error Messages STOPOSS Utility Open System Services Installation Guide —429954-004 5 -4
A Default OSS Configurations Default Configuration for DEFAULTS (Noninteractive) Mode OSS server processes Interactive Mode Table A-1 OSS name servers Table A-2 Table A-3 OSS fileset catalogs and storage pools Table A-4 on page A-2 Table A-5 on page A-2 Table A-1.
Default OSS Configurations Table A-4. Default Configuration for OSS Fileset Catalogs and Storage Pools (DEFAULTS Mode) Fileset Catalog Volume Pool Volume ROOT $OSS $OSS HOME $OSS $OSS TEMP $OSS $OSS DEFAULTS (noninteractive) mode allows only 1 volume named $OSS. Table A-5.
B OSS EasySetup Status Messages The OSS EasySetup utilities (listed in Table 1-1 on page 1-2) 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.
OSS EasySetup Status Messages Start-Up and Finished Messages Start-Up and Finished Messages When you start an OSS EasySetup utility, it displays a message of the form: utility - T0585version (vproc-date) - date time System \node © Copyright 2001 Hewlett-Packard Development Company L.P. When an OSS EasySetup utility finishes, it displays a message of the form: utility finished. utility is either OSSSETUP, OSSREMOV, STARTOSS, or STOPOSS. version is the product version of utility; for example, G07.
OSS EasySetup Status Messages Other Status Messages 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 ... OSSSETUP STARTOSS Table B-1 on page B-4 OSSREMOV STOPOSS Table B-2 on page B-5 status indicates the status of the operation described by text and is one of these: Status Meaning STARTING The operation has started.
OSS EasySetup Status Messages Other Status Messages Table B-1.
OSS EasySetup Status Messages Other Status Messages Table B-2 lists the possible values for text for OSSREMOVE and STOPOSS. Not every invocation of OSSREMOV or STOPOSS displays every text listed in Table B-2. Table B-2. Status Message Texts for OSSREMOV and STOPOSS Utilities Text { Removal | Shutdown } of the OSS subsystem on \system-name [ Process missing. ] security manager process ($ZSMP) startup [ Process missing. ] NULL process ($NULL) startup [ Process missing.
OSS EasySetup Status Messages Open System Services Installation Guide —429954-004 B- 6 Other Status Messages
C OSS EasySetup Error Messages The OSS EasySetup utilities (listed in Table 1-1 on page 1-2) can display these types of error messages: • • • Validation Check Errors Dialog Errors and Warnings on page C-3 Break Key Message on page C-4 Validation Check Errors The utilities perform validation checks before doing anything else.
OSS EasySetup Error Messages Validation Check Errors Home Terminal Check Error ERROR - Unsupported home terminal session... Break or error terminated operation. Installation of the OSS subsystem on \NODE1: FAILED OSSSETUP terminated unexpectedly or encountered errors. Cause. Your home terminal session, $process.#device, is the wrong type (see Required Terminal Emulator on page 1-3).
OSS EasySetup Error Messages Dialog Errors and Warnings Dialog Errors and Warnings A dialog error or warning message is displayed if you respond to a utility’s prompt with an invalid answer. • • Nonfatal Dialog Errors and Warnings Fatal Dialog Errors on page C-4 Nonfatal Dialog Errors and Warnings A nonfatal dialog error or warning: • • • Displays a message only on your home terminal. Does not terminate the utility.
Fatal Dialog Errors OSS EasySetup Error Messages Example C-4. Warning Message for EASYSETUP^UTILVOL WARNING - Invalid value of () used for 'EASYSETUP^UTILVOL' parameter. Using the value of ().
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.
DSM/SCM Glossary new NonStop operating system. DSM/SCM creates a new software revision and activates the new software on the target system. DSM/SCM. See Distributed Systems Management/Software Configuration Manager (DSM/SCM). EDIT file. In the Guardian file system, an unstructured file with file code 101. An EDIT file can be processed by either the EDIT or PS Text Edit (TEDIT) editor. An EDIT file typically contains source program or script code, documentation, or program output.
group ID Glossary provides a file system (see also ISO/IEC IS 9945-1:1990 [ANSI/IEEE Std. 1003.11990], Clause 2.2.2.38); the Guardian application program interface (API) provides a file system; and OSS Network File System (NFS) provides a file system. (OSS NFS filenames and pathnames are governed by slightly different rules than OSS filenames and pathnames.) Within the OSS and OSS NFS file systems, filesets exist as manageable objects.
login Glossary login. The activity by which a user establishes a locally authenticated identity on a server node. Each login has one login name. login name. A user name associated with a session. manager. (1) For a NonStop system, the person responsible for day-to-day monitoring and maintenance tasks associated with a software subsystem on a NonStop node. (2) For a UNIX system, any person in Management and Information Services management for the site. mount.
OSS Glossary OSS. See Open System Services (OSS). OSS Monitor. See Open System Services (OSS) Monitor. 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.
storage pool Glossary storage pool. A set of physical disk volumes administered as a set of logical disk volumes. A logical disk volume can span multiple physical disk volumes. When a logical disk volume becomes full, more physical disk volumes can be added. storage-pool file. A file containing a list of disk volumes to be used by an OSS fileset. As these volumes are filled, more volumes can be added to the storage-pool file. super ID.
Index Numbers 6530 terminal emulator 1-3 A A7CINFO file 1-7 Archive files OSSSETUP utility and 2-1 quickstart and 1-7 B Break key 1-2, C-4 C Catalog files 2-8 Catalog volumes, performance and 2-8 CLCI window 1-3 Components of OSS EasySetup 1-1/1-3 Configurations, default A-1/A-2 Configuring a minimal OSS subsystem 1-6/1-7 COPYOSS utility DSM/SCM and 1-7 OSSSETUP utility and 2-1 D Default OSS configurations A-1/A-2 DEFAULTS (noninteractive) mode of OSSSETUP utility description of 2-3 running in 2-4 Dialo
G Index Files (continued) OSSINSTL 1-2 OSSJOURN See OSSJOURN file OSSLIB 1-2 OSSTREE 2-2 product, installing 1-7 shutdown 5-1 SOFTDOC 1-2 SPI definition 1-6 start-up 4-1 STOPOSS 1-2 STRTOSS 1-2 /tmp/oss.
O Index NonStop TUXEDO 1-1 O OSS already installed check C-2 OSS EasySetup product components of 1-1/1-3 description of 1-1 files of 1-2 requirements of software 1-5 SPI definition files 1-6 terminal emulator 1-3 OSS EasySetup utilities error messages for C-1/C-4 finished message B-2 OSSREMOV See OSSREMOV utility OSSSETUP See OSSSETUP utility STARTOSS See STARTOSS utility start-up message B-2 status messages for See Status messages STOPOSS See STOPOSS utility stopping 1-2, C-4 OSS local server process Se
P Index OSSSETUP utility (continued) session example 2-10/2-13 status messages for B-3/B-5 $OSS disk volume and 2-3 ? command of 2-3 OSSTREE file 2-2 OutsideView terminal emulator 1-3 P pax utility 1-7 Persistence manager process ($ZPM) OSSSETUP utility and 2-1, 4-2 Printers, setting up 1-7 Processes NonStop Kernel generic See NonStop Kernel generic processes Product files, installing 1-7 Q Quickstart procedure 1-1/1-7 R Release check See RVU check Remote execution check C-1 Removing an existing OSS su
T Index Start-up TACL window 1-3 Status messages finished B-2 general B-3/B-5 start-up B-2 where displayed B-1 STOPOSS utility error messages for C-1/C-4 running 5-1 session example 5-2 status messages for B-3/B-5 Stopping OSS EasySetup utilities 1-2, C-4 STOPSOSS file 1-2 Storage pools, default configuration for A-2 STRTSOSS file 1-2 Subsystem processes default configuration for A-1 started by STARTOSS utility 4-1 Subsystem Programmatic Interface (SPI) 1-6 Subsystem settings for ROOT, HOME, and TEMP 2-7
Z Index Z ZOSSINS subvolume OSS EasySetup utilities and 1-1 OSSREMOV utility and 3-1 OSSSETUP utility and 2-2 STARTOSS utility and 4-1 STOPOSS utility and 5-1 ZOSSUTL subvolume installing products that do not use 1-7 OSSSETUP utility and 2-1, 2-7 $SYSTEM and 2-4 Special Characters $0 See Event Management Service (EMS) collector ($0) $NULL default configuration for A-1 OSSREMOV utility and 3-3 required for OSS EasySetup utilities 1-5 STARTOSS utility and 4-1 STOPOSS utility and 5-1 $OSS disk volume defaul
