Additional files in the log/usermod folder
The log/usermod folder contains several files that provide useful information about different activities, such as successful and failed commands, internal errors, and ignored users. You can use these files to debug issues with your entities, users, and commands.
useSAFOnly is set to true. The additional files in the log/usermod folder can be used only when useSAFOnly is set to false. izpCommand and izpUserlist are the most important files because these are the only two files that you can use for manual maintenance. When you use -DRYRUN to run the modify user script, these two files get copied into the components.izp.dataset.hlq.USERLIST.COMMANDS and components.izp.dataset.hlq.USERLIST.PROPOSED data sets so that you can easily access them.
The components.izp.dataset.hlq.USERLIST.COMMANDS data set contains a list of all the commands that should be run based on the parameters you passed, such as -CONNECT. The components.izp.dataset.hlq.USERLIST.PROPOSED contains the proposed state of the user list.
The following table describes the various files that you will find in the log/usermod folder:
| File name | Description |
|---|---|
| izpUsers | A list of users that will be or were modified. If you use the -DRYRUN option, izpUsers lists the users that will be modified. Without the -DRYRUN option, izpUsers lists the users that were modified as a result of the various commands that were run. |
| izpCommands | A list of all commands. This file is populated only when you use -DRYRUN to run the modify user script. If you run the script without -DRYRUN, the files izpCommandsSucceeded and izpCommandsFailed are populated instead of izpCommands. |
| izpCommandsSucceeded | A list of commands that ran successfully. This file is populated when you run the modify user script without -DRYRUN. |
| izpCommandsFailed | A list of commands that failed. This file is populated when you run the modify user script without -DRYRUN. |
| izpUnprocessedEntities | A list of users and groups that could not be processed. Most probably, either the user and the groups did not exist or you did not have access to view them. |
| izpIgnoredUsers | A list of users who were not eligible to perform the operation for which they were being used. For example, if a user that already existed in a group was being added to it, that user would be ignored and listed in the izpIgnoredUsers file. |
| izpUserlist.tmp | The last state of the user list. |
| izpUserlist | The current state or proposed state of the user list depends on whether or not you used -DRYRUN. |
| izpErrors | The internal errors that occurred within the script caused them to end unexpectedly. |
IZPUSRMD as a shell script:
- Navigate to the location of the script:
components.izp.runtimeDirectory/ums/opt/bin. - Run the command in the following format:
./izp-modify-users.sh <-DRYRUN | > <-CONNECT | > <ADD | REMOVE> <SUPER | ADMIN> <USERS_AND_GROUPS>For example:./izp-modify-users.sh add super usera groupa userb groupb
After the script completes running, if the files listed in the Table 1 contain data, it is displayed on the terminal.