Remote Site Management › Remote Site Procedures › Initial Installation at a Remote Site

Initial Installation at a Remote Site

Install CA 2E Translator on the development machine if necessary, working through the Installation section of the user guide and the Set Up menu.

Be sure to complete the following steps:

• Set up system parameters
• Set up target environments (including the planned new remote site)
• Clear down the CA 2E Translator environment

Ship the CA 2E Translator programs, data, and runtime libraries to the remote machine and restore them there. Save/ship the data library with savdta(*no). Be sure to use the same library names as you did on the development machine.

Set up the environment for the remote CA 2E Translator user including user profile, library list, initial menu, and so on. The remote CA 2E Translator user’s library list should contain the same libraries as the development machine.

Your application model and source code are not required by CA 2E Translator on the remote machine. However, a library must exist with the name of the application generation library (aplgenlib) on the remote machine—create this library if it is not already present. If the library already exists, be aware that CA 2E Translator moves the development machine versions of the prompt messages file, the user messages file, and the conditions file into this library from the export library during the import process.

Obtain authorization codes for the remote machine and apply them using the Grant Licensing Authority (YGRTLICAUT) command.

View the System Parameters screen and confirm that all values are correct.

Important! You cannot change these values at the remote site—they are protected and held in data areas.

Run the Cleardown Translator Environment option at the remote site.

Create Target Environment libraries for each now-local environment.

Check the Translator libraries are being backed up on the remote machine.