I'm in the process of defining two new CV's. Is there an easy way to clone an existing CV as a starting point?
Chris’s post are very clear and TEC471781 are very detailed.
We have set up a ‘IDMS Cloning’ first of all, to create new test environments. To do this, we copy all files: SYSTEM, CATSYS, Dictionary, Database…After that, we adapted all the specific definitions: DMCL, DBTABLE, SYSTEM, Dictionary name, Lines names,… Don’t forget:
- to include a specific RUNUNIT for the new dictionary and maybe delete the corresponding original (in ‘SYSGEN’).
- to include the new dictionary in the loadlist/s. (in ‘SYSGEN’).
- GRANT the users to get access to new system and REVOKE to the older.
- If you have users in dictionary, be careful with security options for IDD, MAPC etc. Maybe you would change it depending on the environment.
Once the system is ready, we use some of these procedures to clone the systems yearly. We are copying dictionary and database files, and subschemas and applications programs libraries. We are keeping the basic system definitions (SYSTEM, CATSYS) and PUNCHing from source system:
DMCL, SEGMENTS, DBTABLE, Securities definitions, Program an Task definitions.
And including it in the target system.
We have used only IDMS utilities, SORT, File Manager and the usual tools. I strongly recommend using flashcopy to reduce unavailability
I had fun preparing this and the result is rewarding.
Check out TEC471781, but "easy" is not a word I would choose to describe such a venture
I would suggest that you start by reading the installation manual, chapter 5, go to Installation Types and Complete Base Installation, it will give you an idea of what is required.Then read the tech note referenced by Brian.
It will be much easier if the CVs share system dict and catalog with existing CV –
Punch out the required segments = create new segments with new names where necessary (create new datasets) – build the new DMCL – generat andf punchy it FROM THE EXISTING CV
Same with a system – punch – alter – load back - generate it form within the OLD CV
Then bring up the ne CVs) as jobs at first to get around SOME security issues
If you must use a new catalog and system dictionary – copy the contents of the old to the new – then in the new – then broing up the mew CV using the NEW cataklog and system dictionary – then delete the unneeded objects form the new catalog/dict
Its probably more complemented than that – but that is what I deem top revall having done
Technology Architect, Database Infrastructure Services
Technology Solution Services
123 East Main Street
Louisville, KY 40202
(502) 714-8615, (502) 476-2538
The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.
The KD is old and item #6 has an outdated statement.
"Possibly create a new Startup module for the CV. If you use the generic startup module IDMSDC or RHDCOMVS and the new JCL parameters for specifying system number, DMCL, WTOEXIT etc you won't need to create a new startup module and RHDCPARM for this CV. If you make your own uniquely named startup module and/or will not be using the JCL parameters for DMCL etc, make sure you include the RHDCPARM & WTOEXIT you want for this CV."
Obviously there are no longer any custom startup modules and no more RHDCPARM. There is only the generic startup module and all Parms are specified in the startup JCL.
Basically the rest is a good place to start for a list of things to create a new CV from an existing one.
If the DASD is sharable between the LPARS – why not just share the dictionary ? is there a possibility that there could be different versions of the same ADS code in the two environments? if not then no problem
As for DMCL/DBTABLES – male different dmcls/dbtables in the SAME catalog, accessible to both – but only called by the CV needed
We run one catalog and one appl dictionary across many CVs on multiple LPARS – no problems here
Lead Sys DBA
IBM Global Technical Services on assignmemt to Humana Inc.
T 502.476.2538 or 502.407.7266