Explanation
Netstat opened the message catalog successfully,
but the message catalog was not at the level that Netstat expected.
This message specifies the timestamp and service level that Netstat
expects to find. Netstat will use the default messages instead of
the messages from the message catalog.
In the message text:
- cat_name
- The name of the catalog that Netstat opened.
- service_level
- The FMID or PTF of the message catalog that Netstat expected to
find.
- expected_time
- The timestamp that Netstat expected to find in the message catalog.
The expected_time value is in the following format:
yyyy ddd hh:mmUTC
Where: - yyyy is the year
- ddd is the day (001 - 365)
- hh is the hour (01 - 24)
- mm is the minute (01 - 60)
System action
Operator response
Contact the system programmer.
System programmer response
To resolve this problem, do the following:
- Locate the message catalog. The default location for the message
catalog is the /usr/lpp/tcpip/lib/nls/msg/C/ directory. If the NLSPATH
environment variable is being used, the message catalog can be found
in one of the directories that is specified for NLSPATH.
- Examine the message catalog to find the timestamp and service
level of the catalog. The timestamp is on the first line of the message
catalog. The service level can be found by searching for the first
line with EZASERVICE as the first word. The message is in the format
EZASERVICE Service level is cat_level.
The cat_level is the service level of the message
catalog.
- After you find the timestamp and service level of the message
catalog, perform the following steps:
- If you are customizing the message catalog, be sure to include
the timestamp. See the information about customizing
message catalogs in z/OS Communications Server: IP Configuration
Guide for more information about translating message
catalogs.
- If the service level message cannot be found, the message catalog
is from a z/OS® release before z/OS V1R12. Verify that the correct
file system was mounted. The df directory_path command,
for example df /usr/lpp/tcpip/lib/nls/msg/C/, can
be used to determine which file system is mounted for the message
catalog directory.
- Compare the timestamp and service level of the message catalog
to the timestamp and service level shown in this message.
- If the two service levels are the same, contact IBM® software support center.
- Use the service levels to determine why the mismatch occurred
and correct the error. Possible causes are:
- A PTF was not applied successfully.
- The file system that is mounted does not contain the updated message
catalog.
- The SEZALOAD library does not contain the updated Netstat program.
- The SEZALOAD library and the file system are not at the same release
level.
User response
Contact the system programmer.
Problem determination
Source
z/OS Communications
Server TCP/IP: Netstat
Module
ezacdtne, ezacdone, ezacddne
Routing code
Descriptor code
Automation
If you are automating on Netstat console commands,
automation routines need to be aware of this message. If the automation
does not handle the default netstat messages, the automation might
need to not process the netstat output. You might want to automate
on this message to notify the system programmer about this problem.
Example
EZZ2394I Netstat was expecting netmsg.cat to be at service level HIP61C0 and 2010 041 03:53 UTC -
Netstat is using default messages