search cancel



Article ID: 246078


Updated On:




An endevor user trying to execute a package in foreground might get error message "INVALID SELECTION" in the "Package Foreground Options Menu" panel. The ISPF message ID (displayed by MSGID command) is PKMR208E and the full message text is PKMR208E THE PACKAGE SELECTED IS NOT AVAILABLE.

How to troubleshoot this message?


Release : 18.0

Component : Endevor Software Change Manager


This message means that either

  • The package is not in the correct status for the action. For example, for EXECUTE action, it needs to be in APPROVED or EXEC-FAIL
  • The package has an execution time window and the EXECUTE action is being attempted out of the time window
  • The user has no permission to execute the package. This seems to be the case if other users may execute the package


The status of the package as well as its execution window can be checked using the 'display package' option

About security, the way endevor decides whether a userid is allowed to execute a package depends first thing on the package security model in effect set by PKGSEC= parameter in C1DEFLTS TYPE=MAIN macro. The easiest way to see this setting is via option 1 (display) and 3 (site) from the endevor primary options menu. It shows up in the second panel, in 'security' field under "Package Processing Options" and the value may be either:

  • APPROVER - The user needs to be an approver in order to execute a package
  • ESI - External security decides whether to allow the package execution
  • MIGRATE - User needs to be an approver. If it is not, external security may still allow the action

To see whether the userid is an approver for the package, go to the 'display package' panel. If option A (approvers) is highlighted, it means that the package has approvers. In this case, option A shows the approver groups associated with the package.

With PKGSEC set to APPROVER or MIGRATE, the userid will be allowed to execute the package if it is an approver for the package.
To see whether external security is allowing or denying  the access to the package, an external security trace can be obtained.

With PKGSEC set to ESI, the userid is allowed to execute the package only if it passes the external security check

With PKGSEC set to MIGRATE, what happens is that:

  • If the userid is an approver, it will be allowed to execute the package regardless of whether it is allowed to do that by ESI
  • If the userid is NOT an approver, it will still be allowed to execute the package if ESI allows it to do that
    In a few words, the checklist is:
    - Check the package security option in effect (approver, ESI or migrate)
    - If approver or migrate, see whether the user is an approver for the package
    - If ESI or if migrate with the user not being an approver, see (via an ESI trace) whether ESI is allowing or denying the action