mfisher_ix
2010-11-26 23:27:40 UTC
Hello,
I wonder if you could help mediate a conflict at my Tur(n)key site.
The grumpy MVS operator (my alter ego) would like the COBOL programmers to stop commandeering his console by using the UPON CONSOLE clause in DISPLAY and ACCEPT statements. He says he'll shoot anyone who ever uses these clauses, "for the good of the state".
On the other hand, the antiquarian COBOL programmer (also me) would like to run an interactive COBOL program containing DISPLAY and ACCEPT statements. He says it's his laptop, and his hobby.
I think Mike Murach has shown the way to a peaceful resolution, but am not too clear on the details. Pages 530-531 of Murach's Mainframe COBOL show the TSO commands to allocate SYSIN and SYSOUT, and to call a COBOL load module.
Since the Tur(n)key #3 has no COBUCL job, I'm sure you can see my questions coming from a mile away. If these questions don't bore you too much, I'd like to know:
1) How to code COBUCL. I've seen Jay Moseley's version, but am not sure if it needs any alterations to be used in the Tur(n)key.
2) How (and whether) to use RPF to create a PDS for my COBOL load modules. I've already figured out how to create a PDS named HERC01.TEST.COBOL for my COBOL programs, so the question is how and whether to manually create the corresponding HERC01.TEST.LOADLIB PDS for load modules.
3) What JCL to include in a COBOL job that's meant to be compiled and link-edited, saved for later use, and then called from TSO.
My System/370 JCL book should arrive next week. I also intend to try running KICKS for TSO someday, which would make these moot points. But in the meantime, I'm stumped.
Mit freundlichen Gruessen, und immer mit der Ruhe,
- Matt Fisher
I wonder if you could help mediate a conflict at my Tur(n)key site.
The grumpy MVS operator (my alter ego) would like the COBOL programmers to stop commandeering his console by using the UPON CONSOLE clause in DISPLAY and ACCEPT statements. He says he'll shoot anyone who ever uses these clauses, "for the good of the state".
On the other hand, the antiquarian COBOL programmer (also me) would like to run an interactive COBOL program containing DISPLAY and ACCEPT statements. He says it's his laptop, and his hobby.
I think Mike Murach has shown the way to a peaceful resolution, but am not too clear on the details. Pages 530-531 of Murach's Mainframe COBOL show the TSO commands to allocate SYSIN and SYSOUT, and to call a COBOL load module.
Since the Tur(n)key #3 has no COBUCL job, I'm sure you can see my questions coming from a mile away. If these questions don't bore you too much, I'd like to know:
1) How to code COBUCL. I've seen Jay Moseley's version, but am not sure if it needs any alterations to be used in the Tur(n)key.
2) How (and whether) to use RPF to create a PDS for my COBOL load modules. I've already figured out how to create a PDS named HERC01.TEST.COBOL for my COBOL programs, so the question is how and whether to manually create the corresponding HERC01.TEST.LOADLIB PDS for load modules.
3) What JCL to include in a COBOL job that's meant to be compiled and link-edited, saved for later use, and then called from TSO.
My System/370 JCL book should arrive next week. I also intend to try running KICKS for TSO someday, which would make these moot points. But in the meantime, I'm stumped.
Mit freundlichen Gruessen, und immer mit der Ruhe,
- Matt Fisher