Migrating from a test to a production environment
Under this migration scenario, copying MainView Alternate Access from one system to another system involves the following steps:
- Copy your test-system target libraries to your production-system target libraries.
The libraries are:
For information about specific load modules that are associated with MainView Alternate Access, see Load modules, libraries, and sample members.
- Copy UBBSAMP member BBVINIT and the MainView CLIST (default name MainView) to a UBBSAMP library on your production system, naming the new member BBVINIT.
See Load modules, libraries, and sample members for information about other UBBSAMP members.
- Copy the following UBBPARM members on your test system to a UBBPARM library on your production system:
BBVTASxx where xx is a unique identifier.
- Copy the BBVTAS and BBVLAS (if needed) procs from your test-system procedure library to your production-system procedure library.
Copy the VTAM application major node name from your test system to your production system.
If your test system and production system share the VTAMLST data set where the VTAM application major node resides and you want to run MainView Alternate Access concurrently on both systems, you must define a different major node definition (see Step 2: (optional) Defining the VTAM major and minor nodes) and TAS parameter list members (see Step 5: Defining a default TAS initialization parameter list).You also might need to define a different BBVLAS proc and parameter list member, depending on your site requirements for user logons from VTAM terminals (see Step 7: (optional) Defining a default LAS initialization parameter list and Step 8: (optional) Defining a LAS startup procedure).
- Determine whether you need to update the USS table or logon interpret table on your production system; see Step 3: (optional) Defining a USS table entry or Step 4: (optional) Defining logon interpret table entries for more information.