The messages in this chapter are generated by the Application Cluster Services (ACS) 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.

ACS Subsystem Identifiers

ACS subsystem number for NonStop OS SPI subsystems	252
ACS subsystem name in the NonStop OS	APPCLSTR
ACS subsystem name abbreviation	ACL
External ACS subsystem identifier for release TS/MP 2.1. This identifier occurs in event message text, which is typically produced by EMS event printing distributors for EMS formatted event messages logged by ACS subsystem processes.	TANDEM.APPCLSTR.G06

1001

1001 - Backup process created in CPU cpu-number

cpu-number

the number of the CPU on the local system in which the backup domain coordinator process was started.

Cause The backup domain coordinator process was successfully created in the indicated CPU. This is a status message.

Effect The backup domain coordinator process runs in the indicated CPU.

Recovery Informational message only; no corrective action is needed.

1002

1002 - Backup process creation in CPU cpu-number failed, error errnum, detail error-detail

`cpu-number`	the number of the CPU on the local system in which the backup domain coordinator process could not be started.
`errnum`	the process-creation error code returned by the PROCESS_LAUNCH_() procedure.
`error-detail`	the process-creation error detail code returned by the PROCESS_LAUNCH_() operation. If the value of this field is 0 (zero), the field is omitted from the message.

Cause The domain coordinator process cannot create a backup process in the specified CPU on the local system because the PROCESS_LAUNCH_() operation failed. This is a warning message.

Effect The domain coordinator process runs as a single process.

Recovery Correct the error condition. If the problem persists, contact your service provider.

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

1003

1003 - Backup process in CPU cpu-number terminated abnormally, comp-code error-code, [ stopper stopper-id, ] [ term-ssid term-ssid, ] term-info term-info, [ term-text term-text ]

`cpu-number`	the number of the CPU on the local system in which the backup domain coordinator process was terminated.
`error-code`	the completion code associated with the backup process termination. A completion code of -4 indicates that only the backup process, not both members of the process pair, terminated.
`stopper-id`	the process handle of the process that initiated the termination. This field is included only if the process was stopped externally.
`term-ssid`	the SPI subsystem identifier associated with the process-termination operation. This field is omitted if no subsystem identifier was associated with the termination.
`term-info`	the termination information code returned from the process-termination operation. If the value of this token is 0 (zero), the field is null and is omitted from the message. If the backup process was stopped externally (indicated by completion code 6), this field contains the creator user identifier of the external process that stopped the backup process.
term-text	the termination text associated with the process-termination operation. This field is omitted if no termination text was associated with the termination.

Cause The backup domain coordinator process terminated unexpectedly. This is a warning message.

Effect The primary domain coordinator process creates a new backup process.

Recovery If the problem persists, contact your service provider.

1004

1004 - Core process creation in CPU cpu-number failed, name process-name, error errnum, detail error-detail, [ file file-name ]

`cpu-number`	is the number of the CPU in which the process could not be started.
`process-name`	is the name of the process that was not created.
`errnum`	is the process-creation error code returned by the PROCESS_LAUNCH_() procedure.
`error-detail`	the process-creation error detail code returned by the PROCESS_LAUNCH_() operation. If the value of this field is 0 (zero), the field is omitted from the message.
`file-name`	the Guardian name of a program file, library file, swap file, home terminal, or process name associated with the major error code returned by the PROCESS_LAUNCH_() operation. This variable is omitted if no file is associated with the major error code.

Cause Either the domain coordinator process cannot create an ACS subsystem process in the specified CPU on the local system because the PROCESS_LAUNCH_() operation failed or the ACS subsystem process was created but the PROCESS_LAUNCH_() operation returned a warning.

Effect No ACS subsystem processes are started in the specified CPU. If the PROCESS_LAUNCH_() operation returned an error indicating a programming error in the domain coordinator process, the event is fatal; the primary domain coordinator process terminates abnormally and produces a SaveAbend file.

