News Global Reconnaissance Information System

Global Reconnaissance Information System Core (2.3.02: 11/ 13/ 96) (GRIS)

GRIS provides automated support in planning, scheduling reporting, and monitoring reconnaissance activities under the Sensitive Reconnaissance Operations (SRO) program. GRIS maintains a near real- time status of all SRO missions and provides immediate on- line retrieval of mission, track, and message data. To accomplish this, GRIS provides automatic real- time capture and processing of Reconnaissance Information Processing System (RIPS) format messages, and maintains a mission and track database containing schedule and resultant information. GRIS is used to generate and release the outgoing SRO messages to the Automated Digital Network (AUTODIN) and provides on- line query and report capabilities detailing message, mission status, and scheduling information. It is used to maintain current Track Dictionary data and to generate the master copy of each new dictionary or set of change pages.

This application is intended for use by the Joint Recon Communities at NMCC (JS), ACOM, CENTCOM, EUCOM, PACOM, and SOUTHCOM.

If you ARE NOT one of these sites, DO NOT INSTALL THE GRIS SEGMENT.

This segment should be loaded on your Application Server and Client.

FIXES / NEW FEATURES

This release updates the following:

1. Added help on message error diagnostics to Incoming Message Detail. Help on specific errors can be accessed by pressing the More button inside the Incoming Message Detail help. Also, if you reprocess a message and a red error message stating that the message contains errors pops up, you can get the same specific information by pressing the Help button on the error window (just like for outgoing messages);

2. Added Delete button to Mission Detail History to enable a mission to be backtracked to a given state by simply deleting the item immediately following the desired state;

3. Fixed Track Event and Orbit Index to renumber items after an item has been deleted. Also, deleting a track event will renumber the items under Orbits (because they refer to events). You will not see the renumbering unless you leave the Track Event or Orbit Index and reenter;

4. Added a message sectionalizer to the back end of GRIS to sectionalize any outgoing message over 400 lines long; 5. Made confirmation screens Configurable. You can turn them off by setting CONFIRMATION_ ON in the config file to FALSE;

6. Made reprocessing on save Configurable. If PROCESS_ ON_ SAVE in the config file is set to TRUE, Incoming Message Detail will reprocess a message when you hit the Save button. If it is FALSE, the Save button only saves the edited message, and you have to press Process to reprocess it;

7. Made replacing vs. adding of revised, reprocessed, and retransmitted messages Configurable. If KEEP_ LATEST_ MESSAGE_ ONLY in the config file is set to TRUE, revising, reprocessing, or retransmitting a message will always overwrite the old one. If it is FALSE, revising, reprocessing, or retransmitting will overwrite only a revised message; if the original message was anything else, a new message will be added;

8. The user config file (e. g. config. GCCS) is now checked before the project config vile (viz. config), so default config values placed in the project config file will be picked up if they are absent from the user config file or if the user config file doesn't exist at all;

9. Added this screen;

10. Added a Mission Schedule Message;

11. Changed Fresh Milk terminology to Daily Schedule;

12. If there are no frequencies in the Frequency code table, the Consolidated SRO message will not print them;

13. Replaced the Log from the Mission Query Menu with proper log format;

14. Made the following improvements to the Daily Mission Log:

a. not breaking on DEFAULT HOUR/ MINUTE - fixed

b. actual times not getting reinitialized - fixed

c. multi- day report breaking on scheduled takeoff time only - fixed d. STATUS moved to the second line

e. report made less than 80 columns wide, so it can be printed in portrait mode; 15. Changed message while searching databases to 'Operation is x% complete'. To get this message, you must have the MONITOR trigger turned on. Added this message to database dumps, purges, and reorganizes also;

16. Made database more robust so you won't get a Write_ Before_ Read error on a purge if you erroneously have duplicate records in the database;

17. Removed logic added in 2.2.9 which flagged RECON 3 messages for missions with a different nickname from their tracks. This was incompatible with mixed plate tracks;

18. Fixed a bug introduced into 2.2.9 in the Daily Mission Log: a non- null ACT value would be echoed for all subsequent missions whose ACT value was null; 19. Fixed the Track Summary portion of the Monthly Mission Recap Report and the Statistical Summary Message, so that tracks would appear only once per program;

20. Changed AMP not to check ATD set against ATA (which has not been set yet), because on a Relaunch it would be later than the former ATA, and so would be flagged as an error;

21. Added break capability, breaks are Configurable by changing the 'breaks' file located in the local directory;

22. Made it possible to configure the system so that query selections would be persistent on return from query;

23. Reformatted Mission History (2 lines with item number);

24. Fixed a bug in remark storage: if a remark was greater than 67 characters, only the characters after 67 were being stored in the Mission Database;

25. Added stand- alone RECON template generator. It depends on the recon table, and validates each message token as entered. It is also connected to the help file facility;

