Seat based licences

Date:Archived
Product/Release:LANSA for iSeries
Abstract:How do the seat based licences like Dnn work, what is checked, how many sessions are available, how many log on's are permitted ?
Submitted By:LANSA Technical Support

Seat licences have the format 'Pnn' where 'P' is the product code and 'nn' represents the number of seats in hexadecimal characters(ie: in the range 0 to 9 or A to F). When using the product, each new session is allocated one of the seats up to the maximum indicated by the licence type. It is possible to have up to 255 seats depending on the licensing agreement.

Development in LANSA for iSeries

For development in LANSA for iSeries, a development seat licence (Dnn) is allocated when:

  1. creating a function
  2. editing an existing function's RDML (including viewing)

In the case of (1) the slot is de-allocated as soon as the function is created.

In the case of (2) the licence is de-allocated when the user exits the editor.

This means that another developer/session/user/workstation CANNOT edit RDML (including doing a FFC) while the initial developer is in the editor. However, multiple COMPILES may be active in batch doing FFC's, etc. Compiles do not allocate a slot.

Development in LANSA for Windows

For development in LANSA for Windows when required to use the host monitor to the AS/400, a development seat licence (Dnn) will also be required.

When a customer purchases LANSA for Windows, they will receive a LINK/400 (LPC) licence as part of the package.

If a customer wants to use LANSA for Windows concurrently with LANSA/AD to do development in both environments, then the number of LANSA for Windows copies (with dongles) purchased may be greater that the number of "seats" purchased for LANSA/AD.

Other seat licence issues

If the maximum number of seats are currently being used, a specific error message will be displayed saying "Development licence/slot not currently available". Try again later when a developer has finished editing a function or a LANSA/PC host monitor has terminated.

In the event of a crash, any locks disappear when the job ends. If for some reason the locks are not released after exiting RDML changes or the current jobs hangs, the worst case scenario would require a signoff/sign on again.

For more information on licensing, refer to Appendix B, of the LANSA for iSeries Users Guide.

For more information on "Seat based usage" licences, refer to the LANSA for iSeries Installation and Maintenance Guide from Release 6.5.