Recovery Correct the condition that caused process creation to fail then use the CONTROL command to restart the ACS subsystem processes in the CPU. If the event is fatal or if the problem persists, contact your service provider.

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.

1005

1005 - Core process in CPU cpu-number terminated abnormally, name process-name, comp-code comp-code, [ stopper stopper-id, ] [ term-ssid term-ssid, ] term-info term-info, [ term-text term-text ]

`cpu-number`	the number of the CPU in which the process terminated.
`process-name`	the name of the terminated process.
`comp-code`	the completion code associated with the process-termination operation.
`stopper-id`	the process handle of the process that caused the termination. This variable is included only if the process was stopped externally.
`term-ssid`	the subsystem identifier associated with the process termination. If no subsystem was associated with the process termination, this variable is omitted.
`term-info`	the termination information code associated with the process termination. If the value of this field is 0 (zero), the field is omitted from the message. If the core process was stopped externally (indicated by a completion code of 6), this field contains the creator user identifier of the external process that initiated the termination.
term-text	the termination text associated with the process termination. If no termination text was associated with the process termination, this variable is omitted.

Cause An ACS subsystem process terminated abnormally. This is an error message.

Effect The ACS subsystem process is not available on the CPU of the terminated process. Other ACS subsystem processes continue to run on the CPU.

Recovery Use the CONTROL command to restart all ACS subsystem processes on the CPU. If the problem persists, contact your service provider.

1006

1006 - Guardian file operation procedure() failed, [ file file-name, ] error errnum

`procedure`	the name of the Guardian file-system procedure that reported the failure.
`file-name`	the name of the Guardian file, device, or process that was being accessed by the failed operation. This variable is omitted for Guardian procedures that do not operate on files but nevertheless report failures using file-system error codes.
`errnum`	a file-system error code.

Cause An ACS subsystem process invoked a Guardian file-system procedure on an open or named file and the operation failed unexpectedly. This can be a warning, error, or fatal message.

Effect The ACS operation associated with the file-system operation is aborted.

Recovery Correct the condition that caused the file error and try the operation again.

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.

1007

1007 - OSS operation procedure() failed, pathname path-name, error oss-errno

`procedure`	the name of the OSS procedure that reported the failure.
`path-name`	the path name of the OSS file or directory that was being accessed by the failed operation. This variable is omitted for OSS procedures that do not operate on files or directories.
`oss-errno`	the file OSS error number.

Cause An ACS subsystem process invoked an OSS procedure and the operation failed unexpectedly. This can be a warning, error, or fatal message.

Effect The operation associated with the OSS operation is aborted.

Recovery Correct the condition that caused the OSS error and try the operation again.

1008

1008 - Process operation procedure() failed, process process-name, error errnum, detail error-detail

`procedure`	the name of the Guardian file-system procedure that reported the failure.
`process-name`	the name of the process that failed.
`errnum`	a process-information error code returned by the failed operation.
`error-detail`	process-information error-detail code returned by the failed operation.

Cause An ACS subsystem process invoked a Guardian process-information procedure and the operation failed unexpectedly. This is an error message.

Effect The operation associated with the process-management operation is aborted.

Recovery Correct the condition that caused the error and try the operation again.

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.

1009

1009 - Pathsend operation procedure() failed, Pathway system env-name, [ server erver-name,] error errnum, detail error-detail

`procedure`	the name of the Pathsend or link-management procedure that reported the failure.
`env-name`	the name of the environment supplied to the operation.
`server-name`	the name of the PATHMON process and server class (separated by a period) supplied to the operation. This variable is omitted for link-management procedures that do not operate on server classes.
`errnum`	the Pathsend error code returned by the failed operation.
`error-detail`	the file-system error code returned by the failed operation.

Cause An ACS subsystem process invoked an internal Pathsend or link management operation and the operation failed unexpectedly. This event message is generated only by ACS subsystem processes. It is not generated for application Pathsend requesters that encounter failures when they invoke Pathsend API procedures. This is an error message.

