DSXchange

That's the problem - "all my lines". Ray responded as he did because you said you needed your output to be: 1;2;3;4;5;6;8 You showed a subset of your input fields in the output. Everything before this point assumed a simple concatenation of one record to the next without any 'intelligence'...

Perhaps you should mention the actual error or issue. Ah... Please do not put needed information in the subject when replying as others will not be able to see it unless they start a reply, like I just did. "Re: It will not pass the record to second where condition..." Is this your "f...

Or just use five lookups.

You are missing the fundamental issue: random does not equal unique. Yes, using a unique seed each run will ensure that the sequence of random numbers generated is always different but there's no guarantee that they will be unique within a run and certainly not across runs. It seems that the latter ...

Can you post your actual (full) unedited error? And your example shows "MMDDYYYY" format, why are you using "YYYYMMDD" in your conversion? If your input is an actual timestamp you should be able to use TimestampToString() directly.

One of my rules is to never run anything with unlimited errors. Keep the warning limit small so you can get some error information logged but you don't blow out the logs in the process.

Your metadata needs to match the file format. For example, in a "csv" file you'll need to tell it the field delimiter is a comma. Since you haven't, everything goes into the first column.

Others may know more better than me on the DSGetJobInfo() thing as I can't test as I have no DataStage access. I do seem to recall that the command line dsjob version does include that information but you don't really want to be shelling out to the O/S on every row. Otherwise a lookup to a Universe ...

I'm not aware of any DSGetJobInfo InfoType that would return the category, you may need to query the repository directly if you need that.

Details please. A single number each run or several over the course of the run? And does it really need to be 'random', meaning would a surrogate (unique but sequential) not work?

How is your job designed, what sources and/or API are you using? The 'folder' is called CATEGORY in the DS_JOBS table, by the way.

So that's what you meant by "make it some number". Based on your description and the subject of your post I thought you wanted to extract it as "data from the log file" and convert it from a string to a number, not mask it. Always helps to fully explain what you are trying to do ...

Start by spelling out your requirements - your transformation rules - in words.

You never mentioned that part in your original post, I was under the impression all you wanted were the SSN values which is why I provided the answer that I did. Can you be more specific with regards to exactly what your end result should be?

Read the records as one long string field, filter out any that do not start with 'SSN:' and then use Field() to get the second field from that ":" delimited string. Convert.