When installing the iSeries robot on an AS400 machine which is configured to use a non-English language, the robot may not start correctly and the controller.log may show a sockConnect failed error.
The controller.log may show that the domain has not been properly read from the config file (domain = none) and the controller may be trying to erroneously contact a hub at 127.0.0.1 instead of the proper hub IP:
or in some cases you may see a simple socket connection failure error such as:
Jun 21 15:50:24:875 Controller: ----- NimBUS controller 5.71 Jun 29 2012 started -----
Jun 21 15:50:24:875 Controller: Name = lxxxxxxxx, IP = 10.90.2.99, Port = 48000
Jun 21 15:50:24:875 Controller: OS = IBM / AS400 / AS400
Jun 21 15:50:24:875 Controller: Domain = none
Jun 21 15:50:24:875 Controller: Loglevel = 0, Logfile = controller.log
Jun 21 15:50:24:876 Controller: Running as user NIMBUS (640)
Jun 21 15:50:24:876 Controller: -----
Jun 21 15:50:24:884 Controller: Controller on lxxxxxxxx port 48000 started
Jun 21 15:50:24:892 Controller: send_internal_alarm: sockConnect failed
- In the above case, the controller may start but not the hdb or spooler processes
- AS400 language code
In order to correct this problem, for this case, the language "English Upper/Lowercase" (language code 2924) should be installed as a secondary language in the environment.
Then, the primary language of the user being used to install the robot should be set to "ENU" (US English) and the robot should be reinstalled.
Note that the CCSID on the systems should be set to standard English (00037)
After this, the robot should be able to interpret its config files and start correctly.
The task of configuring the primary/secondary language of the system(s) should be handled by the iSeries/AS400 administrator.
Note that after any changes are made to the language settings, the robot must be restarted for the change to take affect.
Changing the primary language on iSeries 7 systems:
|Language Identifier||Single-Byte CCSID||Mixed-byte CCSID||Language|
|ENU||00037||None||United States English|
Note that in one particular case, the Nimbus profile/ID created at the beginning of the install process:
...somehow had the CCSID value hardcoded at 37. The robots on those systems would not start up correctly but other robots started up just fine which did not have the hardcoded (via customized command) value.