Buttons disabled like Scheduled, Mainframe, Parallel, Remote

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
drostnu
Participant
Posts: 26
Joined: Tue Jul 18, 2006 4:17 pm

Buttons disabled like Scheduled, Mainframe, Parallel, Remote

Post by drostnu »

I'm using Datastage 7.5.2 running in linux, installed it with 'dsadm' user wich is how it should be, but i login into Datastage Administrator, some TABS are disabled which is very weird since in windows they are not.

here's a picture

Image

and also to this and i'm not beeing able to schedule a job, it think that its because the schedule tab is blocked out.

please any help would be appreciated.

regards,

diego.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Schedule is disabled because you are not logged in as dsadm or root or because you are not connected to a Windows-based server.

Mainframe is disabled because you do not have a licence for mainframe jobs.

Parallel is disabled because you do not have a licence for parallel jobs or, if you do, because you are not logged in as dsadm or root.

Remote is disabled because you do not have a licence for parallel jobs and therefore can not execute them remotely.

But you can invoke Help to find out what they do. Just press F1 while on this screen.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
shilpa79
Participant
Posts: 131
Joined: Thu Jan 20, 2005 5:59 pm
Location: Virginia

Re: Buttons disabled like Scheduled, Mainframe, Parallel, Re

Post by shilpa79 »

Admin will have all rights use those tabs.

you can schedule your jobs from director :
Go to director ---> Tools--->Add to schedule
Last edited by shilpa79 on Wed Nov 08, 2006 5:21 pm, edited 2 times in total.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The Schedule tab in Administrator does not schedule jobs. Rather it sets up a Windows user ID under which scheduled jobs will be executed (by AT) and allows the user ID/password combination for that user ID to be tested.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
drostnu
Participant
Posts: 26
Joined: Tue Jul 18, 2006 4:17 pm

DSADM is the user

Post by drostnu »

dsadm is the admin user, i installed the ds server with that user, how come, is not able.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Not if you don't have a licence or the right operating system for that piece.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
drostnu
Participant
Posts: 26
Joined: Tue Jul 18, 2006 4:17 pm

ohh

Post by drostnu »

okay i see, thank you!
ill check other things

Thanks
drostnu
Participant
Posts: 26
Joined: Tue Jul 18, 2006 4:17 pm

Post by drostnu »

problem solved.

talking to the usa support, they told me this.


" When using the DataStage Director to schedule a job to run on a UNIX
server, the Every option is available only with a single day of the week or
month (it is not possible to use it with multiple days within a week or
month).
The DataStage server uses a combination of the UNIX at and cron system
commands to provide flexible job scheduling. A scheduled job runs under
the user name of the connected Director client session that scheduled the
job. You must ensure that any DataStage operators who need to schedule
jobs have adequate permissions to invoke the at and cron commands. See
your UNIX documentation for details of how to do this.
The cron command does not set environment variables for the jobs that it
runs. Therefore some DataStage jobs, particularly those whose components
use third-party software, may not run. If this is the case, you may
need to manually edit the crontab entry to set the required environment
variables."

So, the only thing it works it to put EVERY.

Regards,

diego-.
Post Reply