This topic describes how to detect and
resolve various problems that you might encounter in running the completed
Web service for the tutorial in the Web Services Explorer.
Also see the following sources:
JCL errors
- How can I check for JCL errors?
In this scenario you have run the Generate Runtime
Code wizard for CheckAvailabiltyGP.sfgen or
for CatalogOrderGP.sfgen and you have checked
the output in the Runtime Generation Complete window
and have found no errors.
What should I do if I get a JCL error?
In this scenario you have run the Generate Runtime
Code wizard for CheckAvailabiltyGP.sfgen or
for CatalogOrderGP.sfgen, you have opened the
output files under the most recent job ID, and you have found JCL
errors.
Follow these steps:
- Open the generated JCL file, either SAMPCAPN.jcl or SAMPCIPN.jcl.
There are two copies of this file:
- A local copy in the generation output directory in the EST Project
Explorer, such as:
- A remote copy in the data set that you specified in the wizard.
This file should be visible in the Remote Systems view, for example:
- Determine what changes need to be made to the JCL. You may need
to consult with your system administrator.
- Modify the appropriate components of the service flow project
so that the Generate Runtime Code wizard creates a correct JCL file:
- Review the JCL template DFHMAXCJ (see Obtain customized JCL templates from your system administrator):
- Verify that the programs specified in the JCL template are correct
and valid for your remote z/OS® system.
- Verify that the JCL template is customized throughout (see Obtain customized JCL templates from your system administrator).
For example, the following JCL errors were caused by the fact that
a valid string was not substituted for one instance of the qual place-holder:
STMT NO. MESSAGE
11 IEFC620I UNIDENTIFIABLE CHARACTER q ON THE DD STATEMENT
11 IEFC620I UNIDENTIFIABLE CHARACTER u ON THE DD STATEMENT
11 IEFC620I UNIDENTIFIABLE CHARACTER a ON THE DD STATEMENT
11 IEFC620I UNIDENTIFIABLE CHARACTER l ON THE DD STATEMENT
- Verify that the values that you will specify in the Job
Control Information group on the first page of the Generate
Runtime Code wizard are correct (see Step 5.4: Run the Generate Runtime Code wizard for each of the two generation properties files).
- Run the Generate Runtime Code wizard again for the appropriate
generation properties file and check for errors.
Compiling
and linking
- How do I check for compile errors and link errors?
In this scenario you have run the Generate Runtime
Code wizard for CheckAvailabiltyGP.sfgen or
for CatalogOrderGP.sfgen and you have checked
the output in the Runtime Generation Complete window
and have found no errors.
To check for compile
and link errors:
- In the Remote Systems view, refresh My Jobs and
then expand the job ID for the most recent job (see The My Jobs node in the Remote Systems view).
- Open the output files under the Job ID and check for errors.
What should I do if there are informational
messages in the compile or link listing?
In
the compile and link listing for SAMPCIPN, the following informational
messages typically are harmless:
IGYLI0090-W 398 sequence errors were found in this program.
1929 IGYDS1073-I "LINK3270-REQUEST-0" redefined a larger item.
3047 IGYDS1158-I A non-level-88 "VALUE"
clause was found in the "FILE SECTION" or "LINKAGE SECTION".
The "VALUE" clause was treated as comments.
In the compile and link listing for SAMPCAPN,
the following informational messages typically are harmless:
What should I do if there is an error message
in the compile or link listing, but the corresponding content of the
project appears to be correct?
For example,
suppose that you get the following error message:
3494 IGYPS2121-S "VARIABLE0 OF V-CHECKITEMAVAILABILITY" was not defined
as a data-name. The statement was discarded.
However,
when you open you
see that the variable
variable0 is in fact defined.
To resolve this type of problem, try the following:
- Clean the project:
- On the main menu of the workbench click . The Clean window
opens.
- In the Clean window:
- Click Clean projects selected below.
- Click the entries for CatalogSample and
its subprojects.
- Click OK.
- Wait for the project to be cleaned. On the workbench's status
line, the message Building workspace: (0%) increases
to 100% and then closes when the project is cleaned.
Run the Generate Runtime Code wizard again.
Testing the Web service: connection
problem
- What should I do if I get a "Connection timed
out" message?
In this scenario, after you click
Go in
the Actions view of the Web Services Explorer, the following message
is displayed in the Status pane:
IWAB0135E An unexpected error has occurred.
java.net.ConnectException
Connection timed out: connect
Follow
these steps:
- Open CatalogOrderGP.sfgen in the generation
properties editor.
- In the End Point URI field, verify that
you have specified the correct host name and port.
- Close the generation properties editor.
- Re-run the Generate Runtime Code wizard for CatalogOrderGP.sfgen and
check for errors as usual.
- In the Web Services Explorer:
- Clear the current file entry for SAMPCAPN.WSDL -- in the Navigator
view:
- Right-click the WSDL file entry for SAMPCAPN.WSDL.
- In the upper right corner of the view, click the Clear icon.
The file entry is removed.
- Create a file entry for the new SAMPCAPN.WSDL file (Run the Web service).
- Run the Web service.
Testing the Web service: creation
of the Web service
- What should I do if the Web service is not found?
In this scenario, after you click
Go in
the Actions view of the Web Services Explorer the request is completed
very quickly and there is no information displayed in
Form mode
of the Status pane. You find the following information in the SOAP
response envelope (see
SOAP request and response envelopes):
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>s:Server</faultcode>
<faultstring>Resource http://mvs040.rtp.raleigh.ibm.com:
6182/user25/sampcapn not found</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
Follow these
steps:
- Log on to CICS using the
host connection emulator (see The host connection emulator) or using a host connection
that you created in the Enterprise Service Tools perspective.
- Use the cemt transaction to view information about the
existing Web services (see cemt).
- Page forward until you find the sampcapn Web service. The entry
should look something like the following:
Webs(sampcapn ) Pip(CICSSFRP)
Ins Ccs(00037) Uri($331390 ) Pro(DFHMADPL) Cha Xopsup Xopdir
- Verify that the Web service (sampcapn) is associated
with the correct pipeline (in the example above, CICSSFRP).
Note: It
can happen that a Web service with the same name (sampcapn)
as the new Web service that you are trying to create has already been
defined using a different pipeline (such as DFHMASFP)
than the pipeline that you want to use. If so, then CICS will not create your new Web service because
it already exists.
- You can also look for an error message in the MSGUSR file (see The MSGUSR file for the CICS region), such as:
DFHPI0916 E 12/04/2008 12:14:42 NQA17C01 USER25 WEBSERVICE
sampcapn within PIPELINE CICSSFRP was not created
because it clashes with another WEBSERVICE of the
same name in PIPELINE DFHMASFP.
- If the pipeline is not the correct one:
- Use the cemt transaction to discard the
existing Web service definition (sampcapn).
- Run the Generate Runtime Code wizard again for CatalogOrderGP.sfgen.
(Be sure to set the same options as are described in this tutorial
-- see Run the Generate Runtime Code wizard for CatalogOrderGP.sfgen).
Check for errors as usual.
- Run the Web service in the Web Services Explorer.
What should I do if a resource is not created?
In this scenario, after you click
Go in
the Actions view of the Web Services Explorer, the request fails and
you find the following information in the SOAP response envelope (see
SOAP request and response envelopes):
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>DFHMA06021E</faultstring>
</SOAP-ENV:Fault>
The error code DFHMA06021E signifies that an error
occurred in creating the PROCESSTYPE resource. (The error codes are
documented in CICS Service
Flow Runtime User's Guide.)
Follow these
steps:
- Verify that the files shown in Table 1 have been
copied to the correct directories in z/OS UNIX® System Services.
- Verify that the files have been copied to the correct directories.
The files should be visible in the Remote Systems view under th z/OS
UNIX node.
- Consult with your system administrator to verify the directories.
Table 1. Locations of files on z/OS UNIX System
Services| Type of file: |
Examples: |
| Both the .SFP files: |
/u/cicsts32/csfr/flowfiles/SAMPCARN.sfp
/u/cicsts32/csfr/flowfiles/SAMPCARN.sfp
|
| The WSBIND file and the WSDL file for the Web
service: |
/u/cicsts32/webservices/wsbind/cicssfrp/sampcapn.wsbind
/u/cicsts32/webservices/wsbind/cicssfrp/sampcapn.wsdl
|
- Verify that you the pipeline that you select on the third page
of the Generate Runtime Code wizard is the correct pipeline, such
as:
Table 2. Pipeline example| Pipeline name: |
Pickup directory: |
| CICSSFRP |
/u/cicsts32/webservices/wsbind/cicssfrp |
- You can also look for completion messages and error messages in
the MSGUSR file (see The MSGUSR file for the CICS region).
Here are a two examples of successful completion messages:
DFHPI0910 I 12/05/2008 19:51:30 NQA17C01 USER25 WEBSERVICE sampcapn
within PIPELINE CICSSFRP has been created.
DFHPI0915 I 12/05/2008 19:51:30 NQA17C01 USER25 WEBSERVICE sampcapn
is now INSERVICE and is ready for use.