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

308 lines
11 KiB
Plaintext

English French Notes Complete/Exclude
Additions/Modifications to
Lookup on
which file?:
not found in local lookup file.
Select LOCAL KEYWORD NAME:
...Ok, will now setup KEYWORD and SHORTCUT file DD's
to allow terms for '
<REMINDER> Using 'Edit File', set the lookup routine, XTLKDICL, in
There are still Keywords, Shortcuts and/or Synonyms for this entry.
<<Nothing Deleted!>>
Deleting from Local Lookup file.....
Deleting variable pointers from Local Keyword and Shortcut files.
<REMINDER> Delete the lookup routine, XTLKDICL, from
ANSWER WITH LOCAL KEYWORD NAME, OR CODE
Too many terms meet your criteria; please refine your search.
XTLKL,0)
MTLU found no usable words.
The following word
not used in this search:
matches were found:
Press <RET> or Select 1-
<display protocol not provided>
Answer with a number from 1 to
'^' to quit the MTLU search and attempt a FILEMAN search, or
'^^' to quit and return to your menu, or
'^#' if you want to jump to any of the
allowable choices.
<no long description available>
...Nothing selected. Attempting Fileman lookup.
Print which file?
Shortcuts
Keywords
Sort By?
sorted by Name.
sorted by Code.
One moment while I check/clean up MTLU variable pointers.
NARRATIVE:
-- NO CONTROL CHARACTERS ALLOWED!
Compares two routines
First Routine
Compare to Routine:
Loading Routines.
Routine Compare
Routine name to do compare on.
Compares routines from tape/file with what's on disk.
Device with Routines:
Tape header
Output Report on Device:
Compare of routines from tape, (
) and disk
not on disk
Disk
Routine Group Edit
Has changed, Old:
Is new
Has changed
Caused an error:
Starting LOST routine check.
Not in UCI
Grant World READ access for ^RTH; then comment out lines MSG:MSG+2.
This routine must be used from the Production UCI.
If your Mgr UCI is not named MGR, edit line A+1 appropriately.
Global Gets
Global Sets
Global Kills
Logical Reads
Physical Reads
Logical Writes
Physical Writes
STARTDATE @ STIME
ET
This generates the Checksum/2nd line list for the routines from a BUILD file.
No BUILD file to work from.
No routines in this build.
Routine not in this UCI.
No other routines in this build.
;**[Patch List]**;
Routine Summary
The following routines are included in this patch. The second line of each
of these routines now looks like:
Old
Patch List
Sites should use CHECK^XTSUMBLD to verify checksums.
RTN(
List of preceding patches:
This will update the ROUTINE file for the routines from a BUILD file.
not found in the database.
New ChkSum
Old ChkSum
Old Date
Checksum mismatch
PL?.E1P1
Working on list
PING reply to:
PING SERVER
Build from
This will build a checksum routine for a package from the package file
This will build a checksum routine from the BUILD file.
There isn't a package file pointer.
I will create a routine
But you already have one on file! OK to replace?
Routine list is empty
Calculating check-sums
Building routine
Filing routine
NO SELECTED ROUTINES
This will check the routines from a BUILD file.
Missing patch number
This option determines the current checksum of selected routine(s).
The Checksum of the routine is determined as follows:
1. Any comment line with a single semi-colon is presumed to be
followed by comments and only the line tag will be included.
2. Line 2 will be excluded from the count.
3. The total value of the routine is determined by taking, excluding the
exception, as noted above, and multipling the ASCII value of each
character by its position on the line being checked.
DUZ UNDEFINED...ABORTED.
You're on
. Checksums for selected routines on other systems
will be compared to those on this system.
A checksum job, launched on
already on file.
It has a status of:
Okay to delete the existing data
Nothing deleted...this job aborted.
No routines selected.
No Systems to Check
I will Check the Routines on the following Systems:
Accept this list and continue
Enter Yes if you want to check the routines on the listed Systems
Enter No if you want to create your own list of Systems.
Routine Checksum Checker
Error...not queued!!
Queued to run^
will calculate checksums for the selected
routines here on
These values will be used for comparison with the same routine set on all
the other systems. You will receive an alert when the job finishes. The
alert action will allow you to view/print the report that lists any
routines that do not match the
calculated checksums.
Calculating checksums
Routine Checksum Checker for
Waiting for jobs to finish
ERROR - was idle for more than 30 minutes
Routine checksum job completed.
NOT ON THIS SYSTEM
Checksum on
Normal Completion
ERROR - Job terminated before completion
ROUTINE CHECKSUM REPORT
ERROR -- NO data to retrieve!
Print Routine Checksum Results
JOB STARTED:
JOB ENDED:
UCI,VOL:
MASTER ROUTINE SET USED RESIDES ON UCI,VOL:
VARIABLE CHANGER
VARIABLE TO CHANGE:
CHANGE TO:
F I2=0:0 S RN=$O(^TMP($J,RN)) Q:RN=NL ZL @RN W:$X>70 ! W $J(RN,10) S CH=0 X X1 I CH ZS @RN W !
* DONE CHANGING
is used as a line label and DO or GOTO may be changed.
Record Current Global Nodes for Package for Future Comparison
Date current status is to be recorded as:
Current Version Number (optional):
Enter a version number (beginning with a number at least) or RETURN
Package Globals Record
OPTIONS;DIC(19,^KEYS;DIC(19.1,^HELP FRAMES;DIC(9.2,^BULLETINS;XMB(3.6,^FUNCTIONS;DD(
,^EDIT TEMPLATES;DIE(^SORT TEMPLATES;DIBT(^PRINT TEMPLATES;DIPT(^S;SCRE(
PREPARE A LIST OF GLOBAL NODES WHICH HAVE BEEN ALTERED
There is no global data saved for this package
This analysis will be QUEUED to device other than HOME
Compare Global Nodes
GLOBAL COMPARISON FOR VERIFICATION PACKAGE:
FILE #
IS NOT PRESENT IN NEW VERSION.
APPEARS AS A **NEW** FILE.
has been ** ADDED **
has been ** DELETED **
ENTRIES OF
IN B X-REF OF CURRENT
IN B X-REF OF OLD
XTTYI,1,XTN,1,1,1)
DELETED
OLD IEN=
XTTYI,1,XTN,1,
ADDED
XTTYI,1,XTN,1,M,0)
HELP FRAMES
CHANGED
THIS ROUTINE WILL UPDATE THE VERSION NUMBER OR PATCH LIST
IN THE ROUTINES SELECTED
Will only update the Version number.
This will use the BUILD file for the list of routines to update.
It will update the Patch number of the patch list.
WHAT IS THE VERSION NUMBER:
Enter a number of the form nn.nn[Tnn or Vnn]
The package name will go into the 4th piece of the second line.
This date is only used if building a new second line.
Enter the Version Date
The DATE of this Version
Clear the 'Patch List'
Answer YES to remove the list of patch numbers from the 5th piece of the second line.
Patch
number to
Are you ready
Do you want to QUEUE this job? YES//
XTVRC1-RECORD ROUTINE CHANGES
ZL @XTROU F I=0:1 S X=$T(+I) Q:X=
List CHANGES since DATE
XTVRC1A-IDENTIFY ROUTINES RECENTLY LOGGED AS CHANGED
The following routines have been logged as NEW ROUTINES since
NEW routines were logged
The following routines have logged CHANGES since
old routines were CHANGED
The following routines have NOT LOGGED CHANGES since
UNCHANGED routines were included
The following routines were previously LOGGED BUT NOT IN THE ACCOUNT
Routines were searched for using 2 letter namespaces from routines
originally specified.
DELETED routines identified using 2 letter namespaces input
Enter RETURN to continue...
is shown as name on first line
This routine lists the changes in program code that have been noted.
Select the routine(s) which you want changes listed for:
Show changes back to DATE
(none if number of changes is to be specified):
Show changes for how many past versions (or ALL): 1//
Enter a number indicating the number of past versions you want to see changes
Routine Changes
The following routines ARE NEW to the file (no prior version to compare):
NO CHANGE
The following routines showed no change in the specified number of versions:
changes in code
original line
deleted. code was:
new line
inserted **BEFORE** original line
Name of ROUTINE to be restored:
Save RESTORED ROUTINE as:
Must be a routine name not currently in use.
WARNING: ^XIP global not initialized!
Please see the Pre-installation Instructions in the
patch description for initialization instructions.
>>>> Installation aborted <<<<
Invalid Data Dictionary entry for file #5.12!
Please contact NVS for assistance.
>>>> Installation aborted <<<<
*** Adding missing counties to the State file ***
**ERROR: Missing or Corrupt State:
. This process could not add
already exists - no action taken.
was added successfully.
>>>XU*8*264 Post-Install complete..
locked at time of patch installation. Could not inactivate.
Resident, Allopathic (includes Interns, Residents, Fellows)
Resident, Osteopathic (includes Interns, Residents, Fellows)
locked at time of patch installaion. Could not inactivate.
Reindexing
cross reference...
Done reindexing
cross reference.
Non-production account. No transmission of OAA data will take place.
Begin transmission of OAA data...
Done with transmission of OAA data.
AK.
Press Return to Continue.
as a new person.
This user has the following Person Class enties:
Are you sure you want to remove ALL these entries
This field is uneditable because Expired Date already has data
You cannot change the value of this field.
REALIGNED TO
REALIGNED FROM
PARENT FACILITY
Purge Programmer Mode Entry Log
You will be asked for a date range to purge, Begin to End
PURGE BEGIN DATE:
PURGE END DATE:
Purge User Failed Access Attempts
Purge Menu Option Audit Entries
What Namespace:
NO SWITCHING UCI'S IN PROGRAMMER MODE!
You're now in namespace:
' DOES NOT EXIST IN
' IS AN INVALID NAMESPACE!
GT.M doesn't have an equivlent to UCI's.
You will remain in this enviroment.
What UCI:
YOU'RE IN UCI:
' IS AN INVALID UCI!
DHCP$UCI_CHANGE
[Average Response Time by Site]
[Average Response Times by Nodename]
[Daily Average Response Times by Nodename]
For NODE:
BERSTEIN PERFORMANCE REPORT
Request queued, task number:
Date to START with:
Date to END with:
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################
#################### #################### ####################