|
This is causing level check errors in our RPG programs, even though the
record format level ID is unchanged. Anybody have any insight on this?
I conducted a little experiment:
Original file (Attribute = PF-DTA)
file: 1100119152826
Record: 4AE630978C180
After CRTDUPOBJ with DATA(*NO) CST(*NO) TRG(*NO)
File: 1100121153527
Record: 4AE630978C180
After CRTDUPOBJ with DATA(*YES) CST(*NO) TRG(*NO)
File: 1100121153752
Record: 4AE630978C180
After CRTDUPOBJ with DATA(*YES) CST(*YES) TRG(*YES)
File: 1100121153936
Record: 4AE630978C180
That worked so well, I tried it three more times in succession. All used
the original PF as the OBJ to duplicate:
After CRTDUPOBJ with DATA(*NO) CST(*NO) TRG(*NO)
File: 1100121154227
After CRTDUPOBJ with DATA(*NO) CST(*NO) TRG(*NO)
File: 1100121154435
After CRTDUPOBJ with DATA(*NO) CST(*NO) TRG(*NO)
File: 1100121154532
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.