MPE/iX Commands Reference Manual > Chapter 12 Command List X

Commands SAVE thru SHUTQ

	MPE documents
	Complete PDF
	Table of Contents
	Index

SAVE
SECURE
SEGMENTER
SET
SETCATALOG
SETCLOCK
SETCOUNTER
SETDUMP
SETJCW
SETMSG
SETVAR
SHOWALLOCATE
SHOWALLOW
SHOWCATALOG
SHOWCLOCK
SHOWDEV
SHOWIN
SHOWJCW
SHOWJOB
SHOWLOG
SHOWLOGSTATUS
SHOWME
SHOWOUT
SHOWPROC
SHOWQ
SHOWTIME
SHOWVAR
=SHUTDOWN
SHUTQ

SAVE

Saves a file in the permanent system file domain.

Syntax


  SAVE { $OLDPASS,newfilereference | tempfilereference }

Parameters

$OLDPASS

A system-defined temporary file. After this file is saved, it can no longer be referenced by the name $OLDPASS.

newfile-reference

New actual file designator assigned to $OLDPASS when it is made permanent. Its format is:


  filename[/lockword][.groupname[.acctname]]

If groupname is used, it must indicate a group to which you have save access, as defined by your account manager. If groupname is omitted, the logon group is assigned.

tempfile- reference

Actual file designator of the temporary file to be made a permanent file under the same designator. The file is deleted from the job/session temporary file domain and entered into the system file domain. Its format is:


  filename[/lockword][.groupname[.acctname]]

If groupname is used, it must indicate a group to which you have save access, as defined by your account manager. If groupname is omitted, the logon group is assigned.

Operation Notes

The SAVE command saves a temporary file by converting it to a permanent file in the system file domain. This command is necessary when the subsystem or program that created your file does not allow you to save it while the program is executing.

You must specify a new filename for $OLDPASS, because MPE/iX does not allow $OLDPASS as a permanent file name. If there is a file in the temporary domain with the same name specified by newfilereference, MPE/iX attempts to save $OLDPASS by creating a new temporary file. This temporary file name, created by SAVE, starts with S and is followed by seven digits: Sdddhhmm, where ddd is the Julian day of the year, hh is the hour of the day, and mm is the minute. The new temporary file is then saved under the file name specified by newfilereference, and is deleted from the temporary domain. If both temporary and permanent files exist under the same name specified by newfilereference, the temporary SAVE file is saved as a permanent file. In this case, a printed error message states the file name for the new SAVE file. It can be renamed later using the RENAME command.

This command applies only to temporary files on disk. It is similar to opening a file with the FOPEN intrinsic, and then closing it with the FCLOSE intrinsic, using a permanent file disposition.

Use the SAVE command to save KSAM XL files. Since the KSAMUTIL utility is not supported for KSAM XL, the SAVE command is the only method of doing so.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Examples

To save the temporary file $OLDPASS, containing an object program, to the program file PROGFILE, enter:


  SAVE $OLDPASS,PROGFILE

To save the temporary file TEMPFL as a permanent file with the same name, enter:


  SAVE TEMPFL

To save the temporary file DATAFILE in the group GROUPX, enter:


  SAVE DATAFILE.GROUPX

To save a temporary file (other than $OLDPASS) and change its name, use the SAVE and RENAME commands. Only the logon group and account directories in the current session are searched, for example:


  SAVE DATAFILE
  RENAME DATAFILE,DATABASE

Related Information

Commands: PURGE, LISTFILE, LISTFTEMP, RENAME
Manuals: None

SECURE

Reinstates all file security provisions that you previously suspended with the RELEASE command.

Syntax


  SECURE filereference

Parameters

filereference

Specifies the actual file designator for which you want to reinstate file access control. The filereference can be either in MPE or HFS syntax.

MPE Syntax

If the filereference does not begin with a dot or a slash, it is parsed according to the MPE syntax and has the form:


  filename[/lockword][.groupname[.acctname]]

If the file has a lockword, you must specify it; otherwise, the system prompts you for it. If you do not specify groupname.acctname, the system assumes the logon group and account.

HFS Syntax

If the filename begins with a dot (.) or a slash (/), it is parsed according to HFS syntax.

Operation Notes

Usage
You can use this command only for permanent disk files you created. Under default system security provisions, the file must be in your logon account and must belong to your logon or home group.

Checking the file status
You can enter the LISTFILE command to determine if a file is currently released or secured. Refer to the LISTFILE command in this book for more information.

Access control definition
An access control definition (ACD) overrides file access controls whether or not you have released or secured the file.

Use

You can enter this command from a session, a job, a program, or in break mode. Pressing Break does not affect this command.

Example

To reinstate file access control previously in effect for the file named FILE1, enter:
```
  :SECURE FILE1
```

Related Information

Commands: ALTSECT, LISTF, LISTFILE, RELEASE
Manuals: None

SEGMENTER

Starts the MPE segmenter.

Syntax


  SEGMENTER [listfile]

Parameters

listfile: Actual file designator of an ASCII output file that is to receive listed output from the MPE segmenter. Formal file designator is SEGLIST. Default is $STDLIST. Usually this file is a line printer. This must be defined in a FILE command, and then backreferenced (see "Example").

NOTE: The formal file designator used in this command, SEGLIST, cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

This command starts the segmenter subsystem from MPE/iX. The segmenter subsystem performs the intermediate functions between source code compilation and program execution.

The segmenter employs temporary files named T999SYM, SEGTMP01, and SEGTMP00. If you create temporary files with these names, the segmenter attempts to purge them.

You must have READ and LOCK access to use a relocatable library with the SEGMENTER command.

Use

This command may be issued from a session or a job. It may not be issued in BREAK or from a program, unless the user or the MPE segmenter has process handling (PH) capability. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

Example

To call the MPE segmenter from a session and transmit the output to a line printer instead of the standard list device, enter:


  FILE LISTFL;DEV=LP
  SEGMENTER *LISTFL

Related Information

Commands: FILE
Manuals: MPE Segmenter Reference Manual

SET

Defines elements of the command interpreter. It also allows a job using a spooled $STDLIST to mark its standard list device for deletion when the job terminates. (Native Mode)

Syntax


  SET [STDLIST= { DELETE | SAVE }] [;MSG= { ON | OFF }]
      [ECHO= { ON | OFF }]
      [;SPEED= { 300 | 1200 | 2400 | 4800 | 9600 | 19200 | 19.2K }]

Parameters

DELETE: Flags the job's $STDLIST for deletion at job termination.
SAVE: Cancels the effect of a previous SET STDLIST=DELETE command. Default is SAVE.
ECHO: Turns terminal echoing ON or OFF.
MSG: Specifies whether or not TELL messages are displayed on the user's terminal. MSG=OFF prevents TELL messages from appearing on the terminal. WARN messages override MSG=OFF and will appear on the terminal. (This parameter provides the same function as the SETMSG command.)
SPEED: Specifies the terminal's data transmission rate, within the upper and lower bounds outlined above. The user is responsible for manually changing the terminal's speed setting. (This parameter provides the same function as the SPEED command.)

Operation Notes

The SET command specifies several elements of the command interpreter including the terminal echo and baud rate.

In a job, the SET command can be placed anywhere between the JOB and EOJ statements. It is most practical to place it at the end of a job stream since the command does not execute if the job fails. $STDLIST then prints, allowing you to study your listing and to locate the problem. The effect of a SET STDLIST=DELETE can be reversed by entering SET STDLIST=SAVE into the job stream. Note that the SET command works only on jobs with a spooled $STDLIST.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

The following example illustrates using the SET command from within a program:


  !JOB EXAMPLE, USER.TECHPUB,XGROUP
  !CONTINUE
  !RUN UPDATE.PUB.SYS;PARM=1;MAXDATA=16000
  !IF JCW < FATAL THEN
  !SET STDLIST=DELETE
  !ENDIF
  !EOJ

Related Information

Commands: SETMSG, SPEED, ECHO
Manuals: None

SETCATALOG

Catalogs, or enables, the user-defined commands (UDCs) in a specified catalog file at the user, account, or system level. You can also use this command to disable all UDCs on the system. (Native Mode)

WARNING! If you do not specify a catfilename, all UDC's are disabled (deleted from the UDC directory) regardless of whether or not the ;DELETE option is used.

Use only MPE/iX flat files as UDC files. Issuing the SETCATALOG command for any other file type may cause unpredictable results.

Syntax


  SETCATALOG [ catfilename [,catfilename [, ...]]]
    [ ;SHOW] [ ;SYSTEM] [ ;ACCOUNT]
    [ ;USER= username[.acctname]]
    [ ;RESET][ ;APPEND][ ;DELETE]

Parameters

catfilename: The name of a file containing user-defined commands to be cataloged. Commands within the file must be separated from each other by a line whose first character is an asterisk (*).
SHOW: Specifies a listing of the user-defined commands as the UDC files are cataloged. Error messages are printed for command lines that contain any errors. This parameter is useful for locating errors in UDC files.
ACCOUNT: Specifies cataloging of the file at the account level. Using this parameter requires account manager (AM) capability.
SYSTEM: Specifies cataloging of the file at the system level. Using this parameter requires system manager (SM) capability.
USER: Allows users who have AM capability to change the UDC catalog set for users in their account. Users having SM capabilities can change the UDC catalog set for any user. USER does not rebuild an executing UDC directory, but becomes effective when the user logs off and then logs on after the command has been invoked.
RESET: Causes the file(s) being cataloged to replace all files that are already cataloged. RESET is the default if no option is specified.
APPEND: Permits the user to add UDCs to the directory. This option causes the file(s) being cataloged to be appended to the existing catalog. It also finds and makes adjustments for any logon UDCs if appropriate.
DELETE: Deletes the file(s) from the existing UDC directory. This permits the user to delete individual files from the catalog directory. The original order of the catalog is maintained. It also finds and makes adjustments for logon UDCs. The ACCOUNT and SYSTEM options allow the user to delete the cataloged file at the account or system levels. The default is user level.

Operation Notes

The SETCATALOG command allows you to catalog user-defined commands.

When you set your own UDCs, the change takes place in your UDC catalog immediately. If you specify the ACCOUNT or SYSTEM parameter, your UDC catalog is changed immediately, but other users in your account or system must log on again in order to have those changes available to them. If you set a UDC and specify another user (USER=), that user must log on again in order to have the changes available.

The ability to delete or append files is particularly useful because, although most UDC files do not change, new UDC commands are frequently added or modified. Using the DELETE or APPEND parameter allows you to make changes without incurring the overhead of recataloging the entire directory for every change. Grouping UDC files into functions further reduces the work involved in modifying UDCs.

The RECURSION option relieves the user of having to define a particular command more than once in a catalog set, and from having to maintain a particular order for commands within a catalog set. Refer to the discussion on options in "User Commands" in Using the HP 3000 Series 900: Advanced Skills.

If SETCATALOG is used in a UDC, all valid commands through and including the SETCATALOG command execute. But execution of the UDC terminates after the execution of the SETCATALOG command. Commands that follow do not execute. The SETCATALOG command does not have this effect when executed in a command file.

The SETCATALOG command may be invoked only from the logon command interpreter (user main), where it is passed through the scanner/parser. It cannot be invoked from any other program (any child process).

Use

This command is available in a session, job, or in BREAK. It is not available from a program. Pressing Break has no effect on this command.

Examples

The following command sets the UDC directory for the user JOHN.WORKERS with the commands in the file named UDCA. The USER option cannot be specified with the ACCOUNT or SYSTEM options. Attempting to do so produces an error.


  SETCATALOG UDCA; USER=JOHN.WORKERS

The following two command sequences are equivalent:


  SETCATALOG UDCA, UDCB
  SETCATALOG UDCA
  SETCATALOG UDCB ;APPEND

In the first example, the command has an implied RESET, and thus overwrites the previous file set in the directory. In the second example, UDCA is entered into the directory, and then UDCB is appended to the directory without affecting UDCA. It also finds new logon commands if appropriate.

The following command deletes UDCA from the directory at the account level, provided it was cataloged at the account level. If other account-level UDCs reside in the directory along with UDCA, they remain undisturbed by this deletion. When appropriate, a new logon UDC is set up.


  SETCATALOG UDCA ;DELETE ;ACCOUNT

NOTE: It is not a good practice to create UDC's which have the same name as other files, especially command files or any other files your users may confuse with UDC's.

If you enter a fully qualified file name that has the same name as an existing UDC, the group and account part of the fully qualified name are passed to the UDC as a parameter. For example, if COMM is a UDC, entering COMM.GROUP.ACCT will cause .GROUP.ACCT to be passed to COMM as a parameter even if COMM.GROUP.ACCT is a separate file.

Related Information

Commands: SHOWCATALOG, HELP <udcname>
Manuals: System Startup, Configuration, and Shutdown Reference Manual
Using the HP 3000 Series 900: Advanced Skills

SETCLOCK

Alters the system time or system time zone.

SYNTAX


  SETCLOCK {DATE=date-spec ;TIME=time-spec [; { GRADUAL | NOW }]}
    [CORRECTION= correction-spec]
    [TIMEZONE= timezone-spec]
    [ ;CANCEL]

Parameters

date-spec

A specification of local date in the form mm/dd/yy[yy]. The year may be expressed in two or four digits. If a date is provided, a time must also be provided.

