Testing and Implementing a New Production Version

A new production (i.e. non-trial) version of UPSTREAM can be tested while an existing version continues to be used for full production. To insure that the two instances of UPSTREAM do not interfere with each other:

• Load the new UPSTREAM libraries from the distribution media (Authorize the FDR/UPSTREAM Load Library or Upgrading-and-Replacing-a-Trial-Version and Installation ISPF Dialog) being sure to specify library names different from those used in production.
• Create a new configuration data set and repository data sets for testing:
• Define the “CONFIG” Configuration File
• Define the “CATALOG” Repository Data Set
• Define the “FILEINFO” Repository Data Set
• Define the VTAM application major node (Define Optional VTAM System Resources)
• Assign a TCP/IP port number different from the one used by production (Define an OMVS Segment for the FDR/UPSTREAM Started Task Userid).
• Copy the UPSTREAM startup PROC to your procedure library under a different name (e.g., USTTEST) updating it to point to the test data sets. Your existing startup options may be used (if any). If using the UPSTREAM Scheduler, change the reference from your production to your test UPSTREAM.
• Configure the MAIN options, ISPF panel 4, Configure the MAIN Options updating the SUBSYS and TCPPORT parameters.
• While testing the new ISPF dialogs, the USTALLOC procedure shown at the beginning of (Start the FDR/UPSTREAM ISPF Interface can be used to invoke them.
• Set the required parameters in the test configuration (see Chapter 4 “FDR/UPSTREAM Profiles”). The test backup profiles should have names different from those used for production and should create different backup data set names (DASDPREF= and TAPEPREF=).