tt_host_file_netfile(3) [hpux man page]

tt_host_file_netfile(library call)										tt_host_file_netfile(library call)

NAME

       tt_host_file_netfile -- map between local and canonical pathnames on a remote host

SYNOPSIS

       #include <Tt/tt_c.h>
       char *tt_host_file_netfile(
       const char *host,
       const char *filename);

DESCRIPTION

       The  tt_host_file_netfile function performs a conversion equivalent to that of the tt_file_netfile(3) function, but performs it on a remote
       host.

       The filename argument is a pathname (absolute or relative) that is valid on the remote host.   Every  component	of  filename  must  exist,
       except for the last component.  The host argument is a name of a remote host.

RETURN VALUE

       Upon  successful  completion,  the  tt_host_file_netfile function returns a freshly allocated null-terminated string of unspecified format,
       which can be passed to tt_netfile_file(3) or tt_host_netfile_file(3); otherwise, it returns an error  pointer.	The  application  can  use
       tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

       TT_ERR_PATH
		 The filename argument is a path that is not valid on the remote host.

       TT_ERR_DBAVAIL
		 The  ToolTalk	database server could not be reached on host, perhaps because the host is unavailable or cannot be reached through
		 the network.

       TT_ERR_DBEXIST
		 The ToolTalk database server is not properly installed on host.

       TT_ERR_UNIMP
		 The ToolTalk database server contacted is of a version that does not support tt_host_file_netfile.

APPLICATION USAGE

       The tt_file_netfile(3), tt_netfile_file(3), tt_host_file_netfile(3) and tt_host_netfile_file(3) functions allow an application to determine
       a  path valid on remote hosts, perhaps for purposes of constructing a command string valid for remote execution on that host.  By composing
       the two calls, paths for files not accessible from the current host can be constructed.	For example, if path /sample/file is valid on host
       A, a program running on host B can use

       tt_host_netfile_file("C", tt_host_file_netfile("A", "/sample/file"))

       to determine a path to the same file valid on host C, if such a path is possible.

       Allocated strings should be freed using either tt_free(3) or tt_release(3).

       The tt_open(3) function need not be called before tt_host_file_netfile.

SEE ALSO

       Tt/tt_c.h - Tttt_c(5), tt_file_netfile(3), tt_netfile_file(3), tt_host_netfile_file(3), tt_open(3), tt_free(3), tt_release(3).

														tt_host_file_netfile(library call)

Check Out this Related Man Page

tt_default_session_set(library call)									      tt_default_session_set(library call)

NAME

       tt_default_session_set -- set the current default session identifier

SYNOPSIS

       #include <Tt/tt_c.h>
       Tt_status tt_default_session_set(
       const char *sessid);

DESCRIPTION

       The tt_default_session_set function sets the current default session identifier.

       The  ToolTalk  service  uses the initial user session as the default session and supports one session per procid.  The application can make
       this call before it calls tt_open(3) to specify the session to which it wants to connect.

       The sessid argument is a pointer to the unique identifier for the session in which the procid is interested.

RETURN VALUE

       Upon successful completion, the tt_default_session_set function returns the status of the operation as one of the following Tt_status  val-
       ues:

       TT_OK	 The operation completed successfully.

       TT_ERR_NOMP
		 The ttsession(1) process is not running and the ToolTalk service cannot restart it.

       TT_ERR_PROCID
		 The current default process identifier is out of date or invalid.

       TT_ERR_SESSION
		 The specified ToolTalk session is out of date or invalid.

APPLICATION USAGE

       To change to another opened session, the application must use the tt_default_procid_set function.

       To  join  other	sessions,  the	procid	must  first  set the new session as the default session, and then initialize and register with the
       ToolTalk service.  The calls required must be in the following order:

       tt_default_session_set
       tt_open

       The tt_open(3) may create another ToolTalk procid, the connection to which is identified by a procid.  Only one ToolTalk session per procid
       is allowed.  (However, multiple procids are allowed in a client.)  There are no API calls to determine to which session a particular procid
       is connected.  If it is important for the application to know the session to which it is connected, it must make the following calls in the
       indicated order:

       tt_open
       tt_default_session

       The application can then store the information by indexing it by the procid returned by the tt_open(3) call.

SEE ALSO

       Tt/tt_c.h - Tttt_c(5), tt_open(3), tt_default_procid(3), tt_default_session(3).

													      tt_default_session_set(library call)

Linux and UNIX Man Pages

tt_host_file_netfile(3) [hpux man page]

Check Out this Related Man Page