It is unclear how the Name Equates table should be coded to control package subfunctions.
For example, to ensure that Backout Enabled is always selected, the package is sharable and always a standard package - how can the BC1TENQU table be coded to control this?
Release : ALL
To accomplish this make sure that the C1DEFLTS table has PKGSEC set to ESI (PKGSEC=ESI) and that the BC1TNEQU Tableis setup for Package actions and include PKGSHR, PKGBOE and PKGTYPE.
Below is an example of what the NAMEQU for Package_Actions would look like:
L6=(PKGSHR), SHARABLE PKG (Y/N)
L7=(PKGBOE), BACKOUT ENABLED (Y/N)
L8=(PKGTYPE(1,2)) PKG TYPE (STANDARD/EMERGENCY)
If a package was created with the name PACKAGE1234, that is SHARABLE, backout enabled and Standard - the entity passed to the external security package would look like this:
If a package is created with the name PACKAGE1, that is Non-sharable, backout enabled and the Package Type is Emergency - the entity passed to the external security package would look like this:
ACCESS=NONE would have to be coded for the Entity to ensure that a user would not get access to create a package that was non-sharable, backout enabled =n or was an Emergency package. Below is a few of examples of the rules/resources that would need to be created:
So if the user has access=none and they attempt to create a package where backout enabled is set to No (n) or is non-sharable or an emergency pakcage, the action should be denied and fail with a security violation.