DSXchange

Is there only one record in the file? Then 'reading' it might be as simple as using an Execute Command stage to cat the file to standard out and then you would need to capture the $CommandOutput from the stage to send to the parameter, something the Sequence job would automate for you.

That would typically be handled via a Sequence job and there are a handful of current topics on that subject over in the General forum. This one as one example, there should be plenty more. Basically you need something to 'read' the file and then pass the result to the Job Parameter in the Job Activ...

We just went through an acquisition of Control-M, you'd have to be willing to pay a goodly amount for the "and more" part.

ep_datastage wrote:But the SEQ jobs should only run if the date/time values from the control table meet the run criteria.

Thanks. Can you clarify what 'meet the run criteria' means? I could make an assumption but I'd really rather not.

Was hoping for something more... detailed. So the 'values' are job names? Is there more to it than that, like a time to run it or is that literally all that is in the file? The more details you provide, the quicker we can get to an actual answer / solution.

There's no such thing out of the box but that doesn't mean you couldn't cobble something together. What kind of 'values' are in this table?

I tried to read the same XML file using External Source Stage and the file got parsed properly and data got loaded into the Seq file. So, it means that the XML file is correct and it conforms with the XSD Actually no, no it doesn't. Post your XML file or at least a representative snippet from its h...

You clicked on it where? In what stage? Sounds like there was nothing connected 'upstream' from there. I meant for you to do it from the appropriate job parameter property in the Job Activity stage so it can help you pick what to put there. Pass the exit code directly to the parameter that needs it ...

So... resolved?

While you wait, contact support if you haven't done so already. Not sure how much Data Masking experience there is out there in the wild...

Yes, please - use your words, don't make people puzzle out your requirement from a made up example.

You don't put parameters "within the stages themselves", all you need to do is add Job Parameter(s) to the job itself and then they will show up in the Job Activity stage that runs that job. Then any upstream stage can supply values to them. Best to click on the ellipsis (...) in the param...

As noted elsewhere, you need a Job Parameter to hold it to pass it into the job, then you can reference the #ParameterName# in a derivation. And the Sequence can easily pass the value from the Execute Command stage as input to that parameter in the Job Activity stage. #2 is just a trigger expression...

Create a job parameter to hold it and populate it using the file, then add the column in a transformer and reference the job parameter as the derivation.

harikhk wrote:In case you need the output in the format you mentioned, your code would suffice.

No, not really. There's no "output format" in their posted code. You are correct about the date target part, however.