Creating an MVS Download Receiver
- Open the InfoPrint Manager Management Console.
- On the menu bar, click Edit → New → MVS Download Receiver. The Add MVS Download Receiver dialog opens.
- Fill in the fields according to these specifications. For
more information about the dialog and the fields it contains, see
the Management Console online help.
- Port Number: Enter the port number that you want this receiver to use when it communicates with the host system. This number must match the port number that is specified in the Routing Control File used by the for MVS Download FSA for this computer's IP address or the PORTNO in the PRINTDEV for the AFP Download Plus FSA.
- Target Destination: Select the InfoPrint destination
that you want this receiver to submit jobs to from the drop-down list. InfoPrint Manager will
only submit a job to this destination when the job does not have a
target-destination-name
value assigned to it after its mvs_keywords have been processed against the DCF. - Destination Control File: Click Browse and locate the destination control file that you want to use with this receiver. Select the file and click Save.
- In the Processing Options group box, both of the options
are selected by default.
- When the Retain command files check box is selected, InfoPrint Manager saves
all of the files that pertain to MVS Download jobs
that fail in processing. When MVS Download print
jobs are processed successfully, these files are cleaned up regardless
of what you select here. If you need to resubmit failed jobs, you
do not have to download them from the host system again; the files
are still on your InfoPrint server.
If you deselect this box, you will have to download any jobs that
fail in processing from the host again to print them.
Note: You can diagnose errors by clicking the Server Log item in the left pane of the Management Console.
Operators should evaluate any processing failures, correct the problems that caused the failures, and resubmit the jobs.
For more information, see Resubmitting or deleting MVS Download Receiver orphaned files.
- When the Enable parallel processing check box is selected,
this MVS receiver will process multiple jobs simultaneously. When
it is cleared, the receiver will wait until the Exit for one print
job completes before it starts to process the next job.
This option is normally left selected unless a custom Exit has been written that requires only one instance of the exit to run at a time and in the order the files are received.
This option must be unchecked if the multiple data set function of MVS Download or AFP Download Plus is used.
- When the Retain command files check box is selected, InfoPrint Manager saves
all of the files that pertain to MVS Download jobs
that fail in processing. When MVS Download print
jobs are processed successfully, these files are cleaned up regardless
of what you select here. If you need to resubmit failed jobs, you
do not have to download them from the host system again; the files
are still on your InfoPrint server.
If you deselect this box, you will have to download any jobs that
fail in processing from the host again to print them.
- In the Error Processing Options group box, neither of the
options are selected by default:
- When the Provide Extended Error Information to AFP Download Plus check box is selected, internal errors or exit errors are reported to the host for assistance in problem determination if requested by AFP Download Plus. When the check box is cleared, neither internal errors nor exit errors are reported to the host for assistance in problem determination. To report internal error messages, you must check this box to report internal error messages. In addition, you must also check the Provide Exit Program Errors to z/OS check box to report exit messages. For all new and existing view receivers, the default status of the box is cleared.
- When the Provide Exit Program Errors to z/OS check box is selected, the success of the exit is monitored by the receiver. A zero return code from the exit causes the receiver to indicate success to the mainframe. A non-zero return code from the exit causes the receiver to indicate failure to the mainframe. When this check box is selected and the exit reports an error on a file in an multiple data set job, the mainframe might retry the file. In addition, any error messages generated by the exit are provided to the mainframe when you check this box if the Provide Exit Program Errors to z/OS check box is also checked. When you do not check this box, the success of the exit is not monitored by the receiver. For all new and existing view receivers, the default status of the box is cleared.
- In the Mapping Options group box, neither of the options
are selected by default:
- Select Basic, to use a limited hard-coded conversion table.
- Select Custom, to specify the Host Code Page and,
optionally, the Local Code Page for conversion.
- Host Code Page: Enter the name of the code page from where your JCL is submitted.
- (Optional)Local Code Page: Enter the name of the local code page that you want to use. If this field is left empty, the receiver queries the system code page and uses it instead.
- (Optional) Click Advanced to open the Add MVS Download Receiver
Advanced dialog. In this dialog, you can specify these options. For more information about the dialog and the fields it contains, see the Management Console online help.
- Select Standard Exit Program Options, to specify the Print AFP Download Plus Jobs with Errors on z/OS, the Server Submission Retry Count, and the Server Submission
Retry Interval.
Note: These options are only functional if you are using the new InfoPrint Manager provided exit. If you are using an older InfoPrint Manager provided exit, these options will be ignored. If you are using a custom exit, consult the writer of the exit.
- If you select the Print AFP Download Plus Jobs with Errors on z/OS check box, and AFP Download Plus detects an error in any file in the job, the job is printed including the error messages provided by AFP Download Plus. The error messages provided by AFP Download Plus are printed where the file would normally be printed in the job. If you clear this check box and AFP Download Plus detects an error in any file in the job, the entire job is discarded. For all new and existing view receivers, the default status of the box is cleared.
- Server Submission Retry Count: Enter the number of times the pdpr should be tried. If no value, or a value of 0 is entered, the pdpr is retried.
- Server Submission Retry Interval: Enter the time interval in seconds between the pdpr retries. The value entered must be a integer from 0 to 32767. If no value or a value of 0 is entered, the pdpr is retried immediately.
- Select the Custom Exit Program Options check box, if you
are using custom exits. Consult with the person responsible for the
custom exits to determine whether this box should be selected.
- Exit Program Name: Enter the path and filename of the custom Exit Program that you want this receiver to use. Consult with the person responsible for the custom exit program to determine the name of the exit.
- Additional Exit Program Parameters: Consult with the person responsible for the custom exit program to determine the Additional Exit Parameters.
- Click OK to close the Add MVS Download Receiver Advanced dialog.
- Select Standard Exit Program Options, to specify the Print AFP Download Plus Jobs with Errors on z/OS, the Server Submission Retry Count, and the Server Submission
Retry Interval.
- On the Add MVS Download Receiver dialog, click OK. One or more pop-up informational messages might appear; read them and click OK to dismiss them.
- Select the MVS Download Receivers item in the left pane of the Management Console.
You should see the receiver you just created in the right pane. The receiver status might be STOPPED but it should start momentarily. Click Refresh View on the toolbar until the status changes to RUNNING.
If the receiver does not start within a few minutes, select Edit → MVS Download Manager and manually start the receiver by selecting it and clicking Start
Note: Receivers that will not start more than likely have destination control file errors. You can diagnose errors by clicking the Server Log item in the left pane of the Management Console.