RE: OPNQRYF problem

[rob@xxxxxxxxx]

<SNIP>
...since I never get
OPNQRYF right the first few times anyway.
<ENDSNIP>

Who does?  This is why I like SQL better.

Rob Berendt

==================
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Booth Martin"
                    <booth@MartinVT.com       To:     <midrange-l@midrange.com>
                    >                         cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     RE: OPNQRYF problem
                    drange.com


                    12/03/2001 11:36 AM
                    Please respond to
                    midrange-l






As a matter of habit I always use the &QRYSLT method, and also write the
next line after every modification as a "SNDPGMMSG &QRYSLT" .  Even when
its
finally right I usually comment the SNDPGMMSG lines instead of deleting
them
  Nothing against the debugger, but this is just a habit since I never get
OPNQRYF right the first few times anyway.

--------------------------------------------
Booth Martin
MartinB@Goddard.edu
802-454-8315 x235
--------------------------------------------
-------Original Message-------
From: midrange-l@midrange.com
Date: Monday, December 03, 2001 11:11:23 AM
To: midrange-l@midrange.com
Subject: RE: OPNQRYF problem
A guess (and definitely just a guess) is that *NL stands for "newline" and
that this error means the SQL parser hit the end of the line unexpectedly.
> QRYSLT('LSTCHG *GE "' *CAT
> &BEGUPD + *CAT '" *AND LSTCHG *LE "'
> *CAT + &ENDUPD *CAT '" *AND RECTYP
> I'm not sure how this is SUPPOSED to look, but the "+" should always and
only be at the end of the line when attempting to concatenate a string
together. Your line should probably be something like:
QRYSLT('LSTCHG *GE "' *CAT &BEGUPD +
*CAT '" *AND LSTCHG *LE "' *CAT +
&ENDUPD *CAT '" *AND RECTYP One other notes: You might want to create a
variable called &QRYSLT. That
way, you can concatenate to your heart's content, and then breakpoint the
program prior to the OPNQRYF and review the contents of the &QRYSLT
variable. If it's okay, then you can execute the OPNQRYF. This technique
has saved me hours and hours of debugging time.
Joe
> -----Original Message-----
> From: midrange-l-admin@midrange.com
> [mailto:midrange-l-admin@midrange.com]On Behalf Of Richard Reeve
> Sent: Monday, December 03, 2001 9:49 AM
> To: midrange-l@midrange.com
> Subject: OPNQRYF problem
>
>
> All,
>
> I am attempting an open query in a CL. It
> compiles fine, but when I run the CL I get the
> following message/joblog;
>
> Operand for *NL function not valid.
>
> Error occurred during processing of command.
>
> Function check. CPF9899 unmonitored by MEHLD04J at
> statement 800,
> instruction X'002C'.
>
> CPF9899 received by MEHLD04J at 800. (C D I R)
>
> CPF9899 received by MEHLD04J at 800. (C D I R)
>
>
> the CL is as follows;
> BEGIN: PGM
>
> DCL VAR(&BEGUPD ) TYPE(*CHAR) LEN(07)
>
> DCL VAR(&ENDUPD ) TYPE(*CHAR) LEN(07)
>
> DCLF FILE(EXHMAS)
>
> RTVDTAARA DTAARA(BACKBRIDGE (51 7)) RTNVAR(&BEGUPD)
>
> RTVDTAARA DTAARA(BACKBRIDGE (58 7)) RTNVAR(&ENDUPD)
>
> OVRDBF FILE(EXHMAS) TOFILE(EXHMAS) SHARE(*YES)
>
> OPNQRYF FILE((EXHMAS)) FORMAT(EXHMAS REXHMAS) +
>
> QRYSLT('LSTCHG *GE "' *CAT
> &BEGUPD + *CAT '" *AND LSTCHG *LE "'
> *CAT + &ENDUPD *CAT '" *AND RECTYP
> >
>
> CALL PGM(MEHLD04I)
> END: ENDPGM
_______________________________________________
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.