IBM Z and LinuxONE Languages

Languages

Languages

Broad range of supported development languages and tools allows to transform software delivery practices.

 View Only

  • 1.  zosconnect import does not handle COBOL POINTER fields

    Posted Thu May 21, 2020 02:21 AM
    Edited by Dan Zhang Thu May 28, 2020 05:43 AM

    Disclaimer: This post is migrated from IBM Developer Answers that is no longer in use. Its original author is Mark Salter, posted on May 10, 2018.

    Hit a problem importing a cobol copybook that includes :-

    002100
    002200 05 SRSDMLK-INPUT-DATA
    002300 POINTER.
    002400
    002500 05 SRSDMLK-OUTPUT-DATA
    002600 POINTER.

    The pointers are not liked :-

    com.ibm.zosconnect.ui.programinterface.controllers.exceptions.UnsupportedCobolTypeException: Data structure "SRSDML" has been omitted because field "SRSDMLK_INPUT_DATA" has unsupported type "COBOLAddressingTypeImpl,,pointer". at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.createUnsupportCobolTypeException(TranDataStructureParser.java:1362) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseSimpleModel(TranDataStructureParser.java:1122) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseElementModel(TranDataStructureParser.java:268) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseComposedModel(TranDataStructureParser.java:505) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseElementModel(TranDataStructureParser.java:274) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseComposedModel(TranDataStructureParser.java:505) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseElementModel(TranDataStructureParser.java:274) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureParser.parseCobolCopyBookModel(TranDataStructureParser.java:119) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureController.handleCOBOLFile(TranDataStructureController.java:1211) at com.ibm.zosconnect.ui.programinterface.controllers.datastructure.TranDataStructureController.parseApplicationSourceFile(TranDataStructureController.java:246) at com.ibm.zosconnect.ui.programinterface.wizard.importds.ImportDSTranMessageMetadataWizardPage$9.run(ImportDSTranMessageMetadataWizardPage.java:597) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)


    are POINTERs not supported?

    -------------------------------------------------------
    Question asked by Mark Salter on May 10, 2018
    -------------------------------------------------------



  • 2.  RE: zosconnect import does not handle COBOL POINTER fields

    Posted Thu May 21, 2020 02:23 AM
    Edited by Dan Zhang Thu May 28, 2020 05:57 AM

    Hi,

    Can you tell me which version of the API Toolkit you have installed in eclipse? Head over to your Eclipse -> Help -> About -> Installation Details and look for the IBM z/OS Connect EE API toolkit feature.

    I am at 3.0.4. There were problems with POINTERS addressed back at version 3.0.1 which suggests you may be back level and need to update your plugin.


    ---------------------------------------------------
    Replied by Andy_Armstrong on May 10, 2018
    ---------------------------------------------------





    Original Message


  • 3.  RE: zosconnect import does not handle COBOL POINTER fields

    Posted Thu May 21, 2020 02:35 AM
    Edited by Dan Zhang Thu May 28, 2020 05:55 AM
    This is the approach I took.

    I figured the actual replacement definition might vary with POINTER length (thinking 64-bit) so the user might need to check the compiled code for the length needed.

    That said, the import process should substitute instead of rejecting - but perhaps the 31/64-bit aspect is a blocker.

    ----------------------------------------------
    Replied by Mark Salter on May 11, 2018
    ----------------------------------------------





    Original Message


Related Content