This section lists the Java related configurations, that you need to consider in order to be able to run InterFormNG2 on the IBM i platform.
•Java version 17 must be installed. InterFormNG2 is a Java based application that has been tested and verified to run on the 64bit version of JAVA 17.
•It is highly recommended (and sometimes even necessary) to upgrade Java 17 to the latest update. This is covered here.
•You should ensure, that InterFormNG2 is setup to run on 64 bit Java 17 (and especially not on an older version or a 32 bit version). You can configure InterFormNG2 to run a specific Java version by setting the path in the data area, IFORMNG2/JAVA_HOME. This tells InterFormNG2 to use the 64 bit Java 17 from the normal directory:
CHGDTAARA DTAARA(IFORMNG2/JAVA_HOME *ALL) VALUE('/QOpenSys/QIBM/ProdData/JavaVM/jdk17/64bit')
(If an incompatible Java version is used, then all jobs of the IFORMNG2 subsystem may not start).
•In case of a problem concerning the InterFormNG2 service job, then it can be helpful to end the IFORMNG2 subsystem and manually start up InterFormNG2 in QShell with the commands found in the configuration file, service-as400.sh. This file is found in the IFS inside: /iformng2/InterFormNG-shell/Core.
•You should also consider/verify if your IBM i is running any other JAVA based applications. If already running JAVA on the IBM i, make sure that the installation(s) are made without system wide changes to the general JVM environment.
•In cases when running on an IBM i with a "Modified" JAVA version, it can result in problems when you try to start InterFormNG2. Based on experience it is not always neither simple nor fast to help identify/locate, whatever that has been modified. Examples of things that makes a JAVA installation "Modified" are listed below:
•Any change in system wide properties, that are related to Java. Example: ADDENVVAR ENVVAR('xxxx') LEVEL(*SYS).
•Any use of custom made JAVA System.properties files.
•Any addition/changes/removal of files in folder(and subfolders) to QOpenSys\QIBM\*
Examples: Changes to the file "java.security" -- Addition/Removal of JAR-files or other files.
•If a problem can be traced back to the existence of such a modification - A fee to find and correct the change may be charged.
•The Java settings of InterFormNG2 are set via option 92. Change NG2 installation on the IFORMNG2/IFORMNG2 menu.
•Some IBM i machines are too slow to properly run InterFormNG2. If you are in doubt, if your machine is fast enough, then you should run the speed test before proceeding. Remember, that you could consider to run InterFormNG2 on a Windows server and process files and spooled files from the IBM i on this machine instead as covered here.
Before you consider to run InterFormNG2 on the IBM i you should verify, if your IBM i is fast enough in order to get a proper performance, when you run InterFormNG2.
In order to do a speed test you should do this:
•Shut down the sub system IFORMNG2/IFORMNG2.
•Delete all logfiles in IFS folder \iformng2\Log\
•Run the command, iformng2/iformng2 and select option 92. Configure NG2 installation.
•Here you should change the configuration into this:
IBM I Queue Monitor . . . . . . > *INACTIVE
NG2-Server (Output generator) . > *INACTIVE
CommandLine to NG2 . . . . . . . > *ACTIVE
QIBM_QSH_CMD_OUTPUT - *JOB . . . > *STDOUT
(Note the initial values first, so that you can change them back later. The default values are *ACTIVE for the first three and NONE for the QIBM_QSH_CMD_OUTPUT).
•Now start the IFORMNG2/IFORMNG2 subsystem e.g. via option 10. Start IFORMNG2 subsystem on the IFRORMNG2/IFORMNG2 menu.
•Check out the jobs in the IFORMNG2 subsystem and wait for the TOOLSHED2 jobs to be fully started and wait for them to consume less than 0.5% CPU.
•Now run the command, IFORMNG2/NG2VERIFY three to five times and be patient as this might take several minutes.
•Locate and open the generated logfile in IFS folder \iformng2\Log\
•In the bottom the log file - locate the last “ Test completed total time “ if that time is significant larger that the Reff (reference) times - then the Hardware/Configuration is not recomended to execute NG2.
E.g.:
************** Test completed total time = 3830 ms *****************************************
***** Reff time CPU Intel i7-6700HQ 2500 ms ( Old PC) *********************************
***** Reff time CPU POWER8 (Share <25%) 4000 ms ( Old IBM I ) ***********************
************************************************************************************************