Chapter 73 OSITS (OSI/Transport Services) Messages

Cause  OSI/TS detected an internal state-machine error.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The connection abends. Any file being written is in an unknown state.

Recovery  Retry the connection. If a retry is unsuccessful, you need to seek additional help. Follow these steps:

Cause  OSI/TS detected an unrecoverable internal error.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The transport service provider (TSP) process abends; the backup process takes over as the new primary process and attempts to start a new backup process. However, this error indicates a software problem, and the continued running of the software could significantly damage the files being accessed.

Recovery  If this error occurs, you need to seek additional help. Follow these steps:

Cause  OSI/TS detected an unrecoverable error, such as a state-machine or internal error.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The TSP process, either primary or backup, abends. If the primary process abends, the backup process takes over. If the backup process abends, the primary process attempts to create a new backup.

Recovery  If this error occurs, you need to seek additional help. Follow these steps:

Cause  A request for buffer space was not satisfied.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The attempted operation fails. OSI/TS attempts to recover by retrying the operation.

Recovery  Reconfigure the process with a larger BUFFERPOOLSIZE or fewer MAXCONNECTIONS. You might have to bring down the process first.

If the problem persists, you need to seek additional help. Follow these steps:

Cause  The backup of the specified process has taken over from the primary for one of the following reasons:

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

Recovery  If an operator requested the change, check with the other operations personnel at your installation for instructions.

If the backup processor is down and you want to create another backup process, first either reload the old processor or stop the new primary process and restart the TSP process pair using a different backup processor.

Then follow these steps:

Cause  The backup process has been started in the specified processor.

Effect  Processing continues normally.

Recovery  Informational message only; no corrective action is needed.

Cause  The primary process detected that the backup process had stopped or abended or that the backup processor was down.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The primary process tries to create a new backup process unless the designated backup processor is unavailable. If the backup processor is down, the primary process waits until the processor is reloaded or another backup processor is designated.

Recovery  If the backup processor is down and you want to create another backup process, either reload the old processor or stop the primary process and restart the TSP process pair using a different backup processor.

Cause  The primary process designated by processname was unable to create a backup process because of a process creation error, possibly caused by the backup processor going down. The message displays the error returned by the PROCESS_CREATE_ procedure, followed by the object-file name, swap-volume name, priority, processor number, and process name that were passed to PROCESS_CREATE_.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  If the failure occurred because the backup processor is down, the primary process waits for the CPU UP system message before trying again. Otherwise, the primary process continues trying until a backup process is created. It does not report unsuccessful retries.

Recovery  For information on error, seeAppendix D. Perform the appropriate corrective actions for that error. If the backup processor is down and you want to create another backup process, either reload the old processor or stop the primary process and restart the transport service provider (TSP) process pair using a different backup processor.

Cause  A checkpoint I/O operation from the primary process returned an error because of insufficient resources or an internal logic error. If this error occurs frequently, it is probably caused by an internal logic error.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The primary process stops the backup process and tries to start a new one.

Recovery  See Appendix B, for further information on error. No recovery action is needed when the cause of the error is insufficient resources—for instance, file-system error 30 or 31.

If you suspect an internal logic error, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If these procedures involve contacting your HP service provider, 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.

For additional information on gathering support documentation, see the chapter on troubleshooting in the OSI/TS Configuration and Management Manual.

Cause  The backup process might not have received all of the checkpoint messages that were supposed to be sent by the primary process. This condition is most likely to happen if the primary process fails while the backup process is being brought up.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  If the backup process takes over, it might not be able to assume the primary role correctly. Some of the context established with the old primary process probably is lost. The severity of subsequent problems is not predictable. The subsystem might not be able to recover from these subsequent problems without operator intervention.

Recovery  If the primary process failed, restart the transport service provider (TSP) process pair. Otherwise, stop the backup process and allow the primary process to recreate the backup and resend the checkpoint message.

If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If these procedures involve contacting your HP service provider, 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.

For additional information on gathering support documentation, see the chapter on troubleshooting in the OSI/TS Configuration and Management Manual.

Cause  The process, process-name, could not allocate the extended data segment. error is the SEGMENT_ALLOCATE_ error.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The process abends.

Recovery  Try one or more of the following recovery actions:

For more information on error, refer Appendix F.

Cause  OSI/TS detected a trap caused by a hardware or software error.

Effect  The TSP process abends; the backup process takes over as the new primary process and attempts to start a new backup process. However, this error indicates a software problem, and the continued running of the software could significantly damage the files being accessed.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Recovery  If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If these procedures involve contacting your HP service provider, 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.

For additional information on gathering support documentation, see the chapter on troubleshooting in the OSI/TS Configuration and Management Manual.

Cause  One of the following conditions occurred:

Effect  OSI/TS could not access an NSP subdevice (X25AM, TLAM (for D-series), or TCP/IP socket), or a Distributed Systems Management (DSM) server (such as $ZNET). Any transport connections that have been established are disconnected.

Recovery  file-name and error can help you to determine where the error occurred. See Appendix B, for further information on error. If the message was caused by a configuration error, reconfigure the subdevice or the OSI/AS MIB. If you are running OSI/AS over OSI/TS and the problem persists, use the Subsystem Control Facility (SCF) CHECK command as described in the OSI/AS Configuration and Management Manual.

If the message was caused by an NSP subdevice or $ZNET error, check that the subdevice or the $ZNET process is running and is in the proper state. If not, bring it up again. Otherwise, you need to seek additional help.

