On Fri, 24 Jun 2016 15:17:50 +0000, Sankaranarayanan, Vignesh <[email protected]> wrote:
>This is to cope with MQ FTE's "feature" of not locking datasets for the >duration of a transfer. > >Using ANT scripts to initiate a transfer of a list of datasets that resolve to >a wildcard, we've found that in the time gap between the >initial resolve of the wildcard and the transfer of datasets found in the >wildcard, those datasets are processed by some other entity, >leaving the MQ FTE step to fail saying dataset deleted (already processed). >There's the outcome=defer option in the ANT script but I don't believe it has >led to the job to stay active until the MQ FTE transfer >completes fully. I am concerned that your allocation as OLD will prevent the subsequent use of them for transfer in a later job-step. It may work, but it may not. That is, if you have a data set allocated OLD by your exec, and then a later step in your job tries to do a dynamic allocation either SHR or OLD I think that later allocation may fail. However, I can't test this (no longer having access to z/OS). Plus, you have my initial concern that your use of ALLOC in the exec may itself fail if someone else has the data set allocated already. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
