|
Paul,it.
You can format a tape as ASCII and use it as a save on IBM i to AIX
and back. BRMS can handle those saves quite well. The return trip
would have to be native save/restore command since BRMS would not know
about he contents of those tapes.
Jim Oberholtzer
Agile Technology Architects
Office: 414-433-4363
Cell: 414-915-1445
Sent from iPad
"I've learned that courage is not the absence of fear, but the triumph
over it. The brave man is not he who does not feel afraid, but he who
conquers that fear". -- Nelson Mandela
On Jun 10, 2017, at 2:18 PM, PaulMmn <PaulMmn@xxxxxxxxxxxxx> wrote:don't think any other system can make any sense of them. Best thing
IBM SAVSYS/SAVOBJ/SAVLIB format tapes are unique to the iSeries. I
about them is being able to SAVLIB and RSTOBJ from the same save.
labels (the iSeries SAV* formats are saved on tape in standard format
Transferring data between systems you have to delve into standard
tape
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
with.EBCDIC to ASCII. Files without packed fields are the easiest to deal
Doing something with the file will most likely involve translating
--then SAVSAVFDTA and copy the contents of the SAVF to tape as if the
--Paul E Musselman
PS-- another neat thing about the IBM i is being able to save to a
SAVF,
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.
list
.
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 is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,questions.
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
link: http://amzn.to/2dEadiD
Help support midrange.com by shopping at amazon.com with our
affiliate
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.