modernize problem with DDS logical

We are slowly modernizing our database and programs as business needs arise. We would like to leave some of our old RPG III programs alone since they work and will eventually be replaced. We are trying to do this by using dds logical files over the newly modernized data base.

We modernize the database with DDL in ops navigator and add new fields to the end like real dates, identity columns, sometimes a time stamp, and new stuff with long field names. We keep the original 6 character field names on the existing fields as system name. Any new fields get both a long name and a system name that is longer than 6 characters. Then we use the old physical file name as a logical file.
The new physical, since created with DDL, does not have any DDS specs. (AROPENSY in the example below)

We then modify this new DDS logical( that used to be a physical) to include only the old fields with each old field name listed. And of course the key, which has not changed and is an old field. New fields are not listed in the dds.
sample:

A* RECORD FORMAT LEVEL
A UNIQUE
A R ARREC PFILE(AROPENSY)
A*
A ARCODE
A ARPRFX
A ARMNTH
A ARSNBR
A ARCMCD
A ARSUPL

The RPGIII programs get compiled for the new logical and some but not all programs got errors.

we get errors like:External-Field-Name entry longer than 6 or
Message . . . . : The record format contains DATE/TIME/TIMESTAMP fields. DATE/TIME/TIMESTAMP fields ignored.

When we run DSPFFD on the logical, it shows all the fields, the old with old names, but also the new fields longer than 6 characters that RPGIII does not like.


How can I create a logical file with only the old field names yet points to my new modern database defined by DDL?

Do I have to create views in DDL? Is it not possible to mix DDL with DDS?

I was hoping to ease into some of these new features, without having to change every program all at once. So far, I am not doing so well. Yes, I realize I should just change everything, but there is never enough time.

---Dale

I