26. Added an error message for RECON 2 message events with event of TO or LN and a lat- long location, or with event other than TO or LN and an ICAO location;

27. Fixed a bug in RECON 2 message processing: track time was not getting set;

28. Moved all files created at run time to the gris data directory;

29. Made outgoing messages sensitive to JJJ and HHMM in header (for Julian dates and times);

30. Transmitting an outgoing message now goes through same code as transmitted incoming messages (viz. The headers and footers are updated);

31. !MSNDATA set changed to MANDATORY in recon table;

32. GRIS will raise Code_ List_ Too_ Small when trying to construct a Consolidated SRO Summary Message if there is only one frequency in the Frequency code table, because the same frequency can not be used twice in a row;

33. Changed Track Report to print all 0's for null area time. This situation can only occur in data from the WWMCCS system, as GRIS will not allow null area times to be entered either via AMP or interactively;

34. Migrated GRIS to Oracle;

35. Fixed outgoing messages to update Julian date and time;

36. Added messages to differentiate between a spawned job failure and a timeout while waiting for the spawned job to finish;

37. Added version release number on the main window;

38. Dimmed Reorganize and Dump selections on the maintenance window;

39. Changed format of archive dumps to JSSC format;

40. Made 1MSNDATA set mandatory for all RECON 3 messages;

41. Changed mission result to override Deviation with Abort Complete/ Incomplete But Deviation will still override As Scheduled;

42. Fixed vertical expansion of Mission History that was occurring after deleting an item;

43. Made AMP warning messages to be displayed a Configurable number of times, so they will not go on forever;

44. Added a dump of the user config file to startup; and

45. Added an AMP log, which contains a time stamp message DTG and the message state.

INSTALLATION INSTRUCTIONS

NOTE: If you ARE a GRIS site:

1. Contact the GRIS user before installing the segment.

2. Determine where it makes sense to install GRIS.

3. Only install GRIS where it is NEEDED. DO NOT INSTALL GRIS ON EVERY CLIENT! Typically, there will only be ONE user.

Step 1: Verify installation of required segments: GCCS COE 2.1; AMHS Client 2.1.4; and ORACLE Application Server Tools 7.1.

Step 2: Install GRIS 2.3.02. The following will be presented to the installer: You are currently installing the GCCS Reconnaissance Information System (GRIS).

This system is intended to be used by the Joint Reconnaissance Centers at the following sites...

JCS/ JRC Washington D. C. U. S. Atlantic Command (ACOM) U. S. Central Command (CENTCOM) U. S. European Command (EUCOM) U. S. Pacific Command (PACOM) U. S. Southern Command (SOUTHCOM)

Other sites/ organizations must receive permission from their command's JRC representative to have access to GRIS.
For more information about GRIS, please contact the Joint Reconnaissance Center at DSN 225- 0581. Do you wish to continue with this installation (y/ n)? y Please enter the name of this directory: /home1

/home1 Is this correct (y/ n/ q)? y
USAGE
Every GRIS user must be added to the file /h/ GRIS/ data/ MASTER. You will need to edit this file to include your Unix userid. Make sure that the userid appears in capitol letters and that it is followed by the string $GRIS_ SEGDAT/ For example; MYUSERID=> $GRIS_ SEGDAT/ Also, in order for GRIS to receive incoming messages, your AMHS have a GRIS profile created.
This profile will put a copy of all incoming GRIS messages into a directory where GRIS can find them.

To fully install this release, the following must occur:
1. Install the GRIS segment;
2. If the defaults are not satisfactory, have the site GRIS user set initial data values in the /h/ GRIS/ data/ global/ values/ config file to appropriate values for the database sizes, etc;
3. For those sites converting from a WWMCCS RIS, they need to furnish a dump of their WWMCCS databases (track db and mission db) in the ASCII WWMCCS dump format;
4. Run PostInstall to move the databases to the global data area and install the AMP cron job. The cron job can be found under /h/ data/ global/ gris/ amp, called "amp_ cron". It must be installed manually. Determine who it makes sense to own this cron and install it as that user.

Use the command "crontab /h/ data/ global/ gris/ amp/ amp_ cron", PROVIDED that the user does not have any other cronjobs. Check forst with the "crontab -1" command. If cronjobs exist, then edit the amp_ cron into the cron table manually;
5. Tun /h/ GRIS/ Scripts/ load_ data on the WWMCCS database dumps mentioned in step 3;
6. Set up the sit's AMHS to dump incoming messages to : /h/ data/ global/ gris/ amp/ files You will need the AMHS_ CLT client to be installed on the GRIS client; and
7. GRIS is configured for the following userids: GCCS. If any other userid is used, the file /h/ GRIS/ data/ MASTER can be modified. Contact the GRIS Maintenance POC.