× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Bill,

I've had WRKDBF working on multiple format logicals, the only time it's ever
fallen over for me is when there's been an unexpected null value in one of
the fields.

Fantastic piece of software though.

Jonathan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Reger, Bill
Sent: 20 June 2007 13:38
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL join 2 files

Off topic (slight hijack): WRKDBF should handle multiple format LF's. Mine
work. I'd be interested in what is causing WRKDBF to fail on yours. What
does DMITMMST look like?

Bill

-----Original Message-----
From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx]
Sent: Wednesday, June 20, 2007 8:36 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL join 2 files


Thanks for your help.

I'd forgotten that the field DLDAT was not actually a date data type field
(I "Y2K-ified" some files long before date data types came out) but zoned
8,0. The following statement, based on your suggestion, created the file:

CREATE VIEW QTEMP/ALITMMST AS (
SELECT A.*,00010101 AS DLDAT FROM DMITMMST A
UNION ALL
SELECT B.* FROM OLITMMST B )

Interesting results though. If I try VIEW or WRKDBF, I get dumps. I _can_
run Query/400 against it however. And the DLDAT field is defined as 11,0
instead of 8,0.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.