Leonard

Given the reported block size, the file occupies 4076 full blocks and one
partial block.
MPEXs reported record number is the blocking factor time 4077. It may be
that MPEX 'guesses'
on the record number by looking at the block number and multiplying by the
blocking factor.



At 09:05 AM 7/7/00, Leonard S. Berkowitz wrote:
>Here is today's strange happening. In MPEX, the record number being read is
>beyond the EOF. I would understand that this could happen while writing -- the
>new EOF has not been posted -- but on a read. Is this due to the method of
>reading files in 4k words?
>
>ACCOUNT=  AMISYS      GROUP=  PUB
>
>FILENAME ---TYPE--- JOBNUM PIN ---------PROGRAM--------- ACCESS  RECORD -LOCK-
>
>ARCHSR00  OPENED    #J15126566 ARCHCC1X.PHCPROG.AMISYS   INPUT   831708
>                                 arcjcl12,job1.amisys,pub
>
>
>END OF PROGRAM
>PRPL MGR.AMISYS: LISTF ARCHSR00,2
>ACCOUNT=  AMISYS      GROUP=  PUB
>
>FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
>                   SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX
>
>ARCHSR00*          32B  FA      831543    9000000 204   104448 54 32
>
>
>===================
>Leonard S. Berkowitz
>Perot Health Care Systems
>(Harvard Pilgrim Health Care account)
>voice: 617-509-1212
>fax:   617-509-3737
>pager: 781-226-2431

Bob Schlosser