|
Ran the statement in iNav scripts - no error, returned the data I expected.
As a work around I used the statement to create a file using STRSQL,
put the code in a QMQry as an insert, and insert the records into a
temp table with a CL wrapper. I then open the temp file with the
COBOL program to process. That's the long way around! The temp file
does not show any data problems.
On 8/17/07, Wilt, Charles <WiltC@xxxxxxxxxx> wrote:
Hm, that's strange...
1) Try run SQL scripts from ops-nav
2) Try outputting the results from STRSQL into a file, see anything fishy?
-----Original Message-----
Thanks for the reply. The job log tells me nothing. It fails
on the first fetch. The result is a small set, usually
between 20 and 500 records depending on the day. I have paged
through all the records in the STRSQL execution of the statement.
On 8/17/07, Wilt, Charles <WiltC@xxxxxxxxxx> wrote:
got a data
The system's telling you the problem. I'm guessing you've
record somewhere with a bad value in BRQDVA. Look for aprior message
in the job log that tells you which record.record you got
Or add some code in your program to tell you the last
successfully.yet, unless
STRSQL may be working because it hadn't hit the bad record
you've paged through all the records.helped me
-----Original Message-----
I asked this in the WDSc list, but none of the responses
find the problem. I have the following statement;
Exec SQL
Declare LTRC1 cursor for
with t1 as (Select distinct lnbss, lnbond
from slsfiles/sllnrep
WHERE lnlsts < "P90" )
select
Distinct ZIP_CODE,
PLUS_FOUR,
CAR_RTE_CD,
CAR_RTE_CD,
PLUS_SIX,
PAGE_INFO,
ADDR_LINE1,
ADDR_LINE2,
ADDR_LINE3,
ADDR_LINE4,
BORR_NAME,
BORR_SSN,
RTN_CODES,
LNBOND
from BCTEST/BCSRREP,
SLSFILES/SLBRREP Join T1 on BrBSS = LNBSS
WHERE Dec(BORR_SSN,9,0) = Dec(BRQDVA *100,9,0)
Order by LnBond, Zip_Code
END-EXEC
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.