RE: Transferring *PGM objects from one one machine to another -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

PS-- Aldon/CMS takes care of authority-- it keeps existing authority for an updated object; for a new object you create 'template' objects with the authority you want that type of object to have.

Aldon/CMS uses SAVFs under the covers. Not sure if it uses any SAVRSTOBJ or similar commands. It may just read the SAVFs using a program and re-build them at the other end.

From the days before ACMS, we have an "Install Quick & Dirty" command that saves an object, reads/restores the SAVF, then uses a home-built "archive" command that renames the existing object and restores the new object.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Thursday, May 17, 2018 1:18 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Transferring *PGM objects from one one machine to another

This is a reality check. I am thinking I may have missed a drag and
drop solution...

What do you like, in general, as the preferred solution to move compiled
objects from a development box to a production box?

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.