LU 6.2 in an XRF Environment

USERVAR process of using a generic name to represent a service does not work in an active LU 6.2 environment because LU 6.2 cannot tolerate LU name substitutions. However, support for LU 6.2 in an XRF environment allows generic name substitution, but only in a recovery environment.

The LU 6.2 application uses a USERVAR ID during recovery to transfer its users from one application program to a backup application program. This provides faster backup for failing applications.

To use this support, you need to identify the USERVAR to be used for LU 6.2 communications.

Be aware of the following restrictions:

You can assign only one USERVAR ID to an LU 6.2 application program.
You can have only one LU 6.2 application program as the primary application program to provide a service.
The operator can modify the USERVAR ID for LU 6.2, but the command must be issued from the host system of the application program providing the service.
If an incorrect USERVAR ID is assigned to an active LU 6.2 application program, the ACB must be closed and then reopened with the correct USERVAR ID.
Even sessions that request a bind using the real LU name must still carry the USERVAR ID.