Virtual terminal pool sharing considerations
Virtual terminal pool (VTPOOL) defines the virtual terminal pool from which the virtual terminal manager VTM1 uses a virtual terminal for each OMEGAMON for Db2 Performance Expert session. Usually, each installation of VTM1 includes a VTPOOL definition. You can, however, also share a VTPOOL definition among several VTM1 installations.
Requirement:You can launch the OMPE Classic User Interface from the OMPE TSO or ISPF interface. To provide support for OMEGAMON for Db2 Performance Expert sessions under more than one TSO or ISPF, you must install VTM1 in every VTAM® domain that controls a TSO.
Sample network
For the VTPOOL sharing procedure that is described in this topic, it is assumed that the network looks like this:
In this example, there are two VTAM domains:
- Host Subarea A (HSAA)
- Host Subarea B (HSAB)
Host Subarea A runs OMEGAMON for Db2 Performance Expert and TSO (TSOA). Host Subarea B runs TSO (TSOB).
Assumptions are that:
- Users of OMEGAMON for Db2 Performance Expert who use ISPF or TSO mode must use the local TSO.
- A pool of ten virtual terminals is required for each host subarea.
This means that:
- Users whose terminals are controlled by VTAM domain HSAA must log on to TSOA.
- Users whose terminals are controlled by VTAM domain HSAB must log on to TSOB.
To share the VTPOOL definition, you must:
- Define the VTPOOL to VMT1.
- Define the VTPOOL to each VTAM.
- Provide access to VTPOOL.
Define the VTPOOL to VMT1
To define the VTPOOL of ten virtual terminals to VTM1, use this $VTAPPL statement:
$VTAPPL APPL#=10,VTAPPL=OBVTM1
Define the VTPOOL to each VTAM
To define the virtual terminals to each VTAM domain, define the local name and the network name separately.
Both names are defined in the VTAM APPL definition statement:
- The ACBNAME keyword defines the local name.
- The name field defines the network name.
In the following sample VTAM APPL definition statements, the HSAA network names are different from the HSAB network names. The local names for each virtual terminal are identical in both host subareas.
This example shows HSAA VTAM definition statements for Host Subarea A that correspond to the $VTAPPL definition statement.
HSAAVTM1 VBUILD TYPE=APPL
HSAAVT01 APPL ACBNAME=OBVTM101,EAS=1
HSAAVT02 APPL ACBNAME=OBVTM102,EAS=1
HSAAVT03 APPL ACBNAME=OBVTM103,EAS=1
HSAAVT04 APPL ACBNAME=OBVTM104,EAS=1
HSAAVT05 APPL ACBNAME=OBVTM105,EAS=1
HSAAVT06 APPL ACBNAME=OBVTM106,EAS=1
HSAAVT07 APPL ACBNAME=OBVTM107,EAS=1
HSAAVT08 APPL ACBNAME=OBVTM108,EAS=1
HSAAVT09 APPL ACBNAME=OBVTM109,EAS=1
HSAAVT10 APPL ACBNAME=OBVTM110,EAS=1
This example shows HSAB VTAM definition statements or Host Subarea B that correspond to the $VTAPPL definition statement.
HSABVTM1 VBUILD TYPE=APPL
HSABVT01 APPL ACBNAME=OBVTM101,EAS=1
HSABVT02 APPL ACBNAME=OBVTM102,EAS=1
HSABVT03 APPL ACBNAME=OBVTM103,EAS=1
HSABVT04 APPL ACBNAME=OBVTM104,EAS=1
HSABVT05 APPL ACBNAME=OBVTM105,EAS=1
HSABVT06 APPL ACBNAME=OBVTM106,EAS=1
HSABVT07 APPL ACBNAME=OBVTM107,EAS=1
HSABVT08 APPL ACBNAME=OBVTM108,EAS=1
HSABVT09 APPL ACBNAME=OBVTM109,EAS=1
HSABVT10 APPL ACBNAME=OBVTM110,EAS=1
Provide access to VTPOOL
To provide access to VTPOOL, you must:
- Assemble and link-edit the VTPOOL definition statements to produce the module
&shilev.TKANSAM(KOBVTPL).
VTM1 uses this module at runtime to select a virtual terminal prior to starting a OMEGAMON for Db2 Performance Expert session.
- Store the VTM1 execution-time modules including the link-edited module
&shilev.TKANSAM(KOBVTPL) in a library on DASD that is shared by TSOA and TSOB
users.
If this is not possible, you must use separate libraries with identical modules for both host subareas. You can, however, still perform VTPOOL maintenance from a single master library.
Modify VTPOOL definitions for TSO/ISPF mode
If you use TSO or ISPF mode and if your runtime environment does not share libraries with other runtime environments or with SMP/E, perform these steps:
- Define your virtual terminals and LOGMODE names to the VTM1 program by updating RKANSAM data set member KOBVTPL.
- Assemble and link the KOBVTL source by using the JCL in RKANSAM data set member KOBVTPLX.
The resulting load module KOBVTPL is stored in the RKANMOD data set.
- Update the following member and controls accordingly if you modified the terminal names or the
number of terminals:
- VTAM node list member KOBVT1AP in the RKANSAM data set
- VTAMLIST controls