jbsaclreload
- Organization of this page
Function
The jbsaclreload command reloads the definition information about the operating permissions of JP1 users to the authentication server. When the -ds option is not specified, the listed definitions are the access permission level (JP1_AccessLevel) file and user permission level (JP1_UserLevel) file. When the -ds option is specified, the listed definitions are the access permission level (JP1_AccessLevel) file and JP1 authentication information (managed in the directory server).
Format
jbsaclreload [-h logical-host-name]
[-s authentication-server-name]
[-ds#]- #:
-
The -ds option can be specified in Windows only.
Required execution permission
In Windows: Administrators (If User Account Control (UAC) for Windows is enabled, you must execute the command from the administrator console.)
In UNIX: Superuser or JP1/Base administrator permission
Command directory
- In Windows:
-
installation-folder\bin\
- In UNIX:
-
/opt/jp1base/bin/
Arguments
-h logical-host-name
When using JP1/Base in a cluster system, specify the logical host for which you want to execute this command. The command will reload the definitions about the JP1 user operating permissions set on the specified logical host.
-s authentication-server-name
Specify the authentication server on which to reload the definitions about JP1 user operating permissions. When you specify this option, the -h option is ignored.
-ds
This option can be specified in Windows only.
Specify this option for reloading the DS user's JP1 authentication information from a directory server.
Note
-
The -s option takes precedence if you specify both the -h and -s options. If you omit both options, the host name set in the environment variable JP1_HOSTNAME is assumed as the logical host. If you omit both options and nothing is set in JP1_HOSTNAME, the definitions set on the physical host are reloaded.
-
When the JP1 authentication information of DS users is reloaded from the directory server, some users might not be accepted as JP1 users, for example, because the user name conflicts with the name of a standard user or the length of the user name exceeds the maximum length of a JP1 user name. Use the jbslistuser and jbslistacl commands to check whether the user names are acceptable. The information of users who were not accepted is recorded as warning messages in the integrated trace log of the authentication server.
-
If this command ends abnormally, check error messages in the integrated trace log of the authentication server to eliminate failure causes.
Return values
|
0 |
Normal end |
|
2 |
Invalid arguments |
|
4 |
Insufficient system resource such as memory |
|
8 |
The authentication server has not started or is not responding |
|
12 |
An error occurred in the authentication server side when a DS user was used |
|
16 |
An error occurred in the authentication server side processing |
|
32 |
An error occurred during initialization of the communication functionality |
|
128 |
Inconsistency in internal processing (a C++ exception) |
|
255 |
Other error |