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:
You can also run the command: HALPROD/WRKENV
You may only have one environment but you can have multiple.
There are two options available when migrating data and configuration from Halcyon;
You would only perform a Halcyon DUMP if the Source and Target are not connected via the network.
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”.
Before carrying out the IMPENV, please ensure that the Source and Target can communicate with each other. Take the following steps to confirm this:
If it states ‘ *** is not responding ‘ (*** being your location), then you will need to perform the following:
Check that you can FTP to the remote (source) system from the target.
This is important as the IMPENV process will connect to the source system using FTP.
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):
*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.
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:
It is in here where you define what you would like to DUMP.
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, 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.
Still have questions? We can help. Submit a case to Technical Support.