Journaling a Physical File on IBM iSeries Using STRJRNPF
Filed under: EnterpriseOne - General, IBM i/System i/iSeries/AS400, JDBC, JDBJ, Java, enterpriseone
We have a system that needs to interface directly with some EnterpriseOne Files. This system is written in Java and seems to be very difficult to change any JDBC settings to not use commitment control.
Anyway, to get around this issue, we started journaling the physical file that the JDBC command was trying to update using the following command:
STRJRNPF FILE(PRODDTA/F0911) JRN(OWJRNL/OW_JRNL)Tags: enterpriseone, enterpriseone, EnterpriseOne - General, ibm, IBM i/System i/iSeries/AS400, iseries, Java, JDBC, JDBC, JDBJ, system i
Egen Process JDBJ Gotcha
Filed under: EnterpriseOne - JAS (Java Application Server), IBM i/System i/iSeries/AS400, JDBJ, eGen, enterpriseone
When setting up a workstation to perform the eGen process, once in a while there is a step that I seem to forget. It has to do with two settings in the JDBJ.INI file that need to be changed from their default values and JDBJ driver files:
- [JDBj-SPEC DATA SOURCE] – This whole stanza needs to be commented out. If you don’t, the eGen application will here for the location to which you want to generate your serialized objects, which is defaulted to the local MSDE database.
- [JDBj-JDBC DRIVERS] – The values in this stanza are commented out by default. You will need to uncomment the drivers that are appropriate to your installation. For me, that is:
- AS400=com.ibm.as400.access.AS400JDBCDriver
- SQLSERVER=com.microsoft.jdbc.sqlserver.SQLServerDriver
- JDBJ Driver Files – The four files below need to be copied to the C:\e811\MISC directory.
- jt400.jar
- msbase.jar
- mssqlserver.jar
- msutil.jar
NOTE: This information is for Tools Release 8.97 and may be different for other versions.
Tags: as/400, eGen, eGen, enterpriseone, EnterpriseOne - JAS (Java Application Server), ibm, IBM i/System i/iSeries/AS400, JDBC, JDBJ, sql, Tools Release, version, versionsiSeries JDBC jt400.jar – {note to self}
Filed under: EnterpriseOne - Install/Upgrade, EnterpriseOne - JAS (Java Application Server), IBM i/System i/iSeries/AS400
Excerpt from a post on JDEList.com by Colin Dawes:
You CAN NOT use the jt400 from the client access folder.
You need to use the jt400 that is on your iSeries. The 2 versions are not the same and you’ll get some hanging if you use the iSeries Access version.
The jt400 on the iSeries is located at:
/QIBM/PRODDTA/HTTP/PUBLIC/JT400/LIB/JT400.JARUsually you need to copy this to the following location on Windows:
\WebSphere\AppServer\libI say usually because sometimes during the installation prople point the installed to the iSeries Access Path. In this case the WAS variable will be incorrect and you either need to (1) Change the variable in WAS or copy the jt400.jar from the iSeries on top of the jt400.jar that came with iSeries Access.


