Differences

This shows you the differences between two versions of the page.

--- general:framework_connection [2019/08/07 15:44] – dcumming
+++ general:framework_connection [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 11: / Line 11: @@
 In addition to direct TCP/IP connections, the TapeTrack communications API also supports connections via a HTTP Proxy.
-====== Names and IP addressess ======
+====== Names and IP addresses ======
 As with all TCP/IP connections, the endpoint address can be represented by either a domain name or dotted IP address.
@@ Line 20: / Line 20: @@
 \\
 \\
-<sxh text;>
+<code text;>
 jsmith> nslookup tapetrack.gazillabyte.com
 Server:  dc1.gazillabyte.local
@@ Line 28: / Line 28: @@
 Name:    tapetrack.gazillabyte.com
 Address:  192.241.211.124
-</sxh>
+</code>
 </note>
@@ Line 51: / Line 51: @@
 As an example, using TapeTrack Framework Server at address **tapetrack.gazillabyte.com**, on port **5000** a successful test would look like this:
-<sxh plain;>
+<code plain;>
 [root@documentation-us conf]# TMSS10Ping -P 5000 tapetrack.gazillabyte.com
 bytes from 192.241.211.124: seq=1 time=0.00 ms
@@ Line 61: / Line 61: @@
 packets transmitted
 round-trip min/avg/max = 0.00/0.00/0.00 ms
-</sxh>
+</code>
 If TMSS10Ping fails to make a valid connection, try to connect via port 443.
-<sxh plain;>
+<code plain;>
 [root@documentation-us conf]# TMSS10Ping -P 443 tapetrack.gazillabyte.com
 bytes from 192.241.211.124: seq=1 time=0.00 ms
@@ Line 75: / Line 75: @@
 packets transmitted
 round-trip min/avg/max = 0.00/0.00/0.00 ms
-</sxh>
+</code>
 If a connection cannot be successfully completed through either port contact your network administrator to ensure ports are open.
@@ Line 86: / Line 86: @@
 An example for connecting as user **jsmith**, with password **mypassword** is:
-<sxh plain;>
+<code plain;>
 -S jsmith:-mypassword@tapetrack.gazillabyte.com
-</sxh>
+</code>
 For detailed instructions on how to use the ''-S'' argument please see the [[cli:server_argument|Command Line Server Argument]] page.
@@ Line 125: / Line 125: @@
 All TapeTrack programs use an underlying low level communications API which allows users to trace connection and communications requests.
-To enable logging, set the [[variable:start|environmental variable]] [[variable:TMSSAPILOGDIR|TMSSAPILOGDIR]] to the path of an existing directory.
+To enable logging, set the [[variable:start|Environmental Variable]] [[variable:TMSSAPILOGDIR|TMSSAPILOGDIR]] to the path of an existing directory.
 <note important>
@@ Line 131: / Line 131: @@
 </note>
-<sxh plain;>
+<code plain;>
 set TMSSAPILOGDIR=c:\Users\jsmith\Desktop\logs
 TMSS10Ping localhost
-</sxh>
+</code>
 Creates the file **TMSSAPILOG-005336.txt** with the contents:
-<sxh plain;>
+<code plain;>
 :39:25: TMSS10API_Init (API Version=Feb  2 2017 10:18:50)
 :39:25: TMSS10API_Connect: Server(localhost) Port(5000)
@@ Line 151: / Line 151: @@
 :39:25: TMSS10API_Send: RC(Request OK) Feedback(0) MilliSecs(0) Avail(0) Count(0) Length(0)
 :39:25: TMSS10API_Term
-</sxh>
+</code>
 ===== See Also =====
-[[technote:setting_environmental_variables|Setting environmental variables]]
+[[technote:setting_environmental_variables|Setting Environmental Variables]]
-{{tag>communication environmental_variables logging}}
+{{tag>communication  logging}}