Previous | Contents | Index |
Provides a list of access records or information about an access record or group of access records.The lsacc command is used to display directory information about an access record.
lsacc access [-options]
Alternatedirectory -access
general options:
-comment
-[no]log
-[no]confirm
-identifier
-idtype
-idname
-local_user
-member
-password
-privileges
-env [= prefix_string,format](prefix default = sc)(format default = "$ %s = \" " %s \" "")
-type
#1 |
---|
Schedule> lsacc pjones -full /syscontrol/users/pjones Type = User Settings Comment = Default user setting Identifier = 0xc0000003 Member of = Privleges = AllAccess Password = ******** |
-comment
The COMMENT option is the comment that is associated with an access record.-identifier
The IDENTIFIER option is used to map the access record to a distinct id number. This is usually performed automatically when the record is created.Usage: User Settings, Group Settings, Map Identifier, Next Identifier
-idtype
The IDTYPE option is the used in the map identifier record to identify the map as a User or Group setting.Usage: Map Identifier (System Created)
-idname
The IDNAME option is the used in the map identifier record to identify the corresponding access record name.Usage: Map Identifier (System Created)
-full
The FULL option displays any comments, a variable's value and its type. In the case of a variable expression, it displays the resulting value when the expression is evaluated.-local_user
The LOCAL_USER option is the used in the "proxy for a remote user" access record to identify the local user that is being mapped to this proxy recordUsage: Proxy for a remote user (System Created)
-member
The MEMBER option is used to add an access record to a master record such as Administrator. For instance is you add a user to the Administrator record, the user will possess all access rights of Administrator.Usage: User Settings
-password
The PASSWORD option is the system password that is entered the first time you use SCHEDULE. Usage: User Settings-privileges
The PRIVILEGES option is used to assign any of 5 access privileges to an access record. The possible privileges are:
Field Description AllAccess Grant Access to the entire database ReadAll Grant Read Access to the entire database SubmitAny Grant ability to submit any job ChangeUser Grant ability to change the user of a job Disabled Deny all types of access to this user None No access privileges Usage: User Settings, Group Settings
-env[=prefix_string] or [=(prefix_string,format)]
The environmental variable option requests that all access information be output to a file containing a list of enviroment variables. Every field in the control record is listed in the file as an environment variable. The environment variable name is constructed by prefixing the field name with the provide string. If none is provided a default value of SO is used.The format defines the way that environmental variables are output. The default output specification is: "$export %s=\" %s\" "" (ksh), "$setenv %s=\" %s\" "" (csh) which produces the following format style.
SO_IDENTIFICATION = "0xc00000d8"Alternate output styles may be created by changing the format field.
-template=/schedule_library/template_db.schedule
The template option formats the directory output as it is defined in the template file /schedule_library/template_db.schedule . This output can be used for a variety of reasons and can be output to a file using the OUTPUT option . The supplied template file extracts all database information into a format suitable for insertion if desired.-env[=prefix_string] or [=(prefix_string,format)]
The environmental variable option requests that all access information be output to a file containing a list of enviroment variables. Every field in the control record is listed in the file as an environment variable. The environment variable name is constructed by prefixing the field name with the provide string. If none is provided a default value of SO is used.The format defines the way that environmental variables are output. The default output specification is: "$export %s=\" %s\" "" (ksh), "$setenv %s=\" %s\" "" (csh) which produces the following format style.
SO_IDENTIFICATION = "0xc00000d8"Alternate output styles may be created by changing the format field.
-type
The TYPE option is used to categorize the access record according to how it will be used. The possible types are:
Field Description Group Settings For group access records User Settings For user access records Proxy for a remote user When creating a proxy record for a remote user Map Identifier For internal mapping of access records Next Identifier Place holder for next access record Usage: User Settings, Group Settings, Proxy for Remote User, Map Identifier, Next Identifier
Create an access file.The mkacc command is used to create an access file.
mkacc access [-options]
Alternatecreate -access
general options:
-comment=comment
-[no]log
-[no]confirm
-identifier=id
-idtype=type
-idname=name
-local_user=user_name
-member=group
-password=password
-privileges=access_priv
-type=access_type
#1 |
---|
Schedule> mkacc pjones -privileges=allaccess |
-comment=comment
The COMMENT option is the comment that is associated with an access record.-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-identifier=id
The IDENTIFIER option is used to map the access record to a distinct id number. This is usually performed automatically when the record is created.Usage: User Settings, Group Settings, Map Identifier, Next Identifier
-idtype=type
The IDTYPE option is the used in the map identifier record to identify the map as a User or Group setting.Usage: Map Identifier (System Created)
-idname=name
The IDNAME option is the used in the map identifier record to identify the corresponding access record name.Usage: Map Identifier (System Created)
-local_user=username
The LOCAL_USER option is the used in the "proxy for a remote user" access record to identify the local user that is being mapped to this proxy recordUsage: Proxy for a remote user (System Created)
-member=group
The MEMBER option is used to add an access record to a master record such as Administrator. For instance is you add a user to the Administrator record, the user will possess all access rights of Administrator.Usage: User Settings
-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.-password=user_password
The PASSWORD option is the system password that is entered the first time you use SCHEDULE.Usage: User Settings
-privileges=access_priv
The PRIVILEGES option is used to assign any of 5 access privileges to an access record. The possible privileges are:
Field Description AllAccess Grant Access to the entire database ReadAll Grant Read Access to the entire database SubmitAny Grant ability to submit any job ChangeUser Grant ability to change the user of a job Disabled Deny all types of access to this user None No access rights Usage: User Settings, Group Settings
-type=access_type
The TYPE option is used to categorize the access record according to how it will be used. The possible types are:
Field Description Group Settings For group access records User Settings For user access records Proxy for a remote user When creating a proxy record for a remote user Map Identifier For internal mapping of access records Next Identifier Place holder for next access record Usage: User Settings, Group Settings, Proxy for Remote User, Map Identifier, Next Identifier
Rename an access record.The mvacc command is used to rename an access record.
mvacc access [-options]
Alternaterename -access access_record
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> mvacc sch_test_acc |
-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
Delete an access record.The rmacc command is used to delete an access record.
rmacc access [-options]
Alternatedelete -access access_record
general options:
-[no]log
-[no]confirm
-hostname = target_node
#1 |
---|
Schedule> rmacc sch_test_acc |
-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
12.2 Workgroup commands
EnterpriseSCHEDULE features the concept of workgroups. The basic
functions of Workgroups is to:
This includes the capability to apply load balancing to EnterpriseSCHEDULE job flow by determining the best way to distribute workload. For instance you can apply more job runs to your more powerful servers and allow the jobs to run across multiple nodes, alleviating the load on a single server. This can all be automated by establishing several simple parameters to the Workgroup which the jobs are running in.
Workgroup commands are used to create, edit, delete, copy and rename Workgroups. Workgroups are established by creating and editing an entry in the EnterpriseSCHEDULE database in the /syscontrol/workgroups directory. Once the Workgroup has been created, Member nodes are added and these nodes are assigned a number of parameters that determine how they will perform job processing within the Workgroup. The Workgroup commands are:
Modify a workgroup.The chwg command will modify a workgroup in the database. Modify workgroups in the /syscontrol/workgroups directory. All other directories are not valid Workgroup directories.
chwg [-options] workgroup_name
Alternatemodify -workgroup [-options] workgroup_name
general options:
-[no]log
-[no]confirm
-hostname = target_node
Workgroup options:
-comments=comment
-type=database_type
-mode=execution_mode
-state=status
-owner=owner
-protection=protection
-members=workgroup_members
#1 |
---|
Schedule> chwg /syscontrol/workgroup/test_wg -mode=roundrobin modified /syscontrol/workgroup/test_wg/ |
-comment:"any text string"
The COMMENT field is any useful description that you may want to add. This is an 80 character option.-confirm
-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.-log
-nolog
The LOG qualifier causes each completed operation to issue a note to the user.-members=member_string
The MEMBERS qualifier sets the nodes that are in the Workgroup and the Power rating, job limit and Quorum Votes that the node will have. The MEMBERS string is formulated as:
node_name+power_rating#job_limit%quorum_voteswhere:
Members Description node_name Name of the node to be added to the Workgroup power_rating Rated power level of the node in the Workgroup job_limit Number of jobs that will be allowed to run on that node at one time quorum_votes Number of votes that the node will have in case other nodes fail -mode=execution_mode
The MODE qualifier determines how the workgroups will execute job submissions. The possible modes are:
Mode Description all Run on ALL nodes in the Workgroup roundrobin Run in the nodes in a round-robin fashion failover Run on the first accessible node on the workgroup least Run on the least busy node in the workgroup none No jobs can run in the workgroup -owner:uic
The OWNER field indicates the owner user id and group id code for the workgroup.-protection:[who]-permission
The PROTECTION field modifies the read, write and execute permissions of specified workgroup.who specifies whether permissions are being defined for user(u), group(g) or all others(o).
permission specifies the permissions being defined. Read permission(r) allows reading. Write permission (w) allows the ability to write out a new version. Execute permission(x) allows execution of jobs and calendars, search of directories.-state=execution_state
The STATE qualifier determines whether the database is running jobs or paused. The states are:
State Description not All jobs are PAUSED or waiting to run run All jobs are allowed to RUN -type=execution_type
The TYPE qualifier determines how the database will be distributed throughout the Workgroup, whether it be through clustering or replication. The types are:
Type Description limited The database is shared using a limited cluster system full The database is shared using a fully clustered system distributed The database is distributed between nodes replicated The database is distributed and replicated among nodes
Previous | Next | Contents | Index |