Chapter 78 PATHWAY Messages

Cause  The specified terminal has been aborted.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The PATHMON environment has been successfully shut down.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The PATHMON process aborted due to a fatal error.

Effect  The PATHMON process cannot monitor or control the PATHMON environment nor process requests.

Recovery  Determine why the PATHMON process abended by checking the NonStop Kernel operating system errors in messages logged just before this message, then restart the PATHMON environment. If you cannot determine the cause of the error, contact your service provider 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.

Cause  A server class link cannot be granted to a TCP or a LINKMON process.

Effect  The Pathsend statement or SEND operation fails.

Recovery  For more information, refer to the description associated with the nested message.

Cause  An error occurred while a TCP or LINKMON process was trying to return a link to a server class. The nested message indicates the reason for the failure.

Effect  The effect depends on the reason for the failure.

Recovery  For more information, refer to the description associated with the nested message.

Cause  Either the PATHMON process tried to add an object having a name that already exists, or the PATHMON process tried to start a terminal control process (TCP) or server process using a process name that is already active within this PATHMON environment.

This message usually indicates that there was an attempt to use an object name or a process name twice. For example, if this is a nested message in a CAN’T GRANT LINK error, the process name for a dynamic server already exists in the list of active server processes and TCPs.

Effect  The object is not added, or the TCP or server process is not started.

Recovery  Check the object name or the process name associated with the specified object. Change the name as required.

Cause  An entry that should contain the description of a PATHMON‑controlled object (for example, a server class) is empty. This is an internal error.

Effect  The operation that needed to use the entry cannot complete.

Recovery  Contact your service provider 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.

Cause  An object type does not match the type specified or implied by a request.

Effect  The request that specified the object fails.

Recovery  Correct the object type specified or implied by the request, and then retry the request.

Cause  A TCP stopped abnormally even though a STOP command was not issued.

Effect  The TCP is unavailable.

Recovery  Determine the cause of the TCP failure, then restart the TCP.

Cause  A file-system error occurred during an I/O operation to the PATHMON configuration file.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred during an I/O operation to the specified server class.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred during an I/O operation to the specified TCP or LINKMON process.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred during an I/O operation to the LOG1 file.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred during an I/O operation to the LOG2 file.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred during an I/O operation to $RECEIVE.

Effect  The effect depends on the file-system error that occurred.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred during an I/O operation to the specified TCP or LINKMON process.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  An invalid file name was detected in the definition of the specified object.

Effect  The request that needed the object fails.

Recovery  Correct all invalid file names in the definition of object-name. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  An internal consistency check failed in the PATHMON process. This error is not fatal.

Effect  The PATHMON process creates a memory dump if dumping has been enabled.

Recovery  Contact your service provider 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.

Cause  A message received does not conform to the PATHMON request protocol. This error can be caused by running incompatible versions of PATHCOM, PATHMON, or PATHTCPn. The message was received from the process running under the specified user ID.

Effect  The PATHMON process rejects the request.

Recovery  Contact your service provider 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.

Cause  The LOG1 file is closed.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The LOG1 file is open.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The LOG2 file is closed.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The LOG2 file is open.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  An entry cannot be added, because the PATHMON configuration file is full. This is an internal error.

Effect  Entries cannot be added until the configuration file is available.

Recovery  Contact your service provider 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.

Cause  There is insufficient space in the PATHMON process’s free-space table.

Effect  The operation fails.

Recovery  Specify a larger number for the MEM option in the PATHMON RUN command.

Cause  The PATHMON process cannot grant a link to a TCP or a LINKMON process, because no server processes are available. Either the TCP or LINKMON process is already linked to all server processes in the class, or all processes in the class currently have the maximum number of links (defined in the MAXLINKS attribute).

Effect  The requesting TCP or LINKMON process is not linked to the server class.

Recovery  Increase the value of the MAXSERVERS, MAXLINKS, or LINKDEPTH attribute in the server class definition. (It is recommended that you not set ZLINKDEPTH higher than 1 for servers other than communications-based servers, such as HLS servers.)

Cause  The specified entry does not exist. Either the wrong object name was used or the desired object does not exist.

Effect  The operation fails.

Recovery  Correct the object name or add the object to the PATHMON configuration file.

Cause  There is an invalid system name in the definition of the indicated object.

Effect  The operation fails.

Recovery  Use an ALTER command to correct the system name in the object definition.

Cause  An extraneous entry, which was in an inconsistent state when PATHMON failed, was deleted from the PATHMON configuration file during a cool start.

Effect  The following entry token types are deleted upon a cool start:

Recovery  Informational message only; no corrective action is required.

Cause  An error occurred during the creation of a new process for the indicated server or TCP.

Effect  The new process is not created.

Recovery  See Appendix B, or to Appendix D, for information about the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A PATHMON process name was not supplied when PATHMON was started.

Effect  The PATHMON process cannot be opened; the operation fails.

Recovery  Name your PATHMON process.

Cause  A file-system error was returned on a call to DEVICEINFO2.

Effect  The call to DEVICEINFO2 and the request fails. This error is not logged, but is simply returned to the operator.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  An error occurred during request initiation.

Effect  The request fails.

Recovery  For additional information, refer to the description associated with the nested message.

Cause  The indicated terminal has resumed processing.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The specified object has started.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  A file-system error occurred.

Effect  The effect depends on the file-system error that occurred.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  The specified object has stopped.

Effect  The effect depends on the application and what type of object stopped.

Recovery  For additional information, refer to the description associated with the nested message.

