0% found this document useful (0 votes)
124 views7 pages

What Will It Do For Me?

ChangeMan allows developers to: 1. Capture a copy of the current production code as a base version. 2. Provide different environments to test code. 3. Approve and install edited code into production via an approval process. When assigned a task in ChangeMan, a team member will: 1. Create a package 2. Check out components from production/baseline or stage a new component 3. Edit/delete components and submit for compilation 4. Promote the package to a testing region for testing

Uploaded by

jhf281192
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
124 views7 pages

What Will It Do For Me?

ChangeMan allows developers to: 1. Capture a copy of the current production code as a base version. 2. Provide different environments to test code. 3. Approve and install edited code into production via an approval process. When assigned a task in ChangeMan, a team member will: 1. Create a package 2. Check out components from production/baseline or stage a new component 3. Edit/delete components and submit for compilation 4. Promote the package to a testing region for testing

Uploaded by

jhf281192
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

What will it do for me?

Allow a developer to capture a copy of the current production code (base version)

Provide a developer with different environments in which code can be tested

Allow a developer via the approval process to install the edited code into production


What team member will do when he/she given a task?

1. Create a package.

2. CHECK OUT components from production/baseline (if that program already exists) or STAGE a component
(program/jcl/proc/dbb ....) after developed the component in local directory into package.

3. Edit/delete the components and sumit for compilation.

4. For testing he can PROMOTE that package to testing region.












































Questions
1 Question.

I have to compile 126 source codes.
Can somebody please help me to automate this. Else its going to take huge time if I go on doing them
manually.

Can I prepare some tool sort of thing where I only give package name, DB2 option type, and all the
corresponding linc cards get generated at their respective PDS. If yes, please provide me a path.

You imply by the topic title that you have changeman and the members are already in Changeman so use the
Changeman facilities - cannot remember what they are as it is 6 years since I worked with Changeman but I
am sure it is something like pulling up a member list and selecting those that you want.

2 Question. Promote feature in Change Man

Can any One tell me how to Promote the Libraries from Test region to Production Region. Iam aware that this
can be done with the PROMOTE Feature of Changeman.

You can promote components exists in a package using option 3;P


3 Question.

What is the use of options 1.6.1,1.6.2 in change man tool ?
Please explain briefly.

Well, usually these options serves the same purpose at different shops, however, they are subject to change,
per the choices your-shop-representative might have asked for, at the time of installation.
In general 1.6.1 and 1.6.2 both are used to STAGE components - former is used to stage from "personal PDS"
and the later is used to STAGE/edit components in Changeman package.


4 Question. Precompile variables

While compiling the DB2 module there comes an option 'precompile variables = (Y/N)'. I want to know when
and why we use it.
While real perfection is only one, relative perfections must be many.

When next time you see it, press PF1 key and read-through the documentation.


5 Question. Copy from production to testing

I want syntax, how to copy a module form production to testing region?

Use check out facility in changeman.
Read the following tutorial. Refer step2.
http://www.mainframetutorials.com/changeman.html

There is no syntax -- there is a procedure and the procedure would change shop to shop. Suggest you get in
touch with some "senior" at your shop once you go through the link Natarajan has provided but remember
many things in the link is specific to the shop or the person who has created it.

Packages will be created by the Module Leaders, Project Leaders or Project This step is needed to test the
component like mainframe testing in your test regions. ... jobs to copy all the components from staging libraries
to production libraries.




6 Question: Compile options

Is there posibility to check how changeman build my cobol program, what options it use. I haven't admin rights
in changeman.
For now, I used IGYWCL call from jcl to build my sample programs. Does changemans also use it?
I have changeman version 5.6.0 on z/OS

But if you've ChangeMan, why are you using IGYWCL directly?

because I'm in "reaserch team", not developer
and I have to checking some features.

So what kind of help do you need? ChangeMan works on "panels", where you choose the options to take the
next action. In one of those panels, there is a panel where you can enter your compile options.

If above is not what are you looking for and have some specific question/s - you need to tell us, what are they?

I suspect that ChangeMan generates some JCL to compile program, after sets all options in panels.
I would like to see this JCL. I suspect that I should looking that in SDSF is "Status of jobs", but there is a lot of
jobs and I don't known what (job name? owner = XCHGMAN?) and how search.


7 Question: Doubt in version control in Cman

I have started using Cman recently. Is it possible to view the previous versions of the program which was
changed earlier. Eg i make a change in a program and then after some time i make some changes again in
the same code. Is there any option in Cman to view the previous version?

Yes it is possible. if you moved your code to production after the change.

Change man controls the "history of releases", how many releases? That's a site specific question though.

When you say "after some time" - does it mean after a release or this is talking about those times when you're
making some changes/errors/corrections in your program? If it's about later case - no "history" is saved and
you can't see your previous changes (unless, of course, they are changed), in other case, as natarajan has
said, a history of versions is usually maintained.

You might also like