The Pathsend error codes are described in numeric order on these pages. Each description includes:

• The error number and corresponding error literal

• The cause of the error

• Typical file-system errors that can be encountered with the Pathsend error

• The effect of the error

• How to recover from the error

These errors can be returned to Pathsend requesters. They can also be returned to NonStop Tuxedo clients that invoke NonStop Tuxedo request and response services or conversational services. When Pathsend errors are returned to a NonStop Tuxedo client, the necessary recovery actions might differ from those listed here; for information about recovery from errors in the NonStop Tuxedo environment, refer to the NonStop TUXEDO System Messages Manual.

For examples of how errors are returned to a Pathsend program, refer to the example programs in“Examples” (page 129). The error literals that follow the error numbers— for example, 233 (FEScError)—are used in the example programs.

You can recover from some errors by retrying the Pathsend procedure call; the errors you should retry depend on the requirements of your application. The programming examples in“Examples” (page 129), illustrate retrying the call for certain errors. You can use those examples and the error descriptions in this section to decide how to program for retrying errors.

900

FEScInvalidServerClassName

Cause. The server-class name specified in a call to SERVERCLASS_SEND_ or

SERVERCLASS_DIALOG_BEGIN_ is not syntactically correct. This is a programming error. Typical file-system error: 2 (FEInvalOp)

Effect. The send initiation fails with an error.

Recovery. Correct the server-class name syntax. See the NonStop TS/MP System Management

Manual for a description of the correct syntax for server-class names.

901

FEScInvalidPathmonName

Cause. The PATHMON process name specified in a call to SERVERCLASS_SEND_ or

SERVERCLASS_DIALOG_BEGIN_ is not syntactically correct. This name must be a valid external process name. This is a programming error.

Typical file-system error: 2 (FEInvalOp) Effect. The send initiation fails with an error.

Recovery. Correct the PATHMON name syntax. Refer to Section 5,“Pathsend Procedure Call Reference” (page 75), for details about the correct syntax for PATHMON process names. 902

FEScPathmonConnect

Cause. An error has occurred in the requester’s communication with the PATHMON process. For example, an open operation has failed, an I/O error has occurred, or the PATHMON process has failed.

Typical file-system errors: 12, 14, 40, 48, 201, or one of the path errors between 240 and 255. Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server process.

Recovery. Recovery depends on the file-system error:

• Error 12 (FEInUse) indicates that the PATHMON process was unable to open the LINKMON process. Specific causes of this situation include (but are not limited to):

◦ The maximum number of LINKMON processes that the PATHMON process can communicate with has been exceeded. See the NonStop TS/MP System Management

Manual for information about setting the MAXLINKMONS parameter.

◦ The remote password on the system where the SERVERCLASS_SEND_ request originated was not set for the system where the server class was running. The PATHMON process receives a file-system error 48 but converts this error into a file-system error 12. To recover, ensure that all remote passwords are properly set, as described in the Expand Network

Management Guide.

• Error 14 (FENoSuchDev) indicates the PATHMON process does not exist. Start the PATHMON process or use an existing PATHMON process.

• Error 40 (FETimeout) indicates that a timeout error occurred, possibly because a server was in debug mode. See“Considerations for Debugging Pathway Servers” (page 69)in Section 4 for more information about timeout errors for servers in debug mode.

• Error 48 (FESecViol) indicates there was a security violation. See Section 3,“Writing Pathsend Requesters” (page 51), for information about network and server-class security.

• Error 201 (FEPathDown) or error 240 through 255 indicates that a path error occurred (for example, the PATHMON process failed). Restart the PATHMON process.

903

FEScPathmonMessage

Cause. The LINKMON process received an unrecognizable message from the PATHMON process while processing a SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ request. You might be using incompatible versions of the LINKMON and PATHMON processes, or this could be a LINKMON or PATHMON process internal error.

Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server process.

Recovery. This is a nonrecoverable error. 904

FEScServerLinkConnect

Cause. An error has occurred with the link to the server. For example, an open operation has failed or there is an I/O problem. This error could occur on a call to SERVERCLASS_SEND_,

SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_.

Typical file-system errors: 14, 40, 48, 201, or one of the path errors between 240 and 255. Effect. The call is completed with an error. The message might or might not have been sent to the server process, depending on the file-system error.

