|
Hi, Mark:If it is really a temporary table, do you really even care about level-checks?
If not, then issue: CHGPF docs00 LVLCHK(*NO) That should take care of it ... ;-) Or, alternatively, issue: OVRDBF docs00 *LIBL/docs00 LVLCHK(*NO) when you compile your program, or at runtime ... HTH, Mark S. Waterbury > M Lazarus wrote:
Steve, Good thought, but no dice. I changed the statement as follows: DECLARE GLOBAL TEMPORARY TABLE docs00r AS ( SELECT * FROM docs00 WHERE chkdate BETWEEN '2006-11-01-00.00.00.000000' and '2006-11-30-23.59.59.000000' and TYPE2 in ('BL','POD')) WITH DATA (Docs00r is the format name for docs00.) I still got different format level ID's. -markWorking as designed...with SQL the record format name is created to match the file name. If you REALLY need the file to be named doclist, a workaround is to do this: DECLARE GLOBAL TEMPORARY TABLE docs00 AS ( SELECT * FROM docs00 WHERE chkdate BETWEEN '2006-11-01-00.00.00.000000' and '2006-11-30-23.59.59.000000' and TYPE2 in ('BL','POD')) WITH DATA Then rename the file to doclist. - Steve ----- Original Message ----- From: "M Lazarus" <mlazarus@xxxxxxxx> To: <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, November 28, 2006 1:04 PM Subject: SQL - Declare Global Temporary level checkI came across a situation that I think is an SQL bug, but I'd like to run it by you guys. DECLARE GLOBAL TEMPORARY TABLE doclist AS ( SELECT * FROM docs00 WHERE chkdate BETWEEN '2006-11-01-00.00.00.000000' and '2006-11-30-23.59.59.000000' and TYPE2 in ('BL','POD')) WITH DATA Table DOCLIST created in QTEMP. CHKDATE is a timestamp field. TYPE2 is a variable length field. The data seems to be populated correctly in QTEMP/DOCLIST. Should the format level identifier be the same as the original file (DOCS00)? I would have guessed yes, but they are different. So overriding DOCS00 to QTEMP/DOCLIST throws a level check. Bug or not? -mark
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.