Chris, you seem to know everything about VTAM, SNA, TCPIP -_-
Your reply reminds me of something I did two months ago(Sorry, it may be a little off-topic) That time I wrote a rexx exec to submit one JCL job and after that it'll keep on querying the status of the job. And if it successfully ends, the exec will submit another jcl. Just like that. Of course I know this exec is just a toy and it can never be put on production system. Or the sytem programmer will call me:) Later on I began to learn HLASM and tried to find out whether there is a smarter way to do this using system service. However, i cannot find one. I also searched the internet and found there're so many topics about this and there is not a easy solution. Obviously the most difficult part is: after submitting the job, how my program will know when the job will finish? The easiest answer is 'keeping on doing something'. But on a production sytem it's just untolerable cosidering the fact that the previous job may need hours to complete. However, I'm just curious about this because I know some softwares like Tivoli Workload Scheduler can do this job. Then, how TWS did that? If they use 'loop' too, why I cannot? I talked this to one of my friend and his opinion is that there is nothing special with these production softwares. They still have to use some 'loop' there. 'If everything is dead, then the sytem is dead. Am I right?' My firend told me. 'So there must be somthing alive. How they keep themself alive? Loop. Just they did that more efficient. That's the only difference'. Sounds like a reasonable explanation? And it made me think of the CICS programs. They say CICS program is pseudo-conversational which means after one execution it'll be dead and will not wait for user input which is the case for traditional convesational programs. And the manual says this is more efficient. However, when next user input comes, how does my programs know that since it's dead? So actually there're something which will never be dead (maybe it's the CICS in this case). And when user presses specific keys, it'll invoke the approprate program. Why not the user program do this itseft? Maybe it's still because CICS does this better than user's program:) Sorry for the lengthy input. On 12/23/06, Chris Mason <[EMAIL PROTECTED]> wrote:
dir - as many times as is necessary until the output files appear get JOBzzzzz.s - where zzzzz is the sequence number and s is 1 to the number of output files
Best Regards,
Johnny Luo
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
