VistA-internationalization/TranslationSpreadsheets/WV-DIALOG-0129.txt

308 lines
8.7 KiB
Plaintext

English French Notes Complete/Exclude
Enter END DATE/TIME
You cannot enter the same values for the beginning and ending times!
Enter the maximum number errors to report for every error status.
Enter maximum number errors/status
If you enter '1000' for the maximum number errors/status...
... The most recent 1000 errors for every error type will be included in the
... report. If two different error types exist, and each error type has
... more than 1000 entries, then 2000 errors will be reported.
... (I.e., 1000 errors per error type.)
... The most recent 1000 errors for the error type you just selected
... will be included in the report.
Enter a date/time after
Select the report view now. There are two report views. Both list the
internal entry number from the HL7 Message Administration file (#773) entry,
message ID, processing date or time, and logical link. The two report views
differ in the remainder of the information displayed on the report.
Select data to display
Select the data to be displayed in the last few columns of the report after
the IEN, message ID, processing date or time, and logical link.
Duplicate Message
Duplicate with ien
Duplicate with ien
Duplicate w/#
Incorrect Message Received
Incorrect msg. Id
Incorrect message ID
HL MESSAGE REQUEUER - 3
Selected Message from Logical Link
Init Error
HLClnt:
HLSrv:
Listen
Openfail
Init error
Idle
SYS$NET
Init
IN State:
Wr-err
Retention
Check out
exceeded retries. LL will
keep trying.
LLP Exceeded Retry Param
Send
BHS,FHS
Logical Link
exceeded Open Retries.
HL7.yourdomain.com
DNS Lkup
VA.GOV
HL7.
MPI.
Op-err
Rd-err
SYSTEM LINK MONITOR for
TO SEND
SENT
TYPE
IOELALL;IOELEOL;IORESET;IORVON;IORVOFF;IOIL;IOSTBM;IOSC;IORC;IOEDEOP;IOINHI;IOINORM;IOUON;IOUOFF;IOBOFF;IOBON
-1^Did not pass task number of filer
-1^Entry in file #869.3 does not exist
-1^Unable to create entry in filer multiple
No set logic for file #
does not contain a field
HLDIE-DEBUG
Debug Data Display by FILE,IEN
HLDIE-DEBUGX
No debug data exists...
Enter FILE#:
Enter IEN:
File & IEN
Job#
Rtn
Debug#
Enter #:
Files w/Debug Data
IENs w/Debug Data for File#
Some IENs not displayed (because there were too many)...
(The LAST IEN is
Debug Data Display by Global Search
Search string:
Searching...
HLDIE-DEBUF
Debug Data Display by API Call
no data...
Rtn:
Subrtn:
Max#: 20//
Enter Date/time (FM):
invalid format...
Enter # to display:
entry not found...
HLDIE-DEBUG-
Call#
Press RETURN to continue, or '^' to exit...
HLDIE Debug Utility
IOINORM;IOINHI
Pre-call:
ON[
Select option
HLDIE-DEBUGN
File [#IEN]
DataTM
Edtor
Collecting data...
[No change]
debug string.
debug string
HLDIE-
FILE-HLDIE
HLDIE $$STORESCR Error
An error occurred in $$STORESCR^HLDIEDB2 that must be checked. The
variables that existed at the time of the error are listed below.
The error was '
IMPORTANT!! All debugging was turned off. Please review the problem,
then turn debugging back on.
Local Variable List
error notification email message.
Enter job#:
invalid job#...
Job
Calls
HLDIE Debug String Set/Unset Utility
When asked for a new debug string, you may take one of the following actions:
* Enter RETURN or '^' to exit.
* Enter a debug string. (E.g., '1' or '1^2' or '1^1^1'.)
* Enter '@' to delete the debug string, (If a debug string exists).
Current DEBUG string =
Enter DEBUG string,
or RETURN to exit:
no changes made. Exiting...
No changes made. (If you want to stop debugging, enter '
no changes made...
stopped all debugging!
Control string for HLDIE debugging
debugging set...
Debug data created by HLDIEDBG routine
Kill **ALL** debug data
no data will be killed...
KILLing all debug data...
HLDIE
Data logged by LOG~HLDIE
AH KILL
ACTION STATUS
DT/TM
DT/TM ACTION
DT/TM CREATED
DT/TM REVIEWED
MSGID ID
MSG TYPE
MSG EVENT
MSG LINK
REVIEW STATUS
MSG ID
UNKNOWN EVENT TYPE
UNKNOWN SITE
INACTIVE EVENT TYPE
ALL APPS
ALL STATUSES
ALL TYPES
Please select the profile you wish to use
No profile selected! Try again
or hit RETURN to see more
You can choose a profile by the number or by it's name.
You must enter the number or name of the profile!
HL7 EVENT LOG AT SAN FRANCISCO
**APPLICATION DATA**
S.HLEM EVENT LOG SERVER
UNKNOWN EVENT TYPE AT REMOTE SITE:
REMOTE EVENT ADDED BY SERVER AT
, MAILMAN MESSAGE IEN:
Fileman Failed to store remote event:
SRVR ERROR
HEALTH LEVEL SEVEN
MAIL IEN
HLEM APP DATA
HLEM DISPLAY APPLICATION DATA
# EVENT DT/TM APPLICATION MSG REVIEW CNT
HLEM DISPLAY ONE EVENT
Event ID:
Event Type:
Count:
Descr:
Site of Event:
DT/TM of Event:
DT/TM Reported:
Status Information:
Urgent:
Automated Action:
DT/TM:
Review Status:
Reviewer:
Date:
HL7 Message Information:
Mssg ID:
Sending App:
Logical Link:
Notes:
HLEM EVENT HELP
NO HELP AVAILABLE!
HLEM DISPLAY EVENTS
** Your DUZ is not defined, please report this to your IRM!
You need a profile before viewing the HL7 Monitor Event Log,would you like to create a new profile now
NEW PROFILE
Incomplete profile couln't be deleted!
# TYPE DT/TM APP MSG REVIEW CNT
USER PROFILE:
Enter the number of the event to display
HL7 MONITOR EVENT
FAILED TO ADD THE MAILMAN MESSAGE NUMBER TO THE EVENT
MAILMAN FAILED TO SEND HL7 LOG EVENT TO REMOTE SERVER
HL7 EVENT LOG at
MOORE,JIM
HL7 EVENT LOG
HLEM DISPLAY STATISTICS
Year Month Day Hour Event Count
There are no statistics for this profile and date range!
Enter the begining date
Please enter the earliest date for which you would like to see Event Logging Statistics.
January
February
March
April
June
July
August
September
October
November
December
This routine searches for HL7 protocols with possible errors.
Select an EVENT DRIVER Protocol:
HL7 Interface Debugger
Queued to task number:
** HL7 INTERFACE DEBUGGER **
ACK,ADR,ARD,EDR,ERP,MCF,MFK,MFR,ORF,ORG,ORR,OSR,RAR,RCI,RCL,
RDR,RDY,RER,RGR,ROR,RRA,RRD,RRE,RRG,RRI,RSP,RTB,SQR,
TBR,VXR,VXX
Protocol is UNDEFINED.
**PROTOCOL DISABLED**
Missing data for all key fields.
Version ID is required.
Missing Required Sending Application.
Broken pointer to App Param (file 771).
Missing required Message Type.
Broken pointer to Msg Type (file 771.2).
For Event Driver-Message Type cannot be an acknowledgement.
Broken pointer to Event Type (file 779.001).
Event type is required for versions greater than 2.1.
Event Driver:
Sending Application:
Version:
Message Type(770.3):
Event Driver Error Summary:
No Event Driver Errors Found.
No Subscribers Found.
Subscriber Protocol is UNDEFINED.
**SUBSCRIBER PROTOCOL DISABLED**
Missing Required Receiving Application.
Message Type must be an appropriate response/acknowledgement.
Missing Processing Routine and Routing Logic.
WARNING-Missing both Logical Link and Routing Logic. Will be local only.
For Subscriber:
Receiving Application:
Message Type (770.11):
No Subscriber Errors Found.
Application is INACTIVE.
REPORT-VARNAME
MONITOR-NAME
DECLARE called -
message is completed
HL7 Monitor -
Mail message #
Turn on/off Event Monitors
Recent Checks of the Monitor by Master Job
Check-time
Event monitor status
Press RETURN to continue...
Requeue minutes
0 [Immediate Run]
Notification mail group
Parameter -
STATUS-MASTER JOB
STATUS-EVENT MONITORING
Change '
... nothing changed ...
HL Event Monitor - #
-------- Master job status is
NOT SET YET
-------- Event monitoring status is
Unknown last master job run time...
Unknown next master job run time...
Unknown last master job run...
Last master job run was
Unknown next master job run...
Next run
in the future...
Monitor description:
' event monitor has completed.
Variable List
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################