Cause  The specified terminal suspended processing due to an error in the program. The reason for the error is indicated in the nested message.

Effect  The terminal remains suspended until it is aborted with the Pathway/iTS ABORT TERM command.

Recovery  For additional information, refer to the description associated with the nested message.

Cause  The specified terminal suspended processing due to a SUSPEND TERM command.

Effect  The terminal remains suspended until you issue the Pathway/iTS RESUME TERM command.

Recovery  For additional information, refer to the description associated with the nested message.

Cause  An error occurred while the PATHMON process was processing a system message. The error is indicated by the nested-message.

Effect  The effect depends on the particular error that occurred.

Recovery  For additional information, refer to the description associated with the nested message.

Cause  The internal limit on the total number of concurrent openers of the PATHMON process (currently 300 openers) would be exceeded by starting the specified TCP at this time.

Effect  The START TCP command fails.

Recovery  Stop some other TCPs, PATHCOM processes, or SPI requesters communicating with the PATHMON process, or wait until some of these processes go away, and then try again to start this TCP.

Cause  The link manager failed during a request.

Effect  The request is not completed.

Recovery  Determine the cause of the link manager failure by checking the errors in messages logged just before this message.

After correcting the cause of the failure, restart the TCP (this step is not required if AUTORESTART is specified for the TCP). A LINKMON process failure requires you to reload the CPU.

If you cannot determine the cause of the error, contact your service provider 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.

Cause  A link request from a terminal control process (TCP) or LINKMON process was rejected because the specified server class is frozen.

Effect  You cannot perform a SEND operation to a server class that is frozen. The server class must be thawed before links can be granted.

Recovery  Thaw the server class and reissue the SEND request.

Cause  The specified server class is frozen.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The specified server class is thawed.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  A TCP request specified an entity that is not known to the PATHMON process. This error is an internal error.

Effect  The request fails.

Recovery  Contact your service provider 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.

Cause  A PATHMON process dump was taken at operator request or because the PATHMON DUMP attribute was enabled at the time an internal error occurred.

Effect  Memory has been written to the named dump file.

Recovery  If the dump was taken by operator request, this message is informational only; no corrective action is required.

If an internal error occurred, contact your service provider 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.

Cause  The operating system returned an error on a call to a Guardian procedure.

Effect  The effect depends on the error.

Recovery  Contact your service provider 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.

Cause  An error occurred during an operating system CHECKPOINT procedure operation.

Effect  The PATHMON process stops its backup process, if it is running. When possible, the PATHMON process starts a new backup process.

Recovery  Refer to the Guardian Procedure Calls Reference Manual for information concerning the CHECKPOINT error.

Cause  The PATHMON process was not able to create its backup process. The nested message indicates the reason.

Effect  The PATHMON process runs without a backup.

Recovery  For additional information, refer to the description associated with the nested message.

Cause  An error occurred during an operating system CHECKOPEN operation.

Effect  The primary file is closed. Any additional effect depends on the file that was being opened.

Recovery  Refer to the Guardian Procedure Calls Reference Manual for information concerning the specified CHECKOPEN error.

Cause  An error occurred during an operating system CHECKCLOSE operation. The error number indicates the reason.

Effect  None.

Recovery  Refer to the Guardian Procedure Calls Reference Manual for information concerning the specified CHECKCLOSE error.

Cause  The PATHMON backup process took over processing because the primary CPU failed or because a PRIMARY or SWITCH command was executed.

Effect  If the primary CPU failed, the PATHMON process runs without a backup.

Recovery  If the primary CPU failed, reload the CPU so that the PATHMON process can create a backup process. If a PRIMARY or SWITCH command was executed, this is an informational message only; no corrective action is required.

Cause  A PATHMON process internal-consistency check failed. This is an internal error.

Effect  The PATHMON process terminates. If the DUMP attribute is enabled, the PATHMON process creates a dump file before terminating.

Recovery  Contact your service provider 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.

Cause  A software or hardware failure resulted in a trap. This is an internal error.

Effect  The PATHMON process terminates. If possible, it creates a dump file.

Recovery  Contact your service provider 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.

Cause  During a cool start, the PATHMON configuration file was incompatible with the currently running PATHMON process. This incompatibility can result from the following: either the PATHMON configuration file is a version prior to D30 (which is not compatible with D30 versions of the PATHMON configuration file), or the PATHMON configuration file has an invalid code (the valid file code is 310).

Effect  The cool start fails.

Recovery  Cold start the PATHMON environment.

Cause  The Expand communication link to the external PATHMON environment is down.

Effect  The PATHMON process cannot access the specified link manager.

Recovery  Establish a link to the system in which the link manager is running.

Cause  The backup CPU for the PATHMON process or for the terminal control process (TCP) is not running.

Effect  A backup process cannot be created.

Recovery  Reload the CPU.

Cause  The PATHMON backup process abended or stopped unexpectedly.

Effect  The PATHMON process creates a backup process, if possible.

Recovery  If the problem persists, contact your service provider 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.

Cause  The PATHMON process cannot send checkpoint information to its backup process due to an internal condition.

Effect  The backup is stopped and automatically recreated.

Recovery  Informational message only; no corrective action is required.

Cause  The TCP read the requested program unit code segment into memory after checking the SCREEN COBOL object directory file.

Effect  The TCP uses the latest version of each program unit.

Recovery  Informational message only; no corrective action is required.

Cause  The specified suspended terminal automatically aborted before being restarted with AUTORESTART.

Effect  The terminal terminates abnormally.

Recovery  Informational message only; no corrective action is required.

