Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
Can someone provide me with detailed documentation on the process that Implementer uses to promote Physical Files? I am very interested in how it handles the optimized promotion process. Our shop currently handles the promotion of physical files to the Production environment manually by running CL conversion programs to add/remove triggers, add/remove journaling, and saving/copying of the data. The general feeling is that the Implementer process is not fast/efffecient enough so I would like to review what the detailed Implementer process does.
Solved! Go to Solution.
Hi Mike,
There is detailed information in the Implementer User Guide, Chapter 10-Member and Object Management, on how Implementer promotes physical files, logical files, SQL tables, views and indexes. I've attached 2 documents you may find helpful.
An optimized promotion uses the Change Physical File (CHGPF) command over the target file and library in production to promote the DDS-based physical files on the request. In contrast, a non-optimized promotion uses the standard Copy File (CPYF) command, with the record format field mapping options *MAP and *DROP to retain existing data, over the Implementer work libraries.
Using optimize for physical file promotions achieves performance improvements that reduce the overall promotion processing time. It also reduces the temporary use of disk space that results from having multiple copies of data associated with the traditional copy file technique. Moreover, it reduces the processing time of database file promotions an average of 50 percent over non-optimized promotions.
Consider the following benchmark of a physical file with 127,000 records and 11 logical files:
When promoting DDS-based physical files on an optimized request, Implementer automatically retains any existing DDS-based triggers and constraints in the target production environment.
Please contact Support if you would like to discuss in further detail or if you are experiencing problems with file promotions in Implementer.
Hi Mike,
There is detailed information in the Implementer User Guide, Chapter 10-Member and Object Management, on how Implementer promotes physical files, logical files, SQL tables, views and indexes. I've attached 2 documents you may find helpful.
An optimized promotion uses the Change Physical File (CHGPF) command over the target file and library in production to promote the DDS-based physical files on the request. In contrast, a non-optimized promotion uses the standard Copy File (CPYF) command, with the record format field mapping options *MAP and *DROP to retain existing data, over the Implementer work libraries.
Using optimize for physical file promotions achieves performance improvements that reduce the overall promotion processing time. It also reduces the temporary use of disk space that results from having multiple copies of data associated with the traditional copy file technique. Moreover, it reduces the processing time of database file promotions an average of 50 percent over non-optimized promotions.
Consider the following benchmark of a physical file with 127,000 records and 11 logical files:
When promoting DDS-based physical files on an optimized request, Implementer automatically retains any existing DDS-based triggers and constraints in the target production environment.
Please contact Support if you would like to discuss in further detail or if you are experiencing problems with file promotions in Implementer.