Hi 'Bee'
I am not familair with the 'Profilehandle' problem. Maybe a CNC-type person can help you there.
However I do get very concerned if people tell me that they "terminate" batch jobs, especially when the batch job builds a work file.
R42800 is probably the most dangerous job to terminate. This UBE builds a temporary work file (F42UI800). Once built, the first record is read and all financial transactions are completed. Once all financial transactions are completed, the first record is read again and all sales and inventory transactions are completed and subsequently the record is deleted from the work file.
If you watch the number of records in F42UI800 you will see the number first increase, than stay the same for a while and finally decrease.
Once the UBE is finished F42UI800 is empty again.
If R42800 is terminated at any stage, records will remain in the work file and will be included in the next run of R42800, thus potentially causing duplicates in A/R and G/L.
Also if the job is terminated during the processing of the F42UI800 records, you could have the scenario where A/R and G/L records are created but the associated inventory and sales records have not been processed, thus causing nasty integrity issues.
In short, if you terminated R42800, please verify the number of records in the F42UI800. If there are records left in there, contact an integrity or sales specialist.
By the way there is a reasonably good document on the knowledge garden on R42800. It gives you more info on the sequence of events. However, fixing the potential problems can only be done by SQL.
Good luck and hopefully someone can help you with the 'profile handle' problem.
Rgds,
Sef van den Nieuwelaar
Australia
B732 on NT, XE on NT, B732/A73 on AS400, B733 on NT
