Chapter 119 TLAM (Tandem LAN Access Method/Multilan) Messages
| | |
| ||
| ||
The messages in this chapter are sent by the Tandem LAN Access Method (TLAM)/Multilan subsystem.
| |
| |
| |
 | NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15. |
| |
| |
| |
The subsystem ID displayed by these messages includes TLAM as the subsystem name. Message numbers and headers can help you identify which component of the TLAM/Multilan subsystem sent the message. The list below describes TLAM/Multilan message numbers and headers.
Messages 1 through 22, 186 through 188, and 191 have the header TLAM:MLAM. These messages are associated with the Multilan Access Method (MLAM).
Messages 23 through 92, 179 through 184, and 190 have the header TLAM^MULTILAN:MLSRV. These messages are associated with the Multilan Server (MLSRV) process. Information that appears within parentheses in the message text is information for your Multilan administrator.
Messages 93 through 130 have the header TLAM^MULTILAN:MLRM. These messages are associated with the Multilan Resource Manager (MLRM).
Many of the MLRM messages include a file-system error number (FSERR=) or a network basic input/output system (NETBIOS) return code number (NCBERR=). When the message text shown includes both, only one will actually contain a nonzero value. Error codes preceded by a percent sign (%) are expressed in octal. Error codes preceded by “%H” are expressed in hexadecimal. All other error codes are expressed in decimal. Look up a nonzero file-system error number in Appendix B, or the Guardian Procedure Errors and Messages Manual. Look up a nonzero NETBIOS return code in the Multilan/TLAM Programming Manual. When MLRM encounters a fatal error and terminates abnormally, use Subsystem Control Facility (SCF) commands to delete all windows and workstations before you restart the MLRM. Failure to do so results in ADD WS errors that prevent a workstation user from logging on to the system and using Tandem resources. Messages 131 through 155 have the header TLAM^MULTILAN:MLAD. These messages are associated with the Multilan Attachment Device (MLAD).
Messages 156 through 178, 185, 189, and 192 have the header TLAM:MLMUX. These messages are associated with the Multilan Multiplexer (MLMUX).
| 2 TLAM:MLAM:2 LDev ldev Bad Outbound Ag SDU Port Name: filename Cause: #cause | ||||||
Cause The client has delivered an aggregate SDU to the subsystem that does not conform to the rules governing the format of these messages. Effect The controller discards all remaining frames in the erroneous aggregate SDU message. SDUs previously taken from the message are not affected and are delivered to the media. Recovery The client should isolate the bad message, determine where it deviates from the proper format, and fix the offending code. If the client is using the ZL2S formatting library, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 3 TLAM:MLAM:3 LDev ldev filename Process looping on FEBreakOnly |
Cause The BREAK key was pressed while a process was attempting to write to a terminal. The process retried and entered a loop. After the break is detected, only the break owner (the application that initiated the break) can access a terminal. This message is generated when a process other than the break owner is in a tight loop retrying an operation and getting rejected with FEBreakOnly. Effect Continually retrying an error can tie up the Multilan Access Method (MLAM) in another processor, locking out all application programs. The error is equivalent to TLAM/Multilan operator message 118. Recovery Recovery is application-dependent. Stopping the process may or may not be appropriate. Suspend the process, and determine the identity of the application. Then modify the application to delay between retries. See Appendix B, for a definition of errors 110 and 111. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 4 TLAM:MLAM:4 LDev ldev filename Checkpoint Error Entity: rept-entity Chkpt Type: chkpt-type Cause: #cause | ||||||||||||
Cause The backup input/output (I/O) process cannot process a checkpoint. Effect No immediate problems result, but a switch can result in unpredictable actions by the MLAM. Recovery Halt and dump the processor of the MLAM backup process, then reload. If the problem persists, do not reload the backup; contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 5 TLAM:MLAM:5 LDev ldev filename Operator Requested CPU Switch |
Cause TLAM/Multilan received a valid Subsystem Control Facility (SCF) PRIMARY LINE (SWITCH LINE) request. Effect The MLAM process attempts to give ownership of the controller to its backup. All requests owned by the MLAM process are flushed with file-system error 210. Recovery If you get file-system error 210, reissue your request. See Appendix B, for a definition of error 210. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 6 TLAM:MLAM:6 LDev ldev filename Device Down |
Cause The operator stopped the line with a Subsystem Control Facility (SCF) command, or it stopped itself because of a serious error. Recovery If the error was not forced by an ABORT or STOP command, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 7 TLAM:MLAM:7 LDev ldev filename Device Up |
| 8 TLAM:MLAM:8 LDev ldev filename DLM Version MisMatch DLM Version: %DLM-vsn-code |
Cause The input/output (I/O) process is unable to establish communication with the Multilan Multiplexer (MLMUX) code running in the controller because of a version mismatch. Recovery Check the DLMFILENAME with the Subsystem Control Facility (SCF) INFO CONTROLLER command for the download file, and verify the version of the file. |
| 9 TLAM:MLAM:9 LDev ldev filename Fatal Controller Error System Status: %Hctlr-sys-status System Info: %Hctlr-sys-info Error Code: %Hctlr-err-code | ||||||
Cause A fatal controller error has occurred. Effect If the controller is configured to AUTORELOAD, the input/output (I/O) process reloads the controller and continues operation. Otherwise, the line is downed. Recovery Restart the line with a Subsystem Control Facility (SCF) START LINE command. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 10 TLAM:MLAM:10 LDev ldev filename Can't Configure IO Buffers |
Cause The dedicated buffer size specified for this line in the input/output (I/O) configuration section of the SYSGEN configuration file was too small to allow the I/O process to operate properly. Effect The Multilan Access Method (MLAM) process does not accept any operations. Recovery Reconfigure the controller, using SYSGEN, to have a smaller MAXREQUESTSIZE or a larger LINEBUFFERSIZE. |
| 11 TLAM:MLAM:11 LDev ldev filename Process Internal Error: file-sys-err Caller: %caller-addr | ||
Cause The Multilan Access Method (MLAM) has detected a serious internal error. This error is generated at the point the Multilan Access Method (MLAM) detected the error. Effect Subsequent requests to the line are rejected with file-system error 157. Recovery Halt and dump the processor of the reporting process, then reload. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. See Appendix B, for a definition of error 157. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 12 TLAM:MLAM:12 LDev ldev filename I/O Bus Error file-sys-err | ||
Cause An input/output (I/O) bus error occurred during a transfer with the device on a channel controlled by the sender processor, and an I/O path switch took place. This message occurs when the local area network (LAN) controller is too busy to handle a request from the host. The request is retried a number of times before the message is generated. If this message occurs ten times consecutively (that is, until the retry counter is exhausted), the controller is considered dead. As a result, a processor switch occurs and code is downloaded to the controller. Effect The TLAM/Multilan manager process detects a serious I/O error; the primary process attempts to initiate a switch to its backup process if there is one. The operation is retried, and then the other path is tried. If the error number is in the range 210 through 229, the operation can switch to the other processor. If a controller is generating a continuous I/O power-on interrupt, the application trying to communicate with the device receives an error code (usually 231, I/O power on) in response to its I/O request. This error is equivalent to message 3. Recovery To reduce the number of occurrences of this message, you must determine which problem I/O bus error is occurring. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If you are unable to resolve the error, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 13 TLAM:MLAM:13 LDev ldev filename IO Bus IO Error: %errnum PDT: Int Cause: %status1 Int Stat: %status2 Chan Stat: %status3 IOC Stat: %status4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
When an execute input/output (EIO) operation finishes, an interrupt occurs. At this point, an interrogate I/O (IIO) instruction (HIIO if the interrupt was a high-priority I/O interrupt) must be executed to determine the cause of the interrupt. This instruction returns three words of information and sets the condition code in the same way that the EIO instruction does. Figure 119-1 illustrates the format of the three words. Where:
Table 119-1 Channel Status for TLAM/Multilan Message 13
Cause An input/output (I/O) bus channel error has occurred. Effect The state of the I/O operation is unknown. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 14 TLAM:MLAM:14 LDev ldev filename IO Process Abended Caller: %caller-addr Error: #err-code Reason: #reason | ||||||||||||
Cause The MLAM I/O process detected an error at process initialization time and is unable to go on. Effect The MLAM terminates abnormally. Recovery If the device was added by SYSGEN, verify the SYSGEN configuration. If it still fails, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 15 TLAM:MLAM:15 LDev ldev filename Incoming Requests Have Overrun |
Cause This situation can occur in a large network when many remote nodes stop functioning because of a power failure or when a gateway node stops functioning. Effect Incoming requests have overrun the status message buffer. TLAM/Multilan declares itself nonfunctional and rejects all subsequent requests with file-system error 157. Recovery When processors containing process openers are down, the opens must be manually cleared from the internal tables of the Multilan Access Method (MLAM) input/output (I/O) process (when the table is full, open requests are rejected with error 61). Use the Subsystem Control Facility (SCF) LISTOPENS command to list all openers. Use the SCF ABORT command to abort these openers. See Appendix B, for a definition of error 157. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 16 TLAM:MLAM:16 LDev ldev filename Unable to Communicate With CSM Error: #err-code | ||
Cause The Multilan Access Method (MLAM) was unable to establish communication with the CSM input/output (I/O) process for one of the following reasons:
Effect The MLAM is unable to communicate with the CSM I/O process. When you start a line with the Subsystem Control Facility (SCF) START LINE command, the download is repeated after approximately a 90-second delay. After six retries, the line enters the stopped summary state. Recovery If the MLAM can recover by itself, you can continue to run. If the MLAM does not recover by itself, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 17 TLAM:MLAM:17 LDev ldev Port Configuration Error Port Name: filename SDN: #sdn Error: #port-config-err Parm: #port-config-err-param | ||
Cause A problem was encountered during communication with the controller during the start/stop port phase. Effect The port stays in the stopped state. Recovery Recovery depends on the type of problem. If this message is followed by the message “Port Configuration Failed” (TLAM:MLAM:18), the port has not entered the started state. Issue the START command again. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 18 TLAM:MLAM:18 LDev ldev Port Configuration Failed Port Name: filename SDN: #sdn | ||
Cause This message is generated if a port could not be configured by the controller. This error should be preceded by a port configuration error. Effect The port stays in the stopped state. Recovery Recovery depends on the type of problem. Issue the START command again. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 19 TLAM:MLAM:19 LDev ldev filename State Machine Error SM ID: #level-err State: %state Event: #evt | ||||||
Cause The Multilan Access Method (MLAM) makes extensive use of state machines. This message is generated if the MLAM process detects an internal state-machine error. Effect The subsystem’s action depends on the entity that reported the error. If the controller interface (CtlrIF) or Multiplexer (MUX) reported the error, MLAM declares itself nonfunctional and rejects all subsequent errors with file-system error 157. If one of the other entities reports the problem, that entity is put in the stopped state but the rest of the subsystem functions normally. Recovery If the reporting entity was other than the MUX or CtlrIF, reconfigure the object and continue operation. If the MUX or CtlrIF reported the problem, halt and dump the processor of the reporting MLAM process, then reload. In either case, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. See Appendix B, for a definition of specified error 157. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 20 TLAM:MLAM:20 LDev ldev filename Ownership Change Detected by New Primary |
Cause The backup Multilan Access Method (MLAM) input/output (I/O) process has become the owner of the controller. The reason for the ownership change must be determined from previous messages. Effect The MLAM backup I/O process takes over. Recovery Informational message only; no corrective action is needed. |
| 21 TLAM:MLAM:21 LDev ldev filename UnExpected LIOP Response Caller: %caller-addr DSAP: #liop-dsap SSAP: #liop-ssap Func: #liop-func Mod: #liop-mod | ||||||||
Cause An unexpected LIOP response was received by the input/output (I/O) process. Effect The LIOP frame is discarded. The operation continues; however, requests might be lost as the result of this error. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 22 TLAM:MLAM:22 LDev ldev filename Set Config Value Invalid Invalid Attribute: #val-DLM-inv | ||||||||||||||||||
Cause The SERVICE object attributes in the controller download module in the Multilan Access Method (MLAM) are incorrect. These attributes might have been altered through the Subsystem Control Facility (SCF) interface before the controller was downloaded. Effect After the controller is downloaded, the MLAM tries to configure all of the SERVICE objects in the controller with their attributes kept in the MLAM. If any of these attributes are invalid, the controller rejects the SET CONFIG command. The line stays down until the erroneous attribute value is corrected. Recovery To verify SERVICE object attributes, use the INFO SERVICE command. Use the ALTER SERVICE command to correct the one that is wrong. Table 119-3 Attribute Numbers and Descriptions for TLAM/Multilan Message 22
|
| 23 TLAM^MULTILAN:MLSRV:23 $SRV FILE disk-name, CAN'T ALLOCATE EXTENDED SEGMENT, ERROR alloc-status |
Cause An error occurred during an attempt to allocate the extended segment. Effect The Multilan Server (MLSRV) process is terminated. Recovery Use the SEGMENT_ALLOCATE_ procedure. See Appendix F, for information about the alloc-status error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 24 TLAM^MULTILAN:MLSRV:24 $SRV FILE filename, CANNOT BE CREATED, ERROR IO-errnum | ||
Cause A file could not be created by the Multilan Server (MLSRV) process, probably because an illegal file name was attempted. Effect The user receives a DOS error message. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 25 TLAM^MULTILAN:MLSRV:25 $SRV BACKUP CREATED cpu, pin |
Cause This is a standard message sent from a process-creation procedure call confirming that the backup process has been created. Use the NEWPROCESS procedure or the PROCESS_CREATE_ procedure. Effect The Multilan Server (MLSRV) is now running as a process pair. Recovery Informational message only; no corrective action is needed. |
| 26 TLAM^MULTILAN:MLSRV:26 $SRV filename CAN'T CHECKOPEN (ERROR IO-errnum) | ||
Cause An error has occurred on the CHECKOPEN of a file. Effect The workstation user is not able to open the file. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 27 TLAM^MULTILAN:MLSRV:27 $SRV ERROR CHECKPOINTING EXTENDED SEGMENT (ERROR alloc-status) |
Cause A checkpoint of the extended segment to the backup Server process has failed. Effect The Multilan Server (MLSRV) terminates abnormally. Recovery Use the SEGMENT_ALLOCATE_ procedure. See Appendix F, for information about the alloc-status error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 28 TLAM^MULTILAN:MLSRV:28 $SRV CHECKPOINT FAILURE chkpt-status |
Cause A checkpoint to the Multilan Server process’s backup has failed. Effect The Multilan Server (MLSRV) may terminate abnormally. Recovery If the MLSRV process abends, save the ZZSAnnnn ABEND file for the Global Mission Critical Solution Center (GMCSC). Restart the MLSRV. See the Guardian Programmer's Guide for details about the checkpointing facility. When contacting the Global Mission Critical Solution Center (GMCSC), provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 29 TLAM^MULTILAN:MLSRV:29 $SRV FILE filename, IMPOSSIBLE STATUS FROM COMM ERROR (STATUS comm-err-status) |
Cause An internal error occurred when COMMERROR returned a status that the Multilan Server did not recognize. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 30 TLAM^MULTILAN:MLSRV:30 $SRV Fatal Error - MLSRVCOM Abended |
Cause An internal error occurred. Effect MLSRVCOM terminated abnormally before it completed processing the Multilan Server (MLSRV) input file. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 31 TLAM^MULTILAN:MLSRV:31 $SRV UNABLE TO OPEN DOSACC, FILE ERROR IO-errnum | ||
Cause An error occurred during an attempt to open the file DOSACC. DOSACC is the file in which DOS file-security information is registered. Effect Users are not able to access files or spooler files. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 32 TLAM^MULTILAN:MLSRV:32 $SRV Fatal Error - Can't read first record of DOSENT |
Cause An error occurred when the Multilan Server (MLSRV) attempted to read the first record of the DOS directory file DOSENT. The DOSENT file is probably corrupted. Effect The MLSRV terminates abnormally. Recovery Restore all of the files in the MLSRV process DOS directory from the latest system backup tapes. |
| 33 TLAM^MULTILAN:MLSRV:33 $SRV Fatal Error - DOSENT isn't key-sequenced or has bad structure |
| 34 TLAM^MULTILAN:MLSRV:34 $SRV Fatal Error - Inconsistent DOS directory |
| 35 TLAM^MULTILAN:MLSRV:35 $SRV DOS DISK SIZE EXCEEDED |
| 36 TLAM^MULTILAN:MLSRV:36 $SRV Fatal Error - Can't open DOSENT or DOSACC file (file error IO-errnum) | ||
Cause An input/output (I/O) error was returned when the Multilan Server attempted to open either the DOS directory file DOSENT or the DOS security file DOSACC. Effect The Multilan Server terminates abnormally. Recovery Correct the Guardian security for the DOSENT and/or DOSACC files. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 37 TLAM^MULTILAN:MLSRV:37 $SRV LAM-name DUPLICATE NAME ON NETWORK |
Cause The CMDS file contains MLSRVCOM local area network (LAN) commands that cause duplicate network Server names to be configured. There could also be another program on the LAN that is using the name. Effect Users may not be able to access the Multilan Server (MLSRV). Recovery Correct the MLSRV startup file so it does not contain multiple LAN commands that see the same LAN. |
| 38 TLAM^MULTILAN:MLSRV:38 $SRV filename EDITREAD FAILURE (edit-code) |
| 39 TLAM^MULTILAN:MLSRV:39 $SRV FILE filename, EDIT FILE FULL |
| 40 TLAM^MULTILAN:MLSRV:40 $SRV FILE filename, EDIT FILE LINE TOO LONG - TRUNCATED |
| 41 TLAM^MULTILAN:MLSRV:41 $SRV EDIT FILE REPOSITION TABLE FULL - CONTACT TANDEM |
Cause An internal error occurred during repositioning of an EDIT file. Effect The user receives a DOS error message. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 42 TLAM^MULTILAN:MLSRV:42 $SRV FILE filename, NON-SEQUENTIAL I/O ATTEMPTED TO AN EDIT FILE |
| 43 TLAM^MULTILAN:MLSRV:43 $SRV filename FILE ERROR IO-errnum | ||
Cause A file-system error occurred when a Multilan user attempted to access a file. Effect The user receives a DOS error. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 44 TLAM^MULTILAN:MLSRV:44 $SRV CAN'T PERFORM INITIAL CHECKPOINT (ERROR chkpt-type, chkpt-status CODE loc) |
Cause The initial checkpoint to the backup process failed. Effect The Multilan Server (MLSRV) runs without a backup process. Recovery The MLSRV retries starting its backup process. See the discussion of file-system errors in the Guardian Procedure Errors and Messages Manual for details on the specified CHECKPOINT errors. |
| 45 TLAM^MULTILAN:MLSRV:45 $SRV Fatal Error - Initial command file (/IN) cannot be opened file error (IO-errnum) |
| 46 TLAM^MULTILAN:MLSRV:46 $SRV FILE LAM-name, ADAPTER MISSING OR FAILED, ERROR IO-errnum | ||
Cause Either the adapter card failed or the Multilan Attachment Device (MLAD)failed. Effect The Multilan Server (MLSRV) cannot communicate with an MLAD adapter. Recovery None. The MLSRV periodically retries using the adapter. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 47 TLAM^MULTILAN:MLSRV:47 $SRV Fatal Error - Can't talk to LAM I/O process. |
Cause An input/output (I/O) error occurred when the Multilan Server attempted to communicate with the local area network (LAN) I/O process. Effect The Multilan Server terminates abnormally. Recovery Use the Subsystem Control Facility (SCF) to check the status of the I/O process names on the LAN commands. |
| 48 TLAM^MULTILAN:MLSRV:48 $SRV LAM-name LAM COMMUNICATION LOST, ERROR IO-error (STATUS comm-err-status) | ||
Cause The communication with the local area network (LAN) input/output (I/O) process failed. Effect All users on the LAN are disconnected from the Multilan Server (MLSRV). Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 49 TLAM^MULTILAN:MLSRV:49 $SRV Fatal Error - Bad LAM I/O process name |
| 50 TLAM^MULTILAN:MLSRV:50 $SRV MAXIMUM CONNECTIONS EXCEEDED (res-limit) | ||
Cause The maximum number of connections has been reached. Effect Users receive an error message when they attempt their next NET SHARE (or equivalent) command. Recovery To find the current connection limit, use the MLSRVCOM INFO command. |
| 51 TLAM^MULTILAN:MLSRV:51 $SRV MAXIMUM LANS EXCEEDED (res-limit) | ||
Cause The allocated maximum number of LANs has been exceeded. Effect The Multilan Server (MLSRV) rejects additional LAN commands. Recovery To find the current limit on LANs, use the MLSRVCOM INFO command. |
| 52 TLAM^MULTILAN:MLSRV:52 $SRV MAXIMUM DOS HANDLES EXCEEDED (res-limit) | ||
Cause The Multilan Server (MLSRV) users have opened more DOS files than MLSRV can handle at one time. Effect Additional user requests to open DOS files fail with a DOS error message. Recovery To find the current limit, use the MLSRVCOM INFO command. |
| 53 TLAM^MULTILAN:MLSRV:53 $SRV MAXIMUM OPEN SPOOL FILES EXCEEDED (res-limit) | ||
Cause The allocated maximum number of open spool files has been exceeded. Effect Additional attempts to open spool files as DOS files receive a DOS error message. Recovery To find the current limit on open spool files, use the MLSRVCOM INFO command. |
| 54 TLAM^MULTILAN:MLSRV:54 $SRV MAXIMUM USERS/SESSIONS EXCEEDED (res-limit) | ||
Cause The Multilan Server (MLSRV) has reached its maximum number of users. Effect Attempts by additional users to use the file Server fail. Recovery To find the current user limit, use the MLSRVCOM INFO command. |
| 55 TLAM^MULTILAN:MLSRV:55 $SRV MAXIMUM SHARES EXCEEDED (res-limit) |
| 56 TLAM^MULTILAN:MLSRV:56 $SRV MAXIMUM SPOOL FILES EXCEEDED (res-limit) | ||
Cause The allocated maximum number of spool files has been exceeded. Effect Additional attempts to create spool files fail with a DOS error message. Recovery To find the current limit on spool files, use the MLSRVCOM INFO command. |
| 57 TLAM^MULTILAN:MLSRV:57 $SRV FILE proc-name, BAD MLRM RETCODE (MLRM-status) | ||
Cause The protocol between the Multilan Server (MLSRV) and the MLRM is not working. Effect Users cannot access files or spooler files. Recovery Stop the MLRM and the MLSRV and restart both processes. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 58 TLAM^MULTILAN:MLSRV:58 $SRV LAM-name NETBIOS ERROR netbios-code ON COMMAND netbios-cmd | ||||
Cause A NETBIOS error indicating a hardware or software problem with the local area network (LAN) has occurred. Effect Depending on the NETBIOS error, the Multilan Server (MLSRV) terminates communication with a single workstation or with the entire LAN. Recovery See the Multilan/TLAM Programming Manual for NETBIOS command and error information. The MLSRV process periodically tries to reestablish communication with the LAN. |
| 59 TLAM^MULTILAN:MLSRV:59 $SRV FILE LAM-name, DEVICE IS NOT OF LAN TYPE |
| 60 TLAM^MULTILAN:MLSRV:60 $SRV Fatal Error - CANNOT ADDNAME |
Cause The Multilan Server (MLSRV) was not able to add its network basic input‑output system (NETBIOS) name to any of the gateways that appeared on the local area network (LAN) command at startup time. Effect The MLSRV cannot use the device specified in the LAN command. Recovery Correct the LAN configuration or the LAN command and restart the MLSRV. |
| 61 TLAM^MULTILAN:MLSRV:61 $SRV INTERNAL ERROR - INSUFFICIENT CONTEXT BLOCKS |
Cause The Multilan Server (MLSRV) ran out of context blocks due to an error in findfirst/findnext handling. Effect Users receive a DOS error message. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 62 TLAM^MULTILAN:MLSRV:62 $SRV Fatal Error - Can't create MULTILAN MLSRVCOM (file error num) |
Cause The Multilan Server (MLSRV) received a process-creation error while trying to start the MLSRVCOM process. Effect The MLSRV terminates abnormally. Recovery Use the SEGMENT_ALLOCATE_ procedure. See Appendix F, for information about the file error num. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. In either case, when the problem is corrected, restart the MLSRV. |
| 63 TLAM^MULTILAN:MLSRV:63 $SRV Fatal Error - No LANS specified |
| 64 TLAM^MULTILAN:MLSRV:64 $SRV NO MEMORY AVAILABLE (REQUEST SIZE = req-size) |
Cause Either the extended memory segment is too small, there are too many users, or buffer sizes are too large. Effect The Multilan Server (MLSRV) does not start. Recovery Increase the size of the memory segment using the MLSRVCOM MEMORY command, or determine how to reduce memory use by checking what amount of memory has been allocated using the MLSRVCOM INFO, MEMORY, USERS, or SHARE command. |
| 65 TLAM^MULTILAN:MLSRV:65 $SRV Fatal Error - Insufficient memory or swapfile disk is full. |
| 66 TLAM^MULTILAN:MLSRV:66 $SRV Fatal Error - Multilan Server process unnamed |
| 67 TLAM^MULTILAN:MLSRV:67 $SRV PFS USED UP |
Cause All Tandem input/output (I/O) operations require a process file segment (PFS) to be issued; each PFS has a limit of 256K. Because this limit has been exceeded, no more PFSs are allowed. Effect All new I/O operations are held up. Recovery You can prevent this error by running fewer network Server names, smaller buffers, or fewer users. See the MULTILAN File Server Manual for details. |
| 68 TLAM^MULTILAN:MLSRV:68 $SRV Fatal Error - GUARDIAN 90 OPERATING SYSTEM MUST BE B40 OR LATER |
| 69 TLAM^MULTILAN:MLSRV:69 $SRV filename CAN'T READ, ERROR IO-errnum, (code-loc) | ||||
Cause A read operation to a file has returned a file-system error. Effect Users receive a DOS error. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 70 TLAM^MULTILAN:MLSRV:70 $SRV TOO MANY RETRY FAILURES, SESSION ABORTED |
| 71 TLAM^MULTILAN:MLSRV:71 $SRV MULTILAN SERVER STARTED |
| 72 TLAM^MULTILAN:MLSRV:72 $SRV MULTILAN SERVER STOPPED |
| 73 TLAM^MULTILAN:MLSRV:73 $SRV BAD SMB NPID (SMB-npid) | ||
Cause There is an error in an SMB message from a Multilan user’s workstation. Effect The user is disconnected from the Multilan Server (MLSRV). Recovery None. This is an indication of a problem in the DOS application software in use on the affected workstation. |
| 74 TLAM^MULTILAN:MLSRV:74 $SRV BAD SMB COMMAND, (CODE SMB-cmd) |
| 75 TLAM^MULTILAN:MLSRV:75 $SRV BAD SMB DIALECT, TYPE SMB-msg-type |
Cause There is an error in a Server message block (SMB) message from a Multilan user’s workstation. Specifically, the message type field was not FFH. Effect The user is disconnected from the Multilan Server (MLSRV). Recovery None. This is an indication of a problem in the DOS application software in use on the affected workstation. |
| 76 TLAM^MULTILAN:MLSRV:76 $SRV BAD SMB LENGTH (SMB-len) | ||
Cause There is an error in an SMB message from a Multilan user’s workstation. Specifically, the length of an SMB message was incorrect. Effect The user is disconnected from the Multilan Server (MLSRV). Recovery None. This is an indication of a problem in the DOS application software in use on the affected workstation. |
| 77 TLAM^MULTILAN:MLSRV:77 $SRV SMB-serv BAD SMB SERVER NAME |
Cause There is an error in a Server message block (SMB) message from a Multilan user’s workstation. Specifically, the Server name was not the characters “SMB.” Effect The user is disconnected from the Multilan Server (MLSRV). Recovery None. This is an indication of a problem in the DOS application software in use on the affected workstation. |
| 78 TLAM^MULTILAN:MLSRV:78 $SRV BAD SMB PARAMETER COUNT (SMB-param-cnt) |
Cause There is an error in a Server message block (SMB) message from a Multilan user’s workstation. Specifically, the parameter count was incorrect. Effect The user is disconnected from the Multilan Server (MLSRV). Recovery None. This is an indication of a problem in the DOS application software in use on the affected workstation. |
| 79 TLAM^MULTILAN:MLSRV:79 $SRV UNRECOGNIZED CONTROL spool-status, JOB job-num |
Cause The Multilan Server (MLSRV) reads certain CONTROL sequences from the spooler. If there are CONTROL sequences in the spooler that the Server does not recognize, then it ignores them and sends this message. Effect A workstation user receives a DOS error. Recovery None. See the Guardian Procedure Calls Reference Manual for details on the spooler CONTROL spool-status code. |
| 80 TLAM^MULTILAN:MLSRV:80 $SRV UNRECOGNIZED CONTROLBUF spool-status, JOB job-num |
Cause The Multilan Server (MLSRV) reads certain CONTROLBUF sequences from the spooler. This message was sent because the spooler did not recognize a CONTROLBUF sequence. Effect The MLSRV ignores the unrecognized CONTROLBUF sequence. Recovery None. See the Guardian Procedure Calls Reference Manual for details on the CONTROLBUF spool-status code. |
| 81 TLAM^MULTILAN:MLSRV:81 $SRV UNRECOGNIZED SETMODE spool-status, JOB job-num |
Cause The Multilan Server (MLSRV) reads certain SETMODE sequences from the spooler. This message was sent because the Multilan Server did not recognize a SETMODE sequence. Effect The MLSRV ignores the unrecognized SETMODE sequence. Recovery None. See the Guardian Procedure Calls Reference Manual for details on the SETMODE spool-status code. |
| 82 TLAM^MULTILAN:MLSRV:82 $SRV BAD PRINTREAD STATUS spool-status, JOB job-num |
Cause The Multilan Server tried to do a PRINTREAD (a procedure to read a spool file) and returned a status that did not make any sense. Effect The workstation user receives a DOS error message. Recovery None. See the Guardian Procedure Calls Reference Manual for details on the PRINTREAD spool-status code. |
| 83 TLAM^MULTILAN:MLSRV:83 $SRV SPOOLERCOMMAND ERROR spool-status |
| 84 TLAM^MULTILAN:MLSRV:84 $SRV CONTROL Z CHARACTER IN SPOOL FILE: CONTACT TANDEM |
Cause A control-Z character was encountered in a spool file. Effect The affected user receives a DOS error message. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 85 TLAM^MULTILAN:MLSRV:85 $SRV BAD PRINTREAD DATA FILE, JOB job-num |
| 86 TLAM^MULTILAN:MLSRV:86 $SRV Fatal Error - Too many I/Os for PFS |
Cause The sum of the buffer-size parameters from the local area network (LAN) commands is more than the maximum process file segment (PFS). There was not enough space in the PFS for all of the adapters defined. Effect The Multilan Server (MLSRV) terminates abnormally. Recovery Change the MLSRV startup configuration file to reduce the sum of the buffer-size parameters. |
| 87 TLAM^MULTILAN:MLSRV:87 $SRV PFS THROTTLING IN FORCE |
| 88 TLAM^MULTILAN:MLSRV:88 $SRV TAKEOVER (CODE chkpt-status, loc) | ||
Cause The Multilan Server (MLSRV) backup process has taken over, because the Multilan Server primary process failed. Effect The MLSRV attempts to create a new backup process. Recovery See the Guardian Procedure Errors and Messages Manual for details about the specified chkpt-status code. |
| 89 TLAM^MULTILAN:MLSRV:89 $SRV FILE LAM-name, TRANSIENT LAM ERROR (IO-errnum) - RETRYING | ||
Cause This message occurs when abnormal errors happen, but no data is lost. An example is when a processor fails and the primary process switches to the backup process. Recovery Informational message only; no corrective action is needed. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 90 TLAM^MULTILAN:MLSRV:90 $SRV FILE LAM-name, MORE NAMES SPECIFIED (LAN COMMAND) THAN ADAPTERS CURRENTLY CONNECTED |
| 91 TLAM^MULTILAN:MLSRV:91 $SRV Fatal Error - Unknown error unkwn-code |
Cause An internal error occurred when the Multilan Server (MLSRV) received an unrecognized error code. Effect The MLSRV terminates abnormally. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. Check your MLSRV startup file; correct it, if necessary; and restart the MLSRV process. |
| 92 TLAM^MULTILAN:MLSRV:92 $SRV filename CAN'T WRITE, ERROR IO-errnum, (CODE loc) | ||
Cause A write operation to a file has returned a file-system error. Effect Users receive a DOS error. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 93 TLAM^MULTILAN:MLRM:93 $ZMRM ADAPTER STATUS FAILED, LINENAME=LAM-name FSERR=IO-errnum, NCBERR=netbios-code, NAME=computer-name | ||||||||
Cause The NETBIOS ADAPTER STATUS command to a workstation on a local area network (LAN) failed (caused a nonzero return code) after appropriate Multilan Resource Manager (MLRM) error recovery efforts within the context of the MLRM-RM/PC interaction. Effect The Multilan Resource Manager (MLRM) stops communication with the LAN, and users are not able to log on to the host to access operating system resources. The MLRM retries opening the line later. Recovery For nonzero file-system errors, see the Guardian Procedure Errors and Messages Manual for recovery information. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 94 TLAM^MULTILAN:MLRM:94 $ZMRM AWAITIO ERR ON $RECEIVE FSERR = IO-errnum | ||
Cause The Multilan Resource Manager (MLRM) encountered file-system error while using $RECEIVE for interprocess communication. Be aware that this type of error condition may lead to abnormal termination (ABEND) of the primary MLRM process. If that should happen, the system generates a saveabend file ($SYSTEM.SYSnn.ZZSAnnnn) and the backup MLRM process attempts to take over. Effect The MLRM terminates abnormally. Recovery Try to restart the MLRM. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 95 TLAM^MULTILAN:MLRM:95 $ZMRM BAD STARTUP PARAMS |
| 96 TLAM^MULTILAN:MLRM:96 $ZMRM STARTUP MSG FSERR = IO-errnum | ||
Cause A file-system error occurred while the Multilan Resource Manager (MLRM) was attempting to read its startup message. Effect The MLRM terminates abnormally. Recovery See Appendix B, for a definition of the specified nonzero error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 97 TLAM^MULTILAN:MLRM:97 $ZMRM BACKUP RESTART FAILED, NO RETRY, NPERR = create-err, FSERR = IO-errnum | ||||
Cause The primary Multilan Resource Manager (MLRM) process has failed, and the backup process has taken over (as the new primary process). The new primary process could not start a backup. Effect The MLRM runs without a backup process. Recovery Use the SEGMENT_ALLOCATE_ procedure. See Appendix F, for information about the create-err error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. In either case, see Appendix B, for a description of IO‑errnum. See the Guardian Procedure Errors and Messages Manual for detailed recovery information. |
| 98 TLAM^MULTILAN:MLRM:98 $ZMRM BACKUP RESTART FAILED, RETRYING, NPERR = create-err, FSERR = IO-errnum | ||||
Cause The primary Multilan Resource Manager (MLRM) process has failed, and the backup process has taken over as the new primary process. Effect The new primary process has not been able to start a backup, but it continues trying to do so. In the meantime, the MLRM is running without a backup. The problem in starting a new backup process may be caused by insufficient swap space. Recovery If insufficient swap space is the problem, you should free up some space on the MLRM swap volume. Use the SEGMENT_ALLOCATE_ procedure. See Appendix F, for information about the create-err error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. In either case, see Appendix B, for a description of IO‑errnum. See the Guardian Procedure Errors and Messages Manual for detailed recovery information. |
| 99 TLAM^MULTILAN:MLRM:99 $ZMRM Backup returned from CHECKMONITOR, abending |
Cause The Multilan Resource Manager (MLRM) has detected an internal error. Effect The MLRM process terminates abnormally. Recovery Try to start the MLRM process again. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 100 TLAM^MULTILAN:MLRM:100 $ZMRM ABORT WINDOW FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WINDOW NAME = window-name | ||||||||
Cause The MLRM attempted to abort the specified window but could not do so. Effect Depending on the error, one of two conditions occurs:
Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 101 TLAM^MULTILAN:MLRM:101 $ZMRM ABORT WS FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WSNAME = ws-name | ||||||||
Cause The MLRM attempted to abort the specified WS object but could not do so. Effect Depending on the error, one of two conditions occurs:
Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 102 TLAM^MULTILAN:MLRM:102 $ZMRM ADD WINDOW FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WINDOW NAME = window-name | ||||||||
Cause When the MLRM receives a resource request from the Resource Manager (RM)/PC of a particular workstation, it attempts to add a window name for the specified Tandem resource to open. This message indicates that the attempt to add a window name failed. Effect One of two conditions occurs:
Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 103 TLAM^MULTILAN:MLRM:103 $ZMRM ADD WS FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WSNAME = ws-name | ||||||||
Cause When the MLRM first hears from the Resource Manager (RM)/PC program on a particular workstation, it makes an entry in its internal tables and then attempts to add a workstation (WS) name object name. This message indicates that the attempt to add a workstation name failed. There are two reasons why this error condition might occur:
In either case, the IO-errnum is 0, the config-err is 54, and the MLRM attempts to delete the particular workstation name. It is, however, very likely to fail, because there are probably subordinate windows in existence that the MLRM is not aware of. When that is true, the MLRM also generates a “DELETE WS FAILED” message and the RM/PC program at the particular workstation displays an error message indicating that the workstation is being deleted. Effect Depending on the error, one of two conditions occurs:
Recovery If the name duplication is caused by workstation names left over from a previous execution of the MLRM, you must statically abort and delete the particular workstation (and all its subordinate windows). If the name duplication is caused by SCF or DSM static configuration, you must statically abort and delete the particular workstation (and all its subordinate windows) and then recreate it (and its windows) using a different workstation name. See Appendix B, for a definition of the specified nonzero file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors other than 000054, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 104 TLAM^MULTILAN:MLRM:104 $ZMRM DELETE WINDOW FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WINDOW NAME = window-name | ||||||||
Cause The MLRM attempted to delete the specified window name and could not do so. Effect Depending on the error, one of two conditions occurs:
Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 105 TLAM^MULTILAN:MLRM:105 $ZMRM DELETE WS FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WSNAME = ws-name | ||||||||
Cause The MLRM attempted to delete the specified WS object and could not do so. DELETE WS may have failed because subordinate windows exist for the WS object that are unknown to MLRM (statically created windows). Effect Depending on the error, one of two conditions occurs:
Recovery If it seems reasonable to do so, statically abort and delete all windows for the specified WS object using Subsystem Control Facility (SCF) commands, then repeat the DELETE WS command. See Appendix B, for a definition of the specified (nonzero) file‑system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 106 TLAM^MULTILAN:MLRM:106 $ZMRM START WINDOW FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WINDOW NAME = window-name | ||||||||
Cause After adding a window for an Resource Manager (RM)/PC-requested resource, the MLRM then attempts to start the window. This message indicates that the attempt to start the window failed. Effect Depending on the error, one of two conditions occurs:
Recovery See Appendix B, for a definition of the specified nonzero file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 107 TLAM^MULTILAN:MLRM:107 $ZMRM START WS FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WSNAME = ws-name | ||||||||
Cause After adding a workstation for interaction with Resource Manager (RM)/PC, the MLRM then attempts to start the workstation. This message indicates that the attempt to start the WS object failed. Effect Depending on the error, one of two conditions occurs:
Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 108 TLAM^MULTILAN:MLRM:108 $ZMRM STATUS WINDOW FAILED, LINENAME = LAM-name, FSERR = IO-errnum, CONFIG_ERR = config-err, WINDOW NAME = window-name | ||||||||
Cause After adding and starting a window, the MLRM issues window status commands for that window until the window is opened by a Tandem program or an internal timeout interval has elapsed. This message indicates that the status command failed for the specified window. Effect Depending on the error, one of two conditions occurs:
Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero configuration errors, see either the SCF Reference Manual for Multilan or the SCF Reference Manual for TLAM for recovery information. |
| 109 TLAM^MULTILAN:MLRM:109 $ZMRM PROCESS_GETINFO_ on self failed during initialization, abending |
Cause The Multilan Resource Manager (MLRM) has detected an internal error. Effect The MLRM process terminates abnormally. Recovery Try once more to start the MLRM program. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 110 TLAM^MULTILAN:MLRM:110 $ZMRM Unknown initialization failure abort, abending. MLRM has detected an internal error. |
Cause The Multilan Resource Manager (MLRM) has detected an internal error. Effect The MLRM process terminates abnormally. Recovery Try once more to start the MLRM program. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 111 TLAM^MULTILAN:MLRM:111 $ZMRM INVALID STATEMACHINE EVENT, EVENT = mach-evt, STATE = mach-state | ||||
Cause A fatal internal error occurred within the primary Multilan Resource Manager (MLRM) process. An invalid event number occurred when the MLRM was in the specified state. Effect The primary MLRM process terminates abnormally (abends), the system generates a saveabend file ($SYSTEM.SYSnn.ZZSAnnnn), and the backup MLRM process attempts to take over. Recovery If the primary-backup process switch is successful, the MLRM resumes normal operation. If the backup process cannot successfully take over, the MLRM stops. In either case, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 112 TLAM^MULTILAN:MLRM:112 $ZMRM INVALID STATEMACHINE STATE, EVENT = mach-evt, STATE = mach-state | ||||
Cause A fatal internal error occurred within the primary Multilan Resource Manager (MLRM) process. The MLRM entered an invalid state by way of the specified error. Effect The primary MLRM process terminates abnormally (abends), the system generates a saveabend file ($SYSTEM.SYSnn.ZZSAnnnn), and the backup MLRM process attempts to take over. Recovery If the primary-backup process switch is successful, the MLRM resumes normal operation. If the backup process cannot successfully take over, the MLRM terminates. In either case, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 113 TLAM^MULTILAN:MLRM:113 $ZMRM STARTED USING DOMAIN LAM-name |
| 114 TLAM^MULTILAN:MLRM:114 $ZMRM Process not named, or not named $ZMRM, abending |
| 115 TLAM^MULTILAN:MLRM:115 $ZMRM Process must be started by SUPER group, abending. MLRM must be started using a SUPER group id. |
| 116 TLAM^MULTILAN:MLRM:116 $ZMRM NOT USING DOMAIN LAM-name |
Cause This message indicates that the Multilan Resource Manager (MLRM) encountered problems with line LAM-name while supporting Resource Manager (RM)/PC-initiated access to the Tandem system (and has therefore stopped using that line). During initialization, this may be a normal occurrence, because the MLRM chooses only one line per local area network (LAN) for RM/PC communications. The MLRM also generates this message at that time for each applicable line that it has not chosen. Effect The MLRM searches for another Multilan line connected to the same LAN and, upon finding one, begins using it. Recovery Informational message only; no corrective action is needed. This message could, however, imply that there are problems with the particular line; contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 117 TLAM^MULTILAN:MLRM:117 $ZMRM STOPPED USING WSPTP ON LINENAME LAM-name |
| 118 TLAM^MULTILAN:MLRM:118 $ZMRM Requires GUARDIAN 90 Version B40 or later. |
Cause You are attempting to run TLAM/Multilan on a system that is using a version of the operating system earlier than B40. Effect The Multilan Resource Manager (MLRM) process terminates abnormally. Recovery You must run Multilan on a system that is using a B40 or later version of the operating system. |
| 119 TLAM^MULTILAN:MLRM:119 $ZMRM PROCESS_GETINFO_ on self failed during initialization, abending. |
Cause The Multilan Resource Manager (MLRM) has detected an internal error. Effect The MLRM process terminates abnormally. Recovery Try once more to start the MLRM program. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 120 TLAM^MULTILAN:MLRM:120 $ZMRM $RECEIVE FSERR = IO-errnum | ||
Cause A file-system error occurred when $RECEIVE was being used for interprocess communication. Effect This type of error condition may lead to abnormal termination of the primary Multilan Resource Manager (MLRM) process. If that should happen, the system generates a saveabend file ($SYSTEM.SYSnn.ZZSAnnnn) and the backup MLRM process attempts to take over. Recovery See Appendix B, for a definition of the specified (nonzero) error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the MLRM process abends, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 121 TLAM^MULTILAN:MLRM:121 $ZMRM -ATTEMPTED SECURITY BREACH, WS CALLNAME = computer-name | ||
Cause Someone on the attached local area network (LAN) is attempting illegal access either to the Tandem system (invalid username or password in three successive LOGON commands) or to Tandem files by way of the Multilan Server. Recovery Informational message only; no corrective action is needed. The recovery action varies according to the requirements and established security practices at each individual customer site. |
| 122 TLAM^MULTILAN:MLRM:122 $ZMRM GOODBYE CRUEL WORLD |
Cause A fatal internal Multilan Resource Manager (MLRM) error was detected. Effect The MLRM terminates abnormally. Recovery Try to restart the MLRM. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 123 TLAM^MULTILAN:MLRM:123 $ZMRM -UNKNOWN EVENT |
Cause An internal error of an unknown nature occurred. Effect This type of error condition may lead to abnormal termination (ABEND) of the primary Multilan Resource Manager (MLRM) process. If that should happen, the system generates a saveabend file ($SYSTEM.SYSnn.ZZSAnnnn) and the backup MLRM process attempts to take over. Recovery If the MLRM process terminates abnormally, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 124 TLAM^MULTILAN:MLRM:124 $ZMRM -ADDNAME FAILED, DOMAIN = LAM-name, FSERR = IO-errnum, NCBERR = netbios-code, NAME = computer-name | ||||||||
Cause A NETBIOS ADDNAME command continued to fail (caused a nonzero NETBIOS return code) after appropriate Multilan Resource Manager (MLRM) error recovery efforts within the context of MLRM-Resource Manager (RM)/PC interaction. Effect The MLRM continues to retry the ADDNAME command. Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 125 TLAM^MULTILAN:MLRM:125 $ZMRM DELETE NAME FAILED, DOMAIN = LAM-name, FSERR = IO-errnum, NCBERR = netbios-code, NAME = computer-name | ||||||||
Cause The DELETE NAME command continued to fail (caused a nonzero return code) after appropriate Multilan Resource Manager (MLRM) error-recovery efforts within the context of MLRM-Resource Manager (RM)/PC interaction. Effect The MLRM continues to retry the DELETE NAME command. Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 126 TLAM^MULTILAN:MLRM:126 $ZMRM HANG UP FAILED, DOMAIN = LAM-name, FSERR = IO-errnum, NCBERR = netbios-code | ||||||
Cause A NETBIOS HANGUP command continued to fail (caused a nonzero return code) after appropriate Multilan Resource Manager (MLRM) error-recovery efforts within the context of MLRM-Resource Manager (RM)/PC interaction. Effect The MLRM closes the line to the local area network (LAN) and periodically retries opening the line. Users on the LAN are not able to access operating system resources. Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 127 TLAM^MULTILAN:MLRM:127 $ZMRM LISTEN FAILED, DOMAIN = LAM-name, FSERR = IO-errnum, NCBERR = netbios-code | ||||||
Cause A NETBIOS LISTEN command continued to fail (caused a nonzero return code) after appropriate Multilan Resource Manager (MLRM) error-recovery efforts within the context of MLRM-Resource Manager (RM)/PC interaction. Effect The MLRM closes the line to the local area network (LAN). Users are unable to log on to the host to access operating system resources. The MLRM retries opening the line. Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 128 TLAM^MULTILAN:MLRM:128 $ZMRM RECEIVE FAILED, DOMAIN = LAM-name, FSERR = IO-errnum, NCBERR = netbios-code | ||||||
Cause A NETBIOS RECEIVE command continued to fail (caused a nonzero return code) after appropriate Multilan Resource Manager (MLRM) error-recovery efforts within the context of MLRM‑Resource Manager (RM)/PC interaction. Effect Depending on the NETBIOS return code, the MLRM may hang up on a single user or stop communication with the line to the local area network (LAN). Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 129 TLAM^MULTILAN:MLRM:129 $ZMRM SEND FAILED, DOMAIN = LAM-name, FSERR = IO-errnum, NCBERR = netbios-code | ||||||
Cause A NETBIOS SEND command continued to fail (caused a nonzero return code) after appropriate Multilan Resource Manager (MLRM) error-recovery efforts within the context of MLRM-Resource Manager (RM)/PC interaction. Effect The MLRM closes the line to the local area network (LAN) and periodically retries opening the line. Users on the LAN are not able to access operating system resources. Recovery See Appendix B, for a definition of the specified (nonzero) file-system error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. For nonzero NETBIOS return codes, see the following manuals for recovery information:
|
| 130 TLAM^MULTILAN:MLRM:130 $ZMRM SESSION TABLE FULL, TRYING ANOTHER ADAPTER |
Cause The Multilan Resource Manager (MLRM) tried to post a network basic input/output system (NETBIOS) LISTEN command, but the command was rejected because either the Multilan Attachment Device (MLAD)session table or the adapter session table is currently full. Effect The MLRM deletes its name from that adapter and then tries to do an appropriate ADD NAME command on a different MLAD and post the LISTEN there. Additional users on the local area network (LAN) are not able to log on to the host to access Tandem resources. Recovery Informational message only; no corrective action is needed. This message may, however, indicate that your current configuration is becoming congested and needs to be altered for load-balancing purposes. |
| 131 TLAM^MULTILAN:MLAD:131 gw-name gw-seq gw-mod gw-time Adapter reset. | ||||||||
Cause A gateway reset a network local area network (LAN) adapter (the downstream adapter). A reset can be caused by a Subsystem Control Facility (SCF) ABORT, STOP, or START request, or by the gateway itself. Effect A gateway reset reinitializes names and sessions information (all current information is lost). LAN applications may experience network basic input/output system (NETBIOS) errors. Recovery Recovery is usually handled by LAN hardware and software. For information on NETBIOS errors, see the MULTILAN/TLAM Programming Manual. |
| 132 TLAM^MULTILAN:MLAD:132 gw-name gw-seq gw-mod gw-time Add or Alter error. event-description | ||||||||||
Cause A Subsystem Control Facility (SCF) ALTER or ADD command issued for a gateway contained one or more values that are not supported by the gateway. Effect The gateway uses default values instead of the values specified in the command. Recovery Informational message only; no corrective action is needed. |
| 133 TLAM^MULTILAN:MLAD:133 gw-name gw-seq gw-mod gw-time Gateway boot. | ||||||||
Cause A gateway has executed an initial program load. Every time the gateway is started, this message is generated. Effect The gateway begins operating. Recovery Informational message only; no corrective action is needed. |
| 134 TLAM^MULTILAN:MLAD:134 gw-name gw-seq gw-mod gw-time Gateway buffer shortage. | ||||||||
Cause A gateway cannot satisfy the current processing requirement for buffer resources. Effect The throughput of the gateway may be reduced. Local area network (LAN) applications may experience network basic input/output system (NETBIOS) errors. The most common errors are:
Recovery If this problem becomes chronic, do one or both of the following:
For information on NETBIOS errors, see the MULTILAN/TLAM Programming Manual. |
| 135 TLAM^MULTILAN:MLAD:135 gw-name gw-seq gw-mod gw-time Gateway crash. event-description | ||||||||||
Cause A gateway’s software terminated because of an unusual condition. This message is reported after the gateway has been restarted. Effect When this message is generated, the gateway has already been restarted. Recovery Crash codes can be displayed on the gateway’s screen. Use the “S” key (for statistics) on the gateway. The statistics display contains the crash code. For information on crash codes, see the MULTILAN Configuration and Management Manual. Report this message (and the crash code) to your the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 136 TLAM^MULTILAN:MLAD:136 gw-name gw-seq gw-mod gw-time DSM command error. event-description | ||||||||||
Cause A gateway received an unsupported Subsystem Control Facility (SCF) command or an unsupported Distributed Systems Management (DSM) command. Effect The command is rejected. Recovery Informational message only; no corrective action is needed. |
| 137 TLAM^MULTILAN:MLAD:137 gw-name gw-seq gw-mod gw-time Gateway local event display off. | ||||||||
Cause Someone disabled local event message display on a gateway’s console. Effect Event messages are no longer displayed on the gateway’s console. Recovery Informational message only; no corrective action is needed. |
| 138 TLAM^MULTILAN:MLAD:138 gw-name gw-seq gw-mod gw-time Gateway local event display on. | ||||||||
Cause Someone enabled local event message display on a gateway’s console. Effect Event messages are displayed on the gateway’s console. Gateway throughput can be affected if the gateway is busy or if a lot of display activity is occurring. As a result, response time on the local area network (LAN) can be degraded. Recovery Informational message only; no corrective action is needed. |
| 139 TLAM^MULTILAN:MLAD:139 gw-name gw-seq gw-mod gw-time Gateway disk error. | ||||||||
Cause A gateway experienced a disk error when it attempted to write a message to its local event-message file. Effect Logging of local messages (that is, boot, reset, and crash messages) to the gateway’s disk is stopped. Recovery The gateway disk problem must be handled by someone with personal computer (PC) expertise. You probably need to restart the gateway. |
| 140 TLAM^MULTILAN:MLAD:140 gw-name gw-seq gw-mod gw-time Event(s) not reported, buffer shortage. | ||||||||
Cause A gateway is not reporting events, because the gateway does not have enough message buffer space. This buffer space is not configurable. Effect Some events are not reported. Recovery Informational message only; no corrective action is needed. |
| 141 TLAM^MULTILAN:MLAD:141 gw-name gw-seq gw-mod gw-time Gateway event summary. event-description | ||||||||||
Cause A gateway has summarized events to prevent events from flooding the event-message log. If a warning error message or informational error message is sent to the event-message log, the same message is not sent again for ten minutes. Instead, a summary count of the number of times the event occurred is sent. Effect Some events are reported in summary form. Recovery Informational message only; no corrective action is needed. |
| 142 TLAM^MULTILAN:MLAD:142 gw-name gw-seq gw-mod gw-time Host trace off. | ||||||||
Cause A gateway received a Subsystem Control Facility (SCF) request or a Distributed Systems Management (DSM) request to stop gateway tracing activity. Recovery Informational message only; no corrective action is needed. |
| 143 TLAM^MULTILAN:MLAD:143 gw-name gw-seq gw-mod gw-time Host trace on. | ||||||||
Cause The gateway received a Subsystem Control Facility (SCF) request or a Distributed Systems Management (DSM) request to start tracing gateway activity. Effect Tracing can affect gateway throughput. As a result, local area network (LAN) response time can be degraded. The magnitude of the effect depends on the options requested for the trace. Recovery Turn off tracing if its effect cannot be tolerated. |
| 144 TLAM^MULTILAN:MLAD:144 gw-name gw-seq gw-mod gw-time Invalid event number. | ||||||||
Cause A gateway has issued an unknown event-message number. Recovery Report this message to the Global Mission Critical Solution Center (GMCSC). |
| 145 TLAM^MULTILAN:MLAD:145 gw-name gw-seq gw-mod gw-time Gateway level 2 error. | ||||||||
Cause One or more protocol errors (level-2 errors) occurred when a gateway was communicating with a controller. The situation is usually caused by one of the following:
Effect Gateway throughput can be affected. As a result, response time on the local area network (LAN) can be degraded. The magnitude of the effect depends on the frequency of the errors. Recovery Use the Subsystem Control Facility (SCF) STATISTICS GATEWAY command to examine level-2 and Ethernet statistics. For information on SCF commands, see the SCF Reference Manual for MULTILAN. |
| 146 TLAM^MULTILAN:MLAD:146 gw-name gw-seq gw-mod gw-time Gateway media access failures. | ||||||||
Cause One or more errors occurred when a gateway was communicating with a controller. These errors are usually the result of an Ethernet adapter (upstream or host adapter) experiencing a hardware problem. Effect Throughput on the gateway can be affected. As a result, response time on the local area network (LAN) can be degraded. The magnitude of the effect depends on the frequency of the errors. Recovery Use the Subsystem Control Facility (SCF) STATISTICS GATEWAY command to examine level-2 and Ethernet statistics. For information on SCF commands, see the SCF Reference Manual for MULTILAN. |
| 147 TLAM^MULTILAN:MLAD:147 gw-name gw-seq gw-mod gw-time Trace information displayed at gateway. | ||||||||
Cause Someone enabled the display of trace events on the gateway console. Effect Throughput on the gateway can be affected. As a result, response time on the local area network (LAN) can be degraded. |
| 148 TLAM^MULTILAN:MLAD:148 gw-name gw-seq gw-mod gw-time Gateway local trace off. | ||||||||
Cause Someone disabled the display of trace events on the gateway console. Effect Throughput on the gateway is no longer affected. Recovery Informational message only; no corrective action is needed. |
| 149 TLAM^MULTILAN:MLAD:149 gw-name gw-seq gw-mod gw-time Gateway local trace on. | ||||||||
Cause Someone enabled tracing on the gateway. Effect Throughput on the gateway can be affected. As a result, response time on the local area network (LAN) can be degraded. |
| 150 TLAM^MULTILAN:MLAD:150 gw-name gw-seq gw-mod gw-time NCB shortage. | ||||||||
Cause A gateway’s requirement for network control blocks (NCBs) exceeds the availability of NCBs. Effect Throughput on the gateway can be affected. As a result, response time on the local area network (LAN) can be degraded. Recovery If this message becomes chronic, do one or more of the following:,
|
| 151 TLAM^MULTILAN:MLAD:151 gw-name gw-seq gw-mod gw-time NETBIOS error. event-description | ||||||||||
Cause A gateway experienced a NETBIOS error. Effect Some NETBIOS errors are acceptable and some indicate possible LAN application problems. Recovery Informational message only; no corrective action is needed. If LAN users are reporting problems, examining the gateway’s message log may provide additional information about the problem. For information on NETBIOS errors, see the Multilan/TLAM Programming Manual. |
| 152 TLAM^MULTILAN:MLAD:152 gw-name gw-seq gw-mod gw-time Name or session pool error. event-description | ||||||||||
Cause A gateway attempted to reserve or use name and session pool space that was not available. Effect The request requiring the pool space is not satisfied. Local area network (LAN) applications may experience network basic input/output system (NETBIOS) resource allocation errors. Recovery Do one or both of the following:
For information on NETBIOS errors, see the Multilan/TLAM Programming Manual. |
| 153 TLAM^MULTILAN:MLAD:153 gw-name gw-seq gw-mod gw-time Gateway reply error. event-description | ||||||||||
Cause A gateway did not have enough replay control blocks to maintain its replay capability. Effect Replay functions are lost. LAN applications requesting replay receive network basic input/output system (NETBIOS) resource-allocation errors. Recovery Replay blocks are not a configurable resource. If this message becomes chronic, do one or both of the following:
For information on NETBIOS errors, see the Multilan/TLAM Programming Manual. |
| 154 TLAM^MULTILAN:MLAD:154 gw-name gw-seq gw-mod gw-time Gateway reset has occurred. | ||||||||
Cause A gateway has reestablished its connection to a controller. Effect A reset initializes everything configured for the adapter. Any existing network control blocks (NCBs), names, sessions, pools of names, and pools of sessions are lost. Messages received by entities on the local area network (LAN) are application-dependent. Recovery Informational message only; no corrective action is needed. For information on network basic input/output system (NETBIOS) errors, see the Multilan/TLAM Programming Manual. |
| 155 TLAM^MULTILAN:MLAD:155 gw-name gw-seq gw-mod gw-time Gateway statistics reset. | ||||||||
Cause A gateway has reset its statistics in response to a Subsystem Control Facility (SCF) STATS, RESET command or to a request issued (with the “R” key) at the gateway. Effect The statistics are initialized to zero. Recovery Informational message only; no corrective action is needed. |
| 156 TLAM:MLMUX:156 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Event(s) not reported, buffer shortage. evt-descr | ||||||||||
Cause Event Management Service (EMS) support could not get the buffer to report one or more errors. Effect One or more messages were not reported and therefore were lost. Recovery Informational message only; no corrective action is needed. |
| 157 TLAM:MLMUX:157 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time DSM request in error. | ||||||||
Cause A controller has detected an invalid Distributed Systems Management (DSM) request from internal controller code or from the gateway. |
| 158 TLAM:MLMUX:158 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time EMS event summary. evt-descr | ||||||||||
Cause This message indicates that the controller has summarized multiple errors to prevent an overload condition that would affect performance. Effect None. Processing continues normally. Recovery Informational message only; no corrective action is needed. |
| 159 TLAM:MLMUX:159 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Invalid command. | ||||||||
Cause An internal (in the controller) or external (from the gateway) programming error has occurred. Effect The command is discarded. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 160 TLAM:MLMUX:160 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Invalid event number. | ||||||||
Cause Controller support has issued an error request having an event number greater than the event numbers that can be serviced. The details of the error are not known. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 161 TLAM:MLMUX:161 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Invalid message type. | ||||||||
Cause An internal (in the controller) or external (from the gateway) programming error occurred. Effect The message is discarded. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 162 TLAM:MLMUX:162 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time The controller is disconnected. evt-descr | ||||||||
Cause Either the gateway is not loaded, the gateway has crashed, or there is a cable/transceiver/connector problem. Effect The gateway is not online. Recovery Recovery may be automatic if the gateway reboots itself. Manual intervention may be required if the gateway does load or if there is a cabling problem. |
| 163 TLAM:MLMUX:163 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Connecting to gateway. evt-descr | ||||||||
Cause An XID has been received from a gateway that is currently disconnected. Effect A controller-gateway connection is established. Future GATEWAY commands (for this gateway) are processed by this gateway. Recovery Informational message only; no corrective action is needed. |
| 164 TLAM:MLMUX:164 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time LLC error detected. | ||||||||
Cause A hardware or software failure occurred at link-level support. |
| 165 TLAM:MLMUX:165 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time L2 error detected. | ||||||||
Cause A hardware or software failure was detected in level-2 support. |
| 166 TLAM:MLMUX:166 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Token Bus MAC event. {Lose address sort | No Successor | No Successor 1 | Solicit Any | Bus Idle Timer Expired } | ||||||||||||||||||
Cause This error applies to the 5700 token bus controller only. One of the following unusual Media Access Control (MAC) errors has occurred:
Effect The controller is still functional but may be affected. In the case of “Solicit Any,” the controller attempts to find a station to which to pass the token. Recovery No explicit recovery is needed. This error provides information about unusual occurrences within the token bus network. The network continues to operate, but frequent occurrences of this error may indicate a problem with the network itself, this node, or another node on the network. Normal diagnostic procedures should be followed to prevent this error from occurring frequently. |
| 167 TLAM:MLMUX:167 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Token Bus MAC failure. { Modem Error | Duplicate MAC address | Bus/Address Error | Faulty Transmitter | Unexpected Frame 6 } | ||||||||||||||||||
Cause This error applies to the 5700 token bus controller only. This error is caused by a hardware failure or an incorrect configuration. The specific errors are as follows:
Effect The controller is not functional. Recovery Use diagnostic tools such as Tandem Maintenance and Diagnostic System (TMDS) to research the failure. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 168 TLAM:MLMUX:168 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Packet size error. | ||||||||
Cause A programming error caused a request to transfer a packet larger than the maximum packet size. |
| 169 TLAM:MLMUX:169 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Receive buffer shortage. | ||||||||
Cause A buffer request was denied. Effect The impact on performance can be minor or major, depending on the frequency of occurrence. Recovery Increase the service data unit (SDU) forward count with the ALTER PORT command. Or, add an additional controller to improve the performance. |
| 170 TLAM:MLMUX:170 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Receive control block shortage. | ||||||||
Cause An internal request for a receive buffer was denied. Effect The impact on performance is minor or major, depending on the frequency of occurrence. Recovery Change the service data unit (SDU) forward count with the ALTER PORT command. Or, add an additional controller to improve the performance. |
| 171 TLAM:MLMUX:171 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time SDU size error, LSAP ctlr-lsap, Req ID ctlr-req-id, PID cpu,pin. | ||||||||
Cause A programming error or channel interface overrun occurred. Effect The controller flushes any remaining frames. Recovery Correct the programming problem or repair the channel interface. |
| 172 TLAM:MLMUX:172 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Statistics reset. | ||||||||
Cause You have issued a RESET STATISTICS command. Effect The controller’s statistics are reset to zero. Recovery Informational message only; no corrective action is needed. |
| 173 TLAM:MLMUX:173 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Token Bus Chip failure. evt-descr | ||||||||
Cause This error applies to the 5700 token bus controller only. The token bus chip failed. Recovery See the TLAM Management Programming Manual for more information. Attempt to restart the controller using the Subsystem Control Facility (SCF). If restart fails, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 174 TLAM:MLMUX:174 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Trace frame error. | ||||||||
Cause A programming failure has occurred in the controller. Effect Some trace data is lost. Recovery Informational message only; no corrective action is needed. |
| 175 TLAM:MLMUX:175 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time DSM tracing off. | ||||||||
Cause You have issued a Distributed Systems Management (DSM) command to turn tracing off. Effect Controller tracing is stopped. Recovery Informational message only; no corrective action is needed. |
| 176 TLAM:MLMUX:176 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time DSM tracing on. | ||||||||
Cause You have issued a Distributed Systems Management (DSM) command to trace. Effect Performance is affected if traced activity is high. Recovery Informational message only; no corrective action is needed. |
| 177 TLAM:MLMUX:177 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Transmission error. | ||||||||
Cause A transmission failure was detected. Either there were excessive collisions, there was a direct memory access (DMA) underrun, or there was no carrier sense signal. Effect The frame is discarded and the operation is retried. Recovery Repair the cable, connector, or other failing component. |
| 178 TLAM:MLMUX:178 filename E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Buffer control block shortage. | ||||||||
Cause The throughput demands exceeded buffer resources. Effect The impact on performance can be minor or major, depending on the frequency of occurrence. Recovery Add controllers to ease congestion if this situation occurs often enough to affect performance. |
| 179 TLAM^MULTILAN:MLSRV:179 $SRV filename CANNOT BE PURGED, ERROR IO-errnum | ||
Cause A file-system error occurred while the Multilan Server (MLSRV) was purging a file for a user. Effect A DOS file is not purged; however, it is no longer in the MLSRV DOS directory. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 180 TLAM^MULTILAN:MLSRV:180 $SRV BACKUP STOPPED cpu, pin |
Cause The Multilan Server (MLSRV) backup process has stopped. This was probably caused by a failure of the processor where the backup process was executing. Effect The MLSRV is no longer running as a process pair. Recovery If the MLSRV was started with the BACKUPCPU parameter specifying a specific processor, the MLSRV restarts the backup process when the processor is reloaded. Otherwise, the MLSRV creates a backup process in the next available processor. |
| 181 TLAM^MULTILAN:MLSRV:181 $SRV IMPOSSIBLE SITUATION - CONTACT TANDEM (CODE loc), ERROR IO-errnum | ||
Cause The Multilan Server (MLSRV) detected a nonfatal but impossible processing situation. Recovery See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 182 TLAM^MULTILAN:MLSRV:182 $SRV IMPOSSIBLE SITUATION - CONTACT TANDEM (code-loc) |
Cause The Multilan Server (MLSRV) detected a fatal impossible processing situation. Effect The MLSRV terminates abnormally. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 183 TLAM^MULTILAN:MLSRV:183 $SRV filename FILE NOT CLOSED BY DOS - CACHE CLEARED |
| 184 TLAM^MULTILAN:MLSRV:184 $SRV filename CAN'T POSITION, ERROR IO-errnum | ||
Cause A file-system error occurred while the Multilan Server (MLSRV) was positioning in a file for a user. Effect A workstation user receives a DOS error. Recovery Informational message only; no corrective action is needed. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 185 TLAM:MLMUX:185 controller-name E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time LIP header received with SSAP error. | ||||||||
Cause An internal source service access point (SSAP) addressing problem has occurred. Effect The message is not sent. If this error persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 186 TLAM:MLAM:186 Inbound SDU Not Delivered MSAP Name: name Cause: #cause Param: #param | ||||||||
Cause The MSAP object has received an aggregate SDU from the controller and has attempted to deliver an SDU to the appropriate connection, but it cannot. Note that the MSAP routes an SDU based on the Packet Type and Connection ID fields, in that order. The Connection ID field is the home-grown service control point (HGSCP) equivalent to the DSAP field in the SDU packet header. The MSAP cannot deliver the SDU because of one of the following:
Effect The SDU is not delivered. Recovery Issue the TRACE TLAM/Multilan LINE command, selecting the trace options CIFDI, CIFDO, LCB, and MSAP, and then replicate the error. To replicate this error, issue the ABORT command, then the START command for both the MSAP and local line handler (LH). Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 187 TLAM:MLAM:187 Inbound Message Not Delivered Next Sys: #nextsys MSAP Name: name LH LDev: $LH-ldev File Err: #filerr | ||||||
Cause The message system was unable to deliver the message to the local line handler (LH). This error may occur when the local LH changes processors, but it should not persist. Note that this error often results when critical events, such as CPU Down and CPU Failure, occur. Effect The message is not delivered. Recovery If the error recurs, issue the TRACE TLAM/Multilan LINE command, selecting the trace options CIFDI, CIFDO, LCB, and MSAP. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. |
| 188 TLAM:MLAM:188 Unexpected L2SFrmt Error MSAP Name: name Routine: #routine-id Error: #error | ||||
Cause This error occurs during an attempt to send data. The message service access point (MSAP) module uses the L2S Formatting Library to build and examine aggregate service data units (SDUs). This error is reported when an L2S routine fails with an unexpected error. Recovery Increase the data forward size (DFS). If the error recurs, issue the TRACE TLAM/Multilan LINE command, selecting the trace options CIFDI, CIFDO, LCB, and MSAP. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 189 TLAM:MLMUX:189 fname E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Controller Transceiver Heart Beat Failure | ||||||||
Cause The problem is either an incorrect transceiver configuration, a defective transceiver, or a defective transceiver cable on controller fname. Effect The controller transceiver heartbeat failed. Recovery Check the configuration and hardware. If necessary, replace the transceiver or cable. |
| 190 TLAM^MULTILAN:MLSRV:190 $XXX Redirector sent an invalid LSEEK share mode to file Server. share mode PARAM1, method PARAM2 | ||||||||||||||||||
Cause An attempt was made to perform an LSEEK for a MULTILAN DOS file. This DOS file was opened with a share mode that does not allow LSEEK. Effect The operation cannot be performed because of the share mode for the DOS file. Recovery Change the Multilan DOS file share mode to a mode allowing an LSEEK to be performed. |
| 191 TLAM:MLAM:191 Ldev ldev fname Backup trace request error Entity: #rept-entity Object Type: #obj-type Cause: #cause |
Cause The backup process cannot start a trace. Effect An attempt to stop or alter a trace in a backup input/output (I/O) process failed. Recovery If the cause does not indicate a lack of memory, halt and dump the processor of the Multilan Access Method (MLAM) backup process, then contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 192 TLAM:MLMUX:192 fname E Addr = ctlr-id ctlr-seq ctlr-cmpnt ctlr-time Gateway evt-descr is running an incompatible software version | ||||||||
Cause The gateway is running a version of software that is incompatible with the host TLAM/Multilan software. Effect A gateway is not operating. Recovery Change the gateway software so it is compatible with the host TLAM/Multilan software. |
| 193 TLAM:TLAM 193 TLAM:MLMUX Frame not sent: Clear to send (CTS) lost MAC Address: %Haddress |
| 194 TLAM:TLAM.D11 000194 TLAM:MLMUX Frame not sent: DMA underrun MAC Address: %Haddress |
Cause The local area network (LAN) controller hardware may not be functioning correctly. Effect Direct memory access (DMA) underrun occurred during transmission. The frame was not delivered. Recovery There are 5 recoveries you can try:
|
| 195 TLAM:TLAM.D11 000195 TLAM:MLMUX Frame not sent: Too many collisions MAC Address: %Haddress |
Cause The local area network (LAN) controller hardware may not be functioning correctly or the LAN installation may not be correct. Effect Transmission failed due to too many collisions occurring. The frame was not delivered. Recovery Check the LAN installation. If this problem persists, replace the LAN controller. |
| 196 TLAM:TLAM.D11 000196 TLAM:MLMUX Frame not sent: Late collision MAC Address: %Haddress |
Cause The local area network (LAN) controller hardware may not be functioning correctly or the LAN installation may not be correct. Effect A collision was detected beyond the amount of time needed to transmit data to the furthest station. The frame was not delivered. Recovery Check the LAN installation. If this problem persists, replace the LAN controller. |
| 197 TLAM:TLAM.D11 000197 TLAM:MLMUX Frame not sent: Carrier sense (CRS) lost MAC Address: %Haddress |
Cause If this error is only reported from one station, then a problem may exist in the transceiver and/or the transceiver cable. If other stations on the local area network (LAN) are reporting similar problems, then the problem may exist with the LAN installation. Effect Carrier sense signal (NO_CRS) was lost during transmission. The frame was not delivered. Recovery Verify the correct operation of the transceiver and transceiver cable. Verify the LAN installation. If this problem persists, replace the LAN controller. |
| 198 TLAM:TLAM.D11 000198 TLAM:MLMUX Heartbeat (SQE) test failure. |
Cause The transceiver is not configured to perform the heartbeat test, or a problem exists with the transceiver or transceiver cable. Effect No heartbeat indicator was detected after transmission. Recovery If the transceiver is not configured correctly, then enable the transceiver to perform the heartbeat test or disable the controller from performing the heartbeat test using the Subsystem Control Facility (SCF). If the transceiver is configured correctly, replace the transceiver or transceiver cable or both. |
| 199 TLAM:TLAM.D11 000199 TLAM:MLMUX Transmit control block shortage |
Cause The capacity of the local area network (LAN) installation has been exceeded, or the LAN controller hardware may not be functioning correctly. Effect The frame was not delivered because a buffer mechanism control block shortage occurred. This error can have a major impact or minor impact on performance, depending on how frequently it occurs. Recovery If the capacity of the LAN installation has not been exceeded and this error persists, replace the LAN controller. |
| 200 TLAM:TLAM.D11 000200 TLAM:MLMUX Receive frame descriptor shortage |
Cause The capacity of the local area network (LAN) installation has been exceeded or the LAN controller hardware may not be functioning correctly. Effect Buffer resources are in short supply. This error can have a major impact or minor impact on performance, depending on how frequently it occurs. Recovery If the capacity of the LAN installation has not been exceeded and this error persists, replace the LAN controller. |
| 201 TLAM:TLAM.D11 000201 TLAM:MLMUX Receive buffer descriptor shortage |
Cause The capacity of the local area network (LAN) installation has been exceeded, or the LAN controller hardware may not be functioning correctly. Effect An internal request for a receive buffer was denied. The receive unit (RU) could no longer receive frames due to shortage of buffer descriptors (BDs). The RU temporarily stops receiving frames until BDs are available. This may have an adverse effect on performance. Recovery If the capacity of the LAN installation has not been exceeded and this error persists, replace the LAN controller. |
| 202 TLAM:TLAM.D11 000202 TLAM:MLMUX Connecting to gateway gw-name |
| 203 TLAM:TLAM.D11 000203 TLAM:MLMUX Disconnecting to gateway gw-name Cause: {Operator requested | Timed-out } |
Cause Either the operator requested the gateway to disconnect, or a message was not received from the gateway within the specified time period. Effect A connection has been lost to the gateway and the controller is not online. Recovery If the cause indicates that the gateway timed-out, verify that the gateway is connected and is functioning properly. |
| 204 TLAM:TLAM.D11 000204 TLAM:MLMUX Gateway gw-name already defined |
Cause A gateway attempted to establish a connection in which its name already exists. This occurs when the operator configures two gateways with the same name. Effect The message occurs when an exchange identification (XID) frame is received from a gateway that already exists. Recovery Use the name to determine the offending gateway, and reconfigure it with a different name. |
| 205 TLAM:TLAM.D11 000205 TLAM:MLMUX Correctable memory error detected |
| 206 TLAM:TLAM.D11 000206 TLAM:MLMUX Lost event #lost-evt Event has occurred #count times since time | ||
Cause A persistent error condition exists such that too many errors of different types are being generated. Effect Messages were lost due to too many errors occurring. Recovery This problem is always preceded by many other errors. Resolve the preceding errors and follow the recommended action for the first message lost. |
| 207 TLAM:TLAM.D11 000207 TLAM:MLAM MLMUX Internal Error Major Status: %Hstatus1 Minor Status: %Hstatus2 Info: %Hinfo PC: %Hloc MLMUX version:version | ||||
Cause The MLMUX detected an internal error. Effect The error is most likely a software failure. This operator messages is only generated for 3615 controllers. Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 208 TLAM:TLAM.D11 000208 TLAM:MLAM MLMUX detected non-maskable interrupt (NMI) |
Cause The Multilan Multiplexer (MLMUX) detected a nonmaskable interrupt. Effect This is most likely a hardware failure. This operator messages is generated only for 3615 controllers. Recovery Dump the contents of the controller random-access memory (RAM). If this problem persists, replace the local area network (LAN) controller. |
| 209 TLAM:TLAM.D11 000209 TLAM:MLAM MLMUX detected uncorrectable memory error (UCME) |
Cause The Multilan Multiplexer (MLMUX) detected an uncorrectable memory error. Effect This is most likely a hardware failure. This operator message is generated only for 3615 controllers. Recovery Dump the contents of the controller random-access memory (RAM). If this problem persists, replace the local area network (LAN) controller. |
| 210 TLAM:TLAM.D11 000210 TLAM:MLAM MLMUX detected address/data bus parity error |
Cause The Multilan Multiplexer (MLMUX) detected address/data bus parity error. Effect This is most likely a hardware failure. This operator message is generated only for 3615 controllers. Recovery Dump the contents of the controller random-access memory (RAM). If this problem persists, replace the local area network (LAN) controller. |
| 211 TLAM:TLAM.D11 000211 TLAM:MLAM MLMUX detected BIC parity error |
Cause The Multilan Multiplexer (MLMUX) detected a backplane interconnect card (BIC) parity error. Effect This is most likely a hardware failure. This operator message is generated only for 3615 controllers. Recovery Dump the contents of the controller random-access memory (RAM). If this problem persists, replace the local area network (LAN) controller. |
| 212 TLAM:TLAM.D11 000212 TLAM:MLAM MLMUX detected correctable memory error (CME) |
| 213 TLAM:TLAM.D11 000213 TLAM:MLAM BIC diagnostics failed |
Cause Backplane interconnect card (BIC) diagnostics reported a failure. Effect This is most likely a hardware failure. This operator message is only generated for 3615 controllers. Recovery Dump the contents of the controller random-access memory (RAM). If this problem persists, replace the local area network (LAN) controller. |
| 214 TLAM:TLAM.D11 000214 TLAM:MLAM Bootcode diagnostics failed |
| 215 TLAM:TLAM.D11 000215 TLAM:MLMUX File error file-sys-err occurred during access to download file filename | ||
Cause A file error occurred while accessing the download file. Effect TLAM/Multilan could not download the controller. Recovery Investigate the file error code and determine the cause. See Appendix B, for information on the specified error. |
| 216 TLAM:TLAM.D11 000216 TLAM:MLMUX Incorrect file code for download file filename Expected file code: 510 Actual file code: actual-file-code |
| 217 TLAM:TLAM.D11 000217 TLAM:MLMUX Download file filename does not contain module with the following attributes: Download part number: part-no Download Revision: rev-level BIC type: BIC-type | ||||||
Cause The download file does not contain the Multilan Multiplexer (MLMUX) module for the LAN controller. |
| 218 TLAM:TLAM.D11 000218 TLAM:MLMUX Download file filename corrupted |
Cause The download file has been corrupted. Effect TLAM/Multilan could not download the controller. Recovery Verify that the download file is correct. If the download file is correct, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 219 TLAM:TLAM.D11 000219 TLAM:MLMUX LB SEEROM corrupted: err |
| 220 TLAM:TLAM.D11 000220 TLAM:MLMUX BIC SEEROM corrupted err | |||
Cause The backplane interconnect card (BIC) serial electrically erasable read-only memory (SEEROM) on the local area network (LAN) controller has been corrupted. |
| 221 TLAM:TLAM.D11 000221 TLAM:MLMUX Incomplete bootcode |
Cause The controller experienced a power failure or a reset during a previous update of the electrically erasable programmable read-only memory (EEPROM) contents. Effect Bootcode in EEPROM is incomplete. The EEPROM no longer contains the code to execute the controller diagnostics. This error is generated only for 3615 and later controllers. Recovery Use the Tandem Maintenance and Diagnostic System (TMDS) to update the and ensure that it finishes successfully. |
| 222 TLAM:TLAM.D11 000222 TLAM:MLMUX EIO error, Chanstat: %chanstat Devstat: %devstat | ||||
Cause A channel or device error occurred. Effect An I/O (EIO) instruction failed. Recovery If this problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 223 TLAM:TLAM.D11 000223 TLAM:MLMUX LB is incorrect for configured controller type Download part number: part-num Controller configured: prod-num | ||||
Cause The incorrect controller product number was specified in the CONFTEXT file or the wrong local area network (LAN) controller board was installed. Effect TLAM/Multilan could not download the controller. Recovery Specify the correct controller product number in the CONFTEXT file and re‑execute the SYSGEN program or install the configured LAN controller in the correct input/output (I/O) slot. |
| 224 TLAM:TLAM.D11 000224 TLAM:MLMUX Gateway gw-name is running an incompatible version | ||
Cause There was an attempt to connect a gateway that was running an incompatible version. Effect The gateway was not connected. Recovery Verify that the gateway is running the correct software version. |
| 225 TANDEM:TLAM.D30 000225 TLAM:MLAM LDev ldev text1 notification not delivered PORT Name: port-name Cause:#cause: text2 Send Complete Error: send-compl-error Message System Error msg-sys-error | ||||||||||||||||||||||||||||||||
Cause A notification could not be delivered by the TLAM subsystem to the SNAX subsystem due to the reasons specified by the cause and text2 fields. Effect The notification is discarded and the rejected counter in the MSAP #SNATR statistics is incremented. Recovery For cause values 1 through 3, there is no action to be performed by the operator. The TLAM IOP returns an error code to the SNAX line handler which performs error handling and recovery. For cause value 4, retry the operation later. If TLAM still runs out of extended memory, reconfigure a larger extended memory pool. If TLAM still runs out of extended memory, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well. |
| 226 TANDEM.TLAM.D21 000226 TLAM:MLAM LDev ldev text1 notification not delivered PORT Name: port-name Cause:#cause: text2 Send Complete Error: send-compl-error Message System Error msg-sys-error | ||||||||||||||||||||||||
Cause The cause and text2 fields specify the reason why the notification was not sent to MLMUX. Effect TLAM could not forward a request to MLMUX. The request is discarded and the rejected counter is incremented in the MSAP #SNATR statistics field. Recovery Informational message only; no recovery action is needed. For both causes, the TLAM IOP also returns an error code to the SNAX line handler. The SNAX line handler is responsible for error handling and recovery. |
| 227 TANDEM.TLAM.D21 000227 TLAM:MLMUX fname E Addr = ctllr-id, cltr-seq, cltr-cmpnt,ctlr-time Lobe Wire Fault, LINE stopped |
| 228 TANDEM.TLAM.D21 000228 TLAM:MLMUX fname E Addr = ctllr-id cltr-seq, cltr-cmpnt,ctlr-time Port Address: port-address SDU Size: sdu-size Inbound SDU too large, SDU discarded | ||||
Cause An inbound SDU was received whose length is greater than the MAXREQUESTSIZE specified for the port for which it is destined. The inbound SDU is discarded. Either the application which opened the port is in error, or the configuration of the port is incorrect. Effect The inbound SDU is discarded. Recovery Correct the port configuration or fix the application to match the port configuration. |
| 229 TANDEM.TLAM.D21 000229 TLAM:MLMUX fname E Addr = ctlr-id cltr-seq, cltr-cmpnt,ctlr-time Port Address: port-address Bad outbound AggSDU | ||
Cause This event is issued when an outbound aggregate SDU fails consistency checks performed by the controller on an LLC1 aggregate SDU. The outbound SDU is discarded. Effect The controller validates the SAP, the SDU count and the SDU size for LLC1 aggregate SDUs and issues this event if there is an error in these fields. This means the application is formatting the LLC1 aggregate SDU incorrectly. Recovery Use the TLAM trace command to locate the problem in the application and fix the application. Use of the formatting libraries may avoid most of these problems since the formatting libraries perform several validity checks on the data. |
| 230 TLAM.TLAM.D21 000230 TLAM:MLMUX fname E Addr = ctlr-id cltr-seq, cltr-cmpnt,ctlr-time Insufficient outbound buffers, SDU discarded |
Cause Either there is heavy traffic from the system to the controller because of many link stations, a bottleneck in accessing the ring, or a persistent busy condition on the remote host. Effect This event is issued when the controller has a shortage of outbound buffers Transmit Header Blocks (THBs). The SDUs are lost. Recovery The application load on the controller should be reduced or any congestion problems in the ring should be resolved. |
| 231 TANDEM.TLAM.D21 000231 TLAM:MLMUX fname E Addr = ctlr-id cltr-seq, cltr-cmpnt,ctlr-time Insufficient inbound buffers, SDU discarded |
Cause The cause is a bottleneck between the controller and the rest of the system in handling the inbound SFUs. This could be caused by the NonStop processor being too busy and the controller not getting enough time on the channel to ship its inbound data to the NonStop processor. Effect This event is issued when the controller has a shortage of inbound buffers (Buffer Descriptors). The SDUs are lost. Recovery Remove the bottleneck between the controller and the NonStop processor. |
| 241 TANDEM.TLAM.D21 000241 TLAM:MLMUX IO process abended Unable to access QIO subsystem QIO Error: error # | ||
Cause See error descriptions above under error #. QIOCONF utility is not sizing the poolspace correctly or the configuration is improper. Effect TLAM IOP abends after QIO/TLAM reconfiguration/installation. Recovery Use smaller files and add the SPACECOUNT value set to the number of TLAM IOPs needed. |