DSXchange

That's no standard "timestamp code" that I've ever seen or that Google can turn up, so if it a standard it's a local / company specific one. As noted, I'd go with some sort of lookup.

You were 'unable to parse' this in what sense - you are getting errors? Not sure how to approach it? Not getting proper output?

Detail for us what you've tried and the issues you are seeing.

Have you... texted him... again in those 3-4 weeks?

:? I'm not talking about anything in particular other than the fact that for the trigger ( any trigger ) to have something to evaluate - and for it to possibly 'fire' and allow the job to move on to the next stage - whatever the current stage is doing must complete first. Period. I'm not really sure...

Again, when you say "I unable" - who are you logging in as? If it's not dsadm, then try that. If it is in fact dsadm, show us the .profile change you made. Also, this should be in your dsenv file. Technically.

Specify for us which account's .profile you added the PATH to and what account you are using to do the testing. After adding, did you log out and back in? I'd also suggest you show us the $PATH change that you made.

It will "bring the trigger status back irrespective of Success or failure" but the command being processed must end first.

Right. If you don't explicitly path a command so it knows where to find it, you've got to provide a 'search path' so it knows where to look for it - i.e. an ordered list of directories to search thru. That is the $PATH environment variable.

Searches suggest that this is caused by the temp lookuptable (or in this case the fileset) going beyond the 2GB limit, or running out of space on the drive. In the current case neither of these are true. It is true. The former. Learned this lesson the hard way back in the day when (in our case) we ...

As noted, involve your official support provider.

Allegedly yes, as noted near the end of the first page.

So... hard to follow your explanation but it sounds like the script is hanging rather than the unconditional trigger not 'firing' or the script not executing. It can't move on until the script starts and completes in some fashion. That or fails to start. Starts and never ends? Forever wait.

Out of sheer curiosity, what version of MS Word are you using and do you have any idea if the version makes any difference here?

Why not try it, attempt to answer the question yourself? If you do, make sure you use a sufficiently (very) large volume to do a proper test! IMHO, the short answer would be if the concept wasn't required, it wouldn't have been used as an illustration of how to build this kind of process. Does that ...

Was talking about the wget utility, not your zip file.