DSXchange

DSguru2B

Each active stage will create a process. With multiple jobs running, the resouces will be shared by the jobs and the OS kernal will decide how much to provide to what process.

DSguru2B

When you exported the job, did you export the job design as well?

DSguru2B

You can also use the OPEN and CLOSE commands in the enterprise stage. These properties are present under 'Options'.

DSguru2B

Well a hashed file with just keys can take a lot more than a few million records and not hit the 2GB limit. You can also make the hashed file 64bit and get rid of the 2GB barrier altogether. You can also load your souce into a work table and pass a sql join.

DSguru2B

You dont need the user variable stage. Get rid of it. Connect the execute command stage directly to the job activity stage and in the value expression. Provide the following

Code: Select all

FIELD(Execute_Command_21.$CommandOutput, @FM, 1)

DSguru2B

Executables are in binary internal code. You wont be able to view it. Why do you want to do that?

DSguru2B

You are right. Load wont work as it utliizes the sql loader. I have fixed my original post.
djoni, try to build a job at your current site in which you think the records should be rejected. Send that to IBM.

DSguru2B

For primary key being the same for two or more records, if you use Upsert method then you might not see rejects as the very first one will be inserted and the second and so on, will be updates. Choose upsert method and then you will see. I am surprised IBM said the reject does not work.

DSguru2B

Whatever goes wrong with the job, it will be logged. You can get the log entries by various options of dsjob command. Namely -logsum, -logdetail, -report etc. Look into them.

DSguru2B

I have never tried it. But I dont see why it wont be able to transfer properly in binary mode. But definately you wont be able to view it without decryption. That goes without say. Try decrypting the file.

DSguru2B

The ftp might be succesfull but you need to decrypt the file before being able to read it. Are you just trying to view the encrypted file?

DSguru2B

No, the double/single quotes would not matter.
Then its really your second condition that might not be coming true.
Try the following

Code: Select all

if (new_date <= extract_date) And (@TRUE) 
then 

statement A 

else 

statement B

DSguru2B

Are'nt you suppose to specify the string to trim along with B option. Also you are not comparing it with anything. Use the following if trim(inputfield," ","B")="" or isnull(inputfield) then @NULL else trim(inputfield," ","B")

DSguru2B

You sure its null and not just a space or nothing? Is your source a flat file?

DSguru2B

Welcome Aboard
There are numerous error that you can encounter on a flat file using the sequential file stage. File permissions, metadata problems to name a few. I suggest spending a few hours going through file related problems on this forum.
What do you mean by logical errors though, it passed me.

Search found 6797 matches