time-spec

A specification of local time in the form hh:mm[:ss] where seconds are optional. This specification uses a 24-hour clock; it is not permissible to specify the time using A.M. or P.M. If a time is provided, a date must also be provided.

The operating system will experience problems if the system date and time are too close to the base time of midnight, January 1, 1970. Therefore, for proper system operation this command requires the date and time to be later than ten minutes past midnight on January 1, 1970.

correction-spec

An integer specifying the desired change in the system time. The units are seconds. Thus a positive correction will cause the system clock to advance by the specified number of seconds, while a negative correction will cause the system clock to slow by the specified number of seconds.

time-zone-spec

A specification of the time zone in the form hh:mm, preceded by a required "W" or "E" to specify the Western or Eastern Hemisphere. Thus a specification of W7:00 represents a seven-hour displacement from Universal Time (GMT) with the time zone being in the Western Hemisphere.

Providing a time zone spec is the only way to change the system time and maintain both local and Universal Time (GMT) accurately. See the Operation Notes section for details.

GRADUAL

This option is meaningful only when the date and time specifications are provided. GRADUAL causes the system clock to speed up or slow down until the time change is completed, at which time the system clock will resume its normal pace. GRADUAL is the default for the Date-Time form of the command.

NOW

This option is meaningful only when the date and time specifications are provided. NOW forces the change to be immediate. See the warning in the Operation Notes section about the dangers of changing the system time immediately.

CANCEL

Cancels a current time correction. Any correction which has already taken place before the cancellation will remain; this option does not undo a correction which has already been accomplished. See the Operation Notes and Examples sections for details.

Operation Notes

The SETCLOCK command is used to change the system time or to change the system's time zone.

Changing the system time or time zone does not affect any interval timers in effect. Thus, a PAUSE for a given time duration will maintain that same duration regardless of how the system time is changed.

Changing the system time or time zone will cause any jobs streamed with a time specification (;AT=, ;DAY=, ;DATE= or ;IN=) to be introduced in accordance with the newly-changed system time. Thus, a job streamed with ;AT=9:00 will be introduced when the changed system time is equal to 9:00.

The user may provide SETCLOCK with a date and time, a time correction, or a time zone. The Date-Time form, the Correction form, and the Time Zone form are mutually exclusive; for instance, the user may not provide specifications for both a time correction and a time zone in a single command.

The Date-Time and Correction forms of the command are intended for slight adjustments of the system time. For example, these forms would be used to move the time forward or backward slightly in order to keep the system time synchronized with an external time source. Both local and Universal (GMT) time are adjusted.

The Time Zone form of the command is intended for the larger time changes required to move the system to a new time zone, such as moving between Standard Time and Daylight Savings Time. This form of the command alters the local time without changing Universal Time.

Date-Time: If the Date-Time form of the command is used, the system time is adjusted to the specified date and time. This adjustment is gradual by default. It may be made immediate if ;NOW is specified and the user has System Manager (SM) capability.

Correction: If the Correction form of the command is used, the system time is adjusted forward or backward by the amount of the correction. This adjustment is always gradual.

Time Zone: If the Time Zone form is used, local time is adjusted to match that of the specified time zone. In addition, the system time zone offset is changed to reflect the new time zone.

The Use of The Time Zone Offset

On the HP3000 Universal Time (GMT) is calculated by starting with local time and adding or subtracting a time zone offset. When changing time zones (such as moving from Standard to Daylight Savings Time and back) the local time is altered, but this change must not affect Universal Time. To prevent Universal Time from being altered, both the local time and the system time zone offset must be adjusted. Therefore, using the Time Zone form of this command is the only way to accurately change time zones.

If the Date-Time or Correction form of the command is used, Universal Time will drift along with local time. Thus, the Date-Time and Correction forms of this command should only be used to adjust the clock for drift, not to change time zones.

Results of the Time Zone Form

If the change in time zone is to a later time (a change to Daylight Savings Time or an "Eastern" geographic movement), both local time and the time zone offset are changed immediately.
The effect is that users of local system time will see an immediate jump forward to the new time zone, while users of Universal Time will see no change.
If the change in time zone is to an earlier time (a change from Daylight Savings to Standard Time or a "Western" geographic movement), the time zone offset is changed immediately. Then the local time slows down until the system time corresponds to the time in the new time zone.
The effect is that users of local system time will see a gradual slowdown to match the new time zone, while users of Universal Time will see an immediate forward jump, then a slowdown until the system time again matches "real" Universal Time.

This method of changing time zones ensures that no out-of-sequence time stamps will occur either in local time or in Universal Time.

How a Gradual Time Change Works

Whether the Date-Time or a Correction form is used, the default method of changing the time is to gradually speed up or slow down the system clock until the change is achieved. Thus, even when a previous time is requested, the system clock will still move forward, although at a slower pace than real time. This slower pace will continue until the desired time "catches up" with the system clock. Because of the system clock's forward motion, there will never be a case where two consecutive timestamps appear to be out of sequence and where system time appears to run backwards.

This change in clock speed is accomplished by establishing a system time correction which is gradually consumed. During this time the system clock speeds up or slows down as necessary. When the correction reaches zero, the system clock resumes its normal pace. The rate of the correction depends on the load on the system. The correction rate will be slowed down by frequent timestamp requests, file accesses and frequent operating system activity such as context switches. In general, the correction will take no longer than twice the requested time difference. For example, a request to slow down the clock by one hour will take a maximum of two hours to complete.

Results of the ;CANCEL Parameter

Any time during an on-going correction, issuing this command with the ;CANCEL parameter will immediately set the correction to zero and cause the system clock to resume its normal pace. Any previous correction will remain. When this option is used, the system will report the amount of correction which was cancelled.

How a System Time Change Affects Accounting Information

Changing the system time, even gradually, may cause accounting CONNECT-MINUTES to be distorted. Anyone logging on before the change and then logging off after the change is completed will have their accounting CONNECT-MINUTES data distorted; if the time change is forward, CONNECT-MINUTES will be increased by the amount of the time change, and if the time change is backward, CONNECT-MINUTES will be decreased by the amount of the time change.

Dangers in Using the ;NOW Parameter

The ;NOW parameter permits immediate forward or backward time changes. However, several dangerous situations can occur:

Any applications which rely on the forward progression of time may give inconsistent results if the time is immediately set backwards. Such applications include the processing of timestamped transactions in which the sequence of those transactions is important.
In order to recover data in case of an unexpected hardware or software failure, some applications require that the system time must never seem to go backwards. For instance, some applications log transactions to a circular file. These transactions are timestamped, and if the transactions must be recovered, the recovery program determines the end of data by looking for timestamps which are out of sequence. If the system time is set backwards immediately, transactions which occur after the time change may not be recovered. Therefore, do not set the time backwards using the ;NOW option if there are applications which log their transactions using timestamps.
Accounting CPU-SECONDS data may be distorted. The user whose process was active during an immediate forward or backward change might seem to have a CPU-SECONDS time which is an extremely large positive or negative number.
STORE/RESTORE, TurboSTORE/XL, or any other file archive system based on dates or times may not store or restore the files in the expected manner, since some files may have creation or access times in the future or may even have access times which precede their creation times.
Some compilation tools like MAKE rely on the relative modification dates of the files in the compilation unit. Setting the system time backward and then modifying the main file in the compilation unit may force an unnecessary full compilation, since the main file may have an earlier modification time than the files it depends on. Setting the system time backward and then changing a file needed by the main file will cause MAKE to think that the changed file's modification time precedes that of the main file. Thus, the changed file will not be included in the recompilation.

This list is only meant to include a few of the dangers associated with an immediate time change; this list does not represent all of the problems likely to be encountered. Therefore, if the ;NOW option must be used, it should be used only with a full knowledge of its effects on the system's workload.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Diagnostician (DI) and either Operator (OP) or System Manager (SM) capabilities are required to issue this command. Additionally, System Manager (SM) capabiltiy is required to use the ;NOW parameter.

Examples of Date-Time and Correction Forms:

The following example illustrates setting the system time by providing a date and time:


  :SETCLOCK DATE=07/04/1993;TIME=15:00

The following example illustrates providing a time correction to advance the system time by one hour.


  :SETCLOCK CORRECTION= +3600


  :SETCLOCK CORRECTION= 3600

Both of the above examples cause Universal Time (GMT) to change as well as local time, and therefore while they are useful in correcting the system time for drift (time gain or loss), they are not accurate ways to change time zones.

The following example illustrates setting a time correction, executing a SHOWCLOCK command, cancelling the correction, then again executing a SHOWCLOCK command. Note that by the time of the first SHOWCLOCK the correction has already begun to be consumed.


  :SETCLOCK CORRECTION= -3600
  
  :SHOWCLOCK
  
  SYSTEM TIME: FRI, JUL 24, 1987, 8:47:35 AM
  CURRENT TIME CORRECTION: -3568 SECONDS
  TIME ZONE: 7 HOURS 0 MINUTES WESTERN HEMISPHERE
  
  :SETCLOCK; CANCEL
  
  CORRECTION OF -3550 SECONDS HAS BEEN CANCELLED
  
  :SHOWCLOCK
  
  SYSTEM TIME: FRI, JUL 24, 1987, 8:52:53 AM
  CURRENT TIME CORRECTION: 0 SECONDS
  TIME ZONE: 7 HOURS 0 MINUTES WESTERN HEMISPHERE

Note that in the example above the system clock was slower than normal for several minutes. Cancelling the correction did not undo that change; it merely prevented any further time change. Thus after this sequence of commands, the system clock is set to a slightly earlier time than if no SETCLOCK command had been issued.

Examples of the Time Zone Form:

Moving from Standard Time to Daylight Savings Time:

The following example illustrates changing the system time zone offset from 8 hours 00 minutes in the Western Hemisphere (Pacific Standard Time) to 7 hours 00 minutes in the Western Hemisphere (Pacific Daylight Savings Time). This command will cause local time to jump forward immediately one hour. Universal Time will be unchanged.


  :SETCLOCK TIMEZONE=W7:00
  
  SYSTEM TIME: SUN, APR 4, 1993, 7:12:00 AM
  CURRENT TIME CORRECTION: 3600 SECONDS
  TIME ZONE: 7 HOURS 0 MINUTES WESTERN HEMISPHERE

Moving from Daylight Savings Time to Standard Time:

The following example illustrates changing the system time zone offset from 7 hours 00 minutes in the Western Hemisphere (Pacific Daylight Savings Time) back to 8 hours 00 minutes in the Western Hemisphere (Pacific Standard Time). This command will cause local time to slow down until it loses one hour. Users of Universal Time will see an immediate one-hour jump forward, followed by a slowdown until system Univeral Time again matches real Universal Time.


  :SETCLOCK TIMEZONE= W8:00
  
  SYSTEM TIME: SUN, OCT 31, 1993, 06:23:14 AM
  CURRENT TIME CORRECTION: -3600 SECONDS
  TIME ZONE: 8 HOURS 0 MINUTES WESTERN HEMISPHERE

Related Information

Commands: SHOWCLOCK, SHOWTIME
Manuals: Performing System Management Tasks

SETCOUNTER

Sets the next value of a specified resource counter, and optionally enables automatic rollback when a specified limit is reached. Duplicate values are avoided.

Syntax


  SETCOUNTER [ COUNTER=] [ INSP | OUTSP | JOBNUM | SESSNUM ]
    [ ;BASE = num] [ ;MAX = num ]
    [ ;SHOW]

Parameters

INSP

Specifies the input spoolid counter.

OUTSP

Specifies the output spoolid counter.

JOBNUM

Specifies the job number counter.

SESSNUM

Specifies the session number counter.

The target counter (INSP, OUTSP, etc.) is only optional if the SHOW option is used by itself to display BASE and MAX values for all counters without changing any of them. For any other form of the command, the target counter is a required parameter.

num

A positive integer. For MAX, num may also equal zero. A non-zero num for MAX must be less than or equal to the maximum possible value for that counter. Those values are:

INSP: 9999999
OUTSP: 9999999
JOBNUM: 16383
SESSNUM: 16383

For BASE, num must be less than MAX, except when MAX is equal to zero.

Operation Notes

The SETCOUNTER command allows you to specify limits other than 1 and the maximum possible value of one of four counters (but within that range) You may set limits for one counter with each use of the command and, therefore, you must invoke the command four times to change the limits of all four coutners.

You may also use SETCOUNTER to display the current values of the counters. Only one invocation of the command is necessary to see all current values.

To set a maximum operating value for the specified counter and enable its operation, enter a positive value for the MAX keyword. Specify MAX=0 to disable the operation, that is, the counter's limit is then its maximum possible value. Omitting MAX leaves its previous value in force. Once MAX is reached, the next value tried is the BASE value. If you specify a non-zero value for MAX, it must be greater than the current BASE for the corresponding counter, but less than the maximum possible value.

The BASE keyword causes the specified counter to be immediately yanked to the specified value. If you supply a value, it must be less than the supplied or current value of MAX (other than 0), and in any case, less than the maximum possible value. If you do not specify BASE, it is not changed, nor is current sequencing affected.

For each counter, duplicate values are avoided. For example, if #O10 is in use when due to be assigned as the next output spoolid, it is skipped and #O11 is tried. This process continues until an available value is found.

