source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0107.txt@ 779

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

Internationalization

File size: 11.6 KB
RevLine 
[604]1English French Notes Complete/Exclude
2 Patch is not installed at any sites.
3Note: Tracking of patch installs began 1/1/98. Prior installs are not reported.
4 No patches installed within this date range.
5 No patches installed.
6 Patch is not installed.
7Other domains where this patch is NOT installed:
8 Patch is installed at all sites.
9 All patches installed. This only applies to patches being tracked.
10 No test installs of this patch at any site.
11 No unreleased patches installed at this site.
12 No unreleased patches installed for this package.
13Choose method of reviewing package installs
141) All packages installed
152) Sites that have installed a package
163) Packages installed at a site
17Display beginning date:
18Enter the date to display backto from today.
19Enter the package to review.
20Site:
21Enter the site to review.
22NOIS Update for call:
23NOIS Update Computed Fields on Calls
24FSC UPDATE
25FSC CHKALERT
26Time may be entered as 8A or 8a, 8:00A, 8:15A, 8:15AM or military
27time: 0800, 1300; or MID or 12M for midnight; NOON or 12N for noon.
28Time must be in quarter hours; e.g., 8A or 8:15A or 8:30A or 8:45A.
29UNDER CONSTRUCTION
30 # Call ID Call Subject
31 # Call ID
32Ref
33Pri
34Call Subject
35Brief Format
36Detailed Format
37Statistic Format
38Fields Format
39Enter the file you wish to review.
40These are files you can review (editing only by supervisors).
41 Functional Area
42 Status History
43Select file:
44Select (P)rint, (S)earch, (I)nquire
45Enter PRINT to print the file.
46Enter SEARCH the file.
47Enter INQUIRE to inquire on the file.
48NOIS calls should be edited using other options.
49NOIS workload should be edited using other options.
50NOIS list should be edited using the hidden action DL (Define List) on the List Manager screens..
51NOIS Status History should be edited using other options.
52These are files you can review.
53 Recurring Events
54Select (P)rint, (S)earch, (I)nquire/Edit
55Select (I)nquire/Edit or (N)ew:
56Enter NEW to make a new entry.
57Enter the schedule date.
58RECURRING EVENTS
59Select (B)rief, (D)etailed, (C)ustom, (F)ields, or (S)tatistic:
60Select Calls
61 invalid entry
62EXTENDED HELP
63 enter only a single number
64 enter a number or number range (ex. 5,8-11)
65 enter a single number
66 enter an appropriate number
67Select Parameter:
68Select Module/Version:
69Select Specialist:
70Select Display Format:
71Select Priority:
72Select Subcomponent:
73Select Task:
74Select Functional Area:
75Select Package:
76Select Workload:
77Select Status History:
78Select NOIS call to be deleted:
79FSC PURGE
80No calls on this list.
81 calls will be deleted.
82WARNING!!!! This option is used to PURGE calls.
83Are you sure you want to do this?
84Enter YES to get a list to purge.
85Enter or '^' to exit.
86WARNING!!!! This will purge the calls in this list.
87Enter YES to purge these calls.
88No calls were purged.
89Select Print Template:
90No fields selected.
91(Optional) Select a Field to Collate your fields with:
92NOIS LOCATION
93NOIS OFFICE
94NOIS MODULE/VERSION
95NOIS PACKAGE
96NOIS LOCATION TYPE
97NOIS PACKAGE GROUP
98NOIS TASK
99NOIS SYSTEM
100NOIS FIELD
101TR:FMS
102Creating entry TR:FMS in file 2101.2...
103Entry TR:FMS already exists in file 2101.2
104FINANCIAL MANAGEMENT
105FMS Transfer Document
106An ERROR has occured
107Entry TR:FMS created in file 2101.2
108Requeueing entries in file 2100.1...
109Queued
110READY TO BATCH
111 CODE SHEETS
112'YES' will start batching, 'NO' or '^' will exit.
113THERE ARE NO CODE SHEETS WAITING TO BE BATCHED.
114Creating BATCH NUMBER:
115TOTAL code sheets batched:
116 << CODE SHEET DELETED >>
117This code sheet has been assigned IDENTIFICATION NUMBER:
118UNABLE TO CREATE CODE SHEET!
119-- FMS Control Segment Data --
120-- FMS Document Data --
121Current Status: Warning -
122Enter RETURN or '^' to exit
123GECS(
124GECSDATA(
125Transaction Type:
126Stuffing data into the following fields:
127AMIS MONTH/YEAR:
128First, you should use File Manager's 'Modify File Attributes' option
129and set up the fields used for this code sheet. Use the field numbers
130and global nodes assigned to the application and ISC. Also, use any
131necessary input transforms for manipulating the data for the code sheet.
132Secondly, you should use File Manager's 'Enter or Edit File Entries' option
133and create the Input Template corresponding to the fields used in the
134Generic Code Sheet system. Selected fields should be in the order they
135are to be coded.
136Setting Up File 2101.7 GENERIC CODE SHEET SITE...
137Setting Up File 2101.1 GENERIC CODE SHEET BATCH TYPE...
138Setting Up File 2101.2 GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT...
139** CODE SHEET NUMBER:
140CODE SHEET AUTOMATICALLY MARKED FOR BATCHING !
141DO YOU WANT TO MARK FOR REBATCHING
142'YES' to mark for rebatching.
143'NO' or '^' to abort.
144*** FMS DOCUMENTS DO NOT HAVE TO BE BATCHED ***
145YOU CAN ONLY SELECT CODE SHEETS WHICH HAVE BEEN MARKED FOR BATCHING.
146YOU CAN ONLY SELECT FMS DOCUMENTS WHICH HAVE NOT BEEN TRANSMITTED.
147CODE SHEET MUST BE READY FOR BATCHING BEFORE THE BATCH NUMBER CAN BE EDIT.
148USE THE 'Code Sheet Edit' OPTION.
149Do you want to DELETE this batch number
150Enter 'YES' to DELETE batch number, 'NO' ro select a NEW batch number,
151or '^' to exit.
152READY TO CHANGE THE BATCH NUMBER
153Enter 'YES' to change the batch number, 'NO' or '^' to exit.
154UNABLE TO SET BATCH NUMBER
155CODE SHEET READY FOR TRANSMISSION IN BATCH
156NO CODE SHEETS INCLUDED IN BATCH
157DELETING BATCH
158WARNING -- If you have already sent the AMIS code sheets for this month and the
159code sheets are duplicates, Austin will reject messages for each of the
160READY TO MARK BATCH FOR RETRANSMISSION
161Enter 'YES' to mark batch for retransmission, 'NO' or '^' to exit.
162Batch Number
163 ready for transmission.
164 not found. No action taken.
165 MailMan patch XM*DBA*92 must be installed prior to running
166 routine GECSPAT8. The MailMan patch establishes domain
167 which is required by this routine. Please rerun
168 this routine (D ^GECSPAT8) after installing patch XM*DBA*92.
169Updating GENERIC CODE SHEET BATCH TYPE (#2101.1)...
170This batch type contains the required information for
171Fixed Assets transmissions.
172FIXED ASSETS
173Updating GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT (#2101.2)...
174FA:FMS
175FIXED ASSETS ACQUISITION
176FB:FMS
177FIXED ASSETS BETTERMENT
178FC:FMS
179FIXED ASSETS CHANGE
180FD:FMS
181FIXED ASSETS DISPOSITION
182FR:FMS
183FIXED ASSETS TRANSFER
184Process completed. Routine GECSPAT8 can be deleted now.
185==================== *** INSTALLING PIMS 5.3 PATCH 47 *** ==================
186Installing PIMS Patch DG*5.3*47, routine DGGECSB ...
187Cannot install PIMS patch DG*5.3*47
188routine GECSDG not found!
189GECS BATCH EDIT
190BATCH TYPE:
191Deleting all code sheets created or transmitted before:
192deleting batches and code sheets contained in batches:
193 --deleted, cleaning up associated code sheets:
194cleaning up code sheets:
195Finished - deleted
196 code sheets.
197cleaning up stack file:
198CODE SHEET/TRANSMISSION RECORD DELETION TRANSCRIPT
199This routine will delete Code Sheets from the Code Sheet file and
200Batch and Transmission records from the Transmission Record file.
201Deletion is based upon the date a batch and a code sheet is
202Enter the number of days you wish to retain code sheets
203Enter the number of days you want to retain code sheets. Code sheet created
204past the retaining days will be deleted.
205NOTICE: I recommend keeping code sheets for at least 30 days.
206This program will remove all stack file entries which were created before
207I will now delete all code sheets and associated records which were
208created before
209OK to continue
210Purge Generic Code Sheets
211GECS*
212>> please wait <<
213DO YOU WANT TO DELETE ALL TYPES OF CODE SHEETS
214ENTER 'YES' TO DELETE ALL TYPE OF CODE SHEETS, 'NO' TO SELECT THE BATCH TYPE.
215Do you want to print the code sheet
216'YES' will print a listing of the CODE Sheet.
217'NO' will print a listing of the code sheet ID.
218Do you want a detailed listing
219'YES' will print the ID or actual code sheets by batch.
220'NO' will only print the batch numbers.
221ERROR:
222DESCR:
223MAIL MSGS:
224CONFIRMATION:
225*OLD MSGS:
226*** ACTUAL CODE SHEET:
227*** END OF CODE SHEET ***
228TOTAL CODE SHEETS:
229GCS STACK FILE STATUS REPORT
230TC-TRAN CODE -BATNUM
231DATE@TIME CREATED
232HOLD DATE
233START with TRANSACTION CODE: FIRST//
234Select the starting TRANSACTION CODE. The TRANSACTION CODE is the two
235character code which identifies the document type.
236 END with TRANSACTION CODE: LAST//
237Select the ending TRANSACTION CODE.
238Ending TRANSACTION CODE must follow starting TRANSACTION CODE.
239Print documents created after DATE:
240JAN 1,1993
241N:TRANSMITTED WITH NO CONFIRMATION MESSAGE RETURNED
242Select STATUS(ES) to display
243-- previously selected --
244A STATUS was not selected !
245 Do you want to print ALL stack documents
246 Enter YES to print all documents, NO or '^' to exit.
247SELECTED STATUS(ES) to display:
248 ALL STATUS(ES)
249Print DESCRIPTION of event
250Print DOCUMENT code sheets
251GCS Stack File Report
252<*> please wait <*>
253Select Stack Document:
254Another user is working with the stack document, try again later.
255GECSXMY(
256GCS TRANSACTION
257 REJECT IN FMS
258NO SITE PARAMETERS HAVE BEEN ENTERED IN FILE 2101.7,
259 NOT FOUND IN FILE 2101.7.
260Select STATION NUMBER
261 (^ TO EXIT)
262Site Missing From GENERIC CODE SHEET FILE 2101.7
263Site
264 does not exist in File #2101.7. Please contact
265your Information Resource Management(IRM) Personnel and
266inform them that Site
267 be inserted into File
268#2101.7 in order for you to continue with this option.
269Site Missing From INSTITUTION FILE #4
270 does not exit
271 in the INSTITUTION FILE #4
272Please contact your Information Resource Management
273(IRM) Personnel and inform them that Site
274be inserted into File #4.
275STATION NAME missing from INSTITUTION FILE #4
276 STATION NAME is not entered in Field #.01 of the
277INSTITUTION FILE #4. Please inform your Information Resource
278Management(IRM) Personnel.
279STATION NUMBER missing from INSTITUTION FILE #4
280INTERNAL ENTRY NUMBER(IEN)
281 does not have
282a STATION NUMBER
283entered in field #99 of the INSTITUTION FILE #4. Please
284YOU ARE NOT AN AUTHORIZED USER. CONTACT IRM SERVICE
285Select Stack Document for Retransmission:
286There is not a code sheet for this stack entry.
287** FINAL DOCUMENTS CANNOT BE RETRANSMITTED **
288WARNING: Accepted documents probably should not be retransmitted.
289Do you want to retransmit this document now
290Enter 'YES' to retransmit the document immediately, 'NO' or '^' to exit.
291NEW Status:
292Control segment/first line of code sheet missing
293Segment not defined for entry
294Batch type in file 2101.2 is incorrect
295Code sheet has been altered since creation
296<not recorded>
297<<UNDEFINED BATCH TYPE>>
298No receiving users for batch type:
299Mailman Error:
300CANNOT FIND BATCH NUMBER IN FILE 2101.3.
301RECEIVING USERS FOR THIS BATCH TYPE HAVE NOT BEEN ENTERED.
302Transmission will be to the following:
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.