Installation configuration statements - Latest

Syncsort™ Storage Management Monitor TS7700 Interface Guide
Product type
Software
Portfolio
Integrate
Product family
Syncsort™ software
Product
Syncsort™ Storage Management > Syncsort™ SCC Monitor
Version
Latest
ft:locale
en-US
Product name
Syncsort Storage Management
ft:title
Syncsort™ Storage Management Monitor TS7700 Interface Guide
Copyright
2021
First publish date
1991
ft:lastEdition
2025-12-05
ft:lastPublication
2025-12-05T10:33:33.231000

By default, the configuration statement definitions are located in the MONPOOLS member shared with other Monitor components. However, customer installations running multiple components can segregate the TS-7700 configuration statements into another PDS member and then use an INCLUDE statement in MONPOOLS. For example, if the configuration statements are located in the DTS.R71.RULELIB(TSCONFIG) member, add the following statement in the MONPOOLS member.

INCLUDE TSCONFIG

If your installation is not using any other Monitor components, the TS-7700 statements can be added directly to the DTS.R71.RULELIB(MONPOOLS) member.

Configuration statements

The BVIR interface uses a standard labeled tape volume to both initiate a request for information and return the results. The MON-TS7700 application uses dynamic allocation to allocate a tape from the target cluster or grid.

The configuration statements used in this section can be categorized into three types:

  • Specific Cluster or Grid
  • List of Clusters or Grids
  • Remote System Definition

DEFLIST (specific cluster or grid)

A special DEFLIST TYPE(BVIR) statement is used to define the allocation parameters required to direct a BVIR request to a specific cluster or grid. In most installations, an SMS MGMTCLAS can be used to direct a request to a specific TS-7700 cluster, and the SMS STORCLAS construct can be used to direct a request to a specific grid.

For example, the following sample statements can be used to define access to the installation clusters and grids:


DEFLIST CLSP1 ('MGMTCLAS(CLSP1)') TYPE(BVIR)
DEFLIST CLSP2 ('MGMTCLAS(CLSP2)') TYPE(BVIR)
DEFLIST CLSP3 ('MGMTCLAS(CLSP3)') TYPE(BVIR)
DEFLIST CLSP4 ('MGMTCLAS(CLSP4)') TYPE(BVIR)
DEFLIST GRIDP1 ('STORCLAS(GRIDP1)') TYPE(BVIR)
DEFLIST GRIDP2 ('STORCLAS(GRIDP2)') TYPE(BVIR)

The name on the DEFLIST statement is used by the ISPF panels and batch reporting facility to direct the command request to a specific device. For example, Point-In-Time requests are typically directed at specific clusters. Historical information is typically stored on all clusters in a grid, so historical requests can be directed to any device located in the grid.

The TYPE(BVIR) keyword parameter is required for MON-TS7700DEFLIST configuration statements.

The second positional field enclosed in parentheses contains the dynamic allocation request parameters required to select an appropriate device, or allocate a dataset that already contains the BVIR output data. The parameters must be enclosed in a quoted string. The valid allocation parameters follow:

DATACLAS

The DATACLAS parameter can be used to specify the name of an SMS DATACLAS to be used on the dynamic allocation request. Note: The parameter has an alias of DC.

DSNAME

The DSNAME parameter can be used to specify the name of a dataset that already contains the BVIR output from a previous command. This can be used for situations where a MONRUN job creates and saves the BVIR data for future access by later requests.

MGMTCLAS

The MGMTCLAS parameter can be used to specify the name of an SMS MGMTCLAS to be used on the dynamic allocation request. This parameter is typically used to select a device in a specific cluster. Note: The parameter has an alias of MC.

STORCLAS

The STORCLAS parameter can be used to specify the name of an SMS STORCLAS to be used on the dynamic allocation request. This parameter is typically used to select a device in a specific grid. Note: The parameter has an alias of SC.

SYSTEM

The SYSTEM parameter can be used to specify the name of a DEFCONN statement used to direct the request for a remote system.

This parameter is typically used in conjunction with other parameters which are passed to the remote system for execution. Once the command completes, the BVIR output data is returned to the calling system.

UNIT

The UNIT parameter would only be used with the DSNAME and VOLSER parameters when the specified dataset is not cataloged. Note: SMS always ignores unit information, so UNIT is not required for use with the SMS parameters.

VOLSER

The VOLSER parameter would typically be used with the DSNAME and UNIT parameters when the specified dataset is not cataloged.

List of clusters or grids

If the BVIR command requests require consolidated output data, the DEFLIST statement can be used to create groups of clusters or grids. For example, building on the previous examples, the following sample statements can be used to route command requests to multiple clusters or grids and consolidate the output data for processing:


DEFLIST GP1CLS (CLSPA,CLSPB) TYPE(BVIR)
DEFLIST GP2CLS (CLSPC,CLSPD) TYPE(BVIR)
DEFLIST ALLGRIDS (GRIDP1,GRIDP2) TYPE(BVIR)

For example, if a point-in-time request is made to the GP1CLS name, the command request is made to both the CLSPA and CLSPB clusters and the consolidated data is then processed for output. Similarly, a request for historical data from ALLGRIDS will obtain the data from only one device in each grid and then process the consolidated data. Note: Each cluster in a grid maintains a copy of the historical data so only one request per grid is required.

