z/OS Communications Server: CMIP Services and Topology Agent Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Overview

z/OS Communications Server: CMIP Services and Topology Agent Guide
SC27-3646-00

This section describes the action that is used to request monitoring and stop monitoring LU data for a given PU object or agent host object using the luCollection managed object class.

Management of LUs requires that a manager application program be able to request the names of all the LUs under a certain PU and to monitor their status. The manager application program can use a snapshot action request against the luCollection object to get LU information.

The VTAM® agent supports two types of luCollection

  1. luCollection against a specified physical unit. This form of luCollection is called luCollection (PU) and returns all dependent LUs that are defined (either statically or dynamically) under the PU. The physical unit must be defined at the agent host for this command to be successful. For physical units that represent connections to type 2.1 nodes, the independent logical units currently using the PU as an adjacent link station (ALS) for sessions are also reported on the luCollection snapshot response.
  2. luCollection against the agent host. This form of luCollection which does not specify a linkName in the luCollection distinguished name is called luCollection (Host) and returns LU resources that are associated with the VTAM agent host. This includes:
    • Application programs
    • CDRSCs
    • USERVARs
    • Generic resources
    • Local non-SNA terminals
The reporting of all CDRSCs for luCollection (Host) can generate large amounts of data to be processed because dynamic real CDRSCs as well as predefined CDRSCs can be reported. With the exception of low-entry networking (LEN) independent LUs, these CDRSCs can offer little benefit in terms of managing the network because they represent resources that could be reported by agents at the nodes that own the real resources represented by the CDRSCs. However, these CDRSCs might be of interest in some environments. The user can select which types of CDRSCs are to be included in the luCollection (Host) object reported by the VTAM topology agent by specifying one of the following values on the OSITOPO start option:
  • ILUCDRSC: Report independent LUs only. This is the default value if not specified.
  • ALLCDRSC: Report all CDRSCs, including independent LUs.
Note: This start option does not affect the reporting of independent LUs under luCollection (PU).

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014