DSXchange

Welcome. You can't "get" records from a source based on data solely in a hashed file but you can take the "process in a transformer" path. It does depend on what ">40" means, exactly. In your example, do you mean record numbers 41 thru 100? If so, just compare @INROWNUM...

There may not be all that many people up on 8.7 yet, or anyone who knows that has. Have you posed that question back to IBM?

Suggestion: If you are going to post a solution, you should explain the solution that you are proposing. For example, what exactly would this script do to validate the load? Question back to vskr72: Will you be logging this audit information anywhere or just simply need to check it? What should happ...

Yes.

And yet an exact search for ORLogging returned 42 matches for me.

In other words, it's not all that unusual.

Search the forums, it's already been discussed enough that it doesn't really need repeating.

Another option - don't generate them. It looks like you were using the DOS "dir" command, if so add the /b option for a "bare" listing and it will only output the filenames.

Windows XP is not a supported OS for the server portion.

You'd have to write your own routine, as noted in the linked post, that did not log that information. Note, however, that since you are passing the password to the script on the command line, it will still be visible to anything looking at the running process.

Note: split from this topic.

pandeesh wrote:Moderators,
Please remove this topic entirely.
I don't see anything useful in this.

Now, now, let's not start a trend. I do.

As I already said, I will remove it once it has served its purpose as an object lesson of Things Not To Do.

$APT_IMPORT_PATTERN_USES_FILESET=TRUE

Embarrassment.

This is now on my list to remove entirely...