Re: Access Update Requires Journaling

>From what I have exprienced (nothing from any sort of documentation).
Any time you are doing an insert/update/delete via SQL, you need to
have it journaled. I know there is a way in RPG to don't force the use
of a journal. Maybe that would help you out. Try this:
http://mikewills.name/archives/2003/12/08/updatedelete_in_sqlrpgle.php


On Mon, 14 Mar 2005 15:43:07 -0600, Steve Landess <sjl_abc@xxxxxxxxxxx> wrote:
> > 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
> --
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 


-- 
Mike Wills
Midrange Programmer/Lawson Administrator
koldark@xxxxxxxxx
http://www.mikewills.name
Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.