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




        This list of PTFs below is very handy to have. Thanks Jon.

        Does anyone know what position and value of the H spec contains
the compile directive to correct the incorrect line numbers? What other
possible directives might consistently used. Many of our RPG programs
here at CMI don't have an H spec at this time. Today we compile our RPG
programs to  V3R1M1 for support reasons. The incorrect line numbers
problem has to be remedied ASAP. These source members are being
converted with CVTRPGSRC command which has been recently discussed here
at midrange.com.

Can someone 'paste' a H spec for us ILE new-bees at midrange.com? We
can't expect full explanations, just an example or two. We can go 'look
it up'.

Ken Slaugh
Senior Programmer/System Analyst
AS/400 Professional Network Administrator/MSE
Specialist - Client Access/400
Chouinard & Myhre, Inc.

> -----Original Message-----
> From: Jon.Paris@halinfo.it [SMTP:Jon.Paris@halinfo.it]
> Sent: Friday, May 28, 1999 5:41 AM
> To:   midrange-l@midrange.com
> Subject:      Line numbers on RPG/LE error messages
> 
> 
> 
> You are correct - IBM has not "... left us this problem without a
> solution".
> 
> 
> 
> On releases prior to V4R4 you have to code an H spec keyword to get
> the new
> behavior:
> 
> 
>           OPTION(*SRCSTMT *NODEBUGIO)
> 
> 
> 
> The *SRCSTMT is the one you are asking for - it forces SEU line
> numbers to be
> used rather than compiler generated ones.  The second parameter
> (*NODEBUGIO)
> relates to the debugger.  It avoids you having to step through the
> processing of
> every single field when a file is read/written.
> 
> 
> V4R4 and later support this behavior through the OPTION parameter on
> the command
> (the H spec keyword will still
> be available too).
> 
> 
> PTFs are below for V3R2, V3R6, V3R7 and V4R2. These are the PTFs to
> fix
> TGTRLS(*CURRENT) - other TGTRLS PTFs should be available if required.
> 
> 
>          Compiler (product 57xxRG1) | Runtime (product 57xxSS1)
>          -------------------------- | ------------------------
>  V3R2    SF46001                    | SF45788
>  V3R6    SF45749                    | SF45430
>  V3R7    SF46327                    | SF46321
>  V4R1    (use V3R7 compiler + PTF)  | SF46462
>  V4R2    SF45191                    | SF45189
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-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-Ups:

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.