Thank you all for your input.  I believe I misunderstood the file requirements and I won't be using tar.

Since we pay for Allegro support the wonderful Mrs. Hofmeister will be guiding me.  She's also
way more technically savvy  me.

Ernie
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Lars Appel
Sent: Wednesday, July 25, 2012 2:32 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Tar question

Michael Anderson wrote:
> I agree, without a doubt you are correct. However, I think the
> original post was referring to one MPE file type "code=2501 aka
> STORE", and again the major issue is size.

Ah, thanks for the comment. Looks like I misread the original post.

When the backup is done using store-to-disk, then a plain binary ftp should be sufficient for moving those files to remote storage. As far as I recall, recent RESTORE versions do not insist on the file code.

On the other hand, if required, it could be re-added when pulling the store-to-disk file back to the HP 3000 with ftp get. I seem to recall that FTP/iX allows the target filename to be appended with build parms like ;CODE=2501 or ;REC=128,,F,BINARY or ;DISC=xyz for example.

Regards, Lars.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

________________________________

This message, including any attachments, is intended solely for the use of the named recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution of this communication(s) is expressly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy any and all copies of the original message.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *