You're going to need to make a decision on the IFS. Either you:
A - add some omits for the worrisome objects
B - slap a MONMSG on it and ignore these messages in your joblog
C - End the offending locks.
D - forget the MONMSG and let the backup blow up.
Some people use B with the idea that they can then make a conscientious
decision when messages occur whether to pursue A or C. Like if some new
application comes along that starts locking stuff.
Using option D forces you to make a more rapid decision for A or C.
However, it tends to honk off the BOFH.
Ending stuff may involve
ENDTCPSVR *HTTP ...
or
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.iseries.doc/info/iseries/ae/txml_command.html
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.iseries.doc/info/iseries/ae/tadm_startstop.html
BOFH
http://tinyurl.com/3d2qf7
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.