× 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.



On the same VTL the tapes would not have to be shifted. For example, in
Garrett, with 10 lpars on the same VTL we could save on GDIHQ (prod) and
restore on to GDISYS (dev) by running this command:

RSTLIBBRM SAVLIB(ERPLXF) DEV(GRRTVTL) SAVLVL(*CURRENT) MBROPT(*ALL)
ALWOBJDIF(*ALL) FROMSYS(GDIHQ)

if you have three saves of ERPLXF, all done on GDIHQ it will know to use
the most current save by the SAVLVL(*CURRENT)

Here it would be a little different though. We normally do our saves in
Kendallville on the Mimix replicas. So a save done on GDIHQ2 would be
restored to GDISYS2. The only trick being that normally Mimix replicates
from GDISYS to GDISYS2 so you would have to handle that.
I believe we often shutdown that part of Mimix during such a 'refresh' to
avoid really flooding the journals. Darren (also on this list) normally
handles our refreshing.

The only shifting would be if one just insisted on the save on GDIHQ2 in
Kendallville being restored on to GDISYS in Garrett.

Now, this may be able to be done via scripting. I'm more used to using
the GUI interface of the library but the die hards who connect in remotely
to assist us use the Command Line Interface. There are a few occasions in
which I've noticed some different behavior based on whether or not one
used the GUI or the CLI to perform the task. I do think if more of the
diehards used the GUI then it would have some more of these differences
ironed out.

Rob Berendt

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.