The defaults, established when the system is booted, are MAX=0 and BASE=1. This is for backward compatibility; if these settings are not changed, the system will operate as it does today. These boot time settings can be modified by including one or more instances of this command in SYSSTART.PUB.SYS.

The SHOW option can be used alone to display the current values of BASE and MAX for a specified counter or for all four counters. If used in addition to either BASE or MAX, the value(s) displayed are the new setting(s).

This command may be issued from a session, job, program, or in Break. Any display specified by the SHOW option is breakable, but command operation is not. Any user may execute this command with only the SHOW option to display current values of BASE, Next, and MAX for the specified counter (or all counters if none is specified). When changing either value, this command may be executed only:

at a console session,
by a user with SM capability, -OR-
by any user who has been allowed the use of the SETCOUNTER command with the ALLOW command.

Examples

To display the current BASE, Next, MAX, and maximum possible values for all four counters, enter:


  :SETCOUNTER ;SHOW
                                                          Absolute
     Counter        BASE        Next           MAX        maximum
  ---------------   -----    --------    ----------    ----------
  Input spoolid:        1         172         16383       9999999
  Output spoolid:       1        1872         32767       9999999
  Job number:           1         172             0         16383
  Session number:       1        2753             0         16383

To limit input spoolids to the same range as their corresponding jobs, enter:


  :SETCOUNTER INSP; MAX=16383

Related Information

Commands: SWITCHNMLOG
Manuals: None

SETDUMP

Arms the system debug facility for a process abort. (Native Mode)

Syntax


  SETDUMP [DB [,ST [,QS]]] [;ASCII] [;DEBUG="commands"]

Parameters

DB: This parameter is ignored.
ST: This parameter is ignored.
QS: This parameter is ignored.
ASCII: This parameter is ignored.
"commands": A string of system debug commands surrounded by quotation marks. Refer to the DEBUG command in this chapter.

Operation Notes

This command enables the stackdump facility for any process created later under the current session or job. If the call is armed (enabled), and the process aborts, SETDUMP executes the system debug commands given in the "commands" parameter.

If no commands are specified, a default command string is used to produce a stacktrace and register dump.

If the process is interactive, it subsequently enters the system debugger to wait for further commands. If it is not interactive, the process simply terminates instead of entering the debugger.

Any combination of the four strings (DB, ST, QS, or ASCII) is parsed without error in MPE/iX, but they have no effect on the functional behavior of the commands. The "commands" string, preceded by the DEBUG keyword, is interpreted as a series of system debug commands and is sent to the system debugger that way.

The "commands" parameter may contain a maximum of 255 characters.

NOTE: The DB, ST, QS, and ASCII parameters are retained for compatibility reasons. These parameters are ignored.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

To arm the stackdump/debug facility, enter:


  SETDUMP

Related Information

Commands: DEBUG, RESETDUMP
Manuals: System Debug Reference Manual

SETJCW

Creates or assigns a value to a job control word (JCW) variable.

Syntax


  SETJCW jcwname delimiter value [{ + | - }value]

Parameters

jcwname

The name of a new or existing user-defined or system-defined job control word (JCW). You can use @ to specify all currently defined JCWs.

You may not specify the system-reserved JCWs, HPMINUTE, HPHOUR, HPDAY, HPDATE, HPMONTH, or HPYEAR.

delimiter

One or more punctuation characters or spaces, except %, !, and -. Whatever character is used delimits the name and value.

value

One of the following:

An octal number between %0 and %177777, inclusive.
A decimal number between 0 and 65,535, inclusive.
An MPE/iX-defined JCW value mnemonic (OK for 0; WARN for 16,384; FATAL for 32,768; SYSTEM for 49,152) or an offset value of a mnemonic (OK3 for 0 + 3).
The name of an existing JCW.

All specified values must be in the range of 0 to 65,535, inclusive. If the option + or - is used, the result of the indicated operation must also be within the range of 0 to 65,535, inclusive.

Operation Notes

A job control word (JCW) is a flag that allows information to be passed between processes within a single job or session. There are three forms of JCWs: system-defined, user-defined, and system-reserved.

Job control words in MPE/iX are classed as system variables of type JCW. You may delete user-created variables. You may modify the two system-defined variables CIERROR and JCW. Refer to appendix A, "Predefined Variables in MPE/iX," for a list of system-defined variables.

The SETVAR command creates and assigns variables too, but variables created or assigned with SETVAR are not of type JCW and cannot function as true job control words.

If you create or assign a value to a variable using the SETJCW command and later reassign its value using the SETVAR command, the reassignment succeeds. If the new value is out of range for a JCW, the variable type is changed to that of an ordinary user-defined variable:


  SETJCW PROGCNTR 0
  ....
  SETVAR PROGCNTR 65536
  JCW VARIABLE RECLASSIFIED AS A STANDARD VARIABLE (CIWARN 8126)

PROGCNTR is now a user-defined variable and does not function as a job control word.

JCWs can be tested against specific values. The user can use IF and WHILE conditional statements that act according to the results of these tests. The user-defined JCWs can also be set to user-selected values by a process so that they reflect the completion of steps within that process. System-defined JCWs can be used to determine whether certain events have occurred within MPE/iX.

The values in the system-reserved JCWs can be inspected by the user, but not altered.

To display the contents of a JCW use the SHOWJCW or the SHOWVAR command.

JCW Values and Mnemonics

JCWs may be assigned any positive integer value between 0 and 65,535 inclusive (%0 and %177777). These values are treated as 16-bit unsigned integers by MPE/iX, since all 16 bits are used for numeric information, rather than using the most significant bit as a sign bit.

MPE/iX treats the two most significant bits of a JCW in a special way: the bits define "bases" or "steps" of 16K each. Each of these steps is given a mnemonic to simplify references to it or to the numbers between steps. If the 14 least significant bits are considered to be zeros, the two "step" bits, step value (in decimal), and mnemonic have the following relationship:

Table 12-1 JCW Values and Mnemonics

Bit Value	Step Value	Mnemonic
00	0	`OK`
01	16,384	`WARN`
10	32,768	`FATAL`
11	49,152	`SYSTEM`

It is important to remember that these mnemonics are not the names of JCWs. They cannot be used as user-defined JCW names.

You may use a combination of mnemonics and numbers to indicate numeric values between steps. If you specify a mnemonic and a number with no intervening spaces, an implied addition takes place. For example, WARN3 has a value of 16,387, since it is WARN (16,384) plus 3. The value of the mnemonic plus the appended number value may not exceed 65,535. Again, no valid value of the form, mnemonic[number], may be used as a valid user-defined jcwname. An explicit addition or subtraction can also be specified, using a + or - sign, as in OK+7 (7) or WARN-4 (16,380). A mnemonic may also be added to another mnemonic, as in WARNFATAL.

The result of a mathematical operation must be in the range of 0 to 65,535, inclusive; if the number is out of range, an error message is generated, and the value of the JCW remains unchanged. When the result of an operation is greater than the value of the next "step", the JCW value displayed by the SHOWJCW command will be the mnemonic of the higher step plus any offset. For example, the value OK16385 is displayed as WARN1.

User-Defined JCWs

User-defined JCWs are created and initialized to a value by the SETJCW command or PUTJCW intrinsic. The JCW name contains alphanumeric characters and must begin with an alphabetic character. The name can be up to 255 characters long. The value assigned to the JCW must be in the range of 0 to 65,535, inclusive.

The SETJCW command scans the MPE/iX variable table for the name of the specified JCW (jcwname). If the specified name is found, the JCW is set to value. If the jcwname is not found, it is created and set to value. The term "value," as used here, means the explicitly stated or the computed value.

You may not begin a JCW name with the mnemonic names OK, WARN, FATAL, or SYSTEM, unless you append a number to the mnemonic such that the computed value exceeds 65,535 (for example, WARN999999, or SYSTEM200000). If the computed value exceeds 65,535, MPE/iX does not recognize the term as a valid mnemonic, and treats it as the name of a JCW. This restriction is intended to eliminate the possibility of an ambiguous JCW assignment. For example, it is unclear from the following two commands whether the JCW X is equal to 100 or to 0:


  SETJCW OK=100
  SETJCW X=OK

Naming a JCW with a mnemonic or predefined JCW value results in an error message, as in the following example:


  SETJCW OK200=1982
  JCWNAME CANNOT BE A VALID JCW VALUE (CIERR 1725)

Negative or out-of-range JCW values cause the following error message to be displayed:


  VALUE NOT IN RANGELEGAL RANGE IS 0 TO 65535 (CIERR 1712)

System-Defined JCWs

JCW and CIERROR are MPE/iX system-defined JCWs created for each job and session. The JCW named JCW is always initialized to zero at the beginning of the job or session and remains zero, unless fatal errors occur, or unless the user changes the value. There are two special values for the system-defined JCW:


  %140000 (System 0) Program aborted per user request.
  
  >%140000      Program terminated in an error state.

The CIERROR JCW tracks command interpreter (CI) errors.

CIERROR is set to zero at the beginning of the job or session. If a command interpreter error occurs, CIERROR is updated to reflect the current CI error message number.

Users are advised not to alter the values of the CIERROR and JCW job control words. User-defined JCWs should be used for information the user wishes to control.

The following example shows the use of the CIERROR JCW:


  LISTF
  ^
  UNKNOWN COMMAND NAME. (CIERR 975)
  SHOWJCW CIERROR
  CIERROR = 975
  RUN
  ^
  NO PROGRAM FILE SPECIFIED. (CIERR 600)
  SHOWJCW CIERROR
  CIERROR = 600
  :

System-Reserved JCWs

The system-reserved JCWs are HPMINUTE, HPHOUR, HPDAY, HPDATE, HPMONTH, and HPYEAR. They contain system-assigned minute, hour, day, date, month, and year information. If the user attempts to assign values, an error message is displayed. You can retrieve the values in these JCWs with the FINDJCW intrinsic. The values can also be tested if the JCW is used with an IF, WHILE, SETJCW, SETVAR, or CALC command. The names of the system-reserved JCWs are reserved.

The following describes system-reserved JCWs and possible values:

HPDAY: Day of the week. The possible integers are 1 through 7. Sunday is indicated by 1. Saturday is indicated by 7.
HPDATE: Day of the month. The possible integers are 1 through 31.
HPMONTH: Month of the year. The possible integers are 1 through 12. January is indicated by 1.
HPYEAR: Year of the century. The possible integers are 00 through 99.
HPHOUR: Hour of the day. The possible integers are 0 through 23.
HPMINUTE: Minute of the hour. The possible integers are 0 through 59.

Conditional Execution Using JCWs

JCWs are typically used to control the flow of batch jobs, based on events that take place within the job. You can use the MPE/iX IF/THEN (ELSE/ELSEIF), ENDIF, and WHILE/ENDWHILE statements to test JCW values.

The following example illustrates a conditional execution function. The sample job runs a program that edits, verifies, and counts valid transactions (CHEKPROG). If no fatal errors occur, the job runs the program SHIPPROG, which schedules shipments. The job then runs FINALRPT, which produces a final report. If fatal errors do occur, the CHEKPROG sets the value of the JCW CHEKPROGSTAT to FATAL, and SHIPPROG is not run. Instead, ERRORRPT is run, which produces an error report. A final report is also produced by FINALRPT.

You can use the SHOWVAR command to display the value of any specified variable or any group of variables, including JCW type variables. You can display the contents of a system-defined JCW with the SHOWJCW command only if you specify the jcwname.

In the following example the CONTINUE command prevents an abort in case of errors; the RUN CHEKPROG edits, verifies, and counts valid transactions; the IF command specifies that if no fatal errors occur, schedule shipments; the RUN command schedules the shipments; the ELSE command produces the error report and resets the JCW to 0; and the RUN command produces a final report:


  !SETJCW CHEKPROGSTAT=OK
  !CONTINUE
  !RUN CHEKPROG
  ! IF CHEKPROGSTAT<FATAL THEN
  !  RUN SHIPPROG
  ! ELSE
  !  SHOWJCW CHEKPROGSTAT
  !  RUN ERRORRPT
  !ENDIF
  !RUN FINALRPT

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Examples

To set the job control word CURR1 to 100, and use a comma (,) as the delimiter instead of an =, enter:


  SETJCW CURR1,100

To set CURR1 to the value of the mnemonic WARN, and use a slash (/) as the delimiter instead of an =, enter:


  SETJCW CURR1/WARN

To use an arithmetic operation to set one JCW value relative to another, enter:


  SETJCW NEWJCW=LASTJCW + 56

To schedule a full backup job on Saturdays and a partial backup job on the other days of the week, you could create a user command:


  SETJCW FRIDAY=6
  IF HPDAY = FRIDAY THEN
      SCHEDJOB FULLBKUP;IN=1
  ELSE
      SCHEDJOB PARTBKUP;IN=1
  ENDIF

Related Information

Commands: DELETEVAR, SETVAR, SHOWJCW, SHOWVAR
Manuals: Appendix A, "Predefined Variables in MPE/iX"

SETMSG

Enables or disables the receipt of user or operator messages at the standard list device.

Syntax


  SETMSG { OFF | ON }

Parameters

OFF: Sets job or session to quiet mode and blocks the receipt of TELL command messages from other users.
ON: Enables user or operator messages to be received and displayed at the standard list device.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Operation Notes

