This topic describes how to start a single-service
wizard from the Remote Systems view.
Note: Only the Create New Service Interface (bottom-up) wizard is
available when you open the launchpad from this context.
This topic contains the following subtopics:
Starting the
single-service wizard
To start a single-service wizard from
the Remote Systems view:
- Open the Remote Systems view:
- On the main menu of the workbench, select .
- The Remote Systems view opens.
- Use the Remote Systems view to create a connection to MVS™ on the remote z/OS® system
(see Step B3(a). Create a connection to the remote z/OS system).
- Start the connection (see Step B3(b). Start the connection to the remote z/OS system).
- Expand .
- Right-click the partitioned data set that you want to use.
- Right-click a COBOL data set member file
(the file extension must be .cbl, .cob, .ccp, or .cpy).
- Select Enable Enterprise Web Service. The
Wizard Launchpad opens.
- In the Wizard Launchpad:
- Select the appropriate runtime environment, development scenario,
application mode, and conversion type.
- Click Start.
- The single-service wizard opens.
Differences in the Wizard Launchpad
and wizard pages
When you open the Wizard Launchpad in this
context you encounter the following differences as you work through
the wizard pages:
- On the Enterprise Service Tools Wizard Launchpad, the Save generation properties option
is not supported in this context.
- Warning or prompt about dependencies of copybook files on a COBOL
source file:
- If you right-clicked a COBOL source file (extension .cbl, .cob,
or .ccp) before opening the launchpad, then the Create New Service
Interface (bottom-up) wizard opens a window with the prompt, "Does your source file have any dependent files?"
- If your COBOL source file has dependencies on
COBOL copybooks, click Yes.
- Otherwise click No.
- If you right-clicked a COBOL copybook file (extension .cpy) before
opening the launchpad, then the Create New Service Interface (bottom-up)
wizard opens a window with the prompt, "For successful generation
from this copybook, the copybook should be self-contained".
- If you selected Compiled XML Conversion in
the launchpad:
- For all target runtime environments (Web Services for CICS®, Generate SOAP for CICS, IMS™ Enterprise Suite Soap Gateway, XML
Transformation for CICS, and
Batch, TSO, and z/OS UNIX System Services):
- In the File, data set, or member selection page:
- On the XML Converters tab:
- In the Converter file container field,
the default file container that is displayed is the PDS that contains
the COBOL source file that you right-clicked before opening the Enterprise
Service Tools Wizard Launchpad. You can type or select
a different file container.
- On the WSDL and XSD tab:
- The WSDL file container field is empty.
You must specify a file container in this field.
For the Web Services for CICS target
runtime environment:
- On the Web Services for CICS page, on the Basic
Options tab, the field WSBind file container is
empty. You must specify a file container in this field.
- For the IMS Enterprise
Suite SOAP Gateway runtime environment, on the Correlator
Properties tab, the field Correlator file container is
empty.
- Specify a PDS that has a record type of VB or
VBA.
- If you selected Interpretive XML Conversion in
the launchpad:
- On the page DFHLS2WS: High Level Language to WSDL Conversion,
on the tab Service Artifacts, the field File
container is empty. You must specify a file container
in this field.
Limitations when you open the launchpad
from the Remote Systems view
You should be aware of the
following limitations when you open the
Enterprise Service
Tools Wizard Launchpad from the Remote Systems view:
- The launchpad is available only if you right-click a remote COBOL
member on MVS.
- From the launchpad, only the Create New Service Interface (bottom-up)
wizard is available.
- On the launchpad, the Save generation
properties option is not supported in this context.
- The batch processor does not support this option.
Error detection and reporting
You
should be aware of the following information about error detection
and error reporting: