Migrating legacy applications (Cobol, PL/I) to Java on z/OS

  • View
    443

  • Download
    5

Embed Size (px)

Text of Migrating legacy applications (Cobol, PL/I) to Java on z/OS

  • Automated transformation to Java on z/OSOctober, 2015

  • http://www.eranea,com 2 / 21

    Agenda Solution highlights Proposal Architecture perspectives Conclusion

  • http://www.eranea,com 3 / 21

    Solution highlights

  • http://www.eranea,com 4 / 21

    Value proposition Incremental system migration approach

    automatic legacy code transformation to maintainable and iso-functional Java

    no freeze of application maintenance during migration

    replacement by equivalent system / admin tools Safe transformation process

    automated replay of test scenarios big-bang avoided through incremental safe steps leverage on existing HA features : Data

    replication, Sysplex, GDPS, etc.

  • http://www.eranea,com 5 / 21

    Solution fundamentals Iso-functionality: exact same results "to the last bit and

    pixel" produced during execution Replacement of CICS+BMS, SDF, JCL/JES2, DFSORT,

    ICETOOL, IDCAMS, SCF, SDSF, Interfacing with MQ, DB2, PdfLib, LDAP, SMTP, FTP, SOAP,

    REST, ... Live transactional data sharing: access to the same data

    sources during the transformation System tooling:

    industrialized and repeatable DevOps processes for continuous delivery and automated "hot" deployments

    advanced production monitoring / administration build & source code management and development tools

  • http://www.eranea,com 6 / 21

    Why iso-functionality ? Needed to guarantee the same results after

    transformation Critical to allow live sharing of same data

    sources between legacy and Java, enabling incremental migration

    Allows objective and quantified tests: all data produced by tests run in legacy (Cobol) and Java must be identical

    Transparency for end-users and other applications

  • http://www.eranea,com 7 / 21

    Incremental migration

    time

    DB2

    TP / batch

    z/OS

    DB2DB2shared data sources

    TP / batch

    z/OS CPs

    TP / batch

    zIIPs or (z)Linux

    incrementalmigration users & jobs

    maintenance in Cobolmaintenance in Cobol or Java

    start end

    TP / batchTP / batch(Java)TP / batch

    (Java)TP / batch

    (Cobol)TP / batch

    (Cobol)

    data sourcesdata sources

    z/OS CPs zIIPs or (z)Linux

  • http://www.eranea,com 8 / 21

    Tests automation Online :automated screens and data captures on the original system

    automated replays and captures on the Java systemadvanced automated comparison of screens and database changes

    Batch :automated captures (files, database changes) on the original system

    automated replays and captures on the Java systemadvanced automated comparison of produced data / files

  • http://www.eranea,com 9 / 21

    Architectural options

  • http://www.eranea,com 10 / 21

    Initial dependencies

    TPM(CICS, IMS)

    TP / batchApplication

    data sources(DB2, IMS-DB, MQ, etc.)

    z/OS(files, GRS, etc. )

    LPAR

    SYSP

    L EX

    DIS

    TRIB

    UT O

    R

    CF

    Cobol5

    1

    2 3 4

    datareplication

    5

    1 direct dependency1 indirect dependency

  • http://www.eranea,com 11 / 21

    Nota Bene Next slides describe a limited proposition

    of incremental migration steps

    Discrete stages described hereafter are excerpted of a larger paletteof possibilities: Cobol Java direct calling capabilities Java legacy interfaces (JNI, etc.) accessors / gateways to legacy (CICS

    CTG, IMS Open Connect, WAS Wola, etc.)

  • http://www.eranea,com 12 / 21

    Pipelined transformation

    ...

    start

    end

    time

    completion

    0%

    100%continuousprogress

    DMJava TPM WAS CLOUD Appl 1

    Appl 2

    Appl 3

    At time t, different applications may: - use a different pipeline - have a different target - be in a different progress stage

    DMJava WAS CLOUD

    Java TPM WAS

    DMJava CLOUD Appl N

    Java: Cobol to JavaTPM: TPM on z/OS as Java containerWAS: WAS on z/OS as Java container

    CLOUD: JAS on cloud as Java containerDM: Data migration (transformation)

  • http://www.eranea,com 13 / 21

    TPM on z/OS as container

    TPM(CICS, IMS, MQ)

    TP / batchApplication (Java)

    data sources(DB2, IMS-DB, MQ, etc.)

    z/OS(files, GRS, etc. )

    LPAR

    SYSP

    L EX

    DIS

    TRIB

    UT O

    R

    CF

    JVM (in TPM)

    runtimeJCICS / JIMS JDBC JZOS

  • http://www.eranea,com 14 / 21

    Achievements / benefits Required operations:Cobol to Javause of TPM Java APIs (JCICS, JIMS)use of z/OS java APIs (JZOS)use of standard Java data access (JDBC, MQ, ...)

    Benefits:platform architecture unchangeddevelopment in Java becomes possiblegenerate savings: CP zIIPs

  • http://www.eranea,com 15 / 21

    WAS on z/OS as container

    TP / batchApplication (Java)

    data sources(DB2, IMS-DB, MQ, etc.)

    z/OS(files, GRS, etc. )

    LPAR

    SYSP

    L EX

    DIS

    TRIB

    UT O

    R

    CF

    WAS

    runtime

    JDBC JZOS

  • http://www.eranea,com 16 / 21

    Achievements / benefits Required operations:Cobol to Java replacement of legacy TPM by WAS with implementation in Java (Eranea's runtime features) of CICS and IMS APIs

    use of z/OS java APIs (JZOS)use of standard Java data access (JDBC, MQ, ...)

    Benefits:platform evolution (Sysplex):

    legacy middleware support WAS support unchanged services: scheduling, SDR, etc.

    Java portabilitygenerate bigger savings: zNALC, additional CP zIIP offload

  • http://www.eranea,com 17 / 21

    JAS on cloud as container

    TP / batchApplication (Java)

    data sources(DB2, IMS-DB, MQ, etc.)

    z/OS(files, GRS, etc. )

    LPAR

    SYSP

    LEX

    DIS

    TRIB

    UTO

    R

    CF

    WAS

    runtime

    JDBC JZOS

    TP / batchApplication (Java)

    Linuxinstance SC

    WAS or other JAS

    runtime

    JDBC

    Private cloud

    WL

    MA

    NA

    GER

    NB: Private cloud can also be on System z via zLinux, LinuxOne, etc.

  • http://www.eranea,com 18 / 21

    Achievements / benefits Required operations:

    all actions for WAS as container design and implement a high-availability and

    high-performance transactional private cloud Benefits

    cost savings synergy: reuse of x86 Java platform (when it

    exists) new architecture: private cloud state-of-

    the-art

  • http://www.eranea,com 19 / 21

    Data migration (DM)

    WL

    MA N

    AGER

    SC

    TP / batchApplication (Java)

    Linuxinstance

    WAS or other JAS

    runtimeJDBC

    Private Cloud

    RDB

    JMSetc.

  • http://www.eranea,com 20 / 21

    Achievements / benefits Required operations:

    extract, transform and load data guarantee transparent mapping to

    legacy API Benefits

    additional savings legacy data formats (ex: IMS-DC)

    abandoned

  • http://www.eranea,com 21 / 21

    Thanks!

    Questions?

    send us a mail: contact@eranea.com

    Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21