Main concepts

After ensuring that the Prerequisites are managed, the transformation process can begin.

  1. Build the list of fields to process serving as the platform for automatic propagation and modifications.

    2. Field lists

  2. Configure the propagation.

    3. Working with the TRANSFORM menu: Propagation and Transformations

  3. Run the propagation without modification (#1-2).
  4. Analyze the quality of the propagation (list of anomalies, etc…).

    5. Detecting anomalies generated by propagation

  5. If the quality is not satisfactory, do whatever is necessary to improve it and go back to #3.
  6. Use the results.
  1. Repeat #1 to 5 above to ensure the quality of the propagation.
  2. Configure the types of automatic modifications (extension or addition of file fields, automatic modifications in the programs, behavior for display/printer fields, ...).
  3. Configure the file read/write, screen display/enter routines if necessary.
  4. Delete the lines already marked in AWRKFRMCHG.
  5. Run the modification of PF sources: ACVTDBFFLD.
  6. Run the propagation with automatic program modifications: ACVTPGMFLD(#1-3).
  7. Run the automatic modification for display/printer fields: ACVTDDSFLD.

  8. Apply the modifications: AAPYFRMCHG.

    If, at this stage, you see that the inserted routines are not correctly configured, it would be better to restart the whole process rather than making manual modifications in all the programs!

  9. Consult, then compile the PF (and LF) modifications.
  10. Consult, then compile the DSPF/PRTF modifications.
  11. Consult, then compile the program modifications.
  12. Test, correct, etc.
  13. Transfer to test and/or production and distribute to sites.
Note

When extending a file field (or even if no action is carried out on file fields), you can avoid re-executing the entire propagation and only run #3 (having kept the marked lines).

Reference

It may be necessary to generate the recovery programs on the files in case the PFs were modified. For more information about this, refer to Recovering data.

Data recovery programs automate a specific process which should be run for all the data contained in the file’s fields, which are contained in the list of fields to be processed.

You can generate and run data recovery programs:

  • just after building the list of fields to be processed (if you are absolutely sure it’s complete),
  • after propagating, with a detailed impact analysis, and completing the list of fields to be processed (following the analysis of the anomalies list), or
  • after running and applying the automatic modifications, and after compiling the new PF in the version.
  1. Configure the standard process routine to run for each field.
  2. Generate these recovery programs (with compilation).
  3. Execute the test files (in the version library).
  4. Execute the actual files at specific dates in specific environments.

ARCAD Transformer Field prioritizes the quality of the transformation results. It is important to verify the quality of the propagation results (with the anomaly lists) before using the transformed data. You run the risk of propagating incomplete or incorrect data if you exploit it immediately without analyzing the eventual anomalies detected.