DSXchange

Are you asking for some inherent variable that contains the job's name at runtime that you can use as an argument in a before/after routine call? I guess you're trying to avoid embedding a hardcoded name and want one that automatically resolves at runtime? Search for using the macro DSJobName. You t...

Dynamic hashed files have a modulus value that increases as the file grows. There's only two ways to change the modulus of a hashed file: CLEAR.FILE: removes all data and resets the file to the minimum modulus RESIZE.FILE: analyze the current file contents and adjust the modulus to an optimal settin...

Welcome aboard! Your problem is related to the database, not DataStage. A quick google on "ORA-27063: skgfospo:" found a lot of hits, I'm sure metalink has some tips as well. Sorry, but if DataStage can't get results from a query, it's usually the database. DataStage just issues SQL.

What functionality are you talking about? If you mean new stages, sure, it's fully documented. There's even companies that have written plugins to give new functionality to the product. We just saw some of them at the IOD conference this week.

Active stages insert lines into the log when the stages start and finish. If the log is extremely large or poorly sized (they are dynamic hashed files afterall), then these messages can seriously take a long time to get added to the hashed file. The more active stages in the job, the longer it takes...

Just mimic the before subroutine called ExecSH or ExecDOS using a Function. Now, that function takes your argument and executes it, returning the screen output as the answer.

Not really, if you don't have permissions to add cron entries you can't really use the DS Scheduler. Find a unix admin and get the necessary rights.

Oooo, don't think that's in a support API. We usually try to get info from DS_AUDIT, but that's kind of proprietary stuff. Search the forum for DS_AUDIT to see what other folks are doing.

Why not consider using dsjob with the reporting feature built into that?

Ignoring that your examples give different results (trim and ereplace vs. ereplace and trim), it's perfectly fine to nest functions, just keep your logic legible. Consider using stage variables when the same derivation of a value is repeated for many columns, or you need to simply a derivation/const...

Sorry for not keeping up with this thread, we're at the IOD conference and our attention wanders. Look in your DS BASIC manual for SDIV, or string divide. It may be the simpler method for dealing with your issue. See if that works and can you let me know?

How are you calling a routine from a job? As a before/after subroutine call? If this is so, then you can't do anything with results. Before/after subroutines DO something. Any non-zero return code is considered an error. Are you creating a Batch job as I stated? If you wish to use the call to your r...

Create a Batch job (from Director do Tools-->Batch-->New). Now you can enter any logic necessary. From the Add Job box, choose the job to run when a trigger file appears. Press the Add Job button. The logic for running a job is pasted into the Batch job. Now, all you have to do is write the logic to...

The screen output comes back as an array. You need to parse the output looking for filenames, as well as deal with a no files found situation. The easiest method is something like this: LineCount=DCOUNT(ScreenOutput, @AM) For i=1 to LineCount Line=ScreenOutput<i> If TRIM(Line) <> &qu...

Each call to the operating system runs in its own session. Also, your logic contains a typo where NtCmd should be NTCmd to be consistent (case matters) Try: