Wow... I never thought of searching on CWBDB0099. I was looking at the
other code. FAIL on my part.

Anyway, this work-around works for the data transfer problem. I'll try it
for my insert problem as well. We are still trying to figure out what
changed or why we are just seeing this now.

Mike Wills

On Thu, Aug 2, 2012 at 1:04 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

FWiW, searching the web only on those message identifiers yielded the
following link:
_Solving iSeries Access Data Transfer Problems_ ...
Published: July 27, 2011
"... plenty of references to the CWBDB0099 error with sub-error SQL0181
... clicked on the Date format drop-down box and changed the Date format
to ISO ..."

Regards, Chuck

On 31 Jul 2012 11:41, Mike Wills wrote:
We have a user that ran a query (via WRKQRY) to a file in order to
download the file. She then proceeded to go through the steps she has
done many, many times before to bring it into Excel using the Data
Transfer plugin in Excel. Everything looks good as she goes through
the wizard, our exit point software[1] logged the transaction with
basically a "select * from file as fetch only" however on the final
step she gets the following error:

CWBDB0099 - No more data is available for the stream fetch request
SQL0420 - Character in CAST argument not valid.

We tried in the "regular" file transfer tool to a file and we got the
same error. Then we switched to display the data and it worked. We
switched it back to file and it worked then. :-/

We are on 6.1 and haven't installed any CUME in a while so there
should't be any OS changes recently. Our user is on 5.4 of Client
Access and on another developer's machine she is on 6.1. Both with
the same problem.

To add to the "weirdness", I am getting the same error doing an
INSERT into a completely different file. I assumed it was a bug in my
program with translating data from one type to another, but now I am
starting to wonder if it may be something else.

Has anyone come across this?

1. Our exit program security software is PowerTech Network Security.
The developer has full access, the user has limited access but is
allowed access to that file.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page