|
|
|
The following scenario illustrates how external writer support can be used.
CA XCOM Data Transport is directed to transfer SYSOUT between two z/OS hosts (MVS1 and MVS2). Each has an external writer (also MVS1 and MVS2) predefined by the other host system in their respective CA XCOM Data Transport Destination Tables, but not to JES. A problem might arise if a different JES destination (RMT2) on the remote host, other than the LOCAL predefined destination, was needed.
Note: The remote system and a particular destination on it form what is called a compound destination.
In this case, use both JES Destinations and External Writers. Direct CA XCOM Data Transport to scan for the external writer name only. When CA XCOM Data Transport finds work for the external writer (MVS2), it sends it on to MVS2, while informing MVS2 that the destination name is RMT2. The output created by this JCL on MVS1 is then printed on RMT2 on MVS2:
MVS1
.....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
#PSOTAB LU=APPLMVS2, X
WRITER=MVS2
//OUTPUT DD SYSOUT=(A,MVS2),DEST=RMT2MVS1
MVS2
.....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
#PSOTAB LU=APPLMVS1, X
WRITER=MVS1
//OUTPUT DD SYSOUT=(A,MVS1),DEST=RMT2
| Copyright © 2012 CA. All rights reserved. |
|