The SYSIN file in the OP's JCL was the source member for the compile.
It has no relation to the program's execution other than the coincidence
of the name SYSIN. Very likely, this caused some confusion.
Obviously the OP is working on learning COBOL and JCL, and possibly many
other things. Feel free to continue training, but you should consider
the audience's level of understanding, not to mention the limitations of
an email list for instruction.
sas
On 7/10/2016 14:15, Bill Woodger wrote:
Sure. And there is a dataset with SYSIN data on it, which implies no human
intervention. What do we do now, explode due to the contradiction?
As I said, my guess is a non-Mainframe training example applied to the
Mainframe.
For a COBOL program on the Mainframe, I see no point in "interacting" in TSO.
It doesn't happen in the wild. Why learn how to do it? Learning for learning, sure, but
not as training for COBOL on a Mainframe.
On Sunday, 10 July 2016 19:59:02 UTC+2, Dan Skomsky wrote:
The original program includes the following statements:
DISPLAY "TO END PROGRAM, ENTER 0.".
DISPLAY "TO CALCULATE SALES TAX, ENTER THE SALES AMOUNT.".
The above statements are executed prior to "ACCEPT"ing every inputted amount.
If the intent of this program was to receive input from a file, why would these
statements be within the source? Why would they be repeatedly executed?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
