Gary_Cherlet

IDMS SQL ACM/RCM question

Discussion created by Gary_Cherlet on Aug 16, 2012
Latest reply on Aug 16, 2012 by Gary_Cherlet
The IDMS SQL move process from a test CV to a production CV is driving me nuts (and has since I got here.)

Background:

We have 5 CVs (TEST(CV10), PRODUCTION (CV11), PRODUCTION MIRROR (CV14), QUALITY ASSURANCE (CV13) and Training (CV12).

Programs are only compiled in CV10. Object code is then copied to the appropriate libraries when then move to QA and then Prod and training.

CVs 13 and 12 are OBJECT CVs only. (SUBSCHEMA load modules are copied from CV10 to CV12 and CV13's dictionary)

CVs 11 and 14 are SOURCE CVs. (SUBSCHEMA source is copied from CV10 and re-compiled into CV11 and 14.)

Now, for the (my) difficult part.

We have, maybe, a dozen SQL programs, which seldom, if ever change.

What do I do with the SQL portion of the program (ACM/RCM)?

We now have a SQL program moving to QUAL. An existing PROC in JCL that is run every day, but for internal reasons doesn't spawn the RCM move step, just copies the RCM Load Module. When I ran that step manually today, it didn't seem to work (the program didn't work properly in QA.)

The production move PROC seems to move the object RCM and re-generates the ACM from the RCM. Don't know if that works or not.

Now for my question:

What should I be doing to get these SQL programs "moved" and working properly?

Are there date/time stamp issues between the program object and the RCM object?

Thanks to you IDMS SQL gurus out there for your help.

Dick
Richard Pierce

Outcomes