Many thanks for the replies. Creating the IEAAPP00 member has indeed solved the imediate problem. But, as usual, that has just meant that I've moved on to something else.
?
I can report that both the HISAM and OSAM files are now opening OK (as far as I can see) and that DL/I is now writing into the HISAM file as it should for a DL/I load operation.
?
But there seems to be an issue in that additional strange records are being written to HISAM (which is actually VSAM, via the "bridge"). Whether I have defined the VSAM cluster incorrectly, or whether there is duff logic in the COBOL program, I don't know., so that's my next avenue to investigate.
?
I suspect the the given COBOL program has some issues. I don't know where the DL/I testing program suite came from (I found the name Monceaux in one place - I don't know who that is), and I'm not convinced that the logic is 100% reliable (for example, it doesn't even count the number of input records correctly).
?
So... further investigating to be done when I have a chance, JJ
?
