HP 3000 Manuals HP 3000 Manuals
Parameters within Syntax (cont.)
Positional parameters (cont.)
STREAM
The STREAM command submits a batch job for execution. The batch job runs
independently of your session, which enables you to continue working at
your terminal while the batch job is running.
You can also use this command in conjunction with the DATA command to
submit data to the system from a device file.
Syntax
[ {day-of-week }]
STREAM [filename][,char] [;AT = timespec][;DAY = {day-of-month }]
[ {days-until-month}]
[;DATE = datespec][;IN = [days[,[hours][,minutes]]]]
Parameters
filename Specifies the ASCII file containing the job
commands. The first character of the first record
is assumed to be the replacement character for the
expected colon (:) that identifies commands. You
must have read (R) and lock (L) or execute (X) file
access in order to specify this parameter.
char Identifies MPE/iX commands within the input file.
It is a character that substitutes for a colon (:).
When you enter the input file on a device
configured to accept jobs or sessions, this
character can be any ASCII non-alphanumeric
character except a colon. The default is an
exclamation point (!).
AT Specifies the absolute time of day. Execution
begins in the format HH:MM, where HH is the hour of
the day (0<=HH<=24) and MM are the minutes of the
hour (0<=MM<=60). If you do not specify DAY and
DATE, then:
timespec < NOW---> JOB LOGON TOMORROW
timespec > NOW---> JOB LOGON TODAY
timespec = NOW---> JOB LOGON IMMEDIATELY
WITH EXPLANATORY MESSAGE
DAY Specifies the absolute day in one of the following
forms:
day-of-week Indicates the day of the
week. Permissible values are
SUN[DAY]
MON[DAY]
TUE[SDAY]
WED[NESDAY]
THU[RSDAY]
FRI[DAY]
SAT[URDAY]
day-of-month Indicates the calendar day of
the month expressed using the
integers 1 through 31. If
day-of-month is greater than
or equal to the current
day-of-month, the current
month is the default. If
day-of-month is less than the
current day-of-month, the
day-of-month is deferred
until the same day of the
next month. An error message
is generated if the
day-of-month does not
correspond to the month (for
example, if you enter 31 for
February). If you omit
day-of-month, the current
date is used.
days-until- month Indicates days until the end
of the month expressed using
the negative integers -31
through -1. The chosen
number specifies the calendar
day from the end of the
specified month when the job
will run. For example, a -1
value represents the last day
of the month. If the
specified day from the end of
the month indicates a day
earlier than the current day,
the next month is assumed.
For example, if today is the
seventh day from the end of
the month and you enter a -8
value, the job is scheduled
for the eighth day from the
end of the next month.
DATE Specifies the absolute date in the format mm/dd/yy,
where mm is the month (1<=mm<=12), dd is the day
(1<=dd<=31), and yy is the year. If you omit this
parameter, the current date is used.
IN Specifies the relative date or time in one of the
following forms:
days Indicates the number of days
from the current date
expressed as a positive
integer.
hours Indicates the number of hours
from the current time
expressed as a positive
integer (0<hours<=23). If
you omit this parameter, zero
is used.
minutes Indicates the number of
minutes from the current time
expressed as a positive
integer (0<=minutes<=59). If
you omit this parameter, zero
is used.
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode. Pressing Break during an interactively streamed job
aborts execution of the job.
* Requirements
You must have read (R) and lock (L) or execute (X) file access in
order to stream jobs. The system administrator should assign
general users only X access, because R and L access would allow
general users to obtain security information within the file, such
as passwords and lockwords.
You can initiate stream jobs only if the system administrator has
enabled the stream facility by entering the STREAMS console
command.
* Creating a job stream
To create a job file for streaming, do the following:
1. Enter the following command to invoke the EDIT subsystem:
:EDITOR
2. Enter the ADD command, then add job file commands, as
shown:
/ADD
1 !JOB SMITH,USER.TECH
2 !COMMENT THIS JOB RUNS THE MONTHLY UPDATE PROGRAM
3 !FILE INPUT01=TRANS.DATA.ENGR
4 !FILE MASTER;DEV=TAPE
5 !FILE OUTPUT=NEWFILE.PUB.TECH
6 !RUN UPDPROG
7 !EOJ
8 //
Note that the first command is the JOB command and that an
exclamation point (!) precedes each command.
3. Enter the KEEP and END commands to save your file and
terminate the EDITOR subsystem:
/KEEP MYJOB,UNN
/END
* Scheduling streamed jobs
When you schedule a job for future execution, it enters the SCHED
state. When the specified time arrives, the job enters and
remains in the WAIT state until the system allows the job to
execute. You can specify the time a job is to enter the WAIT
state in absolute or relative time. The differences are as
follows:
Absolute You specify an exact time for the job using
the AT parameter with or without the DAY or
DATE parameter.
Relative You specify a time offset from the current
time using the IN parameter.
If the time that you specify is the same as the current time, your
streamed job logs on immediately. If the time that you specify is
earlier than the current time and you do not specify DAY and DATE,
a warning message is generated, and the job is scheduled for the
specified time tomorrow; otherwise, you can specify any time in
the current century. Because of the limited recoverability of
scheduled jobs, it is recommended that you schedule jobs no more
than a few days in advance.
If you specify DAY or DATE for a job, but do not specify a time,
the job does not enter the WAIT state at midnight on the specified
day. Instead, the job uses the time when the STREAM command
executes and enters the WAIT state at that time on the specified
day.
If the system does not detect any errors, a job ID appears on your
screen. If you include more than one job in the input file, the
system assigns each job a unique job ID and schedules all of the
jobs at the same time.
* Redirecting the listing device
If you want the job listing to appear on a device other than the
standard listing device associated with the streaming device, you
can specify this other device using the JOB command as shown:
!JOB USER.TECHPUBS;OUTCLASS=12
* Terminating interactively streamed jobs
To terminate interactive job input, enter a colon (:). The system
responds by displaying the command interpreter prompt:
>: ** Denotes end of batch job input **
: ** MPE/iX prompts for next command **
Pressing Break aborts the execution of this command and any job
currently being entered through the command. Incompletely spooled
disk space returns to the system.
* Terminating scheduled streamed jobs
You can use the ABORTJOB command to terminate jobs that you have
scheduled for STREAM execution. Refer to the ABORTJOB command for
information on its usage.
* Rescheduling system-terminated streamed jobs
If the system fails or is intentionally stopped, your stream jobs
may be saved or deleted, depending on the method used to restart
the system. If you have scheduled a job for execution earlier
than the system restart, the job enters the WAIT state and
executes when the system parameters allow it to execute.
After the system is restarted, you should first enter the SHOWJOB
command to display the scheduled jobs. Reschedule your stream
jobs that do not appear as scheduled jobs.
Examples
The following examples assume that the current date and time are Monday,
June 10, 1991 at 12:00 pm. The examples also assume that the input file,
named JOBFILE, contains a valid STREAM job.
* To introduce JOBFILE immediately, enter:
:STREAM JOBFILE
* To introduce JOBFILE at 8:00 am, Tuesday, June 11, enter:
:STREAM JOBFILE; AT=8:00
* To introduce JOBFILE at 8:00 pm, Monday, June 10, enter:
:STREAM JOBFILE; AT=20:00
* To introduce JOBFILE in eight hours, at 8:00 pm, Monday, June 10,
enter:
:STREAM JOBFILE; IN=,8
* To introduce JOBFILE in one day plus eight hours, at 8:00 pm,
Tuesday, June 11, enter:
:STREAM JOBFILE; IN=1,8
Sometimes you may enter a stream job intending it to be introduced at a
certain time, but the system interprets your entry differently than your
intentions, as illustrated in the following examples:
STREAM JOBFILE; DAY=MON; Since the time specified (8:00 am) is earlier
AT=8:00 than the current time, JOBFILE will be
introduced at 8:00 am, Monday, June 17.
STREAM JOBFILE; DAY=5 Since the day of the month (5) is earlier than
the current day (8), the next month is assumed.
Since no time was specified, JOBFILE will be
introduced on Saturday, July 6, at 12:00 pm.
STREAM JOBFILE; DAY=31 Since June 31 does not exist, the next month is
assumed. Since July 31 does exist, this is a
legal command. JOBFILE will be introduced on
Wednesday, July 31, at 12:00 pm. If July 31
did not exist, this command would cause an
error.
STREAM JOBFILE; DAY=-2 The -2 means the second to last day of the
month, and since no time was specified, the
current time is used. JOBFILE will be
introduced on Sunday, June 30, at 12:00 pm.
STREAM JOBFILE; DAY=-25 The -25 means the twenty-fifth day from the end
of the month. If one assumes the current
month, that implies June 6, but June 6 is
earlier than the current day; therefore, the
next month is assumed. JOBFILE will be
introduced on Sunday, July 7, at 12:00 pm.
STREAM JOBFILE; Since the specified time is earlier than the
DATE=6/8/87; AT=8:00 current time, this command is not permissible,
and it causes an error.
STREAM JOBFILE; The specified time is later than the current
DATE=6/8/87; AT=20:00 time, so this command is permissible. JOBFILE
will be introduced on Monday, June 10, at 8:00
pm.
Related Commands
ABORTJOB
JOB
LISTSPF
SHOWJOB
STREAMS
STREAMS
The STREAMS command enables or disables the streams device, which permits
or prohibits you from streaming jobs. The system administrator enters
this command and STARTSPOOL LP after starting up the system to enable the
STREAM command.
Syntax
STREAMS {ldev}
{OFF }
Parameters
ldev Specifies the logical device number of the streams
device. The streams device must have an output
device number or class that references logical
devices of type 32. You can use any input device
except the console or terminals. The input device
must be configured in the SYSGEN dialog as capable
of accepting jobs.
OFF Disables the streams facility.
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode. Pressing Break does not affect this command. You can
enter this command only from the console; however, you can enter
this command from your terminal if your system administrator has
used the ALLOW command to enable you to enter the command.
* Requirements
The system administrator must enable the streams device every time
that the system is restarted in order to enable you to stream
jobs. If you attempt to stream a job when the streams facility is
disabled, the following message appears:
STREAM FACILITY NOT ENABLED: SEE OPERATOR. (CIERR 82)
* Selecting the streams device
The streams device is normally LDEV 10. Your system administrator
knows the LDEV for the streams device.
Examples
* To enable jobs and data streams on logical device number 10,
enter:
:STREAMS 10
* To disable data streams, enter:
:STREAMS OFF
Related Commands
ALLOW
STREAM
SYSGEN
The SYSGEN command enables you to create new system configurations,
modify existing configurations, or create installation tapes. This
command is a utility intended for use only by someone trained in
Hewlett-Packard system management tasks.
Syntax
SYSGEN [basegroup][,newgroup][,inputfile][,outputfile]
Parameters
basegroup Specifies the name of a base configuration group in
the SYS account. The account contains
configuration data to be used with the SYSGEN
command for changing the configuration or for
creating the installation tape. If you do not
include this parameter, the default is the group
used to bring up the system, which is normally
CONFIG.
newgroup Specifies the name of a group in the SYS account
used as the default for keeping a new set of
configuration data or a copy of the configuration
data in the base configuration group. If you do
not include this parameter, the default is the
basegroup.
input Specifies the file designator of the file to be
used for command input while the SYSGEN command is
executing. You can redirect input with a file
equation using the formal designator SYSGIN before
entering the SYSGEN command. The default is
$STDIN.
outputfile Specifies the file designator of the file to be
used for output requested while the SYSGEN command
is executing. You can redirect output with a file
equation using the formal designator SYSGOUT before
entering the SYSGEN command. The default is
$STDLIST.
Operation Notes
* Usage
You can enter this command from a session and programmatically.
Pressing Break suspends command execution. Entering the RESUME
command continues the execution.
* Requirements
You must have system supervisor (OP) capability to view
configuration data. You must have system manager (SM) capability
to make and keep configuration changes or to create an
installation tape.
* Unattended backups
The system administrator may want to perform a system backup that
does not require a user response to the tape request necessary for
the backup. In order to perform an unattended backup, however,
the tape drive must be configured with the autoreply mode. Refer
to the "Examples" section for the proper command sequence to
enable this mode.
Examples
* To use CONFIG.SYS as the default basegroup, NEWCONF.SYS as the
newgroup, and the default inputfile and outputfile, enter:
:SYSGEN CONFIG,NEWCONF,$STDIN,$STDLIST
* To include the same parameters in the example above without
specifying the default values, enter:
:SYSGEN ,NEWCONF
* To specify file equations for inputfile and outputfile that
redirect command input and output, enter:
:FILE SYSGIN=INFILE
:FILE SYSGOUT=OUTFILE
:SYSGEN ,NEWCONF
* To configure a tape drive for autoreply mode, enter:
:SYSGEN
SYSGEN>IO
IO>MDEV 7 MODE=AUTOREPLY
IO>HOLD
IO>EXIT
SYSGEN>KEEP
SYSGEN>EXIT
Related Commands
NMMGR
SHOWDEV
VOLUTIL
TELL
The TELL command enables you to send a message from your job or session
to one or more currently running sessions. The message appears on the
list device of the receiving session, which is usually a terminal.
Syntax
{[#]Snnn }
TELL {[sessionname,]username.acctname} [[;]text]
{@ }
{@.acctname }
Parameters
Snnn Specifies the session number to receive the
message.
[sessionname,] Specifies the name of the session or user to
username. acctname receive the message, and the account name to which
the message is directed. This parameter is the
same as the session identity entered with the HELLO
command.
@ Specifies all sessions.
@.acctname Specifies all user names logged on to the account
name.
text Specifies message text, preceded by a space or a
semicolon (;), that consists of a string of any
ASCII characters. If you do not provide message
text, the system still prints a FROM message on the
target terminal as shown:
FROM/sessionid
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode.
* Quiet mode
Users who enter the SETMSG OFF command are in quiet mode and
cannot receive your messages. This also applies to a session
running in quiet mode on the console. If you send a message to a
session in quiet mode, the system blocks the TELL command and
displays the following message:
Snnn username.acctname NOT ACCEPTING MESSAGES
* Multiple users
If several users are running under the same session identity, the
system sends the message to all of them.
* Additional acceptable message media
Messages that you send with this command can include escape and
control characters that invoke bells or inverse video.
* Restrictions
You cannot send a message to a job or to yourself. If you attempt
to send a message to a job, the following warning appears:
TARGET MUST BE INTERACTIVE, NO MESSAGE SENT.
(CIWARN 1627).
If you send a message to a terminal currently interacting with a
program, the system queues the message as high as possible among
the current input/output requests, but does not interrupt any read
or write in progress.
Examples
* To send an instructional message to user FRED, logged on in
account PAYROLL, running a session named FINANCES, enter:
:TELL FINANCES,FRED.PAYROLL USE FILES FROM YESTERDAY'S BACKUPS
* To send a message asking all users logged on in account PAYROLL to
log off, enter:
:TELL @.PAYROLL PLEASE LOG OFF
Related Commands
SETMSG
TELLOP
WARN
TELLOP
The TELLOP command enables you to send a message to the console. The
message appears on the console along with your job and session number and
the time you transmitted the message.
Syntax
TELLOP [text]
Parameters
text Specifies message text, preceded by a space, that
consists of any string of ASCII characters. If you
omit this parameter, no message text is sent to the
console; however, the console still receives
FROM/sessionid.
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode. Pressing Break does not affect this command.
* Command processing
You can send a message to the console, even if a session is not
currently active or if an active session is running in quiet mode.
As with messages transmitted with the TELL command, a message sent
using the TELLOP command prints as soon as possible without
interrupting any console input or input currently in progress.
Example
* To send a message informing the system operator that backups can
begin, enter:
TELLOP CRITICAL PROCESSING DONE. OK TO START BACKUPS
Related Commands
TELL
WARN
WARN
The WARN command enables you to send an urgent operator message to jobs
or sessions. The message interrupts any current pending read or write in
progress.
Syntax
{@ }
WARN {[#]Jnnn } [;message]
{[#]Snnn }
{[jsname,]user.acct}
Parameters
@ Specifies that all users receive the message,
including those running in quiet mode.
#Jnnn Specifies a job number assigned by the system for
the job that is to receive the message. Only jobs
submitted on interactive devices can receive
messages.
#Snnn Specifies a session number assigned by the system
for the job that is to receive the message. Only
jobs submitted on interactive devices can receive
messages.
jsname, user.acct Specifies the names of the job, session, and user
to receive the message, and specifies the account
name under which they are running. (These names
are the same as those entered with the JOB or HELLO
command.)
If several users are running under the same job and
session identity, the system sends the message to
all of them.
message Specifies the message text, consisting of any
string of ASCII characters containing no more than
67 characters. Pressing Return terminates the
message. The default is that no message prints.
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode. Pressing Break does not affect this command. You can
enter this command only from the console; however, you can enter
this command from your terminal if your system administrator has
used the ALLOW command to enable you to enter the WARN command.
* Quiet mode
A user can run a session in quiet mode, which suppresses messages
from other users; however, the WARN command overrides quiet mode
and also overrides a block mode screen.
Example
* To send a WARN message to all sessions, followed by a WARN message
to session #S51, enter:
:WARN @;THE SYSTEM WILL SHUTDOWN IN 5 MINUTES. PLS LOG OFF.
:WARN #S51;LAST CHANCE TO LOG OFF GRACEFULLY.
Related Commands
SETMSG
TELL
TELLOP
WELCOME
The WELCOME command enables the system administrator to define a greeting
message for users when they initiate jobs and sessions.
Syntax
WELCOME [welcomefile]
Parameters
welcomefile Specifies an ASCII file that contains the welcome
message.
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode. Pressing Break does not affect this command if a
welcome file is used; otherwise, Break aborts the command and
leaves the welcome message unchanged. You can only enter this
command from the console; however, you can enter this command from
your terminal if your system administrator has used the ALLOW
command to enable you to enter the WELCOME command.
You do not have to reboot the system after entering this command.
* Creating and deleting messages
You can either create a message interactively or specify a
pre-existing message file (welcomefile) when you enter the
command. Line lengths cannot exceed 72 characters, and the total
number of lines cannot exceed 26.
To delete an existing message, you enter the command and press
Return at the # prompt.
Examples
* To create a multiline welcome message interactively, enter:
:WELCOME
#WELCOME TO THE HP 3000 COMPUTER SYSTEM.
#FILES WILL BE STORED EACH DAY BETWEEN 6AM AND 7AM.
#Return
* To use a predefined message file called MESSAGE1, enter:
:WELCOME MESSAGE1
* To delete MESSAGE1, enter:
:WELCOME
#Return
Related Commands
HELLO
SHOWME
XEQ
The XEQ command executes any command file or program file. This command
is required when you want to execute a command file or program file that
has the same name as an existing MPE/iX or UDC command; however, you can
also use the command for any executable file.
Syntax
The syntax for a command file is
XEQ filename [parameterlist]
The syntax for a program file is
XEQ filename [;INFO={quotedstring}][;PARM={parmvalue}]
Parameters
filename Specifies the file name of the command file or
program file to be executed. The system uses the
search path (HPPATH) if you do not qualify
filename.
parameterlist Lists the parameters passed to filename when a
command file executes. The parameter list
corresponds to the PARM line(s) of the command file
you want to execute.
INFO Specifies a parameter string (quotedstring) for
program files that accept an INFO string. Quotes
are required if the INFO string requires
delimiters, such as ;=", and so on.
PARM Specifies a parameter value (parmvalue) for a
program file to be executed.
Operation Notes
* Usage
You can enter this command from a session, a job, a program, or in
break mode. Pressing Break suspends program files and aborts
command files, unless the command files use the NOBREAK option.
You can execute many command files in break mode; however, if a
command file runs a program, the system prompts you to abort the
suspended program. You cannot execute program files in break mode
unless you abort the suspended program.
Example
* To execute a command file named FCOPY.PUB.MYACCT, enter:
:XEQ FCOPY.PUB.MYACCT
Related Commands
ABORT
RESUME
RUN