View previous topic :: View next topic
|
Author |
Message |
danielm81
New User
Joined: 18 Mar 2021 Posts: 5 Location: España
|
|
|
|
Hi,
I would like to ask a question about endevor. I would like to be able to have several versions for the jcls in my installation. I would like that when it goes from the development environment to production, to be able to modify the source adapting the nomenclature to the production environment. This is some way to do it, since I tried the generate, update and add options, but I can't find the solution.
I accept any suggestion.
Thanks for your help
Best regards, |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3076 Location: NYC,USA
|
|
|
|
You mean to make a use of system symbolic? when jobs run in their environment accordingly job details are changed based on symbolics. |
|
Back to top |
|
|
danielm81
New User
Joined: 18 Mar 2021 Posts: 5 Location: España
|
|
|
|
Rohit Umarjikar wrote: |
You mean to make a use of system symbolic? when jobs run in their environment accordingly job details are changed based on symbolics. |
Hello,
I understand that you say if you work with cataloged procedures.
We do not work with cataloged procedures, but we do change certain parameters in the jcls, such as the db2 subsystem, etc that we want to adapt according to the environment. As the component is promoted it will be adapted to the environment where it is promoted. |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3076 Location: NYC,USA
|
|
|
|
But the same approach should work in jcl only as well, I don’t know how but is there a way for you check with system people ? |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1205 Location: Dublin, Ireland
|
|
|
|
If you use the JCL SET statements for symbolics, you don't need to be using cataloged procedures. SET will work with in-line JCL, too.
Garry. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10888 Location: italy
|
|
|
|
why not ask the endevor support group in Your organisation ???
all the tools used for software development control undergo quite a bit of customisation
now a few points to consider ...
if everything runs in a single <image> of zOs only the endeavour customisation must be taken into account
for each stage/process endeavour ( or any other alike tool )
lets you customise in pretty deep details the libraries and the db2 subsystem to be used - btdtgtts
if on the other side some stage/process is supposed to run in a different image from the one used to issue the command , the the system symbols will become handy
the only thing needed is to have a clear map of who does what/where/when |
|
Back to top |
|
|
|