Cannot see jobs in Datastage Director using a Operator user

arthur_li · Post by **arthur_li** » Mon Mar 05, 2007 3:01 pm

I have recently installed Datastage 7.5.2 on a Windows 2003 server. All jobs are running properly and server seems okay except for one problem:

When logging in as an Operator user in DS Director, only the left panel which shows the high-level view of the project and folders is available. When clicking on the folder itself, no jobs appear on the right panel.

The strange thing is that when logging in as a DS Production Manager or DS Developer user, the DS Director works correctly showing the folders and the jobs. This only happens when logging in as a DS Director user.

The DS Operator user was setup in a separate Windows User group on the server and assigned the DS Operator role through DS Administrator.

The DS Operator user has full read, write, execute permissions on the DS Server.

chulett · Post by **chulett** » Mon Mar 05, 2007 3:05 pm

Welcome aboard. :D

That's the way it works. For some reason known only to The Builders, an Operator can only see released jobs - something very few (if any) peoples do any more.

Rather than using the Operator role, you'd be better off setting up Production as a Protected project.

ray.wurlod · Post by **ray.wurlod** » Mon Mar 05, 2007 3:06 pm

Welcome aboard. :D

There's a check box in the Administrator client Permissions tab for "operator can see full logs". Did you check that?

chulett · Post by **chulett** » Mon Mar 05, 2007 3:07 pm

Really?... rushes off to check...

arthur_li · Post by **arthur_li** » Mon Mar 05, 2007 3:10 pm

chulett wrote:Welcome aboard. :D

That's the way it works. For some reason known only to The Builders, an Operator can only see released jobs - something very few (if any) peoples do any more.

Rather than using the Operator role, you'd be better off setting up Production as a Protected project.

Thanks! So Operators cannot see any jobs until they are released? What does that mean by 'released job'? How do I go about releasing a job so that is available to a DS Operator?

chulett · Post by **chulett** » Mon Mar 05, 2007 3:11 pm

It is checked by default... and doesn't really seem to be related to the topic.

arthur_li · Post by **arthur_li** » Mon Mar 05, 2007 3:11 pm

ray.wurlod wrote:Welcome aboard. :D

There's a check box in the Administrator client Permissions tab for "operator can see full logs". Did you check that? ...

Yes, that has been checked as the default... I still can't see the jobs though...

chulett · Post by **chulett** » Mon Mar 05, 2007 3:17 pm

arthur_li wrote:Thanks! So Operators cannot see any jobs until they are released? What does that mean by 'released job'? How do I go about releasing a job so that is available to a DS Operator?

Trust me, you really don't want to know.

Tell us instead why you setup the Operator role for some folks. If it is for the normal reasons, then you really should look into either Protecting your target projects or using Version Control for promotions, which will make your jobs 'Read Only' outside of dev.

arthur_li · Post by **arthur_li** » Mon Mar 05, 2007 3:22 pm

chulett wrote:
arthur_li wrote:Thanks! So Operators cannot see any jobs until they are released? What does that mean by 'released job'? How do I go about releasing a job so that is available to a DS Operator?

Trust me, you really don't want to know.

Tell us instead why you setup the Operator role for some folks. If it is for the normal reasons, then you really should look into either Protecting your target projects or using Version Control for promotions, which will make your jobs 'Read Only' outside of dev.

Figured out how to release a job... the client asked to have Operator role created... I recommended using a protected project also, but they would like to see this DS Operator user option work at least

chulett · Post by **chulett** » Mon Mar 05, 2007 3:26 pm

Yuck. Sequence jobs will be an issue if you release jobs. Lack of design time information will be an issue if you release jobs. The extra work for no good reason will be an issue if you release jobs.

Push back.

arthur_li · Post by **arthur_li** » Mon Mar 05, 2007 3:45 pm

chulett wrote:Yuck. Sequence jobs will be an issue if you release jobs. Lack of design time information will be an issue if you release jobs. The extra work for no good reason will be an issue if you release jobs.

Push back.

Oh, interesting... what happens to sequence jobs when they are released? I noticed that the jobs are renamed also...

I've tried to push back about the Operator role... it's something the client would really like to see happen.

Most likely they will switch to protected projects afterwards, I recommended they not setup any developer or operator user on the server actually, since it is a Production server, I don't believe anyone should have access except for the DS Production Manager user. The reason they're setting up these Operator and Developer roles is because they want to do some testing on the permissions.... hopefully they remove all these extra users later on.

Thanks for all the help!

chulett · Post by **chulett** » Mon Mar 05, 2007 4:33 pm

I haven't release a job since Version Control was available for the 4.x release of DataStage. Which was well before any such thing as a Sequence job existed. So, I'm taking other's word here (based on fairly recent conversations) that Sequence jobs must be changed to reflect every release of a job that they run.

Releasing a job adds a release suffix to them, such that JobA becomes:

JobA%reln.n.n

Where the last 'n' will increment each time. You then allegedly need to change any Sequence job that needs to run these to use the full 'fixed job release' name as it is known each time any job they control is changed and a new released version is created.

Back in the Old Days, when we wrote our own job control, you could just run the 'base name' of the job and it was smart enough to find the highest released version and automatically run that. I'm told that's no longer the case with Sequence jobs but haven't verified that myself. YMMV.

ray.wurlod · Post by **ray.wurlod** » Mon Mar 05, 2007 5:03 pm

I can't see why the base name alone wouldn't work from a job sequence or from dsjob, but also have not tested it. Released jobs... shudder!!

ray.wurlod · Post by **ray.wurlod** » Mon Mar 05, 2007 5:04 pm

Anyway, there's nothing to stop you complying with their request to create an Operator role.

That it can't do anything is not your fault once you've explained the ramifications.