View previous topic :: View next topic
|
Author |
Message |
zatlas Currently Banned New User
Joined: 07 Dec 2006 Posts: 8 Location: Ne Jersey
|
|
|
|
Hi All
Where can I find information on how to invoke the JCL conveter/interpreter from a program and handling the output. I would like to SCAN a whole library at a time (rather then run 200 jobs with TYPRUN=SCAN) and ahndle the iterpreted output as a text sequential file (rather then sysout.)
I saw an assembler program that does something similar (scanning one job and shows to TSO) on the CBT Tape for MVS 3.8J but it does it via an SVC and it is an old release. I need it for z/OS and would like to run from batch.
Thanks
ZA |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Are you quite familiar with assembler? If you are, i'd suggest downloading what you found and confirm that anything it uses (svcs, control blocks, etc) is still valid and if so, give it a try.
I'd make sure that for the initial testing at least, i did not update/delete anything in the system.
Good luck and let us know how things progress |
|
Back to top |
|
|
zatlas Currently Banned New User
Joined: 07 Dec 2006 Posts: 8 Location: Ne Jersey
|
|
|
|
I am quite familiar with Assembler and I have no problem with the SVC code, and yes I would actually try to use it (even though there are some prominent 24 bit addresses usage in the code.) The problem is that I need it for a client site and NOBODY in their right mind would EVER allow a consultant to compile such a thing :-(
Also this approach is not really suitable for batch processing. However, somebody gave me a solution that might work which involves actually submiting the jobs with TYPRUN=SCAN and capturing the sysout. He gave it to me on a private basis so I cannot share the code unfortunatly, though.
ZA |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Ah, the joy of contracting/consulting.
Yup, they most likely would not want that kind of code just put on the machine as an experiment. However, if it could become part of the statement of work. . . .
Trapping output is surely a non-invasive way to have the info you want machine readable.
Good luck |
|
Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005 Posts: 2358 Location: Israel
|
|
|
|
You can generate and submit a job with SCAN from within REXX, then use SDSF batch commands to trap the output (and delete it if you want) - all from within REXX.
O. |
|
Back to top |
|
|
zatlas Currently Banned New User
Joined: 07 Dec 2006 Posts: 8 Location: Ne Jersey
|
|
|
|
Thanks Ofer
That's exactly the approach I am taking that I've referred to above. |
|
Back to top |
|
|
|