Sponsored Content
Operating Systems Solaris OSI 9.0 Installation some question Post 101808 by RTM on Monday 13th of March 2006 10:45:32 AM
Old 03-13-2006
From sunsolve:

Quote:
An error pop-up displays ERROR: UNABLE TO UNLOAD THE OSI DRIVER (oopi)

If the OSI driver has been running and other applications such as FTAM,
X.400, or a customer written applications that has either pending or open
connections to other destinations, the OSI stack is not able to close and
unload the driver.

Solution:

Stop all other OSI related applications. To find out which application is
causing a problem, issue the command ps -ef | grep osi at the command prompt
in the console. This will display the OSI stack processes along with any
other Sun related OSI applications.

Be sure to perform an orderly shutdown of each application and the OSI stack
as specified in the OSI manual. Using the UNIX kill command on these
processes may cause undesirable results and corrupt files.
 

8 More Discussions You Might Find Interesting

1. IP Networking

The OSI-model

after reading a paper about the OSI-model I'm not exactly sure how to look at this model. Does data (a file) travel from the application level "down" each layer at the client Application V Presentation V Session V Transport V Network V Data link V | | | (Physical) | (3 Replies)
Discussion started by: J.P
3 Replies

2. SuSE

installation question

Hello people! I just wanted to install SuSE on another computer now, so i booted from the newest cd iso.. It has a flashy welcome screen :p and stuff, but then when i start manual installation select everything, then go to ftp install, i say automatic via dhcp or whatever and then it asks for an... (5 Replies)
Discussion started by: thenewestuser
5 Replies

3. Solaris

OSI 9.0 Installation

Dear After i received a demo license for OSI 9.0 from SUN , i installed the packages . but when i tried to start the osinet deamon ( /etc/rc2.d/S90osinet ) i am getting the foellowing errror # ./S90osinet start starting osi daemon/usr/sbin/osinetd cannot find a valid license (STACK 9.0)... (4 Replies)
Discussion started by: itsgeorge
4 Replies

4. Solaris

OSI interface...

I'm using OSI version 9.0 with solaries OS , I 'm thinking of analysing the tracing while sending information through OSI layers , I want to analyze exactly the BER data ? Any one could provide an examples , I know the command for tracing these information but i need to understand the bytes travels... (1 Reply)
Discussion started by: atiato
1 Replies

5. Red Hat

jdk installation question

hi, i just "yum install jdk*.i386" and installation was complete without any error. however, i tried to #javac helloworld " and javac is not found in the $PATH. i tried to locate it and didn't find it. would anyone shed some light on where the "yum install" installed my jdk to? where can i find... (0 Replies)
Discussion started by: k2k
0 Replies

6. Debian

OSI application for Debian...

Is there OSI telecom application which can be installed on debian similar to Solstice Solaries OSI ? I need to get it on debian to build cmise and communicate with Network element . (0 Replies)
Discussion started by: atiato
0 Replies

7. UNIX for Dummies Questions & Answers

linux installation question?

Hi I accidentally installed another operating system after I had installed Linux and now I can no longer access your Linux system.any solution? Thanks (1 Reply)
Discussion started by: adam25bc
1 Replies

8. SCO

Sco 5.0.7 installation question

Is there a way to install the "hpsas" btld for the hard disk controller during installation of the OS without having to use a Floppy disk, ie Pen drive or CD since newer servers do not include a floppy drive? If so, please include specific instructions in the answer. Thank you. (8 Replies)
Discussion started by: juan.navarrete
8 Replies
t_open(3)						     Library Functions Manual							 t_open(3)

