View previous topic :: View next topic
|
Author |
Message |
krish.deepu
New User
Joined: 27 May 2014 Posts: 4 Location: India
|
|
|
|
Hi,
Requirement:
Develop a REXX edit macro to create GDGs.
I've a JCL and PROC. This PROC will be called by different JCLs in various regions. I would like to create an edit macro which can create the required GDGs. This macro can be invoked from JCL.
One thought (which might not be ideal) which I got is, that when we invoke the JJ tool, we would get the GDG base missing error. WHy this approach, coz - The PROC will have HLQ and some part of the GDG name passed as symbolic parameter from JCL (since it changes for different regions).
Is there any way I can trap those message and then parse those for GDG base and then create it? If yes, could you please let me know how can it be acheived. Or else a better solution.?
Thanks ! |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
look at the JJ documentation to see if it can interface REXX
anyway
when an application is deployed the operations group should have done the work for which they are getting paid ...
READ the docs
take care of ALL the prerequisites
creating ( list not exhaustive )
SMS related things
HLQ aliases,
GDG bases
...
...
TAPE Library related
...
also, all the world might be using JJ,
but only the operations group might be able to
define things which mangle the catalogs
defining a GDG base is not something that can be automated
( number of generations might vary ) |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2545 Location: Silicon Valley
|
|
|
|
I did not get a good feel for what the whole scenario / environment is.
But it seems like something is executing in a batch job. You should be able to change the JCL so that the failing messages go to a SYSPRINT file and then add another step in the job to examine the SYSPRINT file looking for those errors, in order to correct and retry.
Show us what errors you are getting.
If you can modify the JJ program, maybe it is better to add a LISTCAT command to verify if the GDG exists. Use the OUTTRAP function to capture the command response. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
Quote: |
If you can modify the JJ program |
JJ is a jcl checker |
|
Back to top |
|
|
krish.deepu
New User
Joined: 27 May 2014 Posts: 4 Location: India
|
|
|
|
Pedro wrote: |
I did not get a good feel for what the whole scenario / environment is.
But it seems like something is executing in a batch job. You should be able to change the JCL so that the failing messages go to a SYSPRINT file and then add another step in the job to examine the SYSPRINT file looking for those errors, in order to correct and retry.
Show us what errors you are getting.
If you can modify the JJ program, maybe it is better to add a LISTCAT command to verify if the GDG exists. Use the OUTTRAP function to capture the command response. |
Hi,
I'll just explain the background.
JJ is a tool which we use here to validate the JCL for syntax, check for DS & GDG base existence etc. Its executed as an edit macro and is in-fact a third party tool, which we don't maintain. So I may not be able to modify it.
When I execute this JJ in a JCL, what I get is some inline comment message lines after each sentence which fails the validation. This includes the validation of GDG bases as well. I'm trying to see If there is any way to capture those inline messages and parse it further to get the GDG base name and then create it. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
the topic has been discussed many times for many jcl checkers
with negative answers .
topic locked |
|
Back to top |
|
|
|