permsmaint - Permissions Maintenance

Program Option Description
U Prints usage and syntax.
c Creates configuration files only. This option does not set permissions.
s Sets permissions based on existing configuration files. This option does not create new configuration files.
b Both - Creates configuration files and sets permissions.
e Optional. Lawson Environment only. The default is both.
a Optional. Applications only. The default is both.
l Optional. Overwrites existing settings with Lawson settings. The default would keep modified, existing settings. The -l option overwrites all modifications with the permission settings of a security level 1, 2, or 3.
p productline Optional. Specify product line to set permissions on.
seclevel

1, 2, or 3. Use with the -c or -b option.

During installation, a 0 option lets you not create the permission configuration files during installation.

Examples

The following syntax creates level 2 configuration files and sets permissions:

permsmaint -b 2

The following syntax creates level 3 application configuration files. The ladirs.cfg file is applied against the product lines' permission files.

permsmaint -c -a 3

The following syntax sets Lawson Environment permissions based on the existing Perms.cfg file:

permsmaint -s -e

The following syntax sets permissions on product line named dev803 only:

permsmaint -s -a -p dev803

Configuration Option Description
extgrps

Optional. This configuration option handles different operating system groups defined by the user. This affects the set permission mode, -s. The user must first create an additional group or groups under Computer Management before extgrps can be used in perms.cfg and ladirs.cfg .

The maximum number of groups that can be added is 10.

Examples

The following syntax adds groups on the existing Perms.cfg and Ladirs.cfg files:

extgrps <extgroup1>,<extgroup2>,<extgroup3>

The following syntax sets permissions on the existing Ladirs.cfg files:

%lawdir%/prodline/MICROSOFT F,0,0,R,F,F

The following syntax sets permissions on the existing Perms.cfg files:

%GENDIR%\lib\help\appsec F,C,C,R,C,F

permsmaint [-U|-c|-s|-b] [-e|-a] [-l] [-p productline] [seclevel]

The permsmaint utility creates configuration files for the Lawson Environment and applications. It sets the permissions in the Lawson Environment and applications according to the settings in these configuration files.

There are options to create the configuration files and set permissions based on existing configuration files. You can also choose to both create the configuration files and set permissions at the same time.

Option -c, -s, or -b is required.

Three levels of permissions are:

  • 1 - The most open.

  • 2 - Settings developed by the Lawson Support and Delivery.

  • 3 - The most restrictive.

Note: The security level set for the Lawson Environment and applications must be the same. Both the Perms.cfg and ladirs.cfg files must have the same security level, such as 2.

The permissions maintenance configuration files can be modified to fit specific security needs. The permissions configuration files reside in $LAWDIR/system. The Lawson Environment configuration file is Perms.cfg. The applications configuration file is ladirs.cfg. Whenever permsmaint -c is run, the existing configuration files are saved to the Perms.cfg and ladirs.cfg files. In addition, the Permissions Maintenance utility attempts to merge the new settings with those in the existing configuration files so that any changes are maintained.

You can also change the owner and group of files by making the appropriate entries in the permissions configuration files, and then running the Permissions Maintenance utility to apply your new settings. For example, the following line in Perms.cfg will change the owner for jqstatus to "root" and the group to "lawson":

In addition to the existing program options, you can also add groups with the extgrps option. After defining the groups separated with a comma, (",") in the configuration files, permsmaint will check the groups and set the permission mode of every directory to the added group.

Note: When setting Read, Full Control, and Change/Modify permissions on ladirs.cfg and Perms.cfg configuration files, the first three permissions are set for Administrators, Developers, and Users, and not the extra groups.