DSXchange

You don't need WeofSeq at the end. CloseSeq will write an end of file mark if you have written to the file. Okay, I haven't tested to back this up, but I believe Ray is mistaken. I have always used WEOFSEQ to insure that a file is truncated. If you open an existing file and then write to it fewer r...

Your solution is not the work-around, it is the solution. If you're just moving a file, better off using command line with a compressed file. You can search this forum, we've debated the FTP stage and its merits/usage at length.

Search this forum for the oft covered ICONV and OCONV functions, as well has how to use substring notation ( variable[x,y] ) and FIELD functions to parse dates.

Moving a file means picking it up as it sits and copying it. Reading a file and writing the results elsewhere is a totally different concept. In the case of moving a file, you don't care about the internal structure, it's just a collection of bytes. By reading a file, you care about carriage returns...

The FTP stage is a remote file reader or writer. If you need a file mover, just invoke the command line ftp program and use either the Command stage or a shell exection.

chulett wrote:If you want to 'truncate' the sequential file before you start writing to it, use (from memory) WEOFSeq first.

You can use it last as well, it just lops off the remainder of the file.

The easiest way to "read" a file into an array is to simply "cat" or "type" the file. Example: UNIXcmd = "cat yourfilename" Call DSExecute("UNIX", UNIXcmd, ScreenOutput, ReturnCode) The screen output is put into a variable called ScreenOutput. Now it's just an array. Each...

What are you trying to do? Using readseq and writeseq to manipulate data in a file is very tricky. Use readseq to scan a file from beginning to end. Use writeseq to sequentially write to a file from beginning to end. You cannot move backwards and forwards in a file, manipulating one row, reading ano...

There's also no warp-drive engine, time travel machine, or cure for the common cold.

Yet.

Really helps out the here and now, don't it?

There is no PX for Windows.

Your error message is that the hash file, as named, does not exist and could not be opened. The name of your hash file is "hfDSErrorFileC113648" and it exists in your project. You need to verify that whatever job creates this hash file has run and did create the file under the name and metadata you ...

Your request is impossible. You're asking for a single command to parse the job design repository to find all usage of a table name. Searching the table definitions for using in the job designs is a broken search method, this trick doesn't work (see MetaStage user complaints). What you want could be...

The control file was unable to be locked by DataStage for creation/update. Make sure that you aren't simultaneously using it in another job.

Oracle 8 client works with 7,8, and 9. Oracle 9 client works only with 8 and 9. The Oracle 8 client seems to be the best choice given your requirements, so therefore the Oracle 8 plugin is your DataStage requirement. Note: Oracle 9 cannot use a dblink to Oracle 7, it's not supported. So, there's no ...

The problem you will face is that there are hundreds of DataStage internal hash files as part of the product. The engine command "LISTF" will list all files in a given project. You will have to discriminate which files relate to your jobs, and which files are part of DataStage. You can get help for ...