After upgrading an IBM OS400 machine to V7R1, jobs run on verson 8 Agent go to LAUNCH ERROR.


Article ID: 87361


Updated On:


CA Automic Applications Manager (AM)


Error Message :
15:24:45.225 AW_OS400_SJ2: AwE-9999
ErrorMsg: AwE-9999 Internal error (1/11/16 3:24 PM)
Details: null
java.lang.RuntimeException: submitMessage doesn't start with 'CPC1221'

After upgrading the OS of an OS400 to V7R1 where an Applications Manager v8 Agent is installed all jobs requested on that Agent go to a LAUNCH ERROR status.

Beginning with V7R1 IBM stopped supporting the classic JVM.  The JVM now runs in ASCII mode not in EBCDIC as it was in the previous versions.  Since Applications Manager had been translating EBCDIC to ASCII so that jobs would run correctly against previous IBM versions it was causing all jobs run from Applications Manager to go to a LAUNCH ERROR status because the translation was causing unprintable output.  In order to resolve the issue we modified our code so that we will no longer perform the EDCDIC to ASCII translation if the OS is V7R1 or above.



Cause type:
Root Cause: After upgrading the IBM OS400 machine to V7R1, all OS400 jobs go to LAUNCH ERROR. This was due to V7 returning ascii for the submit message rather than ebcdic. This has been resolved.


OS: IBM AS/400
OS Version: V7R1


Update to the fix version listed below or a newer version 8 release.

Fix Status: Released

Fix Version(s):
Applications Manager 8.0.16 - Available

Additional Information

Workaround :
  • Downgrade the OS version or use another machine with a lower OS400 version
  • Run OS400 jobs manually
* * To run an OS400 job manually from the command line:
There is a command/lseries WRKJVMJOB. You can print the information from the job which runs the JVM. Then you can run the PM file in QSH output which sends it to the screen, where you can use PF6 to print it.