Chapter 53 Monitor Messages

Cause  During a cold-load or reload operation, the sender processor monitor process could not access the operating-system images and returned the specified file-system error. Either the specified switch value is incorrect, or the subvolume specified by the system number doesn't contain an OSIMAGE file.

Effect  The system freezes with halt code %2002.

Recovery  Make sure that the cold-load switch value correctly specifies the system‑disk subchannel address and system number. You can load a previous system image and use FUP to find the correct system subvolume.

Contact your system manager.

	NOTE: This message is applicable only to D-series RVUs.

Cause  TMDSAUTO was started.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

	NOTE: This message is applicable only to D-series RVUs.

Cause  A PROCESS_CREATE_ error occurred while TMDSAUTO was starting.

Effect  TMDSAUTO does not start.

Recovery  See Appendix D, for a brief explanation of the specified error. See the Guardian Procedure Calls Reference Manual for detailed information on the error and error detail.

Start the Tandem Maintenance Diagnostic System (TMDS) manually. The program file is TMDSAUTO and should be on the SYSnn subvolume. If it is missing, someone probably purged the file or something went wrong during installation.

If neither is the case, contact your service provider for the TMDS product 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.

	NOTE: This message is applicable only to D-series RVUs.

Cause  The specified file-system error occurred while TMDSAUTO was reading its startup message.

Effect  TMDSAUTO does not start.

Recovery  Start TMDS manually. The program file is TMDSAUTO and should be on the SYSnn subvolume. If it is missing, someone probably purged the file, or something went wrong during installation.

	NOTE: This message is applicable only to D-series RVUs.

Cause  The Configuration Utility Program (COUP) was started.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

	NOTE: This message is applicable only to D-series RVUs.

Cause  The specified PROCESS_CREATE_ error occurred while the Configuration Utility Program (COUP) was starting.

Effect  COUP does not start.

Recovery  See Appendix D, for a brief explanation of the specified error. See the Guardian Procedure Calls Reference Manual for detailed information.

Start COUP manually. Check whether the program file, COUP, is on the SYSnn subvolume. Then contact your service provider for the COUP product 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.

	NOTE: This message is applicable only to D-series RVUs.

Cause  The specified file system error can occur during one of the following:

Effect  The online or dynamic system changes implemented by means of this COUP process are lost.

Recovery  Look up errnum in the Guardian Procedure Errors and Messages Manual, perform the required recovery, and repeat the processor cold load or reload procedure.

	NOTE: This message is applicable only to D-series RVUs.

Cause  A system-monitor process could not create the startup command interpreter during a system-load operation because of the specified PROCESS_CREATE_ error.

Effect  The system freezes with halt code %2003.

Recovery  See Appendix D, for a brief explanation of the specified error. See the Guardian Procedure Calls Reference Manual for detailed information on the specified error and error detail.

Make sure that your startup command interpreter exists on the system subvolume that you are loading. If it does not exist, load it onto the system subvolume, then restart the system load. If the startup command interpreter does exist on the subvolume, 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.

	NOTE: This message is applicable only to D-series RVUs.

Cause  The CONFTEXT file has an entry requiring reading of the CIIN file and an error has been encountered when opening this file.

Effect  The initial TACL process is started and left in the logged off state. Therefore, the commands in the CIIN file are not executed.

Recovery  If the CONFTEXT file has a CIIN entry, the CIIN file must be present in the sysnn subvolume. Ensure that the file is present. At the TACL prompt, LOGON to the system as the SUPER.SUPER user and complete the system startup process by obeying the CIIN file. See the TACL Reference Manual for information about the TACL commands: LOGON and OBEY.

Cause  The Open System Services (OSS) Pipe Server process was started.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The Open System Services (OSS) File Manager process was started.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A PROCESS_CREATE_ error occurred when the system monitor process attempted to start the Open System Services (OSS) Pipe Server.

Effect  The OSS Pipe Server does not start. The system may continue running with OSS disabled, or it may halt.

Recovery  See Appendix D, for a brief explanation of the specified error. See the Guardian Procedure Calls Reference Manual for detailed information on the specified error and error detail.

Take the corrective action needed, then reboot.

Cause  The specified PROCESS_CREATE_ error occurred when the system monitor process attempted to start the Open System Services (OSS) File Manager.

Effect  The OSS File Manager did not start. The system may continue running with OSS disabled, or it may halt.

Recovery  See Appendix D, for a brief explanation of the specified error. See the Guardian Procedure Calls Reference Manual for detailed information on the specified error and error detail.

Take the corrective action needed, then reboot.

Cause  Either the Open System Services (OSS) Pipe Server program file or the OSS File Manager program file is missing from the SYSnn subvolume.

	NOTE: When both files are missing, no message is printed. This case is normal for a system in which Open System Services are not required.

Effect  The OSS Pipe Server and File Manager did not start. The system performs a system load, but cannot run OSS programs.

Recovery  The program files for the OSS Pipe Server and the OSS File Manager are OSSPS and OSSFM, respectively. Make sure that both these files are present in the SYSnn subvolume, then reboot.

Cause  The OSS socket transfer agent process was started. This process is given the name $ZTAnn, where nn is the processor number.

Effect  None.

Recovery  This is an informational message only; no corrective action is needed.

Cause  A PROCESS_CREATE_ error occurred when the system monitor attempted to start the OSS socket transport agent.

Effect  The OSS socket transport agent does not start. The system continues running with OSS sockets disabled.

Recovery  The program file for the OSS socket transport agent is $SYSTEM.SYSnn.OSSTA, where nn is a two-digit octal integer that identifies the subvolume from which the system was loaded. It is run with a process name of $ZTAnn, where nn is the processor number.

Take the corrective action needed to allow this program to run. The preferred recovery action is to reload or reboot the processor in which the startup failed. The system monitor then automatically attempts a restart.

A less desirable alternative is to restart the OSS socket transport agent manually by logging on as the super ID and running the OSSTA program in the desired processor with the process of $ZTAnn, where nn is the processor number.

Cause  The OSS terminal helper server process was started. This process is given the name $ZTTnn, where nn is the processor number.

Effect  None.

Recovery  This is an informational message only; no corrective action is needed.

Cause  A PROCESS_CREATE_ error occurred when the system monitor attempted to start the OSS terminal helper server process.

Effect  The OSS terminal helper server process does not start. The system continues running with OSS nonblocking terminal input/output disabled.

Recovery  The program file for the OSS terminal helper server process is $SYSTEM.SYSnn.OSSTH, where nn is a two-digit octal integer that identifies the subvolume from which the system was loaded. It is run with a process name of $ZTTnn, where nn is the processor number.

Take the corrective action needed to allow this program to run. The preferred recovery action is to reload or reboot the processor in which the startup failed. The system monitor then automatically attempts a restart.

A less desirable alternative is to restart the OSS terminal helper server process manually by logging on as the super ID and running the OSSTH program in the desired processor with the process of $ZTTnn, where nn is the processor number.

Cause  The system monitor successfully started the OSS Server Process (OSP).

Effect  None.

Recovery  This is an informational message only; no corrective action is needed.

Cause  The system monitor could not start the OSS Server Process (OSP) process as part of starting the processor.

Effect  The OSP process does not start. Pthreads applications that use thread-aware functions for OSS regular files might experience degraded performance when running in the processor that generated this error.

Recovery  Move applications that use thread-aware regular file I/O to other processors.

Contact your service provider and provide all relevant information:

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 OSS AF_UNIX Release 2 local server 2 process was started in the processor indicated by the server process name.

Effect  The process is given the name $ZLSnn, where nn is the processor number.

Recovery  Informational message only; no corrective action is needed.

Cause  A PROCESS_CREATE_ error occurred when the system monitor attempted to start the OSS local server 2 process $ZLSnn, where nn is the processor number.

	NOTE: This message is not sent if the program file $SYSTEM.SYSnn.OSSLS2 is missing.

Effect  The OSS local server 2 server does not start. Applications that use AF_UNIX sockets might encounter errors.

Recovery  The program file for the OSS AF_UNIX local server 2 (LS2) server is $SYSTEM.SYSnn.OSSLS2, where nn is a two-digit octal integer that identifies the subvolume from which the system was loaded. It is run with a process name of $ZLSnn, where nn is the processor number.

Take the corrective action needed to allow this program to run: