Can a remote site be set up i.e. P on an LPAR which does not share DASD with DP site

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/8/08 by Ingo Pieper

Hi Linda,
for example the CMN14: we have just customized a little bit in this part:
)SET CMPRLST = N
)SEL

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/8/08 by Ingo Pieper

Hy Linda,
here my source (part of CMN14) again (hopefully better to read):
)SET CMPRLST = N
)SEL

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/16/08 by Linda Brennan

Hi Ingo,

apologies for delay.......
we are looking now at getting this P site set up, with transmission type of OTHER ,however we want to keep our DP site as IEBCOPY, will this work?

So we have DP site (A) with IEBCOPY which currently installs to P sites B and F, these share DASD. We now want to use DP site for development and install to Z site which doesn't share DASD.
Does this make sense, is your set-up similar?

Thanks,
linda

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/3/08 by Ingo Pieper

Hi Linda,
yes it is possible, we use it for msome of our environments, which are not connect via shared DASD. We also use C:D to transfer the prod-staging-libs as well as used package contents at promotion time (we even have promotion-targets which are connect via C:D).
so, if you have further questions, don't hesitate to ask.

Cheers
Ingo

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/3/08 by Ingo Pieper

Hi Linda,
it is more or less easy going. But it is not the CMN20 - this job installs the package, it is the distribution part CMN11-15. Especially the CMN14 will be activated and used for transmission vehicle like C:D. You have a flag in each site to define the transmission way (I suspect you standard is "IEBCOPY", there you caon also define "other" and then use it for C:D. in the delivered vendor skels you have then the possibility to use this flag for separating the "standard" way or the the C:D way. Serena also provides some samples (skels) for using c:d - just scan your skel lib for C:D or connectd.
If you want to have same same skels how could look like pls send priv-mail -> I will send them to you.
Cheers
Ingo

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/3/08 by David Hadden

Yes Linda it can be set up and is actually one of the main uses for DP and P site setups. This functionality has been in the product for many years.
You will need to have a transport mechanism available between the LPARS, such as BDT, NDM, XCOM, FTP OR NETMASTR.

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 8/27/08 by Ingo Pieper

Hi Linda,
sorry for delay - just overseen it. Is this still open for you?
Regards
Ingo

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/10/08 by Linda Brennan

Hi Ingo,

thanks for all your help, you have opened a new possibility that we had never considered before. Of course I have a few more questions if you dont mind.

1. Currently in our global parms we have:
TRANSMISSION VEHICLE ===> IEBCOPY (IEBCOPY or Other)
we want to keep IEBCOPY there but we were thinking of inserting some code in CMN10 along lines of ,
SEL

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/8/08 by Linda Brennan

Hi Ingo,
dont have a private e-mail address for you - would love to see how you have updated your transmission skeletons if that would be possible . Slightly off topic, what advantages does havinbg a changeman instance out on P site gain us, theoretically could just post changes into libs and use chanegman on DP for just migrating out changes?
What do you think?

Linda

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/16/08 by Ingo Pieper

Hi Linda,
youre welcome.
It is no problem to have different sites with different transmission types -> thats the reason why it is part of site administration.
One of our installation are similar: One DP site where all developer works with. Install with this site: IEBCOPY / local DASD, the rest are P Install sites, some with IEBCOPY and shared DASD (because it is easier and with a better performance, according to shared DASD, job sumission and such stuff) and other P sites with NDM (OTHER), mainly because they are located over the world (with no possibility via shared DASD).
So, out of my point of view the makes absolutly sense!
If you need helpt to setup the P-CMAN or having further question...
Cheers
Ingo

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/3/08 by Linda Brennan

Thanks David,
do you have JCL or your customised CMN20 skeleton where you put these changes in?
Is there anything else I should be looking at?
Thanks,
Linda

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/16/08 by Linda Brennan

Hi Ingo,

so just to be clear even though DP site has IEBCOPY , if the P site installing to has other this will override the DP transmission type?
Thanks, Linda

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/3/08 by Linda Brennan

Thanks Ingo,
did you find the setup complicated, do you include the C:D as part of your job 20?

Linda

Question posted 7/3/08 by Linda Brennan
Details:

We are setting up a new system on an LPAR and changeman will not be on this.
We are now looking at ways to manage change ie our proclibs and source libraries on this system. Currently we are looking at using changeman on our legacy (existing) system and C:D the changes across to new.
These two systems will not be sharing DASD.

I was wondering had anyone done anything like this before?
Thanks,
Linda

#poste89de45bf5
#remotesitesnonsharingofdasd
#ChangeManZMF
#oldforumpost

Comment posted 7/10/08 by Ingo Pieper

Hi Linda,
your are welcome.
to your new question:
to 1)
To be sure: You want only to use NDM, when having a special compontent-type "JCZ" in package? - Then your suggestion could work.
If not: Just use IEBCOPY if you want to use IEBCOPY - for later maintenance it sould be more easy to go ahead, if the admin parms does what the say.
If it is not sure, that JCZ be the only special "NDM-type" in future: think about a special production site with "OTHER" (and NDM), which is just included in packages if they are needed to go to your NDM target -> this shuld be the better way. In changeMan its no problem to have different production sites with different methods to work - that is the design. Your suggestion coudl work fine now, but get you in trouble in future -> The mind behind it is clear: Having a qucik solution, but in most cases this is followed by: hugh maintenance, decreasing know how and lots of work enhancing it. But's your decision, just a few words to think about.
Your Change of CMN10 just works for Production (not promotion).
to 2)
For each remote production site it is recommended to have a separate changeMan (P, no DP), he ensure a proper work at installation time (I think that's important while installing stuff). C:D could work properly, but also cut have failures (or problems) and maybe (we have some cases) sends no feedback about the success... The CMAN task ensure a proper feedback. So, it is better to keep the whole process to populate stuff in production in changeMan itself - this a feature he is designed for, intstead of post-process in handwritten copying and reporting processes. - This also enable you to backout out stuff (with changeMan in ChangeMan in a secure and tracebale way - your revision guy, wil say "Thank you").
And a long