DSXchange

Doing a "CLEAR.FILE &PH&" has nothing to do with your issue. The "&PH&" hashed file (actually stored as a project subdirectory) contains only Tee'd output from background processes. I would caution you against using the CLEAR.FILE command directly. You should stic...

The first question that raises itself is why you wish to write a routine when you can do the same thing in a Job Sequence with less effort on your part. If you really need to write BASIC code, you need to know from where you want to trigger this - if you are calling this from a transform for each ro...

Hailun - there is a version of PX that runs with windows.

Try editing the post and doing the tags correctly.

dstest, please enclose your routine in "code" tags to make it legible. You will need to use a COMMON block to make your routine's data memory resident for the duration of the job, bit it is too much work to try to decode your post to give you concrete suggestions.

Your log file is corrupted and the quickest way to get back up and running is to use the Director and clear all log file entries; this triggers a TCL command of "CLEAR.FILE" which will reset the log file and get rid of your blink errors. If you are 100% certain that this log file should gr...

Do you have an after-job routine defined?

In addition, those messages are just effects of the error and not the error itself.

any details? (what didn't work - error message(s) & command line scheduled in AT)

Another solution is to could add a merge stage to append a line to your output, just ensure that the order is set correctly. This line would be created using a row generator stage.

You need to specify your definition of what a month is. What about 2010-01-31? Since June doesn't have 31 days what do you do? Once your rules about months are set, you can use the DateFromDaysSince function. Otherwsise you could convert your date into 3 components, do your math on them, then put th...

The job works the same, but I am sure your production data is different from your test data, thus the error.

Sure, that would get rid of your error message, but you need to find out if that is a legal option in terms of your job design.

The DateFromDaysSince function is what you are looking, described on page 593 of the Parallel Job Developer Guide

The simplest means of doing this is calling an after-job which shells out to UNIX and just issue the command to append those spaces to the file.