Comments on: V7R1 Qryslt in CLP

By: NickHutcheson1

NickHutcheson1 — Thu, 13 Sep 2012 15:04:42 +0000

Another programmer had changed the source without documenting or telling me. So, what I first saw was not the way it was when the error popped. Argggh!nick

By: TomLiotta

TomLiotta — Wed, 05 Sep 2012 10:45:35 +0000

If the change worked and T1ORDR is numeric, the change does make sense. It certainly doesn’t make sense that it worked before the 7.1 upgrade, especially a comparison to a blank. That is, unless the field definition itself also changed around the time of the upgrade.

Interesting that the original was “*NE” and the eventual working version was “>” (i.e., “*GT”).

You might slightly simplify the second CHGVAR:

CHGVAR VAR(&QRYSLT) VALUE( &QRYSLT *TCAT ‘ *AND + %CHAR(T1DATE “*ISO”) *GE ”’ *CAT &SDATE + *CAT ”’ *AND %CHAR(T1DATE “*ISO”) *LE + ”’ *CAT &EDATE *CAT ”” )

Tom

By: philpl1jb

philpl1jb — Tue, 04 Sep 2012 18:54:59 +0000

Your change makes sense if T1ORDR is a numeric field.

There may be less casting of variables done in OPNQRYF under v7r1 although I doubt that was the intention.

The error listing still baffels us.

By: TomLiotta

TomLiotta — Tue, 04 Sep 2012 18:43:20 +0000

It also said “position 8″, and that matches my count for the position of *LE. What was the message ID? — Tom

By: philpl1jb

philpl1jb — Tue, 04 Sep 2012 16:16:39 +0000

And the code ran in a previous version of the Op Sys?
Odd that it says the error is on code for *GT and you don’t use *GT in this query.