Upgrading UPSTREAM to a Newer Version

After unloading the distribution libraries, creating the new UPSTREAM installation data sets and testing of a new version is complete, it can be easily placed into full production and set up to use the existing configuration and repository data sets:

1. If the Started Task PROC distributed with the new release is not changed from the old, make a new copy of your Started Task PROC and edit the STEPLIB reflecting the new UPSTREAM program library name/loadlib. You can, and should, use you existing control files. The old library (and PROC) should be saved for a quick and easy fall-back, if required.
2. Either take a current USTREORG of each of the control files and note the backup file created as part of the USTREORG, or take a DUMPX (the backup portion of the USTREORG), saving the backup files created.
3. Bring down the old UPSTREAM and using the new started task PROC created above, bring up UPSTREAM with the new loadlib.
4. Once UPSTREAM is started using the new loadlib, browse the started task logs (JESMSGLG and USTLOG DD statements) for any errors starting up. If you wish, performing a USTREORG or DUMPX for each of the control files verifies the integrity of the control files that have been migrated from the prior version. Performing a backup (writes to the control files and the backup data set), restore (reads from the control files and the backup data set) and any other UPSTREAM functions you use regularly will exercise the product.
5. Once you are satisfied that the new UPSTREAM is performing as expected, rename your production started task PROC to a save version and rename the PROC created in step 1 to your production name.
6. Change the STEPLIB in any USTBATCH job streams and other UPSTREAM batch jobs to refer to the new UPSTREAM program library.
7. The ISPF dialogs can be updated by renaming the new libraries to match the names of the existing production UPSTREAM ISPF libraries (saving the original libraries under another name for any potential fall-back). Alternatively, update your TSO logon procs to reflect the new ISPF panels, clist, messages, skeleton, and tables data sets.
8. Once the new version has been running successfully for a time, the libraries from the old version can be deleted.