Archives of the TeradataForum

Message Posted: Fri, 23 Apr 1999 @ 19:21:40 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I may have come in late and missed the thrust of this discussion, but it sounds like a syntax / setup question.

The answer below includes both syntax and setup. The syntax should be the same no matter what the platform (MVS, Unix, MS-Dos etc etc etc). My environment features two computers the first is a Unix system (gpes26) which interactive users log onto; the second is the Teradata system (gpesa). The two systems are connected via TCP/IP via Ethernet.

I log on to gpes26 using a telnet (or X term) session and run bteq. To connect a bteq session (on gpes26) to the Teradata (on gpesa) I enter the following logon command (to bteq).

     .logon gpesa/glennm

In this scenario, bteq is connected to teradata as a "Network attached client".

This syntax also works for Fastexport, Fast Load and Multiload.

I am not aware of Teraperl, but would be interested in finding out more about (hint) as I use perl alot. Anyway, I imagine that in a Teraperl program running on gpes26 the syntax would be:

     connect gpesa/glennm

It is also possible to set up an environment where a "network attached client" may default to a particular session. The advantage of this is that if you connect from a client system to the same Teradata system most of the time, you can omit the "gpesa/" portion of the logon string.

------

Now the setup. To make this work on Unix (and most likely DOS and Windows) I need to create some entries in the tcp/ip hosts file. The entry is 1.2.3.4 gpesa gpesacop1

If I had multiple cops (nodes) I could also add an entry such as:

     1.2.3.5 gpesacop2
     1.2.3.6 gpesacop3

and so on.

To set these you may need your system administrator to help you

I hope this helps.

Glenn McCall
NCR

	<Prev	Next>		<<First	<Prev	Next>	Last>>