Archives of the TeradataForum

Message Posted: Wed, 16 Nov 2005 @ 18:08:25 GMT

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

Say HUH? An Idle Ferret task consumes no resources ( other than a Window on the DBW screen ). Are you saying that Ferret is still running ( non idle ) after the packdisk is over?

Have you opened an Incident with the Teradata Global Support center?

Can you tell us how to reproduce this behavior so we can debug this and fix it.

The first thing they will probably need is

     /usr/ntos/bin/puma -B ferret    ( backtrace )

on the node where ferret is 'running' when you think it should have exited.

Maybe Ferret is eating your QUIT command thinking it is the input coming for the ABORT/INQ prompt. maybe Ferret INPUT gets messed up when your Script breaks its PIPE to CNSTOOL.

Have you tried the ferret command

     enable scriptmode

to tell ferret you are running from a script so that it can interact with your script processing better?

Typically To Automate packdisk like from CRON you can use the tool.

     CNSRUN

this allows you to interact with CNS without needing the CNSTERM tool up. It works for Any utility provided They don't have an ABORT mechanism. ( which basically eliminates packdisk, scandisk and Checktable, the 3 tools you want to automate ).

However with Checktable we provide a version checktableb which doesn't allow the abort, and for Ferret ( PACKDISK and SCANDISK ) I added a new command

     enable scriptmode

that tell ferret to disable its abort mechanism so it can run correctly through CNSRUN.

However this means that you must allow both checktableb and ferret in script mode to run to completion since in this mode they are not abortable.

     cnsrun -utility ferret -commands \
         '{enable scriptmode} {output over /tmp/packdisk.out} {packdisk fsp = 20 } {Y} {quit}' \
         -debug 1

( the debug 1 is required because by default the output of CNSRUN doesn't come back to the screen. For Ferret isn't a problem since the output is going into the file, but for other utilities it might be. )

each utility command is enclosed in brackets {...}. Each time the utility asks for input CNSRUN will automatically send the next bracketed item.

If you have too many commands that won't fit on the command line you can put them in a file

     /tmp/mycmds

          enable scriptmode
          output over /tmp/packdisk.out
          packdisk fsp = 20
          Y
          quit

and then tell cnsrun where the file is.

     cnsrun -utility ferret -file /tmp/mycmds -debug 1

Note that within the file you don't use the brackets {...}

It is a good idea to keep CNSTOOL / DBW up while you are developing your CNSRUN script because if CNSRUN aborts or send a bad command to your utility, there is a possibility that it will again Leave the utility running in one of the applications windows.

you can also watch what CNSRUN is doing by monitoring the utility in the CNSTOOL/DBW window as well.

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