Topic
  • 3 replies
  • Latest Post - ‏2012-08-10T20:03:39Z by Thampi
F85E_Rajesh_Jeyakumaran
5 Posts

Pinned topic CICS WebServices Using Channels & Containers

‏2010-11-18T05:24:00Z |
I am working on a CICS webservice project using channels and containers.

RDz prompts the user to enter the 'Container' name while generating Webservices programs (bottom-up).
I hope the same container name should be used in the CICS application program for the request & Response.

If i want to send back the response in multiple containers, how can it be done? Is it possible?

Also, it would be very helpful if any one share some documents related to developing CICS WS using Occurs Depending ON (variable arrays?

  • Thanks, Rajesh
Updated on 2012-08-10T20:03:39Z at 2012-08-10T20:03:39Z by Thampi
  • akkina9
    akkina9
    124 Posts

    Re: CICS WebServices Using Channels & Containers

    ‏2010-11-18T19:28:30Z  
    You can use CHANNEL DESCRIPTION DOCUMENT (CDD) interface when a Web service uses many containers in its application interface. You must first create a CCD to describe the containers. The channel description document is an XML document that conforms to a schema that is provided by CICS (http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.doc/tasks/dfhws_channeldesc.html). CCD is only valid for the CICS interpretive (bottom-up) conversion type and mapping level 3.0 and higher.

    In RDz, you will see CCD as an interface that you can pick in "The DFHLS2WS Application and Service properties page"
    http://publib.boulder.ibm.com/infocenter/ratdevz/v7r6/index.jsp?topic=/com.ibm.etools.est.doc/topics/tpxse_intbuprop.html

    Occurs Depending On (ODO) clause is not supported by interpretive solution. The following link helps you figure out what is & not supported in CICS interpretive (bottom-up) solution
    http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.applicationprogramming.doc/datamapping/dfhws_cobol2wsdl.html
    If you have a data structure that CICS interpretive does not support, you can write a wrapper program. See "Using a wrapper program" section at http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.doc/tasks/dfhws_designProvider.html

    ODO is supported in CICS Compiled (botton-up) solution. You will see "Compiled XML Conversion" as a conversion type during creation of Web Servies for CICS Project.
  • F85E_Rajesh_Jeyakumaran
    5 Posts

    Re: CICS WebServices Using Channels & Containers

    ‏2010-11-19T14:51:11Z  
    • akkina9
    • ‏2010-11-18T19:28:30Z
    You can use CHANNEL DESCRIPTION DOCUMENT (CDD) interface when a Web service uses many containers in its application interface. You must first create a CCD to describe the containers. The channel description document is an XML document that conforms to a schema that is provided by CICS (http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.doc/tasks/dfhws_channeldesc.html). CCD is only valid for the CICS interpretive (bottom-up) conversion type and mapping level 3.0 and higher.

    In RDz, you will see CCD as an interface that you can pick in "The DFHLS2WS Application and Service properties page"
    http://publib.boulder.ibm.com/infocenter/ratdevz/v7r6/index.jsp?topic=/com.ibm.etools.est.doc/topics/tpxse_intbuprop.html

    Occurs Depending On (ODO) clause is not supported by interpretive solution. The following link helps you figure out what is & not supported in CICS interpretive (bottom-up) solution
    http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.applicationprogramming.doc/datamapping/dfhws_cobol2wsdl.html
    If you have a data structure that CICS interpretive does not support, you can write a wrapper program. See "Using a wrapper program" section at http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.doc/tasks/dfhws_designProvider.html

    ODO is supported in CICS Compiled (botton-up) solution. You will see "Compiled XML Conversion" as a conversion type during creation of Web Servies for CICS Project.
    Thanks very much.
  • Thampi
    Thampi
    6 Posts

    Re: CICS WebServices Using Channels & Containers

    ‏2012-08-10T20:03:39Z  
    • akkina9
    • ‏2010-11-18T19:28:30Z
    You can use CHANNEL DESCRIPTION DOCUMENT (CDD) interface when a Web service uses many containers in its application interface. You must first create a CCD to describe the containers. The channel description document is an XML document that conforms to a schema that is provided by CICS (http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.doc/tasks/dfhws_channeldesc.html). CCD is only valid for the CICS interpretive (bottom-up) conversion type and mapping level 3.0 and higher.

    In RDz, you will see CCD as an interface that you can pick in "The DFHLS2WS Application and Service properties page"
    http://publib.boulder.ibm.com/infocenter/ratdevz/v7r6/index.jsp?topic=/com.ibm.etools.est.doc/topics/tpxse_intbuprop.html

    Occurs Depending On (ODO) clause is not supported by interpretive solution. The following link helps you figure out what is & not supported in CICS interpretive (bottom-up) solution
    http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.applicationprogramming.doc/datamapping/dfhws_cobol2wsdl.html
    If you have a data structure that CICS interpretive does not support, you can write a wrapper program. See "Using a wrapper program" section at http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp?topic=/com.ibm.cics.ts.webservices.doc/tasks/dfhws_designProvider.html

    ODO is supported in CICS Compiled (botton-up) solution. You will see "Compiled XML Conversion" as a conversion type during creation of Web Servies for CICS Project.
    Hello,

    Thanks for the information.
    Am using RDZ to create a CICS webservice provider which has multiple data structures and we are using multiple containers. Does RDZ has any feature which can be used to create a channel description document or does it need to hand coded?

    Thanks in Advance!

    Rahul