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



Drop that last suggestion of changing CRTBNDRPG command default for the
OPTION parameter.  Just tried it myself on V4R4 and was given the message:

    CPD6260 - No default value exists for keyword OPTION.

So, I guess that if you want to do this, you'll have to replace PDM option
14 with a new option that prompts the CRTBNDRPG command with OPTION(*SRCSTMT
*NODEBUGIO).

RANT(*On : *Minor)
BTW, I find CPD6260 fairly annoying.  The fact is that the OPTION parameter
has several implied defaults, *NOSRCSTMT & *DEBUGIO being among them (just
look at the Help for that parameter).  That said, I don't know if this is a
limitation of multi-value parameters.
RANT(*Off)

- Dan Bale

-----Original Message-----
From: Bale, Dan [mailto:DBale@TFSA.Textron.com]
Sent: Wednesday, February 23, 2000 11:15 AM
To: 'RPG400-L@midrange.com'
Cc: 'Shrader, Patrick'
Subject: RE: H-Spec RPG IV Option PTF


Patrick,

I am almost certain that V3R2 will not support the H-spec Option keyword.
PTF or no PTF.

However, I believe you can still get the desired results using the compile
command parameter OPTION(*SRCSTMT *NODEBUGIO).  I believe this is available
on V3R2 (this may be a PTF'd upgrade, not sure).  It's been a few years
since I've been on V3R2.

If you do have the command parameters to do that on V3R2, you may want to
consider changing the command defaults so that OPTION(*SRCSTMT *NODEBUGIO)
is the default.  (The usual recommendation: duplicate the command in a
library higher in the system library list and apply your changes to that
command.)

- Dan Bale

-----Original Message-----
From: Shrader, Patrick [mailto:pshrader@wkep.com]
Sent: Wednesday, February 23, 2000 10:14 AM
To: RPG Mailing List
Subject: H-Spec RPG IV Option PTF


Hey folks!

I am running V3R2, and I am having problems with RPG IV. When a program
ab-ends, the OS/400 debug information shows the compile statement number
that caused the problem. RPG/400 shows the actual source statement
number. This makes it very difficult to debug RPG IV programs. A couple
years ago I received a PTF from IBM that allowed me to key the following
H-Spec option in RPG IV:

Hoption(*srcstmt:*nodebugio).

This H spec option allowed the system to display the actual line of the
source code that caused the problem, not the compile source.

I have since changed jobs, but the new job is running V3R2, like I was
earlier when I experienced the problem. Can anyone direct me to the
correct PTF number so that the compiler will recognize the above
statement. I recall that the editor still did not like the syntax of the
line, but it would compile. I solved the editor issue by issuing a /copy
command for the offending lines.

Thanks for your help.

Patrick
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.