× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Don, can you copy from the /QNTC/... directory to one on your iSeries? That one could, I assume, be saved. You can copy a directory tree recursively in QShell with the cp command.

You might run into CCSID issues. The language setting for ifles in /QNTC don't always report their CCSID, in my experience. NT, IIRC, is 1252.

One drawback is the disk space used, even temporarily. You could walk the /QNTC

HTH

Vern

At 09:07 AM 10/13/2003 -0700, you wrote:
Our PC Server tech crew is having problems with their
Server backups and have asked if I could include their
data within our iSeries BRMS backup.

Our Integration with our PC Servers is through a 1 gig
ethernet Network. (though we are restricted to 100 mb)

Currently, the only way I came up with to do this is
to provide them a Share to an IFS directory, let them
copy their data to it, and include the IFS directory
in our backup.

I have netserver configured and running, so I can
access data from any PC server in the network. I was
hoping that perhaps I could assign my netserver
directories (i.e. '/qntc/PCServers') as an IFS
directory to our backups, but this did not work, at
least not within BRMS. It came back with an 'Object
not allowed' error.

Does anyone have an idea on how this could be done
cleaner & better than copying data to/from the IFS for
backups?

Thanks,
Don McIntyre



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.