Files > UCI ASSOCIATION

name
UCI ASSOCIATION
number
14.6
location
^%ZIS(14.6,
description
Most TaskMan tasks run in the same uci and volume set in which they were created. However, tasks that need a device that is only available from a different volume set can not. Such tasks must run on the volume set from which the device is available, in a uci equivalent to their current one. Equivalent ucis on different volume sets can have different names, so this file indicates which ucis on different volume sets are equivalent. TaskMan only directly uses the "AT" and "AV" indices. The "AT" index has this structure: ^%ZIS("AT",.01,1.5,2.5,3)="", and is used to find equivalent ucis on different volume sets. The "AV" index has this structure: ^%ZIS("AV",1.5,.01)="", and is used to determine whether a certain uci is part of a certain volume set. Whenever the VOLUME SET field of the VOLUME SET file is changed, a MUMPS cross-reference searches through this file and re-cross-references all pointers to that entry, thereby keeping the two files in synch.
applicationGroups
ZT
Fields
#NameLocationTypeDetailsIndexDescription
.001number11Answer should be a unique number, used to identify this file entry.
.01from uci(+)0;1FREE TEXTBAnswer should be the name of a uci from which a task is being transferred.
1from volume set(+)0;5POINTER14.5Answer should be the name of the volume set from which the task is being transferred.
1.5from volume set (free text)0;2FREE TEXTThis field is write protected and uneditable. It is triggered by field 1, and holds the resolved pointer values for use in the file's cross- references.
2to volume set0;6POINTER14.5Answer should be the name of the volume set to which the task is being transferred.
2.5to volume set (free text)0;3FREE TEXTThis field is write protected and uneditable. It is triggered by field 2, and holds the resolved pointer values for use in the file's cross- references.
3to uci0;4FREE TEXTAnswer should be the name of the uci to which the task will be transferred.

Not Referenced