MVSFORUMS.com

abracadabra · Posted: Fri Feb 29, 2008 1:51 pm Post subject: JCL to REXX

Hi,

I searched the help board but could not find anything conclusive. Is there a method by which a REXX can accept the return code of a single step JCL that the REXX is submitting?
_________________
Cheers!

superk · Advanced Joined: 19 Dec 2002 Posts: 684 Topics: 5

No.

But, let me ask you a question, and maybe you can find a way to get what you need.

Let's say you're in a TSO session (that's a TSO session, not ISPF) and you submit a job. Sure, if you had the NOTIFY= on the jobcard, you'd know the status of the job. But, you want something more permanent. How would you obtain that same information?

OK, now you startup an ISPF session and you have ISPF services available. Again, you submit a job. Now, how would you obtain that information?

Why not have the job, as its last step, create a logfile with all of those details in it? Something you can read elsewhere.

abracadabra · Posted: Fri Feb 29, 2008 2:37 pm Post subject:

My requirement is to throw a message on the panel depending on the RC and continue with subsequent processing
_________________
Cheers!

CraigG · Posted: Fri Feb 29, 2008 3:43 pm Post subject:

When your REXX submits a job it does wait for the job to complete it continues running. What if you submit the job and the initiators are all busy or stopped or the job takes 5 hours to complete?

semigeezer · Posted: Fri Feb 29, 2008 7:04 pm Post subject:

Bad design.

Batch jobs should never be part or an interactive process unless it is absolutely unavoidable (and by that I mean that there is no way to run the same program online). Almost anything you can run in batch, you can run directly through Rexx. Unless there is something very special, and unusual about what you are running, just run it from Rexx (allocate the files to the right dds and call the program). One of the few things that comes to mind that is available in batch but not (easily) online is referbacks to temporary data sets, although you can probably do that with bpxwdyn also if you really need to.

Also, it is common for people to think it is OK to just sit in a loop waiting for jobs to end. No wait state or sleeping, just running and checking the status continuously. Another hallmark of bad design.

I was just at site which has over 600 users per system (with several systems) during the day, runs at 100% CPU almost all the time, and opens about 10 initiators. If classes are not available *yes - class A was shut down for a while* then the jobs never run at all. And if anyone is sitting in a loop waiting for the jobs that never finish, well lets just say they aren't making any friends.
_________________
New members are encouraged to read the How To Ask Questions The Smart Way FAQ at http://www.catb.org/~esr/faqs/smart-questions.html.