Submit SBJTSAMP members to reformat the copy of your current database

SBJTSAMP members that were configured in the previous steps are submitted to unload the old database, load the new copy of the database, and then reformat the new Output Manager V3R1 tables.

1. In HLQ.OLDDB.SBJTSAMP, submit these jobs in the following order (note that each job must complete successfully before submitting the next job in the sequence):
   1. If required by your Db2® site security policies, submit BJT@JCGU to grant CREATE on the collections created by running BJT@JCBU.
   2. BJT@JCBU (binds utility plans), must end in RC = 0.
   3. BJT@JCUO (unload the old database). All steps must end with RC = 0, with the exception of RSSPACE, which can end in RC = 4. Steps RSSTERM and UNLDTERM should FLUSH.
      Note: If this is a trial run of the migration, change ACCESS(RO) to ACCESS(RW) in step DBRW so that you can continue to capture sysouts in the original database. When you are ready to switch to V3R1 for production, make sure the current database is set to RO (read only).
   4. Submit BJT@JCFO to free the plans created by BJT@JCBU. These plans are only needed to run BJT@JCUO.
2. In HLQ.BJT@310.SBJTSAMP, submit these jobs in the following order (note that each job must complete successfully before submitting the next job in the sequence):
   1. BJT@JCLO (loads the new database, and applies updates to convert the data to a state where it can be loaded into the V3R1 database.) The JOBLIB contains a commented DD card for the SBJTLPA library. Uncomment the DD card if the Output Manager LPA modules were not added to the LPA. All steps must end with RC = 0, with the exception of LOAD, RSSPACE, and SQNMx, which can end in RC = 4. Steps LOADTERM and RSSTERM should FLUSH.
      Tip: If you encounter errors when running BJT@JCLO, you need to run BJT@JCDO before you can re-run BJT@JCLO. BJT@JCDO drops the database that was created by running BJT@JCLO.
   2. BJT@JCUL (unloads the altered database built by BJT@JCLO). All steps must end with RC = 0, with the exception of RSSPACE, which can end in RC = 4. Steps RSSTERM and UNLDTERM should FLUSH.
   3. BJT@JCDR (drops the database), must end in RC = 0.
   4. BJT@JCLD (reloads all of the current database data into the new database, using the V3R1 database object definitions). All steps must end with RC = 0, with the exception of step LOAD, which can end in RC = 4. Steps LOADTERM, COPYTERM, and REORGTRM should FLUSH.
      Tip: If you encounter errors when running BJT@JCLD, you need to run BJT@JCDR before you can re-run BJT@JCLD. BJT@JCDR drops the database that was created by running BJT@JCLD.