This control statement is used to set project information.
Synopsis
PRJ ---------- (1) projectname project name ---------- (2) (*) (*1) username owner(OS user) ---------- (3) (**) (*2) manage_user IDs of update rights users (OS users) ---------- (4) (*2) change_user IDs of change rights users (OS users) ---------- (5) (*2) operate_user IDs of operation rights users (OS users) ---------- (6) (*2) monitor_user IDs of reference rights users (OS users) ---------- (7) (*2) manage_com_user IDs of update rights users (Systemwalker user ID) ---------- (8) change_com_user IDs of change rights users(Systemwalker user ID) ---------- (9) operate_com_user IDs of operation rights users (Systemwalker user ID) ------ (10) monitor_com_user IDs of reference rights users (Systemwalker user ID) ------ (11) ;
The projectname operand should be specified immediately after the PRJ keyword.
No user principal name should be specified.
This must be specified.
This must be specified when registering.
About This Control Statement
(1) PRJ
This is the keyword which indicates the beginning of a project information control statement.
(2) projectname Project name
Specify the project name in 50 bytes or less. The following characters may not be used to specify a project name: /?*;,\"<>|:'., space, or any user-defined character. In addition, # cannot be used for the first character.
# can be used for the first character if the attribute of all the job nets in the project is the following:
Normal attribute
This is not case-sensitive. [Windows]
Note that, if the project name that has already been set up is specified, the setting information of already existing project is replaced by this new setting information.
This is case-sensitive. But, if project names with the same spelling but different case are registered separately, the schedule information cannot be collected properly with the policy extraction. [UNIX]
(3) username Owner (OS user)
Specify the user ID of the project owner.
If the impersonation option is specified with the Job Execution Control, this ID can be a user ID used to impersonate the job execution right. Specify the name in the "domain name\user ID" format. The maximum length of user ID is up to 36 bytes (15 bytes for domain name +1 byte for a backslash (\) + 20 bytes for user ID). If you omit the domain name, it is defaulted to the name of the computer where the Jobscheduler service resides. Group names (either for a local or global group) cannot be specified. Also, a user ID containing blank spaces cannot be specified. [Windows]
Specify the user ID of the project owner within 20 bytes. A user ID containing blank spaces cannot be specified. Even when the Extended User Management function [UNIX] or Systemwalker authentication repository is enabled, always specify the OS user for the owner. [UNIX]
(4) manage_user ID of user having update right (OS user)
Specify a user ID to whom permissions to update projects are given.
Specify the user ID in the "domain name\user ID" format. The domain name (including the backslash (\)) can be omitted. The ID must be specified in 36 bytes or less (if specifying a user ID only, it is up to 20 bytes). [Windows]
If the Extended User Management function is enabled, specify the Operation Manager user within 20 bytes in length. [UNIX]
If the Systemwalker authentication repository is enabled, specify the OS user to be given update rights when executing commands.
A group name can also be specified.
Multiple user IDs can be specified by separating them by a comma (,). Note that the ID cannot contain blank spaces.
When you want to delete all the registered users who have the permission to update, you can do it by omitting the user ID in manage_user.
(5) change_user ID of user having change rights (OS user)
Specify the ID of the user to be given change rights.
Specify the user ID using the following format: domain name\user ID. The domain name part (before the \ character) can be omitted. Specify no more than 36 bytes (or no more than 20 bytes if only the user ID is specified). [Windows]
If the Extended User Management function has been enabled, specify an Operation Manager user using no more than 20 bytes. [UNIX]
If the Systemwalker authentication repository is enabled, specify the OS user to be given change rights when executing commands.
It is also possible to specify group names. To specify more than one user ID, separate user ID by commas (,). User IDs that contain spaces cannot be specified.
To delete all change right users that have been registered, omit the user ID specified in the "change_user" control statement.
(6) operate_user ID of user having operation right (OS user)
Specify a user ID to whom permissions to operate projects are given.
Specify the ID in the "domain name\user ID" format. The domain name (including the backslash (\)) can be omitted. The name must be specified in 36 bytes or less (if specifying a user ID only, it is up to 20 bytes). [Windows]
If the Extended User Management function is enabled, specify the Operation Manager user within 20 bytes in length. [UNIX]
If the Systemwalker authentication repository is enabled, specify the OS user to be given operation rights when executing commands.
A group name can also be specified.
Multiple user IDs can be specified by separating them by a comma (,). Note that the ID cannot contain blank spaces.
When you want to delete all the registered users who have the permissions to operate, you can do it by omitting the user ID in operate_user.
(7) monitor_user ID of user having reference right (OS user)
Specify a user ID to whom permissions to monitor/view projects are given.
Specify the ID in the "domain name\user ID" format. The domain name (including the backslash (\)) can be omitted. The name must be specified in 36 bytes or less (if specifying a user ID only, it is up to 20 bytes). [Windows]
If the Extended User Management function is enabled, specify the Operation Manager user within 20 bytes in length. [UNIX]
If the Systemwalker authentication repository is enabled, specify the OS user to be given reference rights when executing commands.
A group name can also be specified. Multiple user IDs can be specified by separating them by a comma (,). Note that the ID cannot contain blank spaces
When you want to delete all the registered users who have the permissions to reference, you can do it by omitting the user ID in monitor_user.
(8) manage_com_user ID of user having update right (Systemwalker user ID)
Specify a Systemwalker user ID to whom permissions to update projects are given. This can only be specified when the Systemwalker authentication repository is enabled.
Specify no more than 32 bytes.
Delimit with commas when specifying more than one.
To delete all update right Systemwalker user IDs that have been registered, omit the Systemwalker user ID specified in manage_com_user.
(9) change_com_user ID of user having change rights (Systemwalker user ID)
Specify a Systemwalker user ID to whom permissions to change projects are given. This can only be specified when the Systemwalker authentication repository is enabled.
Specify no more than 32 bytes.
Delimit with commas when specifying more than one.
To delete all change right Systemwalker user IDs that have been registered, omit the Systemwalker user ID specified in change_com_user.
(10) operate_com_user ID of user having operation right (Systemwalker user ID)
Specify a Systemwalker user ID to whom permissions to operate projects are given. This can only be specified when the Systemwalker authentication repository is enabled.
Specify no more than 32 bytes.
Delimit with commas when specifying more than one.
To delete all operation right Systemwalker user IDs that have been registered, omit the Systemwalker user ID specified in operate_com_user.
(11) monitor_com_user ID of user having reference right (Systemwalker user ID)
Specify a Systemwalker user ID to whom permissions to reference projects are given. This can only be specified when the Systemwalker authentication repository is enabled.
Specify no more than 32 bytes.
Delimit with commas when specifying more than one.
To delete all reference right Systemwalker user IDs that have been registered, omit the Systemwalker user ID specified in monitor_com_user.
Cautions
You cannot specify the same user ID or group name more than once in a single control statement. However the same user ID can be specified if they are for Systemwalker user ID and OS user.
If you set another access right to the user to whom the access right has been given, his or her existing access right is overwritten.
Example of project information control statement
In the following example, the project name is set to "GeneralAffairsDept", the owner is set to "john", the ID of the update rights user is "james", the ID of the change rights user is "kerry", the ID of the operation rights user is "julie" and the IDs of the reference rights users are "anthony" and "mike".
PRJ projectname GeneralAffairsDept username john manage_user james change_user kerry operate_user julie monitor_user anthony,mike ;
