OCTCOMP doesn't really recomple programs.  It inserts code into the program to
take advantage of the 32 bit arch.  Your program will not change in structure or
file code.  It will remain the same.

Later

Heidi Wilker wrote:

> Hello all,
> I have a question regarding OCTCOMP.
> My understanding of OCTCOMP is that it is supposed to recompile
> compatibility mode program code (for which the source code is not
> available), and make it Native mode.
>
> We have an HP-3000, 947, running MPE/ix 6.0
>
> I performed an OCTCOMP on one of our programs.    It seemed to be
> successful.   However, when I list the file, the file code still is listed
> as "PROG" (indicating a compatibility mode program), instead of NMPRG (which
> would indicate a Native mode program).    Listed below, in a LISTF ,2 format
> are both the original compatibility mode program currently being used,
> INTRFACE, as well as the 'target file' for the OCTCOMP function, IN2.
> Note that the EOF is much larger for the OCTCOMP 'target file'.
>
> FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
> --DAYS--
>                   SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX   ACC
> MOD
>
> IN2       PROG    128W  FB         755       1664   1      960  4 16
>
> INTRFACE* PROG    128W  FB         104        104   1      112  1  1
> 4069
>                                                           58 readers
>
> This is the first time I've used the OCTCOMP function, so I'd appreciate any
> experienced user's input.
>
> Thank you!
> Heidi  D.  Wilker

--
Ron Horner
HP3000 Systems Administrator
JCPenney Logistics
[log in to unmask]
(414) 259-2274