Remote system definitions

MON-TS7700 can access clusters and grids that are not physically attached to the local system. If the remote system is also running MON-TS7700, a BVIR request can be routed to the target system via TCP/IP, where the application on the target system makes the BVIR request and then returns the output data to the originating system. This remote access facility works across Sysplex boundaries.

For installations that contain multiple clusters and/or grids that are not attached to all LPARs, the SYSTEM parameter can be used in conjunction with a DEFCONN statement to define connections to the remote systems. To use this facility, the remote system(s) must be configured as follows:

  • MON-TS7700 must be configured on the remote system(s) to access the physically attached clusters and grids
  • The MONRUNM procedure must be located in a system procedure library
  • The remote systems set up the DIF TCP/IP Server

The target systems must have a DIF SERVER TCPIP parameter configured to monitor the IP port specified in the previous step. Once a server has been configured, the DIF started task can receive JCL validation requests from remote systems using the specified IP port and logon credentials passed from the DEFLIST statement.

For example, the following card can be placed in DTS.R61.PARMLIB(DIFINIT). The card specifies the TCPIP jobname running on MVS (TCPIP), and the port number to be used by DIF (10 in the example). For more information, examine “SERVER” on page 6-16 in the Product Installation Guide.

INITOPT SERVER(TCPIP(TCPIP 10)) LOGBUF(5000 500 1)

After adding the INITOPT SERVER card, the DIF started task must be restarted using the following DIF console commands:

F DIF,Z, S DIF

Once the remote system(s) have been properly configured, the local configuration statements can then be modified to access data from remote systems.

Note: The allocation parameters used by the remote system definitions are passed to the target system and aren't necessarily valid on the local system. For example, the following sample statements in the PORTLAND site could be used to define access to the clusters and grids in the NYC installation: 

DEFLIST CLSNA ('MGMTCLAS(CLSNA) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST CLSNB ('MGMTCLAS(CLSNB) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST CLSNC ('MGMTCLAS(CLSNC) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST CLSND ('MGMTCLAS(CLSND) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST GRIDN1 ('STORCLAS(GRIDN1) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST GRIDN2 ('STORCLAS(GRIDN2) SYSTEM(NYC)') TYPE(BVIR)

DEFCONN NYC TCPIP(SYSA.ACME.COM 10 PROC(MONRUNM))

Sample configuration statements

This section documents a sample configuration member to illustrate a relatively complex TS-7700 configuration defining two geographically dispersed sites, with each site containing multiple clusters and grids. Note: This configuration file would be used for the PORTLAND site and allows remote access to the NYC site. A similar configuration file at the NYC site could be used to access the PORTLAND devices.

The following sample statements would typically be located in the DTS.R71.RULELIB(MONPOOLS) member, or the TSCONFIG member with an INCLUDE TSCONFIG statement added to MONPOOLS.

*
* DEFINE CLUSTERS AND GRIDS IN THE LOCAL SITE (PORTLAND)
*
DEFLIST CLSP1 ('MGMTCLAS(CLSP1)') TYPE(BVIR)
DEFLIST CLSP2 ('MGMTCLAS(CLSP2)') TYPE(BVIR)
DEFLIST CLSP3 ('MGMTCLAS(CLSP3)') TYPE(BVIR)
DEFLIST CLSP4 ('MGMTCLAS(CLSP4)') TYPE(BVIR)
DEFLIST GRIDP1 ('STORCLAS(GRIDP1)') TYPE(BVIR)
DEFLIST GRIDP2 ('STORCLAS(GRIDP2)') TYPE(BVIR)

*
* DEFINE CLUSTERS AND GRIDS USED AT THE NYC SITE
*
DEFLIST CLSNA ('MGMTCLAS(CLSNA) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST CLSNB ('MGMTCLAS(CLSNB) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST CLSNC ('MGMTCLAS(CLSNC) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST CLSND ('MGMTCLAS(CLSND) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST GRIDN1 ('STORCLAS(GRIDN1) SYSTEM(NYC)') TYPE(BVIR)
DEFLIST GRIDN2 ('STORCLAS(GRIDN2) SYSTEM(NYC)') TYPE(BVIR)

*
* DEFINE THE LISTS USED TO CONSOLIDATE DATA FROM MULTIPLE CLUSTERS AND GRIDS
*
DEFLIST GP1CLS (CLSPA,CLSPB) TYPE(BVIR)
DEFLIST GP2CLS (CLSPC,CLSPD) TYPE(BVIR)
DEFLIST GN1CLS (CLSNA,CLSNB) TYPE(BVIR)
DEFLIST GN2CLS (CLSNC,CLSND) TYPE(BVIR)
DEFLIST ALLPGRIDS (GRIDP1,GRIDP2) TYPE(BVIR)
DEFLIST ALLNGRIDS (GRIDN1,GRIDN2) TYPE(BVIR)
DEFLIST ALLGRIDS (GRIDP1,GRIDP2,GRIDN1,GRIDN2) TYPE(BVIR)

*
* DEFINE REMOTE CONNECTION TO NYC
*
DEFCONN NYC TCPIP(SYSA.ACME.COM 10 PROC(MONRUNM))