Operator Messages Manual

Chapter 76 OSSTTY Messages

The messages in this chapter are generated by the OSSTTY subsystem. The subsystem ID displayed by these messages includes OSSTTY as the subsystem 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.

1

OSSTTY: Primary started on cpu processor-number1, with backup on cpu processor-number2.

`processor-number1`	indicates the number of the primary processor for the process.
`processor-number2`	indicates the number of the backup processor for the process.

Cause The user started an OSSTTY process pair.

Effect The indicated process is running.

Recovery Informational message only; no corrective action is needed.

2

OSSTTY: Process started on cpu processor-number1, without backup

processor-number1

indicates the number of the primary processor for the process.

Cause The user started an OSSTTY process or the OSH command was used with the -osstty option.

Effect The indicated process is running.

Recovery Informational message only; no corrective action is needed.

3

OSSTTY: Normal Termination of process osstty-name.

osstty-name

identifies the process issuing the message.

Cause The indicated process stopped because the number of seconds allowed for it to remain idle had expired.

Effect To use the process, it must be restarted.

Recovery Informational message only; no corrective action is needed.

4

OSSTTY: OUT EDIT file filename is full, wrapping.

filename

is the Guardian filename of the EDIT file used as the OUT file.

Cause The OUT file specified in the redirection is an EDIT file and is full. If the file was created by OSSTTY, the default line number increment is .001 and such a file cannot have more than 99,999.999 lines.

Effect Data wraps around and is written from the beginning of the file, overwriting existing information.

Recovery Informational message only; no corrective action is needed.

5

OSSTTY: Trace of process osstty-name started. Logging to filename.

`osstty-name`	identifies the process being traced.
`filename`	is the Guardian filename of the EDIT file used as the trace logging file.

Cause A trace of the indicated instance of OSSTTY was initiated.

Effect The level of data logged depends on the level specified when the instance of OSSTTY was started.

Recovery Informational message only; no corrective action is needed.

6

OSSTTY: Trace of process osstty-name stopped.

osstty-name

identifies the process that was being traced.

Cause A trace of the indicated instance of OSSTTY terminated.

Effect The trace file (TLOGnnnn) is closed.

Recovery Informational message only; no corrective action is needed.

7

OSSTTY: Trace file filename1 is full. Logging to filename2.

`filename1`	is the Guardian filename of the EDIT file being closed.
`filename2`	is the Guardian filename of the EDIT file now being used as the trace logging file.

Cause A trace of the indicated instance of OSSTTY used all available space in the indicated log file and has opened a new log file to continue.

Effect The trace log file filename1 is closed. Tracing continues using a new trace log file, filename2.

Recovery Informational message only; no corrective action is needed.

46

The terminal server process process-name replied with value for select support as value1 for the terminal file file-name which is already opened in the cpu cpu-num with select support as value2

`process-name`	is the name of the terminal server process that has replied with a select support flag value in the open reply to the terminal file.
`value1`	is a Boolean type, either True (T) or False (F), depending on the terminal server process response to open of the terminal file.
`file-name`	is a Terminal file name.
`cpu-num`	is the processor number where the terminal file is opened.
`value2`	is a Boolean type, either True (T) or False (F), depending on the terminal server process response to open of the terminal file.

Cause Terminal server process replied with different select support values between different opens of the same terminal file in the same processor.

Effect The OSS application program interface (API) open() fails with error 566.

Recovery Users must close all the terminal sessions where error 566 occurs.

201

OSSTTY: Takeover by backup, reason reason.

reason

is text that describes the reason that the backup copy of the process has taken over its open terminal sessions.

Cause The primary process was stopped by an operator action, terminated abnormally, or stopped because its processor stopped.

Effect Loss or duplication of data can occur within some terminal sessions. Noninteractive users of the subsystem should be encouraged to check data from sessions open when the takeover occurred.

Recovery Informational message only; no corrective action is needed. The backup copy of the process maintains the process’s open terminal sessions.

202

OSSTTY: Checkpoint failed with error error-number.

error-number

is the Guardian file-system error returned by the underlying Guardian procedure call.

Cause The backup process cannot perform a checkpoint. See the Guardian Procedure Errors and Messages Manual for more information about error-number, or use the HP Tandem Advanced Control Language (TACL) ERROR command for an online explanation.

Effect The backup process is no longer operational.

Recovery ïStop and restart OSSTTY. If the problem persists, contact your service provider and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the generated message or messages
Supporting documentation such as Event Management Service (EMS) logs, trace files for both the primary and backup process, 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.

203

OSSTTY: Unable to allocate size-in-bytes bytes

size-in-bytes

is the number of bytes of memory that the OSSTTY process tried to allocate.

Cause The internal allocation of memory buffers failed.

Effect Data transfer might be slow or might fail because memory cannot be allocated for data structures.

Recovery Do one of the following:

Limit the data traffic by using application-specific mechanisms.
Reduce the maximum number of applications that can redirect their data through OSSTTY.
Restart the process in a processor with more available memory, then restart the applications using the process.

If the problem recurs, try increasing the heap space allocated for the OSSTTY object file to a larger value using the NLD program.

204

OSSTTY: Internal resource resource-type management error.

