1 | English French Notes Complete/Exclude
|
---|
2 | of the INIT routines.
|
---|
3 | Package Name
|
---|
4 | Version
|
---|
5 | Date Distributed
|
---|
6 | Moving
|
---|
7 | Entry into Init's.
|
---|
8 | ARE YOU SURE EVERYTHING'S OK
|
---|
9 | ASK I %=1,$D(DIFQ(0)) W !,
|
---|
10 | SHALL I WRITE OVER FILE SECURITY CODES
|
---|
11 | NOTE: This package also contains
|
---|
12 | SHALL I WRITE OVER EXISTING
|
---|
13 | S OF THE SAME NAME
|
---|
14 | Answer YES to replace the current
|
---|
15 | S with the incoming ones.
|
---|
16 | HAS BEEN FILED...
|
---|
17 | ' Help Frame filed.
|
---|
18 | Shall I change the NAME of the file to
|
---|
19 | Shall I replace your file with mine
|
---|
20 | Do you want to keep the Data
|
---|
21 | Do you want to keep the Templates
|
---|
22 | ' BULLETIN FILED -- Remember to add mail groups for new bulletins.
|
---|
23 | REMOTE PROCEDURE
|
---|
24 | ' Option Filed
|
---|
25 | FORM or BLOCK
|
---|
26 | has been installed,
|
---|
27 | but associated file
|
---|
28 | is not on your system!
|
---|
29 | Compiling form:
|
---|
30 | ERROR: Form:
|
---|
31 | cannot be compiled
|
---|
32 | IXF ;;
|
---|
33 | OK, I'M DONE.
|
---|
34 | TE THAT FILE
|
---|
35 | SECURITY-CODE PROTECTION HAS BEEN MADE
|
---|
36 | (Partial Definition)
|
---|
37 | (including data)
|
---|
38 | *BUT YOU ALREADY HAVE '
|
---|
39 | ' AS FILE #
|
---|
40 | Note: You already have the '
|
---|
41 | Screen on this Data Dictionary did not pass--DD will not be installed!
|
---|
42 | Shall I write over the existing Data Definition
|
---|
43 | Want my data
|
---|
44 | merged with^to overwrite
|
---|
45 | your data with mine.
|
---|
46 | NO UPDATING HAS OCCURRED!
|
---|
47 | This version
|
---|
48 | INIT' was created on
|
---|
49 | FIRST, I'LL FRESHEN UP YOUR VA FILEMAN....
|
---|
50 | but I need version
|
---|
51 | of the VA FileMan!
|
---|
52 | GO ;
|
---|
53 | EN ; ENTER HERE TO BYPASS THE PRE-INIT PROGRAM
|
---|
54 | I AM GOING TO SET UP THE FOLLOWING FILE
|
---|
55 | I HAVE TO RUN AN ENVIRONMENT CHECK ROUTINE.
|
---|
56 | INIS HAS BEEN FILED...
|
---|
57 | ZL @X S D=0 F Y=1:1 S DNAME=$T(+Y),DD=$L(DNAME) X %X I 'DD S ^UTILITY(
|
---|
58 | ,$J,X)=D ZL DIFROM6 Q
|
---|
59 | not changed
|
---|
60 | not installed
|
---|
61 | site tracking installed
|
---|
62 | already installed
|
---|
63 | YES means that you want to bring the
|
---|
64 | S in this namespace.
|
---|
65 | NO means that you want to leave them out.
|
---|
66 | This question refers to entries in the ROUTINE documentation file.
|
---|
67 | Also, if you are building a network mail INIT, you must answer
|
---|
68 | YES if you wish to include routines other than just the INIT
|
---|
69 | routines (such as pre and post-inits) into the network mail message.
|
---|
70 | This is a unique 2 to 4 character prefix beginning with an uppercase
|
---|
71 | letter and followed only by uppercase letters or numbers.
|
---|
72 | If this is an established package, you may enter one of the prefixes
|
---|
73 | listed in the left column below.
|
---|
74 | Answer YES if you want to create a program called
|
---|
75 | even though there already is one on file. (It will be overwritten.)
|
---|
76 | Answer NO if you don't want to do this.
|
---|
77 | YES means you want to include the security protection currently
|
---|
78 | on the files in the initialization routines. A recipient of
|
---|
79 | this package will be able to decide whether or not to accept
|
---|
80 | these codes.
|
---|
81 | NO means you do not want to include security codes.
|
---|
82 | Enter the maximum number of characters each routine should
|
---|
83 | contain. This number must be between 2000 and 9999.
|
---|
84 | YES means that you are going to send this Package over
|
---|
85 | the Network as a message.
|
---|
86 | NO means that you are going to generate routines.
|
---|
87 | The scramble password is a private code, which must be
|
---|
88 | exactly correct for a reader to to see the message legibly
|
---|
89 | It may be from 3 to 20 characters long. Upper and lower
|
---|
90 | case characters are treated as the same.
|
---|
91 | A scramble hint is used to suggest to the reader what
|
---|
92 | the scramble password is. Since the password is not
|
---|
93 | recoverable after it is entered, the hint can be a
|
---|
94 | helpful reminder to the reader of the message. The
|
---|
95 | hint will be shown to the recipient just before he
|
---|
96 | is asked to enter the password.
|
---|
97 | Enter YES if you wish to transport dictionaries
|
---|
98 | or NO if you just want to Transport Options, Keys, etc.
|
---|
99 | If YES, then ALL of the templates and forms belonging to the files
|
---|
100 | selected will be included in the initialization routines.
|
---|
101 | If NO, only NAMESPACED templates and forms will be included.
|
---|
102 | If YES, this will change the existing file name
|
---|
103 | to the incoming file name.
|
---|
104 | If NO, it then will go on to the next Question.
|
---|
105 | This allows you to keep your old data if you wish.
|
---|
106 | I suggest if you get to this
|
---|
107 | question Just Default to the Question.
|
---|
108 | This will allow you to Delete or Keep the
|
---|
109 | (Sort,Print,Input) Templates if you wish.
|
---|
110 | Enter Yes if you wish to Delete your file
|
---|
111 | This will overwrite your file with my file
|
---|
112 | If you wish to save your file please say
|
---|
113 | NO. It will then Quit the INIT Process.
|
---|
114 | YES means that the information currently in the Package
|
---|
115 | File will be used to generate the package. You will not be
|
---|
116 | to alter it.
|
---|
117 | NO means that you will be able to define the package as you
|
---|
118 | proceed with the DIFROM.
|
---|
119 | YES means that the package definition will be displayed to
|
---|
120 | you on your current device.
|
---|
121 | NO means that you will continue generating the package.
|
---|
122 | YES means that the current data definitions will be overwritten
|
---|
123 | with the ones in these routines.
|
---|
124 | NO means that only new data fields will be added.
|
---|
125 | YES means that the data coming in with these inits will
|
---|
126 | replace the data on file if a match is found.
|
---|
127 | only be added if there is no data on file.
|
---|
128 | Entries will be added if they do not match exactly
|
---|
129 | on Name and Identifiers.
|
---|
130 | NO means that everything will be left as is.
|
---|
131 | Package Version No. must be entered to put onto the second
|
---|
132 | line of the INIT routines.
|
---|
133 | Format can be either the old type of version no. nnn.nn
|
---|
134 | or the new type, nnnXnn where X is either T for test phase
|
---|
135 | or V for verification phase.
|
---|
136 | Enter the Package Name to go on the second line of the INIT routines.
|
---|
137 | Enter the Distribution Date for this Package, to go on the second
|
---|
138 | line of the INIT routines. It should match the version date
|
---|
139 | on the other routines being sent with this package.
|
---|
140 | No DD Update
|
---|
141 | No Data
|
---|
142 | DDF(1),D0,
|
---|
143 | PACKAGE NAME/SOUCE ROOT
|
---|
144 | (File-top level)
|
---|
145 | DI(.84,
|
---|
146 | .4;PRINT TEMPLATE^.401;SORT TEMPLATE^.402;INPUT TEMPLATE^.403;FORM^.404;BLOCK^.5;FUNCTION^.84;DIALOG
|
---|
147 | DPSVIs
|
---|
148 | NO SUB-SUB TOTALS WERE RUN
|
---|
149 | MARGIN WIDTH OF
|
---|
150 | IS TOO SMALL FOR DISPLAY
|
---|
151 | USE WIDTH OF AT LEAST
|
---|
152 | NO SUB-COUNTS WERE RUN
|
---|
153 | VA FileMan
|
---|
154 | STANDARD CAPTIONED OUTPUT
|
---|
155 | Answer 'N' to create a formatted display as in the Print Option.
|
---|
156 | DISPLAY AUDIT TRAIL
|
---|
157 | Answer 'Y' to display the audit trail for each Entry.
|
---|
158 | OTHER OPTION^1.01
|
---|
159 | DEVICE:
|
---|
160 | Op
|
---|
161 | Oq
|
---|
162 | Or
|
---|
163 | Os
|
---|
164 | Ot
|
---|
165 | Ou
|
---|
166 | Ov
|
---|
167 | Ow
|
---|
168 | Ox
|
---|
169 | Oy
|
---|
170 | Om
|
---|
171 | Ol
|
---|
172 | On
|
---|
173 | BULLETIN MESSAGE
|
---|
174 | ' BULLETIN WILL NOT BE TRIGGERED)...
|
---|
175 | DA=$O(
|
---|
176 | DA))
|
---|
177 | DIIX)
|
---|
178 | KSsDWiRIkCTrf
|
---|
179 | Be sure to edit the routine to fill in the missing details,
|
---|
180 | and to customize the call to CREIXN^DDMOD.
|
---|
181 | -CREATE NEW-STYLE XREF ;
|
---|
182 | XR,
|
---|
183 | RES,
|
---|
184 | ROOT FILE
|
---|
185 | SHORT DESCR
|
---|
186 | WHOLE KILL
|
---|
187 | SET CONDITION
|
---|
188 | KILL CONDITION
|
---|
189 | XR(
|
---|
190 | LOOKUP PROMPT
|
---|
191 | XFORM FOR STORAGE
|
---|
192 | XFORM FOR LOOKUP
|
---|
193 | XFORM FOR DISPLAY
|
---|
194 | Routine name
|
---|
195 | Enter the name of the routine, without the leading up-arrow, that
|
---|
196 | should be built.
|
---|
197 | Answer must be 1-8 characters in length. It must begin with % or a
|
---|
198 | letter, followed by a combination of letters and numbers.
|
---|
199 | Do you wish to replace routine
|
---|
200 | Answer yes if you wish to replace routine
|
---|
201 | with a new version.
|
---|
202 | Programmer initials
|
---|
203 | Enter your initials, which will appear on the first line of the
|
---|
204 | Namespace to use for local variables
|
---|
205 | All variables used in the generated routine will start with the namespace
|
---|
206 | you choose.
|
---|
207 | Answer must be 1-4 characters in length. It must begin with % or a
|
---|
208 | CROSS-REFERENCE FROM
|
---|
209 | to build a routine for
|
---|
210 | Jan^Feb^Mar^Apr^May^Jun^Jul^Aug^Sep^Oct^Nov^Dec
|
---|
211 | You can only change the Type of cross reference to MUMPS, and only if you're a programmer.
|
---|
212 | Cannot create MUMPS cross references on archived files.
|
---|
213 | Index Name is a required field.
|
---|
214 | AEIOUaeiou
|
---|
215 | ' Index already exists.
|
---|
216 | ' cross-reference already exists.
|
---|
217 | Uniqueness Index Name cannot start with 'A'.
|
---|
218 | Please enter a NAME and TYPE for this Index.
|
---|
219 | Indexes used for Sorting Only must start with 'A'.
|
---|
220 | Indexes used for Lookup & Sorting cannot start with 'A'.
|
---|
221 | Only MUMPS Indexes can be Action-type Indexes.
|
---|
222 | Action-type Indexes must start with 'A'.
|
---|
223 | Only programmers are allowed to edit index logic.
|
---|
224 | You can modify the logic of only 'MUMPS' indexes.
|
---|
225 | COMPUTED CODE
|
---|
226 | TRANSFORM FOR DISPLAY
|
---|
227 | File must be a parent (ancestor) of Root File.
|
---|
228 | UNABLE TO SAVE CHANGES
|
---|
229 | FILE for Order #
|
---|
230 | To correct the problem, press <RET> at the Order # on Page 2.
|
---|
231 | In the resulting pop-up page, FILE will be filled in automatically.
|
---|
232 | Try saving again.
|
---|
233 | is not equal to the Root File:
|
---|
234 | The subscript number
|
---|
235 | is used more than once.
|
---|
236 | Subscript numbers must be consecutive numbers starting with 1.
|
---|
237 | <no name
|
---|
238 | New-Style
|
---|
239 | Field
|
---|
240 | INDEXES:
|
---|
241 | RECORD INDEXES:
|
---|
242 | FIELD INDEXES:
|
---|
243 | INDEXED BY:
|
---|
244 | keep with next
|
---|
245 | Short Descr:
|
---|
246 | Description:
|
---|
247 | Key
|
---|
248 | Unique for:
|
---|
249 | Set Logic:
|
---|
250 | Set Cond:
|
---|
251 | Kill Logic:
|
---|
252 | Kill Cond:
|
---|
253 | Whole Kill:
|
---|
254 | <undefined file/field>
|
---|
255 | Computed Code:
|
---|
256 | <undefined computed code>
|
---|
257 | Lookup Prompt:
|
---|
258 | Transform (Storage):
|
---|
259 | Transform (Display):
|
---|
260 | Field:
|
---|
261 | Triggered Field:
|
---|
262 | Traditional Cross-References:
|
---|
263 | Creating index definition ...
|
---|
264 | ROOT TYPE
|
---|
265 | NAME/USE
|
---|
266 | TYPE/USE
|
---|
267 | Building index ...
|
---|
268 | Executing set logic ...
|
---|
269 | Select Subfile:
|
---|
270 | Are you sure you want to delete the index definition
|
---|
271 | Want to create a new index for this file
|
---|
272 | Index definition deleted.
|
---|
273 | Type of index
|
---|
274 | Only programmers can create MUMPS cross references.
|
---|
275 | Enter 'Yes' if you want the index to reside at this level.
|
---|
276 | Want to index whole
|
---|
277 | How is this MUMPS cross reference to be used
|
---|
278 | Want index to be used for Lookup & Sorting
|
---|
279 | or Sorting Only
|
---|
280 | LOOKUP & SORTING
|
---|
281 | ** Only MUMPS cross references can be ACTION-type cross references. **
|
---|
282 | Index Name
|
---|
283 | Action-type indexes must start with 'A'
|
---|
284 | There is already an index defined with this name.
|
---|
285 | There is already a cross-reference defined with this name.
|
---|
286 | Traditional
|
---|
287 | Enter 'T' to select a Traditional cross-reference.
|
---|
288 | Enter 'N' to select a New-Style cross-reference.
|
---|
289 | Compound indexes (indexes based on more than one field)
|
---|
290 | are examples of New-Style cross-references.
|
---|
291 | There are no INDEX file cross-references defined on
|
---|
292 | Current Indexes
|
---|
293 | whole file index
|
---|
294 | (resides on
|
---|
295 | Which Index do you wish to
|
---|
296 | ' on File #
|
---|
297 | Index '
|
---|
298 | cannot be deleted. It is the uniqueness index for
|
---|
299 | Removing old index ...
|
---|
300 | Do you want to delete the data in the old index now
|
---|
301 | Enter 'YES' to delete the data in the old index now.
|
---|
302 | You might answer 'NO' if you know that there is no data in the index, or
|
---|
303 | #################### #################### ####################
|
---|
304 | #################### #################### ####################
|
---|
305 | #################### #################### ####################
|
---|
306 | #################### #################### ####################
|
---|
307 | #################### #################### ####################
|
---|