|
This doesn't work on my V4R3 Box. What gives? I get following error:
The parameter for keyword OPTION is not valid; parameter is ignored.
Help shows:
Additional Message Information
Message ID . . . . . . : RNF1331 Severity . . . . . . . : 20
Message type . . . . . : Diagnostic
Message . . . . : The parameter for keyword OPTION is not valid;
parameter
is ignored.
Cause . . . . . : The parameter for the keyword OPTION must follow these
rules:
- The parameter must be one of *XREF, *NOXREF, *GEN, *NOGEN, *SECLVL,
*NOSECLVL, *SHOWCOPY, *NOSHOWCOPY, *EXPDDS, *NOEXPDDS, *EXT, *NOEXT,
*SHOWSKP, or *NOSHOWSKP.
- The same parameter cannot be repeated.
- If a compile option is specified, the parameter used to not specify the
same compile option cannot also be used, and vise versa. For example,
if
you specify *XREF you cannot also specify *NOXREF, and vise versa.
The parameter is ignored.
Recovery . . . : Correct the parameter for keyword OPTION. Compile
again.
Bottom
Press Enter to continue.
F3=Exit F6=Print F9=Display message details
F10=Display messages in job log F12=Cancel F21=Select assistance level
Art Tostaine, Jr.
CCA, Inc.
Parlin, NJ 08859
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Douglas Handy
> Sent: Wednesday, December 16, 1998 10:21 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: RPGLE - DEBUGIO
>
>
> Hans,
>
> >>I think it is used to have the OPTION(*SRCSTMT *NODEBUGIO) in the
> >>"H" spec to avoid stepping through I/O operations. Could you let
> >>me know how to avoid IO in debug. Our machine is V4R2.
> >
> >You can't avoid I/O in debug. What you can prevent
> >is *updates* to files.
>
> I think what he was referring to was not eliminating the I/O per se,
> but eliminating the debugger stepping thru each field as it is moved
> from the buffer to the field itself. This is rarely useful in RPG
> debugging, and the Option( *NoDebugIO ) was created for this very
> reason. But it is only in the base release of V4R3; it is availavle
> via PTF for releases all the way back to V3R2!
>
> This option was actually added before V4R2 was publicly released, but
> after it was locked down so the PTF is needed for V4R2 as well.
>
> The *SrcStmt is a separate option added by the same PTF's.
>
> Aside to Chanh Le: The syntax was close, but you need to separate the
> options with a : delimiter, i.e. Option( *SrcStmt : *NoDebugIO )
>
> You also need a PTF for versions prior to V4R3. I think these numbers
> are still accurate (but maybe have been superceeded) since this is a
> clip from Barbarra Morris' posting last Feb announcing availability.
>
> 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
>
> +---
> | 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 mailing list archive is Copyright 1997-2025 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.