4 VSM console Configuration Scenarios

This chapter shows samples of the following configuration scenarios:

Database Configurations

The following configurations are examples of two database modes:

SQL Database

Figure 4-1 shows a typical configuration using SQL database services. This is expected to be the most common configuration.

After the VSM console initial configuration has been performed, load the oVTCS policies through the oVTCS MGMTDEF ACTIVATE command and perform an oVTCS configuration. These tasks are executed through the SMCUUUI utility. See "Loading the oVTCS Policy Parameter File Using the SMCUUUI Utility".

Once the MGMTDEF and oVTCS configuration is completed, the VSM console systems may be brought up to full service level.

Figure 4-1 Configuration Using SQL Services

Surrounding text describes Figure 4-1 .

HSC CDS

Figure 4-2 shows a configuration using an HSC CDS.

Assuming you have an existing production environment with VTCS using an HSC CDS, and you want to migrate to VSM console, you can perform the procedure below.

Note:

You can use this method to transition an existing tapeplex under ELS control to a tapeplex under VSM console control. It enables ELS and VSM console to run on the same hardware and to use the same CDS. Specifically this enables a fallback to an all ELS controlled system if required.

  1. Set up VSM console to share an HSC CDS.

  2. Create a test system on VSM console.

    • If it fails, remove VSM console, and the CDS retains the correct data.

    • If it succeeds, add a production environment to VSM console.

  3. If the test system is running properly, move all production to VSM console and stop VTCS on all MVS systems.

  4. Configure VSM console to use SQL database services.

Figure 4-2 Configuration using an HSC CDS

Surrounding text describes Figure 4-2 .

VSM console Configurations

The following configurations are examples for VSM console:

In each example, an SMC client is connected to access the VSM console. Though not shown, a VSM system is present in each configuration. Virtual requests are processed by the oVTCS application residing on the VSM console server.

Configuration for VTVs Only

Figure 4-3 shows a configuration with VSM console processing VTVs only.

In this configuration, there is one oVTCS TapePlex on two VSM console servers (one primary and one secondary). The SMC client's SMCCMDS or SMCPARMS data set must define only one SMC TAPEPlex statement and two SMC SERVer statements, one for each oVTCS TapePlex.

See "Using an MVS Client with the VSM Console" for more information about connecting the SMC client to the VSM console.

Figure 4-3 Configuration for VTVs Only

Surrounding text describes Figure 4-3 .

Configuration with VLE

Figure 4-4 shows a configuration with Oracle's Virtual Library Extension (VLE) added.

In this configuration, there is one oVTCS TapePlex on two VSM console servers (one primary and one secondary). The SMC client's SMCCMDS or SMCPARMS data set must define only one SMC TAPEPlex statement and one SMC SERVer statement for the oVTCS TapePlex.

See "Using an MVS Client with the VSM Console" for more information about connecting the SMC client to the VSM console.

Additionally, the oVTCS on the VSM console must define VLE as a TapePlex. See "Loading the oVTCS Policy Parameter File Using the SMCUUUI Utility".

Figure 4-4 Configuration with VLE

Surrounding text describes Figure 4-4 .

Configuration with a Real Library

Figure 4-5 shows a configuration with a library added logically.

In this configuration, there is one oVTCS TapePlex on two VSM console servers (one primary and one secondary). The SMC client's SMCCMDS or SMCPARMS data set must define SMC TAPEPlex and SERVer definitions for oVTCS on the VSM console.

If the SL library includes non-RTD tape drives, and non-MVC tape cartridges accessible to MVS, then the SMC client's SMCCMDS or SMCPARMS data set must also define SMC TAPEPlex and SERVer definitions for the HSC or ACSLS library server.

If the SL library includes only RTD tape drives and MVC tape cartridges accessible only to oVTCS, then the SMC client's SMCCMDS or SMCPARMS data set does not require SMC TAPEPlex and SERVer definitions for the HSC or ACSLS library server.

The library server can be HSC or ACSLS:

  • If the library server is HSC, then it resides on an MVS host.

  • If the library server is ACSLS, it is located on the ACSLS LDOM on the VSM console server.

See "Using an MVS Client with the VSM Console" for more information about connecting the SMC client to the VSM console.

Additionally, the oVTCS on the VSM console must define the HSC or ACSLS library server as a TapePlex. See "Loading the oVTCS Policy Parameter File Using the SMCUUUI Utility".

Figure 4-5 Configuration with Real Library

Surrounding text describes Figure 4-5 .