DSXchange

Hi, Guru

We consider to take advantage of TFS as our datastage version control repository.

Does any one have experience to use TFS as datastage version control? is there an instruction how to install TFS plugin in IS Manager?

Any reply will be much appreciated.

thanks in advance

xli

Yes, I did, but no help

Yes, I deleted this empty folder from Designer with no problem, but it still shows in Director, and it hang while I tried to open it.

any advise?

xli

Hi, guru A job folder which contains a number of PX jobs cannot be opened in Director. however, I can still open it under Designer. After I deleted all PX jobs successfully, I tried to open it in Director, it prompty a few message such as : Cannot find job job1 Cannot find job job2 ...... I found th...

Yes, exactly what I presumed

It has been resolved by asking my admin to grant me suitable permissions to all files and folds under c:\IBM

Thanks for all your comments

Regards

xli

Hi, I have installed Information Server ver8.0.1 on solaris 9, client softwares on Windows XP. Now, I am trying to logon IS console to configure settings by using suite administator user, it failed login along with error : IBM.Mozart.Platform.UserAuthenticationException: Unknown ---> com.ascential.a...

It is supplied as part of the standard install. However, it sounds like someone has futzed around and created a 'User Defined' version of it as well, seemingly with the same name - not exactly what I would call a Best Practice. :? Hmmm, I don't think there is someone creating a user defined ExecSH ...

confused, as I said, I can see both DSU.ExecSH and DSX .EXECSH in a new project.

Then, is ExecSH a DataStage supplied one or user supplied one ? I have thought of it as DataStage supplied. Actually, I can only see ExecSH in the Routine folder, no EXECSH.


xli

One more question : I found another records in VOC file : DSX .EXECSH 001 V 002 DSG_BP.O/ExecSH.B 003 B 004 BN 009 DSG_BP.O Compared with the record I created : DSU .ExecSH 001 V 002 DSU_BP.O/DSU.ExecSH 003 B 004 BN 009 DSU_BP.O Seems they are pointing to the same routine ExecSH. why are there two r...

Great, it works now !

Many thanks to Ray and ArndW for your help.


xli

Thanks, Ray Now I have added ExecSH record in VOC file : DSU.ExecSH 001 V 002 DSU_BP.O/DSU.ExecSH 003 B 004 BN 009 DSU_BP.O While I ran the test job, I got another error message : before-job routine returned error: Cataloged routine DSU.ExecSH - unable to open object DSU_BP.O/DSU.ExecSH how to fix t...

Hi, Ray we are using version7.1.5A, lots of projects reside on this server, only proj A has this problem. ExecSH is original built-in routine and read-only. there is not a DEFFUN declaring ExecSH as calling "DSU.ExecSH". basically, I don't think there is a user-written version in this proj...

Look at the VOC entry for ExecSH both in the project where it does not work and in one where it does. LIST.ITEM VOC WITH @ID LIKE "...ExecSH..." In proj A (ExecSH does not work) no entry return !! In proj B (ExecSH works) DSU.ExecSH 001 V 002 DSU_BP.O/DSU.ExecSH 003 B 004 BN 009 DSU_BP.O ...

Hi, All I have got the following error message : before-job routine returned error: DSU.ExecSH is not cataloged. ExecSH is actually a built-in routine. rather than user defined. I made a copy of ExecSH, eg ExecSH1, ExecSH1 works fine. I tried to rebuild index, but not help. I wonder if anybody encou...

Looks to me like your scheduler (AutoSys) is changing the PATH environment variable to suit its own purposes - putting itself up front. DataStage jobs pick theirs up from the dsenv script. For whatever reason (primarily because AutoSys works via dsjob command) the PATH environment variable is not b...