Using Enterprise Service Tools, you can generate artifacts
to MVS™ and z/OS® UNIX System
Services on a remote z/OS system.
To
generate artifacts to a remote system, use the Browse button
on any of the wizard pages that allow you to browse to a target file
container.
Table 1 shows
the possible targets for file containers.
Table 1. Possible target(s) for artifacts| Enterprise Service
Tools Artifact |
Target |
| Local Projects |
MVS Offline
Projects |
MVS Projects/System |
z/OS UNIX System
Services System |
| Converters/Driver |
Y |
N |
Y |
Y |
| XSD/WSDL |
Y |
N |
N |
Y |
| WSBind |
Y |
N |
N |
Y |
| XML Correlator |
Y |
N |
Y |
N |
In the container selection window, expand:
- MVS Projects
- To show PDS's that are associated with it.
- MVS Subsystems
- To show filters, which, when expanded, shows the PDSs that are
not migrated or on an offline volume
- z/OS UNIX System Services Subsystems
- To show the ROOT, which, when expanded, shows z/OS UNIX System
Services folders
- MVS offline Projects
- To show the folders that were FULL PDS's before going offline
- Local Projects
In the file selection page
When you select a remote
artifact, IBM® Rational® Developer for System z® uses the following naming convention for the location path
for remote artifacts.
- For z/OS Project PDS -> MVS Project Name/HLQ.PDS.COBOL
- For MVS File Sub System ->
HLQ.PDS.COBOL
- For z/OS UNIX System Services File
Sub System -> /u/temp (the first '/' represents
ROOT)
Table 2. Validation rules| Enterprise Service
Tools Artifact |
Target |
| MVS Offline
Projects |
MVS Projects/System |
z/OS UNIX System
Services System |
| Converters/Driver |
Offline PDS selected must have record type of
F or FB. |
PDS selected must have record type of F or FB. |
Verify write access |
| XSD/WSDL |
Not applicable |
Not applicable |
Verify write access |
| WSBind |
Not applicable |
Not applicable |
Verify write access |
| XML Correlator |
Offline PDS selected must have record type of
VB or VBA |
PDS selected must have record type of VB or
VBA |
Verify write access |