Default language.

Migrating from a test to a production environment

The following information assumes that your test system and production system have identical BMC product mixes and that you typically migrate products by copying your test target libraries to your production target libraries.

Related topic

Customizing-Alternate-Access

Under this migration scenario, copying 

Alternate Access

 from one system to another system involves the following steps:

  1. Copy your test-system target libraries to your production-system target libraries.The libraries are:

    • BBCLIB
    • BBLINK
    • BBPLIB

    For information about specific load modules that are associated with Alternate Access, see Load-modules-libraries-and-sample-members.

  2. Copy UBBSAMP member BBVINIT and the BMC AMI Ops CLIST 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.

  3. Copy the following UBBPARM members on your test system to a UBBPARM library on your production system:
    • BBVLASxx
    • BBVTASxx where xx is a unique identifier.

  4. Copy the BBVTAS and BBVLAS (if needed) procs from your test-system procedure library to your production-system procedure library.

  5. Copy the VTAM application major node name from your test system to your production system.

    Important

    If your test system and production system share the VTAMLST data set where the VTAM application major node resides and you want to run 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).

  6. 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.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*