5.3.1 Restrictions and Assumptions

• A LANSA environment must be installed on the Remote System nominated to Deliver To with a compatible version of LANSA software.

• The Visual LANSA user must be authorized to maintain Remote Systems and use Deliver To.

• The Deployment environment must be defined as a Remote System in Visual LANSA before the Deliver To command will be available against the repository objects.

• The Remote System definition must correspond with the LANSA Communications Administrator entry for this LANSA system.

Delivery will be to a corresponding partition on the Remote Deployment System.

For Remote System of build type IBM i:

• The Partition on the Deployment System must be manually defined and match the partition definition on the Visual LANSA installation.

• Before attempting to deliver any objects to an IBM i remote system you need to Refresh the system to get the workstation names from the Deployment System. Refresh is available as a command in the right click menu against the Remote System object.

• A task ID that is valid on the IBM i system is required to deliver objects to an IBM i remote system. This will be prompted when connecting.

• The Deliver To options when delivering to IBM i are the same as standard Check In options.

For Remote System of build type Linux:

• The Partition on the Deployment System must be defined and initialized before partition objects can be delivered; otherwise you can expect Deliver To to fail. Partition Initialization is available as a command in the right click menu against the Remote System object.

• When compilable objects are Delivered To a Remote System of build type Linux they will always be compiled on the target system.

• Objects that are irrelevant on the Deployment system, such as Components (including Forms), which require a Windows GUI, are not available to Deliver To the Remote System.

• Message Files are only available for delivery to Linux Deployment Systems.