*** UPDATE 4/27/07 ****
> Here are some links that might help {WITH PROBLEM STATED BELOW]:
>
> http://www.websina.com/bugzero/faq/exception-as400.html
> http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci972776,00.html
>
> Looks like some kind of issue with journaling on your database.
Home Run!
I sent the links to client, they reviewed, turned on journalling and now
everything works slicker than the scum on a Louisiana swamp.
Thanks again.
Michael C. Mattias
Tal Systems Inc.
Racine WI
[EMAIL PROTECTED]
>
>
> Michael Mattias/LS wrote:
>>
>> 4/23/07
>>
>> Does anyone familiar with Mercator version (this is version 5 (five))
>> know
>> what can cause this problem?
>>
>> This is the from the Mercator output database trace (*.dbl) file:
>> ===========================================================================
>> Validating the adapter command...
>> Returned status: (0) Success
>> Interface library version 5.0(728)
>> Map:
>> D:\MercatorDevelopment\scripts\maps\whsespec\o940m\Wsi_Updatedbob.mmc,
>> Timestamp: 04/20/07 14:22:25.
>> Data being retrieved for DBQUERY function.
>> Database adapter: ODBC Version 5.0(728)
>> Starting a database unload...
>> Datasource : MILAPPFMT
>> Userid : XXXXXXXX [ EDITED. MCM]
>> Query : update edi940H set ehstatus='S', ehsdate=20070420,
>> ehstime=142220 where ehufcono = 99 and ehuforgn=0 and ehuforno='12667'
>> Query size : 121
>> Output is to a buffer.
>> Retrieving 1 rows per fetch.
>> Error in SQLExecDirect
>> Message: [IBM][iSeries Access ODBC Driver][DB2 UDB]SQL7008 - EDI940H in
>> MILAPPFMT not valid for operation.
>> SQL State: S1000
>> Retrieved 0 records (0 bytes).
>> DBQUERY failed with return code -9.
>> Returned status: (-9) Failed to execute the SQL statement
>> =============================================================================
>>
>> For what it's worth, The only thing I could find for the the official
>> explanation of SQL state S1000 is below, along with the calls which
>> should
>> return it...
>> ==============================================================================================
>> S1000 General error: Unable to create file buffer. SQLFetch
>> SQLFetchScroll
>> SQLGetData
>> S1000 General error: Unable to read from file buffer. SQLFetch
>> SQLFetchScroll SQLGetData
>> S1000 General error: Unable to write to file buffer. SQLFetch
>> SQLFetchScroll
>> SQLGetData
>> S1000 General error: Unable to close or remove file buffer. SQLFreeHandle
>> SQLFreeStmt
>> ============================================================================================
>>
>> Ok, now the cool part:
>>
>> Above work perfectly on another database, whose name is 'MILAPPF'
>>
>> Earlier in this same multi-map setup, we successfully extract from this
>> database ('MILAPPFMT')
>>
>> The map system is structured as a a single map which RUNs more maps
>> thus..
>>
>> MAIN MAP
>> RUN "extract map" (reads database, writes to text files) (Extract: =GET
>> ("DB", "-MDQ mdqname -DBNAME dbname -QUERY queryname))
>> RUN "datamap" (reads extracted text files, creates more text files)
>> RUN "this map to update the database which is failing on this database
>> but not the other"
>> This map uses "=DBQUERY( "update tablename set...[as above]), "-MDQ
>> mdqname -DBNAME dbname)"
>>
>> Both the dbname and mdqname are always read from a configuration file
>> so the
>> extract and update can be pointed at either the 'test' or 'production'
>> database.
>>
>> I am pretty sure my next step is going to have to be enabling the ODBC
>> trace
>> and trying to fibure out something from that, but I am just hoing someone
>> has encountered this before and might point us in a potentially fruitful
>> direction.
>>
>> Believe it or not, my first inclination was that I had too many letters
>> (nine) in the dbname, but that can't be a problem I don't think
>> because the
>> extract works just fine.
>>
>> Thanks in advance for any hints.
>>
>> (A thought just occurred to me: Maybe Permissions are not set correctly?)
>>
>> Michael C. Mattias
>> Tal Systems Inc.
>> Racine WI
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
