Chapter 72 OSIFTAM (OSI/File Transfer, Access and Management) Messages

Cause  The backup Tandem FTAM initiator or responder process has taken over processing, because the primary process has stopped or abended or because the processor of the primary process has failed.

Effect  The backup process takes over for the primary process, with the following possible results:

Recovery  If it is important to have a backup process running at all times, follow these steps:

Cause  The specified Tandem FTAM initiator or responder process has changed from one PROCESS object state to another. If the text Operator Request is displayed, the change was the result of a Subsystem Control Facility (SCF) command issued by an operator. If the text Unknown is displayed, the cause of the state change is unknown.

Effect  The state of the process changes as indicated. See the SCF Reference Manual for Tandem FTAM and APLMGR or the Tandem OSI/FTAM Configuration and Management Manual for an explanation of process-state transitions.

If the new state is STOPPED, all FTAM associations using this process are lost and any files being written over these associations at the time of the takeover are left in an indeterminate state.

Recovery  In most cases, state transitions do not require any recovery action. However, if the new state is STOPPED as a result of an ABORT PROCESS command, follow these steps:

Cause  The specified Tandem FTAM initiator or responder process has detected an unrecoverable internal error.

Effect  The process terminates abnormally, and the backup process takes over as the new primary process and starts a new backup process. All FTAM associations using this process are lost, and any files being written over these associations at the time of the takeover are left in an indeterminate state.

	CAUTION: If this message displays more than once, the continued running of the software could significantly damage the files being accessed.

Recovery  You can attempt to continue running with the backup process; however, if this error recurs, you must stop the backup.

In any case, you need to seek additional help to recover from this error. Follow these steps:

process-name	identifies the initiator or responder process reporting this error.
trap-number	is the number of the trap encountered.
object-file	is the name of the file containing the object code for the process.
bind-timestamp	is the time at which the object file was bound.
entry-point-label	is the procedure entry-point label where the error occurred.
p-register	identifies the contents of the P (program counter) register when the error was detected. For more information on the P register, see the Guardian Programmer’s Guide.
e-register	identifies the contents of the E (environment) register when the error was detected. For more information on the P register, see the Guardian Programmer’s Guide. CAUTION: If this message appears more than once, the continued running of the software could significantly damage the files being accessed.

Cause  The primary Tandem FTAM initiator or responder process has detected a trap reported by the operating system.

Effect  The primary process terminates abnormally, and the backup process takes over as the new primary process. The new primary process starts a backup process. All FTAM associations using this process are lost, and any files being written over these associations at the time of the takeover are left in an indeterminate state.

Recovery  You can attempt to continue running with the backup process; however, if this error recurs, you must stop the backup.

In any case, you need to seek additional help to recover from this error. Follow these steps:

Cause  The primary Tandem FTAM initiator or responder process has successfully started the backup process.

Effect  Processing continues normally.

Recovery  Informational message only; no corrective action is needed.

For more information on backup processes, see the subsection on fault tolerance in the Tandem OSI/FTAM Configuration and Management Manual.

process-name	identifies the initiator or responder process reporting this error.
old-cpu	identifies the processor the process was using prior to the error this message is reporting. CAUTION: This message warrants immediate attention if it is important to have a backup process running.

Cause  The primary Tandem FTAM initiator or responder process has detected that its backup process is not present for one of the following reasons:

Effect  The effect depends on the cause, as follows:

Recovery  If you wish to operate with a backup processor, do one of the following:

For more information on backup processes, see the subsection on fault tolerance in the Tandem OSI/FTAM Configuration and Management Manual.

process-name	identifies the initiator or responder process reporting this error.
%newprocess-error	in octal, consists of the NEWPROCESS error number in bits 0 through 7 and, in some cases, a file-system error number or other code in bits 8 through 15. The most common causes of this error are as follows: Backup processor is down (newprocess-error =%5000, or NEWPROCESS error 10). Swap volume does not contain enough space for the swap file of the backup process (newprocess-error =%2453, or NEWPROCESS error 5 with file‑system error 43).
object-file	is the name of the file containing the object code for the process.
swapvol	is the current swap volume associated with the indicated process name.
priority	is the execution priority specified in the NEWPROCESS call.
cpu	identifies the processor that the process is currently using. CAUTION: This message warrants immediate attention if it is important to have a backup initiator or responder process running.

