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


SEND command

z/OS TSO/E Command Reference
SA32-0975-00

Use the SEND command or the SEND subcommand of EDIT to send a message to anyone of the following destinations:
  • One or more users
  • An operator specified by route code
  • An operator console specified by name

SEND can be used to send a message from one user to another user in the same JESPLEX.

In order for the recipient to receive and display the message, the recipient's profile must include the INTERCOM operand. To change the profile, use the PROFILE command.

By default, when you issue the SEND command with the NOW operand, the message is displayed on the recipient's screen if he or she is logged on and receiving messages. If the receiver is not logged on or is not receiving, the message is deleted and you receive a message stating why the message was not displayed.

If you issue SEND with the LOGON operand and the recipient is logged on and receiving, the message is also displayed. If the recipient is not logged on when you send the message, the message is stored in the broadcast data set. (If your installation uses individual user logs, SEND stores the message in the user log, truncating trailing blanks. Otherwise, SEND stores the message in the broadcast data set and does not truncate trailing blanks.)

When you issue SEND with the SAVE operand, the message is stored even if the recipient is logged on. SEND stores the message in the broadcast data set unless your installation uses individual user logs, in which case, the message is stored in the recipient's user log.

Installations can use security enhancements to customize how the SEND command works. For example, using RACF®, an installation can control which users can send messages to other users. If your installation uses these security features and you send a message to a user that you are not authorized to send messages to, the system cancels your message and displays an informational message on your terminal.

SEND also works differently if your installation uses security labels and security checking. Each time you send a message, the security label you are logged on with is associated with the message. The security label is used to determine if the recipient can view the message.

If you issue SEND NOW or SEND LOGON, the sender's current security label is associated with the message. If the recipient is logged on at a security label that is equal to or greater than the security label of the message, the message is displayed immediately. If SEND NOW was specified and the recipient's security label is less than the message's security label, the message is canceled. If SEND LOGON was specified and the recipient's security label is less than the message's security label, the message is saved in the recipient's user log.

If the message you send is to be saved (when you issue SEND SAVE or SEND LOGON and the recipient is not logged on), the message's security label is saved along with the message in the recipient's user log. The recipient can view messages saved in the user log by issuing the LISTBC command. All messages in the recipient's user log that have a security label that is less than or equal to the security label of the recipient are then displayed. Messages that have a security label higher than the security label the recipient logged on with are not displayed. See LISTBC command for more information about receiving messages from a user log.

If your installation uses security labels and security checking, messages are stored in user logs. If you try to send a message to another user who does not have a user log and the message is to be saved, the message is not sent. You get a message explaining why the message cannot be saved.

Note: The SEND command can not be used to communicate with users who are logged in under z/OSMF ISPF.

The syntax and function of the SEND subcommand of EDIT is the same as that of the SEND command.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014