DSXchange

splayer - check again, if you don't find a &PH& then perhaps you (or someone else) deleted the directory. Do you have a D_&PH& entry in the project?

You need to execute "cd \&COMO\&' at the command line, as UNIX sees the ampersand as a special character.

The maximum number of concurrent jobs that can run is dependant upon so many different variable factors that it is impossible to give a number. It can range from very few to several hundred or more depending upon your configuration. There is no builtin mechanism to effectively form a queue for jobs,...

Unfortunately the maximum number of warnings a job will use is not part of the JOB activity stage. You can set that value you start the job via command line dsjob program, though.

Using the TCL commands directly to delete entries in the DataStage hashed files that contain job metadata is a prelude to finding out if your project backups have worked. You will corrupt jobs and/or the whole project by deleting things from the DS_JOBS (or DS_JOBOBJECTS). You should go and edit the...

I was curious about the v2 of HL7 so I used "HL7 DataStage" in google and got a lot of hits, several of which on IBM pages.

The "\\NextNumber" entry in the DS_JOBS table holds the next job number. Hashed file records can have any format, and it happens that field 1 is used to store the next number in that record, but it is also the column used for JOBNO (in the actual job records), which is why this query returned this r...

Another question, how many binary columns do you have in your file? If just a few, you can let FTP take care of the EBCDIC-ASCII conversion and then reconvert those few COMP columns to EBCDIC and then decode them using the sdk routines into their actual number values.

There is no tuning information stored anywhere. The current hashed file type, modulo and other attributes are stored in the physical file itself in binary form. The DICTionary only describes the format of the data in the file, not the file's format. You can get a hashed file's information display us...

It will hash the 5 values to 2 nodes, one node will get 2/5 of the data, the other 3/5 of the data in your example. You can't get a better distribution unless you use round-robin, but then you would need to repartition again downstream for the sort so that approach is no good.

The same as for normal FTP. You can only push the file from UNIX to Windows if you have an sFTP server running on Windows, otherwise you will have to pull the file from the Windows side.

I agree that deduplicate via hashed files is not the most efficient approach. Sort the incoming data using the fields you need for detecting duplication, then use 2 stage variables in a transform stage (one to get the result of comparing this record with the last, the other to store the last record)

...and As Arnd suggested added some records to the current table and the issue is remaining same... The result you get after adding records is important in diagnosing your error - 'same' doesn't help at all. Do you have just 10,000 records now (implying a limit is set somewhere), 10,001 (implying a...

The TCL DELETE command is not documented and, as you noted, does not really delete a job but deletes only the entry in the DS_JOBS hashed file. I don't know where you got this from but perhaps it came from some post here in DSXchange and is almost certainly taken out of context. This is one reason t...

DataStage TX packs support HL7.

You can have multiple jobs in one .dsx export file. One instance of the manager can only import one file at a time. But you can run multiple instances of the Manager and each can be importing a .dsx file.