IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Overlay warning in changeman


IBM Mainframe Forums -> IBM Tools
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Mohit Saxena

New User


Joined: 21 Aug 2007
Posts: 9
Location: US

PostPosted: Sun Apr 06, 2008 11:43 pm
Reply with quote

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
View user's profile Send private message
CICS Guy

Senior Member


Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table

PostPosted: Sun Apr 06, 2008 11:57 pm
Reply with quote

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
View user's profile Send private message
sagard

New User


Joined: 16 May 2007
Posts: 4
Location: Pune

PostPosted: Mon Apr 07, 2008 12:43 am
Reply with quote

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
View user's profile Send private message
CICS Guy

Senior Member


Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table

PostPosted: Mon Apr 07, 2008 12:48 am
Reply with quote

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
View user's profile Send private message
Mohit Saxena

New User


Joined: 21 Aug 2007
Posts: 9
Location: US

PostPosted: Mon Apr 07, 2008 1:28 am
Reply with quote

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
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Mon Apr 07, 2008 3:50 am
Reply with quote

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
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Mon Apr 07, 2008 4:29 am
Reply with quote

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
View user's profile Send private message
Mohit Saxena

New User


Joined: 21 Aug 2007
Posts: 9
Location: US

PostPosted: Mon Apr 07, 2008 6:23 am
Reply with quote

That explains the query asked.. cheers..
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Sun Apr 13, 2008 7:51 am
Reply with quote

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.. icon_smile.gif
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Sun Apr 13, 2008 7:58 am
Reply with quote

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
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Sun Apr 13, 2008 8:33 am
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> IBM Tools

 


Similar Topics
Topic Forum Replies
No new posts Changeman - how can we know the curr... Compuware & Other Tools 2
No new posts Help, trying to use OVERLAY to get a ... DFSORT/ICETOOL 3
No new posts BNDS and Overlay command TSO/ISPF 9
No new posts Issues with outrec overlay while extr... SYNCSORT 7
No new posts HOW TO OVERLAY A Packed decimal VALUE... DFSORT/ICETOOL 5
Search our Forums:

Back to Top