Comments for The Master Terminal http://themasterterminal.com All about CICS Transaction Server from those who produce and use it Wed, 14 Jul 2010 13:30:24 +0000 hourly 1 http://wordpress.com/ Comment on Ask a question by Steve http://themasterterminal.com/ask-a-question/#comment-611 Steve Wed, 14 Jul 2010 13:30:24 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-611 One more time, with parts of the tags removed, maybe it will post this time... wsdl:binding name="CICSSOAPBinding" type="tns:CjleadsWebSrvcPortType" soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" wsdl:operation name="getDmvData" soap:operation soapAction="https://someaddress:9999/CjleadsWebService" style="document" wsdl:input name="getDmvDataReq" soap:body parts="CjleadsWebSrvcReqMsgPart" use="literal" wsdl:input wsdl:output name="getDmvDataRes" soap:body parts="CjleadsWebSrvcResMsgPart" use="literal" wsdl:output wsdl:operation wsdl:binding wsdl:service name="CjleadsWebService" wsdl:documentation Web Service for data from DMV - CjleadsWebService.wsdl Copyright 2010 NCDOT. All rights reserved. Version: 1.0 2010-05-13 wsdl:documentation wsdl:port name="CjleadsWebSrvcPort" binding="tns:CICSSOAPBinding" soap:address location="https://someaddress:9999/CjleadsWebService" wsdl:port wsdl:service One more time, with parts of the tags removed, maybe it will post this time…
wsdl:binding name=”CICSSOAPBinding” type=”tns:CjleadsWebSrvcPortType”
soap:binding style=”document” transport=”http://schemas.xmlsoap.org/soap/http”
wsdl:operation name=”getDmvData”
soap:operation soapAction=”https://someaddress:9999/CjleadsWebService” style=”document”
wsdl:input name=”getDmvDataReq”
soap:body parts=”CjleadsWebSrvcReqMsgPart” use=”literal”
wsdl:input
wsdl:output name=”getDmvDataRes”
soap:body parts=”CjleadsWebSrvcResMsgPart” use=”literal”
wsdl:output
wsdl:operation
wsdl:binding

wsdl:service name=”CjleadsWebService”
wsdl:documentation Web Service for data from DMV – CjleadsWebService.wsdl Copyright 2010 NCDOT. All rights reserved. Version: 1.0 2010-05-13
wsdl:documentation
wsdl:port name=”CjleadsWebSrvcPort” binding=”tns:CICSSOAPBinding”
soap:address location=”https://someaddress:9999/CjleadsWebService”
wsdl:port
wsdl:service

]]> Comment on Ask a question by Steve http://themasterterminal.com/ask-a-question/#comment-610 Steve Wed, 14 Jul 2010 13:27:58 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-610 The wsdl was not posted, not sure why. Here are the pieces of the wsdl again... Web Service for data from DMV - CjleadsWebService.wsdl Copyright 2010 NCDOT. All rights reserved. Version: 1.0 2010-05-13 The wsdl was not posted, not sure why. Here are the pieces of the wsdl again…

Web Service for data from DMV – CjleadsWebService.wsdl Copyright 2010 NCDOT. All rights reserved. Version: 1.0 2010-05-13

]]> Comment on Ask a question by Steve http://themasterterminal.com/ask-a-question/#comment-609 Steve Wed, 14 Jul 2010 13:25:47 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-609 We are working to implement SSL with our CICS web service. We have had difficulty getting the service to work and I'm seeking some advice concerning the URLS for the CICSSOAPBinding and web service port parts of the WSDL. Should they both be https? We received errors when we ran with both https, but it worked when we removed the "s" from the CICSSOAPBinding URL. Is the service still encrypted at this point? Any ideas on the implications of removing the "s" here. The following are the relevant pieces of the wsdl... Web Service for data from DMV - CjleadsWebService.wsdl Copyright 2010 NCDOT. All rights reserved. Version: 1.0 2010-05-13 We are working to implement SSL with our CICS web service. We have had difficulty getting the service to work and I’m seeking some advice concerning the URLS for the CICSSOAPBinding and web service port parts of the WSDL. Should they both be https? We received errors when we ran with both https, but it worked when we removed the “s” from the CICSSOAPBinding URL. Is the service still encrypted at this point? Any ideas on the implications of removing the “s” here. The following are the relevant pieces of the wsdl…

