First, was there a reason you used MPUT instead of PUT? It doesn't matter for the content, but a simple PUT is usually easier for transfers of single files.
Anyway, without the error message identifier, there is almost nothing we can say. If we don't know what the system thinks is wrong, we can't guess how it might be fixed.
Two general areas need to be reviewed. First, how did the savefile get to the Windows system in the first place? If it wasn't a binary transfer, then it was corrupted at that time. Second, where did the savefile originally come from? If it came from a different AS/400, it might contain data items from an incompatible system version.
But without more details, we don't know.
TOM- the .savf files was established by one of our professional services and from where? that I do not know.. so basically tom what are you trying to say is when this .savf files comes to different as400 and is not compatible to the new as400 this might be the reason? thanks.
BIGKAT-I would like to monitor AUTL, CFGL,CNNL CTLD JOBD LIND which more of them are lists and description.. what we do is to get the original details of each objects and monitor it if someone makes some addition,deletion or modification in the line.thanks
RICKMCD- I’m assisting the AS400 admin for this but for the inputs he’s the one doing it. I truly believe he knows what to do.thanks