You can specify an exit process for the following conditions:
Important! A transfer restart is counted as a normal start.
The exit process is executed when the condition is met. For example, you can take some action and set the schedule as COMPLETED rather than wait for the End of Processing period. You can use the STARTNCL macro to start the following API to force completion:
$RFCALL ACTION=FORCEEND NAME=schedule-name
Another example is to use the SHDCALL macro to send a command to CA 7 WA to submit a job at the completion of the schedule.
For Transfer Failures, the specified process is executed for every transfer failure until the number of successful transfers has reached the expected transfer count.
In addition to the schedule knowledge base variables, the following variables are available to the transfer failure event process:
|
Variable |
Description |
|---|---|
|
&ZRFXFRID |
The Transfer ID |
|
&ZRFPRODUCT |
The Data Transfer product |
|
&ZRFJOBNAME |
The Data Transfer STC or JOBNAME |
|
&ZRFUSER |
The ID of the user that performed the transfer |
|
&ZRFSRCADDR |
The address or node name of the source of the transfer |
|
&ZRFSRCFNAME |
The name of the source data in the transfer |
|
&ZRFTGTADDR |
The address or node name of the target of the transfer |
|
&ZRFTGTFNAME |
The name of the target data in the transfer |
|
&ZRFABENDCODE |
The ABEND code |
|
&ZRFFAILCODE |
The FAILURE Code |
|
&ZRFFAILDESC |
The FAILURE Description |
You may need to associate schedule specific information that cannot be currently accommodated with the SCHEDULE Owner Details panel. You can specify up to 16 extra fields (of 70 characters each). The additional details are available through knowledge base variables &ZRMDBADDET1 to &ZRMDBADDET16.
File Transfer schedules do not support the definitions of relationships with other resources. Use one of the various File Transfer Schedule exits to establish dependencies.
The Schedule Recovery is optional; the default is YES (Schedule Recovery ON). The schedule file (FTSCHD) is required even if Schedule Recovery is set to NO.
To reduce virtual storage use with a large number of schedules, you can set the Transient Log Table Size to zero. If the Transient Log Limit in AUTOTABLES is set to 0, then NO transient logs are allocated for any resource.
Note: If the Transient Log Limit in AUTOTABLES is set to a value greater than 0, individual resource definition can be changed dynamically to a lesser value (including 0).
To specify event exits for a file transfer schedule
The ResourceView : Resource Definition panel appears.
The File Transfer Schedule List appears.
The Panel Display List appears.
The Event Exits panel appears.
The Automation Services : Process List panel appears with a list of processes.
You are returned to the Event Exits panel with the name of the process.
Note: If the process requires parameters, apply the P action.
The schedule is saved with the event exits.