INTEGRATED INFORMATION SYSTEM REQUEST FOR PROPOSALS FEBRUARY 1968

• Document Type: CREST
• Collection: NGA Records (Formerly NIMA)
• Document Number (FOIA) /ESDN (CREST): CIA-RDP78B04747A001900050003-4
• Release Decision: RIPPUB
• Original Classification: S
• Document Page Count: 210
• Document Creation Date: December 28, 2016
• Document Release Date: December 21, 2001
• Sequence Number: 3
• Publication Date: February 1, 1968
• Content Type: REPORT

Approved For Release 2002/091D :CIA=RDP78BO4747AO01900050003-4
INTEGRATED INFORMATION SYSTEM
REQUEST FOR PROPOSALS
FEBRUARY 1968
DECLASS REVIEW by NIMA/DOD
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
GROUP I: EXCLUDED
FROM AUTOMATIC DOWNGRADING
AND DECLASSIFICATION
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
This document contains information affecting
the national defense of the United States,
within the meaning of Title 18, sections
793 and 794, of the U.S. Code, as amended.
Its transmission or revelation of its contents
to or receipt by an unauthorized person is
prohibited by law.
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
REQUEST FOR PROPOSALS
February 1968
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
BACKGROUND AND SYSTEM CONCEPTS
Our concern in this Request for Proposal (RFP) is with imagery
and the efficient exploitation of that imagery. This exploitation
must be facilitated to the greatest possible extent. To accomplish
this, the techniques and practices employed by the photo interpreter
must be continually improved. A key to this improvement involves the
capability of giving the photo interpreter complete, accurate, and
timely information, thus enabling him to produce more meaningful
intelligence per unit of work. One major aspect of such support in-
volves the use of computers. A recent study, which analyzed infor-
mation requirements for the imagery exploitation process, indicated
that it could be improved through the more effective use of computers.
This study also indicated that it is possible to store most of the
required information on computer mass storage devices to which ana-
lysts would have direct and rapid access. This system concept is
called the Integrated Information System (IIS) and embodies such
obvious advantages as immediate access to data by photo interpreters
producing imagery-derived reports and the capability of updating files
immediately for subsequent reporting. Other advantages to this system
include the more rapid dissemination of information in hard-copy re-
ports to users and, eventually, the elimination of some requirements
for finished reports by making possible direct queries of supporting
data bases. Our primary purpose in issuing this Request for Proposal
is to obtain a contractor and the necessary personnel who will he
capable of assisting in implementing this system.
The IIS calls for a data base consisting of four major files:
(1) the Installations Data File (IDF)
(2) the Mensuration Parameters File (MPF)
(3) the Objects Data File (ODF)
(4) the Exploitation Products Data File (EPDF)
This data base will be maintained on UNIVAC Fastrand II drums. In-
dexes to the data base will reside on high-speed FII-880 drums. The
drum memories are controlled by a UNIVAC 494 real-time operating
system. Depending upon their function, personnel will communicate
with this computer storage system through a variety of terminal
devices. These devices will range from simple keyboards (used for
entering information) to cathode ray tubes, which will be used for
the verification, editing, and approval of displayed information.
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
High-speed printers will produce output that does not involve real-
time communication.
The IIS will support the photo interpreter during three major
processes: prior to reporting, during reporting, and after reporting
has been completed. Before the reporting process begins, the $ystem
will
* predict those installations which will
be imaged on film;
* provide data to aid in the assignment of
photo interpreters and in the scheduling
of their workloads;
* issue instructions for the delivery and
control of film to assigned personnel; and
* provide them with necessary data from the
data base for the reporting process.
During the reporting process the system
* will allow the photo interpreter to query
the data base for additional information;
* using 'the Mensuration Parameters File and
other related programming packages, will
permit on-line mensuration;
* following the analytical process, facilitate
the entry, verification, editing, and
approval of reported information.
After the reporting process has been completed, the data derived from
imagery analysis will be used to automatically update the Installa-
tion Data File (IDF) and to generate hard-copy reports in response to
current production requirements. Photographic interpretation reports
may contain collection interpretations for a given day or week. Al-
though emphasis has been placed on the IDF, the program packages must
be applicable to all files in the data base as indicated in the
specifications.
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
The system configuration during the development and implemen-
tation stage includes hardware, software, as well as the data base
files. The hardware configuration for the first stage is given
below. A second UNIVAC-494 system will be installed in the future
when the IIS has been implemented. Estimated installation date of
the second system is April 1969. The associated remote terminals
not listed will also be available during the development of the
various program packages.
UNIVAC Equipment
Rio el Number)
Unit
Quantity
3012-00
Central processor
1
7005-97
Core memory, 132K
1
5008-17
Magnetic tape control
4
859-02
Magnetic tape unit VIIIC
12
6010-00
Fastrand II
2
5009-08
Fastrand II control unit
2
900-06
Communications terminal
module controller
2
755-00
Printer
2
8120-02
Printer control
2
2010-06
1004 11-06 card processor,
reader, punch, & printer
2
597-02
494/1004 adapter unit
2
2009
Card punch
2
7304-01
F11-880 drum
2
8103-03
F11-880 drum control
2
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
Included as supplemental information are hardware specifications for
remote devices which will be connected to the computer complex during
system implementation. Although these hardware specifications are
sufficiently detailed for proposal purposes, they are not to be con-
sidered final. These remote devices will be connected via the MIVAC
Standard Communication Subsystem.
The software system consists of an executive (RUM), a generalized
real-time program (ART), and an assembly system (SPRYF) developed by
the US Government. The RUM Executive System is a mul.tiprogramnied
operating system actuated by interrupts. The interrupts are e:.ther
processed or logged for later processing before control is returned
to the interrupted activity. RUM handles all normal executive serv-
ices and communication interrupts, lists them, and passes control, to
the proper real-time service routines. Only real-time programs; are
allowed to converse with a given remote station, except for privi-
leged IIS batch programs authorized to use Send-and-Receive opera-
tions. These operations will be implemented by the Government during
the IIS development.
The combined services of RUM and ART are referred to as the RYF.
Executive System which provides the following services:
a. Automatic scheduling and loading of programs
b. Staging of remote input and output on mass
storage
c. Logging of CPU activity
d. Conversation between remote stations and special
application programs
e. Standard peripheral interface handlers
For example, a customer initiates a request from a remote station for
a particular program by inputting his request and data on an A;R--35
teletype or other remote device. The request for a program and
associated data will be queued on a Fastrand drum. When the customer
indicates that he is finished sending all the associated data, the
program will be placed on the scheduling queue. The queue is -~eriod-
ically examined to determine which program is to be loaded next.
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
The following factors specify this determination: (a) core require-
ments; (b) the ratio of input/output to computer time; (c) peripheral
requirements; and (d) priority.
Once the program has been loaded and logged, it will access its
data by requesting RYE input.* As requested by the batch program,
RYE will retrieve the data from the drum. The batch program processes
the data and may also output the processed element through RYE. If
output is required, RYE will accept the data and store it on the drum
until an end-of-message is received from the hatch program. RYE will
transmit the data to the customer at remote-station speed when the
device is free. Core and facility requirements of the hatch program
are released upon its termination even though the output has not been
transmitted to the remote station.
Facilities located in the computer room may be accessed directly
by using device-level input/output (RYE file control). Details on
the use of and the restrictions regarding RYE may be found in the
attached RYE manual.** Send-and-Receive concepts described in the
RYE manual are accurate. However, significant modifications will be
made to the Send-and-Receive functions so that provisions for IIS
remote-device requirements (i.e., the volume restrictions and time
constraints will be increased and/or upgraded) will he adequate.
The initial development of the IIS envisaged an additional real-
time program (RT/3) which would service the needs of the program
packages and accommodate up to three worker packages at one time. If
this concept had been used, each package would have been designed to
handle many remote stations. After analyzing this concept, the
Government decided to modify the RYE system to allow special worker
programs to converse with an individual remote station. This was
accomplished by allowing the program to reside in core and request
information from (RECEIVE) and send output to (SEND) a remote station.
This data is intermediately staged on secondary storage by the RYE
system. This choice simplified the design of the IIS application
programs but required that multiple, time-shared copies of the pro-
gram be core resident in a time-shared capacity at any given time.
However, the advantages gained in following the existing RYE phi-
losophy, the savings in design and programming, and the redundant
* Special Send-and-Receive operations will provide conversational re-
quirements.
**NSA, RYE - 494 PROGRAMMER'S REFERENCE MANUAL, September 1966,
UNC ED.
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
functions existing between the real-time programs warrant the use of
the small amount of additional core storage.
Although the program specifications do not reflect this change,
they are entirely satisfactory in scope and detail for RFP purposes.
All references to RT/3 services will be replaced by Send-and-Re,:eive
implementation and/or assigned to other program packages such as file
control, which will be written by the Government. The finalized
versions of the program specifications will he available during the
development of the work statement by the selected contractor but will
not change the scope of the effort.
The computer program packages of the ITS support the following
functions:
1. Data Entry (DEN)
Accepting input data from various types of equipment
(keyboard, card reader, CRT, etc.), error checking, and coli-
version and formatting of the data for further processing.
2. Verification, Editing and Approval (XTA)
The retrieval, display, and modification of data in
response to commands from consoles manned by verifiers, editors,
and an approving authority.
3. Query Handling (PIRL)
The decoding of a user-oriented query language (P[RL)
and the retrieval of desired sets of information from the data
base.
4. Report Generation (RPG)
The automatic generation of hard-copy reports from
information stored in the data base and/or work file.
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
5. Presentation Language (PRES)
The processing of an on-line language which permits a
user to change or create output formats.
6. File Update and Maintenance (AUD)
The creation of sectors of data, the addition of data
to, and the deletion of data from the data base.
7. Installation Prediction (PRED)
The selection of installations prior to preparation
of reports.
8. Assignment (ASGN)
The assignment of film and necessary materials to
photo interpreters prior to the preparation of reports.
9. Executive (RYE)
The control of the entire system is accomplished by
a real-time program and an IIS file control program operating
under the RUM Executive System.
The first five packages specified above are being offered for con-
tractor bidding and assistance. The remaining four packages and the
remainder of the system and the environment will be implemented by
the Government.
The diversity of activity associated with the HS requires care-
ful planning so that the various modules will be phased in or imple-
mented in an orderly fashion. Constraints resulting from such
planning will affect the duration of the programming effort and the
manpower loading and consequently the economics involved. For RFP
purposes, the completion date for packages 1 through 4 is estimated
to be 1 July 1969. The completion of the Presentation Language
package may be deferred for up to six months after 1 July 1969. It
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
must be emphasized that. these dates constitute no more than estimated
time frames within which various programming packages must be develop-
ed, tested, and documented. These packages, or portions thereof, will
be required as phases of the implementation evolve.
During the development of the work statement, the Government will
provide to the selected contractor, a Critical Path Method (CPN)
listing of the implementation plan for the ITS. During this time,
specific dates for the delivery of packages 1 through S will he deter-
mined. The updated CPM and written progress reports, which will be
submitted on a scheduled basis, will constitute a requirement for a
contractor's progress report.
GOVERNMENT PROVISIONS AND RESPONSIBILITIES
Although many details will be discussed and negotiated in
connection with the formulation of the work statement, which w'.11. be
developed after the selection of a contractor, Government support of
the contractor's work will he specified in this portion of the Request
For Proposal.
Because the system configuration and operating environmen?. are
unique, our facilities will be made available to the contractoT? for
the necessary testing and implementation of that portion of tho
system for which he is primarily responsible. The Government will
provide, at no cost to the contractor, the necessary computer time
for assemblies of all IIS-related programs the contractor develops,
including all related equipment (such as magnetic tapes for soi.1rce
and object program libraries, paper stock for listings, etc.). Addi-
tionally, all available data for program maintenance and debug aids
in production status or to be developed by the Government will be
documented and made available to the contractor. The Government in-
tends to provide a minimum of three time periods per week for the
assembly of all related ITS programs. If activity warrants, this
time can be increased, but assemblies will not exceed one per day.
All contractor keypunching requirements, including provisions
for 80-column cards, will be the responsibility of the contractor,
except that a keypunch machine and working area will be available at
the Government installation for the preparation of a small volume of
test data, correction cards, etc. Necessary supplies (coding sheets,
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
25X1A
cards, paper, desks, etc.) will be provided for the contractor's
convenience, particularly during the test and debug phase. Under no
circumstances, however, is this working area to be used by the con-
tractor for flow charting, coding, or documentation activities. This
area will also be equipped with one ASR-35 and one CRT console which
will be made available to the contractor.
It is the Government's intention to charge the contractor for
computer test time at (in units not less
than one-half hour or more than tour hours). is time will he made
available to the contractor at least twice a week (if this time is
needed) at a mutually agreeable time. Essential operating personnel
will be provided. It is anticipated that this time will be used by
the contractor for component tests to determine whether acceptance
specifications for the production of end items (Category I testing)
have been complied. with. As part of Category I testing, the con-
tractor will be required to provide and/or develop all test files,
test plans, and test input necessary to assure himself and the
Government that Category I testing is complete. Because some hard-
ware (such as CRT devices) and Government-supplied software (such as
file control and test files) are unavailable, the necessary simula-
tion will be the responsibility of the contractor. However, as part
of the Government's responsibility, all necessary and related hardware
and software will he made available to the contractor, documented,
and site tested by 1 ,July 1969, so that Category II testing can
continence no later than 1 July 1969.
Category II testing consists of subsystem tests to evaluate
combinations of equipment, programs, and files which will provide a
specific capability. It is the responsibility of the Government to
design criteria, execute and evaluate Category IT tests, and make
available to the contractor the results of the evaluation. The con-
tractor will be responsible for taking the required corrective action.
CONTRACTOR RESPONSIBILITIES
While we recognize that the specifications for the program
packages, associated files, and program interfaces cannot be con-
sidered final, we want to emphasize that the basic functions to be
performed and the related file structures will not he subject to
major modifications. The Government will not change the ITS
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
philosophy. Therefore, the existing specifications and other :infor-
mation regarding contractor requirements make it possible for a
contractor to bid realistically on this Request for Proposal.
First, the Government will require an implementation plan and
schedule of the CPM/PERT type, which will indicate the plans and
philosophy the contractor would use if he were selected for this
project. Significant events must he frequent enough so that this
schedule will he an effective tool for monitoring the implementation
of the contractor's segment of the ITS.
Particular attention should be given to the documentation
required to satisfactorily complete the contract. Requirements for
documentation are specified in the attached Standards Manual with
one exception: documentation need not he provider. .or a user.
Secondly, in the final work statement to he negotiated with the
selected contractor, the Government intends to furnish to the can-
tractor finalized job specifications, precise file formats, detailed
interface requirements, and restrictions that circumscribe programs.
However, the level of program specifications included in this RAP
will not be more detailed than it is at present. For this reason,
one of the contractor's initial deliverable products will he a
written, more detailed specification for each major task. This
nroduct will be submitted to the Government before the contractor
begins coding. Each of these specifications must he reviewed and
approved by the Government. While we recognize that time and know-
ledge preclude the development of detailed specifications in response
to this RFP, the work involved should he considered in the cost and
manpower information in your proposal.
Thirdly, as part of the final development of the contractec.
program packages, the contractor must provide the items listed }-,elow.
1. Detailed job specifications (cf. Standards Manual)
including the following:
a. size of the program and time estimates
b. error diagnostics and recovery techniques
c. acceptance test plans through Category I
testing
d. secondary storage and allocation require-
ments
e. macro flow chart or diagram
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
2. Micro flow diagrams
3. Programming (including coding and assembly)
4. Testing
5. Finished documentation
These items must be detailed in the work statement.
Although it is not required, the submission of an initial CPM
as part of the response to the RFP is desirable. Also helpful in
your response to the RFP would be approximations regarding the
following:
1. Manning or man-hour estimates for each program
package to be contracted.
2. Estimates of the amount of computer test time
that will be required for each program package
Although every individual associated with the implementation of
the IIS program will probably not require a TOP SECRET security
clearance, the contractor's project manager and perhaps one or two
senior analysts and/or programmers will doubtless need such clearances.
Please indicate those employees who have clearances and specify the
types of clearances they hold. Please submit the names of uncleared
employees who might he assigned to the project.
Since the primary purpose of this Request for Proposal is to
obtain contractual personnel who are highly qualified and experienced,
a formal training program to familiarize the contractor with equip-
ment configuration and operating environment will not he required.
However, orientation and familiarization meetings, spread over a
maximum of one week, will be provided. In response to this RFP, we
request that you include a short outline of the topics that you
would like covered and/or emphasized.
Again, we would like to emphasize that the job specifications
accompanying this RFP are primarily for information and estimative
purposes. Suggestions, potential problem areas, and even a modified.
or different approach are welcome, provided that the impact does not
radically change the IIS design goals and concepts. These factors
may be included in your response to the Request for Proposal.
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
Although we do not intend to underestimate the importance we
place upon cost, we must indicate that cost will not he the on:Ly
criterion used in the selection of a contractor. Many considerations
will enter into our evaluation of your proposal. Of great importance
will be the level of experience and the technical qualifications of
those who will be assigned to the implementation of the system, which
includes the preparation of detailed job specifications and the actual
programming, testing, and documenting. This experience and technical
expertise should he presented in the form of brief resumes which will
summarize the background of those you intend to assign to the project.
Particular emphasis should be given to the project leader or manager.
Documented evidence of previous successes and customer satisfaction
in similar or related activities would also be helpful.
As indicated previously, the system will be implemented on a
UNIVAC 494 computer and its peripheral equipment. The periphe:al
equipment will consist principally of random-access mass storage with
-emote terminals ranging from KSR-35's to medium-sized CRT devices,
;,ii of which have capacities similar to the DIDS-400 or UNISCOPE-?300.
SPRYE, the programming language to be used, is similar to SPURT, the
assembly language developed for the UNIVAC 490 computer system,
l.imiliarity with this language and/or equipment is undoubtedly advan-
tigeous. However, more importance will be attached to a demon:;trated
ability to implement similar systems on a large-scale, word-oriented,
remote-access and random mass storage computer complex where the
1,in-t:age used is an assembly type rather than a compiler such as COBOL
or FORTRAN.
It is expected that the executive system provided by the
(,t.voornment will satisfactorily remove the problems of time-cri':ical
remote input and output. Therefore, particular knowledge or s-:rength
i.i this area will receive no additional consideration nor will special
importance he attached to it. Essentially, the contractor will have
the problem of developing sophisticated application packages that will
function as time-shared or multiprogrammed batch programs that accom-
plish a given function, at a given time, and with a given remo--e
terminal. During the evaluation process a great deal of emphasis will
be placed on previous contractor performances in similar application
areas and on individuals who will. be assigned to this project and who
are technically qualified in the same areas.
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
SPECIFICATIONS
FOR
CONTRACTOR'S CONSIDERATION
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002(A.9LDA -~IA-RDP78B04747AO01900050003-SCR 352
INTEGRATED INFORMATION SYSTEM (IIS)
8 February 1968
Approved For Release 2002/0~l~RCL-RDP78BO4747AO01900050003-4
 C`H 352
Approved For Release 2002/ IA-RDP78B04747A001900050003-4
ti
S
Page
on
ec
1. SCOPE
1
2. APPLICABLE DOCUMENTS
1
3. REQUIREMENTS
1
4. VE:A PROGRAM FLOW DIAGRAM
15
Table Page
1. Data Format for Location VEAIN
II. Command Structure
Page
Figure
VEA PROGRAM INTERFACES
1
10
.
2. VEA PROGRAM FLOW CHART
16
Approved For Release 2002/09/0E 6rDC
A-RDP78B04747A001900050003-4
 Approved For Release 2002/0 Cl ,-RDP78BO4747AO01900050003-4(.,p 352
VEA PROGRAM SPECIFICATION
This specification describes the programming necessary to assist in
the verification, editing and approval of data entered into the system by
manual or automatic techniques and intended for eventual entry into the
National Data Base and/or for inclusion in output products. The program
utilizes a Working File as a source and repository for records in process
and the Queue and Status Lists as an index to the location and current
processing status of records in the Working File. The program controls
the transmission of these records to a VEA console for review and-modifi-
cation and the return of these records from the VEA console and to the
Working File. It should be noted that the VEA program is not responsible
for actual modification of the displayed information. This function is
carried out wholly within the console itself.
2. APPLICABLE DOCUMENTS
Status List/Queue List/Working File Specification (PS-1)
IIS Real Time/3 Specification (SS-9)
PIRL Program Specification (SS-4)
File Control Program Specification (SS-12)
RYE-494 Programmer's Reference Manual
3. REQUIREMENTS
3.1 Functional Requirements
This program shall have the capability to locate records in the Work-
ing File via the FCL program; prepare sections of these records for display
on a console; accept, as reviewed, portions of these records returned from
the console; initiate transfer of reviewed records back to the Working
File via FCL; temporarily store data returned from the console for such
purpose; update certain status information in the Queue List via FCL, and
perform the other functions described below.
3.1.1 Locate Records in the Working File
The VEA Program shall have the capability of locating records in the
Working File in both of the following modes:
(a) The VEA Program shall input to the FCL program
the MRN supplied as program input (3.2.1) to
determine the address parameters of the desig-
nated record in the Working File.
Approved For Release 2002/09/04EIIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4 SCR 352
SECRET
(b) The VEA Program shall interrogate the Queue List
to determine the next record on the basis of con-
sole type and category group, record status and
category, and record priority information in the
Queue List (see 3.6.1) and then determine from
the Queue List the starting address of the next
record.
If there is no record that meets the necessary conditions the VEA
Program shall prepare, in accordance with the Section 3.1.2.2a, t, and
Section 3.2.2, a message that says, ''RECORD ddddd IS NOT AVAILABIE." When
the record address has been determined, the VEA Program shall prepare, in
accordance with Section 3.1.2.2a, b, and Section 3.2.2, a message that
says, RECORD NUMBER ddddd IS AVAILABLE" (where ddddd is the machine
reference number of the record located) and shall update the Quei.e List to
indicate that record ddddd is in process.
3.1.2 Prepare Data for Display
3.1.2.1 Modes. - The VEA Program shall have the capability of
delivering sections (as identified in the Working File Specification (FS-1))
of the record located as a result of the function specified in 3,1.1 in
the following modes:
(a) The VEA Program shall retrieve from the Working
File and prepare for display, the section of the
record corresponding to the number supplied as
program input (3.2.1.).
(b) The VEA Program shall retrieve from the Working
File and prepare for display the section follow-
ing the section most recently displayed. If no
sections of the record most recently located have
been displayed, this function shall be interpreted
to display the first section. If the section most
recently displayed is the last section in the
record, the VEA Program shall prepare a display
message in accordance with 3.1.2.2a, b, and c(l)
that gives each section designator and indicates
whether or not reviewed data has been received for
each section (see 3.1-3)-
(c) The VEA Program shall retrieve from the returned
data (see 3.1.3) and prepare for display, the
section of the record corresponding to the number
supplied as Program Input (3.2.1).
Approved For Release 2002/09/04 Skhel* P78B04747A001900050003-4
 Approved For Release 2002/n_QMA &A-RDP78BO4747AO01900050003EWR 352
SEU
3.1.2.2 Display Format. - In either mode, the VEA Program shall
generate a display message containing the section identified in 3.1.2.1 and
meeting the following conditions:
(a) The message shall be equal in length to the number
of characters per line (N) times the number of
lines on the console display as given in the Table
of Console Characteristics for the console to
receive the display.
(b) The first N characters shall be blanks.
(c) The second N characters shall contain:
(1) The machine reference number of the record
from which the section is taken;
(2) The section numeric designator; and
(3) The section name as given in the Working
File.
(d) If the section contains more than one field, each
field shall start at a character position which is
an integral multiple of N plus one.
(e) All character positions that do not contain data
characters shall contain blank characters. A space
character shall be considered a data character.
(f) At least the last 2N characters shall be blank.
If the section would otherwise use part or all of
the last 2N character positions the procedure of
Section 3.1.6 shall be used.
3.1.3 Receive Reviewed Data
The VEA Program shall receive, as Program Input, data which has been
reviewed at a console. The number of data characters in the returned data
may be equal to, less than, or greater than the number of data characters
in the display message generated (3.1.2). The VEA Program shall use this
returned data to generate a revised record for later insertion in the Work-
ing File. If data for a given section is returned more than once, the VEA
Program shall use the data returned last in generating the revised record.
The VEA Program shall terminate this portion of its operation by trans-
ferring to one of the following, dependent on the Command Statement
received as part of the program input (3.2.1)
SS-2
SECRET
Approved For Release 2002/09/04: IA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4 SCR 352
SECRET
(a) Prepare data for display in accordance with 3.1.'?,
mode a
(b) Prepare data for display in accordance with 3.1.2"
mode b
(c) Transfer back to the'RT/3 System; no display is
required.
3.1.4 Return Records to the Working File
When all sections of a record have been reviewed, an "Update Status
Information" command will be received as part of the Program Input and the
VEA Program shall do the following:
(a) Assemble the returned sections (3.1.3) into a revised
record for reentry into the Working File. The sec-
tions shall be in the same order and format; as in the
original record and all command statements, the
identifiers added by 3.1.2.2c, and any blank charac-
ters added to format and/or fill out the display
message shall be deleted.
(b) Inform the FCL Program of the total number of
characters and request a new starting address in the
working File if the number of characters in the
reviewed record exceeds the original number by more
than one hundred.
(c) Initiate an update of the Queue List entry for tha
record just reviewed by: (1) changing the status
symbol to reflect the type of console that just
completed reviewing the records; (2) changing the
indicated starting address of the record in the
Working File if required by (b) above; (3) changing
the process status to indicate not-in-process; (4+)
informing the FCL Program of the location in co:?e
storage of the revised Queue List Entry; and (5)
requesting the FCL Program to enter the revised
entry in the Queue List.
(d) Initiate the return of the revised record to the
Working File by: (1) informing the FCL Program
of the Working File address for the record and the
storage location of the revised record; and (2)
requesting the FCL Program to make the transfer,
Approved For Release 2002/09/045 A TDP78B04747A001900050003-4
 Approved For Release 2002/091p4.RGf-RDP78BO4747AO01900050003-4 CR 352
The VEA Program shall terminate this portion of its operation by
transferring to one of the following dependent on the Command Statement
received as part of the Program Input:
(a) Locate a record in accordance with 3.1.1, mode a
(b) Locate a record in accordance with 3.1.1, mode b
(c) Transfer back to the RT/3 System; no display is
required.
3.1.5 Temporarily Store Displayed Data
The VEA Program shall have the capability of receiving a display mes-
sage that is returned from a console for temporary storage and holding it
until a Program Input is received requesting its return.
3.1.6 Partial Display of Sections
If part of a section display that is being generated in accordance
with Section 3.1.2 would otherwise occupy part or all of the last 2N char-
acter positions of the display message (see Section 3.1.2.2.f), the VEA
Program shall truncate the section so that the last 2N character positions
remain blank. The VEA Program shall also place in the first line of the
display message a command statement for displaying the remainder of the
section. The command statement shall include an operand that indicates the
number of lines of data from the bottom of the partial display of the sec-
tion that are to be repeated at the top of the next partial display of the
section. When a Program Input is received with this command statement, the
VEA Program shall hold the data characters and shall generate a display
message containing the next partial display of the section and meeting the
conditions (a) through (f) of Section 3.1.2.2. When the last of the partial
displays of a section has been received as a Program Input with the command
statement indicating that display review is completed, the VEA shall
assemble the data characters from the partial display messages in the
proper sequence and continue in accordance with the requirements of 3.1-3-
3.1.7 Remove Bottom of Display
The VEA Program shall have the capability of removing a number of
lines from the bottom of a display message appearing as a Program Input and
generating new display message with the remaining data. This display mes-
sage shall be considered a partial display message and it shall be generated
and handled in accordance with the requirements of Section 3.1.6. The data
removed shall be held and included in proper sequence in the next partial
display of the section. The number of lines of data to be removed shall be
determined from the operand of the command statement in the Program Input.
SS-2
Approved For Release 2002/09/04EIIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4 SCR 352
SECRET
3.1.8 Use of Secondary Storage
The VEA Program shall. use blocks of secondary storage for hcldLog
returned data prior to their being returned to the Working File as reviewed
ci to (3.1.3), temporarily stored data (3.1.5), partial displays cf sections
and such other data and information that can be conveniently stored
it ,ceondary storage. The VEA Program shall keep track of the lccation of
data and information within these data blocks and shall initiate transfer into
and out of them in accordance with Section 3.2.4. The VEA Program shall
contain procedures whereby the requirements for core storage are minimized
to the extent practical by the use of secondary storage and the requirements
for secondary storage are minimized to the extent practical by returning
blocks of storage when they are no longer needed by the VEA. Program.
3.1.9 Status Display Request
The VEA Program shall process commands from the approver console in
order to create messages for displays that (1) relate the total system
status for this mission by providing information on the total nwiber of
MRN's that were predicted, entered, verified, edited, and approved or (2)
relate the unique status of any given MRN, i.e., entered, verified, etc.
3.1.9.1 System Stati.zs . - Upon receipt of the command "STh--?---" the
VEA Program shall tabulate the status counts in the Queue List by:
(a) Total number of MRN entered
(b) Total number of MRN verified
(c) Total number of MRN edited
Further, the VEA Program shall request the FCL Program to retrieve the
status list from drum storage and again tabulate total number of MRN's for
the following status:
(a) Predicted.
(b) Approved
The approved status count shall be further subdivided to show four
status counts by type, i.e.,
Approved For Release 2002/09/04 SAh. I4DP78B04747A001900050003-4
 Approved For Release 2002/ lA-RDP78B04747A00190005000 4R 352
To-Lai Number of MRN's = BONUS
Total Number of MRN's = Predicted not covered
Total Number of MRN's = Cloud Covered
Total Number of MRN's = Approved
The above status counts shall be calculated for three report types
(A's and B's), (C's), and (P's). The VEA Program shall then produce a dis-
play message in the following format:
Line +1 SYSTEM STATUS
PRED DDDD
ENT DDDD
VER DDD
EDIT DDD
APPR B DD
NC DDD
CC DDD
T DDDD
PRED DDDD
ENT DDDD
VER DDD
EDIT DDD
APPR B DD
NC DDD
CC DDD
T DDDD
PRED DDDD
ENT DDDD
VER DDD
EDIT DDD
APPR B DD
NC DDD
CC DDD
T DDDD
R
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4 SCR 352
SECRET
3.1.9.2 Unique Status of MRN. - Upon receipt of the input message
"STA ddddd" the VEA Program shall first search the Queue List for the
appropriate MRN. If the MRN is located in the Queue List, the VEA Program
shall decode the individual status code, i.e., status entered, verified,
edited or approved, and prepare the following message:
"MRN ddddd STATUS - LLLL
Entered = ENTR
Verified VERI
Edited = EDIT
Approved = APPR
If the MRN is not located in the Queue List, the VEA Program shall
request the FCL program to retrieve the Status List. Again the VEA Program
shall attempt to locate the MRN in the Status List. If it is fcund it will
be processed in the same manner as the Queue List entry. If no MRN is
located in either the Queue List or Status List, the VEA prograrr shall pro-
duce the following message:
"MRN ddddd STATUS - NULL
3.1.10 Disapprove Report
The VEA Program shall accept as an input message a command message to
signify disapproval and also the status to set the report, i.e., return the
status back to (1) edit, (2) verify, (3) enter, or (4) predicted. The
input message is of the following format:
"DIS LL"
where LL is defined as follows for status back to:
(a)
Edit =
ED
(b)
Verify =
VE
(c)
Entered =
EN
(d)
Predicted =
PR
When LL = ED,
VE, or EN, the VEA Program shall change the status indicator
in the Queue
List to equal the new status. If LL== PR, the VEA Program
shall remove
the entire entry from the Queue List.
3.1.11 Number of Consoles
The VEA Program shall be able to accomplish the requirements above for
Approved For Release 2002/09/04 SEQROP78B04747A001900050003-4
 Approved For Release 2002/TftaA-RDP78BO4747AO01900050003?4R 352
twenty-four VEA consoles that are being used simultaneously. Each console
will be only concerned with one record at a time and no two consoles are
concerned with the same record at the same time.
3.2 Interfaces
The interfaces between the VEA Program and the rest of the system are
shown on Figure 1. Program Inputs originate at the VEA consoles and are
transmitted to the VEA Program by the RT/3 Program. Display messages are
generated by the VEA Program and transmitted to the VEA consoles by the
RT/3 Program. Access to all system files and the block of secondary
storage assigned to the VEA Program is obtained through the File Control
Program, or the RT/3 Program.
3.2.1 Program Inputs
When the VEA Program is to operate, the RT/3 Program shall transfer
to the starting location of the VEA Program and provide the starting loca-
tion of the Program Input data from the console and the console identifica-
tion. This information will be the format shown in Table I. The first
line of the Program Input will contain a command code (the first three
letters being VEA) and, if applicable, a command operand to designate which
of the functions of Section 3.1 shall be performed. The codes and formats
for these commands will be as shown in Table II.
Data Format for Location VEAIN
Word
Content
0
Transfer to VEA Program
1
Core address of input data string
2
Number of words of input data
3
V, E, or A console selection
(bits 29-24+)
Identification of input console
(bits 23-0)
Approved For Release 2002/0994C:" D1A-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET 13CR 352
K QUEUE
LIST
FILE
CONTROL
PROGRAM
VEA
CONSOLES
RT/3
PROGRAM
'ASSIGNED
SECONDARY
-,STORAGE ,
Approved For Release 2002/09/0i~~B. DP78B04747A001900050003-4
 Approved For Release 200?/? /KpClA-RDP78B04747A00190005000d4 352
Table II
Command Structure
Section Ref
Command Code
Char. Pos. 5-7
Operand
Char. Pos. 9-13
3.1.la
3.1.lb
3.1.2.1a
3.1.2. lb
3.1.2.lc
3.1.5
3.1.5
3.1.3a
3.1.3b
3.1.3c
3.1.4a
3.1.4b
3.1.4c
3.1.6
3.1.7
3.1.9.1
3.1.9.2
3.1.10
Retrieve Record N
Retrieve Next Record
Display Section N
Display Next Section
Display Returned Section
Store Display Temporarily
Retrieve Stored Display
Display Review Completed
Display Review Completed
Display Review Completed
Update Status Information
Update Status Information
Update Status Information
Continue Section Display
Remove Bottom Lines
System Status
MRN Status
Disapprove Report
*d = a decimal digit
- = indeterminate
s = space
1 = letter
ddddd
NEyT-
dd---
sssss
ddddd
11
Approved For Release 2002/09 t 4 : 91-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
SCR 352
3.2.2 Display Message
The VEA Program shall initiate the transmission of a Display Message
to a VEA console by transmitting a calling sequence as described in the
IIS RT/3 specification (SS-9).
3.2.3 Files
The description of the content of, and the procedures that shall be
used to obtain data from, the three Systems Files used by the 7EA Program
are described in the "Status List/Wait List/Working File Specification"
(FS-1).
3.2.4 Secondary Storage
The method of transferring data to and transferring data from second-
ary storage shall be as described in "IIS RT/3 Specification" (SS-9).
3.2.5 Other Communication with the Real Time 3 Program
The VEA Program shall be subject to the control procedures described
in "IIS RT/3 Specification" (SS-9).
3.3 Diagnostics
3.3.1 Checks on Program Inputs
The VEA Program shall check each of the Program Inputs and if any of
the following conditions are noted, an appropriate display message shall
be generated and its transfer to the console initiated:
(a) illegal command statement including operand
(b) request for a record for which the machine
reference number is not in the Wait List
(c) request for a record for which the status code
in the Queue List is not one level below the
requesting console type (see 3.6.1)
(d) request for a record for which the category
code in the Queue List does not equal one of the
category codes listed for the requesting console
(see 3.6.1)
(e) request for a record that is already in process
(see 3.6.1)
Approved For Release 2002/09/9TRDP78B04747A001900050003-4
 Approved For Release 2002/0.w44, CJA-RDP78B04747AO01900050003U1R 352
all
(f) request for data display (3.1.2) when the most
recently located record (3.1.1) has already been
returned to the Working File (3.1.4
(g) request for display of a returned section (3.1.2c)
when data for that section has not yet been returned
(h) a second request to restore displayed data temporarily
before data stored on first request has been
retrieved (3.1.5)
(i) request from a console to locate a record (3.1.1)
when that console has already located a record (3.1.1)
that has not been returned to the Working File (3.1.4)
(j) request from a console to receive data (3.1.3) when
that console has not been sent data that-can be returned
(k) request from a console to receive new sections of data
(3.1.3) before all partial displays of a current section
(3.1.6 and 3.1.7) have been sent to the console
(1) request for displaying the remainder of a section
(3.1.6) when there is no partial display that has
not been displayed
(m) the machine reference number or section number on a
display being returned from a console is not the
same as it was in the display message most recently
generated for that console.
3.4 Storage Allocation
Approved For Release 2002/0 899A A-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4 SCR 352
SECRET
3.4.1 Working Storage Allocation
3.4.1.1 Drum Storage Allocation. - The VEA is provided cnly drum
working storage on the FH880, FH432 or FH1782 through a RT/3 request (see
RT/3 specification for calling sequence). The maximum drum working stor-
age allocated to the VEA Program shall be 14,760 drum words.
3.4.1.2 Core Storage Allocation. - Maximum core working storage is
allocated 1,000 computer words.
3.5 General Design Features
3.5.1 Programming Language
The VEA Program shall be coded in the SPRYE Assembly Language.
3.5.2 Flexibility
The VEA Program shall be coded in modules by at least 10 major pro-
gram functions corresponding to the functions of Section 3.1.1 through
3.1.10. If a function is not initially implemented, the controL necessary
to operate a "dummy" module shall be included in the program. i Then this
dummy module is executed, a display message shall be generated that indi-
cates that this operational function is not yet available in the IIS.
SS-2
3.5.3 Recovery Procedure
If the VEA Program is unable to fulfill an operating request because
of machine error, the VEA Program shall initiate a display message request-
ing the VEA operator to re-enter the machine reference number and restart
the review of the record.
3.6 Required Techniques
3.6.1 Determination of Next Record
In determining the next record as required by the mode b o' 3.1.1,
the Program shall find the highest; priority record in the Wait :'ist that
meets the three following conditions:
(a) The record category code in the Queue List is the
same as one of the category codes for the conso:_e
requesting the next record.
Approved For Release 2002/09/045k R. TDP78B04747A001900050003-4
 Approved For Release 200219$/p~E?IA-RDP78B04747A001900050003S~R 352
(b) The record status in the Queue List is one level
below the console type for the console requesting
the next record. (The order of record status
entries from top to bottom is Approved, Edited,
Verified, Entered).
(c)
The process status given in the Queue List for the
record is in the "not-in-process" condition.
4. VF,A PROGRAM FLOW DIAGRAM
Figure 2 represents the program flow logic of the functions in
Section 3.1.
SS-2
Approved For Release 2002/UJ/0~ECIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
IDENTIFY
SOURCE OF
INPUT DATA
STRING
MOVE INPUT
DATA TO
WORKING
BUFFER
REQUEST
LTO GET
HER. MRN
DATA
UPDATE
CIRCUIT
HISTORY
TABLE
REQUEST
RT/3 TO
TRANSMIT
MESSAGE
FORMAT
REQUEST
FOR CIRCUI
HISTORY TBL.
GENERATE
"RECORD NOT
AVAILABLE
DIAGNOSTIC"
REQUEST
TR/3 TO
TRANS. HIS
REQUEST
RT/3 TO
LOAD HIST.
TABLE
GENERATE
'RECORD COULD
NOT BE READ"
FORMAT FORMAT
REQUEST REQUEST
TO LOAD TO LOAD
SE3. YEA 5 SF. VEA 6
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
REQUEST
RT/3 TO
SEND ERROR
AIAGNOSTIC,
GENERATE
"PREVIOUS
DISPLAY
INCOMPLETE"
ASSIGN
TEMP. FILE
ADDR. TO
STORE DEC.
GENERATE
"ILLEGAL
INPUT CODE"
MESSAGE
REQUEST
RT/3 TtC
SEQMENT
 START
SEGMENT
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
COMMAND
VALID
/ALL
SECTIONS
DISPLAYE
FORMAT
FOR DISPLAY
OUTPUT
/REQUEST
RT/3 TO
PUT TAIL S
ON DRUM
YES
FORMAT
lllAlilV
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SCAN FOR
APPROPRIATE
SECTION OF
RECORD
NOTE
SECTIONING
IN HISTORY
REQUEST
RT/3 TO
F4NS.HIST.
O DRUM /
FORMAT
FOR DISPLAY
OUTPUT
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
START
SEGMENT
SEGMENT
IN TEPE.
FORMAT
RETRIEVAL
APPEND
ERROR
DIAL. TO
CURB. DISPLAY
REQUEST
RT/3 TO
ENTER DATA
FORMAT
ERROR
DIAGNOSTIC
DETERHIN.E
DRUM
STORAGE
ADDRESS
END
SEGMENT
vEA 4
UPDATE
HISTORY
TABLE
" Ic
OPERAND
dd ?
OPERAND
BLANK
REQUEST
BT/3 TO
WRITE HIST.
TABLE /
CHANGE COM-
NA D TO
DISPLAY
SECTION T,
CHARGE
OMMAND TO
DISPLAY
NEXT SECT.
END
SEGMENT
YEA 3 ,
UPDATE
HISTORY
TABLE
FORMAT
REQUEST TO
LOAD
SEC. EA 2
UPDATE REQUEST / REQUEST
HISTORY RT/3 TO RT/3 TO
TABLE OH DRUMIST \SEGMENTQ
SEGMENT
YEA 4
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
FORMAT REQ-
UEST TO SAVE
INPUT IN
TEMP. BUF.
REQUEST
RT/3 TO
TRANSMIT
DISPLAY
 SEGMENT
~VEA 5
STATUS
INFO.
SYSTEM
STATUS
ERROR
FORMAT
ERR
STATUS
EXAMINE
HISTORY
TABLE FOR
ISCREPANCY
REQUEST
RT/3 TO
READ STAR
STATUS L
FORMAT
ERROR
DIAGNOSTIC
COMMAND
VALID
FORMAT
ERROR
DIAGNOSTIC
TABULATE
DATA FROM
RECORD N
INITIALIZE
TO EDIT
ALL SECT.
OF REPORT
FORMAT
REQUEST TO
PLACE REC.
IN WF.
IS
OPERAND
ddddd
IS \
OPERAND
NEXT .
GENERATE
END OF
OPERATION
MESSAGE
UP DATE
HISTORY
TABLE
REQUEST
RT/3 TO
READ IN
SECTION
EDIT AND
BLOCK DATA
WITH ANY
PREY. DATA
REQUEST
FCL TO
CHANGE
STATUS
REQUEST
FCL. TO PUT
REC IN WF
I C??ARGE
1 COMMAND TO
REPRIEVE
RECORD N
1. 1 D-1 Th
HISTORY
TABLE
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
RT/3 TO ~-~ RT/3 SEND
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
REaUEST
RT/3 TO
ON DRUB
OVERFLOW
SFD_NETS
INITIALIZE
TO REGROUP
ALL PIECES
T
READ
PART
IIITO
CORE
REOUERT
RT/3 TO
RETRIEVE
DATA
OVER.VLOW
DATA
EDIT AND
BLOCK DATA
WITH ANY
PREY, DATA
ALL
PARTS
UPDATE
HISTORY
TABLE
FORNAT
DATA FOR
CONSOLE
DISPLAY
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET SCR 352
INTEGRATED INFORMATION SYSTEM (IIS)
8 February 1968
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET SCR 352
Section
1
1.
SCOPE
.
2.
APPLICABLE DOCUMENTS
1
1
3.
REQUIREMENTS
4.
DEN PROGRAM FLOW DIAGRAM
1.2
Table
I Data Format for Location DENIN
Figure
1. DEN PROGRAM FLOW CHART
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
SCR 352
1. SCOPE
This specification describes the programming required to enter a
record resulting from an internally or an externally produced Phase I
report into the automated computer system. All such records (except a
record which indicates that the target was "not-on-film") are entered into
the Queue List and Working File. Records for the exceptional condition
will cause only the setting of a status bit in the Status List. The pro-
gram will incorporate the capability for receiving a record in several seg-
ments (i.e., messages) and outputting the record for the Working File as a
single unit and provide additional services as described in detail in this
specification.
2. APPLICABLE DOCUMENTS
Status List/Queue List/Working File Specification (FS-1)
PIRL Program Specification (SS-4)
IIS Real Time /3 Specification (SS-9)
File Control Program Specification (SS-12)
IIS National Data Base File Specification (FS-2)
RYE-494 Programmer's Reference Manual
3. REQUIREMENTS
3.1 Functional Requirements
This program shall accept formatted input messages from multiple
on-line DEN consoles; determine the message type; reformat the message or
perform a line number free text merge; accumulate single messages to form
an output record; and request record storage in the Working File.
3.1.1 Formatted Input Messages
Each input message will be started by a three character group of the
format $X$. The X character defines the type of message and may be either
numeric or alphabetic. Numeric identifiers will signal the start of a
message set and alphabetic identifiers indicate the message is part of a
subset. There are seven possible numeric message identifiers (1 through 7).
3.1.1.1 Numeric Message Sets. - On recognition of $N$, the DEN pro-
gram shall perform the necessary initialization to begin formatting a
record in accordance with the Status List/Queue List/Working File Specifica-
tion (FS-1) for a Working File entry. Subsequent messages bearing an
alphabetic identifier shall become sequential parts of the same record.
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
When a numeric message is received from a given data entry device and
is recognized as such by DEN, the latter shall interpret the numeric as a
signal to terminate the last record received from that data entry device
and initiate a request that the prior record be added to the Working File
via the FCL (QLWF) element using the "new entry" function code, (Code 1).
In addition numeric messages for targets "off-the-film" will result in a
request for a change in the "target-off-film" indicator in the Status List
by FCL (QLWF) using the "change status list" function code, (Code 9).
In response to Numeric Code 1 message, the DEN program shall format
a "Queue Lis t Entry" in accordance with the QLWF specification. If the
"target-off.-film" indicator is present in the message, a "100" indicator
shall be set in the QL source and status bits and DEN shall terminate the
record. For all other Numeric Code 1 messages the "20" indicator shall be
set in the QL source and status bits and the DEN program shall accept
alphabetic messages as additions to the numerically coded one.
Numeric Code 2 will condition the DEN program to accept only L and H
alphabetic message types. The receipt of an L message will cause a new
QLWF entry to be formatted and the receipt of an H message or a second L
message will cause the record to be terminated and sent to the Working File
via the FCL "New entry" function code. The DEN program will set the 40
indicator in the QL source bits.
Numeric Code 3 will instruct the DEN program to construct a QL entry
with the "100"indicator set in the source bits.
Numeric Code 4+ will instruct the DEN program to construct a QL entry
using a machine reference number of 19999 on a source indicator of "400".
Numeric Code 5 will instruct the DEN program to construct a QL entry
using a machine reference number 99999 with the "1000" indicator set in
the source bits.
Numeric Code 6 shall also create a QL entry with the same machine
reference number, i.e., 99999, but with the "200" indicator set in the
source bits.
Numeric Code 7 shall cause a QL entry whose machine reference number
is 99998 with the "2000" indicator set in the source bits.
3.1.1.2 Alphabetic Message Sets. - Each alphabetic message set is
a subset of a numeric type. The expected format of each set is contained
in Section 3.2.1.1. The subsets are added to the record without change,
reformatted according to Section 3.2.2 or merged as outlined in Section
3.1.4 of this specification.
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET SCR 352
All messages, both numeric and alphabetic, received for numeric types
1, 2 and 3 require format conversion. These numeric types require insertion
of a five character mnemonic, "WHEAD," at the beginning of the message in
the Working File to indicate that the section contains header information.
The appropriate five character mnemonic shall be inserted at the beginning
of all other messages for these three record types to indicate the sector
of the NDB to be updated by the message. In addition, those sections of
the record which are to be used only for updating the NDB, e.g. PI notes,
shall be identified by the insertion of a "U" immediately following the
mnemonic indicator. Those messages which will be included only in an output
message shall be identified by the insertion of an "R" following the five
character mnemonic.
3.1.3 IDF Accesses
The majority of messages bearing Numeric Code 1 and some of those with
alphabetic code B require that the IDF be accessed and that the returned
information be included as part of the program output.
3.1.3.1 Code 1 Type Messages. - Numeric Code 1 type messages which
do not contain a "target-off-film" indicator require some information from
the Header sector of the IDF. Such messages shall cause the IDF Header
sector for the given machine reference number to be requested (via the FCL
element) with the following calling sequence:
WORD 1 Link to QRIN
WORD 2 IDF
WORD 3 Machine Reference Number
WORD 4 Blank
WORD 5 Buffer Transfer Address
WORD 6 Zero Indicator Word
The requested header will be returned to DEN in the format specified
in the IIS National Data Base File Specification. DEN shall then extract
the four fields (Installation Name, Country Code, Geo-Coordinates, and
CCMIREX Number) required for the output message and insert them in the latter.
The "R" following the five character mnemonic section identifier shall be
retained.
3.1.3.2 Type B Messages. - DEN will examine Type B messages to
determine if there is an entry in P2 (see 3.2.1.1 below). If the message
contains such an entry, DEN shall request the extraction of the Brief
Description for the installation from the IDF (via FCL) with a calling
sequence analogous to that for a Type G message (Section 3.1.4). Upon
receiving the requested information, DEN shall insert the five character
SS-1
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
mnemonic "WBRIE" followed by an "R" at the beginning of the retr_eved
information to indicate that it is for the output report only.
3.1.4 Text Modifications
Message Type G requires a merge operation with text obtained from the
IDF. The first two digits of the five digit line number define -,he text
that shall be obtained. These two digits and the sectors to be obtained
are as follows:
First 2 Digits
Sector Name
31
New or
significant
collateral
ICOLL
51
Brief
description
I13RIE
52
Fixed
facilities
IFIXE
53
Changes
ICHAN
61
Notes
INOTE
The DEN program shall determine the required sector from the above
table and request it from the IDF (via the FCL element) with the following
calling sequence:
WORD 1 Link to QRIN
WORD 2 IDF
WORD 3 MRN
WORD 4 Sector Mnemonic
WORD 5 Buffer Transfer Address
WORD 6 Zero Indicator Word
The information will be returned to DEN in the format specified for
the requested sector in the "NDB Specification."
The information extracted from the IDF does not contain line numbers.
DEN shall establish the sequential line numbers by counting; each 25 computer
word group as one line. This determination will allow the changes indicated
in the input message to be made to the retrieved information. The second
parameter (P2) of a type G message will instruct the DEN program to add (A),
change (C), or delete (D) after the given line number using the rariable
length text (P3) for the addition or, change (P3 is omitted on a ])). One
of the following five character mnemonic section identifiers, "W17COL,"
"WUBRI," "WUFIX," "WUCHA," or "WUNOT" shall be inserted as a section
identifier preceding the text resulting from the merge of the retrieved
data and the input message. The section identifier shall be followed by a
"U" to indicate the information will be used only to update the NDB.
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET 5CR 352
3.1.5 Indicators
Message Type B shall set queue list indicators. The parameter/indicator
correspondence table is shown below:
Pi 200
P2 20
P3 100
This message shall not be entered in the working file.
3.1.6 Use of Secondary Storage
The DEN program shall use blocks of secondary storage while assembling
the messages from a given Data Entry Console into a record until that record
is transferred to the Working File (or to the Status List). The RT/3
Program shall inform the DEN program of the starting location and size of
the storage block as described in Section 3.2.5. The DEN program shall
maintain a record of the location of data and information within these
assigned blocks and shall initiate transfer in and out of them in accordance
with Section 3.2.4. The DEN Program shall include procedures which keep
the requirements for core storage at a minimum through the use of secondary
storage and shall also minimize its requirements for secondary storage by
returning blocks of storage when they are no longer needed.
3.1.7 Number of Data Entry Consoles
The DEN program shall have the capability for providing the required
services to ten Data Entry Consoles which may be entering data simultaneously.
Each console shall be used to enter individual records in separate messages
and no two consoles shall enter messages for the same record simultaneously.
3.2 Interfaces
Input messages shall originate at the Data Entry (keyboard only)
Consoles. They are transmitted to the DEN program by the RT/3 Program.
Messages are assembled into records by DEN which also requests the transfer
of the records to the Working File and creation of an entry in the Queue
List or the change of an entry in the Status List via the File Control
Program. Access to other system files and the block of secondary storage
assigned to the DEN program shall be obtained through the File Control
Program.
3.2.1 Program Inputs
The DEN program shall be initialized by RT/3 which concurrently pro-
vides the starting location of the input message from a console and the
SS-1
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
console identification. The format of this information shall be as shown
in Table I. The first three characters of the Program Input cor.sists of a
coded message type in accordance with 3.1.1.
Data Format for Location DENIN
Word
Content
0
Transfer to DEN Program
1
Storage address of input data string
2
Number of words of input data
3
Identification of Data Entry Console
3.2.1.1 Input Message Formats. - Input messages are of either the
coded numeric types 1 through 7 or bear a coded alphabetic indicator which
may be one of the alphabetic characters A through L. The format of the
input numeric type messages and their alphabetic subsets are as follows:
(a)
P2$P3
(EOT )
Item
No. Characters
Content
P1
5
Machine
reference number
P2
c;
Mission
number
P3
1
Target-not-on-film indicator
(EOT)
:L
End of Transmission
Approved For Release 2002/09/04 : - DP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET
(1)
P2$...P8 (EOL)
Item No. Characters*
71-
P2 1
P3 9
P4 8
P5 1
P6 2
P7 2
P8 8
(EOL) 1
'Indicates maximum allowed - may be fewer.
(2)
Item No. Characters
P1 1
P2 1
P3 1
(3) $C$ Variable length free text (changes)
$D
(E OT )
Variable length free text (notes) (EroT)
Content
Pass
Track segment
Target x, y coordinates
Limiting conditions
Quality
Coverage
Mode
Remarks
End of Line
Content
Validate
Output
Briefing board
$E$Pl$P2$P3 (EOL)
Item No. Characters
Pl
P2 4
P3 20
(EOL) 1
Content
Object class
Object count
Remarks in free text
End of Line
Variable length free text (significant OB)
$G$Pl$P2
P3 (EOL)
Item No. Characters
f71- 5
P2 1
P3 V
(EOL) 1
NOTE: For types using EOL, the
B$P1P2P3 (EOT)
Content
Line number
Change indicator
Variable length line
(may be omitted)
End of Line
(EOT)
last EOL will be followed by an M,'OT.
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
(b)
Item No. Characters Content
Pi 9 Mission number
(EOT) 1 End of Transmission
Pl$P2$...P9 (EOL)
Item No. Characters Content
P1 5 Machine reference number
P2 thru P9 are each the same as P1 thru P8 cf
A type message.
(EOL)
1
End of Line
(2)
P:L
( E 0 T )
Item
No. Characters
Content
Pi
1
Description valid
(c)
(EOT)
Pl (EOT)
Item
l
No. Characters
End of Transmission
Content
Pi
(EOT)
1
Machine reference nuriber
End of Transmission
(1)
$K$P1$P2$...Pn (EOT)
Item
No. Characters
Content
Pi
>
Installation name
P2
2
Country code
P3
4
Military district
PL+
11
Geo coordinates
P5
10
BE number
P6
rI ,
PIC number
P7
COMIREX number
P8
1
Status of target
P9
3
Target type
P10
5
Elevation
Pi l (EOT)
Cross reference
End of Transmission
NOTE: Type K message may contain only the first four items or it
may contain any number between 4 and 11.
2$P1 (EOM)
(1) $L$
Approved For Release 2002/09/04:
CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
SCR 352
(d)
(e)
t+$Pl (EOT)
Item No. Characters Content
Pl 5 9t, 9999! Machine reference
number (IC)
(EOT) 1 End of Transmission
(1) $J$ Variable length free text (EOT)
Pl (EOT)
Item No. Characters Content
P1 5 "99997 Machine reference
number (OC)
(EOT) 1 End of Transmission
(f) $6$P1 (EOT)
Item No. Characters Content
Pl 5 9" .9999' Machine reference
number (FC)
(EOT) 1 End of Transmission
(g) $7$Pl (EOT)
Item No. Characters Content
Pl 5 99 99 Machine reference
number (Highlights)
(EOT) 1 End of Transmission
NOTE: Numeric message types 4, 5, 6, and 7 will all be followed
by a J type message in variable length free text.
3.2.2 Output Message Formats
The format of the output messages for Type A messages and Type E
messages is as follows:
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
3.2.2.1
(a)
Output Messag
e Format for Type
A Messag
es.
Item
No. Characters
Content
PO
9
Mission
PI
Track segment
P2 11+
Frame
P3
Target x, y coordinates
P4
8
Limiting
conditions
P5
1
Quality
P6
Coverage
P7
2
Mode
P8
8
Remarks
:3
Blanks
All fields are fixed fields. Information will be BCD left adjusted
with trailing blanks.
3.2.2.2
Output Message Format for Type E Messages.
(a)
Item
No. Characters
Content
PO
10
Date Time
Pi
Object class
P2
hI
Object count
P3
20
Remarks
PO
P1
P2
P3
3.2.2.3 Other Alphabetic Message Type. - All other alpha'Detic
message types are placed. in the working file format with no format change.
3.2.3 Files
The description of the contents of and the procedures required to
transmit records to the Working File and the Queue List and to craange
entries in the Status List are contained in the Status List/Queua List/
Working File Specification (FS-1). The contents of and the procedures
which shall be used by the DEN Program to obtain data from the IDF are
described in the IIS National Data Base File Specification (FS-2) and the
SS-1
1.0
SECRET
Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
 Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
SECRET SCR 352
File Control Program Specification (SS-12).
3.2.4 Secondary Storage
The method of transferring data to and receiving data from secondary
storage shall be in accordance with the procedures described in the IIS
RT/3 Specification (SS-9).
3.2.5 Other Communications with the Real Time /3 Program
The DEN program shall be subject to the control procedures described
in the IIS RT/3 Specification (SS-9).
3.3 Diagnostics
No diagnostics are required of the DEN program.
3.4 Storage Allocation
3.4.1 Working Storage Allocation
3.4.1.1 Drum Storage Allocation. - The DEN program is provided with
drum working storage on only the FH432, FH880 or FH1782 through a RT/3
request with a calling sequence in accordance with the IIS RT/3 Specifica-
tion (SS-9). The maximum drum working storage allocated to the DEN program
shall provide for 20,000 words.
3.4.1.2 Core Storage Allocation. - Maximum core working storage
allocated to DEN is 500 computer words which suffices for the maximum size
of a formatted message and may require transfer of a record in segments
from secondary storage. to the Working File.
3.5 General Design Features
3.5.1 Programming Language
The DEN program shall be coded in the SPRYE Assembly Language.
3.5.2 Flexibility
The code of the DEN program shall be subdivided into modules by at
least five major program functions corresponding to the functions stated in
Section 3.1. If a program function is not implemented initially, the con-
trol needed to operate a "dummy" module shall be included in the program.
When this dummy module is executed, the output record prepared by the
program shall include a statement indicating that this operational function
is not yet available in the IIS.
SS-1
SECRET
Approved For Release 2002/09/04: CIA-RDP78B04747A001900050003-4
 Approved For Release 2002/09/04: CIA-RDP78BO4747AO01900050003-4
SECRET
3.5.3 Recovery Procedure
If the DEN program is unable to receive or assemble any portion
of an entered message due to machine error, it shall discard the entire
message unless the message can be distinguished as a numeric coded type
and its machine reference number is decodable. If both of these con-
ditions exist, it shall initiate formatting of a Queue List entry in
accordance with Section 3.1.1.
4. DEN PROGRAM FLOW DIAGRAM
Figure 1 represents the program flow logic of the functions described
in Section 3.1.
SECT
Approved For Release 2002/09/04 : -RDP78B04747A001900050003-4
 Approved For Release 2002/09/04 :CIA-RDP78B04747A001900050003-4
IDENTIFY
DEVICE
INPUTTING
DATA STRING
REQUEST
FCL SEND
ENTRY TO
~STAT.LIST
FORMAT
REQUEST E'OR
SEGMENT
DEN 2
GET QUEUE
LIST ENTRY
FM.RE24TRNED
MESSAGE
REQUEST
RT 3 GET
Y FROM
BIST. TBL.,
E%IT
TO
DFN 2
FORMAT
REQUEST FOR
SEGMENT
DEN S
FORMAT
QUEUE LIST
ENTRY
GET TEMP.
STOR. ADDR.
FROM HLST.
TABLE ENTRY
REQUEST
RTJ3 LOAD
EG DEN
INSERT
QUEUE LIST
ENTRY IN
MESSAGE
REQUEST GET TEMP.
FORMAT REQ
FORMAT
REQUEST
FORMAT RF;Q,
REQUEST
.
FOR PRIOR RT 3 GET STOR. ADDR.
REQUEST TO
FCL LOAD
TO TRANSFER
MESSAGE TO
RT~3 LOAD
MESSAGE IN
H.T. EN`ff