Effect The ACS subsystem operation associated with the Pathsend operation is aborted.

Recovery Correct the condition that caused the error and try the operation again.

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.

1010

1010 - Memory segment operation procedure() failed, segment segment-id, error errnum, detail error-detail

`procedure`	the name of the Guardian memory-segment management procedure that reported the failure.
`segment-id`	the segment- identifier of the memory segment being accessed.
`errnum`	the memory-management error code returned by the failed operation.
`error-detail`	the memory-management error detail code returned by the failed operation.

Cause An ACS subsystem process invoked a Guardian memory-segment management procedure and the operation failed unexpectedly. This is a fatal message.

Effect The process that invoked the failed operation terminates abnormally and produces a SaveAbend file.

Recovery If the failure was due to a file-system error or system-resource limit, correct the condition and use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the failure occurred.

If this is an internal error; contact your service provider.

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.

1011

1011 - Corruption detected in shared memory segment segment-id

segment-id

the identifier of the memory segment in which the corruption was detected.

Cause An ACS subsystem process detected corruption in the ACS subsystem shared-memory segment in its CPU. This is a fatal message.

Effect The process that detected the shared-memory segment corruption terminates abnormally and produces a SaveAbend file.

Recovery Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the corruption was detected.

1012

1012 - Memory semaphore operation procedure() failed, segment segment-id, error errnum

`procedure`	the name of the Guardian binary semaphore procedure that reported the failure.
`segment-id`	the identifier of the memory segment protected by the semaphore that was being accessed by the failed operation.
`errnum`	the Guardian or OSS error code returned by the failed operation.

Cause An ACS subsystem process invoked a Guardian semaphore-system procedure and the operation failed unexpectedly. This is a fatal message.

Effect The process that invoked the failed operation terminates abnormally and produces a SaveAbend file.

Recovery This is an internal error; contact your service provider.

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.

1014

1014 - Process failed holding memory segment segment-id semaphore

segment-id

the identifier of the memory segment protected by the semaphore that was abandoned.

Cause A process terminated while holding the lock on one of the ACS subsystem shared memory semaphores. This is a fatal message.

Effect The process that detected that the semaphore was abandoned terminates abnormally. The shared memory may be corrupt.

Recovery Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the semaphore was abandoned.

1015

1015 - Memory pool operation procedure() failed, segment segment-id, error errnum

`procedure`	the name of the Guardian memory -pool management procedure that reported the failure.
`segment-id`	the identifier of the memory segment containing the pool that was being accessed by the failed operation.
`errnum`	the error code returned by the failed operation.

Cause An ACS subsystem process invoked a Guardian memory-pool management procedure and the operation failed unexpectedly. This is a fatal message.

Effect The process that invoked the failed operation terminates abnormally and produces a SaveAbend file.

Recovery This is an internal error; contact your service provider.

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.

1016

1016 - Insufficient free space in memory segment segment-id pool

segment-id

the identifier of the memory segment containing the pool from which space was to be allocated.

Cause An ACS subsystem process could not allocate the space it needed in the ACS shared-memory segment in its CPU. This is a fatal message.

Effect Depending upon why the process needed the memory allocation, the operation it was performing may have failed or the ACS subsystem processes in the CPU may need to be restarted.

Recovery Use the CONTROL ACS command to restart the ACS subsystem processes in the CPU where the problem occurred.

1017

1017 - Unauthorized OPEN attempted by process process-id, access-user access-id, creator-user creator-id, process-name process-name, open-file file-name

`process-id`	the process handle of the process that sent the unauthorized OPEN request.
`access-id`	the process-access user identifier of the unauthorized requester process.
`creator-id`	the process-creator user identifier of the unauthorized requester process.
`process-name`	the named process descriptor of the unauthorized requester process.
`file-name`	the ACS subsystem process file name that the unauthorized process supplied to the OPEN or FILE_OPEN_ operation.

