DSXchange

Check the help, the Convert function converts one character into another. In your case, converting the slashes to an empty string removes them from the field.

Bottom line is it really doesn't matter what order you stick the pieces together in, or what delimiter you use - as long as it matches the format mask used in the OCI stage. Best Practice is to stick with ISO formatted dates, those in YYYY-MM-DD format, and let the OCI stage automatically generate t...

Not my idea of fun... I can already hear 'taps' playing gently in the background...

You don't need to use a calendar to check for Saturday or Sunday. Holidays, yes, weekend, no... the 'conv' brothers can do that for you.

Probably simplest to build a hashed file with your 'disallowed' dates and do a lookup against that with your incremented date: a hit = bad, no hit = good.

Lots of ways. You could substring it apart around the slashes and put it back together with them. You could use your favorite function like Convert, Ereplace or Change to simply remove them from the field.

Suggest you give Convert a try.

I guess I'm not making my point about what is different with what the RTI jobs do. No solution that includes CLEAR.FILE is appropriate to emulate this, as no log entries are removed. They simply remove all of the multi-instance log entries from the Director when a job is stopped. The only way I've s...

You haven't solved your problem with importing the metadata. And of course it will execute without having to do that first, it just simplifies the setup of the stage when you've got a complex SP.

You have to create the hashed file with more keys than you plan on using for the UV stage lookup - whatever number lets you preserve the amount of detail you need to retrieve. So, create it with three and then use the UV stage with two keys, as one example. Plus all the other things needed to pull t...

No limit that I've ever run into, though I'm sure there is one. But then I've never seen a job that needed 62 job parameters. I have, however, seen problems in older versions with encrypted parameters needing their values to be rekeyed at times, but seem to recall it was only if you 'arrowed' down t...

Yah, the priority part is still a little confused. I'm assuming you just mean that for each value of COL1 you want all values of COL2 in order. And that is just achieved by declaring them in the proper order, from highest to lowest priority to use your terms. The upper and lower-case SortOrder quali...

Actually, it is what you were asking for. Specifically, the automation part he mentions.

Not sure exactly what you are fishing for here. To sort in any tool based on two columns where one has 'priority' as you've called it, just mention them in the proper order: ORDER BY COL1, COL2 The sort stage does something similar using the Sort Specifications property: ColumnName, SortOrder COL1 A...

I was going to say something similar, but then I actually popped the cdrom in and checked.

Nope, no stand-alone pdf in the Version Control folder. Figured it must be packed in the cab file, needing an actual install to release it.

Depending on exactly what you need, as noted ps -ef with an appropriate grep filter can get you the running jobs. For example, all running Server jobs can be found by grepping for phantom to see all running processes, or DSD.RUN to get a unique list.

Not sure on the PX side of the house...