Documentation - DOKA-NG (Functional availability is per selected plan)

There are 3 codes removed from codetable LCRTYP. The codes are 'R', 'RT', and 'S'. Please ensure that there is no contract defined with such a lcrtyp. Therefore execute the sqls defined in the copymaster\tmp\sql299.txt. And if contracts are found, change the lcrtyp of that contracts manually to another lcrtyp or eleminate and archive that contracts.

We created a so called “Copymaster” per product.

These “copymaster” environments are stored in s:\dok5ovly\sr2018_copymaster_<product>.

A “copymaster environment” contains all relevant changes connected to the SWIFT 2018 update.

The “frame files” contain only the changed sources (other than in overlays, where frame files contain the full set of rules on the current security level).

The “other files” contain the complete content, not only differences.

The single steps to merge and activate the SWIFT update into an existing customer version are

• create 2 new “work environments” for the customer,
  one “master” i.e. mmhsf100_sr2018_master
  and one “target” i.e. mmhsf100_sr2018
• copy all files from “copymaster” s:\dok5ovly\sr2018_copymaster_<product>
  into “master” mmhsf100_sr2018_master

• The idea for the merge is, that every file in the “master” has to be handled.
  Depending on the file type it either has to be
  • moved to the “target” update environment (complete bin directory)
  • checked in to the “target” work environment
  • merged into the “target” work environment by using GENXFS

• start GENXFS in the “target” work environment (i.e. mmhsft100_sr2018)
• select the “master” 'mmhsf100_sr2018_master' as source environment
• As “Select Type” choose 'Mod. + Scr.Orphan'
• select the first file in the list as source file
• Check it out (using [Checkout]-Button)
• if a file does not yet exist in the customer environment click on [Create Empty]
• [Move] all elements inside the list, one after the other
• [Move all] all elements in a single step
• choose the next file and proceed the same way as before
• repeat the previous steps, until all files are processed

–> first target is, that the “master” is completely empty and all relevant files are in the “target” work environment

• start a global compile from this “target” work environment and clean up all compile errors, maybe you have to merge customer specific logic into the merged product rules
• Check the sources in the “target environment” with tdvcs, maybe you find more customer specific logic which needs to be 'remerged'

• check out Tdpara,ini; import tdpara.ini.dif with sysupd
• import ct.lcrtyp.xmu and ct.srvtxt.xmu with sysupd too
• Migrate the connected database with sysdba and run [reorg nrm] afterwards (DNG customers only)
• Import the mapping

–> test the result. You should NOT get the infodump which says SWIFT2018 is not completely available.

–> test the result using the test instructions in Business Information