DSXchange

If you wanted all the files under Text then the following would have worked as well

Does you id have read/write permissions to this particular directory? plust provide fully qualified path to the files. If your in the directory where Text resides, provide the fully qualified path of Sales folder.

Not a plausible approach. Redesign it so that the contents of a hashed file are now present in a dataset and use a px job to read the dataset. If you could be more clear on what needs to be done, someone here can point you in the right direction.

Its good to see you guys do your own detective work rather than waiting for the answer. Keep it up.

I told you they would still miss it

In the filter command of sequential file stage, put wc -l. Specify one column in the metadata. This will get your the row count of the file you specify.

Take a minute and review your if then else statement. If the hour and seconds are greater than 23 and 59 respectively, then 00.

You must be hitting the 2GB limit imposed by the OS for a file. Either that or your disk ran out of space.

Did you make sure all your numeric/Integer/BigInt/SmallInt datatypes in the sequential file contain only numbers and no non-numeric characters?
Stick in a transformer and specify a reject link. Specify the array size to 1. The culprit row will be rejected for you to analyze.

In the UV prompt from the unix command line (telnet, putty etc.) or DataStage Administrator.
Also, were the jobs locked by your id? If not then you wont be able to 'free' them. Search for DS.TOOLS in the forum, another way of unlocking the jobs.

Now this is a good informational post, not something you see everyday. Thanks for the great info guys. This is definately going in my favorites bucket :D

The Convert() function will work to retain only alphanumeric characters. But for non-printable characters, I think you will have to go the routine route.

Agreed

So is your scheduler controlling the process by reading return codes or your job sequence is? First of all, the creation of flat files at the end of each extract is redundant, IMHO. As the scheduler can be setup to kick off the 11th job (your main sequence) only after the first 10 finish successfull...

Convert() requires three arguments.
Try something like

That should be close.