× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If it was available where do you think they might put it? Would on the
CRTBNDRPG command be a likely candidate? If so, which parameter might it
be? Would it be the parameter that had these options?
*NOSRCSTMT
Line Numbers in the listing are assigned sequentially; these
numbers are used when debugging using statement numbers. Line
Numbers are shown on the left-most column of the listing. The
source IDs and SEU Sequence Numbers are shown on the two
right-most columns of the listing.

*SRCSTMT
Statement numbers for debugging are generated using SEU sequence
numbers and source IDs as follows:
Statement_Number = source_ID * 1000000 +
source_SEU_sequence_number

SEU Sequence Numbers are shown on the left-most column of the
listing. Statement Numbers are shown on the right-most column
of the listing; these numbers are used when debugging using
statement numbers.

Note: When OPTION(*SRCSTMT) is specified, all sequence
numbers in the source files must contain valid numeric
values. If there are duplicate sequence numbers in the same
source file, the behavior of the debugger may be
unpredictable and statement numbers for diagnostic messages
or cross reference entries may not be meaningful.

Now, if that is it, then what H spec do you think you could add (if any)
to get that so that you wouldn't have to remember this every time you
compiled?



Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.