ZMON Error Messages

Message 001 - Program aborted (location = <line#>)

Explanation:

This message is issued by ZMON when it cannot complete the task requested. The line code indicates the internal line of the ZMON program when the problem occurred. This line number may be useful in tracking the cause of the problem.

Action:

Investigate the cause of the program abort, correct the problem, and if necessary retry the failed ZMON operation. The cause of the abort will usually be given in the previous message from ZMON in the message log.

Message 002 - Resource manager (Rev <ZMON rev>) for ZCOM <ZCOM rev>

Explanation:

This message displays the revision code of the ZMON and ZCOM software.

Action:

None

Message 003 - Cold start with: <filename>

Explanation:

This message displays the name of the TTGEN output file used to cold start the ZCOM sub-system.

Action:

None

Message 004 - Waiting for ZMON requests ...

Explanation:

Message issued when ZMON has completed a COLD start or a QUEUE warm start and is ready to receive any events generated by the LDM.

Action:

None

Message 005 - Stopping system ...

Explanation:

Message printed as a result of ZMON STOP being issued.

Action:

None

Message 006 - Getting ZCOM system status ...

Explanation:

Message printed as a result of ZMON STATUS being issued.

Action:

None

Message 007 - Enable driver debug (level = <level>) ...

Explanation:

Message printed as a result of ZMON DEBUG being issued.

Action:

None

Message 008 - Disable driver debug ...

Explanation:

Message printed as a result of ZMON NODEBUG being issued.

Action:

None

Message 009 - Operator restart of interface card <number> ...

Explanation:

Message printed as a result of ZMON RESTART being issued. The operator has requested that an ACC card be restarted. That is, the card's firmware is re-downloaded onto the card.

Action:

None

Message 010 - Operator shutdown of interface card <number> ...

Explanation:

Message printed as a result of ZMON SHUTDOWN being issued. The operator has requested that the ACC card be halted. The card is no longer usable.

Action:

None

Message 011 - Can't open ZMON file: <reason>

Explanation:

Message printed during the ZMON cold start phase when ZMON cannot open the LDM device file (usually
/dev/zmon).

Action:

Correct the problem with the file, and retry the ZMON startup.

Message 012 - ZMON file: <filename>

Explanation:

Message displays the name of the ZMON device file used to access the ZCOM kernel memory. This file is usually /dev/zmon.

Action:

This message is usually preceded by message 011 describing the reason the file could not be opened. Correct the problem and retry the ZMON startup.

Message 013 - Can't create <file> <errno msg>

Explanation:

This message is displayed when zmon failed to create the ZMON device file (usually /dev/zmon).

Action:

Correct the problem associated with creating the zmon device file and retry.

Message 014 - Clean up ZCOM system before downloading ...

Explanation:

Message printed during the ZMON cold start phase when the ZCOM subsystem needs to be cleaned up before the downloading.

Message 020 - Cold start completed, ZCOM system ready

Explanation:

Message printed when ZMON has completed a cold start of the ZCOM sub-system.

Action:

None

Message 021 - Can't open memory file: <reason>

Explanation:

This message is logged when ZMON cannot open the TTGEN output file specified in the ZMON runstring (zmon cold <filename>). Normally another message will be logged immediately following this one which provides the specific reason for why the file could not be opened.

Action:

Correct the problem with the TTGEN output file and retry the ZMON startup.

Message 022 - Can't allocate scratch memory of <number> bytes

Explanation:

Message printed when ZMON cannot allocate local memory for processing the TTGEN output file.

Action:

Correct the memory shortage problem and retry the ZMON startup.

Message 023 - Memory file read error: <reason>

Explanation:

Message printed when ZMON cannot read data from the TTGEN memory image file. This may indicate a corrupt file.

Action:

Retry the ZMON startup. If this problem persists rerun TTGEN from the source TTGEN configuration file (.answ file) to rebuild the memory image file. When the file has been rebuilt, retry the ZMON startup.

Message 024 - Incomplete read from memory file

Explanation:

Message printed when ZMON cannot correctly read data from the TTGEN memory image file. This may indicate a corrupt file.

Action:

Retry the ZMON startup. If this problem persists rerun TTGEN from the source file (.answ file) to rebuild the memory image file. When the file has been rebuilt, retry the ZMON startup.

Message 025 - ZMON file write error: <reason>

Explanation:

Message printed when ZMON cannot write data to the ZMON LDM device file (usually /dev/zmon). This may indicate a corrupt TTGEN memory image file, or some internal inconsistency in the ZCOM LDM.

Action:

Retry the ZMON startup. If this problem persists rerun TTGEN from the source TTGEN configuration file (.answ file) to rebuild the memory image file. When the file has been rebuilt, retry the ZMON startup. If this still does not clear the problem try rebooting the HP-UX system; and then report the problem to HP.

Message 026 - Incomplete write to ZMON file

Explanation:

Message printed when ZMON cannot write data to the ZMON LDM device file (usually /dev/zmon). This may indicate a corrupt TTGEN memory image file, or some internal inconsistency in the ZCOM LDM.

Action:

Retry the ZMON startup. If this problem persists rerun TTGEN from the source TTGEN configuration file (.answ file) to rebuild the memory image file. When the file has been rebuilt, retry the ZMON startup. If this still does not clear the problem try rebooting the HP-UX system; and then report the problem to HP.

Message 027 - Bad revision (memory file is for ZCOM <rev codes>)

Explanation:

Message printed when ZMON finds an inconsistency between the ZCOM version number in the software and the version in the TTGEN file header. Most likely, the TTGEN output file was generated with an older (and incompatible) version of the ZCOM software than the version currently be used.

Action:

Rerun TTGEN on the configuration file (.answ) corresponding to the output file and attempt to startup the ZCOM sub-system using zmon. If this fails, ensure that the version of ZCOM software is consistent (i.e. check that there are not old versions of some or all of the ZCOM software loaded). Remove inconsistent software or replace with consistent version, then retry the ZMON startup.

Message 028 - Not a ZCOM memory file

Explanation:

Message printed when ZMON cannot identify the header in the TTGEN memory image file passed in the COLD start run string (zmon cold <filename>). The most likely reason is that the file name is wrong or the file is not the output from TTGEN.

Action:

Correct the file name, or rerun TTGEN to produce a correct file, then retry the ZMON startup.

Message 029 - ioctl(memory) error: <ZCOM error>

Explanation:

Message is displayed when ZMON encounters a memory error when configuring the ZCOM kernel memory. The usual cause is insufficient memory (Not enough memory for this configuration) in the zcom_mem_size parameter in the system file used to build your kernel (usually /stand/system).

Action:

Either increase the zcom_mem_size parameter in your "system" file, then rerun mk_kernel and reboot; or reduce the memory requirements (esp. buffer pool size) in the TTGEN configuration file (.answ file) and rerun TTGEN. Then retry the ZMON startup.

Message 030 - ioctl(init) error: <zcom error>

Explanation:

Message is displayed when ZMON receives an error from the LDM during the initialization of the ZCOM sub-system. After displaying this error, ZMON will terminate.

Action:

Rerun TTGEN and rebuild the memory image file (.tmem). Then retry the ZMON startup. If this still does not clear the problem try rebooting the HP-UX system; and then report the problem to HP.

Message 031 - ioctl(start) error: <zcom error>

Explanation:

Message is displayed when ZMON receives an error from the LDM during the initialization of the ZCOM sub-system. After displaying this error, ZMON will terminate.

Action:

Rerun TTGEN and rebuild the memory image file (.tmem). Then retry the ZMON startup. If this still does not clear the problem try rebooting the HP-UX system; and then report the problem to HP.

Message 040 - ioctl(getirr) error: <zcom error>

Explanation:

This message is displayed when ZMON receives an error while reading an event from the LDM interface request queue. After displaying this error, ZMON will terminate.

Action:

Restart ZMON with ZMON QUEUE. If this still does not clear the problem try rebooting the HP-UX system; and then report the problem to HP.

Message 041 - Request at <date/time> - restart card <card number>

Explanation:

Message is displayed as a result of an LDM generated event (such as powerfail) to restart a Mux card.

Action:

None

Message 042 - Card <number>: card number out of range, request ignored

Explanation:

Message displayed as a result of the ZMON request being issued with a Mux number larger than the number of muxes (actually N-1) configured in the TTGEN memory image file.

Action:

If problem persists report it to HP.

Message 043 - Card <number> ZMON file open error: <reason>

Explanation:

Message is displayed if ZMON is unable to open the /dev/zmon file after it receives an event message from the LDM event queue. If this error is reported, than the card needing attention will not be restarted.

Action:

Manually issue a ZMON RESTART request to the Mux card number reported in the message. If the problem persists, check that the file /dev/zmon exists and has the correct access permissions. Rectify the file problems if possible.

Message 044 - Request at <date/time> - startup card <card number>

Explanation:

This message is displayed whenever the Dynamic System Configuration function enable interface is performed. This indicates that the specified interface card is to be restarted.

Action:

None

Message 045 - Request at <date/time> - disable card <card number>

Explanation:

This message is displayed whenever the Dynamic System Configuration function disable interface is performed. This indicates that an application has dynamically (programmatically) shutdown the specified interface card.

Action:

None

Message 046 - Request at <date/time> - shutdown card <card number>

Explanation:

This message is displayed whenever the Dynamic System Configuration function clear interface is performed. This indicates that an application has dynamically (programmatically) flushed all I/O requests and shutdown the specified interface card.

Action:

None

Message 048 - Request at <date/time> - unknown request <code>

Explanation:

Message is displayed if the LDM passes ZMON a restart event code that it does not recognize.

Action:

None. If problem persists report it to HP.

Message 049 - End of ZMON request, program terminated

Explanation:

This message is displayed when a request has been issued to shutdown the ZCOM sub-system.

Action:

None

Message 050 - Card number out of range, restart ignored

Explanation:

Message printed as a result of the ZMON RESTART request being issued with an invalid card (MUX interface) number.

Action:

Reissue the RESTART request with the correct card number.

Message 051 - Card number out of range, shutdown ignored

Explanation:

Message printed as a result of the ZMON SHUTDOWN request being issued with a Mux number larger than the number of muxes (actually N-1) configured in the TTGEN memory image file.

Action:

Reissue the SHUTDOWN request with the correct card number.

Message 052 - Card <number> shutdown completed

Explanation:

Message printed as a result of the ZMON SHUTDOWN request being issued. Once this message appears the card is shutdown and the amber LED is flashing on the back of the card. The card may be restarted using the ZMON RESTART command.

Action:

None

Message 060 - ioctl(status) error: <zcom error>

Explanation:

Message is displayed after a ZMON STATUS request is issued and ZMON cannot successfully read the ZCOM status.

Action:

If problem persists report it to HP.

Message 061 - Status since <date/time> - Aborted (must reset)

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This status means that the ZCOM system has failed during a previous startup, and is unusable.

Action:

A cold start is needed to bring up an usable ZCOM system.

Message 062 - Status since <date/time> - Ready (running)

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This status indicates that the ZCOM system has been successfully started up and is available for normal operations.

Action:

None

Message 063 - Status since <date/time>- Being reset

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This is a transient status that indicates the ZCOM is being stopped.

Action:

None

Message 064 - Status since <date/time> - Booted up

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This is the initial status of ZCOM system when the machine is first booted up. The system is non-operational.

Action:

A cold start is needed to bring up an usable ZCOM system.

Message 065 - Status since <date/time> - Reset (stopped)

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This indicates the system has been stopped. The system is non-operational.

Action:

A cold start is needed to bring up an usable ZCOM system.

Message 066 - Status since <date/time> - Starting up

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This is a transient status that indicates the ZCOM system is being started up.

Action:

None

Message 067 - Status since <date/time> - Initialized (idling)

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This is also a transient status that indicates the ZCOM system is being started up.

Action:

None

Message 068 - Status since <date/time> - Unknown (0x<hex code>)

Explanation:

Message printed as a result of the ZMON STATUS request being issued. This message indicates the ZCOM system is in an unknown state.

Action:

Report the problem to the nearest HP representative.

Message 070 - ioctl(debug) error: <zcom error>

Explanation:

Message printed as a result of the ZMON DEBUG request being issued. The message indicates the IOCTL request to enable the debug has failed.

Action:

Report the problem to the nearest HP representative.

Message 071 - ZCOM driver debug enabled

Explanation:

Message printed as a result of the ZMON DEBUG request being successfully issued.

Action:

None

Message 072 - ioctl(nodebug) error: <zcom error>

Explanation:

Message printed as a result of the ZMON NODEBUG request being issued. The message indicates the IOCTL request to disable the debug has failed.

Action:

Report the problem to the nearest HP representative.

Message 073 - ZCOM driver debug disabled

Explanation:

Message printed as a result of the ZMON NODEBUG request being successfully issued.

Action:

None

Message 074 - ioctl(reset) error: <zcom error>

Explanation:

Message printed as a result of a ZCOM reset request being issued. The message indicates the IOCTL request to reset the ZCOM system has failed.

Action:

Report the problem to the nearest HP representative.

Message 075 - ZCOM system stopped

Explanation:

Message printed as a result of the ZMON STOP request being issued.

Action:

None

Message 100 - Card <number> starting up ...

Explanation:

Message displayed to indicate a Mux card is being started or restarted.

Action:

None

Message 101 - Card <number> can't read IFT record: <reason>

Explanation:

During the restart/shutdown of a Mux card, ZMON needs to retrieve the card configuration information. This information is contained in the ZCOM IFT (interface table) and must be read via the /dev/zmon device file. This error indicates the read has failed for some reason. The restart/shutdown of the card is abandoned if this error is encountered.

Action:

Report the problem to the nearest HP representative.

Message 102 - Card <number> partial read of IFT record

Explanation:

During the restart/shutdown of a Mux card ZMON reports the last backplane activity that the DAM attempted to the card. This information is contained in the ZCOM IFT (interface table) and must be read via the /dev/zmon device file. This error indicates the read has failed for some reason. The restart/shutdown of the card is abandoned if this error is encountered.

Action:

Report the problem to the nearest HP representative.

Message 103 - Card <number> inconsistent or corrupted IFT

Explanation:

During the restart/shutdown of a Mux card ZMON reports the last backplane activity that the DAM attempted to the card. This information is contained in the ZCOM IFT (interface table) and must be read via the /dev/zmon device file. This error indicates the read has failed for some reason. The restart/shutdown of the card is abandoned if this error is encountered.

Action:

Report the problem to the nearest HP representative.

Message 104 - Card <number> restart ignored because card is unusable

Explanation:

ZMON is unable to restart the Mux card because of a hardware or configuration problem. If any selftest failures or timeouts have been reported there may be a hardware problem. If the card is reported as absent, then the problem may be simply that the card is not installed, or not installed in the correct slot. The ACC driver space file information under /usr/conf/space.h.d may be inconsistent with the TTGEN configuration file (.answ). Check the ioscan-f output against the Mux statements in the .answ file. ZMNTR can display the Mux configuration with the MX command.

Action:

Replace hardware or correct configuration problem; then restart ZCOM system.

Message 105 - Card <number> can't open device: <reason> Device file <name of file>

Explanation:

ZMON is unable to open the device file for Mux <number>. The reason given is the explanation of a file system error that is preventing access to the file (e.g. file does not exist, or permissions problem).

Action:

Correct the problem and restart the ZCOM system.

Message 106 - Card <number> request ignored because IFT is not initialized

Explanation:

ZMON tries to process a startup or shutdown request for an interface card, but the card information is not defined (e.g. it is skipped in the TTGEN configuration file). The card information is contained in the ZCOM IFT (interface table), and can be read via the /dev/zmon device file. This error indicates the IFT is not set up. The startup or shutdown of the card is abandoned if this error is encountered

Action:

ZMON expects the cards of number 0,1,2,... up to the largest card number are all defined in the TTGEN configuration file. ZMON logs this message if any card number in-between is not defined. This message can just be ignored if it is intentional to skip an interface card definition. Otherwise, the appropriate information with the missing card number should be defined in the Interface-Definition section of the TTGEN configuration file.

Message 107 - Card <number> too many restarts, card DOWN (unusable)

Explanation:

The ZCOM system allows about 5 restarts of a Mux card per minute. If the number of restarts exceeds this value ZMON assumes there is a serious problem with either the Mux card hardware or software and will abandon its attempts to continue to restart the card.

Action:

If the problem is as a result of a software error in the Mux card the download module can be replaced with a good version and the Mux card restarted using the ZMON RESTART request. If the problem is hardware related the Mux card must be replaced.

Message 108 - Card <number> startup aborted

Explanation:

ZMON has abandoned the Mux startup. The reason will be given in a previous message.

Action:

Take action appropriate to the reason given in the previous message(s).

Message 109 - Card <number> request ignored because it's an old request

Explanation:

ZMON displays this message when it receives an Interface Restart Request (IRR) and finds that the current system is already restarted AFTER the time when this IRR is generated. This usually happens when there are multiple IRRs generated during a card startup (e.g. an unstable card may fail a few times during its startup). The first IRR causes ZMON to restart the card, so all the repeated ones can be ignored.

Action:

None. This message is for information only. It implies the a card failed multiple times during restart. If this happens persistently on a particular card, it could mean the card may have a hardware (or firmware) problem.

Message 110 - Card <number> startup successful, card READY

Explanation:

The Mux card has been successfully started and is ready for use.

Action:

None

Message 111 - Card %d Last BP command: <Hex command codes>

Explanation:

The Mux card hardware or software has failed for some reason. The hex codes are displayed for diagnostic purposes. These codes represent the last backplane command executed by the driver (DAM). This information may be useful in determining the cause of the failure.

Action:

Report these values to HP to assist in diagnosing the reason for the failure.

Message 112 - Card <number> Current ports: Hi-Pri <number> Lo-Pri <number>

Explanation:

The Mux card hardware or software has failed for some reason. These port numbers represent the last ports accessed by the driver. This information may be useful in determining the cause of the failure.

Action:

Report these values to HP to assist in diagnosing the reason for the failure.

Message 113 - Card <number> Current terminal: ZLU <number> Port <number> Term <number>

Explanation:

The Mux card hardware or software has failed for some reason. These port and terminal numbers represent the those last accessed by the driver. This information may be useful in determining the cause of the failure.

Action:

Report these values to HP to assist in diagnosing the reason for the failure.

Message 114 - Card <number> Bad current PTT pointer 0x<address>

Explanation:

The driver has passed a bad terminal number value to ZMON and it is unable to find the physical terminal table entry (PTT).

Action:

Report these values to HP to assist in diagnosing the reason for the failure.

Message 115 - Card <number> Current ports: Expr-Pri 0x<#>, Hi-Pri 0x<#>, Lo-Pri 0x<#>

Explanation:

The Mux card hardware or software has failed for some reason. The hex codes are displayed for diagnostic purposes. These codes represent the last backplane command executed by the driver (DAM). This information may be useful in determining the cause of the failure.

Action:

Report these values to HP to assist in diagnosing the reason for the failure.

Message 118 - Card <number> control request overridden by other request

Explanation:

When there are multiple card control requests issued to ZMON at the same time, a later one may override the one already in-progress, if appropriate. For example, when ZMON is restarting a card and a "zmon shutdown ..." is issued on the same card, the first RESTART request will be aborted by the second SHUTDOWN required. ZMON logs this message to indicate that the first request was overridden.

Action:

None. This message is for information only. ZMON indicates the previous request is cancelled. Usually this message will be followed by Message 108.

Message 120 - Card <number> shutting down ...

Explanation:

The Mux card is being shut down as a result of a ZMON STOP or ZMON SHUTDOWN command.

Action:

None

Message 128 - Card <number> being flushed and set to unavailable

Explanation:

This message is displayed during a MUX card shutdown. It indicates the buffers in the interface table are being flushed, and the terminals linked to the MUX are being set to unavailable.

Action:

None

Message 140 - ioctl(status) error: <reason>

Explanation:

Message is displayed when ZMON checks the ZCOM systems status before attempting to execute some of the ZMON commands. In this case, the IOCTL failed with the reason given.

Action:

Report the problem to HP.

Message 141 - ZCOM system is not running

Explanation:

Message is displayed when a ZMON request is issued (for example, ZMON RESTART) when ZCOM is not running.

Action:

Restart the ZCOM system.

Message 142 - Can't read ZCOM system header: <reason>

Explanation:

Message is displayed when ZMON fetches the ZCOM header record before attempting to execute some of the ZMON commands. In this case the request failed with the reason given.

Action:

Report the problem to HP.

Message 143 - Partial read of ZCOM system header

Explanation:

Message is displayed when ZMON fetches the ZCOM header record before attempting to execute some of the ZMON commands.

Action:

Report the problem to HP.

Message 144 - Bad ZCOM system header label

Explanation:

Message is displayed when ZMON fetches the ZCOM header record before attempting to execute some of the ZMON commands.

Action:

Report the problem to HP.

Message 201 - Card <number> disable error: <reason>

Explanation:

Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 202 - Card <number> enable error: <reason>

Explanation:

Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field.

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 203 - Card <number> reset error: <reason>

Explanation:

Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field.

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 204 - Card <number> restart error: <reason>

Explanation:

Message is displayed when ZMON is attempting to begin execution of the Mux card firmware and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is explained in the <reason> field. If the reason is "Bad response from mux card", then the problem may be due to internal firmware memory allocation checks failing, which will prevent the firmware from correctly initializing.

Action:

Take appropriate action to rectify the problem and restart the ZCOM system. In the case of the firmware checks failing, check any internal memory allocations specified for this card.

Message 205 - Card <number> activate error: <reason>

Explanation:

Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field.

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 206 - Card <number> set-ready error: <reason>

Explanation:

Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field.

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 207 - Card <number> halt error: <reason>

Explanation:

Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field.

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 208 - Card <number> flush error: <reason>

Explanation:

Message is displayed when ZMON is flushing a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field.

Action:

Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.

Message 221 - Card <number> Hard error - card is unusable

Explanation:

Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not work.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 222 - Card <number> Port controller test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 223 - Card <number> Programmable Reload Timer failed

Explanation:

Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 224 - DMA memory-to-memory test failed

Explanation:

Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 225 - Loopback test failed

Explanation:

Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 226 - Card <number> RAM test failed

Explanation:

Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 227 - Card <number> ROM checksum mismatch

Explanation:

Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 231 - Card <number> Port <number> DSR signal missing

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 232 - Card <number> Port <number> External clock test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 233 - Card <number> Port <number> DTR signal missing

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 234 - Card <number> Port <number> RTS signal missing

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 235 - Card <number> Port <number> RS422 external loopback test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 236 - Card <number> Port <number> RS232 DMA external loopback test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 237 - Card <number> Port <number> RS232 external loopback test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 238 - Card <number> Port <number> RS232 internal loopback test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 240 - Card <number> can't read ROM label: <reason>

Explanation:

Before downloading the Mux card ZMON attempts to read the ROM label of the firmware on the Mux card. In this case the read has failed for the reason given.

Action:

Take the appropriate action to rectify the problem and restart the Mux card or ZCOM system.

Message 241 - Card <number> $DWNL (upload) gives non-zero reply

Explanation:

Before downloading the Mux card ZMON attempts to read the ROM label of the firmware on the Mux card. In this case the read has failed.

Action:

Take the appropriate action to rectify the problem and restart the Mux card or ZCOM system.

Message 242 - Card <number> can't open firmware file: <reason>

Explanation:

Message issued when ZMON encounters a problem opening the firmware download file for the Mux card.

Action:

Fix the problem with the file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 243 - Card <number> firmware file: <name>

Explanation:

Message issued when ZMON encounters a problem with the firmware download file for the Mux card. This message will be associated with one describing the problem.

Action:

None

Message 244 - Card <number> firmware file read error: <reason>

Explanation:

Message issued when ZMON encounters a problem reading a record from the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 245 - Card <number> firmware file read error: corrupted record

Explanation:

Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 246 - Card <number> bad firmware file record length in record <number>

Explanation:

Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 247 - Card <number> error in download: <reason>

Explanation:

Message issued when ZMON encounters a problem when writing the firmware download file to the Mux card. The problem may be caused by a problem with the download file, the device file to the LDM, or a hardware problem on the card itself. The Mux will be unusable until the problem is rectified.

Action:

Take the appropriate action to rectify the problem and restart the Mux card or ZCOM system.

Message 248 - Card <number> $DWNL (download) gives non-zero reply

Explanation:

Message issued when ZMON encounters a problem when writing the firmware download file to the Mux card. The problem may be caused by a problem with the download file, the device file to the LDM, or a hardware problem on the card itself. The Mux will be unusable until the problem is rectified.

Action:

Take the appropriate action to rectify the problem and restart the Mux card or ZCOM system.

Message 249 - Card <number> firmware object file <file-name> not executable

Explanation:

Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 250 - Card <number> COFF header access error on <file-name>

Explanation:

Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 251 - Card <number> Cannot seek raw data for section <section-name>

Explanation:

Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 252 - Card <number> Short raw data in section <section-name>

Explanation:

Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 260 - Card <number> dumped to <dump-file-name>

Explanation:

When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. This message is displayed after ZMON has successfully dumped the contents of the interface memory to a file in this directory, and gives the dump file name.

Action:

None

Message 261 - Card <number> can't open dump file: <reason>

Explanation:

Message is generated if ZMON is unable to open the Mux memory dump file. The Mux memory dump will be skipped but the recovery of the Mux card will proceed.

Action:

If future Mux dumps are to succeed then the problem must be rectified.

Message 262 - Card <number> dump file error: <reason>

Explanation:

Message is generated if ZMON is unable to write to the Mux memory dump file. The rest of the Mux memory dump will be skipped but the recovery of the Mux card will proceed.

Action:

If future Mux dumps are to succeed then the problem must be rectified.

Message 263 - Card <number> dump file error: corrupted record

Explanation:

Message is generated if ZMON is unable to write to the Mux memory dump file. The rest of the Mux memory dump will be skipped but the recovery of the Mux card will proceed.

Action:

If future Mux dumps are to succeed then the problem must be rectified.

Message 264 - Card <number> error in upload: <reason>

Explanation:

Message is generated if ZMON is unable to read from the Mux card during the Mux memory dump. The dump sequence will be retried once, after resetting the interface. The problem is most likely to be a hardware or firmware related issue. It may be that the Mux software or firmware has failed in such a way that the upload for the dump is not possible.

Action:

The reset of the Mux card prior to the dump retry or next download may fix the problem. If this has no effect, the Mux card may be defective and require replacement.

Message 265 - Card <number> $DWNL (upload) gives non-zero reply

Explanation:

Message is generated if ZMON is unable to read from the Mux card during the Mux memory dump. The dump sequence will be retried once, after resetting the interface. The problem is most likely to be a hardware or firmware related issue. It may be that the Mux software or firmware has failed in such a way that the upload for the dump is not possible.

Action:

The reset of the Mux card prior to the dump retry or next download may fix the problem. If this has no effect, the Mux card may be defective and require replacement.

Message 266 - Card <number> deleting dump <dump-file-name>

Explanation:

When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. This message is displayed as ZMON deletes a dump file which is incomplete, because of an earlier error which occurred during the dump process.

Action:

None.

Message 267 - Card <number> bad dump file <dump-file-name>

Explanation:

When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. This message is displayed because ZMON has detected an error in the dump process, and the dump file is not complete.

Action:

None.

Message 268 Card <number> dump file compression (gzip) successful

Explanation:

When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. After ZMON has successfully created the dump file, it compresses the dump file if "gzip" is accessible. This message is displayed after the compression is successful.

Action:

None

Message 269 Card <number> dump file compression (gzip) error <number>

Explanation:

When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. After ZMON has successfully created the dump file, it compresses the dump file if "gzip" is accessible. This message is displayed in case "gzip" exits with a non-zero error <number>.

Action:

Investigate the problem with gzip. The original dump file should remain in the /var/opt/acc/dmp directory.

Message 270 Card <number> dump can't fork to gzip: <reason>

Explanation:

When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. After ZMON has successfully created the dump file, it forks a child process to run gzip to compresses the dump file. This message is displayed when ZMON cannot create the child process.

Action:

This may relate to an operating system resource problem. Investigate and rectify the problem, or else system operation may be affected. The original dump file should remain in the /var/opt/acc/dmp directory.

Message 271 - Card <number> Port <number> FALC framing test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 272 - Card <number> Port <number> Unknown port test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 273 - Card <number> Port <number> Unknown port test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 274 - Card <number> Port <number> Unknown port test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 275 - Card <number> Port <number> Unknown port test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 276 - Card <number> Port <number> Line loop test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 277 - Card <number> Port <number> FALC internal loop test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 278 - Card <number> Port <number> Munich internal loop
test failed

Explanation:

Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.

Action:

At a convenient time, shutdown the system and replace the Mux card. Note other Mux cards (if any) will continue operating normally.

Message 280 - ioctl (response) error: <reason>

Explanation:

This message is logged when ZCOM was unable to send a response to the LDM for ZMON request that requires a completion response. The message contains the reason why the IOCTL request failed.

Action:

Examine the reason for the failure and correct if possible. If this appears to be an internal defect of the product, report the problem to your nearest HP support representative.

Message 290 - Get zmon semaphore failure, <errno msg>

Explanation:

This message is displayed when ZMON failed to obtain the zmon semaphore ID.

Action:

Report this problem to Hewlett Packard.

Message 291 - zmon daemon is already active, terminating this copy.

Explanation:

This message is generated if the user tries to issue another command to download the ZCOM subsystem when the ZCOM subsystem has already been downloaded and the zmon daemon is running.

Action:

None, unless the user wants to shutdown the ZCOM subsystem and restart it anew.

Message 292 - Can't get zmasterd's message queue ID.

Explanation:

This message is displayed when ZMON failed to get the zmasterd's message queue ID.

Action:

Report this problem to Hewlett Packard.

Message 293 - Failed to send message to zmasterd, <errno msg>

Explanation:

This message is displayed when ZMON failed to send message to zmasterd.

Action:

Report this problem to Hewlett Packard.

Message 294 - Failed to get sema ID for download, error: <errno msg>

Explanation:

This message is displayed when ZMON failed to allocate a semaphore id used to synchronize the interface download.

Action:

Report this problem to Hewlett Packard.

Message 295 - Download get semaphore failed error: <errno msg>

Explanation:

This message is displayed when ZMON is unable to allocate a semaphore id used to synchronize the interface download.

Action:

Report this problem to Hewlett Packard.

Message 296 - Download release semaphore failed error: <errno msg>

Explanation:

This message is displayed when ZMON is unable to deallocate a semaphore id used to synchronize the interface download.

Action:

Report this problem to Hewlett Packard.

Message 300 - Card <number> Invalid BC or Card address in TTGEN file

Explanation:

The Bus Converter or Card address specified for card <number> in the ttgen .answ file is invalid, and does not exist.

Action:

Correct the Bus Converter or Card Address, re-run ttgen, and restart the ZCOM system.

Message 301 - Card <number> No ACC card at <bus-addr> card address <addr>

Explanation:

There is no ACC card at the address <addr> in the Bus Converter <bus-addr>.

Action:

Either correct the configuration in the ttgen .answ file, or correct the hardware configuration.

Message 302 - Card <number> No ACC card at BC address <bus-addr>
address <addr>

Explanation:

There is no ACC card at the address <addr> in the Bus Converter <bus-addr>.

Action:

Either correct the configuration in the ttgen .answ file, or correct the hardware configuration.

Message 310 - Card <number> Tables (<size>) exceeds free memory (<size>)

Explanation:

The user is able to reconfigure the internal firmware table memory allocation, as specified in the Utilities Reference Guide. In reconfiguring these internal memory allocations for this card, the sum of the allocated dynamic memory tables has exceeded the available free memory.

Action:

You must reduce the memory you attempted to allocate (given by the first number) to less then or equal to the dynamic memory available (as given by the second number). After re-running ttgen, you must restart the ZCOM subsystem.

Message 311 - Card <number> Warning: only <number> buffers available

Explanation

The user is able to reconfigure the internal firmware table memory allocation, as specified in the Utilities Reference Guide. In reconfiguring these internal memory allocations for this card, you have directly or indirectly caused the number of ACC card buffers to be reduced to less than 8,000. Below this number of buffers, the normal operation of the ACC card may be compromised.

Action

Reduce the memory you attempted to allocate to other resources (e.g. terminal tabels, message headers, trace buffer), or decrease the buffer size (zbufsize), in order to be able to increase the number of ACC buffers. Depending on the card type, you may need to specify this number using the zbufnbr interface tunable parameter. After re-running ttgen, you must restart the ZCOM subsystem.

Message 312 - Card <number> Unsupportable dynamic memory configuration

Explanation

This message applies to the Z7340A 8 port PCI ACC card only. The user is able to reconfigure the internal firmware table memory allocation, as specified in the Utilities Reference Guide. You have chosen a dynamic memory configuration which cannot be supported because of the internal memory arrangement of this ACC card. The 16 megabytes of memory is arranged into 2x8 megabyte segments. The second segment may only contain the firmware trace area and ACC buffers. The memory configuration you have specified attempts to allocate other resources into this second segment. In addition, the trace buffer cannot be larger than the second memory segment.

Action

Reduce the memory you attempted to allocate to resources other than buffers and trace buffer (e.g. message headers, timers, terminal tables), and/or reduce the size of the trace buffer. This will allow the second memory segement to be allocated only to buffers and the trace buffer. After re-running ttgen, you must restart the ZCOM subsystem.

Message 320 - Incompatible firmware key table

Explanation:

This message is displayed when ZMON is processing the contents of the firmware download file, and detects an error in the format of the embedded firmware keys table.

Action:

Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.

Message 321 - Cannot open key file <file-name>: <errno msg>

Explanation:

Message display when ZMON detects a problem in opening firmware keys file with the given name.

Action:

Replace the firmware keys file from a backup copy. If a backup copy of the file is not available, then the software may need to be re-installed. You will not be able to download this class of interface without access to this file.

Message 322 - Insufficient key data in file <file-name>

Explanation:

The firmware keys file given is corrupt. This file is required to correctly download this class of interface.

Action:

You must recover a valid copy of this file, or re-install the ACC software.

Message 323 - Protocol %d key entry is corrupt

Explanation:

The firmware keys file given is corrupt. This file is required to correctly download this class of interface.

Action:

You must recover a valid copy of this file, or re-install the ACC software.

Message 330 - Error invoking helper script: <script-name>. Errno <errno>: <errno msg>

Explanation:

An error has occurred as zmon attempts to open the script file <script-name>, which zmon uses to perform some bus address checking. The file system error <errno> has occurred, with explanation <errno msg>.

Action:

Correct the file system problem, and restart the ZCOM system.

Message 331 - Warning: Reached limit, <number>, on the number of installed ACC cards that can be included in the bus-address checking.

Explanation:

The configuration you are attempting to initialize has more ACC cards defined than can be processed in an internal table which zmon uses to verify bus addresses.

Action:

Zmon will continue processing, but you may have other errors which cannot be detected.

Message 332 - Error occurred reading output from the helper script <script-name> Errno <errno>: <errno msg>

Explanation:

A file system error has occurred in reading the output from the script <script-name>. The file system error <errno> has occurred, with explanation <errno msg>

Action:

Take appropriate action to correct the file system error, and restart the ZCOM system. If this error recurs, contact HP support.

Message 333 - Error: Unexpected input from helper script: <script-name> Expected card type. Input line: <string>

Explanation:

The unexpected input <string> was read as output from the script <script-name>. A card type was expected.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 334 - Error: Unrecognized card type: <card_type> from helper script: <script-name> Input line: <string>

Explanation:

Output read form the script <script-name> was <string>, rather than one of the recognized card types.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 335 - Error: Missing bc1/bc bus address field. Input line: <string> From helper script: <script-name>

Explanation:

Output read form the script <script-name> was <string>, rather than bus converter address.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 336 - Could not convert bc/bc1 value, <bc-string> to an integer. Errno <errno>: <errno msg> Input line: <string> from helper script: <script-name>

Explanation:

The string <bc-string> is expected to be a valid integer. The file system error <errno> with explanation <errno msg> has occurred in converting this string to an integer.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 337 - Error: Missing expected bc/card bus address field. Input line: <string> from helper script: <script-name>

Explanation:

Output read form the script <script-name> was <string>, rather than bus converter address.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 338 - Could not convert bc/card value, <bc-string> to an integer. Errno <errno>: <errno msg> Input line: <string> from helper script: <script-name>

Explanation:

The string <bc-string> is expected to be a valid integer. The file system error <errno> with explanation <errno msg> has occurred in converting this string to an integer.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 339 - Could not convert string card value, <card-string> to an integer. Errno <errno>: <errno msg> Input line: <string> from helper script: <script-name>

Explanation:

The string <card-string> was parsed as a card address from the input line <string> from script <script-name>. A file system error <errno> with explanation <errno msg> was diagnosed in attempting to convert it to an integer.

Action:

Verify that the script file has not been corrupted. If the problem recurs, contact HP support.

Message 340 - Error: ACC card <number> in your ttgen .answ file with bus address <bc1>:<bc>:<addr> does not match the type of the card located at that bus address in this system or specifies a card that does not exist in this system. Please verify that the bus address of this card in your ttgen file are correct.

Explanation:

The specified ACC card <number> has an incorrect hardware address for the system on which it is attempting to run.

Action:

Correct either the hardware address in the ttgen .answ file, or the hardware configuration. Examine the output of the ioscan(1M) -f command to verify the hardware addresses of the ACC cards installed on the system. This ACC card will be unusable until you restart the ZCOM system.

Message 400 - File: <file-name>. Line: <number>: <string>

Explanation:

This is an internal trace message.

Action:

None.