Disable the ability to change the record length in existing PF and override and delete existing PF

Disable the record length property option for existing source.
In RDp, when adding a SRCPF with "add to i Project", RDp allows the record length property to be modified, but when revoking the change set, the record length property can not be modified.

1) Developer copies source file from a development machine. The record length is, for example, 125.
2) When he adds the SRCPF to a change set as an RTC version, the record length is changed to 100.
RTC accepts it without any warnings.
The record length is not changed by developer, but instead takes the length set by RTC.
3) When pushed to System i via the build, the system returns errors about the record length.

Development had suggested a way to handle and the customer had responded with the following marked as NOTE:

- if the developer "creates" a new source file in the workspace using the new source file wizard they can assign whatever record length they need to the source file. This allows an lead programmer to create entirely new source files.
- Once the source file is "created" in the workspace its record length value cannot be changed in the properties dialog, but you could change it by directly editing the .properties file for the file if you absolutely had
to.
- Adding a source file to a project from a target IBM i system uses the record length value of the file on the system ("add to i project")

NOTE: The user still can change the record length by this way.

L2 NOTE on NOTE: Is it possible to lock this down so the user cannot change the record length in the .properties?

- Pushing a source file to a target system will use the record length value only for creating a file. It will never alter the record length of an existing file.
- Accepting properties from RTC will override anything the user has entered for record length for a given source file. RTC always wins. If the value
is changed by RTC it will be reflected immediately in the properties of the source file.

If this doesn't work for record length, can you propose how you would like it to work?

NOTE: The customer suggests: As the CCSID or record length is changed, the members in the SRCPF have to be re-pushed. Thus, the original SRCPF should be deleted and the new whole SRCPF should be pushed to the system i.