DSXchange

Thanks, Susan. Yes, I should have added that I needed to find the info = whether or not the job had been compiled in the interim. I also sought to alert the list to the fact that DSJ.LOGSTARTED returns = other than "starting" events. ----- Original Message ----- From: "Susan McNally" Date: Wed, 9 Oc...

Another way to get parameter values for the last run of a job is to use the DSGetParamInfo function with an InfoType of DSJ.PARAMVALUE. This only works if the job hasnt been compiled since it last ran. Susan www.altis.com.au -----Original Message----- From: Ray Wurlod [mailto:rayw@mindless.com] Sent...

This function appears to return the most recent Control event, whether its Started, Finished or Log Purged. I needed to find the most recent Start event, and extract the parameter values that were recorded therein (ultimately so as to reset the job with those parameters). To achieve this, I used an ...

Hi Leonie, Have you tryed with DS.TOOLS?? You can run this command by connecting to the server via telnet or by command option in Administrator (connected by dsadm/Administrator/root user). You will be able to unlock any process. The sequence of the step as you use the DS.TOOLS is: 5. Administer pro...

Hi Leonie, I work in Compaq 5r2 and I think you will have somthing similar on your sever. You can clear the locks of the job in universe or by Director (cleanup resources) ( I have never do it by this last way). In Universe: > LOGTO Project > DS.TOOLS DataStage Tools Menu 1. Report on project licens...

Search the oliver archives at tools4datastage.com Job locks and releasing them is covered many times with various solutions. Good luck! -Ken --- Leonie Bruwer wrote: > Hi Everyone > > Say I loose my client connection due to network > down, or whatever. Now to > the server my client connection is sti...

Hi Everyone Say I loose my client connection due to network down, or whatever. Now to the server my client connection is still active and that would mean you cant access the job ("job accessed by another user"). If you set the timeout option to never timeout it will never release that job unless you...

I believe that as at DS5.2 (for Unix), umask is no longer set in the dsenv file. The file that it needs to be set in differs depending on the Unix flavour. Eg, for Solaris, umask is set in /etc/rc2.d/S99ds.rc. See either the DS Installation or Administrator Guide for more details. Chris. www.altis.c...

Has anyone had any experience with setting project level permissions (in the Administrator) in Datastage 5.1 based on NT userids? Regardless of what permissions I set, all users can access all projects. Is there something were missing in what seems like a straight-forward setup? Thanks! Lindi and John

There are a few using this configuration ! ----- Original Message ----- From: To: Sent: Monday, October 07, 2002 3:49 PM Subject: Re: logging in > > If I recall correctly, the dsadm user id should be set up with a group > dsadm. The redbrick user id would need to be in this group, as well. > > Were ...

This sounds like a permissions issue, in the administrator you can determine which user groups can develop and run jobs. However if the user redbrick is in an appropriate group then it could that the file permissions at the UNIX file level have been set incorrectly. You should have the umask set to ...

If I recall correctly, the dsadm user id should be set up with a group dsadm. The redbrick user id would need to be in this group, as well. Were also using DataStage 5.2 for Red Brick 6.11. Its good to know that theres at least one other similar implementation out there! Denzil Sander cc: Subject: l...

Hi all Im running datastage 5.2r1 on unix. I want to create a job using a different user than dsadm (the user i normally use to create jobs). The user redbrick exists on the unix server. But, when i try connect with the redbrick user, i get an error telling me to check whether the project is set up ...

I will be out of the office starting 10/03/2002 and will not return until 10/09/2002.

I will respond to your message when I return.

Based on my own experience I would have to disagree, particularly if DataStage server is on a single CPU Windows platform. In this case the Monitor client (and the Director log view suffers from this too) are seen as "uvcs" (interactive) processes, and appear to get higher priority (by default) on t...