LanTurn^™ (the LANSA Interface)

LanTurn^™ the TurnOver^™/LANSA^™ Interface, lets you manage LANSA changes within the framework of the TurnOver Change Management system. LANSA definitions are checked out from a production partition into a development partition, changed and promoted the same way other iSeries (AS/400) source and objects are managed by TurnOver. LanTurn provides a more productive LANSA development environment with features like LANSA cross-reference, RDML compare and distribution. Manage the Web with ease as LanTurn supports both LANSA for the Web and Visual LANSA.

TurnOver allows you to analyze and change LANSA applications and your 3GL applications on the same Worklist. Functions such as source compare are fully supported with LanTurn. With just one software change management system to learn, your staff will be productive quickly. Whether your development and production are on the same computer or you distribute changes, your LANSA objects will be installed reliably, every time.

Developers will appreciate the fact that they will not need to import or export LANSA objects between production, test and development partitions; this is done behind the scenes by LanTurn commands. Furthermore, it handles modification of all data library names within the data model during checkout — eliminating the problems that occur when definitions are copied between partitions.

Setup

LANSA "object types" —field, file, function, process, application template, system variable, multi-lingual variable, Visual component, and Web component — are all known to TurnOver. These are activated automatically for you during installation of LanTurn.

LANSA applications are identified by TurnOver application definitions the same way 3GL applications are defined. Any number of development steps (development-to-test, test-to-QA, and so on) are supported. Sample application definitions are provided so you can quickly create your own definitions by copying the sample.

If you distribute changes using TurnOver now, no additional setup is required to distribute LANSA objects. If you are new to TurnOver, distribution to one or more production systems can be done efficiently and quickly

Using the LanTurn Interface.

Analyze LANSA definitions more efficiently

You can analyze LANSA RDML easily using LanTurn's powerful definition compare facilities. Once you identify the definitions you need, add them to your Programmer Worklist. Browse the definitions on your Worklist without starting up another LANSA session, and without opening the definition for update. Want to compare RDML to see what changed last time? A powerful compare utility is built into LanTurn.

Checkout definitions

Checkout LANSA definitions and get to work. Checkout provides you with a record of which LANSA definition each developer is using and, optionally, can lock them so nobody else can change them while they are checked out to you. An audit trail is maintained of all checkout activity. An emergency change feature, used when you need to fix a production object currently being revised, is included.

Make LANSA code changes

Select any definition on your Worklist and modify your LANSA RDML, just as you would normally do. After testing in development, you are ready to promote for further testing, or back into production, as desired.

Build a promotion request

Once you are satisfied with your changes, select the LANSA definitions you want to promote and submit a TurnOver form. You can schedule your promotions to run any time. When a promotion runs, LANSA definitions are exported from your development partition into the target partition. iSeries and AS/400 objects are generated into your target libraries. LanTurn's cross-reference system protects you from the potential of level checks. If problems occur during the promotion, changes can be rolled back automatically. You can even roll back changes after they are installed, if necessary.

Distributing LANSA objects

You can schedule and distribute iSeries objects and, conditionally, LANSA definitions, to any number of production computers any time after the promotion is done. TurnOver will send back confirmation messages and update the project status on your development computer.

Security

Only people authorized to use TurnOver can work with LANSA applications. You authorize each developer only to those applications and LanTurn functions they need.

Link to LANSA Task Tracking

When a TurnOver task is created, LanTurn can be configured to automatically create a corresponding LANSA task and to update that task as work progresses. Once a developer's work is complete, LanTurn is used to filter objects by LANSA task ID and to build a TurnOver Worklist, ensuring all related changes are captured for checkout and promotion through TurnOver.

LanTurn is licensed separately from TurnOver.

Interface & Application Software Support

You can use TurnOver's many APIs or built-in interfaces to bridge to any software package, including:

Built-In Interfaces	Application Support	Optional Interfaces*
Abstract^™	ASI^™	AllFusion 2E^®
AllFusion Plex^™	BPCS^®/ERPLX	AS/SET^®
Code/400^™	PRMS^™	Dimensions^™
Deploy/400^™	PKMS	LANSA^™/Visual LANSA
JD Edwards World^®	HFA^™/Friedman	ProGen Plus^™
Lawson	Infinium^™	Subversion for OS/400
PathFinder	JBA^™	*Optional interfaces licensed separately from TurnOver.
TurnOver PDQ^™	JDA^™
Version Manager^™	JHA^™
WebSmart^™	MAPICS
	Island Pacific
	Kronos
	Movex
	Premenos