Cause  After a failure, the AUTORESTART feature restarted the specified object.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The specified object reached the AUTORESTART limit configured for it.

Effect  The object is not restarted.

Recovery  Solve the problem that is causing the persistent failures, then restart the object. See the operating system errors or messages logged just prior to this message to determine what caused the persistent failures. Once you start the object, AUTORESTART is reenabled for the object.

Cause  The PATHMON backup process was stopped by its primary process. This message normally occurs after the CONTROL PATHMON, BACKUPCPU command causes the backup process to change from one CPU to another.

Effect  The PATHMON backup process is down. A new backup is created in the new CPU as soon as possible.

Recovery  Informational message only; no corrective action is required.

Cause  An attempt to perform a PATHMON process memory dump failed. This is an internal error.

Effect  No dump file is created.

Recovery  Contact your service provider 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.

Cause  An operating system error occurred on a call to the ALLOCATESEGMENT procedure.

Effect  The PATHMON process is unable to allocate an extended data segment. The PATHMON process terminates.

Recovery  See Appendix E, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  An operating system error occurred on a call to the USESEGMENT procedure.

Effect  The PATHMON process is unable to select a particular extended data segment. The PATHMON process terminates.

Recovery  Refer to the Guardian Procedure Errors and Messages Manual for information concerning the specified USESEGMENT error.

Cause  An operating system error occurred during a call to the DEFINE procedure library (for example, to DEFINERESTORE).

Effect  The operation fails.

Recovery  Refer to the Guardian Procedure Errors and Messages Manual for information concerning the specified DEFINE error.

Cause  The library procedure for a DEFINE (such as DEFINERESTORE) is unavailable.

Effect  The processing of DEFINE statements is disabled, making it impossible to add a DEFINE definition to a server class.

Recovery  Install a version of the NonStop Kernel operating system that supports DEFINESAVE and DEFINERESTORE—that is, version C10 or later.

Cause  The PATHMON backup process is initialized, running, and ready to take over for the primary process, if necessary.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  There is insufficient space for additional entries in one of the PATHMON internal tables. This is an internal error.

Effect  The ASSIGN, DEFINE, PARAM, PROCESS, and STARTUP attributes cannot be configured for a server class. If you are running the Pathway/iTS product, additional PROGRAM, TELL, TERM, and TERM objects cannot be configured. No server process can be started whose name has not been configured by the user.

Recovery  Contact your service provider 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.

Cause  The shutdown process has started in the indicated mode.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The STOP PATHMON command was issued.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  An object in the PATHMON environment, such as a terminal control process (TCP) or a server class, could not be stopped.

Effect  The shutdown fails.

Recovery  Stop the object using the TACL STOP command and retry the shutdown.

Cause  The specified file-system error occurred when the PATHMON process tried to access the PATHMON configuration file. This message is entered in the log file, but is not returned to the user.

Effect  The command may or may not fail, depending upon when the file-system error occurred. If the command fails, error 1017 is returned to the user. In either case, the PATHMON configuration file cannot be accessed by subsequent commands.

Recovery  Refer to the Guardian Procedure Errors and Messages Manual for information about the specified file-system error. Cool or cold start the PATHMON environment to make the PATHMON configuration file accessible again.

Cause  The primary PATHMON process failed and the backup PATHMON process is not fully initialized.

Effect  The PATHMON process cannot process requests, monitor, or control the PATHMON environment.

Recovery  Determine why the PATHMON process abended by checking the Guardian errors in messages logged just before this message, then restart the PATHMON environment. If you cannot determine the cause of the error, contact your support representative 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.

Cause  An error occurred while the PATHMON process was trying to create the specified OSS server process.

Effect  The server process is not created.

Recovery  OSS server processes are created by calls to the Guardian PROCESS_SPAWN_ procedure. See the detailed description in this message for additional information. For information about the PROCESS_SPAWN_ procedure call, refer the Guardian Procedure Calls Reference Manual. For information about PROCESS_SPAWN_ codes, including recovery actions, refer the Guardian Procedure Errors and Messages Manual.

Cause  This PATHMON environment does not support Open System Services (OSS) server processes.

Effect  The configured OSS server processes cannot be started.

Recovery  Contact your service provider to inquire about installing OSS support features on your system.

Cause  An error occurred during a call to the Guardian RESIZESEGEMENT or CHECKRESIZESEGMENT procedure.

Effect  The command fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the descriptions of the RESIZESEGEMENT or CHECKRESIZESEGMENT procedures in the Guardian Procedure Calls Reference Manual.

Cause  The PATHMON process could not start up because it could not confirm that either the NonStop TS/MP product or the Pathway/iTS product is licensed for your site.

Effect  System startup fails.

Recovery  Either the NonStop TS/MP product or the Pathway/iTS product must be licensed before the PATHMON process can start an application. If you believe you have secured a license for the NonStop TS/MP or Pathway/iTS product, perform the following:

If a licensing file is present and properly secured, applications running under the licensed product should start up and run as expected.

Cause  You have issued a command for a product that is not licensed for your site. For example, you have tried to use PATHCOM to define a server class, but NonStop TS/MP is not licensed for your site.

Effect  The command fails.

Recovery  The NonStop TS/MP or Pathway/iTS product must be licensed before you can add objects controlled by that product. If you believe you have secured a license for the product associated with the command you just issued, perform the following:

If the appropriate licensing file is present and properly secured, you should be able to define objects controlled by the licensed product.

Cause  The maximum number of LINKMON, TCP, and external TCP processes has exceeded the total number of link managers allowed (currently 800).

