DSXchange

ray.wurlod

Is your source a file, a database connection, or something else? From which stage did you create the reject link? Can you advise the record schema of your source stage and a couple of example reject records?

ray.wurlod

With what commands (exactly and completely) did you try to start the servers?

ray.wurlod

Set APT_STARTUP_STATUS and APT_SHOW_RSH environment variables and the log will report what commands are issued during the startup.

ray.wurlod

Not enough information. Why are they being rejected? Are you capturing the rejects and, if so, can you see any pattern in them? What command are you using to move records from current to previous? Do the current and previous files interact with the source in any way? Which stages are running in para...

ray.wurlod

No, but... Yeah, but...

Your routine could process the wildcard and check the size of each file in turn. Invoke ls through DSExecute, for example.

ray.wurlod

Yes you can.

Open the file with OpenSeq then use the Status statement on the file variable. Field #6 of the dynamic array returned by Status contains the file size.

Code: Select all

OpenSeq filepath To file.fvar
Then
   Status FileInfo From file.fvar
   Then
      FileSize = FileInfo<6,1,1>
   End
End

ray.wurlod

The specification is clear. We're now in think time, because nothing immediately comes to mind. It's easy in a server routine, but your question asks how to do it in a DataStage parallel job (which would probably need to execute in sequential mode).

ray.wurlod

As well as those two I always include APT_DUMP_SCORE (default False), because the score is one of the most useful diagnostic tools you have. The default value of APT_CONFIG_FILE I set to $PROJDEF.

ray.wurlod

Code: Select all

Right(MatchField(InLink.Code, "0N0A0N", 2), 1)

ray.wurlod

Who stopped it? "Stopped" means stopped by user intervention.

ray.wurlod

Yes recursion is possible, but (like any language) make sure you have an exit strategy. Otherwise you will have an infinite loop that will only exit when you blow your stack space.

ray.wurlod

Set up your users as Information Server users and give the product role DataStage User to each (apart from the ones you want to be DataStage Administrators). Then, using the DataStage Administrator client, and logged in as an administrator, allocate the Developer role to each of those users.

ray.wurlod

The limit is primarily imposed by string space in memory. I have had 3MB strings in the user status area.

ray.wurlod

Have the Sequential File stage append to /dev/null (UNIX) or .\NUL (Windows). Then you have no file created.

ray.wurlod

Because View Data does not work properly with multibyte characters.

It is NOT a fault of the stage.

Search found 53125 matches