In <[log in to unmask]> Chris Bartram <[log in to unmask]> writes:
>
> In <[log in to unmask]> Bill Bennett CSY <[log in to unmask]>
> writes:
>
>> On Wed, 7 Jun 1995 18:13:02 -0400, Chris Bartram ([log in to unmask]) wrote:
>> : listf httpd.pub,2
>> : ACCOUNT=  DEV3K       GROUP=  PUB
>>
>> : FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
>> :                   SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX
>>
>> : HTTPD     NMPRG     1B  BA      304640 2147483647   2     1200  1  *
>>
>>
>> : :linkedit
>> : HP Link Editor/iX (HP30315A.05.06) Copyright Hewlett-Packard Co 1986
>>
>>
>> : LinkEd> listprog httpd.pub
>> : LIBRARY "HTTPD.PUB" FILE LIMIT MUST BE <= 4096000 (LINKERR 1163)
>>
>> : LinkEd> altprog httpd.pub;cap=ia,ba,ph,pm
>> : OPERATION INCONSISTENT WITH ACCESS TYPE  (FSERR 40)
>> : THE OUTPUT FILE IS FULL   (LINKERR 1142)
>>
>> The reasion LINKEDIT is having a problem is that the program file is a
>> byte stream file.  There appears to still be checks in LINKEDIT that
>> assumes the program file is 128W (256 byte) record file. So when it
>> calculates the limit using record length, it thinks its using 256 byte
>> records when in reality it is using 1 byte records.
>
>If I recall correctly, just compiling a program using the compiler (from
>the posix shell) generates such a file.
>
>MPEX also can't %altfile the prog file, since it appears to be trying
to
>freaddir on the first record of the (byte stream) file, and gets the
same
>error (operation inconsistent with access type).
 
What version of MPEX are you running?  Version 25 (a.k.a. "2.5") has
added new keywords to the %ALTFILE command, in particular, ;FIXED,
;REC=, and ;BINARY that may help with this conversion.  (Can't promise
it works 100% though -- I remember diddling around with this, but got
caught by the way the operating system returns data from byte stream
files, it "tries" to make them into fixed or variable length files as
far as the reader is concerned, but usually it gets in the way)
 
You might also try several %ALTFILEs one after another.  First, remove
code="NMPRG" (make it ""), then make it fixed length binary, then add
back in code="NMPRG", then change the caps, etc.  When you use keywords
such as "cap=", MPEX makes assumptions about the type and content of
the file (hence the FSERR).  By removing the CODE="NMPRG" attribute,
you can make other changes without MPEX second-guessing what you are
trying to do.  When you get the program back to looking like a program,
re-add the NMPRG attribute and then MPEX should be able to make the
correct decisions about the contents of the file.
 
 
--
Tom Emerson
..can now be reached at:
   [log in to unmask] (here)
   [log in to unmask]    (preferred)