z/OS TSO/E System Programming Command Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


OPERATOR-SEND subcommand

z/OS TSO/E System Programming Command Reference
SA32-0974-00

Use the SEND subcommand to
  • send a message to one or more terminal users
  • save a message for retrieval by user(s)
  • list, delete, or send a particular message from the notices section of the broadcast data set
  • list all messages in the notices section of the broadcast data set
  • communicate with console operators and other terminals in operator mode or extended MCS console mode
In a sysplex, SEND can be used to send a message to:
  • specific user(s) in the same JESPLEX
  • all users on a particular system in the same JESPLEX
  • all users on all systems in the same JESPLEX
  • all users on a subset of systems in the same JESPLEX

The system appends the characters OPER to the messages you send.

If you issue multiple SEND subcommands, the system may not process them in the order in which you issued them.

To provide better installation control and flexibility in the use of the SEND subcommand, you can modify its operation and function by specifying parameters in the IKJTSOxx member of SYS1.PARMLIB and through the use of OPERATOR SEND exit routines.

Using IKJTSOxx, you can set defaults to
  • enable/disable the use of the SEND subcommand
  • have messages stored in either the broadcast data set or individual user logs
Using the OPERATOR SEND exit routines, you can
  • change the defaults you set in IKJTSOxx
  • add diagnostic information to a message
  • reformat a message
  • change the target data set for a message
  • change the target user IDs for a message

For detailed information concerning IKJTSOxx, see z/OS TSO/E Customization and z/OS MVS Initialization and Tuning Guide. For detailed information concerning the OPERATOR SEND exit routines, see z/OS TSO/E Customization.

The syntax of the SEND subcommand of OPERATOR is:

  • SEND is an authorized subcommand.
  • The system does not write messages to the broadcast data set in the same order as they are sent.
LIST
Display a list of all messages stored in the notices section of the broadcast data set. (Each message displayed is preceded by a system-assigned number.)
msg
The message you are sending. Ensure that the message is a one-line message. If you want a quotation mark as part of the message, enter two quotation marks in the original text.
value:
variable-length character string, with a maximum length of 115 characters
msg_nmbr
The identification number of a message in the notices section of the broadcast data set. (The system assigns the identification number.)
value:
an integer
ROUTE
Send the message to all users logged on the indicated system(s).
*ALL
All systems that are members of the same JESPLEX.
systemname
Only system systemname
groupname
Only the named subset of systems that are members of the same JESPLEX.

systemname and groupname are in MVS™ name token format. For information on using the MVS program IEEGSYS to define them, see z/OS MVS Planning: Operations.

If ROUTE= is not specified, the message is sent only to the users on the system on which the SEND subcommand is issued.

ALL
Send the message to all terminal users.

If you specify ALL, or if ALL is defaulted and ROUTE is not specified, the message will be delivered to all logged on users on the system where the SEND subcommand is issued.

USER
Send the message to the indicated terminal user(s)
userid
The user ID of one or more terminal users who are to receive the message. (The maximum number of user IDs allowed is 20.)
value:
1-7 alphanumeric characters, beginning with an alphabetic or special character
LOGON
Send the message immediately to the terminal user(s) logged on and receiving messages; otherwise,
  • users logged on, but not receiving messages, receive it upon requesting messages.
  • if you specify ALL, the system stores the message in the notices section of the broadcast data set; sends it to every user as the user logs on and requests messages; and retains it in the broadcast data set until you delete it.
  • if you specify USER, the system stores the message in the mail section of the broadcast data set or in the user log data set; sends it to each indicated user as the user logs on and requests messages; and deletes it after all indicated users have received it.
  • if you specify NOWAIT, the system creates mail for those users whose terminals are busy.

Using LOGON, a message can be saved for retrieval by a user on any system where the broadcast data set or user log data set is properly shared.

NOW
Send the message immediately
  • if you specify ALL, the system sends the message to all terminal users currently logged on, and then deletes it
  • if you specify ALL and NOWAIT, users whose terminals are busy do not receive the message. The system does not notify you that the user did not receive the message.
  • if you specify USER and NOWAIT, users whose terminals are busy do not receive the message. The system notifies you and then deletes the message.
  • if you specify USER, the system sends the message to the indicated terminal user(s) currently logged on. If any indicated terminal user(s) are not logged on, the system notifies you; and then deletes the message. (Terminal users not currently logged on never receive the message.)
SAVE
Store the message in the appropriate section of the broadcast data set. The system does not send the message immediately, even to those terminal users currently logged on and receiving messages.
  • if you specify ALL, the system stores the message in the notices section of the broadcast data set, and assigns it an identification number. The system displays the identification number at your terminal. The system sends the message to terminal users as they log on and request messages; and retains it in the broadcast data set until you delete it.
  • if you specify USER, the system stores the message in the mail section of the broadcast data set or in the user log data set, and sends it to the indicated terminal user(s) as they log on and request messages. After the last indicated user has received the message, the system deletes it. The WAIT/NOWAIT operand is ignored for SAVE.

Using SAVE, a message can be saved for retrieval by a user on any system where the the broadcast data set data set or user log data set is properly shared.

WAIT
Wait until all specified users can receive the message. If a user's terminal is busy, the other specified users do not receive the message until the user's terminal is no longer busy. A user's terminal is busy if a user's output buffers are full.
NOWAIT
Do not wait until all specified users can receive the message. Even if a user's terminal is busy, the other specified logged on users still receive the message. If you specify USER, you are notified of any users that did not receive the message. If you specify LOGON, the message is saved as mail for those users whose terminals were busy or those users who were not logged on.
BRDCST
Queue the message to all active operator consoles and extended MCS consoles
CN
Queue the message to a particular operator console or an extended MCS console
console
For an operator console, specify the console name defined by your installation.
For an extended MCS console, use the name of the console (usually your TSO/E user ID). If you specify an incorrect console name, you receive an error message.
value:
a console name, 2-8 alphanumeric characters beginning with either an alphabetic character or one of the special characters: #, $, or @.
INTERNAL
Specifies that the message is to be sent to any active console defined with INTIDS=Y.

For additional information about defining consoles with INTIDS=Y, see z/OS MVS Planning: Operations.

OPERATOR
Queue the message to the console associated with the routing code
rte_code
The target destination for a message
value:
as shown in the following table
Routing Code Console
1 Master console action
2 Master console information
3 Tape pool
4 Direct access pool
5 Tape library
6 Disk library
7 Unit record pool
8 Teleprocessing control
9 System security
10 System error/maintenance
11 Programmer information
12 Emulators
13-20 Reserved for your use
21-28 Reserved for subsystem use
29-40 Used by JES3 to represent messages issued for job status
41 Reserved for IBM® use
42 General information about JES2 or JES3
43-64 Reserved for JES2/JES3 use
65-96 Messages associated with particular processors
97-128 Messages associated with particular devices

See MVS System Messages (Volume 1 to 10) if you require further explanations of these routing codes.

DELETE
Delete the message identified by msg-nmbr from the notices section of the broadcast data set
LIST
Display the message identified by msg-nmbr from the notices section of the broadcast data set

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014