Is there a difference in UNIT=DASD or TAPEC while files are created?
Posted: Tue Feb 20, 2018 8:37 am
Hi,
One of our COBOL program has got some files. Not all the files are will opened or written to on every run of the program. It depends on the values supplied by a member by parmlib. There is a strange thing we have noticed that if the files are being created on DASD the empty files does created even if the file is never opened or written by the program though when JCL is using UNIT=TAPEC for the same file and file is not opened, an empty file is not created. Why would such a thing happen and make a difference with DASD and TAPE?
One of our COBOL program has got some files. Not all the files are will opened or written to on every run of the program. It depends on the values supplied by a member by parmlib. There is a strange thing we have noticed that if the files are being created on DASD the empty files does created even if the file is never opened or written by the program though when JCL is using UNIT=TAPEC for the same file and file is not opened, an empty file is not created. Why would such a thing happen and make a difference with DASD and TAPE?