Operator Messages Manual

Chapter 40 GDSX (Extended General Device Support) Messages

spacerspacerspacer
spacer
spacer
  		 
 

The messages in this chapter are sent by the Extended General Device Support (GDSX) product. You will find references to GDSX as well as General Device Support (GDS) in this chapter. GDS represents the subsystem id. while GDSX indicates the product name.

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.


1001

\sys.$process-name: STATUS *1001* GDS - banner, Started

Cause  GDSX started.

Effect  None.

Recovery  Informational message only; no corrective action is needed.



1002

\sys.$process-name: STATUS *1002* GDS - Normal Shutdown

Cause  GDSX performed an orderly shutdown.

Effect  None.

Recovery  Informational message only; no corrective action is needed.



1003

\sys.$process-name: WARNING *1003* DEVICE^HANDLER procedure not bound

Cause  The DEVICE^HANDLER procedure is not bound in the GDSX object code. GDSX issues this message during initialization.

Effect  GDSX initialization continues.

Recovery  If you want the DEVICE^HANDLER procedure bound to GDSX, stop GDSX initialization. Make sure that a user binding file for a valid DEVICE^HANDLER procedure is bound to GDSX, then reinitialize GDSX.



1004

\sys.$process-name: WARNING *1004* LINE^HANDLER procedure not bound

Cause  The LINE^HANDLER procedure is not bound in the GDSX object code. GDSX issues this message during initialization.

Effect  GDSX initialization continues.

Recovery  If you want the DEVICE^HANDLER procedure bound to GDSX, stop GDSX initialization. Make sure that a user binding file for a valid LINE^HANDLER procedure is bound to GDSX, then reinitialize GDSX.



1005

\sys.$process-name STATUS: *1005* GDS User Terminated

Cause  The specified GDSX process was shut down in an orderly manner, using the following SCF command:

STOP PROCESS process-name !

(The ! option terminates external openers before their tasks are complete.)

Effect  All existing openers are terminated and the specified GDSX process is shut down. The file system returns error 66, device downed.

Recovery  Informational message only; no corrective action is needed.



1006

\sys.$process-name: STATUS *1006* GDS Shutdown Pending

Cause  An attempt was made to shut down the specified GDSX process in an orderly manner, using the following SCF command:

STOP PROCESS process-name

Effect  The STOP PROCESS is executed after all existing openers are closed or terminated.

Recovery  Close or terminate existing openers and reissue the STOP PROCESS command.



1021

\sys.$process-name: ERROR *1021* dev-type dev-num (dev-name) - Fault Number: nnn

Cause  GDSX detected a task fault.

Effect  The effect depends on the application.

Recovery  See the Extended General Device Support (GDSX) Programming Manual for information about the specified fault. Recovery is application-dependent and fault-dependent.



1022

\sys.$process-name: STATUS *1022* dev-type dev-num (dev-name) - Started

Cause  GDSX created a new task.

Effect  None.

Recovery  Informational message only; no corrective action is needed.



1023

\sys.$process-name: STATUS *1023* dev-type dev-num (dev-name) - Stopped

Cause  GDSX stopped a task.

Effect  None.

Recovery  Informational message only; no corrective action is needed.



1024

\sys.$process-name: STATUS *1024* dev-type dev-num (dev-name) - Opened by: opener

Cause  GDSX accepted an OPEN message from a requester.

Effect  None.

Recovery  Informational messages only; no corrective action is needed.



1025

\sys.$process-name: STATUS *1025* dev-type dev-num (dev-name) - Aborted

Cause  GDSX aborted a task.

Effect  None.

Recovery  Informational messages only; no corrective action is needed.



1026

\sys.$process-name: STATUS *1026* dev-type dev-num (dev-name) - Closed by: opener

Cause  A requester closed a task.

Effect  None.

Recovery  Informational messages only; no corrective action is needed.



1027

\sys.$process-name: STATUS *1027* dev-type dev-num (dev-name) - Restarted

Cause  GDSX restarted a task. The GDSX primary process failed prior to the restart.

Effect  None.

Recovery  Informational messages only; no corrective action is needed.



1041

\sys.$process-name: ERROR *1041* CheckPoint Failure: err

Cause  The specified I/O error occurred during a checkpoint operation.

Effect  The GDSX primary process stops the backup process, then creates a new GDSX backup process.

Recovery  If the GDSX primary process fails to recreate the backup process, or if the primary process loops, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1042

