View previous topic :: View next topic
|
Author |
Message |
Mohit Saxena
New User
Joined: 21 Aug 2007 Posts: 9 Location: US
|
|
|
|
Hi,
In changeman while promoting a package, I am getting Overlay warning for the same component present in another package. Can somebody please tell me why this warning comes and does that means it will overlay the changes present in other package? and if not then in which case the changes made in one package will effect the changes made for the same component in another package? |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
Sounds like a nice feature....
I'd guess that it is warning you that changes to your component could affect other components that also use your changed component.....
Which, of course, you had already verified and taken care of that possibility....grin.... |
|
Back to top |
|
|
sagard
New User
Joined: 16 May 2007 Posts: 4 Location: Pune
|
|
|
|
Yeps, it does mean that the indicated component in your package(latest promoted one) will overlay changes present in any other package. |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
sagard wrote: |
Yeps, it does mean that the indicated component in your package(latest promoted one) will overlay changes present in any other package. |
That sure beats searching huge multiple Alchemist source files for copys and calls..... |
|
Back to top |
|
|
Mohit Saxena
New User
Joined: 21 Aug 2007 Posts: 9 Location: US
|
|
|
|
hi all... thanx for replies... i have just done some more testing and found that latest promoted component will only overlay the load module and not the contents of the same component in another package. hence the changes made in another package will remain intact just that it has to be demoted and promoted again. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
will only overlay the load module |
How might this be an only?
Possibly, there is something i do not understand, but if this were my situation, i'd be quite concerned that what i am trying to work with already exsits elsewhere and when i promote "mine" i've "de-moted" the other one. . . . Same would happen with the other is promoted.
Walking on load modules is usually (or causes) an emergency. . .
As i said, there may be something i do not understand. . . |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi,
Sigh, well, only this information is right from what is posted so far
Quote: |
latest promoted component will only overlay the load module and not the contents of the same component in another package. |
And let me little modify it..
Promotion are associated with packages, when some component is being promoted one has to supply the package 'number' as well. Change Man would issue a warning that another version of the component being promoted/check out exists within the target PDS, and will be overlaid if promotion/checkout is allowed. It is recommended that you investigate this situation and determine if this is really what is desired.
Latest promoted component will only overlay the load module in the respective change Man Package, which was supplied at the time of promotion, other package(s) has nothing to do in this. |
|
Back to top |
|
|
Mohit Saxena
New User
Joined: 21 Aug 2007 Posts: 9 Location: US
|
|
|
|
That explains the query asked.. cheers.. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi,
dick scherrer wrote: |
How might this be an only? |
Perhaps I don't understand what is being asked, might be if explained again, I would be of little help.
Quote: |
That explains the query asked.. cheers.. |
..is it for me..(yes), you are welcome.. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Only means trivial in this case.
In my worlds, overlaying some load module by one that was not meant to replace it is quite serious.
My question was how can overlaying an existing load module be trivial. . . |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi,
Hmmm...you are always 'on' Dick..(it's Saturday..)
dick scherrer wrote: |
In my worlds, overlaying some load module by one that was not meant to replace it is quite serious. |
Change Man checks if the 'same' load-module exist in Base-line, then it would IEBCOPY 'new' load-module onto older one. Other load-module remain intact.
Quote: |
My question was how can overlaying an existing load module be trivial. . . |
If promotion is to be done in production, there is, usually, a process in place across different sites, whish states the severity of promotion; if it's to be done for some other LPAR, change-man still behaves the same way, IEBCOPY, but no 'usual' process is there, just promote the load-module. At my shop, we have an LPAR, which is replica of Production, to promote load-module to this LPAR, use the 'PROMOTE' option of Change Man & then run some 'refresh-job ' in that LPAR, your new-load module is bass-lined in that LPAR.
Ah..I hope, it was not confusing.. |
|
Back to top |
|
|
|