Web Service for data from DMV – CjleadsWebService.wsdl Copyright 2010 NCDOT. All rights reserved. Version: 1.0 2010-05-13

]]> Comment on Ask a question by Guy Rich http://themasterterminal.com/ask-a-question/#comment-607 Guy Rich Thu, 24 Jun 2010 20:01:19 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-607 May I suggest you look very very closely at the log generated by the DFHWS2LS procedure. Again the log has a LOT of detail on the fields being built into the bind file, and the resulting COBOL copybook. Another approach is to construct a test COBOL copybook structure that reflects what you want the DFHWS2LS procedure to build. Then use the test COBOL data layout as input to DFHLS2WS (i.e. Language Structure to WSDL). Once that is done, then compare the resulting wsdl and bind files generated to the wsdl and bind file generated from the DFHWS2LS and note the differences. Unbounded maxoccurs DO NOT work well with COBOL; DFHWS2LS trys to "compensate" by defining really huge containers, that cause COBOL compiler failures. It's really better to delineate wsdl structures, i.e. make them fixed length. Also you don't need IBM ServiceLink to download the CICS TS 3.2 Web Services Guide. It's a "freebee". May I suggest you look very very closely at the log generated by the DFHWS2LS
procedure. Again the log has a LOT of detail on the fields being built into the
bind file, and the resulting COBOL copybook.

Another approach is to construct a test COBOL copybook structure that reflects
what you want the DFHWS2LS procedure to build. Then use the test COBOL data layout
as input to DFHLS2WS (i.e. Language Structure to WSDL). Once that is done, then
compare the resulting wsdl and bind files generated to the wsdl and bind file
generated from the DFHWS2LS and note the differences.

Unbounded maxoccurs DO NOT work well with COBOL; DFHWS2LS trys to “compensate”
by defining really huge containers, that cause COBOL compiler failures.
It’s really better to delineate wsdl structures, i.e. make them fixed length.

Also you don’t need IBM ServiceLink to download the CICS TS 3.2 Web Services Guide.
It’s a “freebee”.

]]> Comment on Ask a question by Steve http://themasterterminal.com/ask-a-question/#comment-606 Steve Thu, 24 Jun 2010 19:09:37 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-606 I'm working on access to ServiceLink, thanks. Do you know if every data structure in your wsbind syncs to a corresponding data structure in your copybook? We are getting a DFHPI1008 06/24/2010 14:36:44 CICSNCVU 00958 SOAP message generation failed because of incorrect input (INPUT_ARRAY_TOO_LARGE business10). but, there is no business10 in our copybook to fill. The same error came up for a veh4 as well. It seems that whatever utility is building the multiple data structures (and appending a counter to the end) in the copybook and wsbind is getting ahead of itself and creating one extra, which causes this cicsfault. I’m working on access to ServiceLink, thanks.

Do you know if every data structure in your wsbind syncs to a corresponding data structure in your copybook? We are getting a
DFHPI1008 06/24/2010 14:36:44 CICSNCVU 00958 SOAP message generation failed because of incorrect input (INPUT_ARRAY_TOO_LARGE business10).

