It isn't an exact thing.  lrecl stands for "Longest Record Length" and
nrecs stands for "Number of Records".  In this case, you can get a
worst-case number by simply multiplying lrecl by nrecs.  For instance,
 
  MYLIST        LOG9512         LOG OWN V      83   655 95/12/27 01:04:08
 
is <no larger than> 83*655 bytes, or 54365 bytes.  This is a legacy from
VM; I don't know if Eric is planning to rewire things so that the non-
VM systems report actual bytes or not.
 
On the other hand, Ben, in your case you can FTP to the server in question
and look at the contents of your directory and get exact byte counts.
The file in question is actually 31186 bytes.  So as you see, the lrecl*
nrecs formula isn't very exact.  :)  The rest of the files are, respectively,
 
LOG9601       59393 bytes
LOG9602       79415   "
LOG9603       77433   "
LOG9604       26331   "
 
Nathan