Note: For additional information about Purge and Archive please consult the Data Thread Administrator’s Guide.
Note: After normal business hours, contact technical support for a temporary key.
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.
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.
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.
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.
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.
De-activate all monitored files (2 options to do this).
Note: Ensure Data Thread is in your LIBL (ADDLIBLE DATATHREAD)
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.
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:
ENDSBS DATATHREAD *IMMED
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.
SAVLIB LIB(DATATHREAD) DEV(*SAVF) SAVF(QGPL/DTSAVF)
PUT QGPL/DTSAVF QGPL/DTSAVF
RSTLIB SAVLIB(DATATHREAD) DEV(*SAVF) SAVF(QGPL/DTSAVF) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(DATATHREAD)
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:
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.
Note: make sure Data Thread is in your LIBL ( ADDLIBLE DATATHREAD )
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.
Still have questions? We can help. Submit a case to Technical Support.