308 lines
11 KiB
Plaintext
308 lines
11 KiB
Plaintext
|
English French Notes Complete/Exclude
|
||
|
|
of the INIT routines.
|
||
|
|
Package Name
|
||
|
|
Version
|
||
|
|
Date Distributed
|
||
|
|
Moving
|
||
|
|
Entry into Init's.
|
||
|
|
ARE YOU SURE EVERYTHING'S OK
|
||
|
|
ASK I %=1,$D(DIFQ(0)) W !,
|
||
|
|
SHALL I WRITE OVER FILE SECURITY CODES
|
||
|
|
NOTE: This package also contains
|
||
|
|
SHALL I WRITE OVER EXISTING
|
||
|
|
S OF THE SAME NAME
|
||
|
|
Answer YES to replace the current
|
||
|
|
S with the incoming ones.
|
||
|
|
HAS BEEN FILED...
|
||
|
|
' Help Frame filed.
|
||
|
|
Shall I change the NAME of the file to
|
||
|
|
Shall I replace your file with mine
|
||
|
|
Do you want to keep the Data
|
||
|
|
Do you want to keep the Templates
|
||
|
|
' BULLETIN FILED -- Remember to add mail groups for new bulletins.
|
||
|
|
REMOTE PROCEDURE
|
||
|
|
' Option Filed
|
||
|
|
FORM or BLOCK
|
||
|
|
has been installed,
|
||
|
|
but associated file
|
||
|
|
is not on your system!
|
||
|
|
Compiling form:
|
||
|
|
ERROR: Form:
|
||
|
|
cannot be compiled
|
||
|
|
IXF ;;
|
||
|
|
OK, I'M DONE.
|
||
|
|
TE THAT FILE
|
||
|
|
SECURITY-CODE PROTECTION HAS BEEN MADE
|
||
|
|
(Partial Definition)
|
||
|
|
(including data)
|
||
|
|
*BUT YOU ALREADY HAVE '
|
||
|
|
' AS FILE #
|
||
|
|
Note: You already have the '
|
||
|
|
Screen on this Data Dictionary did not pass--DD will not be installed!
|
||
|
|
Shall I write over the existing Data Definition
|
||
|
|
Want my data
|
||
|
|
merged with^to overwrite
|
||
|
|
your data with mine.
|
||
|
|
NO UPDATING HAS OCCURRED!
|
||
|
|
This version
|
||
|
|
INIT' was created on
|
||
|
|
FIRST, I'LL FRESHEN UP YOUR VA FILEMAN....
|
||
|
|
but I need version
|
||
|
|
of the VA FileMan!
|
||
|
|
GO ;
|
||
|
|
EN ; ENTER HERE TO BYPASS THE PRE-INIT PROGRAM
|
||
|
|
I AM GOING TO SET UP THE FOLLOWING FILE
|
||
|
|
I HAVE TO RUN AN ENVIRONMENT CHECK ROUTINE.
|
||
|
|
INIS HAS BEEN FILED...
|
||
|
|
ZL @X S D=0 F Y=1:1 S DNAME=$T(+Y),DD=$L(DNAME) X %X I 'DD S ^UTILITY(
|
||
|
|
,$J,X)=D ZL DIFROM6 Q
|
||
|
|
not changed
|
||
|
|
not installed
|
||
|
|
site tracking installed
|
||
|
|
already installed
|
||
|
|
YES means that you want to bring the
|
||
|
|
S in this namespace.
|
||
|
|
NO means that you want to leave them out.
|
||
|
|
This question refers to entries in the ROUTINE documentation file.
|
||
|
|
Also, if you are building a network mail INIT, you must answer
|
||
|
|
YES if you wish to include routines other than just the INIT
|
||
|
|
routines (such as pre and post-inits) into the network mail message.
|
||
|
|
This is a unique 2 to 4 character prefix beginning with an uppercase
|
||
|
|
letter and followed only by uppercase letters or numbers.
|
||
|
|
If this is an established package, you may enter one of the prefixes
|
||
|
|
listed in the left column below.
|
||
|
|
Answer YES if you want to create a program called
|
||
|
|
even though there already is one on file. (It will be overwritten.)
|
||
|
|
Answer NO if you don't want to do this.
|
||
|
|
YES means you want to include the security protection currently
|
||
|
|
on the files in the initialization routines. A recipient of
|
||
|
|
this package will be able to decide whether or not to accept
|
||
|
|
these codes.
|
||
|
|
NO means you do not want to include security codes.
|
||
|
|
Enter the maximum number of characters each routine should
|
||
|
|
contain. This number must be between 2000 and 9999.
|
||
|
|
YES means that you are going to send this Package over
|
||
|
|
the Network as a message.
|
||
|
|
NO means that you are going to generate routines.
|
||
|
|
The scramble password is a private code, which must be
|
||
|
|
exactly correct for a reader to to see the message legibly
|
||
|
|
It may be from 3 to 20 characters long. Upper and lower
|
||
|
|
case characters are treated as the same.
|
||
|
|
A scramble hint is used to suggest to the reader what
|
||
|
|
the scramble password is. Since the password is not
|
||
|
|
recoverable after it is entered, the hint can be a
|
||
|
|
helpful reminder to the reader of the message. The
|
||
|
|
hint will be shown to the recipient just before he
|
||
|
|
is asked to enter the password.
|
||
|
|
Enter YES if you wish to transport dictionaries
|
||
|
|
or NO if you just want to Transport Options, Keys, etc.
|
||
|
|
If YES, then ALL of the templates and forms belonging to the files
|
||
|
|
selected will be included in the initialization routines.
|
||
|
|
If NO, only NAMESPACED templates and forms will be included.
|
||
|
|
If YES, this will change the existing file name
|
||
|
|
to the incoming file name.
|
||
|
|
If NO, it then will go on to the next Question.
|
||
|
|
This allows you to keep your old data if you wish.
|
||
|
|
I suggest if you get to this
|
||
|
|
question Just Default to the Question.
|
||
|
|
This will allow you to Delete or Keep the
|
||
|
|
(Sort,Print,Input) Templates if you wish.
|
||
|
|
Enter Yes if you wish to Delete your file
|
||
|
|
This will overwrite your file with my file
|
||
|
|
If you wish to save your file please say
|
||
|
|
NO. It will then Quit the INIT Process.
|
||
|
|
YES means that the information currently in the Package
|
||
|
|
File will be used to generate the package. You will not be
|
||
|
|
to alter it.
|
||
|
|
NO means that you will be able to define the package as you
|
||
|
|
proceed with the DIFROM.
|
||
|
|
YES means that the package definition will be displayed to
|
||
|
|
you on your current device.
|
||
|
|
NO means that you will continue generating the package.
|
||
|
|
YES means that the current data definitions will be overwritten
|
||
|
|
with the ones in these routines.
|
||
|
|
NO means that only new data fields will be added.
|
||
|
|
YES means that the data coming in with these inits will
|
||
|
|
replace the data on file if a match is found.
|
||
|
|
only be added if there is no data on file.
|
||
|
|
Entries will be added if they do not match exactly
|
||
|
|
on Name and Identifiers.
|
||
|
|
NO means that everything will be left as is.
|
||
|
|
Package Version No. must be entered to put onto the second
|
||
|
|
line of the INIT routines.
|
||
|
|
Format can be either the old type of version no. nnn.nn
|
||
|
|
or the new type, nnnXnn where X is either T for test phase
|
||
|
|
or V for verification phase.
|
||
|
|
Enter the Package Name to go on the second line of the INIT routines.
|
||
|
|
Enter the Distribution Date for this Package, to go on the second
|
||
|
|
line of the INIT routines. It should match the version date
|
||
|
|
on the other routines being sent with this package.
|
||
|
|
No DD Update
|
||
|
|
No Data
|
||
|
|
DDF(1),D0,
|
||
|
|
PACKAGE NAME/SOUCE ROOT
|
||
|
|
(File-top level)
|
||
|
|
DI(.84,
|
||
|
|
.4;PRINT TEMPLATE^.401;SORT TEMPLATE^.402;INPUT TEMPLATE^.403;FORM^.404;BLOCK^.5;FUNCTION^.84;DIALOG
|
||
|
|
DPSVIs
|
||
|
|
NO SUB-SUB TOTALS WERE RUN
|
||
|
|
MARGIN WIDTH OF
|
||
|
|
IS TOO SMALL FOR DISPLAY
|
||
|
|
USE WIDTH OF AT LEAST
|
||
|
|
NO SUB-COUNTS WERE RUN
|
||
|
|
VA FileMan
|
||
|
|
STANDARD CAPTIONED OUTPUT
|
||
|
|
Answer 'N' to create a formatted display as in the Print Option.
|
||
|
|
DISPLAY AUDIT TRAIL
|
||
|
|
Answer 'Y' to display the audit trail for each Entry.
|
||
|
|
OTHER OPTION^1.01
|
||
|
|
DEVICE:
|
||
|
|
Op
|
||
|
|
Oq
|
||
|
|
Or
|
||
|
|
Os
|
||
|
|
Ot
|
||
|
|
Ou
|
||
|
|
Ov
|
||
|
|
Ow
|
||
|
|
Ox
|
||
|
|
Oy
|
||
|
|
Om
|
||
|
|
Ol
|
||
|
|
On
|
||
|
|
BULLETIN MESSAGE
|
||
|
|
' BULLETIN WILL NOT BE TRIGGERED)...
|
||
|
|
DA=$O(
|
||
|
|
DA))
|
||
|
|
DIIX)
|
||
|
|
KSsDWiRIkCTrf
|
||
|
|
Be sure to edit the routine to fill in the missing details,
|
||
|
|
and to customize the call to CREIXN^DDMOD.
|
||
|
|
-CREATE NEW-STYLE XREF ;
|
||
|
|
XR,
|
||
|
|
RES,
|
||
|
|
ROOT FILE
|
||
|
|
SHORT DESCR
|
||
|
|
WHOLE KILL
|
||
|
|
SET CONDITION
|
||
|
|
KILL CONDITION
|
||
|
|
XR(
|
||
|
|
LOOKUP PROMPT
|
||
|
|
XFORM FOR STORAGE
|
||
|
|
XFORM FOR LOOKUP
|
||
|
|
XFORM FOR DISPLAY
|
||
|
|
Routine name
|
||
|
|
Enter the name of the routine, without the leading up-arrow, that
|
||
|
|
should be built.
|
||
|
|
Answer must be 1-8 characters in length. It must begin with % or a
|
||
|
|
letter, followed by a combination of letters and numbers.
|
||
|
|
Do you wish to replace routine
|
||
|
|
Answer yes if you wish to replace routine
|
||
|
|
with a new version.
|
||
|
|
Programmer initials
|
||
|
|
Enter your initials, which will appear on the first line of the
|
||
|
|
Namespace to use for local variables
|
||
|
|
All variables used in the generated routine will start with the namespace
|
||
|
|
you choose.
|
||
|
|
Answer must be 1-4 characters in length. It must begin with % or a
|
||
|
|
CROSS-REFERENCE FROM
|
||
|
|
to build a routine for
|
||
|
|
Jan^Feb^Mar^Apr^May^Jun^Jul^Aug^Sep^Oct^Nov^Dec
|
||
|
|
You can only change the Type of cross reference to MUMPS, and only if you're a programmer.
|
||
|
|
Cannot create MUMPS cross references on archived files.
|
||
|
|
Index Name is a required field.
|
||
|
|
AEIOUaeiou
|
||
|
|
' Index already exists.
|
||
|
|
' cross-reference already exists.
|
||
|
|
Uniqueness Index Name cannot start with 'A'.
|
||
|
|
Please enter a NAME and TYPE for this Index.
|
||
|
|
Indexes used for Sorting Only must start with 'A'.
|
||
|
|
Indexes used for Lookup & Sorting cannot start with 'A'.
|
||
|
|
Only MUMPS Indexes can be Action-type Indexes.
|
||
|
|
Action-type Indexes must start with 'A'.
|
||
|
|
Only programmers are allowed to edit index logic.
|
||
|
|
You can modify the logic of only 'MUMPS' indexes.
|
||
|
|
COMPUTED CODE
|
||
|
|
TRANSFORM FOR DISPLAY
|
||
|
|
File must be a parent (ancestor) of Root File.
|
||
|
|
UNABLE TO SAVE CHANGES
|
||
|
|
FILE for Order #
|
||
|
|
To correct the problem, press <RET> at the Order # on Page 2.
|
||
|
|
In the resulting pop-up page, FILE will be filled in automatically.
|
||
|
|
Try saving again.
|
||
|
|
is not equal to the Root File:
|
||
|
|
The subscript number
|
||
|
|
is used more than once.
|
||
|
|
Subscript numbers must be consecutive numbers starting with 1.
|
||
|
|
<no name
|
||
|
|
New-Style
|
||
|
|
Field
|
||
|
|
INDEXES:
|
||
|
|
RECORD INDEXES:
|
||
|
|
FIELD INDEXES:
|
||
|
|
INDEXED BY:
|
||
|
|
keep with next
|
||
|
|
Short Descr:
|
||
|
|
Description:
|
||
|
|
Key
|
||
|
|
Unique for:
|
||
|
|
Set Logic:
|
||
|
|
Set Cond:
|
||
|
|
Kill Logic:
|
||
|
|
Kill Cond:
|
||
|
|
Whole Kill:
|
||
|
|
<undefined file/field>
|
||
|
|
Computed Code:
|
||
|
|
<undefined computed code>
|
||
|
|
Lookup Prompt:
|
||
|
|
Transform (Storage):
|
||
|
|
Transform (Display):
|
||
|
|
Field:
|
||
|
|
Triggered Field:
|
||
|
|
Traditional Cross-References:
|
||
|
|
Creating index definition ...
|
||
|
|
ROOT TYPE
|
||
|
|
NAME/USE
|
||
|
|
TYPE/USE
|
||
|
|
Building index ...
|
||
|
|
Executing set logic ...
|
||
|
|
Select Subfile:
|
||
|
|
Are you sure you want to delete the index definition
|
||
|
|
Want to create a new index for this file
|
||
|
|
Index definition deleted.
|
||
|
|
Type of index
|
||
|
|
Only programmers can create MUMPS cross references.
|
||
|
|
Enter 'Yes' if you want the index to reside at this level.
|
||
|
|
Want to index whole
|
||
|
|
How is this MUMPS cross reference to be used
|
||
|
|
Want index to be used for Lookup & Sorting
|
||
|
|
or Sorting Only
|
||
|
|
LOOKUP & SORTING
|
||
|
|
** Only MUMPS cross references can be ACTION-type cross references. **
|
||
|
|
Index Name
|
||
|
|
Action-type indexes must start with 'A'
|
||
|
|
There is already an index defined with this name.
|
||
|
|
There is already a cross-reference defined with this name.
|
||
|
|
Traditional
|
||
|
|
Enter 'T' to select a Traditional cross-reference.
|
||
|
|
Enter 'N' to select a New-Style cross-reference.
|
||
|
|
Compound indexes (indexes based on more than one field)
|
||
|
|
are examples of New-Style cross-references.
|
||
|
|
There are no INDEX file cross-references defined on
|
||
|
|
Current Indexes
|
||
|
|
whole file index
|
||
|
|
(resides on
|
||
|
|
Which Index do you wish to
|
||
|
|
' on File #
|
||
|
|
Index '
|
||
|
|
cannot be deleted. It is the uniqueness index for
|
||
|
|
Removing old index ...
|
||
|
|
Do you want to delete the data in the old index now
|
||
|
|
Enter 'YES' to delete the data in the old index now.
|
||
|
|
You might answer 'NO' if you know that there is no data in the index, or
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|
||
|
|
#################### #################### ####################
|