DSXchange

Use Dcount and Field. Something like

Nothing out of the box. You have to code it.

Yea but still not a good approach. If he has other characters and not a "/" it will pass through undetected.

Wont work for him. He needs more characters to be tested on then just a "/".

I say go with Ken's method instead of playing with readseq and openseq. All you need to do is check for a record in the file. FUNCTION myDate(inPath,outPath) inCmd = "type ":inPath CALL DSExecute("NT", inCmd,ScreenOutput,ReturnCode) fDate=ScreenOutput<1> sDate=OCO...

You mean in the .profile. Thats absurd and really strange.

I_Server_Whale wrote:Refer to the Server Job Developer Guide pdf manual.

Look for complete sytax there. lparams will list all the params the job is using and not the value for that param. You need the option -paraminfo with dsjob.

O yea no matches in px. errr....Hard to switch between job types, especially after a long day.

Look at the ICONV function with conversion code "MCP".

Use the Matches function to direct the data down a reject link and !(not) of reject link to your good link. Or better yet, the index function.
Something like

for the reject link and =0 for the good link.

Read this post for more clarification.

Its just DATE('YYYY-MM-DD'). Refer here

A phantom is nothing but the background process for DataStage. If you are seeing phantom after doing a ps and greping on your id then you will see that and its normal. However, if you are seeing phantom messages in yellow in the datastage log. That is something to worry about. What you see at the un...

Its like a parent thread and a child thread. The job is the parent thread with db connection as a child. With the parent being killed, now you still have a live child thread. Thats the problem. Tell your dba that killing me will not stop this from happening. Just take him/her out to lunch. Correctio...

Annotations my friends.