If the file-system error is a path error, any transaction associated with the call is aborted.

If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_, the dialog is ended on the server side.

Recovery. If this error is returned from SERVERCLASS_SEND_, recovery depends on the file-system error:

• Error 14 (FENoSuchDev) indicates that the server process does not exist. Retry the

SERVERCLASS_SEND_ to cause the LINKMON process to use a different link to the server process or to receive additional links from the PATHMON process. The success of the retry depends on why the server process stopped.

• Error 40 (FETimedout) indicates that the I/O to the server process timed out because it exceeded the configured SERVER TIMEOUT value for the server class.

• Error 48 (FESecViol) indicates there was a security violation. Section 3,“Writing Pathsend Requesters” (page 51), for information about network and server-class security.

• Error 201 (FEPathDown) or error 240 through 255 indicates that a path error occurred (for example, the processor where the server process was running has failed).

If this error is returned from SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_, use SERVERCLASS_DIALOG_END_ or SERVERCLASS_DIALOG_ABORT_ to terminate the requester’s portion of the dialog.

905

FEScNoServerLinkAvailable

Cause. The LINKMON process had no links to the server class and was unable to get a link from the PATHMON process to satisfy this request. For example, MAXLINKS links for each server class are already allocated to other LINKMON processes and TCPs. This is a PATHMON configuration problem.

Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server process.

Recovery. Increase the maximum number of servers in the server class (with the PATHCOM

MAXSERVERS parameter) or increase the number of links available to the server (with the PATHCOM MAXLINKS parameter). For details about the MAXSERVERS and MAXLINKS parameters, see the

NonStop TS/MP System Management Manual.

906

FEScNoSendEverCalled

Cause. The SERVERCLASS_SEND_INFO_ procedure was called before SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ was ever called by this program. This is a programming error. Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_INFO_ call is completed with return error 0, Pathsend error 906, and file-system error 0.

Recovery. Ensure that your application program does not call SERVERCLASS_SEND_INFO_ before it calls SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_.

NOTE: Error 907, FEScInvalidSegmentId, and error 908, FEScNoSegmentInUse, are not returned on D-series systems. Error 908 has been replaced by error 912, FEScParameterBoundsError. 909

FEScInvalidFlagsValue

Cause. The caller set bits in the flags parameter that are reserved and must be 0. This is a programming error.

Typical file-system error: 2 (FEInvalOp) Effect. The send initiation fails with an error.

Recovery. Set the reserved bits in the flags parameter to 0. 910

FEScMissingParameter

Cause. A required parameter was not supplied. This is a programming error. Typical file-system error: 29 (FEMissParam)

Effect. The send initiation fails with an error.

Recovery. Check the syntax of the procedure call and supply the required parameters. 911

FEScInvalidBufferLength

Cause. The buffer length in the request-len or maximum-reply-len parameter for a call to SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_ is invalid. This is a programming error.

Typical file-system error: 21 (FEBadCount) Effect. The send initiation fails with an error.

Recovery. Check the buffer lengths allowed for the request-len and maximum-reply-len parameters in the syntax description for the procedure call, and specify the correct buffer lengths. 912

FEScParameterBoundsError

Cause. The address specified by a reference parameter is out of bounds, or the caller supplied a reference parameter that is an extended address but does not have an extended segment in use. This is a programming error.

Effect. The send initiation fails with an error. Recovery. Correct the programming error. 913

FEScServerClassFrozen

Cause. The server class the process tried to send to is frozen. Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server class.

Recovery. Resend after the system manager or operator has thawed the server class. 914

FEScUnknownServerClass

Cause. The server class is not configured through the specified PATHMON process. The program has specified an incorrect server-class name or specified the wrong PATHMON process.

Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server class.

Recovery. Check the server-class name and the PATHMON process name. Or check if the server class has been configured yet (the PATHMON-controlled objects could be in the process of being cold started).

915

FEScPathmonShutDown

Cause. The send operation has been denied for one of these reasons:

• The PATHMON process for the server class is shutting down.

• A timeout occurred on an I/O operation to a server in debug mode. Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, or

SERVERCLASS_DIALOG_SEND_ call is completed with an error. The message is not sent to the server class.

Recovery. If the PATHMON process is shutting down, determine the reasons for the shutdown and perform appropriate recovery actions.

If a server process is in debug mode and a timeout error (file-system error 40) occurred:

