HP3000-L Archives

September 2005, Week 5

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:
Re: Testing Multi reel store-to-disc
From:
Greg Terterian <[log in to unmask]>
Reply To:
[log in to unmask]
Date:
Thu, 29 Sep 2005 11:50:34 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines) 
<<Once the file is on the Windows server, I found that making (or  creating
from BLDSAMP.ARPA.SYS) the BLDPARMS file (BLDPARMS.ARPA.SYS) with  the
following modification (change the default value for binary files  from)

;REC=-80,,F,ASCII;DISC=204800
;REC=128,,F,BINARY;DISC=204800
;REC=,,B;DISC=16384000

to

;REC=-80,,F,ASCII;DISC=204800
;REC=128,,F,BINARY;DISC=16776959
;REC=,,B;DISC=16384000

This  did the trick for as it insures that the file being ftp'd back to the
3000 is  created with the correct limit. However, by upping the value on the
default  bldparms record for binary, I am also affecting ALL binary files
that  transferred to the 3000.
 
Isn't it true that you can do a file equation like  "FILE 
BLDPARMS.ARPA.SYS=MYPARMS and have MYPARMS modified only?  This way  all the binary files 
received outside of your job will use regular BLDPARMS  file.
 
 
 This has not caused a problem for me as this
is just the limit and  I believe does not 'waste' space.>>


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

ATOM RSS1 RSS2