source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0129.txt@ 784

Last change on this file since 784 was 604, checked in by George Lilly, 15 years ago

Internationalization

File size: 8.7 KB
Line 
1English French Notes Complete/Exclude
2Enter END DATE/TIME
3You cannot enter the same values for the beginning and ending times!
4Enter the maximum number errors to report for every error status.
5Enter maximum number errors/status
6If you enter '1000' for the maximum number errors/status...
7... The most recent 1000 errors for every error type will be included in the
8... report. If two different error types exist, and each error type has
9... more than 1000 entries, then 2000 errors will be reported.
10... (I.e., 1000 errors per error type.)
11... The most recent 1000 errors for the error type you just selected
12... will be included in the report.
13Enter a date/time after
14Select the report view now. There are two report views. Both list the
15internal entry number from the HL7 Message Administration file (#773) entry,
16message ID, processing date or time, and logical link. The two report views
17differ in the remainder of the information displayed on the report.
18Select data to display
19Select the data to be displayed in the last few columns of the report after
20the IEN, message ID, processing date or time, and logical link.
21Duplicate Message
22Duplicate with ien
23Duplicate with ien
24Duplicate w/#
25Incorrect Message Received
26Incorrect msg. Id
27Incorrect message ID
28HL MESSAGE REQUEUER - 3
29Selected Message from Logical Link
30Init Error
31HLClnt:
32HLSrv:
33Listen
34Openfail
35Init error
36Idle
37SYS$NET
38Init
39IN State:
40Wr-err
41Retention
42Check out
43 exceeded retries. LL will
44keep trying.
45LLP Exceeded Retry Param
46Send
47BHS,FHS
48 Logical Link
49 exceeded Open Retries.
50HL7.yourdomain.com
51DNS Lkup
52VA.GOV
53HL7.
54MPI.
55Op-err
56Rd-err
57SYSTEM LINK MONITOR for
58TO SEND
59SENT
60TYPE
61IOELALL;IOELEOL;IORESET;IORVON;IORVOFF;IOIL;IOSTBM;IOSC;IORC;IOEDEOP;IOINHI;IOINORM;IOUON;IOUOFF;IOBOFF;IOBON
62-1^Did not pass task number of filer
63-1^Entry in file #869.3 does not exist
64-1^Unable to create entry in filer multiple
65No set logic for file #
66 does not contain a field
67HLDIE-DEBUG
68Debug Data Display by FILE,IEN
69HLDIE-DEBUGX
70No debug data exists...
71Enter FILE#:
72Enter IEN:
73File & IEN
74Job#
75Rtn
76Debug#
77Enter #:
78 Files w/Debug Data
79 IENs w/Debug Data for File#
80Some IENs not displayed (because there were too many)...
81(The LAST IEN is
82Debug Data Display by Global Search
83Search string:
84Searching...
85HLDIE-DEBUF
86Debug Data Display by API Call
87 no data...
88Rtn:
89Subrtn:
90Max#: 20//
91Enter Date/time (FM):
92 invalid format...
93Enter # to display:
94 entry not found...
95HLDIE-DEBUG-
96Call#
97Press RETURN to continue, or '^' to exit...
98HLDIE Debug Utility
99IOINORM;IOINHI
100Pre-call:
101ON[
102Select option
103HLDIE-DEBUGN
104File [#IEN]
105DataTM
106Edtor
107Collecting data...
108[No change]
109debug string.
110debug string
111HLDIE-
112FILE-HLDIE
113HLDIE $$STORESCR Error
114An error occurred in $$STORESCR^HLDIEDB2 that must be checked. The
115variables that existed at the time of the error are listed below.
116The error was '
117IMPORTANT!! All debugging was turned off. Please review the problem,
118 then turn debugging back on.
119Local Variable List
120error notification email message.
121Enter job#:
122 invalid job#...
123Job
124Calls
125HLDIE Debug String Set/Unset Utility
126When asked for a new debug string, you may take one of the following actions:
127 * Enter RETURN or '^' to exit.
128 * Enter a debug string. (E.g., '1' or '1^2' or '1^1^1'.)
129 * Enter '@' to delete the debug string, (If a debug string exists).
130Current DEBUG string =
131Enter DEBUG string,
132or RETURN to exit:
133 no changes made. Exiting...
134No changes made. (If you want to stop debugging, enter '
135 no changes made...
136 stopped all debugging!
137Control string for HLDIE debugging
138 debugging set...
139Debug data created by HLDIEDBG routine
140Kill **ALL** debug data
141 no data will be killed...
142KILLing all debug data...
143HLDIE
144Data logged by LOG~HLDIE
145AH KILL
146ACTION STATUS
147DT/TM
148DT/TM ACTION
149DT/TM CREATED
150DT/TM REVIEWED
151MSGID ID
152MSG TYPE
153MSG EVENT
154MSG LINK
155REVIEW STATUS
156MSG ID
157UNKNOWN EVENT TYPE
158UNKNOWN SITE
159INACTIVE EVENT TYPE
160ALL APPS
161ALL STATUSES
162ALL TYPES
163Please select the profile you wish to use
164No profile selected! Try again
165 or hit RETURN to see more
166You can choose a profile by the number or by it's name.
167You must enter the number or name of the profile!
168HL7 EVENT LOG AT SAN FRANCISCO
169**APPLICATION DATA**
170S.HLEM EVENT LOG SERVER
171UNKNOWN EVENT TYPE AT REMOTE SITE:
172REMOTE EVENT ADDED BY SERVER AT
173, MAILMAN MESSAGE IEN:
174Fileman Failed to store remote event:
175SRVR ERROR
176HEALTH LEVEL SEVEN
177MAIL IEN
178HLEM APP DATA
179HLEM DISPLAY APPLICATION DATA
180# EVENT DT/TM APPLICATION MSG REVIEW CNT
181HLEM DISPLAY ONE EVENT
182Event ID:
183Event Type:
184Count:
185Descr:
186Site of Event:
187DT/TM of Event:
188DT/TM Reported:
189Status Information:
190Urgent:
191Automated Action:
192DT/TM:
193Review Status:
194Reviewer:
195Date:
196HL7 Message Information:
197Mssg ID:
198Sending App:
199Logical Link:
200Notes:
201HLEM EVENT HELP
202NO HELP AVAILABLE!
203HLEM DISPLAY EVENTS
204** Your DUZ is not defined, please report this to your IRM!
205You need a profile before viewing the HL7 Monitor Event Log,would you like to create a new profile now
206NEW PROFILE
207Incomplete profile couln't be deleted!
208# TYPE DT/TM APP MSG REVIEW CNT
209USER PROFILE:
210Enter the number of the event to display
211HL7 MONITOR EVENT
212FAILED TO ADD THE MAILMAN MESSAGE NUMBER TO THE EVENT
213MAILMAN FAILED TO SEND HL7 LOG EVENT TO REMOTE SERVER
214HL7 EVENT LOG at
215MOORE,JIM
216HL7 EVENT LOG
217HLEM DISPLAY STATISTICS
218Year Month Day Hour Event Count
219There are no statistics for this profile and date range!
220Enter the begining date
221Please enter the earliest date for which you would like to see Event Logging Statistics.
222January
223February
224March
225April
226June
227July
228August
229September
230October
231November
232December
233This routine searches for HL7 protocols with possible errors.
234Select an EVENT DRIVER Protocol:
235HL7 Interface Debugger
236Queued to task number:
237 ** HL7 INTERFACE DEBUGGER **
238ACK,ADR,ARD,EDR,ERP,MCF,MFK,MFR,ORF,ORG,ORR,OSR,RAR,RCI,RCL,
239RDR,RDY,RER,RGR,ROR,RRA,RRD,RRE,RRG,RRI,RSP,RTB,SQR,
240TBR,VXR,VXX
241Protocol is UNDEFINED.
242**PROTOCOL DISABLED**
243Missing data for all key fields.
244Version ID is required.
245Missing Required Sending Application.
246Broken pointer to App Param (file 771).
247Missing required Message Type.
248Broken pointer to Msg Type (file 771.2).
249For Event Driver-Message Type cannot be an acknowledgement.
250Broken pointer to Event Type (file 779.001).
251Event type is required for versions greater than 2.1.
252Event Driver:
253Sending Application:
254Version:
255Message Type(770.3):
256Event Driver Error Summary:
257No Event Driver Errors Found.
258No Subscribers Found.
259Subscriber Protocol is UNDEFINED.
260**SUBSCRIBER PROTOCOL DISABLED**
261Missing Required Receiving Application.
262Message Type must be an appropriate response/acknowledgement.
263Missing Processing Routine and Routing Logic.
264WARNING-Missing both Logical Link and Routing Logic. Will be local only.
265For Subscriber:
266Receiving Application:
267Message Type (770.11):
268No Subscriber Errors Found.
269Application is INACTIVE.
270REPORT-VARNAME
271MONITOR-NAME
272DECLARE called -
273message is completed
274HL7 Monitor -
275Mail message #
276Turn on/off Event Monitors
277Recent Checks of the Monitor by Master Job
278Check-time
279Event monitor status
280Press RETURN to continue...
281Requeue minutes
2820 [Immediate Run]
283Notification mail group
284Parameter -
285STATUS-MASTER JOB
286STATUS-EVENT MONITORING
287Change '
288 ... nothing changed ...
289HL Event Monitor - #
290-------- Master job status is
291NOT SET YET
292-------- Event monitoring status is
293Unknown last master job run time...
294Unknown next master job run time...
295Unknown last master job run...
296Last master job run was
297Unknown next master job run...
298Next run
299 in the future...
300Monitor description:
301' event monitor has completed.
302Variable List
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.