IDS Forum

RE: dbaccess output display width from cron

Posted By: Jonathan Leffler
Date: Thursday, 28 April 2005, at 1:00 a.m.

In Response To: RE: dbaccess output display width from cron (Danny Wright)

forum.subscriber@iiug.org wrote on 04/27/2005 03:25:06 PM:

> I actually tried that, but it didn't seem to have any effect.

Oh - bother. I suspect that means that DB-Access is using an even more
archaic version of the curses library than ISQL, which does recognize
COLUMNS. Did you mention setting COLUMNS? Oh well...
Sorry - the source of the trouble (no controlling terminal for cron jobs)
is probably the correct diagnosis. I didn't attempt to check the use of
COLUMNS.

Recommend using one of the many alternatives suggested by others - or
SQLCMD suggested by me.

--
Jonathan Leffler (jleffler@us.ibm.com)
STSM, Informix Database Engineering, IBM Information Management Division
4100 Bohannon Drive, Menlo Park, CA 94025
Tel: +1 650-926-6921 Tie-Line: 630-6921
"I don't suffer from insanity; I enjoy every minute of it!"


> From: Jonathan Leffler [mailto:jleffler@us.ibm.com]
> Sent: Tuesday, April 26, 2005 9:34 PM
>
> Sorry about the top-posting.
>
> Set COLUMNS=132 in the environment; cron-run programs don't have a
> controlling terminal, and in the absence of information to the contrary,
> assume the terminal is 80 characters wide.
>
> Use SQLCMD - one of the reasons it exists is because ISQL (and
DB-Access)
> are inconsistent in their output formatting.
>
> When you sum integers, the type of the result is a (big) DECIMAL because
if
> you add enough big enough integers together (or count enough rows), the
> result overflows your 32-bit integer value. UNLOAD puts the ####.0
there to
> emphasize that the type is, in fact, a DECIMAL(32) - floating point,
> 32-digit decimal value. SQLCMD does the same - probably for consistency
> with DB-Access, or because it uses the same formatting code as
DB-Access.
>
> forum.subscriber@iiug.org wrote on 04/26/2005 01:37:17 PM:
> > Thanks for all the input from everyone.
> >
> > I had already stripped out as much unnecessary stuff that I could
think of
> > and so I went with Jean's 2nd suggestion - unloading to a file and
> > maniupulating that.
> >
> > By sheer luck, I happened to notice a utility I had downloaded months
ago
> > and forgotten about called beautify-unl.sh (I'm fairly certain it's
from the
> > IIUG software depository).
> >
> > beautify-unl.sh lines the columns up, but leaves the delimiter and
doing an
> > unload added a decimal place to the SUM and COUNT aggregate functions
in my
> > sql statement, so after unloading, I run this....
> >
> > beautify-unl.sh <unload-file> | tr '|' '\t' | sed "s/\.0//g"
> >
> > I'm a bit curious as to why doing an unload causes 1 decimal place to
be
> > displayed, especially since I'm summing integers, and count should
never
> > return anything but an integer, but that's trivial.
> >
> > -----Original Message-----
> > From: ERIEZNIKR@REPSOLYPF.COM [mailto:ERIEZNIKR@REPSOLYPF.COM]
> > Sent: Tuesday, April 26, 2005 1:03 PM
> > To: dwright@sherwoodfoods.com; ids@iiug.org
> > Subject: RE: dbaccess output display width from cron [4812]
> >
> > Agree with Jean
> >
> > Consider Perl report features.
> > Unload to file (unload to foo.bar select ....) then feed your perl
report
> > script. If you need some example on this, just ask!
> >
> > Or remove innecesary fields :-)
> >
> > All the best.
> >
> > -----Mensaje original-----
> > De: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] En
nombre
> > de Danny Wright Enviado el: Martes, 26 de Abril de 2005 01:06 p.m.
> > Para: ids@iiug.org
> > Asunto: dbaccess output display width from cron [4812]
> >
> > I set up a little shell script to run an sql script via dbaccess and
mail
> > the results out to a few people.
> >
> > When run from the command line, the output comes out with columns
displayed
> > horizontally.
> >
> > it looks something like this:
> >
> > column1 column2 column3 etc.....
> >
> > data data data..........
> >
> > But when run from cron (or at), it displays like this:
> >
> > column1 data
> > column2 data
> > column3 data
> >
> > How can I convince it that my display is wide enough to handle
displaying
> > the data horizontally?
> >
> > Even though I'm setting my environment the same way I would when I log
in,
> > it seems to recognize that it's not a tty

Messages In This Thread

• dbaccess output display width from cron
  Danny Wright -- Tuesday, 26 April 2005, at 12:05 p.m.
  • Re: dbaccess output display width from cron
    Jean Sagi -- Tuesday, 26 April 2005, at 12:26 p.m.
    • RE: dbaccess output display width from cron
      Joe Vidrine -- Tuesday, 26 April 2005, at 2:39 p.m.
      • RE: dbaccess output display width from cron
        Tomchik, Kate -- Tuesday, 26 April 2005, at 4:18 p.m.
        • Re: RE: dbaccess output display width from cron
          Jean Sagi -- Tuesday, 26 April 2005, at 4:58 p.m.
        • RE: dbaccess output display width from cron
          Jonathan Leffler -- Wednesday, 27 April 2005, at 12:33 a.m.
  • Re: dbaccess output display width from cron
    Marco Greco -- Tuesday, 26 April 2005, at 2:52 p.m.
  • RE: dbaccess output display width from cron
    ERIEZNIKR@REPSOLYPF.COM -- Tuesday, 26 April 2005, at 4:08 p.m.
  • RE: dbaccess output display width from cron
    Danny Wright -- Tuesday, 26 April 2005, at 4:37 p.m.
    • Re: RE: dbaccess output display width from cron
      Jean Sagi -- Tuesday, 26 April 2005, at 7:10 p.m.
    • RE: dbaccess output display width from cron
      Danny Wright -- Wednesday, 27 April 2005, at 6:25 p.m.
      • RE: dbaccess output display width from cron
        Jonathan Leffler -- Thursday, 28 April 2005, at 1:00 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.