Re: Access Update Requires Journaling

["Steve Landess" <sjl_abc@xxxxxxxxxxx>]

> Jeff Glenn wrote:
>
> Hello. Has anyone had this problem?
> We're using Access to update a file on a V5R3 machine.
> We get the error "ODBC--update on a linked table 'xxxx_xxxx' failed.
> SQL7008 - xxxx in xxxx not valid for operation. (#-7008)" that seems to be
> common.
>
> From what I understand from the archives, this typically means that the 
> ODBC
> setting is expecting commitment control and the file is not being 
> journaled.
> However, the ODBC setting for Commit mode is Commit immediate (*NONE).
>
> If we start journaling the file, the update works correctly. Why is the 
> ODBC
> connection ignoring the Commit immediate setting? I'd rather not journal 
> the
> files we're updating.

Jeff -
You might find more information in the job log of the QZDASOINIT
job that is running on the AS/400 side.  This job runs under QUSER
profile on behalf of the user profile that you use to log in with ODBC.

To find the QZDASOINIT job, open up a green-screen session
while the SQL statement is running, type:

WRKOBJLCK OBJ(ODBCUSER) OBJTYPE(*USRPRF)

where ODBCUSER is the user profile that you are using with the
ODBC driver.

If this user profile is used for multiple instances of ODBC connections,
you'll see several QZDASOINIT jobs.

Use option 5 to display the job, then option 10 to view the job log...

If the Reason Code in the SQL7008 error message is 3, I'd first be checking 
_again_ to verify that the ODBC data source that you're using with Access 
has Commit Intermediate (*NONE) specified.  We're using V5R3 iSeries Access 
to update non-journaled JDE files and ours works just fine with this 
setting.

Otherwise, call IBM support and log a call.

Regards,
Steve Landess
Austin, Texas
(512) 423-0935