Effect  The bad value (MAXEXTERNALCPS, MAXLINKMONS or MAXTCPS) is rejected and the SET PATHWAY command fails.

Recovery  Re-enter the values of MAXEXTERNALCPS, MAXLINKMONS and MAXTCPS, after ensuring that their sum does not exceed the value of the maximum link managers allowed (currently 800).

Cause  PATHCOM command (ABORT/ADD/ALTER/DELETE/FREEZE/STOP/THAW/START) is issued on the objects configured under PATHMON.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The processor number mentioned in the CONTROL PATHMON SPREBALANCECPU command is down.

Effect  Rebalancing of the server processes cannot be started.

Recovery  Reload the processor and issue the command again.

Cause  No special server processes available for rebalancing.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  Pathway attribute SPREBALANCEMODE is not MANUAL.

Effect  Rebalancing of the server processes cannot be started.

Recovery  As the SPREBALANCEMODE is not MANUAL, this command is not needed. If the SPREBALANCEMODE is DISABLE, then rebalancing cannot happen. If the SPREBALANCEMODE is AUTO, then the rebalancing will happen automatically – no manual intervention is needed.

Cause  Illegal syntax entered for the command. The displayed error message will have more information about the syntax error.

Effect  The command fails.

Recovery  Correct the syntax and issue the command again.

Cause  PDMCOM fails to launch the process indicated by process-name. The displayed error message will have more information about the syntax error.

Effect  The command fails.

Recovery  Correct the failure condition indicated in the error message and issue the command again.

Cause  FC command was the first command to be issued at the PDMCOM prompt.

Effect  The command fails.

Recovery  Issue the FC command only if a previous command-line exists.

Cause  The string entered with the FC command does not match any prior command.

Effect  The command fails.

Recovery  Specify a valid string with the FC command and issue the command again.

Cause  FC command was issued with an invalid command number.

Effect  The command fails.

Recovery  Enter a valid command number, and then reissue the command.

Cause  The PDMHELP help file is not a 101 coded file or is not in a readable format.

Effect  HELP command, issued to receive help on the PDMCOM commands or the PDMCOM error numbers, fails.

Recovery  Change the file code to 101. If the file is not in a readable format, then reinstall the product.

Cause  No help is available for the text entered after the help keyword. This error might be caused because the entered text is not a:

Effect  The help on the requested topic does not appear.

Recovery  Enter a valid PDMCOM command, or a keyword related to PDMCOM, or a valid error/warning number, and issue the command again.

Cause  The PDMHELP help file is not found at the location where PDMCOM resides.

Effect  HELP command, issued to receive help on the PDMCOM commands or the PDMCOM error numbers, fails.

Recovery  Place the PDMHELP help file at the location where PDMCOM resides. If the file is missing from the system, then reinstall the product.

Cause  Help could not be made available at this time.

Effect  HELP command, issued to receive help on the PDMCOM commands or the PDMCOM error numbers, fails.

Recovery  Usually, this error follows error number 1507 or 1506. Correct the earlier error, and then reissue the command.

Cause  The string entered with FC command is too long.

Effect  The command fails.

Recovery  This error is very unlikely. Contact your Global Mission Critical Support Center (GMCSC) with a description of the application task that was in progress when the error was encountered.

Cause  PDMCOM was not able to parse the command correctly.

Effect  The command fails.

Recovery  This error is very unlikely. Contact your Global Mission Critical Support Center (GMCSC) with a description of the application task that was in progress when the error was encountered.

Cause  PDMCOM failed to communicate with the specified process name.

Effect  The command fails.

Recovery  Restart the Access Control Server (ACS). If this problem persists, contact your HP Nonstop representative.

Cause  PDMCOM failed to FREEZE or STOP the specified server in the specified PATHMON.

Effect  The command is aborted.

Recovery  Determine the reason for failure and initiate the corrective action accordingly. If the error is displayed during execution of an ALTER-DOMAIN command, then check the configuration of the server throughout the domain. Any inconsistency must be corrected manually.

Cause  Some unexpected error occurred.

Effect  The command is aborted.

Recovery  Take appropriate action depending on the error message.

Cause  The server entry, for which a FREEZE, STOP, ALTER, THAW, START, or ALTER-DOMAIN command was issued, is already locked.

Effect  The command is aborted.

	NOTE: The Lock failed error is also displayed when PDMCOM fails to communicate with the ACS subsystem. If the error appears, verify that the ACS subsystem is up and running.

Recovery  Wait for some time, and then reissue the command.

Cause  OPEN <domain name> is not issued prior to a domain-level command.

Effect  The domain related commands cannot be issued.

Recovery  Reissue the failed command after issuing an OPEN <domain name> command.

Cause  The number of PATHMONs in which the server class is configured, is less than or equal to one.

Effect  The command is aborted.

Recovery  Reissue the command after adding the serve class to more than one PATHMONs in the domain.

Cause  The specified domain name does not exist.

Effect  The domain is not opened.

Recovery  Specify the correct domain name, and then reissue the command.

Cause  Internal request of the ALTER-DOMAIN command to queue Pathsend requests failed.

Effect  The command is aborted.

Recovery  Reissue the ALTER-DOMAIN command.

Cause  Internal request of the ALTER-DOMAIN command to execute the queued Pathsend requests failed.

Effect  The command is aborted.

Recovery  Reissue the ALTER-DOMAIN command.

Cause  The system name specified in the OPEN or ALTER-DOMAIN command is not the local system name.

Effect  The command is aborted.

Recovery  Reissue the command after correcting the system name.

