HPlogo Communicator e3000 MPE/iX Release 7.0 (Software Release C.70.00) > Appendix G HP Stage/iX Reference

HP Stage/iX Commands

MPE documents

Complete PDF
Table of Contents
Glossary
Index

This section lists and describes all the HP Stage/iX and STAGEISL commands.

  • HP Stage/iX is executed from the MPE/iX prompt.

  • STAGEISL is executed from the ISL prompt. STAGEISL is limited to the following commands:

    status

    same capabilities as HP Stage/iX

    list

    nofiles/files and nopatches/patches option not available

    set

    same capabilities as HP Stage/iX

    help

    keyword option not available. This Help only displays for STAGEISL specific commands, it does not display HP Stage/iX additional commands.

    exit

    same capabilities as HP Stage/iX

  • HP Stage/iX has two command modes:

    Normal mode — used by either system operators or system managers. The HP Stage/iX normal mode prompt is: 

    
  STAGEMAN>
    Expert mode — requires system manager capabilities. It expands the command set and expands the options of selected normal mode commands. It enables you to perform HP Stage/iX functions that are ordinarily performed from within HP Patch/iX. The HP Stage/iX expert mode prompt is: 
    
  STAGEMAN$
    Expert mode additional commands are:

    • STAGEFILE

    • DELETEFILE

    • SETDEFAULT

    • SHOWDEFAULT

Table G-1 "HP Stage/iX Commands by Interface" lists, by task, the commands and command capabilities that are available for each condition.

Table G-1 HP Stage/iX Commands by Interface

Activity

HP Patch/iX Menu/Option

STAGEISL Commands

HP Stage/iX Commands
Administrative Options
Initialize HP Stage/iXSTAGEMAN INIT
Uninstall HP Stage/iXSTAGEMAN UNINSTALL
Display Current Status Of Staging AreasSTAGEISL STATUS STAGEMAN STATUS
Staging Area Management
Create Staging AreaCreate [Stage][Tape]STAGEMAN CREATE
Delete Staging AreaSTAGEMAN DELETE
Show Staging Area NamePrompted during Create [Stage][Tape]stageisl listSTAGEMAN LIST

:LISTFILE /SYS/hpstage/...
Show Staging Area DescriptionSTAGEISL LISTSTAGEMAN LIST
Show Staging Area Create DatesAutomaticSTAGEISL LISTSTAGEMAN LIST
Modify Staging Area NameSTAGEMAN CHANGE...
Modify Staging Area DescriptionSTAGEMAN CHANGE...
Validate Staging AreaAutomaticSTAGEMAN VALIDATE...
Invalidate Staging AreaSTAGEMAN INVALIDATE...
Show Staging Area FilesSTAGEMAN LIST;FILES

:LISTFILE/SYS/hpstage/stagename

/...
Show Staging Area PatchesView PatchesSTAGEMAN LIST;PATCHES
Expert ModeSTAGEMAN EXPERT ON
Operating Environment Management
Activate Staged SoftwareSTAGEISL SET STAGE=stagenameSTAGEMAN SET STAGE=stagename
Deactivate (Backout) Staged SoftwareSTAGEISL SET STAGE=BaseSTAGEISL SET STAGE=Base
Display Defaults For Next BootSTAGEISL STATUSSTAGEMAN STATUS
Display Current Staging AreaSTAGEISL STATUS

Displays staging area used in last boot.		STAGEMAN STATUS

Displays staging area currently booted and running.
Commit To Current StageSTAGEMAN COMMIT

HP Stage/iX Command Summary

Table G-2 "Staging Area Management Commands" lists the Staging Area management commands, general operation commands, and STAGEMAN Expert Mode commands. In all three tables, SM stands for System Manager and OP stands for System Operator.

Table G-2 Staging Area Management Commands

Required Command (Abbrev)

Capabilities

Description
INITIALIZE (INIT)SMInitialize the HP Stage/iX facility
UNINSTALLSMUninstall HP Stage/iX completely from your system.
STATUS (ST)SM | OPDisplay current status of HP Stage/iX.
LIST (L)SM | OPList any staging areas on your system.
DISKUSE (DU)SM | OPDisplay the total disk space used by a staging area.
CREATE (CR)SMCreate a staging area.
DELETE (DEL)SMDelete a staging area.
CHANGE (CH)SMChange the name or description for a staging area.
VALIDATE (VAL)SMValidate a staging area.
INVALIDATE (INVAL)SMInvalidate a staging area.
COMMITSMMake the current staging area the Base.
SETSMSet the default staging area for the next boot.
DUPLICATESMCopy one staging area to another.
IMPORTSMImport a staging area from another system.
EXPORTSMPrepare a staging area to be exported to another system.
RECOVER (REC)SMRecovers a staging area that is not recognized in the environment.

Table G-3 "General Operation Commands" lists the general operating commands.

Table G-3 General Operation Commands

Required Command (Abbrev)

Capabilities