Cause  The primary Tandem FTAM initiator or responder process was unable to create its backup process because it received a NEWPROCESS error.

Effect  The inability to create a backup has one of the following effects on the process:

Recovery  If the backup processor is down (NEWPROCESS error %005000) and it is important to have a backup process running, do one of the following:

If the problem is insufficient space on the specified swap volume, do one of the following:

For any other NEWPROCESS error, see Appendix C, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If a file-system error is specified, see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

For more information on backup processes, see the subsection on fault tolerance in the Tandem OSI/FTAM Configuration and Management Manual.

process-name	identifies the initiator or responder process reporting this error.
error	identifies a file-system error. CAUTION: For some values of error, this message may indicate a system problem or a problem with the software. For this reason, this message represents a critical event.

Cause  A checkpoint input/output (I/O) message sent by the primary Tandem FTAM initiator or responder process to its backup process has returned a file-system error.

If the error is 201, the backup process went down and the primary process tried to send a checkpoint message to the backup before it detected that the backup was down.

If the error is in the range 30 through 34, a system resource problem has occurred. For instance, if the error is 30, all the link control blocks (LCBs) in the primary processor were in use.

Some other values of error can indicate a problem with the software.

Effect  If error is 201, the primary process creates a new backup process and retries the checkpoint. In this case, the error is self-correcting.

Recovery  Recovery action depends on the file-system error. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If error is 201, no corrective action is needed.

If error is in the range 30 through 34, perform the corrective action indicated in the file-system errors chapter of the Guardian Procedure Errors and Messages Manual.

If the corrective action indicated in the Guardian Procedure Errors and Messages Manual does not solve the problem, or if some other file-system error occurred, contact the Global NonStop Solution Center (GNSC) 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.

Cause  The specified FTAM initiator or responder was asked to create a process, but was unable to do so.

Effect  The process is not created.

Recovery  To determine the cause of error, convert the octal error number into binary and consult the error output description of the NEWPROCESS procedure call in the Guardian Procedure Calls Reference Manual. In most cases, you can simply repeat the NEWPROCESS call with corrected parameters.

Cause  A Tandem FTAM responder process has been unable to initiate communication with a TAPS process because an attach has failed. The following are the most likely reasons for the failure:

The TAPS process returns information about the failure in status, error‑code, and error‑subcode. For information on these APS codes, see the Tandem OSI/AS Programming Manual.

Effect  The attach fails; the responder waits five minutes and then retries the attach.

Recovery  If the error has occurred because an attach was attempted less than five minutes after a restart of the TAPS process, the responder retries the attach in five minutes and no corrective action is needed. Otherwise, take one of the following actions to recover from this error:

Cause  A Tandem FTAM initiator or responder process has detected an internal state-machine error.

Effect  The association for the state machine identified by sm-id terminates abnormally. Any file being written over this association is in an unknown state.

Recovery  To recover from this error, you need to seek additional help. Follow these steps:

Cause  A Tandem FTAM responder process has encountered a problem in attempting to access the NonStop SQL database. This problem might occur if you do not use NonStop SQL to recompile the FTAMROBJ file before attempting to access SQL files. If this is the case, the SQL error is -8025, “The SQL region was not SQL compiled.”

Effect  In most instances, the SQL statement fails, but the association is not lost. The exact effect of this message, however, depends upon the specific SQL error.

Recovery  For the appropriate recovery action and the specific cause and effect of this error, look up the SQL error in the NonStop SQL Messages Manual.

If the error is a result of not using NonStop SQL to recompile the FTAMROBJ file, you must stop all Tandem FTAM responder processes that use the object file in question, recompile the FTAMROBJ file using NonStop SQL, and then restart all processes. For more information on SQL recompilation of the object file, see the Tandem OSI/FTAM Configuration and Management Manual.

Cause  The VFS of the specified Tandem FTAM responder process has encountered a file-system error while attempting to access the specified file.

Effect  Access to the file is lost, prohibited, or restricted.

Recovery  Recovery action depends on the file-system error. If you encounter one of the common errors listed above, perform the corresponding action listed below:

For recovery from other errors, see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  A remote FTAM user has sent an invalid initiator ID or filestore password to the specified Tandem FTAM responder process in an F-INITIALIZE request. This could be due to either an application error or a breach of security.

Effect  No association is established.

