Yes, I will send you the specs for the job tomorrow. I solved it by forcing a batch number in the application that is generating the interface file. Batch number increments from that source each time, so the problem is solved, and the job works, all posts correctly, but still, I am certain I will need to do other similar jobs, so finding out why it is behaving so oddly is a must.
One other thing, I am invoking the job outside of mas, which has always worked fine in previous versions, but now, the user has to exit mas, and go back in after a job, or they get an error, it's very strange, as if the vi job is locking files. I think maybe because the user id on the job is different than the currently logged on user.
Ah well,
Thanks for the help.
ChaZ
There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.