Cause  The PATHMON process specified with the PATHMON attribute of the ALTER-DOMAIN command is not a part of the domain opened by the earlier OPEN command.

Effect  The command is aborted.

Recovery  Specify the correct PATHMON name, and then reissue the command.

Cause  The server class specified in the ALTER-DOMAIN command is not a part of the PATHMON specified in the command.

Effect  The command is aborted.

Recovery  Specify the correct server class name, and then reissue the command.

Cause  The CONTROL DOMAIN PARTITION command was issued for a domain-server combination, which was already partitioned.

Effect  The command is rejected.

Recovery  Issue the CONTROL DOMAIN UNDO PARTITION command, and then reissue the command.

Cause  The CONTROL DOMAIN UNDO PARTITION command was issued for a domain-server combination, which was not partitioned.

Effect  The command is rejected.

Recovery  Issue the CONTROL DOMAIN PARTITION command, and then reissue the command.

Cause  The number of CONTROL DOMAIN PARTITON command reached the maximum value—128.

Effect  The command is rejected.

Recovery  Reduce the number of partition requests.

Cause  The command is issued when the ACS infrastructure is shutting down.

Effect  The command is rejected.

Recovery  Start the ACS Infrastructure, and then reissue the command.

Cause  PDMCOM failed to open an OBEY file. <error no> indicates the error during the OPEN operation.

Effect  The command fails.

Recovery  Check the error number, and try to resolve the error condition. If the problem persists, contact your HP NonStop representative.

Cause  PDMCOM failed to read an OBEY file.

Effect  The command fails.

Recovery  The OBEY file might be corrupt. Create a new OBEY file and reissue the command. If the problem persists, contact your HP NonStop representative.

Cause  The FC command is issued in an OBEY file.

Effect  The command fails.

Recovery  Remove the FC command from the OBEY file and reissue the command.

Cause  The redisplay command is issued in an OBEY file.

Effect  The command fails.

Recovery  Remove the redisplay command from the OBEY file and reissue the command.

Cause  The re-execute command is issued in an OBEY file.

Effect  The command fails.

Recovery  Remove the re-execute command from the OBEY file and reissue the command.

Cause  The HISTORY command is issued in an OBEY file.

Effect  The command fails.

Recovery  Remove the HISTORY command from the OBEY file and reissue the command.

Cause  PDMCOM cannot interpret the file name because it might be invalid.

Effect  The command fails.

Recovery  Check the file name supplied. Correct any error in the file name. If the problem persists, contact your HP NonStop representative.

Cause  The OBEY file name is not supplied.

Effect  The command fails.

Recovery  Specify an OBEY file name and reissue the command.

Cause  The OBEY file supplied contains non-printable characters.

Effect  The command fails.

Recovery  Check the OBEY file supplied. Remove any non-printable characters from the OBEY file and reissue the command.

Cause  An abort request failed.

Effect  None

Recovery  Determine the cause for the failure and re-issue the abort request.

Cause  An abort request failed.

Effect  None

Recovery  Determine the cause for the failure and re-issue the abort request.

Cause  The PATHMON process is not open.

Effect  The request to the PATHMON process fails.

Recovery  Use the PATHCOM OPEN command with the PATHMON process name.

Cause  The indicated server class has been frozen.

Effect  None

Recovery  Informational message only; no corrective action is required.

Cause  The value specified for an attribute is not within the valid range.

Effect  The command fails.

Recovery  Respecify the value in the valid range for that attribute.

Cause  The processor number is not in the range 0-15, or the same processor number is defined for the object’s primary and backup processes.

Effect  The command fails.

Recovery  Redefine the processor number with a correct value.

Cause  A file name did not conform to file-naming conventions. PATHCOM checks for valid network file names in the ASSIGN, IN, OUT, PROGRAM, SWAP, TCLPROG, FILE, and PRINTER attributes.

Effect  The command fails.

Recovery  Rename the file with a valid name.

Cause  The number format entered is not valid.

Effect  The command fails.

Recovery  Enter a valid number.

Cause  The priority value entered is not in the 0-255 range.

Effect  The command fails.

Recovery  Enter a valid priority value.

Cause  The syntax for the newly introduced or modified command is incorrect.

Effect  The command fails.

Recovery  Enter the input characters by using the correct syntax.

Cause  The time value entered cannot be represented in 16 bits.

Effect  The command fails.

Recovery  Enter an acceptable time value.

Cause  An internal consistency check failed in PATHCOM.

Effect  The contents of the program register(%p-reg) is displayed; PATHCOM does not terminate.

Recovery  Contact your Global Customer Support Center (GCSC). Before contacting the GCSC, please have this information available:

This information is invaluable for the support staff to be able to understand the problem and help fix the problem.

Cause  A reply was received that does not comply with the NonStop TS/MP internal interprocess message protocol. This error can be caused by:

Effect  The reply fails.

Recovery  Depending on the cause, run compatible versions of PATHCOM and the PATHMON process, ensure that PATHCOM is accessing a PATHMON process, or provide network names for terminals.

Cause  The closing quotation mark is missing from a character string.

Effect  The command fails.

Recovery  Enter the closing quotation mark and resubmit the command.

Cause  A required attribute is missing, or the attribute is invalid for this command.

Effect  The command fails.

Recovery  Enter the required attribute and resubmit the command.

Cause  No free space is available in the PATHCOM internal data area.

Effect  The operation fails.

Recovery  Contact your Global Customer Support Center (GCSC).

This information is invaluable for the support staff to be able to understand the problem and help fix the problem.

Cause  The object name in a PATHCOM command does not exist.

