× 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.



Thanks for that Rob. It's just a pity you feel the need to be sarcastic.

I never have to use H specs or CRTBNDRPG. We use standard H specs from a copybook. We use a homemade compile utility. The help is in French. But now I have it in English, so thanks again.



-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
Envoyé : lundi 1 mars 2010 17:30
À : Midrange Systems Technical Discussion
Objet : Re: greenscreener problem

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
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 03/01/2010 11:05 AM
Subject: greenscreener problem
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hi,

A coworker informed me that when I save my RPG source, the
line numbers
weren't being recalculated. This led to my source lines
having numbers
like :

0001.00
0002.00
0003.00
0003.01
0003.02
0004.00

The lines 0003.01 and 0003.02 being those I modified with WDSc.

This caused him a problem, because in STRDBG he would type
something like
Find 0003.01. He would not find the line in the program
because he says
that the compiler renumbers the source lines in the program.
However, if
the lines of the source member are renumbered, he can go
easily to the
line number. I hope that makes sense.

I've found how to renumber in the preferences, but that slows
me down when
I save. I'm not sure about the compiler creating a program
with renumbered
lines, though. Can that behaviour be controlled.


David FOXWELL
Service Informatique
Tél : 03 90 23 91 63
david.foxwell@xxxxxxxxx<mailto:david.foxwell@xxxxxxxxx>
P Pensez à l'environnement avant d'imprimer ce message

--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


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.