Cause An unauthorized requester process attempted to open an ACS subsystem process. This is a warning message.

Effect The attempt fails. A reply containing an FESECVIOL (48) system error is returned to the process.

Recovery Informational message only. This event indicates a possible attempt to breach the security of the ACS subsystem.

1018

1018 - Invalid request message received from process process-id

process-id

the process handle of the requester process that sent the invalid request message.

Cause An ACS subsystem process received an invalid request message. This is a warning message.

Effect The invalid request message is ignored. A reply containing an FEINVALOP (2) error is returned to the requester process.

Recovery Correct the requester program.

1019

1019 - Incompatible request version received from process process-id

process-id

the process handle of the requester process that sent the request.

Cause An ACS subsystem process received an incompatible version of a request message. This is a warning message.

Effect The request message is ignored. A reply containing an FEINVALOP (2) error is returned to the requester process.

Recovery This event indicates that incompatible versions of ACS components are installed.

1020

1020 - Invalid reply message received from process process-id

process-id

the process handle of the server process that sent the invalid reply message.

Cause An ACS subsystem process received an invalid reply message or a reply message that has an incompatible version. This can be an error or fatal message.

Effect The reply message is discarded. The operation associated with the request is aborted.

Recovery Contact your service provider.

1021

1021 - Protocol error in communication with process process-id

process-id

the process handle of the process that caused the protocol error.

Cause An ACS subsystem process detected a protocol (operation order) error by another system process. This is an error message.

Effect The operation in which the protocol error occurred is aborted.

Recovery Contact your service provider.

1022

1022 - PATHMON process-name I/O operation timed out

process-name

the name of the PATHMON process.

Cause An I/O operation from an ACS subsystem process to a PATHMON process timed out. ACS subsystem processes use a timeout value of 5 minutes for an I/O to a PATHMON process. This is a warning message.

Effect If the I/O operation was initiated in response to a send operation, the send operation fails with Pathsend error FESCPATHMONCONNECT and file-system error FETIMEDOUT.

The ACS subsystem attempts to close communication to this PATHMON process. New send requests fail with Pathsend error FESCPATHMONSHUTDOWN and file-system error FEOK.

When all links to the PATHMON process are closed from the requester side, the ACS subsystem closes communication to this PATHMON process then opens a new communication channel for future send requests.

Recovery Close all the links to this PATHMON process from the requester side. After closing all the links, retry send operations. If the problem persists, try to find out why the PATHMON process continues to time out.

1023

1023 - TSMP protocol violation by PATHMON process-name

process-name

the name of the PATHMON process.

Cause The PATHMON process communication with the ACS subsystem does not follow the TSMP protocol. This can be a warning or error message.

Effect The send operation fails with Pathsend error FESCPATHMONMESSAGE and file-system error FEOK.

Recovery Retry the send operation. If the problem persists, check the PATHMON process. You may need to shutdown and restart your Pathway application.

1024

1024 - PATHMON process-name I/O operation failed, error errnum

`process-name`	the name of the PATHMON process.
`errnum`	the file-system error code returned by the failed operation.

Cause An I/O operation from the ACS subsystem to a PATHMON process failed unexpectedly. This is a warning message.

Effect If the I/O operation was made in response to a send operation, the send operation fails with Pathsend error FESCPATHMONCONNECT. The file-system error code provides detailed information on the error.

The ACS subsystem attempts to close communication to this PATHMON process. New send requests fail with Pathsend error FESCPATHMONSHUTDOWN and file-system error FEOK.

Recovery Close all the links to this PATHMON process from requester side.

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.

1025

1025 - PATHMON process-name OPEN operation failed, error errnum

`process-name`	the name of the PATHMON process.
`errnum`	the file-system error code returned by the failed operation.

Cause An attempt to open a PATHMON process failed. This is a warning message.

Effect The send operation fails with Pathsend error FESCPATHMONCONNECT.

Recovery Check the error code for detailed information about the error. Retry the send operation. If the problem persists, contact your service provider.

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.