resource-type

identifies the entity that has caused the problem. Possible values include memory, data structures, program logic, and so forth.

Cause The OSSTTY process found an inconsistency in its internal program logic or data structures.

Effect The OSSTTY process terminates abnormally, which might lead to a loss or duplication of data being processed for open terminal sessions.

Recovery If a backup process exists, it takes over processing of open terminal sessions. Otherwise, start a new OSSTTY process.

Noninteractive users of the subsystem should be encouraged to check data from sessions that were open when the error occurred.

205

OSSTTY: Maximum number of users limit has reached, currently number-of-users users.

number-of-users

is the number of processes (open terminal sessions) currently directing their data through OSSTTY.

Cause The number of opens of the OSSTTY process has reached the design limit for OSSTTY.

Effect All new opens are rejected; new requests from existing opens are serviced.

Recovery Do one or both of the following:

Start a new OSSTTY process and direct newly launched applications to use the new copy of the OSSTTY process.
Reduce the number of applications redirecting their standard files data through the current OSSTTY process.

206

OSSTTY: OUT EDIT file file-name is full.

file-name

is the Guardian filename of the EDIT file used as the OUT file.

Cause The OUT file specified in the redirection is an EDIT file, is full, and OSSTTY was started without using the -wrap command option. If the file was created by OSSTTY, the default line number increment is .001 and such a file cannot have more than 99,999.999 lines.

Effect The OUT file is no longer accessible to redirect data to. OSSTTY’s IN and TERM file redirections remain accessible.

Recovery Do one of the following:

Purge the existing file or rename it.
Restart OSSTTY using the -wrap command option.

207

OSSTTY: State of Window window-name, redirecting to proc/filename changed from old-state to new-state Reason reason

window-name

is the name of the OSSTTY redirection window that is the subject of this message. Valid values are:

#stdout	indicates that the window functions as the standard output file
#stdin	indicates that the window functions as the standard input file
#stderr	indicates that the window functions as the standard error file

proc/filename

is the name of the Guardian process or EDIT file that was specified as the target for the win-name redirection in the run command that started the OSSTTY session.

old-state

is the state of the window before the change took place.

new-state

is the state of the window after the change took place.

reason

is the reason the state changed. The displayed information can indicate the change was the result of an error that occurred in the window interface, of a recovery operation, and so forth.

Cause An error caused a change in the accessibility of the redirectional targets. This message can have the following combinations of the three states for its old-state and new-state values:

STARTED - SUSPENDED
SUSPENDED - STOPPED
STOPPED - STARTED

For example, suppose the OUT file specified for OSSTTY is $VHS:

OSSTTY opens $VHS and writes the data coming from applications to $VHS. The state for the OSSTTY #stdout window is STARTED.
$VHS goes down, so the state changes to SUSPENDED and remains in that state until OSSTTY exhausts its allowed number of retries to send data to $VHS.
While the state for the OSSTTY #stdout window is SUSPENDED, OSSTTY’s #stdout window accepts new requests.
If $VHS remains inaccessible even after all retries have been done, the state for the OSSTTY #stdout window changes to STOPPED. No new requests are serviced and existing requests are returned with an error.

Effect The OSSTTY window might become unavailable.

Recovery If the window state is SUSPENDED, this is an informational message only; no corrective action is needed.

If the window state is STOPPED, look for other EMS events from about the same time that are related to OSSTTY and the processes specified in the IN, OUT, and TERM redirection to identify the problem.

208

OSSTTY: request-type request from groupID,userID rejected. Reason reason

`request-type`	is the type of process request involved; for example: OPEN, READ, WRITE, and so forth.
`groupID,userID`	is the user ID of the process making the request.
`reason`	is the reason for which the request was rejected.

Cause OSSTTY rejected the indicated request. The request could have been rejected for reasons that include:

The application does not have access permission.
The redirectional target is not available.
The request was not in the proper format.

Effect The application cannot gain access to the OSSTTY redirectional targets.

Recovery Check whether the OSSTTY -secure and -access options were used in the command that started the OSSTTY process. Correct and reenter the command based on the information provided in reason.

209

Communication error with terminal helper objectname file system error errno

`objectname`	is the process name of the OSS terminal helper server that was the target of the communication.
`errno`	is the Guardian file-system error returned by the underlying Guardian procedure call that encountered the communication problem. See the Guardian Procedure Errors and Messages Manual for more information about `errno`, or use the HP Tandem Advanced Control Language (TACL) ERROR command for an online explanation.

Cause OSSTTY detected an error when communicating with the OSS terminal helper server identified as objectname. If the error reported by errno is retryable, the most likely cause is either a system resource shortage on the processor used by either the terminal helper process or OSSTTY.

Effect Applications that perform OSS file system input or output with terminals might not function properly.

If the error reported by errno is retryable, the communication is retried indefinitely, with increasing delays of up to 60 seconds between attempts. The message is logged once per hour during periods when an input or output operation is being retried.

Recovery If the error reported by errno is retryable, stop other applications on the processors running OSSTTY and the OSS terminal helper server to free resources. If the situation does not improve, then the processors running OSSTTY and the OSS terminal helper server should be reloaded.