Additional Information can be found in Technical Release Upgrade.
This documentation is written while we did our first DNG Upgrade Project in 2018. This might be not that easy in case you upgrade an older Doka Version. A lot of times we are refering how we did it. It might be growing over the time with information we're collecting from other upgrades.
ask for the ini-directory of their production system. This includes ini-files, tdps' (user profiles) and so on. aks as well for codetables (export all codetables in SYSTBL)
Possible Structure:
| What | Goal | Comment | Resp |
|---|---|---|---|
| Estimation | |||
| Gap-Workshop | Showing the customer the new version in one week | It is useful to give the customer a Online Version with Demo Data if they are interested | PM |
| Project Plan | Define project Plan with Customer | timeline/milestones, start/end of project, outline test cycles, include personal ressources | PM |
| Kickoff | internal + external Kickoff with relevant stakeholders | Project team is set + timeline, set weekly calls with customer PM + Steering Commitee calls | PM |
| Start of Development | The overlay will be copied on a specific date and if development takes place in old environment we have to make sure to keep the sources up to date (MRG step in DO5-SERs for DNG environment) | It make sense to make the customer clear that change requests for DO5 Environement should be moved to after DNG Golive. Only High Level Production Issues should be fixed. Otherwise we have to keep track the whole upgrade project about MRG steps. | Dev with QA2 permission |
The new Viewtype “combogrid” and other features of DNG require an Unicode Server. You might have to go from Standards Server to Unicode with the upgrade.
1. Setup a Customer Version on source drive (e.g. S:\dng101\xxx101)
2. Copy overlay from old instance (in our case S:\d50600s2\xxx50xxxfrz\frame\) to new instance ( in our case S:\dng101\xxx101\frame\)
3. Checkout overlay in newly set dng workenvironment
Using GENXFS copy 'In Src Only' Frames and Code starting with ???.fr5, ???.fr6, *.tr8, *.fr8, *.tr5, and *.fr5 → This means accepting DNG changes that do not exist in Doka 5.
Using GENXFS copy 'Modified' Frames which are not client specific. Only for ???.fr5, ???.fr6, *.tr8, *.fr8, *.tr5, and *.fr5 → This means accepting DNG specific frames/code/panels etc where no client specific changes exists.
Start Client DNG trade2 Environment in design mode and delete all fields and Labels that appear in red, BUTPANs (Button List on the right of Panels in Doka 5), and Bevels (simple lines or borders/frames on panels)
Compile transactions starting with static data transactions (DBxxxx) and then what is relevant for the Client (i.e. if customer uses Export Products the most so start with LE* and BE* for compiling. They were able to test Export Products while we continued compiling other transactions.)
| Transaction | Question / Error | Answer | Comment |
|---|---|---|---|
| BRTPAY | FPDGRP module in 50600, but not anymore in DNG101 | FPD is no longer supported in DNG101. Thus please remove it and clear the usage afterwards. | |
| DBAOIT | Reverts to the Office. Never loads the transaction | ||
| DBIDIA | Error: Illegal assignment in Ownusr (1100) default rule. USRGET/SEAKEY is not declared as OUT-field | ||
| DBLGTX | Error: Length of key for keytable LEGFRM (0) differs from lenght of field SELLEGFRM (3). | ||
| MGRTSK | SRVTSU is that still needed? | SRVTSU is supported in 50600, not in DNG101 anymore | Check with customer if they really don't use it |
| SYSDBA | Popup: Delete the following module(s) from ALL list in sysdba.ini? This modules do not exist in sysdba (any more.) PTYLNK | ||
With DNG the Style changed completely compared to Doka 5. See the Styleguide for details.
Following things has to adopt to DNG Style:
* Bevels
* Buttons
* Labels (right aligned)
* Field positions
To quickly identify in all overlay sources of your customer those frames, you can search via
http://hhcentfs/scripte/findframe.php
Enter in “Suchpattern” the keyword and select the directory of your customer in the drop down.
| Subject | keyword for “Suchpattern” | Comment | Example | Example |
|---|---|---|---|---|
| Bevel | FrameObject 5 | Bevels needs to be deleted. | ||
| Buttons | FrameField | First: get the list and second: Search in the list for “ 6 ” because this identifies Buttons (don't forget blanks before and after “6”) | FrameField BCTP\RESREJ\BUTTXMSEL 6 455 316 1 0 0 0 1 0 0 0 {-} | |
| Labels | Label | check, if last byte is 1 and check, if field position is correct (in most cases 126) | Label S0000008 118 28 1 {-} | Label S0000013 0 44 0 {-} |
| BUTPAN | BUTPAN | Buttonpanels are not existing anymore in DNG. They have to be deleted. | FramePanel BUTPAN PF000044 68 528 0 0 1 0 0 0 0 1 | |
| Streamgrids with Buttons | tdviewtypebutton | All grids in the customer overlay has to be modified according DNG Style (Sourcecode in init of grids + Buttons to Bitbuttons in Grids). |
tdp files
To do the first Delivery we have to:
1. Prepare new Packlist - .mod-File
1.1 Copy old packlist and exchange do5 modules with dng modules on anwxxx/sec-Folder
1.2 Get new SN-Number from Office Management
1.3 With new SN-Number we get a new SECKEY, which needs to be delivered to customer as well
2. In GENMKP is now next
Issues which came up with first time migraton via SYSDBA
| No. | Error | Answer/Solution | Comment |
|---|---|---|---|