1026

1026 - No OPEN received from PATHMON process-name

process-name

is the name of the PATHMON process.

Cause A PATHMON process was not able to open an ACS subsystem process. This is a warning message.

Effect The send operation fails with Pathsend error FESCPATHMONMESSAGE and file-system error FEOK.

Recovery Try the send operation again. If the problem persists, check the PATHMON process. You may need to shutdown and restart your Pathway application.

1027

1027 - PATHMON process-name was externally shut down

process-name

the name of the PATHMON process.

Cause A PATHMON process pair was shut down in response to a TS/MP SHUTDOWN command. This is a warning message.

Effect Depending on the availability of the links with the ACS subsystem processes, some of the send operations may succeed using the existing links while others may fail with Pathsend error FESCPATHMONSHUTDOWN and file-system error FEOK.

Recovery No recovery action is required.

1028

1028 - Invalid message received from PATHMON process-name

process-name

the name of the PATHMON process.

Cause An ACS subsystem process received an invalid message from a PATHMON process. This is a warning message.

Effect If the MAT message was sent in response to an operational command from PATHCOM or from SPI requesters, the command fails. PATHMON logs an EMS event.

Recovery No recovery action is required.

1029

1029 - Core processes started in CPU cpu-number

cpu-number

the number of the CPU in which the processes were started.

Cause The ACS subsystem processes in the specified CPU on the local system were started in response to a START command or were restarted in response to a CONTROL command. This is a status message.

Effect None.

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

1030

1030 - Core processes stopped in CPU cpu-number

cpu-number

the number of the CPU in which the processes were stopped.

Cause One or more ACS subsystem processes in a CPU failed or were stopped in response to a STOP command. If due to a failure, the physical CPU may have failed. This is an error message.

Effect Pathsend operations initiated in the CPU fail with FESCLINKMONCONNECT errors until the ACS subsystem processes are restarted.

Recovery Use the CONTROL ACS command to restart the ACS subsystem processes.

1031

1031 - Event log file operation procedure() failed, file file-name, error errnum

`procedure`	the name of the Guardian file-system procedure that reported the failure.
`file-name`	the name of the event log file that was accessed by the failed operation.
`errnum`	a file-system error returned by the failed operation.

Cause An ACS subsystem process encountered an error while writing an event message to the LOG1 or LOG2 event log file. This is an error message.

Effect The event log file is closed and event messages are written to the other event log file.

If neither event log file is available or if a second event log file was not configured, event messages are written to the system's primary event collector ($0) in EMS format.

If an error occurs while writing to $0, it is closed and the event message is discarded. The AC subsystem attempts to reopen $0 when another event occurs.

Recovery Correct the condition that caused the error, then stop and restart the ACS subsystem to reopen the event log file(s).

1032

1032 - LOG1 opened on file file-name

file-name

the name of the LOG1 file.

Cause The LOG1 event log file was opened successfully. This is a status message.

Effect None.

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

1033

1033 - LOG1 closed on file file-name

file-name

the name of the LOG1 file.

Cause The LOG1 event log file was closed either in response to an operator command or because an error occurred while writing to the log file. If this event was due to an error on the log file, a previously issued event message described the error. This is a status message.

Effect None.

Recovery If the event was due to an error on the log file, check the previously issued event message for a detailed description of the problem. If the event was issued in response to an operator command, this is an informational message only; no corrective action is needed.

1034

1034 - LOG2 opened on file file-name

file-name

the name of the LOG2 file.

Cause The LOG2 event log file was opened successfully. This is a status message.

Effect None.

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

1035

1035 - LOG2 closed on file file-name

file-name

the name of the LOG2 file.

Cause The LOG2 event log file was closed either in response to an operator command or because an error occurred while writing to the log file. If this event was due to an error on the log file, a previously issued event message described the error. This is a status message.

Effect None.

1036

1036 - PATHMON process process-name is not running

process-name

