Step I – Planning a Data Thread 3.x Move
- Data Thread 3.x Installation. For best results, before the move, Data Thread must already be installed on the ‘destination’ system so the user profile, SBSD (subsystem description), job queue, and CLS (class of service) are installed properly.
- The Data Thread Application Preparation. Before moving to the new system, the basic functions within Data Thread should be tested on the ‘source’ system to ensure the data and historical information is not corrupt and is ready to be used on the destination system after the move.
- Data Queues. Data Thread stores historical data from monitored files using data queues. Data is moved from the data queues to the Data Thread data ‘vault’ in the form of database files. These queues must not contain data at the time of migration, to avoid data corruption.
- Monitored files. All monitored files (Option 11) must be de-activated and the Subsystem (DATATHREAD) must be shut down prior to copying the Data Thread library to a SAVF in preparation for the move. Once they are de-activated, some time should be given before shutting down the Data Thread Subsystem in order to allow the monitor job(s) to clear out all of the data queues.
- Database files holding the historical data. Although it is permissible to move the historical data to a different system, it is recommended that these database files are trimmed prior to the migration, using the ‘Purge and Archive’ procedure available within Data Thread.
Note: For additional information about Purge and Archive please consult the Data Thread Administrator’s Guide.
- License Key. Obtain a license key for the new system from the Powertech Sales team.
Note: After normal business hours, contact technical support for a temporary key.
Step II – Install Data Thread R03MXX
To successfully move Data Thread from one system to another (i.e. D/R system), you must first install Data Thread on the destination system using the software installer.
The installer creates the required user profile, SBSD, CLS, and job queue for Data Thread.
- Data Thread has one profile: DATATHREAD.
- Data Thread has one job queue: QUSRSYS/DTJOBQ.
- Data Thread has one SBSD: QUSRSYS/DATATHREAD
- Data Thread has one CLS: QUSRSYS/DATATHREAD
Note: If the user profile, CLS, SBSD, or job queue exists, installation will fail. If installation fails, delete this user profile and/or CLS, SBSD, job queue, and try the installation again.
Step III – Data Thread Journal and Replication
Data Thread has one journal, DTJOURNAL, which is used when journaling is configured within Data Thread (Option 11) for monitoring files. This Option is turned on by selecting ‘D’ for the action selected. Refer to Data Thread Setup in an HA Environment for more information.
Step IV – Data Thread Files to Move
All files within the Data Thread library will be saved to a SAVF file and then copied to the ‘destination’ system and restored after the Data Thread application has been installed and the library has been cleared.
Step VI – License Objects
Data Thread 3.07, or later, has the ability to enter multiple licenses (press F7 – License List on License Setup screen). If multiple licenses have been entered and a license is included for the new system, the DATATHREAD/PDT9800U and DATATHREAD/PDT9800U2 user spaces will be copied with the SAVF file and restored on the new system.
Step VII has the commands to use to save and restore the files, index and the license object to the new system.
Step VII – Move Data Thread Commands
De-activate all monitored files (2 options to do this).
- In Option 11 from within Data Thread, enter “29” next to all of the files that are currently activated (they will be highlighted in white).
- If there are many files activated, you can submit the following command to de-activate all files:
Note: Ensure Data Thread is in your LIBL (ADDLIBLE DATATHREAD)
- Submit the command:
CALL IDT465 PARM(‘0’ ‘*ALL’ ‘ ‘)
Note: Ensure ALL files have been de-activated by navigating to Option 11 from within Data Thread and checking to make sure all monitored files are presently colored yellow, indicating that they are not activated.
After all the data queues are empty, shut down the subsystem. The subsystem monitor job IDT450 is the job that cleans out the data queues and moves the data to the database files and should be running.
To check the data queues for data submit the command:
CALL DQVIEW SLAW (press ENTER twice to view)
This will list the data queues and show if there is any data in them. Example:
In this example the data queues are empty and it is now safe to stop all the monitor jobs and shut down the Data Thread subsystem. Hit F12 to exit DQVIEW.
Note: If there is any data in any of the data queues please allow the IDT450 monitor job/s to run until the data queues are empty.
- Next, shut down the monitor jobs under the Data Thread subsystem. There are two ways to do this:
a. From option 17 within Data Thread, submit the command ENDALL.
b. With Data Thread in the LIBL, from the command line, submit the following command:
- To end the Data Thread subsystem from the command line submit the following command:
ENDSBS DATATHREAD *IMMED
- Once the subsystem has been shut down:
a. Copy the Data Thread library on the ‘source’ system to a SAVF file.
b. FTP the SAVF file to the ‘destination’ system.
c. Clear the library that was created from the installation.
d. Restore the library from the SAVF file.
On the source system submit the commands:
- Create the SAVF file:
- Save the Data Thread library to the SAVF file:
SAVLIB LIB(DATATHREAD) DEV(*SAVF) SAVF(QGPL/DTSAVF)
On the destination system submit the commands:
- Create the SAVF file:
- FTP the SAVF file to the destination system. Submit the commands (from the ‘source’ system):
FTP <destination server name>
- Sign on with your Username and Password.
- Enter BIN for a Binary Transfer:
- Transfer the file using the ‘PUT’ command:
PUT QGPL/DTSAVF QGPL/DTSAVF
- Install Data Thread.
- Once the installation is complete, clear the library in preparation for restoring the library that was saved and FTP’d from the source system.
- Submit the command to clear the library:
- Next, submit the following command to restore the library from the SAVF file:
RSTLIB SAVLIB(DATATHREAD) DEV(*SAVF) SAVF(QGPL/DTSAVF) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(DATATHREAD)
- Once the restore is complete, submit the command to go into Data Thread, navigate to the license key configuration screen, and install the new license key. Submit the command:
- Take option 18 and insert the new license key for this system.
Step VIII – Restart the Data Thread Subsystem and monitor jobs for Data Thread on the destination system
- After the license key has been successfully entered, start the Data Thread Subsystem and monitor jobs with the following commands.
- Next, start the monitor jobs under the Data Thread Subsystem using 1 of 2 options:
a. From the command line submit the command:
b. From Option 17 in Data Thread submit the command STRMGR.
The following ‘minimum’ list of monitor jobs should now start under the Data Thread Subsystem
List the Subsystem details:
List of minimum jobs that should have started:
Step IX – Data Thread Monitored File Activation on the New (Destination) System
After the license key has been entered, the Subsystem and the monitor jobs started, the monitored files that were de-activated can be re-activated.
- Re-activate all monitored files (2 ways to do this).
- In Option 11 from within Data Thread place 22 next to all of the files that are currently de-activated ( they will be highlighted in yellow ).
- If there are a lot of files de-activated you can submit the following command to re-activate them all from a single command.
Note: make sure Data Thread is in your LIBL ( ADDLIBLE DATATHREAD )
- Submit the command:
CALL IDT465 PARM(‘1’ ‘*ALL’ ‘ ‘)
Note: Using the command CALL IDT465 to re-activate the files will actually re-activate the files that were de-activated previously automatically.
Note: Please check to ensure ALL appropriate files have been activated by navigating to Option 11 from within Data Thread and check to make sure all appropriate monitored files are presently colored white, indicating they have been activated successfully.