On Fri, 28 Jul 2017, at 22:00, Farley, Peter x23353 wrote: > I would have to somewhat disagree with that position. If a COBOL program > issues OPEN INPUT for a file, that file *can* be READ by that program. > If it issues OPEN OUTPUT or OPEN IO then that file *can* written to, and > possibly also read for the IO case.
The trouble is, you're saying what might happen to the file associated with a particular DD. But in any specific piece of JCL you won't know which of those actions will take place on the specific files mentioned in that instance of the JCL. I see no point in somehow auto-generating a list of datasets that might need to be written to, if in practice few or none of them will be. Also... why is anyone, so-to-speak testing what a production program will do? Doesn't the site have any testbeds... where a corresponding set of test datasets are tested in the same overall relationship as the live ones? -- Jeremy Nicoll - my opinions are my own. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
