Archives of the TeradataForum

Message Posted: Fri, 15 Jun 2001 @ 21:07:45 GMT

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

Hello-

Well, JDBC just happens to be the bane of my existence lately. So I've got a couple of (maybe) useful ideas.

The first thing is to know what your Os's network interface commands do. Get comfy with netstat and some of your other interface goodies. You can use these to monitor sockets and ports and get an idea of what the communication looks like on all of the boxes.

Next, I'd suggest a quick read of the CLIv2 manual for Network attached something-or-other. Basically the CLIv2 manual on the cdrom, that'll also have the JDBC users guide in it.

What we have done is setup the exits on the JDBC gateway to act as an ACL for the gateway, thereby we are controlling access to teradata at the gateway, and our little developers (who like to swap code) can't give their friends access to a gateway box they don't have rights to admin.

The exits are documented in the CLI manual, but I will say this: don't ask for the mtdp.h header file, you don't need it and they won't give it to you....

Now the exits are very neat in that they can also be coded to capture Pre- and Post- SQL commands to and from the gateway. That means taht you can capture both sides of the query at the gateway and tune it in process (or stop it, or whatever).

Now, for more on the jserver, the process is still a bit of an annoyance to me, teh scripts I've used for starting and stopping it have been less than good, and if you don't use the jutil utility that NCR puts out, it seems to shut down rather nastily (in older versions it would power off the box running the gateway). I'm still working on this, but another way to monitor what is happening is the 'ps' command for looking at processes (I work on MP-RAS, so I'm not sure of the Windows equivalents here), it will show you what you'd want to know about the initial process and any children and such that it has spawned. Along with this is the 'truss' command, this is useful to intercept a process in progress (or at startup) and watch exactly what it is doing. You cna see what libraries it opens, what fd's get allocated, and what it is running.

For most of these, the man pages are excellent resources, but again, the CLI manual held the secret of those exits for me, take a look there as well.

loadc

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