Effect  The command fails.

Recovery  Enter a correct object name and resubmit the command.

Cause  A response is needed but PATHCOM is running noninteractively. This message is equivalent to the interactive DO YOU WISH TO CONTINUE? prompt.

Effect  Because PATHCOM is in noninteractive mode, the process terminates.

Recovery  Enter the required response.

Cause  The named terminal has resumed operation.

Effect  None.

Recovery  Informational message only; no corrective action is required.

	NOTE: You will receive this message only if you are using the Pathway/iTS product

Cause  The named object is running.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  The named object is stopped.

Effect  None.

Recovery  Informational message only; no corrective action is required.

Cause  An input string exceeded the maximum acceptable length.

Effect  The request fails.

Recovery  Resubmit the input string with a valid length.

Cause  The named terminal is suspended.

Effect  None

Recovery  Informational message only; no corrective action is required.

Cause  The primary and backup processes of the named TCP exchanged operation in response to a TCP SWITCH command.

Effect  The command completed successfully.

Recovery  Informational message only; no corrective action is required.

	NOTE: You will receive this message only if you are using the Pathway/iTS product.

Cause  This is an internal PATHCOM error.

Effect  The operation fails.

Recovery  Contact your Global Customer Support Center (GCSC).

This information is required for the support staff to be able to understand the problem and help fix the problem.

Cause  A tell message with the indicated message identification is pending.

Effect  None

Recovery  Informational message only; no corrective action is required.

Cause  The named server class is thawed.

Effect  None

Recovery  Informational message only; no corrective action is required.

Cause  The number of nested command files exceeded the maximum depth of 4.

Effect  The command fails.

Recovery  Rewrite the command files with 4 or less nested files.

Cause  The number of processor pairs exceeded the maximum number of 16.

Effect  The command fails.

Recovery  Specify 16 or less processor pairs.

Cause  The number of defined servers exceeded the maximum value defined for the MAXSERVERS attribute.

Effect  The command fails.

Recovery  Reduce the number of defined servers or increase the value of the MAXSERVERS attribute in the SET SERVER command.

Cause  The limit for the configured number of PARAMs has been reached.

Effect  The SET SERVER PARAM command fails.

Recovery  Reduce the number of PARAM messages.

Cause  PATHCOM is trapped because of a hardware or software failure. These values reflect the process environment at the time PATHCOM failed:

Effect  PATHCOM fails.

Recovery  Contact your Global Customer Support Center (GCSC). Before contacting the GCSC, please have this information available:

Cause  The microcode required for operating NonStop TS/MP has not been installed in the system.

Effect  NonStop TS/MP cannot run.

Recovery  Load the required NonStop TS/MP microcode and start the PATHMON objects.

Cause  The process name contained more than five characters including the dollar sign ($).

Effect  The command fails.

Recovery  Reenter the process name with the correct amount of characters.

Cause  The value specified for a security attribute was invalid.

Effect  The command fails.

Recovery  Enter the correct security attribute.

Cause  The value specified for a user name was invalid.

Effect  The command fails.

Recovery  Enter the correct user name.

Cause  The value specified for the LINKDEPTH attribute was either 0 or greater than 255.

Effect  The command fails.

Recovery  Enter a correct value for the LINKDEPTH attribute.

Cause  A RUN command is allowed in interactive mode only.

Effect  The command fails.

Recovery  Re-enter the command in interactive mode.

Cause  The value specified for TERM TYPE is invalid.

Effect  The command fails.

Recovery  Enter a correct value for TERM TYPE.

	NOTE: You will receive this message only if you are using the Pathway/iTS product.

Cause  The number of static servers defined for a server class is greater than the maximum value specified for the MAXSERVERS attribute for that class.

Effect  The command fails.

Recovery  Reduce the number of static servers defined or increase the value of the MAXSERVERS attribute.

Cause  There is no PATHMON environment error defined with this number.

Effect  The error request fails.

Recovery  Enter a valid error number.

Cause  The TCP has read the requested program unit code segment into memory after checking the SCREEN COBOL object directory file.

Effect  The TCP uses the latest version of each program unit.

Recovery  Informational message only; no corrective action is required.

Cause  The primary process is running in its configured processor.

Effect  The PRIMARY TCP command completed successfully.

Recovery  Informational message only; no corrective action is required.

Cause  A RUN PROGRAM command was issued with the NOWAIT option but the FILE attribute was not specified; or NOWAIT was specified, but the name of the PATHCOM command terminal was entered for the FILE attribute. A program cannot be run with the NOWAIT option set on the PATHCOM command terminal.

Effect  The command fails.

Recovery  Either specify the FILE attribute or specify a terminal other than the PATHCOM command terminal when using the NOWAIT option.

Cause  An attempt was made to execute PATHCOM on a version of the HP NonStop operating system previous to the C40 release. PATHCOM requires the features supported by later releases of the operating system.

Effect  PATHCOM abends.

Recovery  Obtain and install the correct release of the operating system. Contact your Global Customer Support Center (GCSC). Before contacting the GCSC, please have this information available:

Cause  An ALTER command was issued that attempted to reset a required attribute.

Effect  The command fails.

Recovery  Stop the PATHMON environment, redefine the attribute using the SET command, and restart the PATHMON environment.

Cause  An error occurred, identified by the error number, in a procedure call to the DEFINE procedure library.

Effect  The operation fails.

Recovery  For information concerning the specified DEFINE error, refer the Guardian Procedure Errors and Messages Manual.

Cause  The size of the DEFINE definition being added to a server class exceeds the PATHMON process internal limit.

