5 Configuring a Remote Library

Figure 5-1 shows an example configuration with a remote library; the following sections tell how to configure this example.

Figure 5-1 RTDs Operating Under a Remote TapePlex

Description of Figure 5-1 follows
Description of ''Figure 5-1 RTDs Operating Under a Remote TapePlex''

Modifying the SMC SCMDS File

SMC manages all communication between VTCS and a remote TapePlex, so SMC must know how to connect to the remote TapePlex. You do so by defining a local and a remote TapePlex plus one or more SMC SERVER statements that define the TCP/IP control paths to the remote TapePlex. You may want to do this in your SMC CMDS file as shown in the following example.

TAPEPLEX NAME(TMVSA)LOCSUB(HSC0)
TAPEPLEX NAME(TMVSB)LOCSUB(HSC1)
SERVER NAME(TMVSB)IP(192.168.1.10)PORT(60000)

This example contains:

  • A TAPEPLEX statement, which defines a local TapePlex, TMVSA, with an HSC running on the local MVS host (HSC0).

  • A second TAPEPLEX statement, which defines a remote TapePlex, TMVSB, with an HSC running on the remote MVS host (HSC1).

  • A SERVER command that defines a UUI communication path to TMVSB, where:

    • The remote server name is TMVSB.

    • The IP parameter value is the ELS port IP address of 192.168.1.10 for UUI communications.

    • The PORT parameter value is 60000; this value is always used for the SERVER PORT parameter for SMC communication with a TMVSB.

Updating the VTCS CONFIG Deck to Define a Remote Library

You must update VTCS CONFIG deck to define the remote library and the connectivity from the VTSS to the remote library. As shown in the following example, the remote library is defined by a CONFIG STORMNGR statement.

TAPEPLEX THISPLEX=TMVSA
STORMNGR NAME=TMVSB
VTSS NAME=VTSS1 LOW=70 HIGH=80 MAXMIG=8 MINMIG=4 RETAIN=5
RTDPATH  NAME=RM1RTD1 STORMNGR=TMVSB DEVNO=1A00 CHANIF=0A:0
RTDPATH  NAME=RM1RTD2 STORMNGR=TMVSB DEVNO=1A01 CHANIF=0A:1
RTDPATH  NAME=RM1RTD3 STORMNGR=TMVSB DEVNO=1I00 CHANIF=0I:0
RTDPATH  NAME=RM1RTD4 STORMNGR=TMVSB DEVNO=1I01 CHANIF=0I:1
VTD LOW=6900 HIGH=69FF

In this example, note:

  • The CONFIG TAPEPLEX statement specifies TMVSA as the local TapePlex.

  • A STORMNGR statement specifies TMVSB as the remote library.

  • The CONFIG RTDPATH statements for VTSS1, which specify:

    • The name of the RTDPATH.

    • The connection to the remote library (STORMNGR=TMVSB).

    • The device number (DEVNO).

    • The CHANIF value for each VTSS to RTD connection in ci:p format where:

      • c is 0 or 1.

      • i is A or I.

      • p is 0 through 3.

        Note:

        For VSM5s, the CHANIF value must match the values specified on the VSM5 IFF Configuration Status Screen. For VSM 6s, this must be unique for each VTSS but does not correspond to an actual value on the VSM 6 TCP/IP ports.

You can now use the STORclas STORMNGR parameter to route data to the remote library. For example:

STOR NAME(REMLIB) STORMNGR(TMVSB)

MVC Pool Considerations

Any MVCs in a remote library must be included in the local MVC pool definitions, preferably through VOLPARM/POOLPARM definitions. The local HSC treats the remote MVCs as non-library.

Any remote library server typically needs to define the MVCs as "externally managed" by some method. Having a remote TapePlex sharing a pool of local MVCs is not supported because there is no serialization.

If a pool of MVCs is shared for data transfer purposes, then only one TapePlex can actively write to the MVCs. The other TapePlexes can have only read-only access. Serialization of the MVCs on drives is the responsibility of the user.