Saving messages in the broadcast data set

Use the SEND...,SAVE command to store messages in the broadcast data set to be issued only at LOGON time, or when requested.
 
SE {'message'},{USER=(userid[,userid]...)},SAVE
   { msgno   } {ALL                      }
 

The parameters are:

‘message’
The message to be sent to the terminal users.
msgno
The number of the message to be sent.
USER(userid)
The identifications of those users to receive the message. The message is stored in the mail sections for those users. (There is a mail section for each TSO user.)
ALL
All terminal users are to receive the message. Terminal users who are currently using the system receive the message immediately. In addition, the message is placed in the notices section and assigned a number. This number, printed when the message is stored, can be used as msgno in this and other forms of the SEND command.
SAVE
The message is to be stored in the appropriate section of the broadcast data set until a user logs on or requests messages. If ALL is specified, the message is stored in the notices section of the broadcast data set and is retained until explicitly deleted. If userid is specified, the message is stored in the mail section of the broadcast data set and deleted after it is sent to the intended user. No attempt is made to send it immediately, even to those users logged on and receiving messages.
Note: WAIT and NOWAIT have no effect when specified with SAVE.

Example:

To submit messages to the broadcast data set before stopping time-sharing for the day, enter:
se 'time-sharing will close down at 5:00 p.m. today.',save

When you start time-sharing the next day, the messages are available for users logging on. The above command does not affect those users currently logged on and receiving messages.