MPE/iX Commands Reference Manual (32650-90877)
Chapter 9 347
Command List VII
Commands MOUNT thru OUTFENCE
Operation Notes
The OCTCOMP command translates MPE V/E instructions into native mode instructions. If
you specify targetfile, a new file is created. If you do not specify targetfile, OCTCOMP
attempts to append the translated instructions to input file. The append fails and an error
message is displayed if the input file is too small to qualify as an output file. In such a case,
the solution is to specify
targetfile
.
User-defined labels are stripped from the input file, and they may not be added to a
translated file.
After a new master installation tape is loaded, you must retranslate the file on which you
used the systemsl option (to create SL.PUB.SYS). Otherwise, it runs in emulator mode.
The noovf parameter can improve the code generated. However, the user must ensure that
the necessary conditions hold for code translated using this parameter. For the noovf
parameter, the input code must not use the overflow trap mechanism.
The OCTCOMP command does not support the following:
• File equations involving the input, targetfile, or list files (backreferencing is not
supported).
• $NULL, $STDIN, $STDLIST, or $NEWPASS for input, targetfile, or list; $OLDPASS for
targetfile or list; but $OLDPASS is supported for input.
• Using an explicit or implicit RUN command to execute the OCTCOMP command.
Use
This command is available in a session, job, or program. It is not available in BREAK.
Pressing
Break aborts the execution of this command.
Examples
The following set of examples illustrates the use of the add=, ignore=, and trans=
parameters and the effect each of them has on the content of the translated code output file
with each succeeding invocation of OCTCOMP. In each example, the input file is assumed to
consist of seven segments, 0 through 6.
In the following example, the translated output file, OCTOUT, consists of the SL file
SOURCEIN and translated segments 1, 2, 3, and 4 only.
OCTCOMP SOURCEIN,OCTOUT;INFO="TRANS=1,2,3,4"
In the following example, the output in OCTOUT consists of the existing SOURCEIN object
code image, existing translated segments 1, 2, 3, and 4, with translated segments 0, 5, and
6 appended to the file. Segment 5 does not have overflow detection.
OCTCOMP OCTOUT;INFO="ADD=0,5,6;NOOVF=5"
In the following example, the output in OCTOUT2 consists of the object code image from the
existing file OCTOUT, with translated segments 0, 3, 5, and 6 only. This time segment 5 has
overflow detection in OCTOUT2.
OCTCOMP OCTOUT,OCTOUT2;INFO='IGNORE=1,2,4'
This output would be the same if the call to OCTCOMP were given using the original object