|
Jeff, >Oooh. Which PTF is that? (Now watch. I'll already have it and not know >it.) Depends on the version. These were PTF'd all the way back to V3R2. The following is a quote from the original post by Barbara Morris back on Feb 10, 1988. These numbers may be superseded since they are 21 months old, but these should get you going in the right direction. <begin quote> PTFs are available for V3R2, V3R6, V3R7 and V4R2 that address the problem. Currently the PTFs only fix TGTRLS(*CURRENT) - the other TGTRLS PTFs will be available soon. Compiler (product 57xxRG1) | Runtime (product 57xxSS1) -------------------------- | ------------------------ V3R2 SF46001 | SF45788 V3R6 SF45749 | SF45430 V3R7 SF46327 | SF46321 V4R1 (use V3R7 compiler + PTF) | SF46462 V4R2 SF45191 | SF45189 <end quote> *Everybody* should get these PTF's, and use *SrcStmt as a standard part of their H specs. It sure makes ILE debugging easier. Note that the original PTF's added the support to the compiler, but *not* to the syntax checker in SEU. Therefore, SEU will complain, but ignore it and compile it anyway. You may also want to put it in a separate /Copy member. This circumvents the SEU message, but more importantly gives an easy method to make global additions to your H specs, while still allowing you to add other H specs to your source. (As opposed to supplying just a default H spec data area.) I also like *NoDebugIO, but *SrcStmt is the real benefit IMHO. The PTF cover letters explain the options. Doug +--- | 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 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.