That sucks, Don't support cron jobs huh? Guess I'm not really surprised
about that...
      We run alot of stuff via Control-M, which is similiar in nature to
cron (It just has alot more features) and we have no problems with 5.1.6.3.
Do you have your cron setup run the dsmc command directly (as root) or do
you do a su - <user> -c <command>. The environment that cron supplies the
commands it runs is not the full profile of the user and that has sometimes
caused me problems before. I also have a few things running via cron, but I
use the su - <user>  -c <command> method to ensure a full environment for
my command to run in (It's a korn shell script).

Best of luck.

Jonathan Kaufman

Foot Locker Inc.
E-Mail: jkaufman AT footlocker DOT com





                                               To:      ADSM-L AT VM.MARIST DOT 
EDU
                                               cc:
                        "Ochs, Duane"          Subject: Re: tsmservers: q 
actlog ...
                        <Duane.Ochs@QG.
                        COM>
                        Sent by: "ADSM:
                        Dist Stor
                        Manager"
                        <ADSM-L AT VM DOT MARI
                        ST.EDU>


                        04/09/2003
                        01:31 PM
                        Please respond
                        to "ADSM: Dist
                        Stor Manager"







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.


>  -----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
>