Allows a job or session to receive or block TELL messages from other users. WARN messages from the system operator override quiet mode and are received and displayed.

Examples

To block messages, enter:


  SETMSG OFF

To receive messages, enter:


  SETMSG ON

Related Information

Commands: SET, TELL
Manuals: None

SETVAR

Assigns values to MPE/iX variables. (Native Mode)

Syntax


  SETVAR varname { <space> | , | ; } expression

Parameters

varname: The variable that is to be set to a value.
expression: The expression that is evaluated and assigned to varname.

Operation Notes

This command assigns values to MPE/iX variables. Variable names may be any combination of letters and numbers plus the underbar character, up to a total of 255 characters. Variables must start with a letter or the underbar character.

The expression parameter may be an MPE/iX expression, a Boolean, integer, or string value, or the name of another variable. If expression consists of elements and operators MPE/iX accepts ('abc' + 'cd' or 2*5+1), SETVAR will evaluate it. The operators defined in Table 12-2 "Logical Operators - The SETVAR Command" may be used in expression.

Table 12-2 Logical Operators - The SETVAR Command

Logical operators:	AND, OR, XOR, NOT
Boolean functions and values:	BOUND, TRUE, FALSE, ALPHA, ALPHANUM, NUMERIC, ODD
Comparison operators:	=, <>, <, >, <=, >=
Bit manipulation operators:	LSL, LSR, CSR, CSL, BAND, BOR, BXOR, BNOT
Arithmetic operators:	MOD, ABS, * , / , + , -, ^ (exponentiation)
Functions returning strings:	CHR, DWNS, UPS, HEX, OCTAL, INPUT, LFT, RHT, RPT, LTRIM, RTRIM, STR
Functions returning integers:	ABS, LEN, MAX, MIN, ORD, POS, TYPEOF
Other functions:	FINFO, SETVAR

The allowed operands are any variable, integer constant (hexadecimal ($), octal (%), or decimal) quoted string constant, the Boolean constants TRUE and FALSE, or the JCW mnemonics (SYSTEM, FATAL, for example, as defined in the SETJCW command).

Note that all variables are global, so the CI variable name should not be the same as the JCW name that is being used or the operation of the code that uses that JCW will be affected.

Compound logical expressions can be formed using the AND, NOT, XOR, and OR logical operators, and nested within parentheses.

The Boolean value of the keyword TRUE or FALSE is overridden if there is a variable of the same name. For example, to store the string value 'ABC' in X, enter:


  SETVAR TRUE 'ABC'
  SETVAR X TRUE

The SETVAR command may be used to set the command interpreter's search path (HPPATH), the command interpreter's prompt (HPPROMPT), and all other variables. You use SHOWVAR to see all the variables that were created by the user. Issuing SHOWVAR @ causes the display of every predefined and user-defined variable.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break terminates an INPUT ( ) function.

Example

To change the command interpreter prompt to your username.accountname, enter:


  SETVAR HPPROMPT "!HPUSER.!HPACCOUNT:"  or
  
  SETVAR HPPROMPT HPUSER+"."+HPACCOUNT+":"

The result is the same regardless of which form of the command you use.

Related Information

Commands: DELETEVAR, INPUT, SETJCW, SHOWJCW, SHOWVAR
Manuals: Appendix A, "Predefined Variables in MPE/iX"
Appendix B, "Expression Evaluator Functions"

SHOWALLOCATE

Displays status information about the ALLOCATE command.