Effect  The DEFINE definition is not added.

Recovery  Correct the size of the DEFINE.

Cause  PATHCOM is not able to parse or display the DEFINE definitions. This error can occur, for example, if one or more of the required DEFINE procedures, such as DEFINESAVE and DEFINERESTORE, are not available.

Effect  The DEFINE operation fails.

Recovery  Contact your Global Customer Support Center (GCSC). Before contacting the GCSC, please have this information available:

Cause  The START PATHWAY COLD command (without the ! option) was issued, the PATHCTL file exists, and the stored configuration is valid.

Effect  The PATHMON environment can be cool started from the existing PATHCTL file.

Recovery  If you choose to continue the command, the current PATHCTL file is overwritten.

Cause  The START COLD command (without the ! option) was issued. Although the PATHCTL file exists and the stored configuration is valid, the PATHMON process name specified in the START command is different from the PATHMON process name stored in the PATHCTL file.

Effect  The PATHMON environment can be cool started from the existing PATHCTL file using the old PATHMON process name, or the PATHMON environment can be cold started using the new PATHMON process name specified in the START command.

Recovery  If you choose to continue, the current PATHCTL file is overwritten and the new PATHMON process name is used.

Cause  An attribute you defined for an OSS server process is valid only for Guardian server processes.

Effect  The SET, ADD, or ALTER command fails.

Recovery  Remove the inappropriate attribute definition from the server class configuration by using the RESET SERVER command.

Cause  An attribute you defined for a Guardian server process is valid only for OSS server processes.

Effect  The SET, ADD, or ALTER commands fail.

Recovery  Re-enter the command in interactive mode.

Cause  The value for an OSS server process attribute exceeded the maximum length.

Effect  The SET, ADD, or ALTER command fails.

Recovery  Define a value for the attribute within the valid range.

Cause  An OSS pathname in the command is invalid due to a disallowed forward slash (/) or null character.

Effect  The attribute value for the OSS server process is not set.

Recovery  Make sure that OSS pathnames (other than those specified for the CWD attribute or the CMDCWD command) do not have a forward slash (/) as the last character.

Cause  The combined length of the values defined for the server class attributes ARGLIST and ENV exceed the 24,000-character maximum.

Effect  Whichever attribute was specified last, ARGLIST or ENV, is not set.

Recovery  Set the ARGLIST and ENV values within the allowed maximum length. See the description of the ARGLIST and ENV attributes in Managing the Pathsend Environment.

Cause  A relative pathname was entered for the specified OSS attribute. When PATHCOM resolved the relative pathname, using the OSS directory specified in the CWD attribute or the CMDCWD command, the resulting absolute pathname exceeded the maximum 1023 bytes allowed.

Effect  The server class ADD or ALTER command fails.

Recovery  Redefine the default directory or the relative pathname for the specified attribute within the allowed maximum length.

Cause  The value specified for the CWD attribute was not an absolute pathname. If no pathname has been defined for the CWD attribute, then the pathname entered for the specified OSS attribute is not an absolute pathname.

Effect  If you attempted to set the CWD attribute, the pathname is rejected and the attribute is not set. If you attempted to add or alter other OSS attributes, the ADD or ALTER command fails.

Recovery  Either specify an absolute pathname for the given attribute or set an absolute pathname using the SET SERVER CWD command or the CMDCWD command. See the descriptions of the OSS attributes in Managing the Pathsend Environment.

Cause  The value specified for the PROCESSTYPE attribute conflicts with values set for other attributes in the server class.

Effect  The value for the PROCESSTYPE attribute is not changed.

Recovery  Reset all conflicting attribute values before changing the value of PROCESSTYPE.

Cause  The SET PATHWAY NODEINDEPENDENT attribute is set to ON, but a value other than \* was specified by the CMDVOL command as the node name in the default settings for file name expansion.

Effect  The \* node name specification conflicts with the NODEINDEPENDENT attribute setting.

Recovery  Perform one of these.

Cause  The CPU weight is not in the range of 1 through 100. Or, summation of all the weights is not equal to 100.

Effect  The command fails.

Recovery  Redefine the CPU weight with a correct value.

Cause  Pathway attribute SPREBALANCEMODE is not MANUAL, AUTO, or DISABLE.

Effect  Pathway attribute SPREBALANCEMODE will not be set.

Recovery  Set SPREBALANCEMODE as MANUAL, AUTO, or DISABLE.

Cause  A SCREEN COBOL object file is corrupted, or the SCREEN COBOL compiler generated invalid code. This is an internal error.

Effect  The terminal is suspended.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the GlobalGlobal Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The value of a DEPENDING ON data item was larger than the limit specified in the OCCURS clause.

Effect  The terminal is aborted; the operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The value of a subscript expression either is zero or is larger than the limit implied by the OCCURS clause.

Effect  The terminal is aborted; the operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  A terminal control process (TCP) detected a SCREEN COBOL verb that is not allowed during screen recovery.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The number of parameters passed in the USING clause of a CALL statement does not equal the number of parameters given in the Procedure Division header of the called program.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The maximum size of a parameter passed in the USING clause of a CALL statement does not equal the maximum size of the corresponding parameter given in the Procedure Division header of the called program.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  A screen-manipulation operation was attempted before a DISPLAY BASE statement was executed.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The terminal control process (TCP) detected an attempt to reference data outside the SCREEN COBOL program’s local data area.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The terminal control process (TCP) detected an attempt to execute a SCREEN COBOL program unit on an incompatible device. Or, if the device type is compatible, then an internal error has occurred.

