|
|
|
|
|
|
|
| ☜ | User and Group (Job)Draft MDC Standard | ☞ | ||||
| ^$Job( processid , expr1 V "UseR" ) | = | expr2 |
| ^$Job( processid , expr1 V "GROUP" ) | = | expr2 |
If and only if the process identified by processid is associated by the implementation with a user for security purposes, the value of the node “UseR” is an implementation-specific unambiguous identifier of the user owning the process.
If and only if the process identified by processid is associated by the implementation with a group of users for security purposes, the value of the node “GROUP” is an implementation-specific unambiguous identifier of a user group to which the user owning the process belongs.
These are write-once ssvns. At the time of process initiation as the result of execution of a Job command, the ssvn values associated with the initiating process are copied to the ssvns associated with the new process’s processid unless overridden, in an implementation-specific manner, by the processparameters on the Job command’s jobargument. If a node has a $Data value of 0 or 10, the process may create the node and assign an unconstrained value to it. When a node has a $Data value of 1 or 11, a value may not be assigned nor may the node be Killed; when a process attempts to do so an error occurs with ecode = “M96”. At the termination of the process identified by processid, these ssvns become undefined.
|
|
|
|
|
|
|
Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.
Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.
This page most recently updated on 18-Nov-2023, 11:33:17.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)