|Contents:||Main||Chapter||See Also:||Getting Started Manual||Advanced User Manual|
(Required) A required variable which should be set to zero or some string whose numeric evaluation is zero, e.g., "LIST DRUGS". If set to a text string, the string is used to replace the word "SORT" in the "SORT BY:" prompts, when FileMan asks the user for sort values:
LIST DRUGS BY: NAME//
(Required) The open global root of the file in the usual format, e.g., "^DIZ(16540," or the file number.
(Optional) The various fields to be printed. If this parameter is not sent, the user will be prompted for fields to print. FLDS can contain the following:
If there are more fields than can fit on one string, FLDS can be subscripted (FLDS(1), FLDS(2), and so forth), but FLDS as a single-valued variable must exist.
(Optional) The fields by which the data is to be sorted. If BY is undefined, the user is prompted for the sort conditions. You can sort by up to seven fields; that is, you can have up to a 7-level sort.
You can set BY to:
If one of the comma pieces of the BY variable is the @-sign character, the user will be asked for that SORT BY response. So if you want to sort by DIAGNOSIS but allow the user to order the sort within DIAGNOSIS, set BY="DIAGNOSIS,@".
NOTE: You cannot use the name of a SORT template in the BY variable if the BY(0) input variable has been set. If you want to create such complex sorts, you can include the BY(0) information within the SORT template. See the section Storing BY(0) Specifications in SORT Templates, within the Details and Features section: Controlling Sorts with BY(0).
NOTE: If more than one field is included in the BY variable, separate the fields with commas. The same comma-pieces will identify the field in the FR and TO variables. If, for example, you wanted a sorted report of entries with DOBs in 1960 and with ZIP CODEs in the 90000s, you could define the variables by writing:
BY="DOB,ZIP CODE" FR="01/01/60,90000" TO="12/31/60,99999"
Since the delimiter of BY is a comma, the value placed in the variable should not contain a comma. Therefore, if your field name contains a comma, use the field number in the BY variable instead of its name. For the same reason, if sort from or to values contain commas, the alternate FR(n) and TO(n) input arrays described below should be used instead of the FR and TO input variables.
(Optional) The START WITH: values of the SORT BY fields. If FR is undefined, the user will be asked the START WITH: question for each SORT BY field. If FR is defined, it consists of one or more comma pieces, where the piece position corresponds to the order of the sort field in the BY variable. Each comma piece can be:
NOTE: If BY contains the name of a SORT template and if the developer answered NO to the question SHOULD TEMPLATE USER BE ASKED 'FROM'-'TO' RANGE... for a field at the time the template was defined, then the information in the FR and TO variables is ignored for that field. Instead, the from/to ranges stored in the sort template are used.
If you customize sorts using BY(0), see special note on FR in that section.
(Optional) An alternate way to provide the START WITH: values of the SORT BY fields. If FR is defined, it will override this array. The subscript n corresponds to the comma piece in the BY variable (i.e., the sort by field number). This alternate way of inputting the from and to values allows the use of values containing commas, such as PATIENT NAMEs. Each nth entry in the array corresponds to, and can have the same value as, the nth comma piece in the FR variable. The only difference is that any nth entry, FR(n), can be undefined, causing the START WITH: question to be asked for the nth SORT FIELD.
For example, if you were using the unsubscripted TO and FR variables to do a sort on two fields, you might do as follows:
To set up the same sort using the subscripted forms of TO and FR, you would set them up as follows:
S FR(1)="A",FR(2)="01/01/95" S TO(1)="Zz",TO(2)="01/31/95"
NOTE: If you customize sorts using BY(0), see special note on FR in that section.
(Optional) The GO TO: values of the SORT BY fields. Its characteristics correspond to the FR variable. If undefined, the user will be asked the GO TO: questions for each SORT BY field. If TO is defined, it consists of one or more comma pieces. Each comma piece can be:
NOTE: If BY contains the name of a SORT template and if the developer answered NO to the question SHOULD TEMPLATE USER BE ASKED 'FROM'-'TO' RANGE... for a field at the time the template was defined, then the information in the FR and TO variables is ignored for that field. Instead, the from/to ranges stored in the SORT template are used.
(Optional) An alternate way to provide the GO TO: values of the SORT BY fields. If TO is defined, it will override this array. The subscript "n" corresponds to the comma piece in the BY variable. This alternate way of inputting the from and to values allows the use of values containing commas, such as PATIENT NAMEs. Each nth entry in the array corresponds to, and can have the same value as, the nth comma piece in the TO variable. The only difference is that any nth entry, TO(n), can be undefined, causing the GO TO: question to be asked for the nth SORT BY field.
If you customize sorts using BY(0), see special note on TO(n) in that section.
(Optional) The header desired for the output. DHD can be one of the following:
(Optional) If this variable is defined, the user will be prompted to enter a header. Set it equal to null (""). If this variable is undefined, the user will not have the opportunity to change the header on the print.
(Optional) If this variable is set to 1, the SORT criteria will print in the header of the first page of the report.
(Optional) Starting page number. If variable is undefined, page 1 will be assumed.
(Optional) A string of M code which will be executed for every entry after all the fields specified in FLDS have been printed.
(Optional) A string of M code which is executed after the printout has finished but before returning to the calling program.
(Optional) A string of M code which is executed before the printout starts.
(Optional) If %ZIS chooses an SDP device, and if multiple copies are desired, you can call for them by setting DCOPIES equal to the number (greater than one) of copies desired. For more information about SDP devices, see the "Kernel Systems Manual."
(Optional) EN1^DIP calls the ^%ZIS entry point to determine which device output should go to. This requires user interaction unless you preanswer the DEVICE prompt. You can do this by setting IOP equal to the name of the device (as it is stored in the DEVICE file) to which the output should be directed. You can also set IOP in any of the additional formats recognized by ^%ZIS to specify the output device (see the "Kernel Systems Manual" for more information on ^%ZIS and IOP).
If you need to call ^%ZIS beforehand to obtain the name of the device in question from the user, call it with the %ZIS N flag set so that ^%ZIS doesn't actually open the device. The name of the device is then returned in the ION output variable. EN1^DIP will open and close the device you specify in IOP on its own; don't open it yourself beforehand.
In addition to setting IOP equal to a device for printing, you can use this variable (in conjunction with the DQTIME variable described immediately below) to queue the printing of a report. This functionality is only available if Kernel is present. Also, you must set up all of the input variables for EN1^DIP so that the user is not asked any questions. For example, the BY, FR, and TO variables must be defined. To establish queuing, IOP should equal Q;output device. For example:
S IOP="Q;MY PRINTER - NLQ"
(Optional) If output is queued, this variable contains the time for printing. You can set it equal to any value that %DT recognizes. For example:
(Optional) You can screen out certain entries so that they do not appear on the output by setting the optional array DIS. The first subscript in this array can be 0 (zero). This variable (as well as all the others) contains an executable line of M code which includes an IF-statement. If the execution of the IF sets $T to 1, then the entry will print. The internal number of the entry being processed is in D0.
(Optional) You can set other elements in the DIS array: DIS(1), DIS(2), DIS(3), etc. The subscripts must be consecutive integers starting at 1. Again, they must contain M code that sets $T. If many elements are defined, then DIS(0) (if it exists) must be true and any one of the other elements in the array must be true for the entry to print.
(Optional) If this variable is set to 1 and if no records are found within the sort ranges specified for the print, the report header and the "No Records to Print" message is not printed.
(Optional) If Kernel is present, by default, prints queued through the EN1^DIP call can be stopped by the user with a TaskMan option. However, if this variable is set to 0, users will not be able to stop their queued prints.
DISTOP can also be set equal to M code that will be executed once near the start of a queued print. If the code sets $T to true, the user will be able to stop the job; if $T is false, the user will not be able to. For example:
S DISTOP="I DUZ(0)=""@"""
would mean that only those with programmer access could stop the print.
(Optional) If the user stops a queued print job by using TaskMan's option, code in this optional variable will be executed before the output device is closed. It might, for example, do clean up necessary because the job did not run to completion.
Reviewed/Updated: March 10, 2007