To define a TWS request that
TWS Automation can use, a workstation representing the
target NetView domain is required.
This workstation, which is defined with TWS using the standard TWS dialogs, should be a general, automatic
reporting workstation. Its name must have the format
NVxx
Notes:
Reserve NVxx workstations for TWS Automation. Unpredictable
and undesirable results may occur if these workstation names are used
for other workstations.
If using automation workstations, the workstation destination
name can contain the NetView domain
ID. If it does not, the workstation name is mapped to the NetView domain
ID.
Figure 1 shows a typical
definition. Figure 1. Sample NVxx Workstation
Definition in TWS
--------------------- BROWSING A WORK STATION DESCRIPTION ---------------------
Command ===>
Enter the command R for resources , A for availability or M for access method
above.
Work station : NV01
Description : SA WS on SAT1
Work station type : General
Reporting attribute : Automatic
FT Work station : No
Printout routing : SYSPRINT
Server usage : Planning
Destination :
Splittable : No Job setup : No
Started task STC : No WTO : No
AUTOMATION : No
WAIT : No
Transport time : 00.00
Duration :
Last updated by : SAUSER on 07/12/06 at 15.07
Entries in the SA z/OS policy database
(WORKSTATION DOMAINS policy object, entry type ODM) translate NVxx to an
actual NetView domain ID. The automation
administrator defines these entries. In this manner, the scheduler defining the TWS applications does not need to know the
NetView domain ID names, but rather works with
the workstation representation of those names. This allows changes to the relationship of
workstations to NetView domain IDs without
modifying the TWS definitions.
Note: You may use TWS database
management dialogs or batch loader jobs to define the NVxx workstations.