\sys.$process-name: ERROR *1042* CheckOpen Failure: err

Cause  A GDSX backup process's call to CHECKOPEN failed.

See the Guardian Procedure Calls Reference Manual for information on the error number.

Effect  The GDSX primary process stops the backup process, then creates a new GDSX backup process.

Recovery  If the GDSX primary process fails to recreate the backup process, or if the primary process loops, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1043

\sys.$process-name: ERROR *1043* Unable to create backup process - NEWPROCESS error: err - File-system error: errnum

Cause  A NEWPROCESS error and a file-system error occurred while a GDSX process was trying to create a backup process.

Effect  The GDSX primary process does not create the backup process.

Recovery  For information on the errors, see Appendix B and Appendix C. If necessary, contact your Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable”

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.



1044

\sys.$process-name: WARNING *1044* Unable to open backup process - Error: err

err

is an input/output (I/O) error number.

Cause  A GDSX process could not open its backup process.

Effect  The GDSX primary process runs without a backup process.

Recovery  Contact your Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1045

\sys.$process-name: WARNING *1045* Unable to write to backup process - Error: err

Cause  A GDSX process could not write to its backup process. The error is an I/O error number.

Effect  The GDSX primary process stops the backup process, and then creates a new GDSX backup process.

Recovery  If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1046

\sys.$process-name: WARNING *1046* Backup Deleted

Cause  A GDSX backup process was deleted.

Effect  The GDSX primary process runs without a backup process.

Recovery  The GDSX primary process will create its backup process. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1047

\sys.$process-name: ERROR *1047* Backup Abended

Cause  A GDSX backup process abended.

Effect  The GDSX primary process runs without a backup process.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1048

\sys.$process-name: WARNING *1048* Backup Stopped

Cause  A GDSX backup process was stopped.

Effect  The GDSX primary process waits 30 seconds, then recreates the backup process.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1049

\sys.$process-name: WARNING *1049* Takeover by Backup: { Primary Stopped | Primary Abended | Primary CPU Failure | Operator Command }

Cause  A GDSX backup process took over from its primary process because the primary process was stopped by an operator command, the primary process abended, the primary processor failed, or an operator command initiated a primary switch.

Effect  The GDSX backup process becomes the primary process.

Recovery  If the primary process abended, investigate the event log to determine why.

If the primary processor failed, follow the recommended recovery procedure for a processor failure. Otherwise, no corrective action is needed.



1050

\sys.$process-name: STATUS *1050* Backup Created in CPU cpu

Cause  A GDSX backup process was created.

Effect  None.

Recovery  Informational message only; no corrective action is needed.



1051

\sys.$process-name: STATUS *1051* Maximum Checkpoint Size Exceeded - Backup Terminated

Cause  The checkpoint information exceeds the configured checkpoint buffer size.

Effect  The GDSX backup process stops. The primary process recreates the backup process.

Recovery  Use the command INFO PROCESS to find the configured checkpoint buffer size. Reconfigure GDSX and increase the checkpoint buffer size.



1052

\sys.$process-name: ERROR *1052* Checkpoint Table Overflow - Backup Terminated

Cause  The checkpoint table overflowed.

Effect  The GDSX backup process stops. The primary process reestablishes the backup process.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1053

\sys.$process-name: ERROR *1053* INTERNAL ERROR at %E-register.P-register

Cause  GDSX detected an unrecoverable internal error. There is a logic problem in the program reporting the error.

Effect  GDSX stops.

Recovery  Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

  • Descriptions of the problem and accompanying symptoms

  • Details from the message or messages generated

  • Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.



1054

\sys.$process-name: ERROR *1054* dev-type dev-num (dev-name) - C-Series Call attempted Fault Numer: nnn

Cause  A converted GDSX user task attempted to call a restricted C-series procedure.

Effect  Call returns with condition code < (CCL). The procedure is not executed.

Recovery  Call the D‑series procedure that has superseded the restricted C‑series procedure.



1055

\sys.$process-name: ERROR *1055* dev-type dev-num (dev-name) - D-Series Call attempted Fault Numer: nnn

Cause  An unconverted GDSX user task attempted to call a restricted D-series procedure.

Effect  File-system error 5601 is returned and the procedure is not executed. See Appendix B, or to the Guardian Procedure Errors and Messages Manual for more information.

Recovery  Call the corresponding C-series procedure.



Chapter 39 FCS Monitor Messages
  		 


Chapter 41 GUARDIO Messages