the PATHMON process name supplied to the Pathsend operation.

Cause The PATHMON process name supplied to a Pathsend operation is not currently running. This is a warning message.

Effect The Pathsend operation fails with an FESCPATHMONCONNECT error and a file-system FENOSUCHDEV error detail.

Recovery Correct the Pathsend requester program or start the named Pathway system.

1037

1037 - Server name pathmon-name.serverclass-name is not defined

`pathmon-name`	the name of the PATHMON process specified in the Pathsend operation.
`serverclass-name`	the name of the server class supplied to the Pathsend operation.

Cause The server class name supplied to a Pathsend operation is not defined in the PATHMON process specified with it. This is a warning message.

Effect The Pathsend operation fails.

Recovery Correct the Pathsend requester program.

1038

1038 - Server pathmon-name.serverclass-name file operation procedure() failed, [process process-id], file file-name, error errnum

`pathmon-name`	the name of the PATHMON process that manages the server class.
`serverclass-name`	the name of the server class that contains the server process.
`procedure`	the name of the Guardian file-system procedure that reported the failure.
`process-id`	the identifier of the server process accessed by the failed operation.
`file-name`	the file name of the server process used by the failed operation.
`errnum`	the file-system error code returned by the failed operation.

Cause A Guardian file-system operation on a server process failed unexpectedly or completed with an unexpected error code. This can be a warning or an error message.

Effect The Pathsend operation associated with the file-system operation fails with an FESCSERVERLINKCONNECT Pathsend error. The link to the server process is released.

Recovery Correct condition that caused the operation to fail. Retry the Pathsend operation.

1042

Unauthorized attempt to invoke server pathmon-name.serverclass-name, access-user access-id

`pathmon-name`	the name of the PATHMON process specified in the Pathsend operation.
`serverclass-name`	the name of the server class specified in the Pathsend operation.
`access-id`	the process-access user identifier of the unauthorized requester process.

Cause A Pathsend requester process attempted to perform a Pathsend operation on a server class that the process is not authorized to communicate with. Authority to communicate with a Pathway server class is determined by the OWNER and SECURITY configuration attributes of the server class.

Effect The Pathsend operation fails with an FESERVERLINKCONNECT Pathsend error and FESECVIOL file-system error detail.

Recovery None. This event message indicates a possible attempt to breach the security of a Pathway application.

1062

1062 - (process-name): No backup CPU available

process-name

the name of the domain coordinator process followed by its CPU and PIN enclosed in parentheses.

Cause The backup CPU specified in the domain-coordinator process startup string is not available or no backup CPU was specified and no other CPUs are available on the system. This is a warning message.

Effect The domain coordinator process runs as a single process.

Recovery If message 1066 was generated, use the CONTROL command to restart the ACS subsystem processes in the CPU. If that does not correct the problem, reload the failed CPU(s).

1063

1063 - Invalid backup CPU specified: cpu-number

cpu-number

the invalid CPU number.

Cause An invalid CPU number was specified in the domain coordinator process startup string. This is a fatal message.

Effect The primary domain coordinator process terminates immediately.

Recovery Start the domain coordinator process. Specify a valid CPU number for the backup process or specify the value -1 to allow the domain coordinator process to select a backup CPU.

1064

1064 - ACS reserved process name process-name is in use.

process-name

the reserved process name that is currently being used.

Cause One of the process names reserved for ACS subsystem processes is currently in use by another process. This is an error message.

Effect If the domain coordinator process detects the problem during process startup, it terminates abnormally. If it detects the condition during the START ACS command processing, the START operation fails and no ACS subsystem processes are started.

Recovery Stop the process that uses the ACS reserved process name.

1065

1065 - Corrupt or invalid BCINI file: file-name

file-name

the Guardian name of the domain-coordinator process-initialization file (BCINI).

Cause The ACS subsystem domain-coordinator process-initialization file (BCINI) is invalid or contains invalid data. This is a warning message.

