DSXchange

Roy I'm not familar with log agents - are you saying that we can write Director Log information to an ascii file ? If this is possible then I might be able to write this to a file remotely on a server that can be easily accessed (FTP Activity perhaps or remote shell ?) If so how do I write the infor...

Craig

If you mean access to the UAT and Production servers then I guess it will be physically controlled by access to the UNIX servers. Looks like I'm going to have to play the game unless someone knows a way of getting the same information out as is sent to the Director Logs.

Roy

I know we use autosys and I think Tivoli plays a part for monitoring failed processes but I'm not sure about that. Access to UAT and Production Director logs is definitely not an option.

I was told that Job Sequences weren't supported so I challenged that asking why. The response I got is below - hopefully it is just a matter for me to find out what my options are and inform them :- The reason that I initially made that statement (i.e Job Sequences not supported") was based on ...

I am wondering what options exist, when running Job Sequences, to get failure information regarding the underlying Server Jobs. Assuming that I have no access to Director on UAT and Production servers what other options do I have ? I know that if using dsjob then there is a "-logdetail" th...

Seems you may have sorted your problems but here's my findings re the sybase stored procedures. Sybase Procedures are supported in version 7.5.1 - this is the only reason that we upgraded to this version. I haven't found any documentation on these but the online help with a bit of trial and error we...

I had a go at using @USER0 and couldn't see how it would work in one of the cases that I have. The data being passed back currently via Ans is of the format ABCD#01 Jan 1990#31 Jan 1990#,XYZA#01 Feb 1990#28 Feb 1990# and so on. The Ans (ReturnValue) is comma delimited and each record is made up of 3...

Thanks for the repsonse Craig I have 'automatically handle failures' turned off otherwise the job sequence does fail - I'll try adding a failure link on the trigger conditions on the Routine. I've not got as far as thinking about monitoring the running of the job sequences in terms of Tivoli/Patrol ...

I'm not sure if this is a problem or not but I guess this thread will confirm if it is. I have a job sequence with several server jobs activities tagged together - after one of the server jobs I have a Routine which I have defined as a Transform Function. The Routine opens a sequential file and crea...

thanks very much for the answer - it's sort of what I expected to hear but just needed clarification from one of the experts.

As far as I can see there seems to be two methods for releasing code :- (1) In DataStage Manager whole projects or components can be exported as .dsx files via either DataStage Components or Executable Jobs from under the Export menu. (2) Reading through the documentation for the DataStage Version C...

Thanks for the feedback guys but ODBC in my case is just too slow. The database set is optimised - my main skill is Performance & Tuning with Sybase/SQL Server so hopefully I know what I'm doing when these things get set up :) . The main problem in my case is that the DataStage Server is based i...

thanks guys - that's the pointer I needed. Client software now installed and sifting through the .pdf document.

I've been trying to get a handle on version control within DataStage and need some pointers in a few areas. I have saved all of my server jobs and controlling job sequence with the default revision 50.0.0 in the job properties. When I create a releasable .dsx I guess that this will automatically cha...

I've just binned the idea of using the ODBC stage for MSSQL Server as it is painfully slow. I was getting an insert rate of 7 rows per second which for thousands of rows is not a non-starter. Unfortunately there is no bcp or import stage within DataStage for MSSQL Server and breaking out to unix is ...