|
|
| Author |
Message |
seenivasakan
Currently Banned
New User
Joined: 13 May 2007
Posts: 21
Location: Karnataka
|
|
|
|
Greetings.
From my rexx code i am submitting JCL. I am using ISPF panels also. Once the jcl gets submitted, the REXX code should wait for some time, once the JCL execution is success then rexx code should throw a different ISPF panel.
how to check the status of Job submiited from Rexx.
Any one has any idea to accomplish this?
Thanks in advance
Regards |
|
| Back to top |
|
 |
References
|
 Posted: Fri Apr 11, 2008 11:14 am Post subject: Re: waiting till JCL is executed successfully? |
|
|
|
|
enrico-sorichetti
Global Moderator
Joined: 14 Mar 2007
Posts: 2565
Location: italy
|
|
|
|
why You keep asking?
all the advice given was against such approach...
for two reasons...
1. technical... no connection at all between a batch execution and a tso session
2. organizational... its' s yes ( I know I am rude ) stupid. to have a tso session waiting with the screen locked
until a batcjh has finished
posting over and over the same question will get You nowhere
evaluate if it is possible to execute Your process in a tso only environment
if the post is related to copybook assemblies
just to make You meditate on the process ...
IBM FileManager does it from a foreground ISPF option |
|
| Back to top |
|
|
seenivasakan
Currently Banned
New User
Joined: 13 May 2007
Posts: 21
Location: Karnataka
|
|
|
|
Thanks enrico-sorichetti for your reply.
My requirement is like that. I need to halt rexx script for some time.
i explored all the possibilities. Because of such a requirement i am keep on exploring web for possible solution.
Regards
Seeni |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 2893
Location: Brussels once more ...
|
|
|
|
| What was wrong with the previous advice given ? |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 7440
Location: 221 B Baker St
|
|
|
|
Hello,
| Quote: |
| I need to halt rexx script for some time |
I suggest not.
Even if you find some way to implement such a bad solution, it will most likely cause far more problems than it is worth.
Think of how impossible it would be to run your mainframe if everyone who wanted to do something similar tied up resources in such a fashion?
I've been a few places where people did something like this and when the system management & support people found out, it was discontinued.
Is there some reason to believe that repeatedly asking for a way to do some bad thing that you will eventually get answers you will like?
If i notice this posted as a new topic again, i'll just delete it. |
|
| Back to top |
|
|
seenivasakan
Currently Banned
New User
Joined: 13 May 2007
Posts: 21
Location: Karnataka
|
|
|
|
no more haltling.............
BIngo......... |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1001
Location: Chennai - India
|
|
|
|
sorry enrico,expat and dick for posting on this topic again.
I have had a similar requirement which i accomplished using REXX.
- First a job gets submitted
- I keep monitoring the job till it gets over
- If the job A ran fine i would start executing my REXX code again
I too agree with you all that it is not the best approach. I shall goahead and post the code if you ppl are ok with that. |
|
| Back to top |
|
|
|
|
