DSXchange

Thanks for that 'digithead' remark, Kim. I guess. For the record, installs have always been done as 'root' and umask is set correctly on all servers. Oh, and I posted the 't' bit explanation I got from the man page on 'chmod', plus a little different one from 'ls': Execute/search by others; set stic...

No. How do you propose to do a lookup without 'key columns'?

What stages? Did you import the XML's metadata so you are using the proper XPath expressions?

How exactly is this differing with what we've said, Roy?

Do you have access to the Ctrl-M server? Any idea how the logs are actually stored? Talk to your Ctrl-M peoples...

The 'required information' part is documented in the XMLPACK_20_Designer.pdf in Appendix B - Advanced Transformations.

Check out the DSGetLinkInfo function.

Isn't that just a matter of sort descending on calls and constrain to five rows?

Is there some reason to have the "t" bit set on /tmp? No clue, but I'm guessing yes as every HPUX 'server' here has it set like that. What in the heck does 'save-text-image-on-file-execution' mean? Regardless, not something I could change... I'd have to see if 'they' will. And in case it's not clea...

Curious if anyone has seen this behaviour before and can explain what in the heck is going on. Simple scenario - point a Sequential File stage to write to a file in a folder with the 'Overwrite' option enabled. The file ends up being owned by the user running the job. Now, I know that's not always t...

Ok, got that... perhaps I'm smoking crack, but I started with version 3.1 and I distinctly remember the concept of 'categories' being added later in the product's life. I recall it being a Big Deal when it showed up. Maybe that was in 4.x. Oh, well. I was thinking 'folders' perhaps might mean 'Proje...

The only way to 'suppress' errors like that - ones spit back from your target database - is to ensure they never happen in the first place.

I don't recall version 4 having categories. Perhaps 'folders' means something else in this context? Or perhaps I'm just wrong.

Clear the hashed file 'before job'.

The 'current date' certainly could be acceptable the vast majority of the time as long as you have a mechanism to override it if you need to. That's how we handle it. There are tons of posts on reading parameter values from a flat file. Also on reading values from a DB in a DS job and passing it out...