Except for exit routines called from the HASPCOMM module of HASJES20 and exit routines called from JES2 initialization and termination, exit routines called from the JES2 main task environment can communicate with the operator through the $WTO macro. Exit routines called from the HASPCOMM module can communicate with the JES2 operator through the $CWTO macro. Exit routines called from a JES2 subtask or during JES2 initialization and termination can communicate with the operator through the $$WTO and $$WTOR macros or through the MVS™ WTO and WTOR macros. Exit routines called from the user environment or functional subsystem environment can communicate with the operator through the MVS WTO and WTOR macros. Note that, if a message is to be associated with jobs processed by a functional subsystem, the job id must be included with the message. notification. Exits 2, 3, and 4 allow you to send an exit-generated message to the operator along with certain return codes by setting a flag in the RXITFLAG byte. Exit 5 allows you to control the standard $CRET macro “OK” message and to send your own exit-generated message text through the $CRET macro. Exit 9 allows you to control the standard output overflow message. Exit 10 allows you control over the text and routing of all $WTO messages. For details, see the individual exit descriptions.