Effect The domain coordinator cannot save the current ACS subsystem configuration to the BCINI file.

Recovery Use the STOP command to stop the ACS subsystem, then purge the corrupt file and start the subsystem again.

1066

1066 - Invalid backup CPU cpu-number - CPU needs to be enabled

cpu-number

the number of the CPU.

Cause A backup domain coordinator process terminated unexpectedly in the indicated CPU and the ACS subsystem processes in that CPU have not been restarted. This is a warning message.

Effect The domain coordinator runs as a single process if the process was configured for a specific backup CPU when it was added. If the STARTUPMSG attribute specified a value of -1, the domain coordinator attempts to start a backup process in the next available CPU.

Recovery Use the CONTROL ACS command to restart the ACS subsystem processes in the specified CPU.

1067

1067 - Invalid ACS product path actual-subvol - expecting system-subvol

`actual-subvol`	the name of the Guardian subvolume where the domain coordinator program resides.
`system-subvol`	the name of the Guardian subvolume that contains the OSIMAGE file used to load the system.

Cause The domain coordinator program does not reside in the system subvolume used to load the system ($SYSTEM.SYSnn). This is a fatal message.

Effect The domain coordinator process terminates abnormally.

Recovery Contact HP support to install the ACS program files in $SYSTEM.SYSnn.

1068

1068 - Hometerm file-name is no longer valid for process process-name

`file-name`	the name of the home terminal.
`process-name`	the name of the process that could not be created.

Cause The home terminal is no longer valid and cannot be used to create a backup domain coordinator process or other ACS subsystem process. This is an error message.

Effect If the backup domain coordinator process fails, the primary domain coordinator process continues to run without a backup process. If one of the other ACS subsystem processes fails, the CPU where it was running is disabled.

Recovery Restart the home terminal if possible. Otherwise, stop and restart the ACS subsystem with a new home terminal.

1069

Process pair for process-name is switching over

process-name

the name of the process pair.

Cause The primary process can no longer continue. This is an informational message.

Effect Primary process terminates and the backup process takes over.

Recovery Informational message only; no corrective action is needed.

1070

Process pair for process-name cannot switch over

process-name

the name of the process pair.

Cause The process pair cannot switch because no backup process is running. The backup-process CPU may be down or the ACS subsystem processes have not been restarted in that CPU.

Effect The process pair cannot switch; ACS subsystem processes may not be available to handle requests.

Recovery If the backup-process CPU is down, reload it. If the backup-process CPU is up, use the CONTROL command to restart the ACS subsystem processes.

1071

1071 - Primary process in CPU cpu-number terminated abnormally, comp-code comp-code, stopper stopper-id, term-ssid term-ssid, term-info term-info, term-text term-text

`cpu-number`	the number of the CPU on the local system in which the primary domain coordinator process was running.
`comp-code`	the completion code associated with the process-termination operation. A completion code of -4 indicates that only the primary process, not both members of the process pair, terminated.
`stopper-id`	the process handle of the process that stopped the primary process. This variable is included only if the process was stopped externally.
`term-ssid`	the subsystem identifier associated with the process termination. If no subsystem identifier was associated with the process termination, this variable is omitted.
`term-info`	the termination information code associated with the process termination. If the value of this field is 0 (zero), the field is omitted from the message. If the core process was stopped externally (indicated by a completion code of 6), this field contains the creator user identifier of the external process that initiated the termination.
`term-text`	the termination text associated with the process-termination operation. This field is omitted if no termination text was associated with the termination.

Cause The primary domain coordinator process terminated abnormally. This is a warning message.

Effect The backup domain coordinator process becomes the primary domain coordinator process and creates a new backup process.

Recovery If the problem persists, contact your service provider.

1072

1072 - ACSCTL Parsing Status – error-info, file file-name, [line line-number]

`error-info`	the description of the error in text format.
`file-name`	the fully qualified file name of the ACSCTL file.
`line-number`	the line number in the ACSCTL file where the error is found. This field is not displayed for a status message.