Recovery  Investigate the problem to identify the cause, and correct any application errors. You can use the initiator addresses in the message to locate the remote application causing the error. If no application errors are found, log errors and failed security attempts for the monitoring and tracking of possible security breaches.

Cause  A security error has occurred during an attempt to access a file using the VFS of the specified Tandem FTAM responder process. This could be due to an application error, an error in setting the security of the file, or a breach of security.

Effect  The operation fails.

Recovery  Investigate the problem to identify the cause, and correct any application errors. You can use the initiator addresses in the message to locate the remote application causing the error. Also check the file’s security setting to make sure that the file is properly secured. If no application or security-setting errors are found, log errors and failed security attempts for the monitoring and tracking of possible security breaches.

Cause  The Tandem FTAM protocol-error counter for the specified initiator or responder process has reached a predefined threshold. This counter is incremented each time the process detects a protocol error in a protocol data unit (PDU) received from a remote FTAM process. A protocol error is any sequence of errors that violates FTAM protocol as defined by the International Organization for Standardization (ISO) 8571 standard. Examples of such errors include PDUs received out of sequence and values received that are outside of permitted ranges.

The protocol-error threshold is defined through the Subsystem Control Facility (SCF) as the value of the THRESHOLD attribute of the PROCESS object. This error is generated whenever the value of the protocol-error counter reaches a nonzero multiple of the threshold value. If the threshold is zero, this error is never generated.

Effect  The association with the remote entity is lost or is never established. If the failure occurs during a data transfer, any file being written to might be unusable.

Recovery  Check the remote entity for compatibility. You can monitor the frequency of this message for an indication that a serious problem exists. You can perform a trace of the Tandem FTAM initiator or responder using the PROV and ASN.1 selection options to investigate the PDU structure. See the Tandem OSI/FTAM Configuration and Management Manual and the SCF Reference Manual for Tandem FTAM and APLMGR.

Cause  The specified Tandem FTAM responder process has completed a file transfer (successfully or unsuccessfully) when the file is closed.

Not every “File transfer completed” event has a corresponding “File transfer started” event. This can happen when a responder process cancels a request and closes the file after the very first read attempt.

This message is always followed by OSI/FTAM operator message 24. Together, messages 23 and 24 completely describe a single “File transfer completed” event.

Effect  Informational message only; no corrective action is needed. It is generated at the completion of any file transfer operation performed by the responder process whenever a close indication, abort, or cancel request occurs in the data transfer regime. The value of Transfer status indicates whether the file transfer has completed successfully or has failed.

Recovery  Use this message in conjunction with OSI/FTAM messages 24 and 25 to monitor the status of file transfers. If Transfer status is Success, no recovery is required. If Transfer status is Failure, check the following:

If the sending application canceled the transfer, no recovery is required. If the application received diagnostic messages, corrective action depends on the diagnostic messages and might be handled by the application. If this message is preceded by other operator messages, perform the corrective action indicated for those messages.

Cause  The specified Tandem FTAM responder process has completed a file transfer (either successfully or unsuccessfully).

This message is a continuation of OSI/FTAM message 23. Together, messages 23 and 24 completely describe a single “File transfer completed” event.

Effect  For information on the effect of this message, see message 23.

Recovery  For recovery information, see message 23.

Cause  The specified Tandem FTAM responder process has started a file transfer and has received a legal write or read indication (one that does not cause a cancel or abort to be generated).

For read operations, this error is sent after the operating system has successfully completed the first read operation and there is data to include in the first data indication protocol data unit (PDU).

For write operations, this error is sent when the first data indication PDU is received.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Use this message in conjunction with OSI/FTAM messages 23 and 24 to monitor the status of file transfers.

Cause  The specified Tandem FTAM responder process has received a legal F-SELECT indication (one that does not cause an abort to be generated).

Effect  The effect depends upon the Select result and the Connection state.

If Select result=Success and Connection state=Selected, the specified file has been selected.

If Select result=Failure and Connection state=Initialized, the specified file has not been selected. In this case, the error may be immediately followed by OSI/FTAM message 29 containing diagnostic information.

Recovery  If Select result=Success and Connection state=Selected, no corrective action is needed.

If Select result=Failure and Connection state=Initialized, see the diagnostic information contained in OSI/FTAM message 29 and take the appropriate recovery steps.

Cause  The specified Tandem FTAM responder process has received a legal F‑CREATE indication (one that does not cause an abort to be generated).

