Establishing multinode persistent sessions

When the application opens its ACB, it must indicate that persistent sessions are supported (PARMS=(PERSIST=YES)). The application must also include PERSIST=MULTI on its application definition. An MNPS application must be defined using a model application definition if the application operates at a network node. Upon completion of the OPEN ACB, the following information is added to the multinode persistent session structure:

Name of the owning VTAM®
Application program in persistence disabled state
Capabilities of the application (for example: NQN, APPC, and MACRF)

The application program then issues SETLOGON OPTCD=PERSIST to enable persistent LU-LU session support. If an application program wants to disable support for multinode persistent LU-LU sessions, SETLOGON OPTCD=NPERSIST should be issued. In both cases, the application program state in the coupling facility is updated to show "persistence enabled" or "persistence disabled," respectively.

You can issue the DISPLAY ID command to determine if application program sessions are recoverable.

If the command is issued from the owning VTAM, the /M status modifier in message IST635I indicates that the session might be recoverable by multinode persistent session (MNPS) support. The current MNPS state is also displayed.
```
IST1550I MNPS STATE = ENABLED
⋮
IST635I APPLAA1 ACTIV/M-P EAABEE1819963497 0000 0000 0 0 NETA
```
If the command is issued from another VTAM connected to the coupling facility structure in the sysplex message, IST1549I is issued. Message IST1549I contains MNPS STATE=ENABLED if the application program is recoverable by MNPS support.
```
IST1549I OWNER = NETA.SSCP1A MNPS STATE = ENABLED
```

Because sessions established for multinode persistent application programs use separate HPR connections from sessions not involving MNPS application programs, you might notice an increase in the number of HPR connections.