DSXchange

Sakthi_Sst wrote:The issue is resolved at last ,my userid did not have execute permissions in " AT " utility.

The very first response you got here asked you to check that.

Because you don't. And there's nothing 'wrong' about it. You get the DataStage internal representation of that date, which is the number of days past some date I don't recall off the top of my head. Don't worry about it. What happens when you convert 03307 to internal format using the 'J' code and t...

The picture doesn't help at all except, as Kumar notes, to let us know which stage is 'Package3_2'. Confirm again. Your user-defined sql does not conform to the rules needed for execution in an OCI stage. Every column in the stage must be bound into the query. Key fields must be used in the where cl...

Did you put the 'mv' part in the Command section and the '#filepath#/#OldFile# #filepath#/#NewFile#' in the Parameters section? Double-checked the spelling and case of each parameter name?

What does the log entry show for the stage when the job runs? Cut-and-paste, please no hand typing.

No, but feel free to write one if you like.

If all you need to do is check that any field you know is a number has a decimal point in it, then using the Index function would seem to me to be one easy way to do it. Routine or not.

That could be one assumption as to why they think they need that many projects... however, the OP has not explained the 'why' of the 'what' yet.

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

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.

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

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

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

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.

From $DSHOME, step #6 would actually be:

6 -> ./bin/uv -admin -stop

And some Operating Systems require dsadm to be in the 'root' group, but most don't. I think Tru64 may be the only one? It would be in the Install Guide.

And yes, we need that many projects (99) in our dev environment! I be surprised if 'need' is the right word. You may very well have chosen to use that many projects, but 'need'? I'd be really, really (really) curious how you are using your projects that results in the need for so many of them. Seri...

DSguru2B wrote:Thats the User Limit Craig.

Well, that may also be the User Limit for some... here it is 22. I'm referring to the old Ascential paper Authorizations that one used to get. Not in the office so can't back up what I'm saying right now.

Still don't think there's a limit, per se.