MKS implementer issue
We use the product MKS implementer to manage our implemention of file and program changes from a test environment to production.
Whenever we make a file structure change to the physical file, such as increasing a field size in our test environment and then implement the change, the logicals associated with that physical file do not reflect the change. I then must go thru manually recreating each of the logicals.
Is anyone familiar with this problem? It could be that we don't have implementer configured properly.
As always, your help is appreciated.
Software/Hardware used:
MKS Implementer
Software/Hardware used:
MKS Implementer
ASKED:
October 22, 2012 1:46 PM
Answer Wiki:
Last Wiki Answer Submitted:
Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.
When you add an obect to check out there is an option “9 – display related objects”. Use this option to display and then select all the related objects.
I understand what you are saying but I thought implementer,recognizes something has changed in the physical file and manages recreating the logicals at the time of promotion and implementation? I didn’t think that I have to check out each logical?
Thanks for your help
I didn’t think that I have to check out each logical?
You possibly don’t… if you set the configuration appropriately.
Unfortunately it’s been more than 12 years since I’ve seen how MKS works. I don’t how configuration changes might be made.
But why aren’t you asking MKS Support this question? This is a major reason for product support to exist.
Tom
Sorry Tom. Just thought someone might have some ideas. MKS is now owned by the company PTC and I’m having problems finding support on this particular product.
Issues with “Support” for a 3rd-party product would seem to be a valid subject. Does the MKS Technical Support Integration Update page not provide a working phone number or e-mail contact address? — Tom