Are the tables the same on Test and Prod? Possibly an update was done on Test that wasn't done on Prod that changed the table on Test.

Thanks for the responses JimY and TJ Mann. Yes, we compared the schema of the CBPMTLOAD table and both environments are identical, as is the file used since it was the exact same file (reviewed and compared after ftp transfer to each server using a text editor).

However, it appears to work fine now (even though no true changes were made)...So here's what happened folks...

In trying to get this command to work on this CBPMTLOAD table, we had attempted to run the improtdb command (importdb -nd) both with and without a header record in the input file, using both the -nd options alone and with the -f option added to them (-fnd). No matter how we tried it, the import failed.

However, once I put in a ticket to Infor, they advised me that since we had a header present in our input file, I should add the -f option to indicate that there is a header record. So, when we tried this (again), it failed (again). Upon learning of this result, Infor then advised me to go back to using only the n & d options, but with also removing the header record from the input file.

Now knowing that we had already tested this both ways and seeing it fail both ways, in an effort to continue through with my due diligence, I did in fact try the steps suggested by Infor (again), but low and behold!! When I removed the header record and ran it thorugh using just the -nd again, it worked!! Then, and this is whre is really gets weird...having subsequently gone back and added the header record back in, I am now able to successfully run the same importdb -nd command either way. Illogically, it now works every time I try it, using just the two initial options -nd, whether we include a header record in the input file or not.