To generate the labels on one CPU and route the label image to another CPU to print, use the CAICCI Destination assignment.
If this is the case, have two LAB subtasks running under CTS; one on the sending CPU and one on the receiving CPU. Additionally, the two CPUs need to be on the same CAIENF/CAICCI network to facilitate the cross-CPU communications.
Note: For more information about establishing CAIENF/CAICCI networks, see the CA Common Services for z/OS Administrator Guide.
A CAICCI destination code may be entered if you want the output processor to route the label image to another common tape labels started task on another CPU. The value entered in this field must contain CA$FO immediately followed by the four-character CPU identification where the receiving Common Tape labels started task is executing. The output processor validates the CAICCI Identification entered is up and operational before sending the label request through CAICCI Communications to the secondary label processor. No output assignments are propagated on label requests sent using CAICCI services. Any existing assignments can be modified by using the SET statement.
The ORIG_ID field contains the originating CAICCI Identification of the current request. SOURCE_ID contains a one-position value to identify the source of the current request. Possible values are B (Batch) or O (Online). These two fields can be used by the CA Earl program to select labels for printing.
If none of these outputs are requested, PRINTER1 is used by the output processor to print all label images.
Note: The delivered sample (TMELBLS) does not establish any output options, so label images for both REEL and CART densities (setup and actual labels) default to the same output (PRINTER1). If you use both REEL and CART densities,modify a copy of the sample to establish a different output for each type of label being generated.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|