Move the resources using MVS Download

A third option is to move your AFP resources using the MVS Download feature of InfoPrint Manager itself. You can achieve this by setting up a MVS Download receiver that receives jobs and copies them into a particular directory without printing them. You would only use this receiver to move your resources. Setting up this configuration is different depending on your environment. Each time you modify a resource, you submit a job that sends the modified resource to each system that you are running an InfoPrint Manager server on. To accomplish this task, you might need to customize the JES inish deck, the Host MVS Download routing control data set, the Destination Control File (DCF), and the Exit Program. The modifications needed will depend on your existing MVS Download configuration used for sending jobs, although the process of getting the AFP resources to the InfoPrint Manager computer is the same in all cases:

1. Place the resource on the spool for MVS Download to process with identification that it is an AFP resource, the resource name, and the desired target path. (Target path is optional)
2. Set up the routing control data set to send the AFP resources to unique MVS Download receivers on the InfoPrint Manager system. (Optional)
3. Set up the routing control data set to not prefix each record with a record length field for AFP resources.
4. Set up the DCF to map the desired resource path/name to the target-destination-name. (Optional)
5. Modify the supplied Exit to copy the received AFP resource into the proper resource directory with the provided resource name. The full functions of this Exit would depend on the options chosen above. For example:
   1. If the target path was not supplied, the Exit would either need to have it hardcoded or determine it using other means.
   2. If both AFP resources and print jobs are being sent to the same receiver, the exit would need to distinguish between the two by some mechanism and take the proper action for each.
   3. If the DCF does not map the resource path/name to the target-destination-name, it will either need to parse it from the other parameters or determine it using other means.

This option is more difficult to set up than the other two, but is less time consuming once you have it implemented, because every time you change your AFP resources all you have to do is resubmit a job for transmission to your Windows systems. If you have multiple Windows systems to update or can further automate this process, this method might work well for you. One possible configuration example follows.