|
..just to mention fld1 is of type *char (length 2) and fld2 is *char(length
4) and fld3 is of *char(length 3) and fld 4 is also * char and length is
8(having date value in it of DDMMYYYY format)
So unable to figure out which value is not compatible with * EQ here in
OPNQRYF.
..Thanks
On Thu, Jan 7, 2021 at 8:14 PM Rob Berendt <rob@xxxxxxxxx> wrote:
I so do not miss OPNQRYF. Since embedded sql I've found no further use
for it.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
techie21 IT
Sent: Thursday, January 7, 2021 9:17 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Operand for *EQ function not valid error
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
Hi,
In one of my CL program I am getting this error in OPNQRYF statement.
*Operand for *EQ function not valid.*
OPNQRYF FILE((QTEMP/f1)) QRYSLT('fld1 *EQ "AB" *AND fld2 *EQ "ABCD" *AND
fld3 *EQ " " *AND fld4 *EQ "06012021" ')
And additional message stating cause on pressing 'F1' for above error
message is
Message ID :- CPD3131 Severity : 30
Message Type:- Diagnostic
"The operator or built-in function *EQ, was specified at position 52 in the
expression on the QRYSLT parameter.If the error occurred on the MAPFLD
parameter,the expression was specified for the definition of field *N. For
the %Range,%VALUES,and %WLDCRD built -in functions,the error may be caused
by the first operand for the *EQ operator that is associated with the built
-in function. Conditions that can cause this error includes:-.......
........
......
................
So any idea what is wrong going here in my OPNQRYF statement?
Thanks much...
------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.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.