THIRD.DISP.DELETE = YES | NO
The PNODE setting for the THIRD.DISP.DELETE= parameter controls how IBM® Connect:Direct® processes the value of the third subparameter of the (TO)DISP= parameter during a COPY operation when an ABEND occurs in the COPY step on the receiving node.
|YES||Enables the third disposition delete feature.|
|NO||Disables this feature.|
The following table describes the conditions under which THIRD.DISP.DELETE=YES is enforced and the result it produces.
|This processing occurs||When all of these conditions are present|
|The data set on the receiving node is deleted.||ABEND occurs in the COPY step on the receiving node (SNODE).|
|Third subparameter of the TO(DISP) parameter is not defined, or is defined as DELETE.|
|Third subparameter of the TO(DISP) parameter is not defined as KEEP or CATLG.|
|The destination output file does not exist, that is, the COPY statement creates a file, which means that if RPL is specified, there is no file to replace.|
|The DISP parameter of the TO side of the COPY statement is set to one of the following options:
|The Process is ineligible for REQUEUE because one of the following is true:
When THIRD.DISP.DELETE=NO is set, the following processing occurs:
- IBM Connect:Direct does not apply the third subparameter value, even if it is set to DELETE in the Process itself.
- IBM Connect:Direct uses the value set for the second subparameter of the TO(DISP) parameter as the value for the third subparameter. For example, if the second subparameter is set to CATLG, the third subparameter is treated as if CATLG were specified.
When you create GDG data sets using relative numbering, for example, DATA.SET.NAME(+1), you must specify CATLG as the third subparameter of the TO(DISP) parameter. If you fail to do so, a RETRY failure occurs. For example, you can specify DISP=(NEW,CATLG,CATLG) or DISP=(,CATLG,CATLG).
Modifiable through MODIFY INITPARMS command: YES