• Use the PATHCOM STATUS PATHMON command to find the server classes that are in the LOCKED state.

• Identify the server program file for each locked server class.

Issue the TACL command STATUS *, PROG object-file-name to list all running processes.

• Stop these processes by using the TACL STOP command.

For more information about timeout errors for servers in debug mode, refer to“Considerations for Debugging Pathway Servers” (page 69)in Section 4.

916

FEScServerCreationFailure

Cause. The LINKMON process was unable to get a link to the server class due to a server creation failure. This is usually a server-class configuration problem, or a server might have a problem that causes it to fail.

Typical file-system error: 0 (FEOK)

Effect. The send initiation fails with an error.

Recovery. Verify that the server class has been configured correctly. If the problem is not in the configuration, correct the error in the server.

917

FEScServerClassTmfViolation

Cause. The transaction mode of the Pathsend program does not match that of the server class. The process has a current transaction ID at the time of the send, and the server class is configured with the TMF parameter set to OFF. This is a programming error or a server-class configuration error. Typical file-system error: 0 (FEOK)

Effect. The call is completed with an error. The message is not sent to the server class. Recovery. Correct your program or change the server-class configuration setting to TMF ON. 918

FEScSendOperationAborted

Cause. The send operation has been terminated at an indeterminate point. Typical file-system error: 40 (FETimedOut)

Effect. The send fails. A message might or might not have been sent to the server process, depending on when the send was aborted.

Recovery. The recovery action depends on which file-system error has occurred. With error 40 (FETimedOut), you might want to try a larger timeout value.

919

FEScInvalidTimeoutValue

Cause. The caller supplied an invalid timeout value in a call to SERVERCLASS_SEND_,

SERVERCLASS_DIALOG_BEGIN_, or SERVERCLASS_DIALOG_SEND_. This is a programming error.

Typical file-system error: 2 (FEInvalOp) Effect. The send initiation fails with an error.

Recovery. Specify a valid timeout value. See the procedure call syntax description for details about valid timeout values.

920

FEScPFSUseError

Cause. The caller’s process file segment (PFS) could not be accessed. Typical file-system error: 31 (FENoBufSpace)

Effect. The send initiation fails with an error.

Recovery. Code the process to stop itself if this error occurs. 921

FEScTooManyPathmons

Cause. A call to SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ specifies a PATHMON process not known to the LINKMON process, and the LINKMON process is already communicating with the maximum number of PATHMON processes allowed. The maximum number is 256. Typical file-system error: 0 (FEOK)

Effect. The call is completed with an error. The message is not sent to the server process.

Recovery. In some cases, you can recover from this error by retrying the call. Whether a retry will work depends on the design and operating environment of your application. If the PATHMON processes in your application are frequently created and stopped, retry the call. Otherwise, investigate the cause of the large number of PATHMON processes and eliminate some processes. For more information about LINKMON limits, refer to“LINKMON Limit Errors” (page 44)and also to the NonStop TS/MP System Management Manual.

922

FEScTooManyServerClasses

Cause. The LINKMON process already has links to the maximum number of server classes allowed for all PATHMON processes. The maximum number is 1024.

Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server process.

Recovery. In some cases, you can recover from this error by retrying the call. Whether a retry will work depends on the design and operating environment of your application.

For more information about LINKMON limits, refer to“LINKMON Limit Errors” (page 44)and also to the NonStop TS/MP System Management Manual.

923

FEScTooManyServerLinks

Cause. The LINKMON process already has the maximum number of concurrent links to server processes allowed for all PATHMON processes. The maximum number is 1750.

Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server process.

Recovery. In some cases, you can recover from this error by retrying the call. Whether a retry will work depends on the design and operating environment of your application.

For more information about LINKMON limits, refer to“LINKMON Limit Errors” (page 44)and also to theNonStop TS/MP System Management Manual.

924

FEScTooManySendRequests

Cause. The maximum number of concurrent server-class send operations allowed has been exceeded. The maximum number is 255 per requester and 512 for all requesters running in a processor. This error can occur on a call to SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, or

SERVERCLASS_DIALOG_SEND_. Typical file-system error: 0 (FEOK)

Effect. The call is completed with an error. The message is not sent to the server process.

Recovery. In some cases, you can recover from this error by retrying the call. Whether a retry will work depends on the design and operating environment of your application.

