EngageOne

Migrating Generate to Windows/Linux ? The challenges and how to overcome them

  • 1.  Migrating Generate to Windows/Linux ? The challenges and how to overcome them

    Pitney Bowes
    Posted 04-17-2019 07:45
    What are the challenges when migrating your EngageOne Generate applications to Windows / Linux and how to resolve them

    Getting your Data right up front

    When first importing your Keyed or Delimited data in Designer Data Format Editor (DFE) , users have the option to choose between the codepage definitions :
    • Host Default (Default setting) - Use the Generate Host operating system codepage to define the Data codepage
    • Explicit Windows / ISO / EBCDIC codepage - Choose an  explicit codepage from a wide range of encodings 
    Which option is best for my data ?
    • Host Default is suitable for Data where the data is common across Windows and Non Linux UNIX Operating Systems - Example : Windows 1252 is common among these Operating systems.
    • Explicit Windows / ISO / EBCDIC Codepage - If the data is expected to be migrated between different Generate Host operating systems. This allows the existing HIP / Data to be ported without issue between Windows / UNIX / Linux / Mainframe Operating systems.

    I've used "Host Default" in DFE, but  now want to Migrate my Generate Operating System , what are my options ?

           Non Linux UNIX (AIX, Solaris, HP) to Linux
           When migrating from AIX, Solaris or HP UNIX to Linux x64 Generate , the Operating System "Host Default" codepage will usually change              (e.g ANSI / Windows 1252 to Unicode / UTF-8) and can result in either incorrect or aborted output.

          Use the Generate command line "Set Code Page" override "SCP" option to resolve this :
          Example : if your data is using an ANSI / Windows codepage on a Linux Generate Operating System , use

           doc1gen myapplication.hip ops=myapplication.ops SCP=1252

          Please review the full list of Generate "Set Code Page" overrides available in Appendix A within

         Generate Production Guide (link)

           .. to find the correct Generate SCP value appropriate for your Data codepage.

         Mainframe (Z/OS or OS/400) to Windows / Linux (x64)
         When migrating from Mainframe Operating Systems (Z/OS or OS/400) to a Windows / Linux x64 version, you will need to

    1. Establish the EBCDIC codepage used by the source Data / Operating System
    2. Establish the equivalent  Linux x64 codepage relevant for the Data 
    3. Use a third party download package to Translate the Data from the source Mainframe (EBCDIC) codepage to the Target (Windows / ISO / Unicode) codepage
          Note : Usage of Generate "SCP" override for EBCDIC codepages on Windows / Linux(x64) Operating systems is NOT supported


        Publish for Generate Journal / Lookup Table Code Page review    If your Generate HIP has been published using the "AUTO" (Host Default) Journal codepage :

        Migrating from Windows / UNIX options;
    •      Use the relevant Generate "SCP" codepage override to specify the correct language / codepage, OR
    •      Republish the HIP with the codepage setting updated for the relevant Journals / Lookup Tables

        Migrating from Z/OS or OS/400  option:
    • Republish the HIP with the codepage setting updated for the relevant Journals / Lookup Tables



    ------------------------------
    Paul Barron
    Principal QA
    EngageOne Compose (Designer / Generate)
    Watford, United Kingdom
    ------------------------------