LANSA LICENSE - F6 Add/Create and F22 Delete options not available

Date:18 August 2014
Product/Release:LANSA on IBM i - V13 and above
Abstract:Possible reasons for no options being available in LANSA license to Add or Delete a license.
Submitted By:LANSA Technical Support
Updated:4 May 2015

Description:

There are a few reasons why the F6 option to Add/Create licenses and the F22 option to delete a license are not available when running LANSA LICENSE.

Example screen show missing F22 option

The first set of possibilities revolve around the QOTHPRDOWN user profile that is set up as part of a LANSA installation.

  1. You should check for either a disabled QOTHPRDOWN profile or not having QOTHPRDOWN as the LANSA owner. If QOTHPRDOWN is disabled, it needs to be re-enabled in order to be able to Add or Delete licenses. If you are not planning on using QOTHPRDOWN profile as the LANSA product owner, then you must perform the steps outline in the section "If not using QOTHPRDOWN as the Product Owner" in the Installing LANSA on IBM i guide.
  2. Also related to QOTHPRDOWN, you should check the following user profile value
    Password expiration interval . . PWDEXPITV
    Some companies set a password expiration interval. If this expiration interval is passed for QOTHPRDOWN, this will make the F6 option unavailable too. Since users don't actively log in with QOTHPRDOWN (and you don't generally need to), often users are unaware that the expiration interval is passed for QOTHPRDOWN. You can overcome this by logging in with QOTHPRDOWN, where you will be required to change the user profile password and F6 will be available again. LANSA will look into enhancing the licensing to cater for this possibility.
    Be aware that the Password expiration interval (PWDEXPITV) for QOTHPRDOWN may be set to *SYSVAL. Checking the system value QPWDEXPITV, you might see a value like 90 days. Which means that once you change the QOTHPRDOWN password, you will encounter the same issue once 90 days has expired (and you haven't change the QOTHPRDOWN password in that period). You should consider setting the Password expiration interval . . PWDEXPITV for QOTHPRDOWN to *NOMAX to avoid this issue recurring.

Another possibility is that the user profile you are logged in with has the authority to view licenses but doesn't have the appropriate authority to Add/Delete licenses. Its worthwhile knowing the hierarchy of users that can Add/Delete licenses.

  • If you log in as QSECOFR or a user that is part of the QSECOFR group, you will have F6/F22 available in LANSA Licensing (whether you specify a partition or not). For example LANSA LICENSE or LANSA LICENSE Partition(NNN) will both work OK.
  • If you log in with the security officer for partition SYS and run LANSA Licence without specifying the partition, you will have F6/F22 available in LANSA Licensing. For example, LANSA LICENSE will work OK.
  • If you log in with the security officer for partition SYS and run LANSA Licence specifying partition(SYS), you will have F6/F22 available in LANSA Licensing. For example, LANSA LICENSE Partition(SYS) will work OK.
  • If you log in with the security officer for partition NNN and run LANSA Licence specifying partition(NNN) on the command, you will have F6/F22 available in LANSA Licensing. For example, LANSA LICENSE Partition(NNN) will work OK.
  • If you log in with the security officer for partition NNN and run LANSA Licence without specifying partition(NNN), you will not have F6/F22 available in LANSA Licensing. For example, LANSA LICENSE will not work OK.

A further thing to check is whether the user profile running LANSA LICENSE has the correct authorities to its own profile. To explain this possibility, lets say that we have set a user profile with very few rights (User: NORIGHTS) as the partition security officer for a partition AAA.

  • When the user profile has *ALL rights to itself according to DSPOBJAUT OBJ(NORIGHTS) OBJTYPE(*USRPRF) and we execute LANSA LICENSE PARTITION(AAA) then the license screen does have “F6=Add/Create”.
  • When the user profile has no rights to itself according to DSPOBJAUT OBJ(NORIGHTS) OBJTYPE(*USRPRF) (either covered by *PUBLIC *EXCLUDE or NORIGHTS *EXCLUDE) and we execute LANSA LICENSE PARTITION(AAA) then the license screen DOES NOT HAVE “F6=Add/Create”.

So, if you run the command

DSPOBJAUT OBJ(NORIGHTS) OBJTYPE(*USRPRF)

and you see

Group               User Group Authority
*PUBLIC             *EXCLUDE
NORIGHTS            *EXCLUDE

or something to that effect, then that also a likely reason.