BillyBoyo wrote:Mmmm... not generally a good way to do it. The Computer Operator, who has access to the Console, is not your "user" - normally, anyway, unless it is some processing for OPS?
It will be far better to allow your actual user to input data through a screen at their desk. It can be validated. The data will go to a file designed for that purpose. That file will later be read by three different programs. The data input by the user can be recorded/reported/backed-up so that the three programs can be later re-run to get the same results, the use can't argue that they didn't ask for "that" and Computer OPS can concentrate on running the system. It is unfair to expect Computer OPS to do accurate data-entry as well.
So, what you'd need in the JCL would be// DLBL etc
BillyBoyo wrote:Mmmm... I doubt it, unless you want to investigate "getting dirty" with Assembler, which I'd not suggest as a good idea.
The "usual" alternative would be to include what is needed as part of the "run instructions" and have your "Production Control" prepare the job correctly. They will have more time, fewer other things to do. They may still prefer that it is not their responsibilty, and you are back to the file...
BillyBoyo wrote:I'm not saying it is possible with Assembler I'm saying that if the world were about to explode unless you could do this, then you'd better try to find out how to do it. Otherwise leave it.
I know you can't do it in Cobol.
BillyBoyo wrote:Is the world about to explode?
If you are determined to do this through JCL, how about looking into using the "punch"?. Punch the JCL you want, assign SYSPCH to SYSIPT. Amended JCL arrives. Your auditors or production control may not like this approach.
But by whom/how would the parameter get set anyway?