Embedded Files
Subscribe to keep this site alive! Under new management but as always, still 100% FREE. Anyone with the IBM i is a friend of ours.
The Challenge: We got a new trading partner for an outgoing document that requires a new translation format. To minimize impact during testing, we created a new UFD (using the one in production as prototype). This new UFD was pointing to a copy of the files in our test library.
The Challenge: We got a new trading partner for an outgoing document that requires a new translation format. To minimize impact during testing, we created a new UFD (using the one in production as prototype). This new UFD was pointing to a copy of the files in our test library.
Testing is done and when we are about to retrofit the changes to production, we were told that we cannot make changes to the way we add-to-TC and was advised that we cannot introduce new UFDs. There must be some hard coding somewhere that prevents a new user file definition from being recognized.
Testing is done and when we are about to retrofit the changes to production, we were told that we cannot make changes to the way we add-to-TC and was advised that we cannot introduce new UFDs. There must be some hard coding somewhere that prevents a new user file definition from being recognized.
In the Work with Transaction Center Entries - F6, both versions of the UFD are available. Both say All Trading Partners and No Selection criteria specified. Do you think we need to add Selection Criteria to both user file definitions?
In the Work with Transaction Center Entries - F6, both versions of the UFD are available. Both say All Trading Partners and No Selection criteria specified. Do you think we need to add Selection Criteria to both user file definitions?
The Analysis: To answer your question: Your organization most likely uses a Control Language Program (CLP) and has hardcoded the oldUFD. You can find this in one of the following commands or programs: ED710 (deprecated), UADDMBX, ADDTC or ADDMBX (deprecated).
The Analysis: To answer your question: Your organization most likely uses a Control Language Program (CLP) and has hardcoded the oldUFD. You can find this in one of the following commands or programs: ED710 (deprecated), UADDMBX, ADDTC or ADDMBX (deprecated).
The Solution: If you are not in the position of changing the CLP, swapping the UFD of your new format to the on in production will solve it. This is assuming that you did not do any changes in the UFD as far as Record IDs, Field Names, User Fields and SetID Fields. There is also an option to incorporate the changes to the format in production.
The Solution: If you are not in the position of changing the CLP, swapping the UFD of your new format to the on in production will solve it. This is assuming that you did not do any changes in the UFD as far as Record IDs, Field Names, User Fields and SetID Fields. There is also an option to incorporate the changes to the format in production.
Page updated
Google Sites
Report abuse