z/OS JES2 Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Controlling the JES2/VTAM interface

z/OS JES2 Commands
SA32-0990-00

Use the $S LOGON(n) command to start the JES2/VTAM interface, as previously described in “Starting Node Communication Using SNA/VTAM”. JES2 allows you to assign a password and ID to the JES2/VTAM interface and monitor the interface activity. You can also stop and restart the interface. The following describes the commands you issue to perform these functions:
Assigning a password and ID to the JES2/VTAM interface
Use the $T LOGON(n) command to assign a password and an application ID to the JES2/VTAM interface. You must be certain to make note of the password assigned because there is no facility for displaying the password in effect. This command requires system authority.
Note: The password and application ID assigned to the JES2/VTAM interface must also be defined to VTAM®. For VTAM interface information, refer to z/OS Communications Server: New Function Summary, .
Monitoring the JES2/VTAM interface
You can also use the $T LOGON(n) command to record SNA events on the master console as an aid in diagnosing SNA problems. These events can also be traced. This command requires system authority.
Note: When the JES2/VTAM interface is monitored, activity on all SNA lines is monitored.
Stopping the JES2/VTAM interface
For SNA remote workstations, use the $P LOGON(n) command to stop the JES2/VTAM interface. When you issue this command, all logon requests are rejected. Sessions that are already established are allowed to finish normally. Use the value of n specified in the LOGON(n) initialization parameter that defines the interface to be stopped.
Restarting the JES2/VTAM interface
Use the $E LOGON(n) command to stop and restart the JES2/VTAM interface on a logical line. Use the value of n as defined in the LOGONn initialization parameter for the interface to be restarted. When you issue this command, data currently being transmitted immediately stops, and the partial input is purged. Any output being transmitted is placed on the output queue. When data is transmitted again, the output is transmitted from the point where it was stopped.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014