From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 14-JUN-1989 16:22 To: MRGATE::"ARISIA::EVERHART" Subj: Re: ZOO Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Wed, 14 JUN 89 11:59:29 PDT Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Wed, 14 Jun 89 11:36:02 PDT Received: by ucbvax.Berkeley.EDU (5.61/1.36) id AA07669; Wed, 14 Jun 89 10:52:13 -0700 Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-vax@kl.sri.com (info-vax@kl.sri.com) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 14 Jun 89 16:32:16 GMT From: beta!dxxb@lanl.gov (David W. Barts) Organization: BCS Richland, Inc. Subject: Re: ZOO Message-Id: <26276@beta.lanl.gov> References: <1113@vaxb.acs.unt.edu>, <1160@vaxb.acs.unt.edu> Sender: info-vax-request@kl.sri.com To: info-vax@kl.sri.com In article <1160@vaxb.acs.unt.edu>, james@vaxb.acs.unt.edu (James Shoffit) writes: -> Dominick Samperi writes: -> -> > |>It is easy enough to make ZOO work better under VAX/VMS with respect -> > |>to interactions with KERMIT, etc. Just change the fopen calls -> > |>to have options as I suggested in previous messages for binary files. -> > |>Force record access and create a fixed-length 512 byte record file. -> > |>No Big deal. -> > -> > This might have been the best solution before VMS introduced STREAM -> > (not STREAM_LF!) files. Using 512-byte fixed-length records forces the -> > programmer to do I/O in 512-byte blocks (writing a partial block fails), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Last time I tried it, I did something like fopen("foo.bar", "w" "rfm=fix, mrs=512"); Whenever I failed to fwrite() a multiple of 512 bytes before doing an fclose(), the file was automatically padded with zeroes on closing. If you're using open/read/write/close instead of fopen/fread/fwrite/fclose, change it. The former family of calls is NOT part of ANSI C, the latter is. David W. Barts, Ph. 509-376-1718 (FTS 444-1718), dxxb@beta.lanl.GOV