English	French	Notes	Complete/Exclude
        Patch is not installed at any sites.			
Note: Tracking of patch installs began 1/1/98. Prior installs are not reported.			
        No patches installed within this date range.			
        No patches installed.			
        Patch is not installed.			
Other domains where this patch is NOT installed:			
        Patch is installed at all sites.			
        All patches installed. This only applies to patches being tracked.			
        No test installs of this patch at any site.			
        No unreleased patches installed at this site.			
        No unreleased patches installed for this package.			
Choose method of reviewing package installs			
1) All packages installed			
2) Sites that have installed a package			
3) Packages installed at a site			
Display beginning date: 			
Enter the date to display backto from today.			
Enter the package to review.			
Site: 			
Enter the site to review.			
NOIS Update for call: 			
NOIS Update Computed Fields on Calls			
FSC UPDATE			
FSC CHKALERT			
Time may be entered as 8A or 8a, 8:00A, 8:15A, 8:15AM or military			
time: 0800, 1300; or MID or 12M for midnight; NOON or 12N for noon.			
Time must be in quarter hours; e.g., 8A or 8:15A or 8:30A or 8:45A.			
UNDER CONSTRUCTION			
 #      Call ID                    Call Subject                                  			
 #     Call ID     			
Ref			
Pri			
Call Subject			
Brief Format       			
Detailed Format    			
Statistic Format   			
Fields Format      			
Enter the file you wish to review.			
These are files you can review (editing only by supervisors).			
          Functional Area			
          Status History			
Select file: 			
Select (P)rint, (S)earch, (I)nquire			
Enter PRINT to print the file.			
Enter SEARCH the file.			
Enter INQUIRE to inquire on the file.			
NOIS calls should be edited using other options.			
NOIS workload should be edited using other options.			
NOIS list should be edited using the hidden action DL (Define List) on the List Manager screens..			
NOIS Status History should be edited using other options.			
These are files you can review.			
          Recurring Events			
Select (P)rint, (S)earch, (I)nquire/Edit			
Select (I)nquire/Edit or (N)ew: 			
Enter NEW to make a new entry.			
Enter the schedule date.			
RECURRING EVENTS			
Select (B)rief, (D)etailed, (C)ustom, (F)ields, or (S)tatistic: 			
Select Calls			
  invalid entry			
EXTENDED HELP			
  enter only a single number			
  enter a number or number range (ex. 5,8-11)			
  enter a single number			
  enter an appropriate number			
Select Parameter: 			
Select Module/Version: 			
Select Specialist: 			
Select Display Format: 			
Select Priority: 			
Select Subcomponent: 			
Select Task: 			
Select Functional Area: 			
Select Package: 			
Select Workload: 			
Select Status History: 			
Select NOIS call to be deleted: 			
FSC PURGE			
No calls on this list.			
 calls will be deleted.			
WARNING!!!! This option is used to PURGE calls.			
Are you sure you want to do this? 			
Enter YES to get a list to purge.			
Enter or '^' to exit.			
WARNING!!!! This will purge the calls in this list.			
Enter YES to purge these calls.			
No calls were purged.			
Select Print Template: 			
No fields selected.			
(Optional) Select a Field to Collate your fields with: 			
NOIS LOCATION			
NOIS OFFICE			
NOIS MODULE/VERSION			
NOIS PACKAGE			
NOIS LOCATION TYPE			
NOIS PACKAGE GROUP			
NOIS TASK			
NOIS SYSTEM			
NOIS FIELD			
TR:FMS			
Creating entry TR:FMS in file 2101.2...			
Entry TR:FMS already exists in file 2101.2			
FINANCIAL MANAGEMENT			
FMS Transfer Document			
An ERROR has occured			
Entry TR:FMS created in file 2101.2			
Requeueing entries in file 2100.1...			
Queued			
READY TO BATCH 			
 CODE SHEETS			
'YES' will start batching, 'NO' or '^' will exit.			
THERE ARE NO CODE SHEETS WAITING TO BE BATCHED.			
Creating BATCH NUMBER: 			
TOTAL code sheets batched: 			
  << CODE SHEET DELETED >>			
