DSXchange

In the controlling job, or in a before-job subroutine, write the header record to the file. Within the job itself use "append to file" as the rule in the target Sequential File stage. In the controlling job, or in an after-job subroutine, write the trailer record to the file. The count can be obtain...

No. There is only one data type in a text file, "text". Once the data are in DataStage, you can use expressions or Routines to check data types. For example: FUNCTION IsInteger(Arg1) * Returns 1 if Arg1 is an integer, 0 otherwise. * Can not use arithmetic functions in case Arg1 is non-numeri...

Welcome aboard! :D A hashed file is like a database table, in that it is a way of storing rows and columns. "Hashed" means that the location of a record is determined by applying a hashing algorithm to the primary key value, rather than by using a table scan or primary key index. This means that loo...

Single character replacements are more efficiently handled using the Convert function rather than Ereplace.
Also for efficiency, initialize a stage variable (or a constant in code, using Equate) so that Char(10) is only evaluated once.

You can, however, use nested expressions. Use parentheses to make things clearer. For example, if you want to use the result of the function to add to a column: If (Condition) Then Func1(arg1,arg2) + DSLink.SourceSystem Else DSLink.SourceSystem You do need to do something with the re...

It appears that the end-of-line character (\n) is missing from the last line of your text file. DataStage survives this, but issues a warning so that you're aware of it. Edit the text file and position to the end. You should be at the beginning of an empty line. If you're at the end of the last line...

How did you determine that?

I can only suggest that the project account is not fully/properly installed, or that the Administrator client is filtering what you're permitted to do (for example, you can't LOGTO from the client). Try adding a new project simply to see whether DS_CONNECT is in the VOC there. You can delete the new...

Try DS_CONNECT rather that DS.CONNECT. I'm very surprised that there's no CONNECT. Are you in an account that is a DataStage project?

DataStage access security is based around operating system groups, not user IDs. You will need to create separate groups, let's say dsproj1 and dsproj2, and put user1 in one and user2 in the other. In the Administrator client, configure the security for project1 so that group dsproj1 is in the Devel...

Reset (not re-compile) the job after it aborts, and post the "from previous run..." message. This usually provides additional diagnostic information that helps to solve the problem.

The entry in UV.ACCOUNT would allow UV/Net to access the remote account, except that UV/Net is no longer a part of DataStage. This entry is not used by the BCI/UCI mechanism, so is not needed. I believe, though have never tested the theory, that the remote account name and the entry name in uvodbc.c...

Looks like the DRS behaves differently from other stage types. Report it as a bug. Workaround could be to use explicit stage type, or ODBC, which I'm aware isn't an acceptable workaround for PeopleSoft deployment.

I recently saw a similar problem where it took nearly five minutes to open a Job Activity in a Job Sequence. Systematic diagnosis, using server-side tracing, showed that most of this time was taken up with building the drop-down list of job names in the Job Activity, and there was a large number of ...

Documentation on the use of header files is in the DataStage BASIC manual (basic.pdf), one of the standard manual set. I've just looked at the code you posted a bit more closely; it seems to be missing an outer loop where the "all" column names might be incorporated. Is there more to this routine th...