On Wed, 9 Apr 2003 13:31:47 -0500
"Ochs, Duane" <Duane.Ochs AT QG DOT COM> wrote:

> Here is the response from IBM. TSM commands from CRON are not
> supported. Sucks for me, but it has worked for over 2 years... That is
> until I upgraded to 5.1.6.2 .
>
> Normally IBM TSM support does not support TSM commands run from cron,
> however it is suggested that the following tsm envirnment variables be
> used in a script that runs tsm commands from cron:
>
> export DSM_DIR=<PATH_TO_dsm.sys>
> export DSM_LOG=<PATH_TO_DSM_LOG>
> export DSM_CONFIG=<PATH_TO_dsm.opt>
>
> If the above don't clear the "sessions stay open" problem that you are
> seeing, you will have to define a TSM schedule to gather the
> information you need to gather everyday.
>


If command entered from your normal working environment do work, but not
from cron, you may have many problems. My bet would be that there is one
major difference in the environment, like

1- shell
2- enviroment vars set in you environment but not in the env of the user
that owns the cron job (you vs. root maybe?)


1) is fixed by starting your script with the propper #!/bin/<shell> line
or setting the SHELL environment var in your crontab file, in all other
cases, you get the shell from your /etc/passwd entry
2) is fixed by explicitly setting all env vars to the desired value in
your script
dont forget, cron usually gives you init's environment, so you mey be
missing on things from /etc/environment (or friends) or your .profile

>
> >  -----Original Message-----
> > From:         Ochs, Duane
> > Sent: Wednesday, April 09, 2003 9:32 AM
> > To:   ADSM-L@VM. MARIST. EDU (E-mail)
> > Subject:      tsmservers: q actlog ...
> >
> > Since upgrading to 5.1.6.2 server on AIX I have seen that the
> > sessions that are created during this process do not release at
> > times. The only way I have been able to get rid of them is by
> > stopping the TSM server software and restarting.
> >
> > I use a cron job to do the following:
> > dsmadmc -id= -pass= -commadelimited -outfile=/usr/actlog_q.txt
> > -display=table 'tsmservers: q actlog begindate=today-1
> > begintime=07:00 enddate=today endtime=07:00 search=ane49??i'
> >
> > dsmadmc -id= -pass= -outfile=/usr/stats.rpt 'tsmservers: q event * *
> > begindate=today-1 begintime=07:00 enddate=today endtime=07:00'
> >
> > I then parse the contents to create reports on number of files,data
> > sent, etc...
> >
> > Has anyone else seen this behaviour or come across a solution for it
> > ?
> >
> >  Duane Ochs
> > Systems Administration
> > Quad/Graphics Inc.
> > 414.566.2375
> >