RE: SQL vs native I/O round 19 (long)

["Walden H. Leverich III" <WaldenL@xxxxxxxxxxxxxxx>]

Loyd,

What OS release. I modeled it on something I'm doing on V5R1 with a MAX() in
a subselect.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 

-----Original Message-----
From: Goodbar, Loyd (ETS - Water Valley) [mailto:LGoodbar@xxxxxxxxxxxxxx] 
Sent: Thursday, June 12, 2003 4:40 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL vs native I/O round 19 (long)


Walden,
Sorry, but got error "Token MAX was not valid. Valid tokens: + ) -." in the
subselect for "max(dmatdt)".

Upon further investigation, we do not need to know the transaction type for
the last used date. I did this just for verication purposes. However, we do
know the transaction types that should be ignored.

Thanks,
Loyd

--  
Loyd Goodbar
Programmer/analyst
BorgWarner Incorporated
ETS/Water Valley
662-473-5713
lgoodbar@xxxxxxxxxxxxxx


-----Original Message-----
From: Walden H. Leverich III [mailto:WaldenL@xxxxxxxxxxxxxxx] 
Sent: Thursday, June 12, 2003 3:15 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL vs native I/O round 19 (long)


Loyd,

Do you need to know the transaction type? Your initial description of the
problem doesn't state so, but your query seems to imply it. If not try this
query:

Select czekcd, 
czfktx, 
(select max(dmatdt) 
        from dbdmrep
        where dmekcd = czekcd
                and dmazcd = czazcd
                and dmcdcd not in ('ADJ',';PHY',';STD')
)
from dbczrep
where czazcd = 'WV'
order by czekcd

-Walden
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.