12.1.4 Transferring necessary data that is not in the JP1/AJS3 shared directories
Data that is on the shared disk but not in the JP1/AJS3 shared directories must be transferred to the remote site while the system is operating normally. Because this data is not included in the copy process from the main site to the remote site, it must be transferred in a separate operation.
If the logical host names are different at the main site and remote site, make sure that the correct logical host name is specified when transferring data to the remote site.
- Organization of this subsection
(1) Data necessary for work tasks that is not located in the JP1/AJS3 shared directories
The following table lists the data that is not found in the JP1/AJS3 shared directories but is necessary for work task operation.
|
No. |
Necessary data |
Method of placement on remote site |
|---|---|---|
|
1 |
User applications executed as jobs |
Place the data on the remote site during normal operation. |
|
2 |
Data and files required by user applications |
Place the data on the remote site during normal operation. |
|
3 |
Execution environment for user applications |
Configure the environment on the remote site to allow user applications to be executed. Necessary settings might include OS user names and JP1/Base user mapping settings. |
(2) Transferring data necessary for work tasks that is not located in the JP1/AJS3 shared directories
The following figure shows an example of how to transfer program data and files that are not part of JP1/AJS3.
|
|
![[Figure]](GRAPHICS/ZJ120055.GIF)
Tolerance for site failures should be incorporated into the design of work tasks that access servers beyond the local host. For example, when designing a user application that communicates with the manager host, the application should include the appropriate error-handling capabilities or the ability to connect to the new manager host after operation switches to the remote site.