This code sheet has been assigned IDENTIFICATION NUMBER: 			
UNABLE TO CREATE CODE SHEET!			
-- FMS Control Segment Data --			
-- FMS Document Data --			
Current Status: Warning - 			
Enter RETURN or '^' to exit			
GECS(			
GECSDATA(			
Transaction Type: 			
Stuffing data into the following fields:			
AMIS MONTH/YEAR: 			
First, you should use File Manager's 'Modify File Attributes' option			
and set up the fields used for this code sheet.  Use the field numbers			
and global nodes assigned to the application and ISC.  Also, use any			
necessary input transforms for manipulating the data for the code sheet.			
Secondly, you should use File Manager's 'Enter or Edit File Entries' option			
and create the Input Template corresponding to the fields used in the			
Generic Code Sheet system.  Selected fields should be in the order they			
are to be coded.			
Setting Up File 2101.7 GENERIC CODE SHEET SITE...			
Setting Up File 2101.1 GENERIC CODE SHEET BATCH TYPE...			
Setting Up File 2101.2 GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT...			
** CODE SHEET NUMBER: 			
CODE SHEET AUTOMATICALLY MARKED FOR BATCHING !			
DO YOU WANT TO MARK FOR REBATCHING			
'YES' to mark for rebatching.			
'NO' or '^' to abort.			
*** FMS DOCUMENTS DO NOT HAVE TO BE BATCHED ***			
YOU CAN ONLY SELECT CODE SHEETS WHICH HAVE BEEN MARKED FOR BATCHING.			
YOU CAN ONLY SELECT FMS DOCUMENTS WHICH HAVE NOT BEEN TRANSMITTED.			
CODE SHEET MUST BE READY FOR BATCHING BEFORE THE BATCH NUMBER CAN BE EDIT.			
USE THE 'Code Sheet Edit' OPTION.			
Do you want to DELETE this batch number			
Enter 'YES' to DELETE batch number, 'NO' ro select a NEW batch number,			
or '^' to exit.			
READY TO CHANGE THE BATCH NUMBER			
Enter 'YES' to change the batch number, 'NO' or '^' to exit.			
UNABLE TO SET BATCH NUMBER 			
CODE SHEET READY FOR TRANSMISSION IN BATCH 			
NO CODE SHEETS INCLUDED IN BATCH 			
DELETING BATCH 			
WARNING -- If you have already sent the AMIS code sheets for this month and the			
code sheets are duplicates, Austin will reject messages for each of the			
READY TO MARK BATCH FOR RETRANSMISSION			
Enter 'YES' to mark batch for retransmission, 'NO' or '^' to exit.			
Batch Number 			
 ready for transmission.			
 not found. No action taken.			
   MailMan patch XM*DBA*92 must be installed prior to running			
   routine GECSPAT8. The MailMan patch establishes domain 			
 which is required by this routine. Please rerun			
   this routine (D ^GECSPAT8) after installing patch XM*DBA*92.			
Updating GENERIC CODE SHEET BATCH TYPE (#2101.1)...			
This batch type contains the required information for			
Fixed Assets transmissions.			
FIXED ASSETS			
Updating GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT (#2101.2)...			
FA:FMS			
FIXED ASSETS ACQUISITION			
FB:FMS			
FIXED ASSETS BETTERMENT			
FC:FMS			
FIXED ASSETS CHANGE			
FD:FMS			
FIXED ASSETS DISPOSITION			
FR:FMS			
FIXED ASSETS TRANSFER			
Process completed. Routine GECSPAT8 can be deleted now.			
==================== *** INSTALLING  PIMS  5.3  PATCH 47 *** ==================			
Installing PIMS Patch DG*5.3*47, routine DGGECSB ...			
Cannot install PIMS patch DG*5.3*47			
routine GECSDG not found!			
GECS BATCH EDIT			
BATCH TYPE: 			
Deleting all code sheets created or transmitted before: 			
deleting batches and code sheets contained in batches:			
  --deleted, cleaning up associated code sheets:			
cleaning up code sheets:			
Finished - deleted 			
 code sheets.			
cleaning up stack file:			
CODE SHEET/TRANSMISSION RECORD DELETION TRANSCRIPT 			
This routine will delete Code Sheets from the Code Sheet file and			
Batch and Transmission records from the Transmission Record file.			
Deletion is based upon the date a batch and a code sheet is			
Enter the number of days you wish to retain code sheets			
Enter the number of days you want to retain code sheets.  Code sheet created			
past the retaining days will be deleted.			
NOTICE: I recommend keeping code sheets for at least 30 days.			
This program will remove all stack file entries which were created before			
I will now delete all code sheets and associated records which were			
created before 			
OK to continue			
Purge Generic Code Sheets			
GECS*			
>> please wait <<			
DO YOU WANT TO DELETE ALL TYPES OF CODE SHEETS			
ENTER 'YES' TO DELETE ALL TYPE OF CODE SHEETS, 'NO' TO SELECT THE BATCH TYPE.			
Do you want to print the code sheet			
'YES' will print a listing of the CODE Sheet.			
'NO' will print a listing of the code sheet ID.			
Do you want a detailed listing			
'YES' will print the ID or actual code sheets by batch.			
'NO' will only print the batch numbers.			
ERROR: 			
DESCR: 			
MAIL MSGS: 			
CONFIRMATION: 			
*OLD MSGS: 			
*** ACTUAL CODE SHEET:			
*** END OF CODE SHEET ***			
TOTAL CODE SHEETS: 			
GCS STACK FILE STATUS REPORT			
TC-TRAN CODE  -BATNUM			
DATE@TIME CREATED			
HOLD DATE			
START with TRANSACTION CODE: FIRST// 			
Select the starting TRANSACTION CODE.  The TRANSACTION CODE is the two			
character code which identifies the document type.			
  END with TRANSACTION CODE: LAST// 			
Select the ending TRANSACTION CODE.			
Ending TRANSACTION CODE must follow starting TRANSACTION CODE.			
Print documents created after DATE: 			
JAN 1,1993			
N:TRANSMITTED WITH NO CONFIRMATION MESSAGE RETURNED			
Select STATUS(ES) to display			
-- previously selected --			
A STATUS was not selected !			
  Do you want to print ALL stack documents			
  Enter YES to print all documents, NO or '^' to exit.			
SELECTED STATUS(ES) to display:			
  ALL STATUS(ES)			
Print DESCRIPTION of event			
Print DOCUMENT code sheets			
GCS Stack File Report			
<*> please wait <*>			
Select Stack Document: 			
Another user is working with the stack document, try again later.			
GECSXMY(			
GCS TRANSACTION 			
 REJECT IN FMS			
NO SITE PARAMETERS HAVE BEEN ENTERED IN FILE 2101.7,			
 NOT FOUND IN FILE 2101.7.			
Select STATION NUMBER			
 (^ TO EXIT)			
Site Missing From GENERIC CODE SHEET FILE 2101.7			
Site 			
 does not exist in File #2101.7. Please contact			
your Information Resource Management(IRM) Personnel and			
inform them that Site 			
 be inserted into File			
#2101.7 in order for you to continue with this option.			
Site Missing From INSTITUTION FILE #4			
 does not exit			
 in the INSTITUTION FILE #4			
Please contact your Information Resource Management			
(IRM) Personnel and inform them that Site 			
be inserted into File #4.			
STATION NAME missing from INSTITUTION FILE #4			
 STATION NAME is not entered in Field #.01 of the			
INSTITUTION FILE #4. Please inform your Information Resource			
Management(IRM) Personnel.			
STATION NUMBER missing from INSTITUTION FILE #4			
INTERNAL ENTRY NUMBER(IEN) 			
 does not have 			
a STATION NUMBER			
entered in field #99 of the INSTITUTION FILE #4. Please 			
YOU ARE NOT AN AUTHORIZED USER.  CONTACT IRM SERVICE			
Select Stack Document for Retransmission: 			
There is not a code sheet for this stack entry.			
** FINAL DOCUMENTS CANNOT BE RETRANSMITTED **			
WARNING: Accepted documents probably should not be retransmitted.			
Do you want to retransmit this document now			
Enter 'YES' to retransmit the document immediately, 'NO' or '^' to exit.			
NEW Status: 			
Control segment/first line of code sheet missing			
Segment not defined for entry			
Batch type in file 2101.2 is incorrect			
Code sheet has been altered since creation			
<not recorded>			
<<UNDEFINED BATCH TYPE>>			
No receiving users for batch type: 			
Mailman Error: 			
CANNOT FIND BATCH NUMBER IN FILE 2101.3.			
RECEIVING USERS FOR THIS BATCH TYPE HAVE NOT BEEN ENTERED.			
Transmission will be to the following:			
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
