The IMPENV command allows you to pull the live data while in use, to another environment that is dormant. This dormant environment is activated when you role swap your production system to the HA system.

How does the IMPENV command work?

Our command is invoked on the target system and connects to the source via FTP. The first task of the command is to save the Halcyon data into save files, that data is then transferred and restored on the target system, overwriting the data in the dormant environment. There are four options available for you to specify the type of data to import (i.e. all data, system data, configuration only or non-system data, such as product files only).

Typically the IMPENV command is scheduled to run daily from either the Halcyon Advanced Job Scheduler in the ‘live’ monitoring environment, or alternatively by using the IBM job scheduler. The command can be run frequently such as every 30 minutes or just once a day.

Can I restrict access to the replicated environment?

Halcyon provides a maintenance mode for environments that enables you to set the environment into a ‘locked’ state. Only the network monitors are allowed to be started so you can maintain connectivity with other Halcyon IBM i environments as well as our Enterprise Console. Any authorities or options that would normally allow add, change or delete are also disabled.

What happens when I role swap?

Following the successful completion of the IMPENV command, the specified level of data will be up-to-date and ready to go live. In order to change the environment that is responsible for your production monitoring, you will end the monitors on the production system and start the monitors on the HA system for the PROD environment. Then you need to end the monitors on the HA system and start the monitors on the production system for the HA environment.

I’m running the Advanced Job Scheduler (HJS), how does this replication method work with the schedule?

Within the Advanced Job Scheduler, you have the option to hold overdue groups from running at monitor startup. This can be controlled at environment or group level and ensures that if the HJS monitors are inactive when they are started, any job that should have ran will be held if the scheduled run time has passed. Giving you total control over how to manage your overdue schedule.

The following would be required in order to implement Halcyon’s replication between a production and HA system.

Production system

  • A PROD environment installed for production system monitoring
  • A HA environment installed for replication

HA system

  • A HA environment installed for production system monitoring
  • A PROD environment installed for replication

IBM i scheduled entries

  • Schedule HALPROD/IMPENV to run on the HA system to pull data from PROD environment on the production system
  • Schedule HALHA/IMPENV to run on the production system to pull data from HA environment on the high availability system

Role swap – how Halcyon is handled

  • Run HALPROD/ENDMON on the production system to end the production monitoring
  • Run HALHA/ENDMON on the HA system to end the production monitoring
  • Run HALPROD/STRMON on the HA system to start the production monitoring
  • Run HALHA/STRMON on the production system to start the production monitoring

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

Last Modified On: February 27, 2019