TERMINAL COMMANDS SIGNON Command

SIGNOFF Command

When a writer is interrupted (I/O error, for example), the operator can enter a FLUSH, a RESTART, or a STOP command through the reader.

Note. If a punch writer and a list writer are active at the same time, list output receives priority over punch output.

The SIGN ON command identifies the terminal, and makes the logical connection between the terminal and the system. It must "be the first card submitted from the terminal after the line is started by the central operator. It can also be submitted during the course of the session, in which case it terminates the current session and initiates the next session.

The operator must use the remote-id assigned to him during POWER/VS generation, since the terminal characteristics are defined in relation to this remote-ide If the same remote-id is used to sign onto another terminal with different hardware characteristics, causing unpredictable results.

The security password must match the password set for the line by the central operator.

If the central operator did not specify a password when the line was started, it must match the password set for the line during POWER/VS generation. If no password is set for the line, the password parameter can be omitted.

* ..

SIGNON remid[,password] user information Operands

remid. Specifies the remote-id assigned to the terminal during POWER/VS generation.

Remote users are identified by numbers from 1 to 200.

password. Specifies the password set for the line by the central operator, or set during POWER/VS generation. It can be any combination of up to eight alphameric characters.

user information. Consists of up to sixteen bytes of user information, which are moved to the line account record. This information is punched in· columns 56 to 71.

Note. An invalid SIGNON command is interpreted as a SIGNOFF command. The terminal is disconnected if it is on a switched line.

Example:

* ..

SIGNON 002, SECRET Sign on at. a teoninal with remote-id 002 and password SECRET.

The SIGNOFF command informs the system that the remote operator will terminate the session at the nextend-of-ftle condition on the reader. POWER/VS will disconnect the terminal from the system, stop any active writers, and: prepare the line for other terminals to sign on.

Note. A terminal is forced to sign off when it has been idle for a number of minutes, as defined during POWER/VS generation.

* ..

SIGNOFF (no operand) Example:

* ..

SIGNOFF Terminate a session.

TASK MANAGEMENT COMMANDS

START Command

STOP Command

The START command is used to initiate an RJE write task (writer). The RJE read task (reader), is controlled only by the central operator.

The remote operator must enter a START command in order to receive his output.

POWER/VS does not send unsolicited output to any terminal.

A START command is invalid when applied to an active task.

The START command is also used to cause broadcast messages to be accepted. (When an RJE task is started, the terminal accepts broadcast messages until MSG is specified in the STOP command.)

* ..

START

~

^task task,class

^~

MSG Operands

task. Specifies the task to be started as LST or PUN. Write entries are processed on a first-in, first-out basis within priority, within class.

class. Defines the output class( es) upon which the task is to operate. Up to four classes can be designated by specifying one to four alphabetic characters from A through Z.

The order specified is the order in which the classes will be processed. If no class parameter is specified, only class A is selected.

MSG. Specifies that all subsequent broadcast messages directed to this terminal are to be accepted (printed).

Examples:

* ..

START PUN Start punch task for class A.

* ..

START LST,AB Start list task for classes A and B.

The STOP command is used to terminate an RJE write task. The terminal operator cannot control the operation of an RJE read task.

A STOP command is invalid when applied to an inactive task.

The STOP command is also used to cause broadcast messages to be ignored (not accepted).

* ..

STOP

task

I

task,EOJ task,RESTART MSG

7.4 DOS/VS POWER/VS Installation and Operations

(

GO Command

F LUSH Command

Operands

task. Specifies the task to be stoppe~. LST or ~UN are the valid entries.

EOJ. Specifies that the task will not stop until it has completed processing the current

entry. '

-RESTART. Specifies that when the task is started again, processing will begin at the record following the last one processed before tl!e STOP command was issued.

MSG. Specifies that all subsequent broadcast messages directed to this terminal are to be ignored. In addition, existing messages

lP

the q4eue are deleted immediately.

Note. If either EOl or RESTART is (lot specified along with "task", processing will begin at the first record of the current job entry when this task is started again (via START).

Examples:

* ..

STOP PUN,RESTART

* ..

STOP LST ,EOJ

* ..

STOP LST

* ..

STOP MSG

Stop the punch task. When the task is restarted, processing of the entry continues at t~e point of interruption.

Stop, the list task after completion of the current list entry.

Stop the list task immediately. When the task -is restaited', processing will start at the beginnirtg

of

the interrupted list entry.

, ~ ,

Ignore~roa~cast messages.

The GO command is used to re-activate a write task after receiving the "mount forms"

message.

* ..

GO task

Operands

task. Specifies the task to be re-activated as ~~T or PUN.

Example:

* ..

GO LST Re-activate the list task. The proper forms have been mounted.

The FLUSH command is used to discontinue the job entry currently being processed

by an RJE write task.

-When the write task is flushed, further output processing is terminated for this POWER/VS job, and the write entry' is-de~eted,unless HOLD is specified.

FLUSH is invalid when applied to an inactive task. Also, FLUSH can only be issued for a task that has been interrupted by -the remote or central operator or by an action-type POWER/VS message.

* ..

^FLUSH

{task } task ,HOLD

RESTART Command

Operands

task. Specifies the task to be deleted as LST or PUN.

HOLD. Specifies that the corresponding write entry is not to be deleted, but put in the hold state.

Examples:

* ..

FLUSH PUN

* ..

FLUSH LST,HOLD

Delete the punch entry currently being punched.

Continue with the next entry.

Skip the list entry currently being printed, but do not delete it from the queue.

Continue with the next entry.

The RESTART command directs the RJE write task to discontinue printing or punchih_o immediately and to resume output from a specified point. A list writer can resume printing from either the beginning of the list entry, or up to 9999 pages forward or backward from the interrupted page. A punch writer can resume punching from either the beginning of the punch entry, or up to 9999 cards forward or backward.

The number of duplicated pages printed or cards punched because of a RESTART command is separately counted and stored in the list account record (if created).

RESTART is invalid when applied to an inactive task. Also, RESTART is only applicable to a task that has been interrupted by the operator or by an action-type POWER/VS message.

* ..

^RESTART

{task } task,n

Operands

task. Specifies the task to be restarted as LST or PUN.

n. Specifies a signed or unsigned value from 0 to 9999. A plus sign indicates the number of pages or cards forward and a minus sign indicates the number of pages or cards backward from the last interrupted page or card. No sign indicates a specified page or. card count from the beginning.

If the operand is omitted or is too large a backward count, output resumes from the first page or card. If too large a forward count is specified, message 1 Q42I is issued and the command is ignored.

Example:

* ..

RESTART LST,.lO Reprint .the previous ten pages and continue to the end of output.

QUEUE MANAGEMENT COMMANDS

Dans le document DOS/VS POWER/VS Installation and Operations (Page 85-88)