Changes Not Being Captured |
Scroll |
One of the most common problems likely to be encountered is that changed data is not being captured after configuring a data capture agent.
First, confirm that all of the environment preparation, component configuration and component verification activities have been completed successfully for the IMS Log Reader Capture agent.
If after confirming the configuration What to do next depends on which IMS Capture has been implemented
Next, verify that:
1.The IMS DBD's containing the segments to be captured have been modified with the EXIT Keyword to ensure IMS writes the type "99" records IMS Log required by the IMS Log Capture, see Modify IMS DBD's for Capture.
2.While IMS is running, start the capture.
3.Display capture statistics. This can be done via SQDCONF display or by "F <taskname>,DISPLAY" MVS command. The former will send the display to the SQDCONF job, the latter will write the display to the SYSPRINT data set in the capture task.
4.Create activity on databases that have type 99 records turned on. There must be enough IMS activity or workload to push data out of the WADS.
5.Display capture statistics again and see if Last Record LSN, Last Pushed LSN, or Safe Restart Point have changed.
6./SWITCH OLDS.
7.Create some more activity. Or issue a checkpoint.
8.Display again and so we can check the LSNs and in particular the SQDF981I Safe Restart Point.
If you are still not able to capture changed data, contact Precisely https://www.precisely.com/support for assistance.