Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!sloane
From: sloane@kuhub.cc.ukans.edu (Bob Sloane)
Newsgroups: news.software.anu-news
Subject: Re: Why are 33 blocks allocated for an .ITM file?
Message-ID: <22350.25e55442@kuhub.cc.ukans.edu>
Date: 23 Feb 90 21:18:25 GMT
References: <3.25e3a98b@ubvms.cc.buffalo.edu>
Organization: University of Kansas Academic Computing Services
Lines: 19

In article <3.25e3a98b@ubvms.cc.buffalo.edu>, newsmgr@ubvms.cc.buffalo.edu
 (Jim Gerland - Manager, User Support Services) writes:
> Can someone tell me why NEWS allocates 33 blocks for almost all of the
> ITM files even if they are only 2 blocks (2/33)?  This is not consistant.
> 
> If this is not necessary, can someone tell me how to change this?

Hmmm.  I am running V5.9C and I can't seem to find an 2/33 block .ITM
files.  What version are you running?  I know that the .BATCH files
created by the NNTP server (WIN) are created 33 blocks long. Is that
what you are talking about?  Other than that, I would tend to suspect
some of the device/RMS settings at your site. I don't suppose the
device as a cluster factor of 33?  Or perhaps some of the system
default RMS allocation quantity stuff is causing this?  Other than
that, I would look for fopen() calls in the source and see if any are
specifying the optional RMS parameters.
-- 
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane@kuhub.cc.ukans.edu, sloane@ukanvax.bitnet, AT&T: (913)864-0444