Syntax


  SHOWALLOCATE [ STATUS [,listfile]
    [ALLOCATE  [,[fileset] [,listfile]] ]
    [ALL [,[fileset] [,listfile]] ]

Parameters

STATUS

Request to display a summary of status information includes:

(1)Number of programs allocated;

(2)Size and percentage of utilization of the following system tables:

Code segment table, code segment extension block table, and loader segment table.

ALLOCATE

Request to display programs for ALLOCATE specified by fileset, and the number of users sharing each program.

ALL

Request to display all information provided by parameters: STATUS and ALLOCATE and the default.

fileset

Specifies the set of files to be searched for. Default is @.@.@. This parameter is of the form:


  filesdesignator[.groupdesignator[.acctdesignator]]

fileset can be entered in any of the following formats and may use wild card characters, in any order, as replacements.

file.group.account

SHOWALLOCATE file named in specified group and account.

file.group

SHOWALLOCATE specified file named in any group and any account.

file

SHOWALLOCATE specified file named in any group and any account.

@.group.account

SHOWALLOCATE all files in specified group and account.

@.@.account

SHOWALLOCATE all files in all groups in specified account.

@.@.@

SHOWALLOCATE all files in system and default.

@

SHOWALLOCATE all files in all groups in all accounts.

@.group

SHOWALLOCATE all files in specified group in any account.

file.@.account

SHOWALLOCATE specified file in any group of specified account.

NOTE: The characters @, #, and ? can be used as wild card characters in the fileset parameter. These wild card characters have the following meanings: @ specifies zero or more alphanumeric characters.
# specifies one numeric character.
? specifies one alphanumeric character.
The characters can be used as follows:

n@

All files starting with the character n.

@n

All files ending with the character n.

n@x

All files starting with the character n and ending with the character x.

n##..#

All files starting with the character n followed by up to seven digits (useful for listing all EDIT/3000 temporary files).

?n@

All files whose second character is n.

n?

All two-character files starting with the character n.

?n

All two-character files ending with the character n.

listfile

Name of an output file to which all output is written. When specified, a new ASCII file with variable length records closed in permanent domain, user-supplied carriage control (CCTL), OUT access mode, and EXC (exclusive access) option. This parameter may also be a back-referenced file. Default is $STDLIST.

Operation Notes

This command generates the status information of the specified system tables and lists files which are allocated.

Use

This command requires system manager (SM) capability to execute for other groups or accounts.

Examples

To display status information for all allocated files in the system.


  SHOWALLOCATE ALLOCATE
  
     ALLOCATED PROGRAMS         SHARE COUNT

     EDITOR.PUB.SYS . . . . . . . .    0
     FCOPY.PUB.SYS  . . . . . . . .    2
     LISTDIR5.PUB.SYS . . . . . . .    1
     
     NUMBER OF PROGRAMS FOUND = 3

To display status information for all allocated files starting with a character "S" in the account named SYS.


  SHOWALLOCATE ALLOCATE,S@.@.SYS
  
     ALLOCATED PROGRAMS         SHARE COUNT
     
     SPOOK5.PUB.SYS . . . . . . . .    1
     SLPATCH.PUB.SYS . . . . . . . .   0
     
     NUMBER OF PROGRAMS FOUND = 2

To display summary status information regarding allocation.


  SHOWALLOCATE STATUS
  
     ALLOCATION STATUS
     
       NUMBER OF PROGRAMS ALLOCATED = 3
       
       ALLOCATION RELATED TABLES      SIZE   %USED
       
       CODE SEGMENT TABLE              191    52
       CSTX BLOCK TABLE                144    13
       LOADER SEGMENT TABLE           32000    3

Related Information

Commands: ALLOCATE
Manuals: Performing System Operation Tasks

SHOWALLOW

Displays which operator commands have been allowed.

Syntax


  SHOWALLOW [{ @.@ | user.@ | @.acct | user.acct }]

Parameters

@

All users, if used in place of user, or all accounts, if substituted for acct.

Default is that the commands allowed for the logged-on user are displayed.

user

Defines a particular user.

acct

Defines a particular account.

user.account

Defines a particular user in a particular account.

Operation Notes

This command displays the operator commands that have been allowed to specific users if the user.acct form is entered. If the @.@ form is entered, the commands allowed to all users in all accounts are displayed. System manager (SM) capability is required to specify @.@. Account managers (AM capability) may specify all users in their own account. When SHOWALLOW is executed from the system console, @ may be substituted for user and/or acct. In addition, SHOWALLOW separately lists which operator commands have been globally allowed.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command. Account manager (AM) or system manager (SM) capability is required to execute this command for other groups or accounts.

Example

To list the operator commands allowed to the user USER.SYS, enter:


  SHOWALLOW USER.SYS
  #S86 USER.SYS
    USER HAS THE FOLLOWING COMMANDS ALLOWED:
    ABORTIO     ACCEPT     DOWN     GIVE
    
    THERE ARE NO GLOBAL ALLOWS DEFINED.

Related Information

Commands: ALLOW, DISALLOW
Manuals: Performing System Operation Tasks

SHOWCATALOG

Displays information about user-defined commands (UDCs). (Native Mode)

Syntax


  SHOWCATALOG [listfile] [;USER=username [.acctname]]

Parameters

listfile

An arbitrary file name that identifies the output from SHOWCATALOG that is sent to the line printer. Specifying listfile sends the listing to device class LP (line printer). You may use a file equation to direct the listing of the catalog to a disk or tape file. If you omit this parameter, the listing is sent to the $STDLIST device.

USER

Permits the user to list other users' cataloged files. Account manager capability (AM) is required to show cataloged files for users within your logon account. System manager capability (SM) is required to show users' cataloged files in other accounts.

username. acctname

Specifies the user and/or account name whose file names are to be displayed. The @ wildcard character may be used to specify all the members of a set:


  USER=username
  USER=username.acctname
  USER=@.acctname
  USER=@.@

Operation Notes

This command lists user-defined command files, their commands and the level at which they were cataloged (user, account, or `system). This may not be the executing UDC catalog directory, as with the USER option. The user may specify a listfile to send the listing to the line printer. You may use a file equation to direct the listing of the catalog to another disk or tape file. Default is that the listing is sent to the $STDLIST device.

If SETCATALOG is performed with the USER option after the user logs on, the user's executing UDC directory is not affected. Only the UDC catalog set is affected. The next time the user logs on, the UDC directory is built from this set. Thus the SHOWCATALOG command with the USER option shows the UDC catalog set. The SHOWCATALOG command alone shows the currently executing UDC directory commands.

Use

This command is available from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

To display the account-level UDC files of all users in the GRIMSBY account, enter:


  SHOWCATALOG ;USER=@.GRIMSBY

To display the system-level UDC files of all users in all accounts, enter:


  SHOWCATALOG ;USER=@.@

To display all UDC command files for the current user and send the listing to the line printer (LP), enter:


  SHOWCATALOG MYFILE

To display all UDC command files for the current user and send the listing to the disk file called MYFILE, enter:


  FILE MYFILE;DEV=DISK
  SHOWCATALOG *MYFILE

To send all system-level UDC files to the line printer under the name LISTALL, enter:


  SHOWCATALOG LISTALL,@.@

To display a list of the cataloged files for the user SCOTT in your account, enter:


  SHOWCATALOG,SCOTT

Related Information

Commands: SETCATALOG, HELP <udcname>
Manuals: System Startup, Configuration, and Shutdown Reference Manual

SHOWCLOCK

Displays information about the system date and time.

SYNTAX


  SHOWCLOCK

Parameters

None.

Operation Notes

Prints the current time, date, the time correction in effect, and the time zone. See the command SETCLOCK for information about time correction and time zone.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example


  :SHOWCLOCK
  
  SYSTEM TIME: FRI, JUL 24, 1987, 8:47:35 AM
  CURRENT TIME CORRECTION: -3428 seconds
  TIME ZONE: 7 HOURS 0 MINUTES WESTERN HEMISPHERE

Related Information

Commands: SHOWTIME, SETCLOCK
Manuals: None

SHOWDEV

Reports the status of input/output devices.

Syntax


  SHOWDEV [ ldev | classname ] [;ACD]

Parameters

ldev: Logical device number of device for which status information is to be displayed. This number is unique for each device. Default is that status information for all system devices on the system is displayed.
classname: Device class name of device(s) for which status information is to be displayed. This name may apply to several devices. Default is that status information for all devices on the system is displayed.
ACD: Keyword requesting display of ACD (access control definition) for the device.

Operation Notes

The SHOWDEV command displays the status information for all input and output devices on the system. The display spacing is important and has been changed after the 4.7 release. The display appears in the following format:


  SHOWDEV
  LDEV     AVAIL     OWNERSHIP     VOLID     DEN  ASSOCIATION
     1     DISC      N/A
     2     DISC      N/A
     3     DISC      N/A
     4     DISC      N/A
     5     AVAIL
     6     SPOOLED   SPOOLER OUT
     7     AVAIL
     8     AVAIL
     9     AVAIL
    10   A AVAIL
    11     DISC      N/A
    12     DISC      N/A
    13     DISC      N/A
    14     DISC      N/A
    15     DISC      N/A
    16     DISC      N/A
    17     AVAIL
    18     AVAIL
    19     SPOOLED
    20   A UNAVAIL   #S914: 8 FILES
    21   A AVAIL

COLUMN

MEANING

LDEV

Includes the logical device number and may include one of the following:

J: Accepts jobs.
D: Accepts data.
A: Accepts jobs and data.

AVAIL

Lists the availability of devices and disks as follows:

AVAIL: The device is available as a real, nonshareable device.
AVAIL W: The device is a tape with write enable on the media.
SPOOLED: The device is available for input or output spooling.
UNAVAIL: The device is not available; it is under the control of a job, session, or a system process, such as a spooler.
DISC: The device is a disk and is always available.
DISC (RPS): The device is a CS-80 disk on which rotational position sensing (RPS) has been enabled.

OWNERSHIP

Includes device ownership and may include one of the following:

SYS: Controlled by the system. If #nnn appears, it specifies the process identification number (PIN) of the controlling process (program).
SPOOLER IN: Input spooling in effect, controlled by spooler.
SPOOLER OUT: Output spooling in effect, controlled by spooler.
#Jnnn: Controlled by the indicated job.
#Snnn: Controlled by the indicated session.
nn FILES: Indicates number of files currently in use on a disk.
DOWN: Device is offline, requested by system operator with the DOWN command.
DP: Device is being taken offline (DOWN command operation pending).

VOLID

The volume identification and may include one of the following:

IBM: The named magnetic tape volume that has a label written in the IBM format.
ANSI: The named magnetic tape volume that has a label.
NOLABEL: The named magnetic tape volume that has no label. Default.

DEN

Density of the tape, which may include one of the following:

6250: Density of 6250 BPI (bytes-per-inch).
1600: Density of 1600 BPI, or the density of the tape is unrecognizable.

ASSOCIATION

Indicates the logical devices by device class that have been established by the user with the ASSOCIATE command.

ACD

Access Control Definition. May include any of the following information per username.acctname:

R: READ access.
W: WRITE access.
L: LOCK access.
A: APPEND access.
X: EXECUTE access.
NONE: NO access.
RACD: Copy or read the ACD.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

To display the status of the device identified by logical device number 5 enter:


  SHOWDEV 5
  LDEV     AVAIL   OWNERSHIP   VOLID  DEN  ASSOCIATION
     5     SPOOLED SPOOLER OUT

To display the status of all devices of the device class CARD, enter:


  SHOWDEV CARD
  LDEV     AVAIL   OWNERSHIP  VOLID  DEN  ASSOCIATION
     6   A AVAIL

Related Information

Commands: DISCRPS, ABORTIO
Manuals: Performing System Operation Tasks

SHOWIN

Reports the status of input device files.

Syntax


  SHOWIN [ #Innn STATUS ] [;SP] [;item [;...]]

Parameters

#Innn

Identifies the particular input device file for which information is to be displayed. Default is that MPE/iX displays information for all input device files used by the logon job or session.

STATUS

Summarizes the status information for all current input device files. Default is that MPE/iX displays information for all input device files used by the logon job or session. The information appears in following format:


  8 FILES DISPLAYED
      0 ACTIVE
      0 READY;INCLUDING 0 SPOOFLES, 0 DEFERRED
      8 OPENED; INCLUDING 0 SPOOFLES
      0 LOCKED; INCLUDING 0 SPOOFLES
      0 SPOOFLES; 0 SECTORS

SP

Displays status information for the currently spooled input device files associated with the logon job or session. Default is a display of status information for all input device files.

item

Displays the status of current input device files as identified. Default is that MPE/iX displays status information for all input device files used by this job.

Syntax for Item


  [DEV=ldev] [JOB={ @J | @S | @ | [#] { Jnnn | Snnn }} ]
  [{ ACTIVE | OPENED | READY }]

Parameters for Item

ldev

Displays the status of input device files identified by logical device number ldev.

JOB=

Displays the status of input device files. JOB= may be one of the following options:

@J: Displays the status of input device files for all jobs.
@S: Displays the status of input device files for all sessions.
@: Displays the status of device files for all jobs and sessions. (Default.)
[#]Jnnn: Displays the status of all input device files for a specified job.
[#]Snnn: Displays the status of all input device files for a specified session.

ACTIVE, OPENED, or READY

Displays the status of all input files in a specified state. ACTIVE displays the status of active device files. OPENED displays the status of opened device files. READY displays the status of ready device files.

Operation Notes

This command displays the status information about one or more currently defined input device files. This information reflects the status at the time the command is entered, and always appears on the standard list device. Except for the keyword STATUS, which has its own format (refer to "Parameters"), the format of the information is as follows:


  DEV/CL DFID  JOBNUM FNAME  STATE   FRM SPACE RANK PRI #C
  10     #I10  #J133  $STDIN OPENED

The information displayed in this format is defined as follows:

COLUMN

MEANING

DEV/CL

Logical device number of device.

DFID

Device file identification in the form #Innn. The number displayed in the DFID is identical to the LDEV number.

JOBNUM

Job or session number (jsnum) of the job or session using the device file, if not used for READY or ACTIVE data. Otherwise, the job/session name appears on the line following standard device information.

FNAME

File name associated with the device file.

STATE

One of the following:

ACTIVE: Input being read from a spooled device to a disk.
READY: Input spooling completed; file is now ready for use by a program.
OPENED: A file is being accessed by a program.

FRM

Forms message indicator. The letter F appears only if a forms alignment message applies to the device file. Does not apply to input files.

SPACE

Approximate disk space currently used (in sectors), for jobs only.

RANK

The order in which the file is entered into the system with respect to other files of the same priority and class name or logical device.

The letter D following RANK indicates a deferred file for spooled device files only. A file can be deferred if its priority is less than or equal to the system outfence or the outfence of a specific device.

PRI

The outpriority of the device file, requested by the user or adjusted by the system operator. Specified for spooled output device files only.

#C

The number of copies needed, specified for spooled output device files only.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

The following is an example of how to determine the status of an individual input device file:


  SHOWIN #I80
  DEV/CL DFID JOBNUM FNAME   STATE   FRM SPACE RANK PRI #C
  43     #I43 #S37  $STDIN   OPENED              8

If you do not know the device file identification number (DFID) of the device file whose status you want to determine, you may request the status display by entering either the logical device number or the device class name of the device on which the file originated:


  SHOWIN DEV=43
  DEV/CL DFID JOBNUM FNAME  STATE  FRM SPACE RANK PRI #C
  43     #I43 #S37  $STDIN  OPENED

You may also request displays of device file information using various combinations of qualifications (devices, jobs/sessions, and states). For example, to display information about all OPENED input device files used by all sessions (but not jobs) in the system, enter:


  SHOWIN JOB=@S;OPENED
 
  DEV/CL DFID JOBNUM FNAME   STATE FRM SPACE RANK PRI #C
  7      #I7  #S38   MASTER  OPENED
  26     #I26 #S18   $STDIN  OPENED
  32     #I32 #S41   $STDIN  OPENED
  34     #I34 #S26   $STDIN  OPENED
  42     #I42 #S28   $STDIN  OPENED
  43     #I43 #S37   $STDIN  OPENED
  50     #I50 #S40   $STDIN  OPENED
  51     #I51 #S17   $STDIN  OPENED
  
  8 FILES (DISPLAYED):
      0 SPOOFLES: 0 SECTORS

Related Information

Commands: SHOWOUT, LISTSPF
Manuals: Performing System Operation Tasks(32650-90137)

SHOWJCW

Displays the current state of one or more job control word (JCW) variables.

Syntax


  SHOWJCW [jcwname]

Parameters

jcwname: The name of a valid job control word (JCW) variable. Default is that all user-defined and system-defined JCWs are displayed.

Operation Notes

The SHOWJCW command is used to display the current state of one or more job control words (JCWs). Job control words in MPE/iX are classed as variables of type JCW. Specifying a particular JCW (user-defined, system-defined, or system-reserved) displays the value of that particular JCW. If you do not specify a particular JCW, user-defined and system-defined JCWs are displayed. The value of the third type of JCW, system-reserved JCW, is displayed only if you specifically enter its jcwname. The SHOWVAR command can be used to show variable values as well.

You may retrieve the value assigned a JCW with the FINDJCW and HPCIGETVAR intrinsics.

You may test the value of a JCW with an IF or WHILE command. In this way, the value of a given JCW can be used to conditionally execute another instruction or set of instructions. For example:


  !CONTINUE
  !SPL MYPROG,MYUSL
  !IF JCW>=FATAL THEN
  !  TELL USER.TECHPUBS;COMPILE FAILED
  !ELSE
  !  TELL USER.TECHPUBS;COMPILE COMPLETED
  !ENDIF

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

To show the current state of all user-defined and system-defined JCWs, enter:


  SHOWJCW
  JCW = 0
  CIERROR = 0

To display the current state of a valid user-defined job control word named JCW1, enter:


  SHOWJCW JCW1
  JCW1=3

To display the contents of a system-reserved JCW, enter:


  SHOWJCW HPDAY
  HPDAY=4

Related Information

Commands: DELETEVAR, SETJCW, SETVAR, SHOWVAR
Manuals: Appendix A, "Predefined Variables in MPE/iX"

SHOWJOB

Displays status information about jobs/sessions.

Syntax


  SHOWJOB [ [#]Snnn | [#]Jnnn | STATUS | SCHED ] [item [;...]]
    [;*listfile] [;JOBQ]

Parameters

#Snnn: The session number (assigned by MPE/iX) of the session for which the status information is to be displayed. The information appears in Type I format, described under "Operation Notes." Default is that the status information for all jobs/sessions is displayed.
#Jnnn: The job number (assigned by MPE/iX) of the job for which status information is to be displayed. The information is in Type I format, described under "Operation Notes." Default is that the status information for all jobs/sessions is displayed.
STATUS: Lists the number of jobs and sessions in each processing state and the current jobfence and job/session limits. This information is in Type II format, described under "Operation Notes." Default is that the status information for all job/sessions is displayed.
SCHED: Displays only the scheduled jobs. The information is in Type III format, described under "Operation Notes."
item: A list of jobs/sessions whose status is displayed. Default is that the status information for all jobs/sessions is displayed. The syntax appears below.
*listfile: Formal file designator of the file on which the output listing is written. A backreference to a FILE equation is required. The listfile is a temporary file with record size of 256 bytes, blocked one record per block, with carriage-control (CCTL), with the time and date displayed. You can override the default characteristics of listfile with the FILE command. Default is $STDLIST.
JOBQ: Which will indicate the queue name to which the job belongs. A new field JOBQ is added into the showjob output format.

Syntax for Item


  [JOB={ @J | @S | @ [{ @ | jsname} ,] username.acctname }]
  [;{INTRO | EXEC | SUSP | WAIT [, { N | D }] }]

Parameters for Item

JOB=

A list of jobs/sessions for which status information is to be displayed. Use one of the following options:

@J: Displays status information for all jobs.
@S: Displays status information for all sessions.
@: Displays status information for all jobs and sessions. Default.
[jsname,] username.acctname: The jsname is an optional name given to the session or job by the user. The username parameter is the user name established by the account manager. This name may consist of one to eight alphanumeric characters beginning with an alphabetic character. The acctname parameter is the name of the account established by the system manager. This name may consist of one to eight alphanumeric characters beginning with an alphabetic character. The @ can be used to replace the jsname or username in a specified account.

INTRO, EXEC, SUSP or WAIT

Displays the status of all jobs or sessions in a specified state. INTRO means that the job is introduced. In this case, the spooler process validates the JOB command and, if the job is legitimate, copies the job input records to disk. EXEC means that the job is executing. SUSP means that the job or session is suspended, because table entries or system resources are unavailable. WAIT means that there are no available list devices for the job. WAIT has the following subparameters:

N: Displays the status of nondeferred READY device files.
D: Displays the status of deferred READY device files.

If information for only one device file is displayed, output is in Type I format; if information for more than one device file is displayed, output is in Type I followed by Type II format. (Format types are described under "Operation Notes.")

Operation Notes

This command enables you to determine the number of jobs and sessions in each processing state, the current jobfence and job/session limits, and allows you to keep track of individual spooled and streamed jobs that are entered in the system. The command jobq will indicate the queue name to which the job belongs.The output appears in the following formats:

Type I:


  JOBNUM STATE IPRI JIN  JLIST  INTRODUCED JOB NAME
 
  #S16   EXEC        45  45     MON  7:08A TEST.PUBS
 
  JOBFENCE= 0; JLIMIT = 3; SLIMIT= 16

Type II:


  7 JOBS:
      0 INTRO
      0 WAIT; INCL 0 DEFERRED
      7 EXEC; INCL 7 SESSIONS
      0 SUSP
  JOBFENCE= 0; JLIMIT= 3; SLIMIT= 16

If the SHOWJOB SCHED command is used, the output is displayed as shown below. The STATE field shows that the job is scheduled. The SCHEDULED-INTRO field shows the time and date the job will be introduced to the system. Note that the scheduled jobs are listed in the order in which they will be introduced to the system. If you enter only the SHOWJOB command, the formatted output for jobs and sessions in the INTRO, WAIT, and EXEC states is displayed first in the Type I and Type II formats. The formatted data for jobs in the SCHED state is displayed last and is in the Type III format.

Type III:


  CURRENT: 5/13/85 1600
 
  JOBNUM STATE IPRI JIN  JLIST SCHEDULED-INTRO JOB NAME
 
  #J38   SCHED    3  10  6     5/16/84 11:24   NOTHING,JON.OSE
  #J23   SCHED    8  10  PP    5/25/84  8:01   REPORT,MGR.OSE
  #J25   SCHED    8  10  LP    7/ 4/84 18:05   FIREWORK,MR.SAM
 
  3 JOBS (DISPLAYED)
  JOBFENCE=7; JLIMIT=2; SLIMIT=20

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

To determine the number of jobs and sessions in each processing state, the current jobfence and the job/session limits, enter:


  SHOWJOB STATUS
  6 JOBS:
      0 INTRO
      0 WAIT; INCL 0 DEFERRED
      6 EXEC; INCL 6 SESSIONS
      0 SUSP
  JOBFENCE= 0; JLIMIT= 3; SLIMIT= 16

To get a report on all jobs and sessions in the system, enter:


  :SHOWJOB
 
  JOBNUM  STATE IPRI JIN JLIST  INTRODUCED JOB NAME
  #S745   EXEC        29 29     MON  2:53P DL,SPL.ALANG
  #S746   EXEC        26 26     MON  2:53P CLI.AOPSYS
 
  2 JOBS:
      0 INTRO
      0 WAIT; INCL 0 DEFERRED
      2 EXEC; INCL 2 SESSIONS
      0 SUSP
  JOBFENCE= 2; JLIMIT= 1; SLIMIT= 16

  :SHOWJOB;jobq
  JOBNUM  STATE IPRI JIN JLIST JOBQ      INTRODUCED  JOB NAME
  #J3     EXEC       10S LP    HPSYSJQ   WED 11:46A  FTPMON,FTP.SYS
  #J7     EXEC       10S LP    SYSMGRQ   WED  5:47P  EMG,MGR.SYSMGR
  #S81    EXEC        34 34              THU 12:17P  MGR.GOPI

The following example of a SHOWJOB command sequence illustrates an override of the default characteristics of listfile with the FILE command, and shows the output produced with the new listfile characteristics:


  FILE A;REC=40,1,F,ASCII;NOCCTL
  SHOWJOB;*A
  SAVE A
  FCOPY FROM=A;TO=

  HP32212A.03.26 FILE COPIER (C) HEWLETT-PACKARD CO. 1984

  MON, MAY 7, 1987, 7:54 AM

  JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME
  #S46   EXEC        20 20   MON  7:14A  OPERATOR.SYS
  #S45   EXEC        47 47   MON  6:37A  USER.PUBS
  #S47   EXEC        28 28   MON  7:26A  SUPPORT.DOC
  #S48   EXEC       102 102  MON  7:28A  USER.TECH
  #J19   EXEC       10S LP   MON  6:41A  JON.OSE
  #S49   EXEC*       34 34   MON  7:31A  FLASH.G
  #J21   EXEC       10S LP   MON  7:15A  DELIVER,MAIL.MAIL
  #J22   EXEC       10S LP   MON  7:14A  RSPOOLJ,RSPOOL.SYS

  8 JOBS (DISPLAYED):
      0 INTRO
      0 WAIT; INCL 0 DEFERRED
      8 EXEC; INCL 5 SESSIONS
      0 SUSP
  JOBFENCE= 6;  JLIMIT= 4;  SLIMIT= 50
  EOF FOUND IN FROMFILE AFTER RECORD 17

  18 RECORDS PROCESSED *** 0 ERRORS

  END OF SUBSYSTEM
  :

The SHOWJOB command reports a job or session as being in EXEC* when it is initializing. After initialization is complete, the state changes to EXEC. The number shown in the EXEC state is the sum of the jobs and sessions in both EXEC and EXEC*.

Related Information

Commands: ABORTJOB, BREAKJOB
Manuals: Performing System Operation Tasks

SHOWLOG

Displays the number of the system's current log file and the percentage of disk space used. (Native Mode)

Syntax


  SHOWLOG

Parameters

None.

Operation Notes

The log file number, xxxx, and percentage of file space used, yy, is displayed in the format:


  SYSTEM LOG FILE #xxxx IS yy% FULL

If the logging system is disabled, MPE/iX displays the message:


  NO LOGGING

If logging is enabled but currently suspended due to an error, both messages are displayed.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. System supervisor (OP) capability is required to use this command.

Example

To display the current log file status, enter:


  SHOWLOG
 
  SYSTEM LOG FILE #7 IS 20% FULL

Related Information

Commands: ALTLOG, CHANGELOG, GETLOG, LISTLOG, LOG, OPENLOG, RELLOG, RESUMELOG, SHOWLOGSTATUS, SHOWNMLOG, SWITCHLOG, SWITCHNMLOG
Manuals: Performing System Operation Tasks
System Startup, Configuration, and Shutdown Reference Manual

SHOWLOGSTATUS

Displays status information about currently opened user logging files assigned to a logging identifier.

Syntax


  SHOWLOGSTATUS [logid]

Parameters

logid: Displays status of the user logging file associated with the logging identifier, logid, created by the GETLOG command. Default is that the status of all logging identifiers is displayed.

Operation Notes

This command lists the status of currently running logging processes. The status includes the total number of records written by the process and the number of users accessing the logging file. By default this command gives the following information about all currently running logging processes. To display the status of the logging identifier LEN, enter:


  SHOWLOGSTATUS LEN
 
  LOGID  CHANGE AUTO USERS STATE  CUR-REC  MAX-REC % USED CUR-F
 
  LEN    NO      NO   4  INACTIVE  100       1000  10%   1

The information provided in this format is defined as follows:

COLUMN: MEANING
LOGID: The name of the logging process.
CHANGE: Whether the CHANGELOG command is permitted (whether the name of the first logging file ends in 001).
AUTO: Whether an automatic CHANGELOG has been enabled (whether the AUTO parameter has been specified through the ALTLOG or GETLOG command).
USERS: The number of users accessing the logging file.
STATE: ACTIVE, INACTIVE, INITIALIZING, or RECOVERING. INACTIVE is displayed when a process is waiting for information from user processes that involve intrinsics. INITIALIZING starts the log process. RECOVERING is displayed immediately after a START RECOVERY is issued.
CUR-REC: The number of records in the log file.
MAX-REC: The maximum number of records permitted.
% USED: The percentage of the maximum used.
CUR-F: The current file number in the set.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

Refer to "Operation Notes."

Related Information

Commands: ALTLOG, CHANGELOG, GETLOG, LISTLOG, LOG, OPENLOG, RELLOG, RESUMELOG, SHOWLOG, SWITCHLOG
Manuals: Performing System Operation Tasks
System Startup, Configuration, and Shutdown Reference Manual

SHOWME

Reports the status of a job or session. (Native Mode)

Syntax


  SHOWME

Parameters

None.

Operation Notes

To display the status of the current job/session enter:


  SHOWME
  USER: #S485,MGR.DSUSER,PUB   (NOT IN BREAK)
  RELEASE: V.UU.FF  MPE XL HP31900 A.11.70  USER VERSION: V.UU.FF
  CURRENT: MON, MAY 7, 1987, 11:09 AM
  LOGON:   MON, MAY 7, 1987, 11:08 AM
  CPU SECONDS: 3        CONNECT MINUTES: 1
  $STDIN LDEV: 88       $STDLIST LDEV: 88

The system welcome message, if one exists, appears immediately following the SHOWME display. The information provided in the format above is defined as follows:

ITEM

MEANING

#S485

This is the session number. It may also be a job number.

(NOT IN BREAK)

An (IN PROGRAM), (IN BREAK), or (NOT IN BREAK) message to indicate whether SHOWME was executed programmatically, in BREAK, or directly from the MPE/iX command interpreter.

RELEASE: V.UU.FF

The RELEASE: V.UU.FF number is determined by Hewlett-Packard at build time of the operating system and provides an identity for software releases (also known as the MIT). This number cannot be changed. (Prior to MPE/iX release A.11.70, this was referred to as BASE.

USER VERSION

The USER VERSION: V.UU.FF can be given a value during a SYSGEN and allows you to identify any changes to your total software package such as patch level, third party software, or other specifics. Any ASCII character can be used. In prior releases, this number was printed out immediately after the MPE/iX product number HP31900.

HP31900 A.11.70

The PRODUCT V.UU.FF immediately follows the product number HP31900. It is determined by Hewlett-Packard when a new version of the MPE/iX operating system is compiled. This V.UU.FF number cannot be changed and is used when entering a service request (SR) against the MPE/iX operating system product for that particular release.

CURRENT

Shows the current time and date.

LOGON

Shows the logon time.

CPU SECONDS

Shows the central processor time (CPU) used by this job/session.

NOTE: SHOWME calculates CPU usage by adding the local CPU usage of the current process to the accumulated total of all terminated processes. The CPU usage listed for a programmatic SHOWME, therefore, would rarely agree with that for a SHOWME executed during BREAK.

CONNECT MINUTES

The amount of time the job/session has been connected.

$STDIN LDEV

The logical device number of the job or session's standard input device.

$STDLIST LDEV

The standard list device number.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Example

Refer to "Operation Notes."

Related Information

Commands: HELLO, JOB, SHOWJOB
Manuals: None

SHOWOUT

Displays the status of output device files.

Syntax


  SHOWOUT [{ #Onnn | STATUS | SP } [item [;...]] ]

Parameters

#Onnn

Identifies a particular output device file for which you want information. The information is displayed in Type I format, which is described in the "Operation Notes" section of this command. The default is to display status information for all output device files used by the logon job or session.

The number of the device file identifier is identical to the LDEV number of the device. For example, if the LDEV number is 20, the device file identifier appears in the DFID column as #20.

STATUS

Summarizes the status information for all current output device files. The information is displayed in Type II format, described in the "Operation Notes" section. The default is to display status information for all output device files used by the logon job or session.

SP

Displays the status information for currently spooled output device files associated with the logon job or session. The information is displayed in a combination of two formats, Type I format followed by Type II format, which is described in the "Operation Notes" section. The default is to display status information for all output device files used by the logon job or session.

item

Displays the status of all current output device files as identified. If information for only one device file is displayed, the output appears in Type I format. If information for more than one device file is displayed, the output appears in Type I format followed by Type II format. The syntax for item follows:

Syntax for Item


  [DEV={ ldev | classname }]
  [JOB={ @J | @S | @ | [{ @ | jsname },] username.acctname }]
  [;{ INTRO | EXEC | SUSP | WAIT [, { N | D }] }]

Parameters for Item

ldev or classname

Displays the status of output device files. The ldev parameter displays the files residing on the device identified by the logical device number. The classname parameter displays the status of the output device files residing on all devices in a class name.

JOB=

Displays the status of output device files using one of the following options:

@J: Displays the status of output device files for all jobs.
@S: Displays the status of output device files for all sessions.
@: Displays the output device files for all jobs and sessions.
[#]Jnnn: Displays all output device files for specified job.
[#]Snnn: Displays the status of all output device files for a specified session.

ACTIVE, OPENED, READY, or LOCKED

Displays status of all output files in the specified state. An ACTIVE file is one that is currently being produced on your printer or plotter. Only one output spoolfile can be ACTIVE at any one time. OPENED files are those being accessed by a program. A spoolfile will be OPENED when a spooler process is writing the file to disk; during that time, however, the file is not ready to be printed. READY files are completely spooled and ready to be output. A LOCKED file is READY but cannot be accessed until the system relinquishes its exclusive use of the file.

READY files may include one of the following:

N: Displays the status of nondeferred READY device files.
D: Displays the status of deferred READY device files.

Operation Notes

This command displays the status information for one or more currently defined output device files. The information reflects the status at the time the command is entered and always appears on the standard list device. Two types of spooling queues are maintained in MPE/iX, one output queue for each logical device configured on the system and one additional queue for all device classes. Within each queue, files are linked according to the following parameters and listed in descending order of importance by output priority, device class, and rank. If the priorities are equal, the spooler alternates between queues.

Information about all spoolfiles on the system is available only from the console. Information about spoolfiles created in a specific job or session is available during that job or session only.

To list information about an individual output device file, you may specify its device file identifier (DFID) in the SHOWOUT command:


  SHOWOUT #O26
 
  DEV/CL DFID  JOBNUM FNAME    STATE FRM SPACE RANK PRI #C
  EPOC   #O26  #J242  $STDLIST READY        36   D   1   1
 
  OUTFENCE = 6

The information provided in this format is defined as follows:

COLUMN

MEANING

DEV/CL

Logical device number or device class name of the device.

DFID

Device file identification, which begins with the letter O (not zero) followed by a number. The numeric portion of the DFID is identical to the LDEV number of the device.

JOBNUM

The job/session number (jsnum) of job or session using the device file.

FNAME

File name assigned to device file.

STATE

The status, indicated by one of the following subparameters:

ACTIVE: The spooled device file on disk is actually being written to a printer or plotter.
OPENED: The device file on disk is being accessed by a program. If the device file is spooled, a program is currently writing to the disk.
READY: The spooled device file on disk is ready for output.
LOCKED: READY, but the system has exclusive access to the file.

FRM

The forms message indicator (the letter F) appears only if a forms alignment message applies to this device file.

SPACE

The approximate disk space currently being used, expressed in sectors. This applies only to spooled output device files.

RANK

The ranking of the file and its order in the system with respect to other files of the same output priority and classname or ldev. A time stamp activated by the FCLOSE intrinsic determines the file's rank.

The letter D following RANK indicates a deferred file. This applies only to spooled device files. A file can be deferred if its priority is less than or equal to system outfence or to the outfence of a specific device.

PRI

The output priority requested by a user or as adjusted by the system operator for spooled device files only. A priority of 1 is lowest, and 13 is highest.

#C

Number of copies needed, for spooled device files only.

The output may appear in two possible formats or in a combination of the two formats:

Type I:


  DEV/CL DFID  JOBNUM FNAME    STATE FRM SPACE RANK PRI #C
  32     #O32  #S16   $STDLIST OPENED

  OUTFENCE = 6

Type II:


  19 FILES
     0 ACTIVE
     2 READY; INCLUDING 2 SPOOFLES, 2 DEFERRED
     17 OPENED; INCLUDING 1 SPOOFLE
     0 LOCKED; INCLUDING 0 SPOOFLES
     3 SPOOFLES: 1572 SECTORS
  OUTFENCE = 6
  OUTFENCE = 2 FOR LDEV 13

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

To display the total number of output device files currently existing, the number of those that are spooled, and their current status, enter:


  SHOWOUT STATUS
  11 FILES:
     1 ACTIVE
     1 READY; INCLUDING 1 SPOOFLES, 0 DEFERRED
     9 OPENED; INCLUDING 1 SPOOFLES
     0 LOCKED; INCLUDING 0 SPOOFLES
     3 SPOOFLES: 7212 SECTORS
  OUTFENCE= 2
  :

You can also request information about a specific output device file, device number or device class name of the device for which the file is destined in the SHOWOUT command:


  SHOWOUT DEV=43
 
  DEV/CL DFID  JOBNUM FNAME    STATE FRM SPACE RANK PRI #C
  43     #O43  #S37   $STDLIST OPENED
 
  OUTFENCE= 2
  :

Related Information

Commands: SHOWIN, LISTSPF
Manuals: Performing System Operation Tasks

SHOWPROC

Displays information about the specified process(es). (Native Mode)

Syntax


  SHOWPROC [ [ PIN= ] { pinspec | ( pinspec [, ...]) }]
    [; JOB= { jobspec | ( jobspec [, ...]) }]
    [; FORMAT={ SUMMARY | DETAIL }]
    [; { TREE | NOTREEE }]
    [; { USER | ANYUSER }]
    [; SYSTEM]
    [; { TRUNC | NOTRUNC }]

Parameters

pinspec

The process that you want to see.

The pinspec, expressed [#p ]pin, is a Process Identification Number (PIN). Specifying pinspec is optional and has no default; see jobspec.

An ordinary user may show processes matching their own user and account names (those which "belong to" the user) by specifying 0 as the pinspec. A user with SM or OP capabilities may show any process on the system. A user with SM capability (the system manager) may see system processes by specifying the SYSTEM option.

NOTREE is the default for all pinspec target processes, and can be overridden with the TREE option.

The USER and ANYUSER options do not apply to pinspec.

jobspec

The name of the job or session whose processes you want to display. A jobspec can be any of the following: jobnumber, username, @S, @J, or @. A jobspec is optional and defaults to the user's current job ID, for example, #!HPJOBTYPE!HPJOBNUM.

The jobnumber must be in the form #Jnnn or #Snnn. SM or OP capability is required to specify another user's job or session number. The username must be in the form user[.account]. SM or OP capability is required to specify another user's username. If there is more than one job or session under the same username, all are displayed.

You can use wildcards; they have the following meanings:

@S - all sessions
@J - all jobs
@ - all sessions and jobs

An ordinary user can only see their own processes, even when jobspec is wildcarded. For example, if the user name is JEFF.MFG and you enter the command as shown below, then only processes for jobs logged on as JEFF.MFG are displayed.


  :SHOWPROC job=@J

On the other hand, if the user STEVE.UI (who has OP or SM capability) enters the command shown below, then all processes for all jobs on the system are displayed.


  :SHOWPROC job=@J

If the user STEVE.UI only wants to see his own job processes, he must enter:


  :SHOWPROC job=@J; user

The USER option, and its counterpart option, ANYUSER, are described below.

The SYSTEM option is ignored for all jobspec target processes.

TREE is the default for all jobspec target processes, and can be overridden with the NOTREE option.

SUMMARY

This format displays a subset of a process' attributes. These include the subqueue name, process priority, CPU time, execution state, associated JOB or SESSION number, PIN (indented to show tree structure), program name, and INFO=string, if any (or command step if the process is CI.PUB.SYS). The INFO=string and command step information is only visible to the system manager and to processes that belong to the user. SUMMARY is the default format.

DETAIL

This format displays a more comprehensive set of the attributes associated with a process.

TREE

This option displays each process specified, as well as all of its descendents. TREE is the default for all jobspec target processes.

NOTREE

This option displays only the process specified. No information appears for the process's descendants. NOTREE is the default for all pinspec target processes.

SYSTEM

The SYSTEM option is required if the target process from pinspec is a system process. It displays system processes as well as descendant user processes. SM capability is required. SYSTEM is ignored for all jobspec processes.

USER

The USER option filters output when jobspec is wildcarded by displaying only processes matching the user's name. USER is the default for users without OP and SM capability.

ANYUSER

This option defeats the filtering of the wildcarded jobspec and displays all matching processes. SM or OP capability is necessary to specify ANYUSER, and users with these capabilities get ANYUSER by default. OP or SM users may reduce the SHOWPROC output to just their own processes by using the USER option.

TRUNC

The TRUNC option truncates output records that would exceed the record width of $STDLIST for the user. A $ replaces the last character of the line to signify truncation. TRUNC is the default option.

NOTRUNC

This option displays output records in their full form. As a result, output from the command may wrap around the display.

Operation Notes

The SHOWPROC command displays information about processes except lockwords, which are never displayed. By default, the processes shown are the root CI and its descendents (TREE option). Any user may issue this command. Users with OP or SM capability may see information for processes belonging to other users. SM users may also see system processes via the SYSTEM option.

Any user may issue the SHOWPROC command and see information about all processes that belong to them. A process "belongs" to a user if one or more of the following conditions exists:

the process is within the user's logon job/session
the process' user and account names match the user's user and account names and the system's JOBSECURITY is set to LOW
the user has OP or SM capability.

If rule 1 or 2 applies or the user has SM capability then all information (except lockwords) is visible. Otherwise, only the Command Interperter (CI) command and/or program names are shown. That is, the parameters of a CI command and the INFO= string passed to a program are not visible.

When SHOWPROC is executed in a job, regardless of capabilities and process ownership, only the CI command name and program are displayed.

If you specify both the ;PIN= and ;JOB= parameters, information for the list of pins will precede the information for the list of jobs. Duplicate specifications are not detected.

SHOWPROC may be issued from a Session, Job, Program, or in BREAK. Pressing Break aborts the execution of this command.

The fields displayed are described below. The field's width, in characters, is shown within parentheses. A "v" indicates that the field has a variable size width.

CPUTIME (8):

CPUTIME is consumed in hh:mm:ss or m:ss.mls. A pair of asterisks (**) appears in the hours field when hours overflows. The three-character "mls" sub-field holds milliseconds.

JOBNUM (6):

The job or session number for the process.

LOGON (v):

The job/session, user, and account name associated with this process.

PARENT (5):

Process Identification Number for the process' parent (decimal). This field is unique to the DETAIL format. The DETAIL format displays PARENT so that process relationships can be determined. A zero indicates that the process does not have a parent (for example, PROGEN).

PIN (5):

Process Identification Number for the process (decimal). The SUMMARY format indents the PIN column by two spaces for each child process so that you can clearly see a process' descendants. The DETAIL format precedes the pin with a percent sign (%) to indicate that the process is an artificial member of its workgroup, and does not indent the display.

PRI (5)

The priority at which the process is currently executing. A lower numeric value indicates a higher priority. It also indicates whether the process is linear, runs with fixed priority (L), or is decayable (D). This field is unique to the DETAIL format.

PROGRAM (v):

The file name of the program the process is executing.

QUEUE (v):

The scheduling queue attribute associated with this process. The QUEUE field is unique to the DETAIL format.

QPRI (5):

A combination of SUBQUEUE and PRIORITY which appears as Qnnn[*]. Q is a single character abbreviation of the process' scheduling queue attribute. The nnn is the process' priority, and * indicates that this process is a system process. The QPRI field is unique to the SUMMARY format.

STATE (5):

The execution state of the process, which can be one of the following:

BLKIO blocked for terminal write or control.
WAIT generic process block, usually waiting for a message.
BLKCB blocked for control block.
BLKMM blocked for memory manager.
READY ready to execute (or executing).

STEP (v):

The command that the displayed CI process is currently executing. This field is not shown for non-CI processes.

WORKGROUP (v):

The workgroup of which the process is a member. WORKGROUP appears as [%]name, where % indicates that the process is an artificial member of the workgroup, and name is the workgroup name. A process becomes an artificial member when it is explicitly placed into the workgroup via ALTPROC or AIFPROCPUT instead of naturally meeting the membership criteria of the workgroup.

On the next page is a sample output of the DETAIL format. In this example, pin 2 is a system mode process, running linearly at priority 142. Pin 99 is a user mode process running linearly at priority 160. Pin 121 is a user mode process that is an artificial member of the "Payroll_Online" workgroup


  :SHOWPROC pin=(2,99,121,188);format=detail;system
  
  PIN PARENT  PRI  CPUTIME  STATE  JOBNUM (PROGRAM) STEP
  --- ------  ---  -------  -----  ------ --------------
  2   1       142L 7:23.687 WAIT          (LOAD.PUB.SYS)
  
  LOGON     :
  PROGRAM   : LOAD.PUB.SYS
  QUEUE     : BS
  WORKGROUP : BS_Default
  
  ***********************
  
  PIN PARENT  PRI  CPUTIME  STATE  JOBNUM  (PROGRAM) STEP
  --- ------  ---  -------  -----  ------  --------------
  99  68      160L 0:05.020 BLKIO  S45     (QEDIT.PUB.SYS)
  
  LOGON     : NMTEST,SLC.MYTEST
  PROGRAM   : QEDIT.PUB.SYS
  QUEUE     : BS
  WORKGROUP : Program_Development
  
  ***********************
  
  PIN PARENT  PRI  CPUTIME  STATE  JOBNUM (PROGRAM) STEP
  --- ------  ---  -------  -----  ------ --------------
  121 97      158D 0:12.045 READY  J51    :tdp "text report"
  
  LOGON     : JREPORT,GREG.MYTEST
  PROGRAM   : TDP.PUB.SYS
  QUEUE     : DS
  WORKGROUP : %Payroll_Online
  
  ************************
  
  PIN PARENT  PRI  CPUTIME  STATE  JOBNUM (PROGRAM) STEP
  --- ------  ---  -------  -----  ------ --------------
  188 101     100D 0:04.200 WAIT   S56    (TDP.PUB.SYS) text test1
  
  LOGON     : CMTEST,DOUG.MYTEST
  PROGRAM   : TDP.PUB.SYS
  QUEUE     : BS
  WORKGROUP : BS_Default

Below is a sample output of the default SUMMARY format. The information in the (PROGRAM) STEP column is visible only when the user issuing the command has SM capability, or when the process specified on the command line (in this case, #P54) belongs to the user.


  :SHOWPROC #P54; tree; trunc
  
  QPRI CPUTIME  STATE JOBNUM PIN  (PROGRAM) STEP
  
  C152 0:12.999 WAIT  S12    54   :tdp "text myfile"
  C152 0:02.000 WAIT  S12    38   (TDP.PUB.SYS) text myfile
  C152 0:01.030 READY S12    67   (FCOPY.PUB.SYS)from=foo.pub.sys;to=
  
  :SHOWPROC #P54; tree; notrunc
  
  QPRI CPUTIME  STATE JOBNUM PIN  (PROGRAM) STEP
  
  C152 0:12.999 WAIT  S12    54   :tdp "text myfile"
  C152 0:02.000 WAIT  S12    38   (TDP.PUB.SYS) text myfile
  C152 0:01.030 READY S12    67   (FCOPY.PUB.SYS)from=foo.pub.sys;to=
    bar,new

Example

To display a summary of information for all non-system processes in the current job/session, enter:


  :SHOWPROC

To display a summary of information for PIN 42, enter:


  :SHOWPROC #p42

To display a summary of information for PIN 42 and all of its descendants, enter:


  :SHOWPROC #p42; tree

To display the detail information for PIN 42, enter:


  :SHOWPROC #p42; format= detail

To display a summary of information for all processes (requires SM capability), enter:


  :SHOWPROC 1 ;system ;tree

To display a summary of information for all non-system processes that are jobs (requires SM or OP capability), enter:


  :SHOWPROC job=@j; anyuser

To display a summary of information for PINs 150, 247, and 211, enter:


  :SHOWPROC (150,#p247,211)

To display a summary of information for all non-system processes logged on as MGR.PAYROLL (requires SM or OP capability), enter:


  :SHOWPROC job=mgr.payroll

To display a summary of information for all non-system processes belonging to Job 2 or logged on as ME.AP (requires SM or OP capability), enter:


  :SHOWPROC job=(#j2,me.ap)

To display the detail information for all non-system processes in the current job/session, enter:


  :SHOWPROC detail

To display the detail information for all non-system processes on the system (requires SM or OP capability), enter:


  :SHOWPROC job=@; format= detail

Related Information

Commands: TUNE, ALTPROC, SHOWQ, NEWWG, ALTWG, PURGEWG, SHOWWG
Manuals: MPE/iX Intrinsics Reference Manual

SHOWQ

Displays scheduling data for all processes and the scheduling characteristics of the CS, DS and ES scheduling subqueue(s). (Native Mode)

SYNTAX


  SHOWQ [; { ACTIVE | STATUS }]

Parameters

ACTIVE: Displays only the processes currently running or those about to run. This is the right-hand portion of the display. The STATUS lines are printed last.
STATUS: Reduces the output from SHOWQ to the final status lines of display (base and limit priorities, quantum bounds).

Operation Notes

The process scheduling and subqueue information appears in two major columns: DORMANT and RUNNING. RUNNING processes are those that currently require the CPU in order to continue, or that will require it in the immediate future. CPU time is automatically allocated to the highest priority process that is ready to run. DORMANT processes are those waiting on longer-term events.

On occasion, a process appears in more than one column, indicating that it was changing state when you executed SHOWQ.

As the default, SHOWQ lists dormant and running processes and the scheduling characteristics of the CS, DS, and ES subqueues. However, the ACTIVE and STATUS options permit you to filter the SHOWQ output which, on large systems, may display hundreds of live processes.

Use the ACTIVE option to display running processes and the scheduling characteristics of the CS, DS, and ES scheduling subqueues. Use the STATUS option to display just the scheduling characteristics of the CS, DS, and ES subqueues. (Note that the ACTIVE output appears when both options are specified, since status information is a subset of the active information.)

Below is an example of the two-column output produced by the SHOWQ command. The symbols that may appear in such a listing are explained in the remainder of the discussion.


  DORMANT         RUNNING
  Q PIN  JOBNUM   Q PIN  JOBNUM
  A  1            C M163 #S263
  B  2            C U215 #S256
  B  3
  A  4
  D U29  #J30
  C M37  #S234
  C M55  #S248

Each entry in the three columns displays the following information for a single process; the meaning is explained below.

{ A B C D E } [ M U ] pin [ #Jnnn #Snnn ]


  A    the queue attribute of the process is AS
  
  B    the queue attribute of the process is BS
  
  C    the queue attribute of the process is CS
  
  D    the queue attribute of the process is DS
  
  E    the queue attribute of the process is ES
  
  M    this is a job or session main process
  
  U    this is a user process
  
  pin   process identification number, a decimal
  
  J nnn  job number: a process executing in a batch job
  
  S nnn  session number: a process executing from a session

The process identification number (pin) may appear with or without an M or U label. Processes without an M or U label are system processes.

In addition, SHOWQ prints the scheduling characteristics currently in effect. In the example below, QUEUE is the scheduling subqueue and BASE, LIMIT, MIN QUANTUM, MAX QUANTUM, BOOST and TIMESLICE are scheduling values set by the TUNE command. MIN and MAX quantums are bounds for the quantums and ACTUAL quantum is the current quantum value.


                      ------QUANTUM-------
  QUEUE  BASE  LIMIT  MIN    MAX    ACTUAL  BOOST  TIMESLICE
  -----  ----  -----  ---    ---    ------  -----  ---------
  CQ     152    200   1      2000   200     DECAY  200
  DQ     202    238   2000   2000   2000    OSC    200
  EQ     240    253   2000   2000   2000    DECAY  200

You may issue the SHOWQ command from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command. SHOWQ requires System Supervisor (OP) capability.

NOTE: The MPE/iX Scheduler now supports the workgroup concept. However, backward compatibility is maintained through five default workgroups created by the system. The scheduling characteristics of the CS_Default, DS_Default, and ES_Default workgroups mimic those of the CS, DS, and ES scheduling subqueues. In fact, the information displayed for the CS, DS, and ES scheduling subqueues is the same information as that for the default workgroups.

Please refer to the NEWWG and SHOWWG commands for more detail.

Since SHOWQ displays limited information regarding workgroup processes, Workload Manager users should use the SHOWWG and SHOWPROC commands rather than SHOWQ. Non-Workload Manager users may choose to use these commands if they prefer the format for viewing the default workgroups.

Example

To display the active processes and the current scheduling subqueue characteristics, enter:


  :SHOWQ;ACTIVE
  
  DORMANT          RUNNING
  Q PIN  JOBNUM   Q PIN  JOBNUM
  
                  C M163 #S263
                  C U215 #S256
  
                      ------QUANTUM-------
  QUEUE  BASE  LIMIT  MIN    MAX    ACTUAL  BOOST  TIMESLICE
  -----  ----  -----  ---    ---    ------  -----  ---------
  CQ     152    200   1      2000   200     DECAY  200
  DQ     202    238   2000   2000   2000    OSC    200
  EQ     240    253   2000   2000   2000    DECAY  200

Related Information

Commands: TUNE, ALTPROC, SHOWPROC, NEWWG, ALTWG, PURGEWG, SHOWWG
Manuals: MPE/iX Intrinsics Reference Manual
Performing System Management Tasks

SHOWTIME

Prints current time and date. (Native Mode)

Syntax


  SHOWTIME

Parameters

None.

Operation Notes

Prints current time and date, as indicated by system clock.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

To display the time and date, enter:


  SHOWTIME
  MON, JUL 24, 1987, 8:47 AM

Related Information

Commands: SETCLOCK, SHOWCLOCK
Manuals: None

SHOWVAR

Displays specific variable names and their current values. (Native Mode)

Syntax


  SHOWVAR [ varid] [, ...]]
          [job= jobID]
          [; { USER | HP | ANY }]

Parameters

varid: The name of the variable for which the current value is to be displayed.
jobid: The job or session number who's variables are to be displayed. Example: #J123 or S4321. SM capability is required to see the variables from another job or session. Only user-defined variables are visible when "jobID" is specified. It is recommended to always specify the USER option when using JOB=. This adds clarity to scripts and job streams, and preserves their functionality should JOB= be enhanced to display predefined variables.
USER: Selects only the user-defined variables matching each varid. USER is the default when varid is omitted. It is recommended to use USER in conjunction with JOB=, see the note above.
HP: Selects only the predefined HP variables matching each varid.
ANY: Allows all variables matching varid to be seen. ANY is the default when one or more varids are supplied, as long as jobid is not specified>

Operation Notes

This command displays to $STDLIST the variables specified and their values. It displays information in the format:

VARIABLE NAME = value.

Users with SM capability may display user-defined variables for another job or session by using the JOB= parameter. If jobid matches the job ID of the user execuiting the command no restrictions are placed. Plaese specify the USER option in scripts and jobs that use JOB=. This documents the intent, and allows these scripts and jobs to function the same if JOB= is later enhanced to show predefined and use user-defined variables.

Anyone can specify the USER, HP and ANY options. However, an error is reported if HP is used in conjunction with a jobid.

Table 12-3 Specified Variable-ID/Result

Variable-ID	Displays
(omitted)	All variables and values that the user has set.
`@`	All variables.
`A,B,C`	Values for variables `A`, `B`, and `C`.
`B@`	All variables whose names begin with `B`.

You may use the wildcard characters @, #, ?, and [ ] to specify a set or range of variables or file names in many commands.

@: Specifies zero or more alphanumeric characters, or the underbar character (_). Used by itself, it specifies all possible combinations of such characters. Used with other characters it indicates all the possible names that include the specified characters (@ABC@ = all names that include ABC anywhere in the name).
#: Specifies one numeric character. A###@ = all names that begin with A followed by any three digits, followed by any combination of zero to three alphanumeric (or underbar) characters.
?: Specifies one alphanumeric character. A?# = all three-character names that begin with A, followed by an alphanumeric character, followed by a digit.
[ ]: Specifies a set or range of characters. The set may appear anywhere in the name. This range specification is not case sensitive and, therefore, [A-K] is the same as [a-k]. If you specify a null set such as [k-a], then MPE/iX gives you a warning that this specification is invalid.
@[abc]@# =: All names containing a, b, or c and ending in a single digit.
[a-k]@ =: All names that begin with any one of the letters a through k.
[n-a] =: Not valid in variables and would be flagged as an error.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.

Examples

To display two specific variables, enter:


  SHOWVAR firstvariable, secondvariable

To display all variables beginning with a single alphabetic character and ending with the characters axval, enter:


  SHOWVAR ?axval

To display all variables created by the user with the SETVAR, INPUT, or SETJCW command, or with the HPCIPUTVAR, PUTJCW, or SETJCW intrinsics, enter:


  SHOWVAR

To display all variables created currently in the variable table, those created by the user and all predefined variables, enter:


  SHOWVAR @

To display all user-defined variables for session 32. Must have SM capability, enter:

SHOWVAR ;job=#s32

To display all user-defined variables matching s@ for job 23. Must have SM capability, enter:

SHOWVAR s@ ;job=J23 ;user

To display all user-defined variables beginning with the letter "H". Note: the predefined HP variables, like HPPATH, are not shown, enter:

SHOWVAR h@ ;user

To display all predefined variables containing "TIME" in their names. User created variables, like MYTIME, would not be seen, enter:

SHOWVAR @time@ ;hp

Related Information

Commands: DELETEVAR, INPUT, ECHO, SETVAR, SHOWJCW
Manuals: Appendix A, "Predefined Variables in MPE/iX"
Using the HP 3000 Series 900: Advanced Skills

=SHUTDOWN

Initiates a shutdown of MPE/iX.

Syntax


  =SHUTDOWN [ system | terminal | dtc | tape | disc |
    network | other ]

Parameters

None.

Operation Notes

The =SHUTDOWN command performs an implicit =LOGOFF of all sessions, including the session logged at the system console. All system processes are stopped in an orderly fashion. This includes the completion of all pending system activity and any processing necessary to ensure that the integrity of all system tables and directories is maintained. Once these procedures are complete, SHUT is displayed on the console, the CPU halts, and console interrupt (CTRL-A) is ineffective.

Device configuration changes that were made after the preceding load (UP, DOWN, ACCEPT, REFUSE, and spooling commands) are not retained. Configuration changes made during a system startup from tape are recorded and retained until the next system startup from tape. Newly assigned or released global resource identification numbers (RINs) are permanently recorded.

All communication lines must be closed before issuing a =SHUTDOWN command or a manual halt of the system may be necessary. Note that data is lost if a transmission is in progress when the halt is performed. If any network service (NS) lines are left open when the =SHUTDOWN command is issued, lines to the remote system remain open and any remote sessions become hung. In this case, the remote system's operator may need to issue ABORTIO commands for the hung sessions and then abort the sessions themselves.

Spooled devices stop operation immediately upon receiving a =SHUTDOWN command. A START RECOVERY retains spoolfiles which are printed when the system is returned online.

You can use any of the options to indicate the reason that you are shutting down the system. These options were developed to identify any possible type of system hang that might occur. For example, if you shutdown to clear a DTC hang, you can use the =SHUTDOWN dtc option.

Use

This command may be issued only at the physical console.

Example

To shut the system down, first issue a warning to all users to allow them time to log off, and then execute =SHUTDOWN as shown below:


  WARN @;SYSTEM WILL SHUTDOWN IN FIVE MINUTES. PLS LOG OFF.
  
  CTRL-A
  =SHUTDOWN
  10:49/#S40/25/LOGOFF
  10:49/20/ALL JOBS LOGGED-OFF

To shut down the system in order to identify a DTC hang, use the dtc option. The console responds by listing shutdown messages similar to these:


  CTRL-A
  =SHUTDOWN dtc
  
  Shutdown of operating system begins. (Shut 1)
  Shutdown of user processes begins. (Shut 2)
  Shutdown of jobs & sessions begins. (Shut 3)
  Spoolers notified of a shutdown. (Shut 16)
  Shutdown of system processes begins. (Shut 4)
  Shutdown of system managers begins. (Shut 5)
  Shutdown of operating system complete. (Shut 6)

Related Information

Commands: =LOGOFF
Manuals: System Startup, Configuration, and Shutdown Reference Manual

SHUTQ

Closes the spool queue(s) for the specified logical device, device name, or all members of a device class. (Native Mode)

Syntax


  SHUTQ { ldev | devclass | devname | @ } [;SHOW]

Parameters

ldev

The logical device number of the device.

devclass

The device class name of the devices.

devname

The device name of the device. Note that it is not possible to have a device class name and a device name that are the same. If you enter an alphanumeric character string, the command searches the device class list first, and then the device name list.

SHOW

The SHOW parameter displays the current queue state (enabled or unenabled) of the devices specified with the SHUTQ command.

@

The @ parameter globally disables all currently open spooling queues without closing the spooling queues. Thus when the spooling queues are globally reenabled with the OPENQ @ command, all spooling queues that were opened before being globally disabled will again be open.

Refer to the Native Mode Spooler Reference Manual (32650-90166) for more discussion on enabling and disabling of spooling queues.

Use the @ option without any other parameter. The SHOW option entered with the @ option returns an error.

Operation Notes

The SHUTQ command closes the spool queue(s) for a logical device or all members of a device class configured in the system. The spooler process, however, does not need to be running for the device. If the spooler process is running, it is unaffected by shutting the queue.

This command also serves as an option to the STARTSPOOL and SPOOLER commands, which are documented in this chapter.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. It may be issued only from the console unless distributed to users with the ALLOW or ASSOCIATE command.

Examples

To shut the queue for all devices in class LP, enter:


  SHUTQ LP

To shut the spool queue and show the state of the queue and other information about the specified device, enter:


  SHUTQ 6;SHOW

Related Information

Commands: OPENQ, STARTSPOOL, SPOOLER
Manuals: Native Mode Spooler Reference Manual
Performing System Operation Tasks

Chapter 12 Command List X

Chapter 13 Command List XI