Author: Robert Sample
Posted: Thu May 19, 2016 6:41 am (GMT 5.5)
Possibility 1: the SEMT (sic) SET FILE(FILENAME) CLO DIS failed to either close or disable (or both) the file, and hence CICS still has it allocated / open.
Possibility 2: as soon as CICS deallocates the file, another job (batch or started task) allocates it.
Uh-huh. There's no system back up of the high-level qualifier, or volume, that ever executes? There's no application back up for the data set?
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Thu May 19, 2016 6:41 am (GMT 5.5)
Possibility 1: the SEMT (sic) SET FILE(FILENAME) CLO DIS failed to either close or disable (or both) the file, and hence CICS still has it allocated / open.
Possibility 2: as soon as CICS deallocates the file, another job (batch or started task) allocates it.
| Quote: |
| No other JCL/PARM uses the file we are trying to delete. |
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth