DSXchange

kduke wrote:My script has a way to unlock all jobs too. Not wise in the daytime but at 2 in the morning it is safe.

Safe for most peoples, I'm sure. I'll bet not safe for you, you night owl.

You should be more assertive, Ray.

It will be dog slow unless you index the constraining columns.

Which would be the 'O/S' that I mentioned. And it will take more than a simple 'unzip' command in the Filter. That might get you the file names being unzipped but not their content. Make sure your unzipper / decompressor has an option to write the uncompressed output to standard out. For example: gu...

I'm not sure there's ever been a true problem here per se, only the perception of a problem.

No. At least not directly. You'll need to 'uncompress' it first and that's a job for your O/S. Or your file transfer mechanism.

Craig,can you explain a bit on what you meant. Records in a flat file can be 'read' by the cat command on UNIX. So a custom routine that takes the filename can cat the file using DSExecute and capture the result, sending it back. Then if you call it in the Initial Value of a stage variable, it only...

We are thinking of something, where the job is just re-started, it should start picking up records from the point it had left in the previous run? That would be the 'automated' part. Stop and think about how it would need to work. Outline the steps needed to accomplish that. Then implement them in ...

Flat file. Routine to 'cat' and capture the value. Use it in the Initial Value of a stage variable.

In other words, it's just a counter of the rows coming into the transformer. And there is an @OUTROWNUM for each link leaving the transformer.

Sure. The fact that your source is a flat file simplifies this and I'm assuming you are doing commits over the course of this load. A Job Parameter that is the 'number of records to skip' - i.e. the number successfully loaded to this point. Then it's just a constraint: @INROWNUM > #RecordsToSkip# De...

What do you need in this timestamp? One consistent value over the run of the job? Something that changes over the course of the run? Same basic answer but with a slightly different approach. In any case, you'll need to build a routine to get the system date/time and put it in a timestamp format. The...

Precision and Scale.

Specially HP-UX 11.11 (11i) PA-RISC. We have one server running 7.5.2 - all others run 7.5.1A - and there have been enough silly little unexplainable issues that I'm about to nuke the farking thing and reload 7.5.1A. Hopefully that will help isolate if it is a problem with the server or the version ...

The backup script available on Kim Duke's website will automatically skip locked jobs and log the ones skipped. I believe you are out of luck on the 'no executables' part.

Right. As I said - "you need to have multiple links from the same Transformer to a single OCI stage before the option becomes available on the Transaction tab of that OCI stage". And from the online help: "All the input links in the transaction group must originate from the same Transformer stage."