but, there is no business10 in our copybook to fill. The same error came up for a veh4 as well. It seems that whatever utility is building the multiple data structures (and appending a counter to the end) in the copybook and wsbind is getting ahead of itself and creating one extra, which causes this cicsfault.

]]> Comment on Ask a question by Guy Rich http://themasterterminal.com/ask-a-question/#comment-605 Guy Rich Thu, 24 Jun 2010 14:03:16 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-605 Unbounded maxoccurs ... sounds like that may translate into a COBOL OCCURS DEPENDING ON. No I've never experienced such an issue. It sounds like a really good question to ask of IBM ServiceLink. Do you have access to IBM's ServiceLink Feature ?? Also please read CICS TS 3.2 Web Services Guide (SC34-6838-01) There's a sections that goes into a fair amount of detail maxoccurs and how DFHWS2LS handles such data structures. You can download the PDF version from IBM's website. Unbounded maxoccurs … sounds like that may translate into a
COBOL OCCURS DEPENDING ON. No I’ve never experienced such an issue. It sounds
like a really good question to ask of IBM ServiceLink. Do you have access to
IBM’s ServiceLink Feature ??
Also please read CICS TS 3.2 Web Services Guide (SC34-6838-01) There’s a sections
that goes into a fair amount of detail maxoccurs and how DFHWS2LS handles such
data structures. You can download the PDF version from IBM’s website.

]]> Comment on Ask a question by Steve http://themasterterminal.com/ask-a-question/#comment-604 Steve Thu, 24 Jun 2010 12:13:12 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-604 Have you run into any issues with "unbounded" maxoccurs in mapping from an xsd to a copybook? My theory is that DFHWS2LS is getting thrown off by these and created an extra structure for them in the wsbind, but not in the copybook. Have you run into any issues with “unbounded” maxoccurs in mapping from an xsd to a copybook? My theory is that DFHWS2LS is getting thrown off by these and created an extra structure for them in the wsbind, but not in the copybook.

]]> Comment on Ask a question by Guy Rich http://themasterterminal.com/ask-a-question/#comment-602 Guy Rich Wed, 23 Jun 2010 19:20:57 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-602 Hmmm well the Bind file is the "Rosetta Stone" that enables CICS web services to convert xml data structures into the corresponding Language Structure e.g. COBOL. I would look at the log produced when you run the DFHWS2LS procedure If you've run DFHWS2LS several time before, I suggest going into the USS sub-directory structure and deleting the old log (DFHWS2LS and DFHLS2WS both append to their respective logs), You can use the ISPF/OMVS edit feature to view the Bind file, However I would recommend NOT modifying it. The log does list every action that occurs while it's building the copybook and the bindfile. I also suggest opening a PMR with IBM via the ServiceLink Electronic Response. You can send IBM the log. Hmmm well the Bind file is the “Rosetta Stone” that enables CICS web services to
convert xml data structures into the corresponding Language Structure e.g. COBOL.

I would look at the log produced when you run the DFHWS2LS procedure
If you’ve run DFHWS2LS several time before, I suggest going into the USS sub-directory structure and deleting the old log (DFHWS2LS and DFHLS2WS both append
to their respective logs), You can use the ISPF/OMVS edit feature to view the Bind file, However I would recommend NOT modifying it.
The log does list every action that occurs while it’s building the copybook and
the bindfile.
I also suggest opening a PMR with IBM via the ServiceLink Electronic Response.
You can send IBM the log.

]]> Comment on Ask a question by Steve http://themasterterminal.com/ask-a-question/#comment-601 Steve Wed, 23 Jun 2010 19:06:33 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-601 Thanks, we've simplified it extensively, and have a good grasp on using the various containers. The issues is that there is a field defined in the wsbind that doesn't appear in the copybook. Because it isn't in the copybook, we can't populate it. Is there some way to determine why this appears in the wsbind? There isn't any real way to edit that file directly, so we can't just remove it. Without knowing why it is appearing, we can't fix the wsdl/xsds. Are there any good ways of seeing the contents of the wsbind and determining their origins? Thanks, we’ve simplified it extensively, and have a good grasp on using the various containers. The issues is that there is a field defined in the wsbind that doesn’t appear in the copybook. Because it isn’t in the copybook, we can’t populate it. Is there some way to determine why this appears in the wsbind? There isn’t any real way to edit that file directly, so we can’t just remove it. Without knowing why it is appearing, we can’t fix the wsdl/xsds. Are there any good ways of seeing the contents of the wsbind and determining their origins?

]]> Comment on Ask a question by Guy Rich http://themasterterminal.com/ask-a-question/#comment-600 Guy Rich Wed, 23 Jun 2010 18:47:37 +0000 http://masterterminal.wordpress.com/?page_id=26#comment-600 Hi Steve ... I also ran into this "issue" last year.. A query to IBM ServiceLink didn't help much ...essentialiy IBM say that it isn't a problem ...it's a "feature" ... We got around it by simplifying our wsdl document structure. If at all possible use character strings of fixed length. Hi Steve … I also ran into this “issue” last year..
A query to IBM ServiceLink didn’t help much …essentialiy IBM say that it isn’t a problem …it’s a “feature” …
We got around it by simplifying our wsdl document structure.
If at all possible use character strings of fixed length.

]]>