Home Package List Routine Alphabetical List Global Alphabetical List FileMan Files List FileMan Sub-Files List Package Component Lists Package-Namespace Mapping

Print Page as PDF

Sub-Field: 8993.02

Package: Kernel

XULM LOCK DICTIONARY(#8993)-->8993.02

Sub-Field: 8993.02

Information

Parent File	Name	Number	Package
XULM LOCK DICTIONARY(#8993)	ARRAY SUBSCRIPTS	8993.02	Kernel

Details

Field #	Name	Loc	Type	Details
.01	SUBSCRIPT ORDER NUMBER	0;1	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>99)!(X<1)!(X?.E1"."1.N) X` LAST EDITED: `MAY 10, 2012` HELP-PROMPT: `Enter an integer indicating the order of the subscript within the locked data structure. The first subscript is 1, then 2, etc.` DESCRIPTION: `This field is the order number of the subscript in the locked data structure. For example, if the lock is on ^DPT(,0), the '0' should have 2 as its order number.` CROSS-REFERENCE: `8993.02^B` `1)= S ^XLM(8993,DA(1),2,"B",$E(X,1,30),DA)=""` `2)= K ^XLM(8993,DA(1),2,"B",$E(X,1,30),DA)`
.02	SUBSCRIPT	0;2	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>240!($L(X)<1) X` LAST EDITED: `MAY 09, 2012` HELP-PROMPT: `Enter the subscript exactly as it appears in the lock template.` DESCRIPTION: `This is the text parsed out of the LOCK TEMPLATE. For example, if the lock template is ^DPT(DFN,0), the first subscript is DFN and the second subscript is 0.`
.04	TYPE	0;4	SET	**********************REQUIRED FIELD********************** 'L' FOR LITERAL; 'V' FOR VARIABLE; LAST EDITED: `JUL 16, 2012` HELP-PROMPT: `What type of subscript is this?` DESCRIPTION: `Subscripts in the LOCK TEMPLATE can either be a literal or a variable. A literal subscript is one whose value in the lock table will match the value in this field exactly. A variable subscript is one whose value in the` `table need not match.` `There are several fields within this file that provide for executable MUMPS code to be specified. At the point the MUMPS code is executed, for each subscript defined as being type VARIABLE, the variable of that same` `name will be defined and be assigned the value that appears in the lock table for the subscript of the same position.` `For example, given the lock template ^DPT(DFN,0), with DFN defined as a variable subscript and 0 as a literal subscript.` `An entry in the lock table of '^DPT(123,0)' might be considered a match to this lock template. For any of the M code specified in the MUMPS fields, the variable DFN=123 would be defined at the point the M code is` `executed. Assuming that the variable DFN was defined to the the IEN of a record in the patient file, then the variable could be used to supply information about the patient record that the lock was on.`
1	VARIABLE CHECK LOGIC	1;E1,245	MUMPS	INPUT TRANSFORM: `K:$L(X)>245 X D:$D(X) ^DIM` LAST EDITED: `AUG 29, 2012` HELP-PROMPT: `Enter standard MUMPS code that will check whether the value of the subscript is consistent with the lock template or should be screened out. Matches should return Y=1, non-matches should return Y=0.` DESCRIPTION: `This field applies only to subscripts that are represented as a variable in the lock template, and is optional even for variables.` `If the subscript is represented by a variable, this field may contain MUMPS code that checks that the value is consistent with the use of the lock.` `For example, suppose the lock template is ^DPT(DFN,0). Does the lock on ^DPT("sally",0) match the lock template? Yes, but that is not the intention. In order to screen out erroneous matches this field may be used to` `specify a check.` `All variables that appear in the LOCK TEMPLATE will be defined at the time the logic is executed with the values parsed from the lock table. It should return the value of Y=1 if the variable value is consistent with the` `lock template, or Y=0 if not.` `For example: S Y=$S((DFN)&&$D(^DPT(DFN,0)):1,1:0)` `If the lock template contains more than one variable, it is only necessary to provide the check logic once. For example, if the lock is on ^DPT(DFN,"INSURANCE",POLICY), you could associate the full check logic with` `either DFN or POLICY. Both variables will be defined at the time the check logic is called.` `WRITE AUTHORITY: @`