Datastage Scheduler - Extra

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Datastage Scheduler - Extra

Post by admin »

This is a topic for an orphaned message.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

Seema,

Thought of another test:
On the server:
- open a CMD shell
- Enter the Command that you were going to schedule
Because it appears as though the Command Not the Schedule is Failing.

If you have success as yourself
Then you can try as The DataStage User.


Thanks Jack

----- Original Message -----
From: "Jack Luchjenbroers"
To:
Sent: Monday, December 04, 2000 8:46 PM
Subject: Re: Datastage Scheduler


> Seema,
>
> Have you tried testing the other way:
> - Logging on to DataStage as the user account(Administrator)
> - Bearing in mind that the first time login as a New user it is
> a good idea to use the DomainName as well as the user Id.
> ie DomainName /User Id
> (not sure of the direction of the / and my other one doesnt work
> on this keeboard.
> - If your user is local to this machine then the DomainName is
> proberly
your
> Machine Name.
>
>
> Thanks Jack
> ----- Original Message -----
> From: "Seema Ranchoddas"
> To:
> Sent: Monday, December 04, 2000 8:21 PM
> Subject: Fw: Datastage Scheduler
>
>
> > I had already set the Schedule Service to start automatically for a
> > user account(Administrator). I tried the Test.cmd and it works. I
> > have also
> tried
> > creating another user and setting the schedule service to start
> > automatically for that user account, logged on as that user and
> > tried scheduling the job in Datastage. The job still didnt run.
> >
> > Any more ideas??
> >
> > Seema
> >
> >
> > >
> > >----- Original Message -----
> > >From: "Jack Luchjenbroers"
> > >To:
> > >Sent: 04 December 2000 10:45
> > >Subject: Re: Datastage Scheduler
> > >
> > >
> > >> Seema,
> > >>
> > >> You should check the follwing things:
> > >> - Check to see how the Schedule Service Logs On
> > >> - Create a simple CMD file ie
> > >> C:/temp/Test.cmd
> > >> Echo Test > C:/temp/trace.txt
> > >> - At 18:13 C:/temp/test.cmd
> > >> - If the above works you may need to have your schedule service
> > >> log
on
> as
> > >a
> > >> Specific User
> > >> and allocate that user the required Privledges.
> > >>
> > >> Jack
> >
>
Locked