Over the last few months I've been testing the creation of an IBM i image using the IBM Image Construction and Composition Tool (ICCT). In the end it worked perfectly well, but initially it wasn't the smoothest of rides. Therefore I thought I'd share a few gotchas and tips to help you along the way.
Firstly I found that "kidnap" (or "spider bite" as I prefer to call it) worked best. In other words, capturing a running system.
There are a number of licpgms that are required to ensure that the ICCT can access the image for capturing and can also send execution bundles on subsequent synchronization and deploy. Ensure the following are on :
5733SC1 IBM Portable Utilities for I (*BASE and option 1)
5770SS1 option 13 System Openness Includes
5770SS1 option 33 Portable App Solutions Environment
Startup program change
Verify these TCPIP servers will be auto-started: UPDDTA FILE(QUSRSYS/QATOCSTART)
Never far from our thoughts when dealing with IBM i, make sure that you try and install the latest cume. SI48604 is mandatory for correct function of the Activation Engine but this can be found on c3037.
Use the following commands to enable and disable the Activation Engine. The AE must be enabled prior to "spider bite".
CALL PGM(QSYS/QAENGCHG) PARM(*DISABLE)
CALL PGM(QSYS/QAENGCHG) PARM(*ENABLE)
Scripting the software bundles
Use this shebang :
For IBM i commands, use this format :
/QOpenSys/usr/bin/system -i "SBMJOB CMD(CALL PGM(PFFTP/PFFTP) PARM('IIM'))"
When running jar in a script I came across an interesting issue. The jar command worked fine interactively in QSHELL, but I received an error
when running in a software bundles script. The error was to do with the execution of QJVATOOLS.PGM
In the end I got it working by using a different jar in the script :
/QIBM/ProdData/OS400/Java400/jFromPASE jar -xf CZUT2ML.zip