For more information about LINKMON limits, refer to“LINKMON Limit Errors” (page 44)and also to the NonStop TS/MP System Management Manual.

925

FEScTooManyRequesters

Cause. The LINKMON process is already communicating with the maximum number of requesters allowed. The maximum number of concurrently active Pathsend requesters per processor is 256. This error can occur only on the requester’s first call to SERVERCLASS_SEND_ or

SERVERCLASS_DIALOG_BEGIN_. Typical file-system error: 0 (FEOK)

Effect. The SERVERCLASS_SEND_ or SERVERCLASS_DIALOG_BEGIN_ call is completed with an error. The message is not sent to the server process.

Recovery. Retry if the number of Pathsend requesters fluctuates in this processor. 926

FEScDialogInvalid

Cause. The specified dialog identifier is not valid. This error can occur on a call to SERVERCLASS_DIALOG_SEND_, SERVERCLASS_DIALOG_END_, or

SERVERCLASS_DIALOG_ABORT_. Typical file-system error: 0 (FEOK)

Effect. The send initiation fails with an error.

Recovery. Use a valid dialog identifier. 927

FEScTooManyDialogs

Cause. The requester cannot start a new dialog, because it already has the maximum number of dialogs open. The maximum number of dialogs per requester is 256. This error can occur on a call to SERVERCLASS_DIALOG_BEGIN_.

Typical file-system error: 0 (FEOK)

Effect. The send initiation fails with an error. Recovery. Reduce the number of dialogs. 928

FEScOutstandingSend

Cause. The requester has an outstanding send operation on this dialog. This error can occur on a call to SERVERCLASS_DIALOG_SEND_.

Typical file-system error: 0 (FEOK)

Effect. The send initiation fails with an error.

Recovery. Complete the current send before starting another. 929

FEScDialogAborted

Cause. The dialog has been aborted for one of these reasons:

• The server requested a dialog abort.

• The server terminated between send operations.

• The server terminated immediately following send completion (with a reply of FEContinue), but before the LINKMON process had replied to the requester.

If the server terminated, the termination could be due to a server error or a network error. This error can occur on a call to SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_. Typical file-system error: if the server requested the abort, 1 (FEEOF); if the server terminated, the file-system error returned by the LINKMON process

Effect. The dialog is aborted. If flags.<14> was not set to 1 on the call to

SERVERCLASS_DIALOG_BEGIN_, the transaction is also aborted. The procedure (if waited) or AWAITIOX (if nowait) returns with an error.

Recovery. Use SERVERCLASS_DIALOG_END_ to terminate the requester’s portion of the dialog. 930

FEScChangedTransid

Cause. A call to SERVERCLASS_DIALOG_SEND_, SERVERCLASS_DIALOG_END_, or

SERVERCLASS_DIALOG_ABORT_ was done under a different transaction identifier than the previous call to SERVERCLASS_DIALOG_BEGIN_ (which had specified flags.<14> = 0). This is a

programming error.

Typical file-system error: 0 (FEOK)

Effect. The operation fails with an error.

Recovery. Use RESUMETRANSACTION to make the correct transaction identifier current, and reissue the call that failed.

931

FEScDialogEnded

Cause. A call to SERVERCLASS_DIALOG_SEND_ failed because the server had already ended the dialog, either by replying with FEOK or FEEOF or by terminating while a send was still outstanding. Typical file-system error: the file-system error of the last server response. Any number other than 0 (FEOK) indicates one of these:

• The dialog has been aborted.

• The previous call to SERVERCLASS_DIALOG_BEGIN_ or SERVERCLASS_DIALOG_SEND_ failed with an error that indicated an abort, but the requester has not yet aborted the dialog. Effect. The procedure initiation fails with an error.

Recovery. None. Use SERVERCLASS_DIALOG_END_ to end the specified dialog or SERVERCLASS_DIALOG_ABORT_ to abort it.

933

FEScDialogOutstanding

Cause. A call to SERVERCLASS_DIALOG_END_ was made, but the server has not ended the dialog. Typical file-system error: 0 (FEOK)

In document Matemáticas 3. Guía del docente. Roberto Villaseñor Spreitzer Víctor Manuel García Montes José Luis Hernández Palomino. prohibida su venta (Page 62-65)