Hi all,
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.
Regards.