HP3000-L Archives

July 2004, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Brandt <[log in to unmask]>
Reply To:
Tom Brandt <[log in to unmask]>
Date:
Thu, 22 Jul 2004 15:10:56 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
I emailed Walt privately on this, but you can specify the file attributes
on the put command when you ftp from a non-MPE client to an MPE server:

 >put MYSTORE MYSTORE;REC=128,1,F,BINARY;CODE=2501


At 02:59 PM 7/22/2004, John Clogg wrote:
>The file has to be built with a file code of 2501.  If you FTP directly
>from one MPE machine to another, the file code and other file attributes
>will be preserved.  With using a non-MPE machine as an intermediary, you
>lose that info.  If you have MPEX on the receiving machine, you can alter
>the file code of the file:
>  ALTFILE MYSTORE;CODE=2501
>
>If you don't have mpex, try this:
>  FILE MYSTOR2;CODE=2501
>  FCOPY FROM=MYSTORE;TO=*MYSTOR2;NEW
>
>This will copy the store file into a new file that has the correct file
>code. Another method is to initiate the second FTP transfer from the MPE
>machine, since MPE's FTP client allows you to specify file attributes on
>the GET command:
>  GET MYSTORE;CODE=2501
>
>This method is also useful if any other file attributes, such as record
>length, are not being accurately duplicated.

--
Tom Brandt
Northtech Systems, Inc.
130 S. 1st Street, Suite 220
Ann Arbor, MI 48104-1343
http://www.northtech.com/

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

ATOM RSS1 RSS2