In the JES2 network environment, each job entry subsystem must have a unique name defined to VTAM®. When you need to define several instances of JES2 as VTAM applications, you can enter a single command to define a unique name to each instance. For example, you can establish the following naming convention for the application names:

JES&SYSNAME.

If you enter the following command:

ROUTE *ALL,$t logon(1),p=,a=jes&SYSNAME.

For a sysplex that contains three MVS™ systems names SYS1, SYS2, and SYS3, the following commands are entered on each system:

$t logon(1),p=,a=jessys1  /* Define appl jessys1 on system SYS1 */
$t logon(1),p=,a=jessys2  /* Define appl jessys2 on system SYS1 */
$t logon(1),p=,a=jessys3  /* Define appl jessys3 on system SYS2 */

Because the application names follow a naming convention, you can enter subsequent commands to affect some or all of the JES2 instances identified by application names. For example, to stop JES2 and restart all the JES2/VTAM interfaces in the sysplex, enter the following command:

ROUTE *ALL,$e logon(1),a=jes&SYSNAME.

The commands entered on each system are:

$e logon(1),a=jessys1  /* Restart appl jessys1 on system SYS1 */
$e logon(1),a=jessys2  /* Restart appl jessys2 on system SYS1 */
$e logon(1),a=jessys3  /* Restart appl jessys3 on system SYS2 */