Interactive vs Batch with an ERP or scheduler
In my mind, I've always thought of Interactive jobs as being the jobs where a user is actively interacting with the screen, i.e. the program is awaiting their responses and proceeding when values are received. I've associated batch jobs with something where my CL has a SBMJOB command, and things run in the background.
When we bring the idea of an external ERP or a scheduler, I'm curious if my mental model still holds. If I have a program in an ERP where, say, a user enters a few params and then clicks a button to call my CL and execute the program, is that still interactive? I'm not 100% sure what goes on under the hood, but seeing as my CL just gets executed directly, there's no SBMJOB command in it, and the user has to wait a few secs (i.e. unable to do something else while it's processing), it feels like this would still be interactive.
Similarly, if a job scheduler calls my CL every day at a certain time, is that still "interactive" with the "user" being the scheduler itself? I'm not sure it's accurate for me to reduce the distinction of batch/interactive to the existence of a SBMJOB command in my CL program, haha! But just reading the definitions of these jobs isn't getting my head fully there on what happens in practice with these kinds of situations. Many thanks for any helpful thoughts!