×
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.
IBM SAVSYS/SAVOBJ/SAVLIB format tapes are unique to the iSeries. I
don't think any other system can make any sense of them. Best thing
about them is being able to SAVLIB and RSTOBJ from the same save.
Transferring data between systems you have to delve into standard
tape labels (the iSeries SAV* formats are saved on tape in standard
format with standard labels, but within that standard file is IBM's
unique save structure). This means you have to use a CPYF to a tape
device file. The system at the other end can read the file and do
something with it.
Doing something with the file will most likely involve translating
EBCDIC to ASCII. Files without packed fields are the easiest to deal
with.
--Paul E Musselman
PS-- another neat thing about the IBM i is being able to save to a
SAVF, then SAVSAVFDTA and copy the contents of the SAVF to tape as if
the backup had originally been to tape! Due to some of the errors
you can get with a SAVF I've always felt that a SAVF was pretty much
a virtual tape device, and that SAVSAVFDTA was pretty much a straight
copy.
.
At 11:55 AM -0400 6/10/17, Jack Kingsley wrote:
Has anyone converted platforms and had much luck integrating the current
BRMS tapes with some other platform, lets say LINUX.
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.
midrange.com
