Re: PO Commit failures


Well Known Member
Re: PO Commit failures

Title: AS/400® Journaling Issues after Applying SP13 and Later Service Packs
Abstract: After applying SP13 and later Service Packs to B73.3.1 or
B73.3.2, issues arise with AS/400® journaling.



B73.3.1, B73.3.2

Document ID

Date Created

Date Reviewed

Date Revised


Checking out objects will fail after applying the service pack. The
following will be found in the jde.log after attempting a check out.
Similar errors may also be found in the jde.log when running some

ODB0000165 - SQLDriverConnect failed. DSN: OWJRNL

[Microsoft][ODBC Driver Manager] Data source name not found and
no default driver specified - SQLSTATE: IM002ODB0000183 - SQLExecute failed

[IBM][Client Access Express ODBC Driver (32-bit)][DB2/400
SQL]SQL7008 - F9882 in SYSB7331 not valid for operation. - SQLSTATE: S1000

JDB9900401 - Failed to execute db request

JDB3600011 - Failed to perform Update for F9882

Add a new System ODBC Data Source in the System DSN:

The name of the Data Source should be OWJRNL. The library should
also be OWJRNL.


Choose any AS/400 on the network as the AS/400 System.

Set the Translate option to Translate.

Use ODBC defaults for the remaining ODBC settings.

The below change is necessary only if you are running B7332.

Add the following setting in the JDE.INI file on the client side:



This setting will logically switch ON the code necessary for ODBC
Journaling. The default is currently set to 0. (This setting is currently
not in the JDE.INI file and should be added.)

Modifying existing Journaling on the AS/400 Enterprise server:

If you currently have OneWorld on the AS/400, bring down all instances of
OneWorld on the AS/400 else, skip this step.

Physically end journaling on all OneWorld files for all instances of
OneWorld. If you are using third party tools that rely on Journaling, please
bring them down and explicitly end journaling on all the files. If you are
not currently journaling any files on the AS/400 skip this step.

Create a new library (OWJRNL). OneWorld should own the newly created
library. If you are currently journaling on a separate ASP make sure that
the library OWJRNL is created in that ASP. If you are not journaling on a
separate ASP, create OWJRNL in the default ASP.


1. 1. The name of the library (OWJRNL) should be the identical to the
Default Libraries setting for ODBC data source OWJRNL.

2. If you have multiple AS/400's serving as data base server, make sure
that the name of the library is consistent across the entire network. This
is crucial because there is only one ODBC setting (OWJRNL) for all the data
base servers and System setting for the OWJRNL data source will be changed
at Runtime.

(Refer to the OneWorld AS/400 Security Document on enforcing OneWorld
security on the AS/400, if you have any security concerns.)

Edit the following settings in the "DB SYSTEM SETTINGS" section in the
server JDE.INI file.


Default Journal=OW_JRNL

Default Journal LIBRARY=OWJRNL

Default Journal Receiver=OW_JRNL000

Default Journal Receiver LIBRARY =OWJRNL

Size of Journal Receiver=6000

If you do not have any one of the above settings do not add them. OneWorld
will use system defaults.

If you have several instances of OneWorld running on the AS/400 please
change all JDE.INI files.

Moving the Default Journal LIBRARY and Default Receiver LIBRARY to a
consistent library will not cause issues during OneWorld upgrades and
rebuilding. Currently the name of the Default Journal LIBRARY and Default
Receiver LIBRARY are changed with every new release of OneWorld.

If you are currently using third party tools, these will use journaling.
Change the settings in all the tools so the journal and journal receiver
libraries are pointed to OWJRNL. This will provide a central location for
managing journaling on the AS/400 and eliminates identical files from being
journaled in different libraries.

Installing the Stored Procedure on the AS/400.

Two new programs and a command will be shipped along with OneWorld. The
program STRJOURNAL is a stored procedure on the AS/400. This program will
start journaling for ODBC Client Access connections. The program INSTALLSP
and command INSTALLSP are essential for installing the stored procedure on
the AS/400.

Copy the programs STRJOURNAL, INSTALLSP and command INSTALLSP to the OWJRNL
library from your B733XSYS library.

Invoke the command INSTALLSP with the default settings. Any changes you make
to the command parameters should reflect the changes made to Default Journal
settings in the server JDE.INI file on the application server.

The INSTALLSP program will create a file OWJRNLINFO in the OWJRNL library.
This should not be deleted. The information stored in this file will be used
to start journaling via Client Access ODBC connections.

If you want to change the journal information, invoke the INSTALLSP command
with the new parameters.

There is no need to reinstall the stored procedure after every upgrade, but
there is no harm in doing so.


If the INSTALLSP command fails, refer to the IBM APAR II12248. The
following errors may show up in the joblog if the INSTALLSP fails:

STRJOURNAL in OWJRNL type *N not found.

Data mapping error on member SYSRO00001.

Message . . . . : Data mapping error on member SYSRO00001.

Cause . . . . . : A data mapping error occurred on field
DBINFO in record

number 0, record format SYSRO00001, member number 1, in member

file SYSROUTINE in library QSYS2, because of error code 20.

----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Wednesday, February 07, 2001 4:17 PM
Subject: PO Commit failures

> Searched breaking news and the KG for your fix and could not find
> anything.....

JD Nowell
OW: B7332
ES: AS400 V4R4 CO: DB2/400 SP: 11.2
Users: 250 TSE Users: 100