If the REDEFINES was originally one of those which is allowing part of a record to be "re-used" for data which is unique to different circumstances of the data, like (AGENT-AGENT-NAME, AGENT-CUSTOMER-NAME REDEFINES AGENT-AGENT-NAME) then only one of your new fields will contain a value on any one record.
Something like this is most likely for your REDEFINES. If you remove the REDEFINES so that there are now two fields, when AGENT-AGENT-NAME is given a value, then AGENT-CUSTOMER-NAME needs an initial value (like SPACE or LOW-VALUES). When AGENT-CUSTOMER-NAME is given a value, AGENT-AGENT-NAME needs an initial value.
If the REDEFINES is to allow a different definition of the field for some purpose, like a packed-decimal with a YYYYMM redefined for acessing the YYYY, the more work needs to be done, as the original intention has been spoiled.
Sometimes, although not usually on records, the REDEFINES is to allow "something to be done" to a field which can't be done with the other definition. Like accessing a one-byte binary value. Again, if this was the original intention, more work is needed, as this will now fail to achieve its object.
There is no "magic resolution" to any of these, you have to identify how the REDEFINES is being used, where the different elements of the REDEFINES are being referenced, and ensure that the correct new procedure code is included to achieve both the original and new purposes.