At TCPIP startup, why do we get the message EZZ0154I CONFIGURATION: UNABLE TO OPEN MESSAGE CATALOG ?

EZZ0154I indicates that the configuration component was unable to open the configuration message catalog "cfmsg.cat" in the message catalog directory. In that case, the configuration component will use the internal default messages instead of the messages from the external message catalog.

EZZ0154I can be issued if any of the following conditions have not been verified:

1. Was OMVS fully up BEFORE the stack was started? EZZ0154I can be issued if OMVS didn't fully initialize until part way through the stack startup. In that situation, EZZ0154I may be accompanied by message EZZ0159I CONFIGURATION: MESSAGE CATALOG CFMSG.CAT IS UNUSABLE, THE DEFAULT MESSAGES WILL BE USED Look for this message in your syslog: BPXI004I OMVS INITIALIZATION COMPLETE . Make sure it is issued before starting the stack.

2. The path being searched for is: /usr/lib/nls/msg/C/cfmsg.cat Does cfmsg.cat exist on your system? If you cannot locate cfmsg.cat, run EZAMKDIR, which will create the directories and the associated symbolic links required for the message catalog.

3. Make sure that the default location for the external message catalog is correctly set. To do that, verify that the NLSPATH environment variable is set as follows: NLSPATH=/usr/lib/nls/msg/%L/%N.
   

4. Ensure that the service level is correct: verify that the time stamp of the latest PTF in SMPE matches the time stamp on the catalog.