Solving problems

The following list includes some of the locale-related problems you might encounter when creating an instance or archiving data.

The cause of each possible problem is described, and the steps to recover from the problem are explained.

Problem: You receive the message: CPFA0A9 Object not found. LOCALE /QSYS.LIB/EN_GB_E.LOCALE NOT FOUND

Cause: You specified a locale that does not exist on the system.

Recovery: Either specify a locale that does exist on the system, or create the locale that you need using the CRTLOCALE command.

Problem: You receive the message: OND1005 OnDemand instance MYINSTANCE was not created. The qshell job log also contains OND0588 You must set a locale.

Cause: You did not specify a locale in the user profile creating the instance, or you did not signoff and signon again after changing the user profile to specify a locale.

Recovery: Delete the IFS directories created for the instance. Delete the instance user profile. Delete the instance authorization list.

Problem: Your data will not load into OnDemand. There is no system log message indicating the cause of failure. The job log for the load job does not contain a specific error message.

Cause: You do not have a locale specified in the user profile running the load job.

Recovery: Check the job log for the qshell job, QP0ZSPWP, for the error message OND0588 You must set a locale.. If the job log contains this message, you must change the user profile running the load job to specify a locale.

Problem: Your spooled file fails to archive. The system log contains message 88, including text similar to the following Row 1: The string " 1/12/13" could not be converted to a date from the format of %m/%d/%y. You check the Load Information tab in the application definition and see that the date format is specified as %y/%m/%d and that leading spaces are to be removed.

Probable Cause: The user profile archiving the data has a locale specified, but that locale is not compatible with the instance into which the data is being loaded. For example, specifying a Czech locale but trying to archive US English data will cause this type of failure. Note that you might, in fact, have an actual date definition error, but it is likely related to locales if you have already verified the date information as being correct.

Recovery: Specify a locale in the user profile archiving the data that is compatible with the instance into which the data is being archived.