Cause The ACS subsystem provides the status information of the ACSCTL file parsing.

Effect The ACSCTL file parsing error or status is logged.

Recovery Correct the condition that caused the error and try the operation again.

1073

1073 - ACSCTL File Status – error-info, file file-name, errno errnum

`error-info`	the description of the error in text format.
`file-name`	the fully qualified file name of the ACSCTL file.
`errnum`	the error code returned by the system function fopen().

Cause The ACS subsystem provides the status information of the ACSCTL file.

Effect The ACSCTL file error or status is logged.

Recovery Correct the condition that caused the error and try the operation again.

1074

1074 - PATHMON pathmon-name was internally shut down, code error-code

`Pathmon-name`	the name of the PATHMON process being shutdown.
`Error-code`	the reason for internal shutdown. This is for internal use.

Cause The ACS subsystem is closing the connection to the Pathmon process because:

An I/O to the PATHMON process timed out.
An I/O to the PATHMON process failed.
ACS subsystem received unexpected message from PATHMON process.
Local or remote PATHMON process processor is down.
Node on which PATHMON process is running is unavailable.
PATHMON process is unilaterally stopped or abended.

Effect If the I/O operation was initiated in response to a send operation, the send operation fails with Pathsend error FESCPATHMONCONNECT and file-system error encountered during the I/O. The ACS subsystem closes communication to this PATHMON process, and then opens a new communication channel for future send requests.

Recovery Informational message only; no corrective action is required.

1076

GET—LINK acquiring number of links links on CPU cpu-number to SERVER serverclass-name, DOMAIN|PATHMON pathmon-name | domain-name Link-expiry-time expiry-time seconds

`number of links`	total number of links specified in the GET-LINK command.
`cpu-number`	CPU number specified in the GET-LINK command.
`serverclass-name`	the name of the serverclass specified in the GET-LINK command.
`pathmon-name`	the name of the PATHMON process for which GET-LINK command is issued.
`domain-name`	the name of the domain specified for which GET-LINK command is issued.
`expiry-time`	the link-expiry-time interval specified in the GET-LINK command in seconds.

Cause Displays the input of GET-LINK command. This is a status message.

Effect None

Recovery Informational message only; no corrective action is required.

1077

GET—LINK acquired number of links (S — number of static links : D — number of dynamic links) links on CPU cpu-number to SERVER serverclass-name, PATHMON|DOMAIN pathmon-name | domain-name.

`number of links`	total number of links acquired by the GET-LINK command on a specified CPU.
`number of static links`	number of static links acquired.
`number of dynamic links`	number of dynamic links acquired.
`cpu-number`	CPU number.
`serverclass-name`	the name of the serverclass for which the links are acquired.
`pathmon-name`	the name of the PATHMON process for which links are acquired.
`domain-name`	the name of the domain specified for which links are acquired.

Cause Displays the execution summary of GET-LINK command. This is a status message.

Effect None

Recovery Informational message only; no corrective action is required.

1078

GET-LINK failed to acquire link with Pathsend error error-code, file system error error-code for SERVER serverclass-name, PATHMON|DOMAIN pathmon-name | domain-name.

`error-code`	a filesystem or Pathsend error code.
`serverclass-name`	the name of the serverclass for which the link acquisition request failed.
`pathmon-name`	the name of the PATHMON process for which the link acquisition request failed.
`domain-name`	the name of the domain for which the link acquisition request failed.

Cause The link acquisition request failed unexpectedly for GET-LINK command. This event is only generated by GET-LINK command. It is not generated for application Pathsend requestors that encounter failures when they invoke Pathsend API procedures.

Effect The link acquisition request failed.

Recovery For information about Pathsend and file system error, see TS/MP 2.5 Pathsend and Server Programming Manual. Correct the condition that caused the error and reissue the command.

Chapter 2 APPCLSTR (Application Cluster Services) Messages

ACS Subsystem Identifiers