NAME
t_open() - establish a transport endpoint SYNOPSIS
DESCRIPTION
The function must be called as the first step in the initialization of a transport endpoint. This function establishes a transport end- point by opening a file that identifies a particular transport provider and returning a file descriptor that identifies that endpoint. The argument name points to a file name that identifies a transport provider. When using HP XTI to connect to the OSI protocol stack, name must be for the connection-mode service, or for the connectionless service. When using HP XTI to connect to the TCP protocol stack, name should be For UDP, name should be (See also the section.) For TLI, use the device file name of the transport provider desired. Note that HP TCP/UDP/IP and HP OSI COTS and CLTS only support XTI. oflag identifies any open flags (as in and is constructed from optionally or-ed with These flags are defined by the header file returns a file descriptor that will be used by all subsequent functions to identify the particular local transport endpoint. This function also returns various default characteristics of the underlying transport protocol by setting fields in the structure. This argument points to a which contains the following members: The values of the fields have the following meanings: addr A value greater than or equal to zero indicates the maximum size of a transport protocol address. A value of -1 specifies that there is no limit on the address size. A value of -2 specifies that the transport provider does not provide user access to transport protocol addresses. options A value greater than or equal to zero indicates the maximum number of bytes of protocol-specific options supported by the provider. A value of -1 specifies that there is no limit on the option size. A value of -2 specifies that the transport provider does not support user-settable options. tsdu A value greater than zero specifies the maximum size of a transport service data unit (TSDU). A value of zero specifies that the transport provider does not support the concept of TSDU, although it does support the sending of a data stream with no logical boundaries preserved across a connection. A value of -1 specifies that there is no limit on the size of a TSDU. A value of -2 specifies that the transfer of normal data is not supported by the transport provider. etsdu A value greater than zero specifies the maximum size of an expedited transport service data unit (ETSDU). A value of zero specifies that the transport provider does not support the concept of ETSDU, although it does support the sending of an expedited data stream with no logical boundaries preserved across a connection. A value of -1 specifies that there is no limit on the size of an ETSDU. A value of -2 specifies that the transfer of expedited data is not supported by the transport provider. connect A value greater than or equal to zero specifies the maximum amount of data that may be associated with the connection estab- lishment functions and A value of -1 specifies that there is no limit on the amount of data sent during connection establishment. A value of -2 specifies that the transport provider does not allow data to be sent with connection establishment functions. discon A value greater than or equal to zero specifies the maximum amount of data that may be associated with the and functions. A value of -1 specifies that there is no limit on the amount of data sent with these abortive release functions. A value of -2 specifies that the transport provider does not allow data to be sent with the abortive release functions. servtype This field specifies the service type supported by the transport provider, as described below. flags This is a bit field used to specify other information about the transport provider. If the bit is set in flags, this indi- cates the underlying transport provider supports the sending of zero-length TSDUs. See Appendix A, "ISO Transport Protocol Information," of the manual from X/Open Company Limited for a discussion of the separate issue of zero-length fragments within a TSDU. If a transport user is concerned with protocol independence, the above sizes may be accessed to determine how large the buffer must be to hold each piece of information. Alternatively, the function may be used to allocate these buffers. An error will result if a transport user exceeds the allowed data size on any function. The servtype field of info specifies one of the following values on return: The transport provider supports a connection-mode service but does not support the optional orderly release facility. The transport provider supports a connection-mode service with the optional orderly release facility. The transport provider supports a connectionless-mode service. For this service type, will return -2 for etsdu, connect, and discon. A single transport endpoint may support only one of the above services at one time. If info is set to a null pointer by the transport user, no protocol information is returned by Obsolescent Interfaces When using TCP and UDP through HP XTI, name can be and respectively. These names are supported for backward-compatibility purposes. They might not be supported in future releases, and they should be replaced with and respectively. Fork Safety is not fork-safe. RETURN VALUE
A valid endpoint identifier is returned upon successful completion. Otherwise, a value of -1 is returned and is set to indicate an error. HP OSI does not support the servtype. ERRORS
On error, is set to one of the following: [TBADFLAG] An invalid flag is specified. [TBADNAME] Invalid transport provider name. [TSYSERR] A system error has occurred during execution of this function. [TPROTO] (XTI only) This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no suitable XTI ( SEE ALSO
open(2), t_sync(3), thread_safety(5). STANDARDS CONFORMANCE
t_open(3)
All times are GMT -4. The time now is 02:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy