|
I've experienced similar problems with our remote journaling environment.
After hours of time on the phone with IBM, we were never able to come up
with a definitive answer to what was going on either.
Your solution to restart the remote journaling process is probably the best
you can do...
My solution was to create a process that would wake up every few hours and
check to see if remote journaling was active. I did this by trying to start
it again. If it wasn't active, this restart attempt would take care of the
problem. If the restart didn't work, the problem usually was associated with
the remote side so I would submit a remote command resetting the remote side
and then try starting it again.
This solution has worked very well for me. I used the IBM advanced job
scheduler (IJS) to schedule this job to run every 2 hours. IJS executes this
program with the *RESTART parameter first. If I encounter any major error,
the program ABENDs. IJS then automatically executes the program again with
the *SHUTDOWN parameter followed by another execution with the *RESTART
parameter. IJS also initiates a pager message indicating there was a problem
with remote journaling. 99% of the time this process fixes the problem.
This may sound a bit confusing so, I've attached a copy of my program for
you to take a look at too.
Notes: My program example maintains a remote journaling environment for
several journals, not just one and the name of our remote system is S17. ==================================
MORE INFORMATION ON THIS TOPIC
==================================
Ask the Experts yourself: Our Backup & Recovery gurus are waiting to answer your questions.
Search400's targeted search engine: Get relevant information on backup & recovery.
Check out this search400 Featured Topic on backup & Recovery.
|
