|
There is no way Bob's solution will work, if this is a multiple-format logical. Unless the message I got can be circumvented. If it's a flat file (old 36 variety?), then his answer is great. AFAIK. :-( Vern At 04:12 PM 3/14/02 -0800, you wrote: >Yeah, I think I might just stick to Bob's solution. I'm more familiar and >comfortable with that one, but I'd definitely welcome some nuances. :) > > >>> vhamberg@attbi.com 03/14/02 04:04PM >>> >SQL message: > > >Message ID . . . . . . : SQL7003 Severity . . . . . . . : 30 > >Message type . . . . . : Diagnostic > > > >Message . . . . : File XCJTALL in XCBA has more than one format. > >Cause . . . . . : SQL cannot process a file unless it has only one format. > >Funny thing, though - I was allowed to create an alias for this >multiple-format logical. Still could not use it, however. > >Updates would be to the physical, probably using some branching code, >dependent on the format just retrieved. > >At 06:24 PM 3/14/02 -0500, you wrote: > >Ted Barry wrote: > > > > >I've never had to deal with this one > > >until now... Is it possible to select > > >and/or even update a file with multiple > > >record formats? > > > >Maybe. If you have packed numbers to update it gets harder - you'd probably > >have to write your own UDFs. Anyway, treat the record as a giant character > >string and "select" based on a substring. If your header records all have a > >"1" in column 123 then you can select the headers with > > > >select * from flatfile where substr(flatfile, 123, 1) = '1' > > > >You update the same way. Let's say you need to change that "1" to a "A" > > > >update flatfile set flatfile = substr(flatfile,1,122) > > concat "A" concat substr(flatfile,124,length_of_rest_of_record) > > where substr(flatfile,123,1)='1' > > > >Conceptually, you're building an entire new flat record composed of the > >first part of the record concatenated with the changed columns concatenated > >with the last part of the record. > > > >I only do this in extreme cases, like being on a system without a compiler. > > --buck > >_______________________________________________ > >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. > >_______________________________________________ >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. > > >_______________________________________________ >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.
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.