You can define more than one host connection in a service flow
project.
There are various scenarios
in which you might want to define multiple host connections in a service flow
project.
One possible scenario is that you have created a flow that controls a terminal
application (or possibly multiple terminal applications) on a single host
system, but you want to use this flow with several different host systems.
For example:
- Your are developing a flow that controls two terminal applications named
TermApp01 and TermApp02.
- These two terminal applications are available to users on several of your
host systems. (Both terminal applications are available on each host system.)
- You want to test your flow separately with each of the host systems. Or,
you want to generate runtime code for each of the host systems.
- Therefore, you create a different host connection file for each host system,
and you test the flow separately with each host system.
In this type of scenario, the terminal application (or multiple terminal
applications) that the flow controls are all available on each host system.
You test the flow with each host system separately. When you run the flow,
it connects to only one host system.
Another possible scenario is that you are developing an "aggregate flow"
that includes two or more individual flows, and each individual flow accesses
a terminal application running on a different host system. For example:
- You are developing an aggregate flow Flow01 that contains two individual
flows, Flow01A and Flow01B.
- Flow01A accesses a terminal application residing on one host system, HostA.
- Flow01B accesses a terminal application residing on a different host system,
HostB.
- Therefore you define two host connection files, one for each of the individual
flows.
Note: For an aggregate flow like this, which accesses terminal applications
on multiple host systems:
- Each host connection must reside in a separate terminal applications subproject.
- Of the runtime environments for which the service flow project tools can
generate runtime code, only the CICS® Service Flow Runtime environment supports
this type of flow.