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



>From the latest RPG IV redbook:

The following information provides details on the specific PTFs necessary to
enable the OPTION *SRCSTMT and *NODEBUGIO features in releases of the RPG IV
compiler prior to V4R4, where the support is in the base release. 

You need a compiler PTF for the release where you compile the programs, and
a runtime PTF for the release where you run your programs. For example, if
you compile on V4R2 with TGTRLS(V3R2M0), you need SF47055 on the V4R2
system, and you need SF45189 on the V4R2 system if you want to run your
program there, and you also need SF45788 on the V3R2 system where you run
your program. If you compile and run any programs on your V4R2 system for
*CURRENT release, you will also need SF45191.

Release Compiler        TGTRLS  Runtime
                (57xxRG1)                       (57xxSS1)

V3R2            SF46001 *CURRENT        SF45788
V3R6            SF45749 *CURRENT        SF45430
V3R7            SF46327 *CURRENT        SF46321
SF47056                 *PRV,V3R2,
                                V3R6
V4R1            SF46327 *CURRENT,       SF46462
                                *PRV
                SF47056 V3R2, V3R6
V4R2            SF45191 *CURRENT        SF45189
                SF46944 *PRV,V4R1,
                                V3R7
                SF47055 V3R2
V4R3            SF45191 *CURRENT        N/A
                SF46944 *PRV,V4R1,
                                V3R7
                SF47055 V3R2

Regards,

Gerry


-----Original Message-----
From: Shrader, Patrick [mailto:pshrader@wkep.com]
Sent: Wednesday, February 23, 2000 3:14 PM
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.