|Using TenDo ||
TenDo offers various connectivity options.
TenDo provides functionality for terminating sessions, keeping sessions alive, and connecting to 1010data from behind corporate proxy servers.
can't log in: rc=5 (Already logged in)In this event, you will need to end the existing connection before TenDo can use the account to connect to 1010data. You do this by killing the existing session with the -k switch. This option doesn't take an argument and is called as follows:
$ tendo -k -u [USERNAME] [TABLE] @[QUERY]This command will automatically disconnect your existing session and run your query via TenDo.
$ tendo -u [USERNAME] -P http://[PROXYUSERNAME]:[PROXYUSERPASSWORD] @www.corporateproxyserver.com:8080 [TABLE] @[QUERY]This command routes the TenDo connection through the specified proxy server, then connects to 1010data and runs your query as normal. If you do not know the correct proxy server information to provide, ask your network administrator. If you encounter the Transport error 7: Couldn't connect to server message, you need to add proxy credentials.
Some queries take longer to finish running than others. Occasionally, a TenDo session will timeout while a query is running if the query is very large. This is especially true if you are behind a corporate proxy server. To help manage your connection and prevent unwanted timeouts from occurring, TenDo provides two useful options: -~ and --retries. You can use these options in unison to prevent timeouts from happening before your query finishes running.
$ tendo -u [USERNAME] [TABLE] @[QUERYFILE] -~ 400This command tells TenDo to reestablish the transaction after 400 seconds. If a timeout has occurred, when TenDo retries the query, it will pick up where it left off at the time of the timeout. Note that we have not provided a number of times to retry. If you do not provide a number of retries using the --retries option, TenDo will default to 10 total attempts; the initial attempt and 9 retries.
$ tendo -u [USERNAME] [TABLE] @[QUERYFILE] -~ 400 --retries=15This command tells TenDo to retry the query every 400 seconds for 15 consecutive attempts. If you multiply your specified retry interval by the number of retries you've specified, the product will be the total amount of time (in this case 6000 seconds or 1 hour and 40 minutes) before the transaction will timeout entirely. This is important because your total time before a complete timeout should roughly be as long as the maximum theoretical time it will take your query to run. You may need to experiment with your proxy server and your queries to find the optimal number.
$ tendo --pool=[GROUP_NAME] -u [GROUP_OWNER_NAME] -p [GROUP_OWNER_PASSWORD] [TABLE] @[QUERY]This tells TenDo to login to 1010data with the first free account in the SAM pool. If no accounts are presently available, TenDo will return an error stating that the system is busy.