Yiannakis -

As you've discovered, an interactive session and a scheduled process
are two very different things.

When first implementing a schedule, give it a basic try first by
setting SCHEDMODe PRompted in your client, and then use DEFine
CLIENTAction on the server to kick off a basic OS Command, such as
reporting the date/time.  This will assure that the overall mechanism
is functional.  Then you can set SCHEDMODe as needed for real and do
the DEFine SCHedule.  And don't forget DEFine ASSOCiation.

If you still have problems, refer to the Problem Determination Guide,
which contains a section on pursuing scheduler problems.  Key to
resolution is inspection of the schedule log and the dsmerror.log.
Details therein may then be posted on this mailing list if you're
stumped.  Remember that PRESchedulecmd and POSTSchedulecmd functions
which a site may add to its scheduler regimen can easily foul up a
schedule if misconstructed.

   Richard Sims

On Apr 5, 2006, at 6:24 AM, Yiannakis Vakis wrote:

Hi,
We have installed the client products on an AIX and a Linux server.
We have
followed all the necessary installation steps and we believe
evrything went
ok.
Then we logged in the TSM server and the connection was accepted
since I
queried the schedule and TSM replied back. So I'm sure that the
installation
went well.
Then we tried to set up a schedule. We created a schedule that runs
a script
(something that is done for several other windows servers) and run the
scheduler. We see that the scheduler runs as a service (using the
ps -ef
command). We have the PASSWORDACCESS GENERATE in the dsm.sys.

HOWEVER, THE SCHEDULE IS AT THE PENDING STATE!!!

TSM Server is 5.2 under Windows 2000
Client for Linux is at 5.3 under Linux Red Hat 4.2
Client for AIX is at 5.2 under AIX 4.3

Any suggestions?