Effect  The operation fails.

Recovery  Check that the terminal type specified when the program unit was compiled is compatible with the physical terminal. If necessary, resolve the incompatibility. Otherwise, an internal error has occurred; contact your service provider 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.

Cause  There is an error in the terminal’s format routines. This is an internal error.

Effect  The operation fails.

Recovery  Check that the terminal type specified when the program unit was compiled is compatible with the physical terminal. If necessary, resolve the incompatibility. Otherwise, an internal error has occurred; contact your service provider 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.

Cause  The terminal control process (TCP) detected an attempt to execute a SCREEN COBOL program unit on an incompatible device. Or, if the device type is compatible, then an internal error has occurred.

Effect  The operation fails.

Recovery  Check that the terminal type specified when the program unit was compiled is compatible with the physical terminal. If necessary, resolve the incompatibility. Otherwise, an internal error has occurred; contact your service provider 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.

Cause  A screen was referenced but is not displayed. The screen is identified by a screen number.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The terminal control process (TCP) detected an attempt to display an overlay screen in more than one overlay area at the same time.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The terminal control process (TCP) detected an invalid I/O protocol value; or an internal Pathway error occurred.

Effect  The operation fails.

Recovery  If an invalid I/O protocol value was detected, contact the application programmer.

If an internal error occurred, contact your service provider 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.

Cause  A data-related error occurred during numeric manipulation. The error can be caused by an overflow, by dividing by zero, by an invalid value in a numeric data item (for example, blank spaces in a USAGE DISPLAY item), or by attempting to move a value into a data item that is not large enough to hold it.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The limit configured for the MAXTERMDATA attribute in the SET TCP command was exceeded.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  A file-system error occurred while a terminal control process (TCP) was opening the specified terminal.

Effect  The program terminates abnormally.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A file-system error occurred while a terminal control process (TCP) was performing a terminal I/O operation.

Effect  The I/O operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  The write count provided by the terminal control process (TCP) did not match the count written (returned by the terminal). This might be caused by a terminal hardware problem.

Effect  The I/O operation fails.

Recovery  The INFO field returned by the STATUS TERM command displays the transfer count requested by the TCP. Run terminal diagnostics for the device and make any necessary repairs.

If this error is not caused by a hardware problem and a front-end process is being used, check that it is correctly coded to emulate the type of device that was specified. If a front-end process is not being used, locate the problem within the program.

Cause  The program unit specified in a CALL statement was not found in the TCLPROG files.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  A SCREEN COBOL SEND operation to a server failed for the reason indicated in an earlier operator message.

Effect  If the transaction message was sent to the server, the system does not know how much processing was done by the server before the failure.

Recovery  Recovery depends on why the SEND operation failed as indicated by an earlier operator message. See the description of that message for additional information.

Cause  The value specified in a SCREEN COBOL SEND statement does not have the format of a valid server class name.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The size of a program unit’s code is greater than that allowed by the CODEAREALEN attribute.

Effect  The program terminates abnormally.

Recovery  Increase the value for the CODEAREALEN attribute. Use the compiler listing for the program unit to determine the minimum size that can be specified for the attribute.

Cause  The TCLPROG directory (DIR) file is corrupt. This is an internal error.

Effect  The program terminates abnormally.

Recovery  Contact your service provider 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.

Cause  Input data received from the terminal does not have the structure expected by the terminal control process (TCP), even after screen recovery and retries.

Effect  The I/O operation fails.

Recovery  Run diagnostics for the device.

If a front-end process is being used, check that it is correctly coded to emulate the type of the device that was specified.

Cause  The requested operation does not match the transaction mode state.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  A file-system error occurred during a call to a Transaction Management Facility (TMF) procedure.

Effect  The call to the TMF procedure fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  The terminal control process (TCP) attempted to restart a transaction more than the number of times defined for the MAXTMFRESTARTS attribute.

Effect  The transaction is not restarted.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  An attempt to use the Transaction Management Facility (TMF) failed because TMF auditing is not configured in this system.

Effect  None.

Recovery  Configure TMF auditing or isolate and correct the problem within the SCREEN COBOL program.

Cause  An attempt to use the Transaction Management Facility (TMF) failed because the TMF software was not running.

Effect  None.

Recovery  Configure and start TMF auditing or isolate and correct the problem within the SCREEN COBOL program.

Cause  A file-system error occurred while the TCP backup process was opening the Transaction Management Facility (TMF) TFILE.

Effect  The operation fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, refer to the Guardian Procedure Errors and Messages Manual.

Cause  A terminal I/O operation requires a larger buffer than defined by the TERMBUFF attribute in the terminal control process (TCP) configuration.

Effect  The operation fails.

Recovery  Use the SET TCP command to define a larger value for the TERMBUF attribute.

Cause  A program unit (PU) was called with a USE FOR TERMINAL-ERRORS statement from a USE FOR TERMINAL-ERRORS declarative.

Effect  The call fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  An illegal timeout value was used in an ACCEPT statement. The value was either less than 0 or too large to be represented in an INT(32) field.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.

Cause  The field referenced in a verb does not contain numeric data. To find the item name that caused the error, find the indicated number in the DESC column and read across to the left.

Effect  The operation fails.

Recovery  Contact the application programmer. The descriptor number appears on the compiler listing if you included the ?MAP or ?SMAP option in your program.

Cause  Either an invalid device was specified or the printer for the IBM 3270 terminal is not attached to the same control unit as the terminal.

Effect  The operation fails.

Recovery  Isolate and correct the problem within the SCREEN COBOL program.