开云体育

To Kevin (and everyone), I took a look at the DL/I COBOL application that you provided. Sadly, not much luck so far (as below), but I'll take another look when I have some time. I did the DL/I download from the AWS tape, and the stage 1 and stage 2 IMSGEN worked fine.

So I ran the DL/I application in MVT/HASP, on the basis that it ought to work, and would provide some sort of baseline. The PSBGEN, COBOL compile, and link, all went fine. But the DBDGEN gave me several MNOTE-style errors, which I thought I had fixed, but maybe not. The DLIBATCH execution failed 0C5 as soon as the COBOL program got control. I suspect that the parameter list passed by DFSIRC00 was invalid, but I still have some work to to on the dump.

I then tried MVS (TK4-) and it actually went further. Once again, all started out OK with the exception of the DBDGEN (same error messages, unsurprisingly). The COBOL program got control, outputted an "I've started" message, opened a QSAM file and read several input records, which it used to create a DL/I segment, but when COBOL did an ISRT call on the DL/I database there was an error message from an SVC 19 module. The message was complaining that it couldn't open a DCB because it couldn't find the appropriate DD statement, but it was obvious that the DDNAME had been somehow overwritten with garbage.

If there's anyone out there in MVS land who has a long memory and can recall DL/I, and who remembers any error situations such as those above, then I'd appreciate any ideas about what has gone wrong - so it's (1) strange DBDGEN MNOTE messages (2) 0C5 in DL/I batch (3) open error in DL/I batch with garbled DD name.

I'll keep trying, but time is up for a little while; hopefully I'll get back to it some time in the future.

JJ