Minisoft 92 does not support file codes at this time.

Window's ftp supports use of 'buildparms' on sends / puts; no other
'client' product is actually necessary for this. Probably most anyone
else's ftp does this as well; this is a standard capability whose use
varies from target system to target system. There was a thread last
Friday involving ftp between a Vax and a 3K that may interest you. The
Vax's ftp did not like the commas in the REC buildparm, but these are
avoidable, as ftp has modes for ASCII, which defaults to fixed, and
BINARY, which defaults to variable, if you can live with these defaults,
and can live without blkfactor.

The syntax is:
ftp> PUT localfile remotefile;buildparms

From the HP ARPA File Transfer Protocol User's Guide, Ch 5 Using the FTP
Server, More Information About FTP and MPE XL:

When transferring files from your system to MPE XL, you can use
file-building parameters following the PUT command string:
ftp> PUT   localfile  remotefile; buildparms

The supported build parameters are:
 ;REC=[-recsizebytes][,blkfactor[,[{F}][,{BINARY}] ] ] ]
                               {V}   {ASCII}
 [;DEV= device]
 [;CODE= filecode]
 [;DISC=[ numrec][,[ numextents][,[ initialloc] ] ]

I will be happy to answer other questions you may have. BTW, why are you
asking about this?

--------
>Chuck Duncan. <[log in to unmask]> wrote in article
><[log in to unmask]>...
>> Frank,
>>
>> With Reflection 1 for Winsows 95/NT, I transfer files with labels to my
>PC
>> using the ;label option on the Host file name [transfer type labels may
>also
>> work].  Besides keeping all the information necessary to build the file
>when
>> transfered back to the HP, it also preserves the file labels.   Does
>MS-92
>> have a similar option?
>>
>> Chuck Duncan
>> [log in to unmask]
>>
>