Description
HELP (H)SM | OPGet help for an STAGEMAN command.
ERRMSGSM | OPDisplay cause/action text for a STAGEMAN error.
EXIT (E)(none)Exit STAGEMAN.
LISTREDO(none)Display the STAGEMAN command history.
REDO(none)Re-execute (and edit) a previous STAGEMAN command.
DO(none)Re-execute a previous STAGEMAN command.
LOG(none)Log a copy of all STAGEMAN output to a file.
USE(none)Execute an STAGEMAN command file.
COMMENT (#)(none)Used to document a command file.
OPTION(none)Used to set options for command file processing.

Table G-4 "Expert Mode Commands" lists the expert mode commands.

Table G-4 Expert Mode Commands

Required Command (Abbrev)

Capabilities

Description
STAGEFILE (SF)SMPut a file in a staging area.
DELETEFILE (DF)SMDelete a file from a staging area.
SETDEFAULT (SETD)SMSet the default attributes for a particular file.
SHOWDEFAULT (SHOWD)SMDisplay the default attributes for a particular file.
COMPLETE (COMP)SMMark a staging area as complete.
EXPERTSMPut STAGEMAN in expert mode.

CHANGE (CH)

The CHANGE command will allow you to change various attributes of an HP Stage/iX staging area. Specifically, CHANGE will allow you to change:

  • The name of the staging area.

  • The description of the staging area.

The CHANGE command can be abbreviated CH.

Syntax


  CHANGE [STAGE=]stage_name [[;NAME=]new_name]
                            [[;DESC=]quoted_string]

Parameters


  [STAGE=]stage_name (required)
The current name of the HP Stage/iX staging area. This must be a valid staging area name for a pre-existing staging area. The staging area cannot be in use, or designated for use on the next boot (see the SET command).

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1". 

  [;NAME=]new_name (optional)
If this parameter is omitted then the current name of the staging area will be unchanged. Otherwise, this name will be used for the new name of the staging area.

This must be a valid HP Stage/iX staging area name and must be unique. The staging area name can be up to 16 characters in length. The name must be a valid MPE/iX directory name. For this reason, the name cannot contain a slash (/) character. It can contain letters (upper or lower case), numbers, and the special characters underscore (_), dash (-), and period (.).

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1". 

  [;DESC=]quoted_string (optional)
If this parameter is omitted then the current description for the staging area will be unchanged. Otherwise, this description will replace the old description for the staging area.

This parameter must be a quoted string if it contains any delimiter characters (like blanks, commas, semi-colons, or any other punctuation characters). The description can be any string up to 128 characters in length.

Example

To change the name of a staging area: 

  STAGEMAN> CHANGE old_stage;NAME=new_stage
To change the description associated with a staging area: 

  STAGEMAN> CHANGE old_stage;DESC="network reliability patches"

COMMENT (#)

The COMMENT command can be used to document command files used by the USE command. STAGEMAN ignores the COMMENT command and any text following it.

The COMMENT command can be abbreviated #.

Syntax


  COMMENT comment_text

Parameters


  (none)

Example

STAGEMAN will ignore both of these comment lines: 

  STAGEMAN> COMMENT this is just a comment
  STAGEMAN> # this is another comment

COMMIT

The HP Stage/iX subsystem allows system managers to activate patched system software without overwriting the pre-existing system software environment. Whenever the system is booted from an HP Stage/iX staging area, the system manager has the option of reverting to the previous system software environment by booting from the Base (see the SET command).

If the system manager has been using a particular HP Stage/iX staging area for a period of time, and is satisfied with the overall quality of the patched system software environment (including reliability and performance), then the system manager can make the patched software environment the new Base. The action of making the current staging area the new Base is not reversible. For this reason, HP Stage/iX refers to the action as "committing." The COMMIT command can be used to make the current staging area the new Base without re-booting the system or doing an UPDATE.

In order to use the COMMIT command, the system must be booted from an HP Stage/iX staging area, and there must not be an alternate staging area designated for the next boot.

The COMMIT command will perform several steps. It will first prompt you for confirmation to commit to the current software environment. (The ;NOCONFIRM option can be used to suppress the confirmation prompt.) The COMMIT command makes all of the necessary changes to the system software environment so that the current system software becomes the new Base. Finally, the COMMIT command deletes the HP Stage/iX staging area.

When you commit to a stage, any other stages that were created from the same Base, as the committed stage, may no longer be valid with respect to the new Base.

The COMMIT command cannot be abbreviated.

Syntax


  COMMIT [;{ CONFIRM}]
           {NOCONFIRM}

Parameters


  [;{ CONFIRM}] (optional) {NOCONFIRM}
The ;CONFIRM or ;NOCONFIRM option specifies whether or not the COMMIT command will prompt you for confirmation. If you specify ;NOCONFIRM, then STAGEMAN will NOT prompt you for confirmation. The default is ;CONFIRM.

Example

To "commit" to the current staging area ("stage1" in the example below): 

  STAGEMAN> STATUS
  Currently active staging area: stage1
  Staging area to be used for next boot: stage1.
  STAGEMAN> COMMIT ;NOCONFIRM

COMPLETE

The COMPLETE command marks a staging area as complete. When a staging area is marked as complete, it tells STAGEMAN that all files that should belong to it have successfully been staged, and the staging area is now a complete unit. A staging area will not validate until it has been marked as complete.

Syntax


  COMPLETE [STAGE=]stage_name

Parameters


  [STAGE=]stage_name (required)
The name of the staging area to be marked as complete.

Example

To mark staging area "Stage_1" as complete: 

  STAGEMAN> COMPLETE STAGE_1

CREATE (CR)

The CREATE command will create an empty HP Stage/iX staging area. At the time the staging area is created, you are allowed to specify a brief description for the staging area.

Staging areas are normally created by HP Patch/iX. A default description is associated with the staging area at that time, but you can change that description using the CHANGE command.

When a staging area is initially created, it will be considered "invalid". It will remain invalid until it is validated by the VALIDATE command.

You must specify a name for the staging area to be created. The staging area name must be a valid HP Stage/iX staging area name (see below), and cannot be the name of a staging area that already exists. The name "BASE" is reserved by HP Stage/iX to refer to the Base system software environment (see the SET command). You are not allowed to create a staging area named "BASE." This includes all forms of the word BASE, Base, or base.

HP Stage/iX staging areas are created as sub-directories under the HP Stage/iX root directory. The HP Stage/iX root directory is /SYS/hpstage/. The staging area "stage_1" for example would be kept in the MPE directory /SYS/hpstage/stage_1/.

The CREATE command can be abbreviated CR.

Syntax


  CREATE [STAGE=]stage_name [[;DESC=]quoted_string]

Parameters


  [STAGE=]stage_name (required)
This parameter specifies the name to be given to the newly created staging area. The staging area name can be up 16 characters in length. The staging area name must be a valid MPE/iX directory name. For this reason, the staging area name cannot contain a "/" character. It may contain letters (upper or lower case), numbers, and the special characters "_", "-", and ".".

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1". 

  [;DESC=]quoted_string (optional)
This parameter must be a quoted string if it contains any delimiter characters (like blanks, commas, semi-colons, or any other punctuation characters). The description can be any string up to 128 characters in length.

Example

To create a new staging area called "new_stage" with the description "misc. patches": 

  STAGEMAN> CREATE NEW_STAGE;DESC="MISC.PATCHES"

DELETE (DEL)

The DELETE command will delete an HP Stage/iX staging area and its contents. If the system is currently booted from an HP Stage/iX staging area, then that staging area cannot be deleted. In addition, if a staging area has been designated for the next boot (see SET command), then it cannot be deleted.

The DELETE command will prompt you for confirmation to delete the staging area before it is deleted. You will not be prompted if the ;NOCONFIRM option is specified.

It is acceptable to delete a staging area that another staging area was created from. Each staging area has all the information to function from the committed Base. A staging area created from another staging area incorporates all the information from the first staging area.

The DELETE command can be abbreviated DEL.

Syntax


  DELETE [STAGE=]stage_name [;{ CONFIRM}]
                              {NOCONFIRM}

Parameters


  [STAGE=]stage_name (required)
This parameter specifies the name of the staging area to be deleted.

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1". 

  [;{ CONFIRM}] (optional) {NOCONFIRM}
The ;CONFIRM or ;NOCONFIRM option specifies whether or not the DELETE command will prompt you for confirmation. If you specify ;NOCONFIRM, then STAGEMAN will NOT prompt for confirmation. The default is ;CONFIRM.

Example


  STAGEMAN> DEL OLD_STAGING_AREA;NOCONFIRM

DELETEFILE (DELETEF,DF)

The DELETEFILE command removes a file from a staging area. The file is physically purged from the staging area's directory, and all references to it are removed from the HP Stage/iX environment.

The DELETEFILE command can be abbreviated as DELETEF or DF.

Expert Mode Command:

Syntax


  DELETEFILE [STAGE=]stage_name [FILE=]file_name

Parameters


  [STAGE=]stage_name (required)
The name of the HP Stage/iX staging area from which the file (or files) is (are) to be deleted. This must be an existing staging area. The staging area cannot be in use, and cannot be designated for use on the next boot.

Staging area names are case sensitive. 

  [FILE=]file_name (required)
The name of the file to be deleted. The file name can be wildcarded.

The filename in this command is case sensitive.

Example


  STAGEMAN> DELETEFILE stage1, SYSGEN.PUB.SYS
  STAGEMAN> DF stage1, SYSG@

DISKUSE (DU)

The DISKUSE command can be used to determine how much disk space is currently being used by an HP Stage/iX staging area.

When a staging area is currently in use, the files that are normally in that staging area have been renamed into their natural locations. As a result, a staging area is virtually empty when it in use (only a few HP Stage/iX specific files remain). The DISKUSE command is misleading when a staging area is currently in use, since it cannot account for the disk space used by the files which have been renamed. The DISKUSE command prints a warning if you do a DISKUSE on the currently active staging area.

The DISKUSE command in STAGEMAN is really just an interface into the MPE/iX DISKUSE command. The output is therefore identical to the MPE/iX DISKUSE command. For additional information on the MPE/iX DISKUSE command, use the MPE/iX help facility. This can be done with STAGEMAN by typing: 

  :HELP DISKUSE
The DISKUSE command can be abbreviated DU.

Syntax


  DISKUSE [STAGE=]stage_name

Parameters


  [STAGE=]stage_name (required)
This parameter designates which staging area will be displayed. The staging area name must be a valid HP Stage/iX staging area name. STAGEMAN will use this name to construct the full path name for the directory where the staging area is kept.

Example

To determine the disk space used by staging area "stage_area_5": 

  STAGEMAN> DISKUSE stage_area_5
        SECTORS
   TREE           LEVEL     DIRECTORY
  147888         147856     /SYS/hpstage/stage_area_5/

DO

The DO command is used to re-execute a command from the command history stack.

Syntax


  DO [COMMAND=]command_id

Parameters


  command_id:
The command from the redo stack which we want to re-execute. The command may be specified by its relative or absolute order in the command line history stack, or by name (as a string), in whole or in part. The default -1 is the most recent command. This parameter is optional.

Example

To re-execute a command by its absolute order in the command line history stack, enter: 

  STAGEMAN> DO 5
To re-execute a command by its relative order in the command line history stack, enter: 

  STAGEMAN> DO -3
To re-execute a command by its name, enter: 

  STAGEMAN> DO INIT

DUPLICATE

The DUPLICATE command copies one staging area to another. All files from the original staging area are copied, and the resulting staging area — except for the name — is an exact duplicate of the original. The EXCEPT parameter allows an indirect file to be passed that contains a list of files in the original staging areas that should not be duplicated.

The DUPLICATE command can be abbreviated DUP.

Syntax


  DUPLICATE [FROM=]stage_name
            [;TO=]stage_name
            [[EXCEPT=]exception_file]

Parameters


  [[FROM=]stage_name (required)
The name of the existing staging area to be copied. 

  [[TO=]stage_name (required)
The name of the new staging area. All the normal rules for staging area names apply (see CREATE). 

  [[EXCEPT=]exception_file]
The name of an ASCII file that contains a list of files in the FROM staging area that should not be moved to the TO staging area.

Example


  STAGEMAN> DUPLICATE stage1, stage2

ERRMSG

The ERRMSG command allows you to display cause/action text related to a specific STAGEMAN error.

Syntax


  ERRMSG [ERROR=]error_number

Parameters


  [ERROR=]error_number (required)
The error number associated with the STAGEMAN error. This number is always displayed in parenthesis immediately following the error message text.

Example


  STAGEMAN> status

  *Error: The HP Stage/iX Globals file is temporarily in use
  by another & process. Can't complete command. (STAGEMAN 1170)
  
  STAGEMAN> errmsg 1170
  
  MESSAGE:
  
  The HP Stage/iX Globals file is temporarily in use by another
  process. Can't complete command. (STAGEMAN 1170)
  
  CAUSE:
  
  STAGEMAN could not open the HP Stage/iX Globals file because it was
  held open exclusively by another process at the time. The other
  process was most likely STAGEMAN (or HP Patch/iX) being run in
  another job or session (STAGEMAN always opens the Globals file for
  exclusive access).
  
  ACTION:
  
  Either terminate the additional STAGEMAN process, or allow the
  command being executed by that process to complete.

EXIT

The EXIT command (abbreviated E or EX) exits the STAGEMAN utility. You must have System Manager (SM) or System Operator (OP) capability to execute this command.

Syntax


  EXIT

Parameters


  (none)

Example

To exit from STAGEMAN, enter: 

  STAGEMAN> EXIT

EXPERT

The EXPERT command is used to put STAGEMAN into expert mode. There are several STAGEMAN commands that extend the basic STAGEMAN functionality which require you to be in EXPERT mode. All expert mode commands require SM capability. The EXPERT command itself requires SM capability to execute.

The following commands are allowed in expert mode only:

Table G-5 Commands Only Available in Expert Mode

Command

Description
STAGEFILE (SF) Put a file in a staging area.
DELETEFILE (DF) Delete a file from a staging area.
CHANGEFILE (CF) Change the attributes of a staged file.
SETDEFAULT (SETD) Set the default attributes for a particular file.
SHOWDEFAULT (SHOWD) Display the default attributes for a file.

NOTE: The STAGEMAN prompt will always indicate which mode STAGEMAN is currently executing in. When STAGEMAN is in normal mode, the prompt is STAGEMAN>. When STAGEMAN is in expert mode, the prompt is STAGEMAN$.

Syntax


  EXPERT [[MODE=]{ ON}]
                 {OFF}

Parameters


  [[MODE=]{ ON} (optional)
          {OFF}
If the MODE parameter is not specified then the EXPERT command will simply display the current mode for STAGEMAN. Otherwise the EXPERT command will explicitly set STAGEMAN into expert mode if ON is specified, and normal mode if OFF is specified.

Example

To see what mode STAGEMAN is currently executing in 

  STAGEMAN> EXPERT
  STAGEMAN is currently operating in NORMAL (non-expert) mode.
To put STAGEMAN into expert mode 

  STAGEMAN> EXPERT ON
To put STAGEMAN into normal mode 

  STAGEMAN$ EXPERT OFF

EXPORT

The EXPORT command prepares a staging area to be exported to another system. EXPORT - together with IMPORT - provides a standardized method of patch/software distribution. Three EXPORT options are currently supported (see the Parameters description).

Syntax


  EXPORT [STAGE=]stage_name [;{NOPACK}]
                              {TAPE }
                              {PACK }

Parameters


  [STAGE=]stage_name (required)
The name of the staging area to be exported. 

  [;{NOPACK}] (optional)
    {TAPE }
    {PACK }
Default: NOPACK

The export option to be used. Three options are currently supported:

  • NOPACK — All files belonging to the staging area are simply copied to the Export directory (/SYS/hpstage/export/). From here the files can be moved to the Import directory (/SYS/hpstage/import/) on the target machine in any way you choose. The staging area can then be accepted into that HP Stage/iX environment via the IMPORT ;NOUNPACK command.

  • TAPE — The staging area directory is written to tape via STORE. The staging area can then be accepted into the target system's HP Stage/iX environment via the IMPORT ;TAPE command.

  • PACK — The staging area is packaged into a single file in the Export directory under the name of the staging area (/SYS/hpstage/export/stage_name). This file can then be moved to the Import directory (/SYS/hpstage/import/) on the target system using either tape or a network transport utility (for example, FTP) and accepted into the HP Stage/iX environment via IMPORT ;UNPACK.

Example


  STAGEMAN> EXPORT STAGE1;PACK

HELP

The HELP command (abbreviated H or HE) displays information about a STAGEMAN command. You must have System Manager (SM) or System Operator (OP) capability to execute this command.

Syntax


  HELP [command_name] [{DESC }]
                       {PARMS }
                       {EXAMPLE}
                       {ALL }

Parameters


  command_name: (optional)
The name of the command. This parameter is optional. If you omit the command name, STAGEMAN displays information about all commands. 

  (keyword) : (optional)
Default: DESC

Defines which part of the help text you would like printed.

  • DESC — Show the command's description and syntax.

  • PARMS — Show the command's parameters only.

  • EXAMPLE — Show command usage examples only.

  • ALL — Show all help text related to the command.

Example

To get information about the INITIALIZE command, enter: 

  STAGEMAN> HELP INITIALIZE
To get examples on how to use the LIST command, enter: 

  STAGEMAN> HELP LIST EXAMPLE

IMPORT

The IMPORT command accepts a staging area from another system into the HP Stage/iX environment on the local system. See the help discussion under EXPORT for more information.

Syntax


  IMPORT [STAGE=]stage_name [;{NOUNPACK}] {TAPE } {UNPACK }

Parameters


  [STAGE=]stage_name (required)
The name of the staging area to be imported. 

  [;{NOUNPACK}] (optional) {TAPE } {UNPACK }
The import option. The default is NOUNPACK.

Example


  STAGEMAN> IMPORT STAGE1;TAPE

INITIALIZE (INIT)

The INITIALIZE command is used to set up the various data structures and directories that the HP Stage/iX facility requires to operate.

STAGEMAN always verifies that the HP Stage/iX facility is correctly initialized. If HP Stage/iX is not correctly initialize, STAGEMAN will print out a warning message.

The INITIALIZE command is non-destructive. It can be typed at anytime to re-initialize HP Stage/iX should some file, directory, or data structure become corrupted. It will not delete any staging areas or affect the contents of any staging area in any way.

The INITIALIZE command can be abbreviated INIT.

Syntax


  INITIALIZE

Parameters


  (none)

Example


  :STAGEMAN
  
  STAGEMAN A.00.00, (C) Hewlett-Packard Co., 1995. All Rights Reserved.
  *Warning: The HP Stage/iX environment is not initialized.
  (STAGEMAN 1090)
  
  STAGEMAN> initialize
  Successfully initialized the HP Stage/iX environment.
  
  STAGEMAN>

INVALIDATE (INVAL)

The INVALIDATE command is used to mark a particular staging area as being invalid, preventing that staging area from being used (see the SET command).

The LIST command can be used to view the current status (valid or invalid) of a staging area. The VALIDATE command will set the valid flag, allowing a particular staging area to be used.

The INVALIDATE command can be abbreviated INVAL.

Syntax


  INVALIDATE [STAGE=]stage_name

Parameters


  [[STAGE=]stage_name (required)
The name of the HP Stage/iX staging area to be invalidated. This must be a legal staging area name for a pre-existing staging area. The staging area cannot be in use or designated for use on the next boot (see the SET command).

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1".

Example


  STAGEMAN> INVAL FOO

LIST (L)

The LIST command will give you a list of HP Stage/iX staging areas. Wildcard characters are accepted when listing staging areas.

By default the LIST command will display the name of the staging area, the last modified date, a flag indicating whether or not the staging area is valid or invalid (see VALIDATE/INVALIDATE commands), and the brief description associated with the staging area.

In addition, an asterisk (*) will be displayed at the end of the staging area name if the staging area is active (in use); a caret (^) will be displayed at the end of the staging area name if the staging area will be used for the next system boot (see the SET command).

The LIST command will also list more detailed information about the files that are in a particular staging area, and/or the patches that are staged in a particular staging area.

The LIST command can be abbreviated L.

Syntax


  LIST [[STAGE=]stage_name] [;{NOFILES}] [;{NOPATCHES}]
                              {FILES}      {PATCHES}

Parameters


  [[STAGE=]stage_name] (optional)
This parameter is used to designate a staging area to be viewed. The staging area name can be either a valid HP Stage/iX stage name, or a pattern with MPE wildcards. All of the usual MPE wildcard characters (@, ?, #, etc.) are allowed. The default value for this parameter is @ (which will list ALL staging areas).

Staging area names are case sensitive. 

  [;{NOFILES}] (optional)
    { FILES}
This parameter specifies whether or not the LIST command will display information about specific files within a given staging area. The default value for this parameter is ;NOFILES. If the ;FILES parameter is specified then the LIST command will display information for each file in the staging area(s) about disk restrictions (LDEV1, contiguous, or none), file disposition (add, replace, delete), and the file code, end-of-file, and limit values as they would appear in a LISTF(ILE) output. 

  {;{NOPATCHES}] (optional)
    { PATCHES}
This parameter determines whether or not the LIST command will display information on the specific patches in a given staging area. The default value for this parameter is ;NOPATCHES. If the ;PATCHES parameter is specified then the LIST command will display the patch ID, date and time installed by HP Patch/iX, and a brief description for each patch found in the staging area(s).

The ;PATCHES option will not be able to display any patch information if the file PMSWINFO.PUB.SYS is not in the given staging area. This file is normally staged by the HP Patch/iX product when the staging area is created. If this file does not exist in the staging area, a message stating that no patch information is available will be displayed.

The patches displayed will be the sum of all patches applied by HP Patch/iX, which includes any patches installed in the Base, as well as in the staging area.

Example


  To see a list of all staging areas type:

  STAGEMAN> list

  STAGING AREA NAME MOD DATE V DESCRIPTION
  ----------------- -------- - ---------------------------------------
  stage1 *^         09/29/95 V PowerPatch 1 plus reactive patches
  STAGE2 ^          09/30/95 I PowerPatch 2
         |
         | --- (staging area is active and set for next boot)

  To see a list of all staging areas that begin with the string "st",
  and information about all files and patches in each of those staging
  areas type:

  STAGEMAN> l st@;files;patches

  STAGING AREA NAME MOD DATE V DESCRIPTION
  ----------------- -------- - ---------------------------------------
  stage1 *^         09/29/95 V PowerPatch 1 plus reactive patches

  ** FILE INFO FOR "mike1":
  
  FILE NAME                          REST   DISP FCODE EOF LIMIT
  ---------------------------------- ------ ---- ----- ------------------
  NL.PUB.SYS                         LDEV1  REPL NMPRG 114519 4&
  START.MPEXL.SYS                    CONTIG REPL       3791    & 8192

  ** PATCH INFO FOR "mike2":
  
  Patch      Date and Time     Description
  --------- -----------------  ------------------------------------------
  MPEQX999  02/20/96 11:08 AM  5.5 Dummy Patch for Beta Testing
 
  NOTE: Staging area names are case sensitive, so the above command will
  display staging areas that start with "st", but not staging areas that
  start with "ST".

LISTREDO

The LISTREDO command is used to display the command history stack. The output order is from the least to the most recent command with absolute command reference numbers preceding each command.

Syntax


  LISTREDO

Parameters


  (none)

Example


  STAGEMAN> LISTREDO

LOG

The LOG command is used to record the human/machine dialog as it appears to the user on the STDLIST. The log file is an exact snapshot of the session with STAGEMAN.

Syntax


  LOG [FILENAME=]filename

Parameters


  [FILENAME=]filename (required)
Any valid MPE/iX file to which you have READ and WRITE access. If the file doesn't exist, it is created.

Example

To enable logging and log all input and output to the file "logfilea", enter: 

  STAGEMAN> LOG LOGFILEA

OPTION

The OPTION command is used to set various STAGEMAN options. These options effect how STAGEMAN handles command files (also see the USE command). There are currently two different options which can be set by the OPTION command.

The LIST option specifies whether or not the command and command output will be displayed when executing a command from a command file. If the list option is set to NOLIST, the command will not be echoed and the command output will be suppressed. If the option is set to LIST, then the command will be echoed and the output will be displayed to STDLIST (and to the log file if one is active — see the LOG command). The default for the LIST option is NOLIST. To see the output of a command executed from a command file, either type OPTION LIST prior to executing (via USE) that command file, or put an explicit OPTION LIST command inside the command file.

The CONTINUE option specifies whether or not STAGEMAN will continue to process commands within a command file if an error is encountered. The default value for the continue option is NOCONTINUE. If the continue option is set to NOCONTINUE, then STAGEMAN will abort the processing of a command file when an error occurs. To override this behavior, set the CONTINUE option to CONTINUE.

If you enter the OPTION command with no parameters, then the command will display the current value for the LIST and CONTINUE options.

The scope of the option command is for the duration of the command file, or until another option command is encountered (whichever comes first). For example: if you put an OPTION LIST command within a command file, the LIST option will remain in effect until STAGEMAN finishes processing the command file, or until it encounters an OPTION NOLIST command.

The OPTION command cannot be abbreviated.

Syntax


  OPTION [{ LIST}] , [{ CONTINUE}] {NOLIST} {NOCONTINUE}

Parameters


  [{ LIST}] (optional) {NOLIST}
If this parameter is omitted, the value of the LIST option is unchanged. Otherwise the value of the LIST option is set to the value specified. 

  [{ CONTINUE}] (optional) {NOCONTINUE}
If this parameter is omitted, the value of the CONTINUE option is unchanged. Otherwise the value of the CONTINUE option is set to the value specified.

Example

To see what options are currently set: 

  STAGEMAN> OPTION
  The following options are currently set: NOLIST, NOCONTINUE.
To set the list option to NOLIST and the continue option to CONTINUE: 

  STAGEMAN> OPTION NOLIST CONTINUE

RECOVER

The RECOVER command recovers a staging area that is not currently recognized by the HP Stage/iX environment. This command is normally only necessary when recovering a system with an INSTALL/UPDATE, where the HP Stage/iX environment has to be re-initialized (INITIALIZE), and one or more staging areas have to be restored from tape. In this case, each previously existing staging area that is restored from a backup needs to be accepted into the HP Stage/iX environment with the RECOVER command. RECOVER updates the system's HP Stage/iX Globals file with all appropriate information about the staging area.

Syntax


  RECOVER [STAGE=]stage_name

Parameters


  [STAGE=]stage_name (required)
The name of the existing staging area to be recovered.

Example

To recover staging area "stage_1": 

  STAGEMAN> RECOVER stage_1

REDO

The REDO command is identical in function to the MPE/iX redo command. It allows a command in the command history stack to be edited and re-executed.

Syntax


  REDO [COMMAND=]command_id

Parameters


  command_id: (optional)
Specifies the command to re-execute. The command may be specified by its relative or absolute order in the command line history stack, or by name (as a string). The default is -1, the most recent command. This parameter is optional.

Example

To edit the most recent command beginning with the string 'DIS': 

  STAGEMAN> REDO DIS
To edit command number 10 (absolute) on the command history stack, enter: 

  STAGEMAN> REDO 10
To edit the second-to-last command on the stack (one command before the most recent), enter: 

  STAGEMAN> REDO -2

SET

The SET command is used to designate a particular HP Stage/iX staging area for use on the next boot. When a staging area is in use, it is considered "active". The process of "activating" a staging area requires that the system be re-booted (using the ISL> START command). The SET command is used to designate which staging area should be used on the next reboot. On each subsequent reboot (START) the system will automatically use the same staging area as was used on the previous reboot, unless the system manager changes the default by using the SET command.

You must specify the name of a validated HP Stage/iX staging area to the SET command. The SET command will accept the string "BASE" to indicate that the system should be booted from the BASE on the next reboot.

The SET command cannot be abbreviated.

Syntax


  SET [[STAGE=]stage_name]

Parameters


  [[STAGE=]stage_name (required)
The name of the HP Stage/iX staging area to be used for the SET. This must be a legal staging area name for a pre-existing staging area.

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1".

Example


  STAGEMAN> SET STAGE=new_staging_area

SETDEFAULT (SETD)

The SETDEFAULT command sets the default values for a particular file to be used by the STAGEFILE command. For example: the SETDEFAULT command can be used to the set the defaults for NL.PUB.SYS, so that whenever an NL is staged using the STAGEFILE command, the values for all of the STAGEFILE parameters can be omitted.

There is a file, STAGEDEF.PUB.SYS, that contains all of the default values for files that make up HP software products. This file contains multiple SETDEFAULT commands. The STAGEDEF file is implicitly executed whenever STAGEMAN is run.

The SETDEFAULT command can be abbreviated as SETD.

Expert Mode Command:

Syntax


  SETDEFAULT [FILE=]file_name

             [;DISK={ NONE}]
                    {CONTIG}
                    { LDEV1}

             [;DISP={ IGNORE}]
                    {REPLACE}
                    { ADD}
                    { DELETE}

             [;ONERR={IGNORE}]
                     { WARN}

             [;VAL={BASIC} ]
                   {EXISTENCE}
                   {CHECKSUM}

             [;VALINFO="validation_info"]

             [;LIFTYPE={NONE} ]
                       {BOOT}
                       {IPL}
                       {DATA}
                       {AUTOF}

             [;OWNER="owner_name"]

             [;FILEGROUP={LDEV1} ]
                         {SLT}
                         {OTHER}

Parameters


  [FILE=]file_name (Required)
The fully qualified filename for the file which the subsequent defaults should be set. 

  [;DISK=disk_restrict] (Optional)
Values: CONTIG (C), LDEV1 (1), NONE(N)

Default: NONE (see also SETDEFAULT)

  • CONTIG — Implies that the file must be on LDEV1 and that the file requires contiguous disk space. (MOST RESTRICTIVE)

  • LDEV1 — Implies that the file must be on LDEV1.

  • NONE — Implies that there are no disk space restriction on the file. Files with no restrictions can be placed anywhere within the MPEXL_SYSTEM_VOLUME_SET.


  [;DISP=file_disp] (Optional)
Values: REPLACE (R), ADD (A), DELETE (D), IGNORE (I)

Default: REPLACE (see also SETDEFAULT)

  • REPLACEMENT — Indicates that this file will replace an existing file when the system is booted from this staging area.

  • ADD — Indicates that this is a new file.

  • DELETE — Indicates that this file will be deleted when the system is booted from this staging area.

  • IGNORE — Files with this disposition are placed in the staging area, but are ignored during system start.


  [;ONERR=error_action] (Optional)
Values: WARN(W), IGNORE (I)

Default: WARN (see also SETDEFAULT)

If an error occurs while processing a file, the error_action for that file will dictate what the start code will do.

  • WARN — start will continue. An error message will be printed.

  • IGNORE — start will continue, no error message will be printed.


  [;VAL=val_method] (Optional)
Values: BASIC (B), EXISTENCE (E), CHECKSUM (C)

Default: BASIC (see also SETDEFAULT)

This parameter describes which technique will be used to determine if a particular file is valid at validation time (see VALIDATE). All files in a staging area must be considered valid before HP Stage/iX will consider the staging area valid.

  • BASIC — Basic validation should be performed on this file. This includes insuring that the file exists in the staging area, and that the disk space restrictions match what they should be.

  • EXISTENCE — The file that the staged file corresponds to must exist in the Base.

  • CHECKSUM — The computed checksum for the file corresponding to the final target file name must be in the array of acceptable checksums (see: validation_info parameter).

The CHECKSUM option is not currently supported. 

  [;VALINFO="val_info"] (Optional)
This parameter is not currently supported. 

  [;LIFTYPE=lif_type] (Optional)
Values: NONE, BOOT, IPL, DATA, AUTOF

Default: NONE (see also SETDEFAULT)

Determines whether or not the file belongs in the system LIF Directory, and if so, what file type it should be placed in the directory as. 

  [;OWNER="owner_name"] (Optional)
Default: "MANAGER.SYS"

The owner name that should be assigned to the staged file. 

  [;FILEGROUP=] (Optional)
Values: LDEV1, SLT, OTHER

Default: OTHER

Determines at what point in the start process the file actually gets switched (renamed) to its natural location. There are currently three supported switching "windows":

  • LDEV1 — The file must be switched as early as possible in the start process because the correct version is needed early on (an example is SL.PUB.SYS). The file therefore must reside entirely on LDEV 1.

  • SLT — This is the normal file group for most of the files found on the System Load Tape. Files in this group are switched ahead of files in the OTHER group.

  • OTHER — This is the default file group. Files here are switched after the system is almost completely up and running.

Example


  STAGEMAN$ SETDEFAULT
  START.MPEXL.SYS;disk=C;disp=R;val=E;onerr=W
  STAGEMAN$ SETD
  USERFILE.PUB.SYS;disk=LDEV1;disp=ADD;val=B;onerr=IGNORE

SHOW DEFAULT (SHOWD)

Shows the defaults that were set for a file by the SETDEFAULT command.

The SHOWDEFAULT command can be abbreviated as SHOWD.

Expert Mode Command:

Syntax


  SHOWDEFAULT [FILE=]file_name

Parameters


  [FILE=]staged_file_name (Required)
The name of the file whose defaults you are checking. Wildcards are allowed.

Example

To show all defaults: 

  STAGEMAN$ SHOWDEFAULT
To show the defaults for all files in PUB.SYS type: 

  STAGEMAN$ SHOWD @.PUB.SYS

STAGEFILE (STAGEF,SF)

The STAGEFILE command is used to put a file into a staging area. The file can be anywhere initially (referred to as its pre-stage location). You are required to specify the final target filename for the file. This is the name that the file will ultimately have when the system is booted from the staging area. In addition, you can optionally specify several pieces of information about the file. This additional information will be used during boot-up when processing the file.

The STAGEFILE command can be abbreviated as STAGEF or SF.

Expert Mode Command:

Syntax


  STAGEFILE [STAGE=]stage_name [FROM=]from_file_name
            [TO=]to_file_name

            [;DISK={NONE}]
                   {CONTIG}
                   {LDEV1}

            [;DISP={IGNORE}]
                   {REPLACE}
                   {ADD}
                   {DELETE}

            [;ONERR={IGNORE}]
                    {WARN}

            [;VAL={BASIC}]
                  {EXISTENCE}
                  {CHECKSUM}

            [;VALINFO="validation_info"]

            [;LIFTYPE={NONE} ]
                      {BOOT}
                      {IPL}
                      {DATA}
                      {AUTOF}

            [;OWNER="owner_name"]

            [;{MOVE}]
              {COPY}

Parameters


  [STAGE=]stage_name (Required)
The name of the HP Stage/iX staging area. This must exist, cannot be in use, and cannot be the staging area designated for use on the next boot. 

  [FROM=]from_file_name (Required)
The name of the file in its current (pre-staged) location. This can be expressed in either POSIX (HFS) or MPE syntax ((example: /SYS/PUB/NL and NL.PUB.SYS are equivalent). 

  [TO=]to_file_name (Required)
The final target name for the file. This must be expressed as a fully qualified filename. It can be expressed in either POSIX (HFS) or MPE syntax (example: /SYS/PUB/NL and NL.PUB.SYS are equivalent).

NOTE: If the filename is expressed in POSIX syntax, but is expressible in MPE syntax, the filename will be converted to MPE syntax. This is to avoid the problem of the same file being stageable under two names. 

  [;DISK=disk_restrict] (Optional)
Values: CONTIG (C), LDEV1 (1), NONE(N)

Default: NONE (see also SETDEFAULT)

  • CONTIG — Implies that the file must be on LDEV1 and that the file requires contiguous disk space. (MOST RESTRICTIVE)

  • LDEV1 — Implies that the file must be on LDEV1.

  • NONE — Implies that there are no disk space restriction on the file. Files with no restrictions can be placed anywhere within the MPEXL_SYSTEM_VOLUME_SET.


  [;DISP=file_disp] (Optional)
Values: REPLACE (R), ADD (A), DELETE (D), IGNORE (I)

Default: REPLACE (see also SETDEFAULT)

  • REPLACEMENT — Indicates that this file will replace an existing file when the system is booted from this staging area.

  • ADD — Indicates that this is a new file.

  • DELETE — Indicates that this file will be deleted when the system is booted from this staging area.

  • IGNORE — Files with this disposition are placed in the staging area, but are ignored during system start.


  [;ONERR=error_action] (Optional)
Values: WARN(W), IGNORE (I)

Default: WARN (see also SETDEFAULT)

If an error occurs while processing a file, the error_action for that file will dictate what the start code will do.

  • WARN — start will continue. An error message will be printed.

  • IGNORE — start will continue, no error message will be printed.


  [;VAL=val_method] (Optional)
Values: BASIC (B), EXISTENCE (E), CHECKSUM (C)

Default: BASIC (see also SETDEFAULT)

This parameter describes which technique will be used to determine if a particular file is valid at validation time (see VALIDATE). All files in a staging area must be considered valid before HP Stage/iX will consider the staging area valid.

  • BASIC — Basic validation should be performed on this file. This includes insuring that the file exists in the staging area, and that the disk space restrictions match what they should be.

  • EXISTENCE — The file that the staged file corresponds to must exist in the Base.

  • CHECKSUM — The computed checksum for the file corresponding to the final target file name must be in the array of acceptable checksums (see: validation_info parameter).

The CHECKSUM option is not currently supported. 

  [;VALINFO="val_info"] (Optional)
The VALINFO parameter is not currently supported. 

  [;LIFTYPE=lif_type] (Optional)
Values: NONE, BOOT, IPL, DATA, AUTOF

Default: NONE (see also SETDEFAULT)

Determines whether or not the file belongs in the system LIF Directory, and if so, what file type it should be placed in the directory as. 

  [;OWNER="owner_name"] (Optional)
Default: "MANAGER.SYS"

The owner name that should be assigned to the staged file. 

  [;{MOVE}]
The default behavior for the STAGEFILE command is {COPY} is to copy the file to the staging area, thus not deleting the FROM file. If you want the FROM file to be purged, use the MOVE option.

Example


  STAGEMAN> STAGEFILE STAGE1, NL.INSTALL.SYS, NL.PUB.SYS
  STAGEMAN> STAGEF STAGE1, START.INSTALL.SYS,
  START.MPEXL.SYS;DISK=C
  STAGEMAN> SF STAGE1, SL.INSTALL.SYS, SL.PUB.SYS;ONERR=WARN

STATUS (ST)

The STATUS command can be used to display the current status of the HP Stage/iX environment. If HP Stage/iX is initialized, then the STATUS command will give some basic information about the HP Stage/iX subsystem (including the name of the staging area that is currently in use, and the name of the staging area that is to be used on the next restart of the system). If the HP Stage/iX facility is not currently initialized, the STATUS command will only report that fact.

For additional information on a particular staging area use the LIST command. For additional information about designating a particular staging area to be used for the next reboot of the system see the SET command.

The STATUS command can be abbreviated ST.

Syntax


  STATUS

Parameters


  (none)

Example

To view basic HP Stage/iX information: 

  STAGEMAN> STATUS
  Last booted with: BASE
  Next boot will be with: stage_1

UNINSTALL

The UNINSTALL command COMPLETELY uninstalls the HP Stage/iX facility. If you type UNINSTALL, then ALL HP Stage/iX staging areas will be deleted. In addition ALL HP Stage/iX directories, files, and data structures will be deleted.

The HP Stage/iX facility will be considered uninitalized after doing an UNINSTALL command. It can be re-initialized using the INITIALIZE command, but any staging areas which were deleted will be lost.

The UNINSTALL command will always prompt for confirmation to UNINSTALL HP Stage/iX unless you explicitly specify the ;NOCONFIRM option.

To execute UNIINSTALL, you must be running from your Base location (SET to Base). All staging areas will be removed. You cannot execute UNINSTALL while you are running from a Staging Area (SET to staging_area).

The UNINSTALL command cannot be abbreviated.

Syntax


  UNINSTALL [;{ CONFIRM}]
              {NOCONFIRM}

Parameters


  [;{ CONFIRM}] (optional)
    {NOCONFIRM}
The ;CONFIRM or ;NOCONFIRM option specifies whether or not the UNINSTALL command will prompt for confirmation. If you specify ;NOCONFIRM, then STAGEMAN will NOT prompt for confirmation. The default is ;CONFIRM.

Example

To uninstall HP Stage/iX: 

  STAGEMAN> UNINSTALL
  This will destroy your HP Stage/iX environment. Are you sure [Y/N]? y
  Successfully uninstalled the HP Stage/iX environment.
To uninstall HP Stage/iX without prompting for confirmation: 

  STAGEMAN> UNINSTALL;NOCONFIRM
  Successfully uninstalled the HP Stage/iX environment.

USE

The USE command is used to execute STAGEMAN commands from an ASCII command file. USE opens the specified file, executes all commands from the file, and then closes the file and returns to interactive user input. USE commands can be nested.

Syntax


  USE [FILENAME=]filename

Parameters


  [FILENAME=]filename (required)
Any valid MPE/iX file for which you have READ access.

Example

To use the USE command to process an ASCII file in STAGEMAN, enter: 

  STAGEMAN> VALIDATE

VALIDATE (VAL)

An HP Stage/iX staging area must be validated before it can be used. The VALIDATE command is used to validate a staging area. VALIDATE will verify the integrity of the staging area, and will report back any problems with the staging area. If there are no problems, a "valid" flag will be set stating that the staging area is ready for use.

The LIST command can be used to view the current status (valid or invalid) of a staging area. The INVALIDATE command will reset the valid flag, preventing a particular staging area from being used.

The VALIDATE command can be abbreviated VAL.

Syntax

Normal Mode: 

  VALIDATE [[STAGE=]stage_name]
Expert Mode: 

  VALIDATE [[STAGE=]stage_name] [;NOOVERRIDE]
                                [;OVERRIDE ]

Parameters


  [[STAGE=]stage_name (required)
The name of the HP Stage/iX staging area to be VALIDATED. This must be a legal staging area name for a pre-existing staging area. The staging area cannot be in use or designated for use on the next boot (see the SET command).

Staging area names are case sensitive. "STAGE1" is not equivalent to "stage1" or "Stage1".

Expert Mode Parameter: 

  [;{NOOVERRIDE}] (optional)
    { OVERRIDE}
If ;OVERRIDE is specified, then STAGEMAN will set the valid flag without checking to see if the contents of the staging area are really valid. Otherwise, STAGEMAN will validate that each file is actually in the staging area, that each file is OK (for example, disk space restrictions are observed), and any additional checking that may be performed on a file by file basis (see the STAGEFILE command).

The default value for this parameter is ;NOOVERRIDE.

Example


  STAGEMAN> VALIDATE STAGE=stage_1



Using HP Stage/iX

Appendix H Error Messages and Warnings