|
Part of our nightly saves performs the following: Sav dev(. . . . ..DEVD') obj(('/*') ('QYSlLIB' *Omit) ('/QDLS' *Omit)) Looking at the joblog, it seems that this command is also going out and touching other servers and will occassionally return CPDB050 reason 110. The name referred to in the message is another server on the network. I assume this is all due to the QNTC file system -- but why is the Sav going outside the AS/400? I assume that it's trying to touch every server in our domain. Why? I did a '5' on the QNTC link via WrkLnk and it's taking quite a while to return information. It's also kicking out the CPDB050 messages as well. I'm wanting to see whether there are some links set up that I don't want. How do I get the Sav command to "stay at home" and not go out to the network? Is it as easy as *Omit on QNTC? Bill
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.