DSXchange

However, multi-statement blocks are not available in expressions; indeed no form of statement is available in an expression. Alright, so that clears it as far complex derivation is concerned in a single expression cell. Disappointing but that's what it is. I continue to maintain that your example c...

No, complex expressions are OK in DataStage BASIC But routines written in BASIC are not available in parallel jobs, except with BASIC Transformer and we already discussed that I believe. However, in a derivation expression things are different. You're right that you cannot assign work variables (us...

Hi all, In a transformer stage, is there a way to get the input field name as well as its value dynamically? For example, in a stage variable, using a custom routine, I could do something like this: myStageVar = myCustomRoutine(inputLinkFieldName, inputFieldNameValue) Is this something that's possib...

Maybe I can surf on this thread as "complex derivation" had an exact match to what I was looking for. My guess is that by complex derivation, the OP was thinking about when, for a single output field, you could have multiple lines of codes, including assigning variables to end up with a fi...

I seem to recall you were thrown directly into the deep end of the pool? Meaning, self-learning from the documentation, experimentation and silly places like this? Anyway, not sure how far you want to take this. Any interest in pursuing the Server job and USERSTATUS solution? Or have we beaten this...

It is certainly a possibility and if fact, when I started working with the product and looking for a solution to this problem, the server job "userstatus" was the answer. However, reading further on this forum and also in official documents on the products, I read that mixing server jobs w...

Yes, the info is taken from a table then in the job, I append two files with the info: First file is a parameter set value file and the second file contains only the value, all done in part via the transformer stage loop condition. So my PS value file looks like this: name1=value1 name2=value2 name3...

Nowadays you should be looking into Parameter Sets, specifically with the concept of Value Files they added a number of years ago. Did we have this conversation already? :wink: Indeed we did. But here's an example where I believe parameter sets and value files won't work: Notification activity stag...

It all goes back to my first inquiry on passing info from job to job in a sequence. I find the whole process extremely convoluted with Datastage: Write file with info needed for next job Read file with execute command stage Convert @FM in $CommandOutput Use Field function to get value needed for nex...

User chulett wrote this at one point: Another option, since the results are returned in a dynamic array, is to use array notation. That can help simplify things if you ever need to return something other than the first item in a list of returned values. Execute_Command_1.$CommandOutput<1> Can somebo...

And you can always inline the Field function to get the value in your example: Field(Field($CommandOutput,'|',1,1),'=',2,1) Forgive me if the syntax isn't exactly correct, working from memory here, but you basically take the first field from a pipe delimited string and then from that take the secon...

Unless I missing something, I don't see a need to play any Execute Command games with the values file. Chullet, The goal of doing this is to not have to use "UserStatus" from a job to trigger another job in the sequence. I read on the forums that it's not recommended anymore since the app...

Gents, another question on the subject if I may. If I read the parameter set value file with an "Execute Command" stage in the sequence in order to use a value to start another job activity, how do you deal with the trigger? Let's say my parameter set value file contains this: param1=ABC p...

Well, I fixed the compilation problem. Apparently, I misinterpreted how to use parameter set value files. I thought that the value file was where I put the parameters and that each value file could have different parameters. Looks like I have to add the parameters in the parameter set and all value ...

Ray, It is PS_1.param1, it's a typo on my part in the original post. I'll fix the post. As for PS_1 set, it is added in the sequence and jobs as well already. So why the compile error? The sequence will know the name of the value file only when it's passed as a parameter with dsjob since it looks I ...