Filter
Top Products
distributed servers. VSE, OS/390, TPF, AIX and others are discovering the
enormous value VM/ESA brings to the table.
DB2 Guest Sharing
With DB2, VM, VSE and OS/390 users can now share a DB2 database among
several VSE and/or OS/390 guests. For most customers, consolidating several
guest databases into one DB2 database reduces administrative work, simplifies
operation, increases data integrity, and improves performance. DB2 guest
sharing also streamlines access to operational data by decision support
personnel, who often use CMS-based tools. Furthermore, sharing one DB2
database gives VSE, OS/390 and VM applications access to remote data by way
of Distributed Relational Database Architecture (DRDA) support. Finally, the DB2
VM Data Spaces Support Feature offers even higher performance for users of
DB2 Version 3 Release 3 through ESA/390 architecture and VM/ESA Data
Spaces.
3990 Models 3 and 6 Fast Write Transparency
VM/ESA makes 3990 models 3 and 6 DASD Fast Write and Cache Fast Write
functions available to guests, such as some VSE releases which support
3380/3390s but not the 3990 models 3 and 6 Extended Functions. This allows
customers to benefit immediately from moving to the newer storage controllers.
Multiple 3270 Session Support
VM/VSE users often do several things simultaneously on different operating
systems. Operators can manage consoles for multiple guest virtual machines,
while programmers can move between CMS sessions and virtual test systems.
Not surprisingly, users want to be able to run several sessions at each terminal
simultaneously to simplify their work. VM/ESA Pass-Through Facility (PVM)
supports several concurrent sessions per user with the ability to switch from
session to session using a command or hot-key. This function is also available
for VM/OS/390 users.
26.3.3.4 Use of CMS
Lastly, it is worth considering the roll of CMS in the migration environment. CMS
along with XEDIT and the Shared File System (SFS) provide an excellent
environment for managing and modifying the many objects that will need to be
moved between the VSE system and OS/390 system. JCL members and other
source objects can be moved from the VSE environment and placed into a
hierarchical directory structure within SFS. These directories can be accessed by
multiple CMS users with complete data integrity ensured. Copies of directories
and their contents can easily be made to freeze modification levels for easy
backout. Modified objects can then be moved into the OS/390 environment and
placed into appropriate partitioned data sets. The CMS environment then
becomes the location where modifications are being made. This ensures that
nothing in the VSE environment is inadvertently changed wiping out the original
contents. In addition it provides a clearing house to quickly see what has been
moved to the OS/390 environment if it appears as though critical elements are
missing. Lastly, it provides a central location where both old and new copies can
be compared side-by-side for problem determination, and tools such as REXX
and CMS Pipelines to automate the management and comparison tasks.
Chapter 26. Test Environments 429