If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If these procedures involve contacting your HP service provider, 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.

For additional information on gathering support documentation, see the chapter on troubleshooting in the OSI/TS Configuration and Management Manual.

Cause  OSI/TS failed to perform a Subsystem Programmatic Interface (SPI) command on a subdevice to or from the X25 Access Method (X25AM) process or, on D-series RVUs, the Lan Access Method (TLAM) process. The subdevice may be configured incorrectly.

Effect  Failure to add or start a subdevice causes the associated transport connection to be disconnected; outstanding transport service requests are returned with an error. No further action is taken for failure of other SPI commands.

Recovery  To identify the Distributed Systems Management (DSM) error reported in error, see the OSI/TS SCF Reference Manual, the SCF Reference Manual for X25 or, if (on D-series RVUs) the SCF Reference Manual for TLAM. If the error was caused by a configuration error, reconfigure the OSI/TS subdevice or subdevices or the OSI/AS Management Information Base (MIB). For delete errors, you must delete the subdevice with the Subsystem Control Facility (SCF) STOP command.

For failure of other commands, follow the standard procedures at your site for contacting the appropriate support personnel. If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If these procedures involve contacting your HP service provider, 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.

For additional information on gathering support documentation, see the chapter on troubleshooting in the OSI/TS Configuration and Management Manual.

Cause  OSI/TS could not allocate a time-list element (TLE) from the operating system.

	NOTE: This event is designated by the subsystem as critical, because it warrants immediate attention if normal processing is to continue.

Effect  The TSP process abends; the backup process takes over as the new primary process and attempts to start a new backup process. However, this error indicates a software problem, and the continued running of the software could significantly damage the files being accessed.

Recovery  Run SYSGEN to increase the number of TLEs or redistribute the load on the processors.

If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If the problem persists, you need to seek additional help. Follow the standard procedures at your site for contacting the appropriate support personnel. If these procedures involve contacting your HP service provider, 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.

For additional information on gathering support documentation, see the chapter on troubleshooting in the OSI/TS Configuration and Management Manual.

Cause  An error other than a protocol error or invalid destination address occurred on the connection identified by su-name.

Effect  OSI/TS terminates the connection and continues processing.

Recovery  Reestablish the connection. If the error occurs repeatedly, you need to seek additional help. Follow these steps:

Cause  OSI/TS received a request with an invalid destination address on the connection identified by su-name.

Effect  OSI/TS rejects the request and continues processing.

Recovery  Check the subdevice configuration for correct destination addresses: remote transport selector (TSEL), remote network service access point (NSAP), remote local area network (LAN) subnetwork point of attachment (SNPA), or the X.25 data terminal equipment (DTE) address. Correct the configured addresses as needed.

Cause  OSI/TS detected a transport-protocol violation by the remote transport entity on the connection identified by su-name. A protocol error is any sequence of errors that violates file transfer, access, and management (FTAM) protocol as defined by the International Standards Organization (ISO) 8571 standard. Examples of such errors include protocol data units (PDUs) received out of sequence and values received that are outside of permitted ranges.

Effect  OSI/TS terminates the connection and continues processing. If the failure occurs during a data transfer, the state of the source file is unchanged but the target file might be unusable.

Recovery  Retry the connection. If a retry is unsuccessful, interoperability problems might be indicated and you need to seek additional help. Follow these steps:

Cause  A Network Layer internet protocol (IP) network-management counter has reached a predefined threshold. Depending on the threshold value, frequent occurrences of this error can indicate anomalies in the subsystem configuration or the network, such as hardware errors or overload at peak times.

Network Layer network-management counters are the modulo threshold values specified in the Subsystem Control Facility (SCF) or the Programmatic Subsystem Interface (SPI) ALTER SERVICE command for the network (L3) service. A Network Layer IP counter is incremented each time an IP packet is discarded for the general reason associated with that counter—for instance, because of a reassembly error. This error might indicate a problem, or it might merely indicate that the threshold was set too high.

Effect  None.

Recovery  Check the discard-code. You can monitor the frequency of this message for an indication that a problem exists. You can perform a trace of the transport service provider (TSP) process using the L3 selection option to investigate the protocol data unit (PDU) structure.

If a configuration or network problem is indicated, contact the network administrator at your installation for further analysis of the problem.

If no problem is indicated, thresholds can be adjusted by the OSI/TS subsystem administrator to increase or decrease the frequency of error messages or to completely suppress the generation of this error message.

Cause  A Transport Layer network-management counter has reached a predefined threshold. Depending on the threshold value, frequent occurrences of this error can indicate anomalies in the subsystem configuration, such as incorrect addresses.

Transport Layer network-management counters are the modulo threshold values specified in the Subsystem Control Point (SCF) or the Subsystem Programmatic Interface (SPI) ALTER SERVICE command for the transport (L4) service. A Transport Layer counter is incremented each time the transport service detects the occurrence associated with that counter—for instance, the receipt of an inbound CR transport protocol data unit (CR-TPDU). This error might indicate a problem, or it might merely indicate that the threshold was set too high.

Effect  None.

Recovery  Check the dr-or-er-code. You can monitor the frequency of this message for an indication that a problem exists. You can perform a trace of the transport service provider (TSP) process using the L4 selection option to investigate the protocol data unit (PDU) structure.

If a configuration or network problem is indicated, contact the network administrator at your installation for further analysis of the problem.

If no problem is indicated, thresholds can be adjusted by the OSI/TS subsystem administrator to increase or decrease the frequency of error messages or to completely suppress the generation of this error message.