This message is always followed by OSI/FTAM message 28. Together, messages 27 and 28 completely describe a single event.

Effect  Informational message only; no corrective action is needed. The effect depends upon the values displayed for Override value and File Status.

If Create result=Success and Connection state=Selected, the action taken by the subsystem depends upon Override value and whether a file already existed. The valid combinations for this error are shown in Table 72-1.

If Create result=Failure and Connection state=Initialized, the valid combinations for this error are shown in Table 72-2.

Recovery  If Create result=Success and Connection state=Selected, no corrective action is needed.

If the create failed because the file already existed, check the file name to see if it is correct or change Override value before retrying the request or both.

If the create failed for an unknown reason, see the diagnostic information contained in OSI/FTAM message 29, immediately following this error, and take the appropriate recovery steps.

For more information on creating files, see the subsection on creating files in the Tandem OSI/FTAM Programming Guide and the subsection on FTAM procedures in the Tandem OSI/FTAM Programming Reference Manual.

Cause  The specified Tandem FTAM responder process has received a legal F‑CREATE indication (one that does not cause an abort to be generated).

This message is a continuation of OSI/FTAM message 27. Together, messages 27 and 28 completely describe a single event.

Effect  For information on the effect of this message, see message 27.

Recovery  For recovery information, see message 27.

Cause  A Tandem FTAM responder process has received an F‑CREATE or F-SELECT response containing diagnostic information.

Effect  An F‑CREATE or F-SELECT response can contain up to ten diagnostic structures; this message can contain only one diagnostic structure. Therefore, message 29 is issued repeatedly until all diagnostic structures contained in the response have been sent.

Recovery  Use this diagnostic information to help locate the cause of an error. Recovery action depends on the error. For more information on error handling, error codes, observers, and sources, see the subsection on error-handling concepts in the Tandem OSI/FTAM Programming Guide. For a list of FTAM diagnostic messages, see Appendix C of the Tandem OSI/FTAM Programming Reference Manual.

Cause  The specified alternate collector has been defined, but is not running. The most common causes of this error are as follows:

This message is sent only after an initiator or responder process has performed the following steps:

Effect  The operator message in progress and this message (message 99) and all subsequent messages are sent to the primary collector ($0).

This message is generated once by the APLMGR process and once by each initiator and responder process as each process encounters a problem with the alternate collector.

Recovery  If you wish to operate with an alternate collector, you must first determine whether the alternate collector has failed to start processing or whether you need to change the configuration of the alternate collector.

If the alternate collector was not started prior to adding the FTC profile, you must delete the FTC profile, start the alternate collector, and then add the FTC profile.

For more information on retrieving information about the alternate collector, see the subsection on retrieving configuration information in the Tandem OSI/FTAM Configuration and Management Manual. For more information on alternate collectors in general, see the EMS Manual.

Cause  The virtual filestore (VFS) of the specified FTAM responder process has encountered a file-system error while attempting to access the specified file.

Effect  Access to the file is lost, prohibited, or restricted.

Recovery  Use the proper VFS configuration file.Then restart the VFS file processing. For more information on VFS, see the OSI/FTAM Responder Manual.

Cause  The startup file is corrupted. The virtual filestore (VFS) parameters configured for the FTAM Responder are invalid.

Effect  VFS file-processing fails.

Recovery  Configure all the mandatory parameters in the startup file. Then restart the VFS file-processing. For more information on VFS, see the OSI/FTAM Responder Manual.

Cause  The entry contains an invalid attribute name.

Effect  VFS file-processing fails.

Recovery  Specify a valid attribute name in the VFS configuration file, then restart VFS file-processing. For more information, see the OSI/FTAM Responder Manual.

Cause  An invalid attribute value was specified for the named attribute.

Effect  VFS file-processing fails.

Recovery  Specify a valid attribute, then restart the VFS file processing. For more information on VFS, see the OSI/FTAM Responder Manual.

Cause  One or mandatory parameters (file code and file type for an entry) is missing.

Effect  VFS file-processing fails.

Recovery  Specify all the mandatory parameters in the startup file, then restart the VFS file processing. For more information on VFS, see the OSI/FTAM Responder Manual.

Cause  The FTAM initiator and responder processes are configured with valid VFS parameters.

Effect  VFS file-processing continues normally.

Recovery  This is an informational message only. No corrective action is needed.