DSXchange

Hi Janos, I don't think I can help, because I can't see anything wrong with your code. Are you sure the parameter set is set up correctly? Can you see the values in it from a normal DataStage job? What does it say in the log when you execute the routine from a job? Are there any warnings? If it abor...

I have a routine to add days, months or years to a date, which correctly handles month end dates (for instance 28/02 + 1 month = 31/03). It will obviously need tweaking to subtract dates, but the principle is there. If you are interested send me a personal email address and I'll send you the DataBas...

Thanks Ankur and Craig, my syntax was indeed wrong: psPasswords = DSGetParamInfo (DSJ.ME, "psPasswords", DSJ.PARAMVALUE) should have been: DB_Password = DSGetParamInfo (DSJ.ME, "psPasswords.IPSS_Password_Parm", DSJ.PARAMVALUE) This now works - case closed - thanks again.

I am trying to pick up the value of an encrypted password from a parameter set by using the DSGetParamInfo command within a routine. Unfortunately all this does is return: psPasswords=(As pre-defined). The "(As pre-defined)" is as shown in the job control => parameters window, not the valu...

Hi all, just to say thanks for your input - much appreciated.

Jean

Correct, without using the Basic Transformer...

In good old Server Edition, in the derivation of a transformer stage, you just did an OCONV using the MCT conversion To Produce Text With First Letter Capitalisation.

Anyone know of a nice simple way of doing this in Enterprise Edition?

No it's not necessary, job will compile and run with null parameter defaults.

For even greater flexibility you can put data into a hash file or files and then write a pre- or post-transform routine to open the file(s) and merge the data, if necessary into a completely different field (column) format! Just make sure you have sensible key fields.

There is a routine around which will let you set a parameter value from within a transform by having the following derivation: RoutineName(in.ParameterName:"={Parameter value}") or RoutineName("{ParameterName}={Parameter value}") or RoutineName("{ParameterName}=":StageV...

No, the jobs are not automated, though can obviously be scheduled. The Metrics job has the following parameters: CATEGORY: Enter one or more categories here PATH: Full path name to output csv file directory FNAME: Output CSV file name The Monitor Details job has the following parameters: CATEGORY: E...

I have written two DataStage jobs that reproduce the Director log, and also the same details as shown in the Monitor window. Both of these are saved to CSV files on the Server. The files can then be FTP'd or whatever onto your PC. Here are examples of the output: http://i172.photobucket.com/albums/w...

Designer: if trying to open a job that is locked do NOT go to the window to open another job, simply show a message stating the job is locked.

In very large projects it is possible to wait for ages for the window to open another job to appear. And I have never used the resulting OPEN option!!

Designer: 'Deselect ALL' option in Column Display window when doing a View Data on a file stage

Thanks ArndW. I have already cleared the file so we could continue. I really only posted this out of interest.