OMD Messages
The OMD370 utility may produce messages for either invalid object
decks created by the compiler, or problems related to input parameters,
which should be corrected by the site programmer. Persistent problems
with the OMD370 utility or invalid object decks should be reported to
SAS/C Technical Support. The diagnostics described in this chapter
typically can be corrected by the user.
The general format of an OMD message is
*** Warning: message text
or
*** ERROR: message text
Can't create OMD listing.
An error occurred when OMD370 tried to open the listing file. This can
be caused, for instance, by specifying a write-protected location for
the file. Except on UNIX, this message is usually accompanied by
a message from the run-time library, which contains more specfic
information about the problem. Correct the problem and re-run OMD370.
Can't open [object | source] file [file-name | none specified].
OMD370 could not open the specified file. Under UNIX, if no name is given
on the command line, the name shown will be none specified. Ensure
that the file exists and re-run OMD370.
Invalid DDname prefix specified: prefix
OS/390 only: The prefix specified in the FILES option was not a correct
prefix for a DDname. The prefix must be between 1 and 3 characters.
The first character of the prefix must be alphameric, or @, #, or $.
The remaining characters must be alphameric.
Invalid OMD option: option
OMD370 did not recognize the specified command line token as an option.
Refer to the documentation for OMD370 for a list of OMD370 options.
Invalid pagesize: num. Set to 55.
The value specified by the PAGESIZE (-p) option was less than 10 or
greater than 255. OMD370 resets the value to the default, 55 lines per
page. Specify a value in the accepted range.
No line number/offset table.
The compiler's nolineno option was in effect when the object
module was generated. This causes the compiler to suppress the
generation of the line number/offset table CSECT that OMD370 uses to
match source line numbers to offsets in the generated code. Recompile
the program using the lineno option. lineno is the default.
Not enough memory to continue.
An OMD370 storage allocation could not be satisfied. If you
are running in OS/390 batch, increase the region size for the job. If you
are running in TSO, increase the TSO region size. If CMS, increase the
size of your virtual machine.
Premature end of source file.
The line number/offset table CSECT in the object file specified a line
number that exceeds the number of lines in the source file. This can
occur when the specified object file is not associated with the specified source
file. This can also occur if a C source file that has been generated by
the C++ translator is compiled but the CXX option is not used. Ensure
that the source file and object file match or, if the source file was
generated by the C++ translator, the CXX option is used when the source
file is compiled.
TEXT filename missing or invalid.
CMS only: The filename specified as the first non-option argument to
OMD370 is missing or cannot be interpreted as a CMS filename. Check
that the filename is not preceeded with a - (dash) and
contains no invalid characters.
TXTLIB filename not specified with LIB option.
CMS only: The LIB (-l) option was used but no filename was found.
Re-run OMD370, specifying the name of a text library (having the
filetype TXTLIB) following the LIB (-l) option.
Unknown card type in object file.
OMD370 detected a record in the input file that is not a
valid object record type. Check to make sure that the input file is an
object file generated by the compiler or a 370 assembler such as
Assembler H or HLASM.
Copyright © 2001
by SAS Institute Inc., Cary, NC, USA. All rights reserved.