MKMSGF
HEXPLANATION: The hardware vital product data for your workstation
could not be obtained from the VPD.INI file, or the VPD.INI file
could not be found.
ACTION: Run EPWINST and provide all requested hardware information
to update the VPD.INI file.
HEXPLANATION: A semaphore error occurred.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The LAN adapter could not be opened.
ACTION: Make sure you have installed the LAN adapter and that
your LAN software is properly installed and configured.
HEXPLANATION: Unable to determine the LAN adapter's address.
ACTION: Make sure you have installed and properly configured
the LAN adapter.
HEXPLANATION: A LAN Service Access Point (SAP) could not be opened.
ACTION: Make sure that your LAN software and hardware are properly
installed and configured.  You may need to alter your configuration
to increase the SAP upper limit.  Also ensure that not all SAPs have
been consumed by one or more other applications.
HEXPLANATION: An alert could not be transmitted over the LAN.
ACTION: Make sure that your LAN software and hardware are properly
installed and configured.  Make sure that a LAN management program
is running on an accessable node to receive and/or forward the alerts.
HEXPLANATION: An alert could not be sent via Communications Manager
using APPC.
ACTION: Make sure Communications Manager is properly configured
to transmit alerts.  APPC must be loaded, and the DLC parameters
may need to be updated.  In particular, make sure the I-field
size is AT LEAST 521 bytes (the default is 1033 bytes).
HEXPLANATION: A required Dynamic Link Library (DLL) could not be loaded.
ACTION: Reinstall or copy the indicated file to a directory specified
by the LIBPATH statement in the CONFIG.SYS file.
HEXPLANATION: A procedure address in a Dynamic Link Library (DLL)
could not be found.
ACTION: Reinstall the product, and make sure it is supported on the
version of OS/2 that you are running.
HEXPLANATION: The alert queue is full.  This indicates that alerts
are either not being processed at all or not quickly enough by
communications software (locally or remotely).
ACTION: Deactivate the alert router using the command 'EPWROUT 0'.
HEXPLANATION: The alert could not be transmitted.
ACTION: Make sure your communications software and hardware (both
local and remote) is functional and properly configured to transmit
alerts.
HEXPLANATION: The alert queue could not be read.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: An alert could not be written to the alert queue.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The alert queue could not be created.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The alert queue could not be opened.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The router is unable to read from the pipe.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The router is unable to write to the alert queue.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The router is unable to acquire the pipe semaphore.
ACTION: Report the symptom string in the matching error log entry
to your service representative.
HEXPLANATION: The OS/2 Error Logging Facility is probably not
installed on your workstation.
ACTION: Add the necessary statements to your CONFIG.SYS file to
enable the OS/2 Error Logging Facility.  For OS/2 1.3, see the
documentation for the 'LOG' command in the OS/2 Command
Reference.  For OS/2 2.0, type the 'SYSLOG' command to get the
required statements.
IEXPLANATION:  The Alert Block has been dumped to an EPW Dump File
for reference purposes.
ACTION: Look in the EPWROUT.DMP file for a description of the Alert
Block.
EEXPLANATION: An error occurred while attempting to connect to EPW.
ACTION: Be sure that EPW has been installed and initiated.
EEXPLANATION: An error occurred while attempting to open a file. This
could be due to lack of sufficient disk space.
ACTION: Ensure that there is ample disk space available.