DSXchange

Craig, Thanks for the reply. I agree with you totally re the design time issue. The number of times we have needed to look at things that would have been very easy in designer - well, I'd best not start. Unfortunately, two people were thrown in to design and build a new system from scratch after goi...

As a result of another issue, we have found that when we import a .dsx into our production project (let's call it Proj C), new versions of routines do not overwrite the existing versions. The process we use to go from development to production is (we understand that this is not 'best practice' and a...

Sorry for not getting back to you guys earlier. Thanks for the replies but unforunately, we have tracked down the problem to new versions of routines not overwriting existing versions in our production environment.

I have posted another query re this issue.

Thanks again for your help

Cheers
Johnno

Hi all, I have been trawling through the forum looking for a possible solution to my problem and am not sure whether or not I have found it. I have a DS Basic job that reads a sequential parameter file and then submits a sequence using these parameters. Immediately after I finish reading the file I ...

Thanks folks - all sorted!

Hi all, I can't believe this hasn't been covered before, but I can't get anything returned for a search on either 'before' or 'after'. Anyway, I was wondering whether or not it was possible to use job parameters, stage variables, or any other dynamic value as the input value to an after-job routine,...

Thanks for all your replies. I have finally got access to the Ascential developer net to check out the posts relating to this issue (thanks again chulett). I will try and have a play with this and see how it works and what it can/can't really do (if I ever get any time!). For now I just use the DOS ...

Thanks very much. As much as I wish you could have told me different, I'm glad I found out the reason behind it as we will need to change a few of our jobs (and a whole 6 days before implementation!!!) I will study the link you provided and look at it in some more detail tomorrow (train strike in Lo...

Being on a Windows platform we could, as you say, use DOS commands to produce a file of filenames. My major concern is however, that as we have used this approach so many times in the past with this being the first problem, have we made a serious misjudgement in the design? And if not, why won't thi...

This is the only column we have and we populate this with the filename. We are only interested in the filename and as you have to have a key in this stage, we have just set this column as the key.

Cheers
Johnno

In the folder stage the on the outputs/columns tab is: Column name: FileName Derivation: (none) Key: Yes SQL Type: VarChar Length: 255 Nullable: No In the sequential file stage that the data is being written to, the inputs/columns tab is: Column name: FileName Key: Yes SQL Type: Char Length: 64 Null...

Not quite sure how to explain this but here goes: I use a folder stage to identify all the files in a specific directory folder that are to be processed in the current run. I have used the same basic job for a number of other processes and it works fine. For this process the wildcard is *.DAT. The p...

Thanks Kim,

Have got it working now - it only appeared not to be continuing with the sequence when it actually was. Have now put calls to dsloginfo to indicate when a certain routine was being run.

Cheers
John

I have been experiencing some rather weird results when checking the user status and job status in custom triggers for a job activity within a sequence. The code I am using is: CheckStationId.$UserStatus = 2 AND CheckStationId.$JobStatus <> 3 Although the UserStatus = 2 and the JobStatus = 0, the ne...

Thanks Craig. Will report it to Ascential. Will also take out those fields that default to Null.