Introduction

In this example, we assume the environment being used is called PROD if your environment name is different, you will need to substitute it in the command examples shown.

Take the following steps to confirm the environment you wish to migrate:

  1. Type the command: GO HALCYON
  2. Take Option 42 ‘Configuration menu’
  3. Take Option 3 ‘Work with Environments’

You can also run the command: HALPROD/WRKENV

You may only have one environment but you can have multiple.

Options

There are two options available when migrating data and configuration from Halcyon;

  1. Run an IMPENV (IMPort ENVironment) on the target to get the data from the source.
  2. Perform a Halcyon DUMP on the source and then import the environment into the target.

You would only perform a Halcyon DUMP if the Source and Target are not connected via the network.

Limitations

  1. Halcyon MUST be at the same version on both the source and target systems.
  2. Halcyon must be shut down on the target system (the system you are importing into). To check what version of Halcyon you are currently running, please run the command: HALPROD/DSPPRDINF

Licence codes

Halcyon licence codes are imported also when using *ALL. Be aware that you may need to correct licence codes after using IMPENV and specifying *ALL for “data to import”.

Importing data from a source System using IMPENV

Communications check

Before carrying out the IMPENV, please ensure that the Source and Target can communicate with each other. Take the following steps to confirm this:

  1. Type the target system use the command: HALPROD/WRKRMTLOC
  2. Take Option 9 ‘Test Comms’ against the location you are importing from.
  3. If the Message states the location responded, then proceed to the next step.

If it states ‘ *** is not responding ‘ (*** being your location), then you will need to perform the following:

  1. Is there a corresponding location in WRKRMTLOC on the system that didn’t respond?
  2. Are there any Firewalls inbetween that could be blocking this?

Check FTP is available between the source and target

Check that you can FTP to the remote (source) system from the target.

FTP RMTSYS(‘HOSTNAME’)

This is important as the IMPENV process will connect to the source system using FTP.

Perform the Import

To run the IMPENV command we need to ensure that Halcyon is not started on the target system you are importing into.

To perform an IMPENV, use the following command on the target LPAR and prompt (F4): 

HALPROD/IMPENV

  1. Select the system you are importing the data from (the source)
  2. Specify the environment that you are importing the data from.
  3. Specify what products you wish to import. If you are doing a migration, this will be *ALL.
  4. This is where we define what data to import. There are 4 options:

*ALL – All product data except for what is defined as *EXCLUDE is imported. (*EXCLUDED data is not required for an IMPENV)

*CONFIG – Configuration data is imported, such as: Rules, Calendars, Phones etc.

*NONSYS – Non-system data is imported, such as: Alert Log, Message Log etc.

*SYS – System data is imported which does not change, such as: Menu Files, Lists etc.

5. Enter a valid username and password for the source system, so that the IMPENV can connect.

Perform a Halcyon DUMP

The first step is to understand what libraries you need to select when carrying out a DUMP. Run the command: WRKLIBPDM LIB(‘H*PROD’)

The first three letters of the library define what needs to be included in the DUMP. You may have more or less libraries than the ones listed in the screenshot.

Once you have gathered this information, take the following steps:

  1. Go into the Halcyon Main Menu on the source system
  2. Take Option 41 ‘Utilities menu’
  3. Take Option 30 ‘Dump product Data’

It is in here where you define what you would like to DUMP.

  1. This is where you select the products noted when you ran the command: WRKLIBPDM LIB(‘H*PROD’). To add all the entries, use the ‘+’ symbol and press enter. This will provide more fields to enter all of the product details.
  2. When running the WRKLIBPDM LIB(‘H*PROD’) command, you will notice a product called HAL. This is the “common library” and this will need migrating over as well. You cannot put this down as a product as it can only be selected using this parameter
  3. Specify a Save File to DUMP this to.
  4. This is where we define what data to DUMP. There are 4 options:
  • *ALL – All product data except for what is defined as *EXCLUDE is imported
  • *CONFIG – Configuration data is imported, such as: Rules, Calendars, Phones etc.
  • *NONSYS – Non system data is imported, such as: Alert Log, Message Log etc.
  • *SYS – System data is imported which does not change, such as: Menu Files, Lists etc.

Advice: If you just wish to copy the configuration, use *CONFIG, if you wish to migrate the entire environment (including logfiles, etc to a new machine) use *ALL.

If you wanted to dump all your Halcyon products (based on the libraries noted earlier), the common library and all your data, your screen will look like this:

Press <Enter> to initiate the dump and wait for it to finish.

When complete, you can now transfer the save file from the source to the target machine by using FTP, tape or some form of replication.

To Restore from a Halcyon DUMP

To restore from a Halcyon DUMP, you will first need to get the Save File on to the new system. Once there, you’ll need to run the IMPENV command and specify the Save File this was dumped to.

  1. Select *SAVF as this is where the data was dumped to
  2. Specify the Save File that you dumped the data to
  3. Specify what environment you dumped this data from
  4. Select this to *ALL as it will restore everything from the Save File
  5. Select this to *ALL as it will restore everything from the Save File.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 29, 2020