UNITED STATES INTELLIGENCE BOARD COMMITTEE ON DOCUMENTATION FINAL REPORT: TASK TEAM IX (ADP SYSTEMS LIBRARY)

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP80B01139A000500350002-9
• Release Decision: RIPPUB
• Original Classification: C
• Document Page Count: 109
• Document Creation Date: December 9, 2016
• Document Release Date: August 20, 2001
• Sequence Number: 2
• Publication Date: February 23, 1966
• Content Type: REPORT

Approved Fo~l~ele~tse 2001/09/05 :CIA-RDP80B01139A000500350002-9
C-t7~I~~F-~1~iA~~~N~~~I-~~~.
COI3i~~U-11 ~.~~ ~ `~~'3
23 Fcb~?uarg- 1.96&
t31Yi~T1;D STA'.i'F~ INT'IeI.I..1~~E1~C~ ~C}ARI)
CU1Vi1~SIT'1':~F C'aYV I?~C6.7?MIFIaJ~?1~`1'tCil~
Final tt~xt: Ts~s`s Team l~~
AI?~' Systems Librar,~~
~jact repot is attached far c:ovrdin~.tian avithin meanbc~ a~er~cies~"
departments at~d discussion at a siabsequeat me?ti~~9 fo~? deveioprnent
~f CODi$ s~ecornn;+endation~. tc tk~e UBIR,
C~:arles .Aa l~rf~gs
Sevretary
G1~C?U~ Y
G=~-N= F=>i~~~~'--~d~-Tt>I~~=:~:. ir'xel~.adea fror.~ autc~rrsatic
dasvn~radit~ ano?
riecl.assifica~an
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-0-~1-F-I-D-E-N-T-I-A-L
U N I T E D S T A T E S I N T E L L I G E N C E B O A R D
COMMITTEE ON DOCUMENTATION
TASK TEAM IX - ADP SYSTEMS LIBRARY
T/IX/R-1
~I- February 1966
Group I
Excluded from automatic
downgrading and
declassification.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
T/IX/R-1
4 February 1966
MEMORANDUM FOR: Chairman, Committee on Documentation
SUBJECT: Submission of Final Report
1. Submitted herewith is the Final Report of Task Team IX for
CODIB consideration and approval. The report has one attachment which
is the draft, as approved by the Task Team, of the recommended
Instruction Manual for Submission of Entries to the USIB ADDS File
and Program Catalog System (FPCS).
2. The Final Report covers Task Team IX's recommended concept
of the USIB ADP systems catalogs, the content of the catalogs, frequency
of reporting and updating, and publication of the catalog by DIA on
behalf of USIB. The Team has held nineteen meetings,. from October, 1964
through December, 1965 with many redrafts between meetings to resolve
differences. A combined total of approximately 1600 manhours has been
expended by the Task Team members and supporting personnel (not counting
CSS personnel). This total includes 500 manhours (professional and
clerical) expended by DIA, exclusive of the Task Team IX members, in
the preparation of the DIA Instruction 5S-S-1 on which the Task Team
IX draft of a. USIB manual is based. This DIA Instruction includes
recommendations made by Task Team IX members.
3, The Task Team has been composed of representatives from CIA,
DIA, NSA and the Air Force (AFNINB), with State furnishing. one
"observer." Mr. Robert M. Landau of the CODIB Support Staff served
as Secretary. Army (ACSI) and Navy (ONI) were unable to provide
representation. This was of less significance than originally envis-
aged because, as explanined in the attached report, the Task Team is,
in essence, recommending to CODIB a subset of the larger DIA-DoD
Group 1
C-O-N-F-I-D-E-N-T-I-A.-L Excluded from automatic
downgrading and
declassification.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E~-N-T-I-A-L
intelligence ADP catalog for which DIA has already obtained Army and
Navy concurrences. The observer from State has indicated that his
status is mainly derived from the fact that State has nothing to
contribute to the USIB 1~bPS Library (or Catalog); it would, therefore,
be inappropriate for State to try to influence Task Team IX's delibe-
rations. Be this as it ..may, the question still remains whether State
intends to abstain from reporting to the catalog even though at a
future date the Department might develop and operate specific intelli-
gence ADP projects. This question also applies to AEC and FBI evE~n
though they have not beon represented on Task Team IX. The Task Team
feels that the answer tp this question can be obtained best through
CODIB with its full USIB.-agency representation.
4. As noted in the attached Final Report, three items remain
temporarily unresolved because of work still in progress by other
groups. The first refers to the Unit Identification Code (UIC). A
new DoD UIC is currently being prepared by the JCS for DoD under a
committee chaired by the Office, ASD (Comptroller). This new UIC
is expected to be published by DoD during 1966; it will be included
in the JCS PUB 7. In the meantime, Task Team IX has obtained the new
UIC as prepared by JCS for all USIB agencies and for those DoD agencies
most likely to contribute. to the USIB File and Program Catalogs. The
second item refers to the Intelligence Activity Codes which should be
reconsidered when the Content Control Scheme being developed by CODIB
Task Team I is published. and approved. The third item refers to DTA's
method of publishing the ADPS catalogs. A final DIA decision on the
details of how to publish them has not yet been made, but whatever
decision is made on behdlf of USIB will, of course, be coordinated
with USIB member agencies5. Task Team IX recommends that these three
remaining tasks be monitored by, or coordinated with, CODIB through
the CODIB Support Staff.. The Task Team feels that these three un-
resolved items are of an administrative nature which should not delay
the submission of the Final Report.
5. The Final Report includes content lists for File Description
and Program Description; and their associated indicators for "manda-
toryT' and "optional" reporting items for non-DoD USIB agencies, all
.items being mandatory for DoD agencies. These mandatory USLB items
represent the extent to'which all members of Task Team IX could agree.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05.: CIA-RDP80B01139A000500350002-9
CONFIDENTIAL
25X1A
25X1A
25X1A
Task Team Members:
IA
M
Mr.~ Robert M. Landau,. SS, Secretary
CONF:I:DENTIAL
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A.-L
T/IX-R-1
4 February 1966
U N I T E D S T A. T E S I N T E L L I G E N C E B 0 A. R D
COMMITTEE ON DOCUMENTATION
TASK TEAM IX - ADP SYSTEMS LIBRARY
FINAL REPORT
TABLE OF CONTENTS
SUMMARY... .. .. .............................. ............. ii
RECOMMENDATIONS. .. ......... ............. .................iii
DISCUSSION... ........ .. ..... ......................... 1
.. .. ...
Purpose of Catalog-Conflicting O,pinions ....................... 1
The USIB ADP Catalog System, A Subset of the DIA/DoD
Catalog System.. ...... .............. ... .,.......... 2
Mandatory and Optional Reporting Items for Non-DoD
USIB Agencies ....................... ,. .. ........ 3
Reporting Manual for the USIB File and.Program.Cata.log
System ................. ...... 7
Quarterly Publication in Sections.Determined+bywSubject
and Security Levels . ......................... ............ 9
Cost and Manpower Factors... ................................ 10
ATTACHMENT ;
INTELLIGENCE AUTOMATIC DATA. PROCESSING SYSTEMS MANUAL:
Submission of Entries to the USIB ADPS File and Program Catalog
System (FPCS)
Annex 1: Sample File and Program Description Cards (Fo:rmats 1
through 8)
Annex 2: Geopolitical Code for Intelligence Systems (Copied from
DIA Instruction 65-5A, Enclosure 1)
Annex 3: Intelligence Subject Code, Chapter Summaries (Copied
from Chapter I of the Intelligence Subject Code)
Group 1
C-O-N-F-I-D-E-N-T-I-A.-L Excluded from automatic
Approved For Release 2001/09/05: CIA-RDP80B01139A00050~~~~~`s-ding and
fication.
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
SUMMARY AND RECOMMENDATIONS
SUMMARY
1. Task Team IX found that the purpose of establishing and main-
taining a catalog system reflecting ADP files and programs within the
Intelligence Community is subject to different interpretations. DTA con-
siders the catalog system as a management tool for guiding DoD intelli-
gence ADPS developments as well as a general information register for
the cognizance of all concerned. The Air Force member of the Task Team
subscribed to this view. The CIA and NSA members saw little use of the
catalog system as a management tool as far as their agencies were con-
cerned. They felt that all that is needed from the system are answers
to the two questions: "What intelligence ADP files and programs are
available?'T and "Where are they?" Once these questions are answered,
the details required for decision making can be obtained by contacting
the custodial agency. It was. agreed, however, that since DIA will use
the catalog system as a worldwide management tool, it needed more de-
tailed answers to the two questions than did CIA and NSA. The reporting
system developed was, therefore, designed to answer both needs by dividing
the reporting items into two orders of responses: "mandatory" and
"optional" for non-DoD USIB agencies and for NSA.
2. This reporting system. means that CIA a.nd NSA would submit data.
for all mandatory reporting items considered of common interest to all
USIB agencies, but would respond to the optional reporting items only
as and when the data. are readily available and/or conform with the Agency
policy, DoD intelligence agencies will respond to all reporting items
both optional and mandatory. Both CIA and NSA Task Team members objected
to reporting on ADP development efforts, limiting their reporting to
operational ADP files and .programs.
3, The Task Team membership represented only CAA, DIA, NSA, and
Air Force, with State providing only an "observer' (who indicated that
State has nothing to contribute to the ADPS catalog system). Because
of this situation, the question remains unanswered whether State, AEC,
and FBI will contribute to the catalog system as specific intelligence
ADP files and programs become operational,
4. By request of USIB, DIA is already charged with the machine
processing and publication of a catalog of ADP systems for SIGINT, By
a separate DoD directive, DIA is similarly charged with developing an
ADP catalog system for DoD intelligence agencies. At the time the Task
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Team was formed in October 1964, DIA had already started to develop
formats for the DoD reporting system. Since the objectives of the two
reporting systems are identical, the Task Team left it to DIA to
develop a single operating system to handle the preparation of both
catalogs rather than two distinct systems. Accordingly, the USIB
catalog system is recommended as a subset of the DoD system, both being
identical except that non-DoD USIB agencies are not bound to report
against a.11 reporting items. The Task Team also -left to DIA the re-
sponsibility for the design of the machine formats a.nd programs to be
used in the processing system, incorporating the Task Team reporting
recommendations, The Task Team agreed with DIATs recommendations for
quarterly publication of the two catalog systems (Files and Programs),
but formulated specific instructions for methods of publication, breaking
up the File and Program descriptions into a series of volumes reflecting
various Security and Control levels.
5. The Task Team was unable to provide .cost estimates for operating
the catalog system as requested by the Chairman of CODIB, but gave an
indication of manpower (i.e., time) requirements for pr.epara.tion of inputs
to the system, i.e., from two to four hours for reporting on each file
or program description submitted, Because of the inability to provide
a realistic cost estimate at this time, the Task Team finds it advisable
to establish a method of annual appraisal of the cost and effectiveness
of operating the syste m, a task recommended as a continuing assignment
to the CODIB Support Staff.
6, The manual attached to this Final Report contains the instruc-
tions for submission of entries to the USIB ADPS File and Program Catalog
System. This manual establishes the reporting system in form of punched
cards, four series of cards for the spec if is file description (card
formats 1, 2, 3 and 4), and four for the program description (car.d formats
5, 6, 7 and 8). All mandatory reporting items are preceded by an
asterisk, all other items not so marked being optional. The first six
reporting items (first 16 columns) of each card are necessary card
identifiers which are standard for all cards submitted (report originator;
f i1e or program identifier; card _format no.; card security; action code:
addition of a new file or program description, or changing information
already submitted). Of the 33 entries for file description, 20 are
mandatory; of the 24 entries for program description, 18 are mandatory.
RECOMMENDATIONS
The Task Team Recommends That:
1. The Intelligence ADPS Manual: (U) Submission of Entries to
the USIB ADPS File and Program Catalog System (FPCS), as contained in
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A.-L
iv -
Attachment 1 to this Final Report, be approved as a USIB publication.
2. Non-DoD USIB Agencies and NSA be charged with reporting against
all "mandatory" items, leaving other items "optional" with the under-
standing that DoD intelligence agencies, except NSA, will report against
all. items.
3. The catalog system be published by DIA in accordance with the
Security--Control system as indicated in paragraph 14 of this Final
Report, i.e., descriptions of files and of programs should be published
in four volumes each if so indicated by security classification: one
for SAO--Controlled, one for SI (SSO--Controlled), one for Top Secret
and Secret (whatever the highest security classification of total
report contributions indicate), and one for Confid_entia.l a:nd Unclassified.
4, The CODIB Support Staff, in conjunction with CIA, DIA, and NSA
be charged with preparing a standard report format for ~~n annual assess-
ment by USIB agencies of cost figures in terms of manpower and dollar
expenditures for maintaining the USIB FPCS and for commenting on the
usefulness of the system. This annual a.ss~ssment should be submitted
to CODIB by the CODIB Support Staff.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
DTSCUSSIpN
1. Purpose of Catalog--Conflicting Opinions. In order to better
understand the proposed concept of operation of the USIB ADP systems
library (to be presented in-form of a catalog), some general background
on the views of the various agency representatives regarding the function
of the library is necessary. The recommended concept is a result of
efforts to resolve basic differences in the view of Task Team IX agency
representatives. These differences are a result of conflicting opinions
regarding the purpose of the ADP library.
2. To DIA the catalog of intelligence ADP files a.nd programs has
a two-fold purpose:
a. To serve as a management information system for
DIA to aid in carrying out its worldwide DoD intelligence
ADP management function.
b. To serve as a general USIB and DoD information
register of exchangeable ADP intelligence files and programs.
With these considerations in mind and before the work of Task Team IX
began, DIA, in response to DoD Directive No. 5100.40, dated 28 September.
1963, developed a draft DIA Instruction No. 65-8-1: IDHS, Vol. VII,
Management Systems: (U):Paxt:l, The ADP File and Program Catalog System
(FPCS). This draf-~ was used as a starting point for deliberations of
Task Team IX, and it wa.s the desire of DIA to consolidate the recom-
mendations of Task Team IX with those of DIA into a single instruction
which would satisfy DTA's objectives as well as those of other USIB
agencies.
3, While recognizing that DIA had a second use for the catalog,
both CIA and NSA felt that the extensive file and program information
requ.i.red by the DIA Instruction wa.s unnecessary for USIB exchange pur-
poses. They felt that the catalog need not contain a.11 of the reporting
details required by the DIA. draft instruction. In fact, most of the
controversy which developed. during the meetings centered around the
question of how much information needed to be submitted about each file
or program in order for a potential user to determine whether or nut
he needed a particular file or program. CIA and NSA maintained that
on.l.y a minimum amount of information about an exchangeable file or
program should be recorded and circulated to potential users, and that
if further information was necessary before a decision could be made by
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
- 2 -
a potential user, it could be obtained through subsequent contacts with
the agency submitting the particular description. It was felt that
heavy reliance should be placed on the content of the brief abstract
which was to be submitted and that additional deta.il.s were considered to
be in the "nice to have" category. It was pointed out that no matter how
many details were given in the description entered in the catalog, a
prospective user of a file or program would have to contact the agency
in possession of the file or program for additional details before a
decision could be made, Tl-iere was considerable support for this view-
point, both from inter-governmental agency studies on the subject, and
from previous USIB direction. The basic USIB directive which prompted
the work of Task Team IX (USIB-S-13,1/4, 24 May 1963 approved by
memorandum USIB-M-276, item 3, dated 26 June 1963) contained only nine
reporting items related to ADP program and equipment descriptions (13
items if broken down into subcategories) compared with 26 items for the
program descriptions required by the DIA draft. However, DIA consis-
tently maintained that additional information beyond that outlined by
the CIA and NSA representatives was needed in the general information
catalog in order to satisfy their management responsibilities as well
as to reduce the number of subsequent queries.
4, The USIB ADDS Catalog Systems- A Subset of the DIA/DoD Catalog
System. The solution to these divergent viewpoints was not found until
the Task Team agreed to the concept that the USIB ADP Catalog System
would function as a compatible subset of the larger DIA-DoD Intelligence
ADDS Catalog System. It was felt that it would be much mare feasible
and economical for DIA to develop a single operating system to handle
the preparation of both catalogs rather than two distinct systems. It
was further decided that, since DIA was charged with the machine pro-
cessing and publication of the USIB catalog, they should be given full
responsibility for the design of the machine formats and programs to be
used in their processing system. The Task Team then decided to restrict
its ef:Eorts to: (a) determining the method of reporting each item of
information (not the arrangement or format of the items); (b) determining
the items of information to be reported on a "mandatory" and "optional"
basis by non-DoD USIB agencies; (c) determining the frequency, content
and order of the catalogs to be published; and (d) preparing a draft
USIB Instruction which is compatible with the proposed DIA Instruction
in order that a single processing system can be used by DTA, Task Team
IX then proceeded to recommend modifications to the DIA draft and to
determine which reporting items in the revised DIA draft instruction,
which contained these modifications, could be supplied on a mandatory
basis by the non-DoD intelligence agencies. Only those items which the
representatives unanimously agreed to submit a.re included as mandatory
items. However, CIA and NSA have indicated that the optional items will
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved-For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
- 3 -
be reported when the information can be conveniently obtained and
recorded.
5. Mandatory and Optional Re orting Items for Non-DoD USIB
Agencies. Since DIA was previously requested by the USIB directive
mentioned in paragraph 3 above to maintain the ADP catalog for the whole
Intellligence Community, Task Team IX agreed to accept the basic format
contained in DIA Instruction No. 65-8-1 for the submission of file and
program descriptions. .The proposed USIB Instruction Manual submitted
as Attachment 1, is compatible with DIA Instruction No. 65-8-1; the
only essential differences in the copies to be distributed to USIB
agencies are the insertion of asterisks for "mandatory" reporting items,
and a slightly different editorial arrangement.
6. The items for File Description and for Program Description
are given below. Items recommended as mandatory are indicated by an
asterisk (*) .
a. File Description:
* (1) Report Originator
~ (2) File Identifier (a code assigned by
the file custodian)
~ (3) Card Format Number (Identifier)
* (4) Card Security Classification or Card
Security Control
* (5) Card Handling/Releasability
* (6) Action Code (addition of new file; changing
previous information; etc.)
* (7) Descriptive Title of the File
* (8) Highest Card Security Classification or
Card Security Control (for file description)
* (9) Highest Card Handling/Releasability (for
file description)
Means mandatory reporting items
C-O-N-F-I-D-E-N-T-I-A.-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C=O-N-F-I-D-E-N-T-I-A.-L
~ (10) File Security Classification or Security
Control
~ (11) File Handling/Releasability
~ (12) File Intelligence Subject Code (ISC)
* (13) Date of File Description (Year, Month).
~ (14) Date of File Automation
* (15) Earliest Date of Information in File
(Year , Month)
* (16) File Currency:
(a) Active Files
l Unit of Time Lag (Update Cycle:
Daily, weekly, monthly, etc.)
Amount of Time Lag (Currency
Indication: lag time between the
latest date of information in the
file and the actual date the file
was updated: Hours, days, months,
etc . )
Storage Medium (Cards, paper tape,
magnetic tape, disk, drum)
Disk or Tape Recording Mode (Binary,
Binary Coded Decimal, Mixed)
Narrative description of the purpose
of the file (abstract)
Geopolitical Area (Countries or geo-
graphical areas covered by the file;
use country codes as given in DIA
Instruction 65-6A plus "ZZ't for worl.d-
.wide).. NSA will not fill this in until
an appropriate USIB code is approved..
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
- 5 -
(21) Intelligence Activity Supported by the File
(22) Approximate Number of Logical Records in File
(23) Logical Record Size
(24) Estimated Annual File Growth Rate, expressed
in number of logical records
(25) Logical Record Type (Fixed length; variable
length; mixed)
(26) Magnetic Tape Block (Maximum No. of BCD
characters)
(27) Dependency on other Files
(28) File-Order (Random or mixed, sequential)
(29) File Up-Date Cycle
(30) Exchange Count (Number of other organizations
who receive or have received copies of this
file)
(31) Equipment Manufacturer and Model
(32) Programs used to process this file
(abstract)
(33) Substantive Data Elements
b, Program Description:
*
(1)
Report Originator
~
(2)
Program Identifier (identifying code
assigned by the program custodian)
~
(3)
Card Format Number (Identifier)
~
(4)
Card Security Classification or Card.
Security Control
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
- 6 -
*
(5)
Card Handling/Releasability
(6)
Action Code (Addition of new program;
changing previous information; etc.)
~
(7)
Program Security Classification or
Security Control
*
(8)
Program Handling/Releasability
~
(9)
Descriptive Title of the Program
*
(10) Highest Card Security Classification
Card Security Control (of program
or
description)
*
(11) Highest Card. Handling/Releasability
*
(12) Program Status (Operational)
*
(13) Date of Program Automation (Date program
was operational): Year, month [See item
(22) below]
*
(14) Program Language
*
(15) Software Dependency
~
(16) Equipment Manufacturer and Model
*
(17) Minimum Set. of Equipment and. Special
Features Required to Run this Program
~
(18) Abstract Describing the Program
(19) Program Documentation Status
(20) Program Run Frequency (Daily, weekly,.
monthly, quarterly, semi-annually, etc.)
(21) Program Size (Approximate number of core
locations required by the program)
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
(22) Software Source
(23) Date of this Program Description: Year,
month
(24) Exchange Count (number of other organi-
z~tions who have received copies of this
program)
NOTE: The ordering of the items above is arranged for convenience in
evaluating Task Team IX's recommended "manda.tory'T and "optional" report-
ing entries. As such, it is quite different from the ordering in
Attachment 1 which is arranged by card formats, four each for File and
for Program descriptions.
7. As seen from the above list, 20 of the 33 file description
entries required by the DIA Instruction have been recommended as
mandatory for the non-DoD USIB agencies. Of the 24 program description
entries required in the DIA Instruction, 18 were receommended as
mandatory for non-DoD USIB agencies.
8. Included as mandatory reporting items for all of the agencies
are all but one of the items contained in the original USIB reporting
directive cited in paragraph 3 above. This was item "2. (g)" of the
USIB directive:
"Detailed information on interface with supporting
communications facilities or systems."
The only known interface systems now in use within DoD are the AUTOVON
(Automatic Voice Network) and AUTODIN (Automatic Digital Data Network).
Both of these are operated by the Defense Communications Agency (DCA)
for the Defense Communications Systems (DCS). Some tests are now
being conducted by DCA for intelligence applications, but security
risks have made any proposed system at the present time unacceptable
for all higher levels of classif ica.tion. Other interface systems wh~?ch
are tailored for specific processes are in existence at NSA on a
limited scale. However, there are no programs now in existence which
are felt to be of any general use in the Intelligence Community.
Therefore, Task Team IX believes that this item should not be included
at this time.
9. Resorting Manual for the USIB File and Program Catalog System.
A few explanatory remarks are pertinent here concerning Attachment 1
which is the Task Team draft: "Intelligence ADPS Manual--Submission
of Entries to the USIB ADPS File and Program Catalog System." This
Approved For Release 200C11~7~~~Z`~A~2~P~O~OT1~RD00500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
Manual has been prepared by Task Team IX based on the DIA Manual. In
conformance with paragraph 4 above, it incorporates all suggestions
submitted by Task Team IX plus additional DoD items of reporting which
are not mandatory reporting items for non-DoD USIB agencies. A11
mandatory reporting items, applicable to all USIB agencies, have been
marked. by an asterisk in the .left margin, The instructions in this
Manual are essentially identical to those published as DIA Instruction
65-8-1. The DIA Foreword has been. changed to conform to the USIB
format, such as that used in the publication of the Intelligence Subject
Code (ISC).
10, The Manual covers five chapters, as follows;
Chapter I Introduction
Chapter II System Concepts (contains a Summary of Catalog
content).
Chapter III File and Program Description Card Identification
Chapter IV File Description
Chapter V Program Description
To facilitate accession when preparing inputs, the short supporting
documents are incorporated in pertinent chapters and the longer ones
are annexes. These supporting documents are:
a, Unit Identification Codes (Agency Identification),
yellow ,pages III-6 and 7,
b. Intelligence Activity Codes (Supported by an ADP
File), .pages IV-11 and 12.
c. Equipment Make and Model, green pages IV-23 and 24.
d. Programming Languages, yellow pages V-11 and 12,
e. Sample File and Program Description Cards (Formats 1
through 8), Annex 1.
f. Geopolitical Code for Intelligence Systems [Doi],
Annex 2.
g. Intelligence Subject Code (Chapter I Summa.ries),
Annex 3,
11. A comment is pertinent here concerning the Unit Identification
Codes (UIC). It is now being prepared. by the JCS as a six-digit code
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
for all defense units. A DoD committee chaired by Mr. John W. Bullock
of ASD (Comptroller) is currently working on this code. The completed
code will probably not be published before sometime in Calendar Year
1966. In the meantime, Task Team IX has obtained JCS-approved codes
assigned to the USIB/DoD agencies most likely to report to this
catalog.
12. The ISC three-digit code will be used to indicate its general
subject areas covered by an ADP f i1e. The Intelligence Activity Codes
were developed by DIA as a general list of DoD intelligence activities
supported by the ADP file concerned. It is realized that -these codes
may not yield a. perfect subject and activity classification for each
catalog entry; but Task Team IX feels that it will be adequate for its
limited purpose of indexing USIB catalog entries until better codes are
adopted by USIB.
13. Quarterly Publication in Sections Determined by Subject and
Security Levels. Task Team. IX recommends acceptance of DTA's recommen-
dation to publish the ADP catalog quarterly. Reporting on new entries
for the catalog is timed accordingly.
14. Task Team IX recommends that DIA publish and disseminate the
catalog in two parallel sections, one for file description and one for
program description. Each of these two sections should be published
in four volumes with the fallowing security classification:
a. SAO -- Controlled
b. SI (SSO -- Controlled)
c. Top Secret or Secret (whatever the highest security
classification of total report contributions indicate)
d. Confidential and Unclassified
The USIB directive, cited in paragraph 3 above, requested that all con-
tributions to the catalog be held at its lowest possible classification.
To simplify dissemination of the catalog, Task Team IX recommends that all
catalogs except the SSO and SAO catalogs regardless of security level be
published as NOFORN, CONTROLLED DISSEMINATION, GROUP 1. The SSO a.nd
SAO catalogs should be published as NOFORN and conform to the highest
security classification of total report contributions,
15. All of the catalogs will be listed by organization, and within
organization by the file or program identification number. A11 will have
G-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
a permuted title index which will lead to the appropriate entry in the
catalog. The file descriptions will also be indexed by intelligence
subject code, intelligence activity code, and by country code.
16. Cost and Manpower Factors. The Chairman of CODIB has requested
that all proposals by Task Teams include estimated implementation costs
in terms of both dollars.-and manpower (CODIB Minu-tes for the 62nd
Meeting, 4 May 1965; paragraph 5.b .). However, it is impossible for
Task Team IX to submit a cost estimate at this time for two reasons:
a. Very little information is currently available as
to the number of expected catalog submissions.
b. The computer processing system has not as yet been
planned and developed by DIA. This will be a significant
part of the cost of the operat ion.
17. However, some idea. of the manpower required for the prepara-
tion of an entry into the catalog was gained in the process of pre-
paring two prototype entries included in Attachment 1. One of these is
a sample file description, the other a sample program description. In
order to acquire the necessary information to prepare the entries in the
proper format, the efforts of a number of people were required. Even
though one of the participants wa.s fairly familiar with format require-
ments, it took about four hours each to complete -the two entries. These
prototypes included information on both mandatory and optional reporting
items. It is estimated that if only the mandatory items were furnished,
the entries could have been prepared in about two to three hours. This
limited sample is all that could be used at this time as a guide in
making a general estimate, but Task Team IX feels that since a large
number of people will be called upon from time to time to make -the
entries into the catalog and that these people may not be familiar with
preparation procedures, the time taken for these -two entries is.a repre-
sentative minimur~. Only about 15 minutes was required to punch the
necessary information onto IBM cards.
18. Since a realistic cost estimate cannot be provided at this
time, Task Team IX recommends that a standard report format be prepared
by the CODIB Support Staff in conjunction with CIA, DIA a.nd NSA. At a
minimum, this report should provide cost figures in terms of both
manpower and dollar expenditures, and comments concerning the usefulness
of the exchange system, i.e., the number of programs and files that have
been exchanged as a result of the publication of -the catalogs, and other
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
benefits that may have been derived through the exchange. This standard
reporting form should be submitted to CODIB through the CODIB Support
Staff, by each reporting agency- on an annual basis, The first annual
report would be due one year following the official publication of
Attachment 1. Although it is generally felt that an exchange of files
and programs among the agencies of the Intelligence Community is
desirable, we feel that in actual practice this may not be true. An
annual report. as proposed would provide a means of evaluating the cost
of maintaining the ADP catalog system vs. the usefulness of the system
to the participating agencies.
C-O-N-F-I-D-E-N-T-I-A.-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
{t~) SCI~~M:f~ aIQRJ ~J.: ;IaNT,~I;I:;S TO T:~IE tlS:L~3 A3~1:'S f',i:l,k;;
ADD PROGRAM t;A.TAL()G ~Y~~'~M (I'I'rS)
4 f.'c~~77~~aa,ry 1. ~~6(i
k X.(_'.}.t.71~.~ CA f 7'i ~iTl c1 L.~:(.117j.;~.~~.
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-T-A-L
U N I T E D S T A. T E S I N T E L L I G E N C E B O A R D
FOREWORD
These Instructions prescribe the reporting requirements, pro-
cedures, and formats for submission of descriptions of automated
intelligence master data files and computer programs for inclusion
in the USIB ADP Systems Library Catalog.
The Instructions are issued ,pursuant to their approval by the
? United States Intelligence Board (USIB) on It
has been prepared by an interagency task team under the direction
of the Committee on Documentation (CODIB). At the request of USIB,
the Defense Intelligence Agency (D IA) will-maintain the USIB ADP
Systems Library Catalog on behalf of the United States Intelligence
Community. DIA will periodically publish catalogs of library ADP
files and programs holdings.
Comments of users on means to improve the Catalog will be
welcomed. Such comments, or requests for additional explanations,
changes or additions should be addressed, through channels, to the
Chief, CODIB Support Staff, Office of Central Reference, Central
Intelligence Agency.
PAUL A.. BOREL
CHAIRMAN
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
G-O-N-F-I-D-E-N-T-I-A-L
Chapter I, Introduction
II. System Concepts
III. File and Program Description Card Identification
IV. File Description
V. Program Description
Annex 1
Card Format 1 (descriptive title of the file)
Card Format Z (geopolitical areas and file dependency}
Card Format 3 (miscellaneous file descriptions)
Card Format 4 (programs used to process the file,.
substantive data elements, and narrative
description of file purpose)
Card Format 5 .(descriptive program title)
Card Format 6 (software dependency)
Card Format 7 (minimum equipment and special
features needed to .run program)
Card Format 8 (abstract describing the program)
Annex 2 Geopolitical code for .Intelligence Systems
Annex 3 Intelligence Subject Code
C-O-N-F-I-D-E-N-T-I-A-L
Approved For. Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Chapter I
1. The File and Program Catalog System (FPCS) is designed
to prdvi,de the United States Intelligence Community with data
to produce a central catalog of automated master intelligence
data files and of computer programs used to process these data
files. This catalog will be published quarterly by the
Defense Intelligence Agency (DIA) on behalf of USIB and of DoD
and is intended to facilitate the exchange of information
among members of the Intelligence Community.
2. The success of this system depends entirely upon the
strict adherence, by all participants,. to coding instructions.
Data submitted that is not in accordance with this manual will
be rejected in processing. These reports will be returned for
resubmission during the next reporting cycle.
3. It should be noted that DIA, as the publishing agency,
is operating this catalog under two directives, one stewing from
USIB (USIB-S-13.1/4, approved on 26 June 1963), the other stew-
ing from DoD Directive No. 5100.40, dated 28 September 1963:
"Responsibilities for the Administration of Automatic Data
Processing Equipment Program:" In consequence of the two
directives, the reporting requirements submitted in this manual
reflect combined requirements of USIB and DoD, the former
being a subset of the larger DIA/DoD reporting requirements.
In this manual, the USIB reporting requirements have been
marked by an asterisk in the left margin, preceding the card
column designations for each card format used. Items so
marked are mandatory reporting items for all USIB agencies
excluding DIA/DoD, while all reporting items apply to DIA/DoD.
This arrangement has been instituted in the interest of
economy. USIB agencies reporting against the mandatory report-
ing items are encouraged to respond to other reporting items
shown in this instruction manual...: '
4. Caution must be used in designating file and program
identifiers. Each reporting agency is responsible for assigning
.Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
a unique identifier for each file: or. prograrri developed within
the agency. Unit I.D. plus file or .program identifier will
be the accession to the file. File or program identifiers must
not be reused.
5. Requirements far additional data elements or data
codes should be submitted to the Chief, CODIB Support Staff,
Office of Central Reference, Central Intelligence Agency.
6. .This Instruction Manual is effective immediately.
C-O-N-F-I-D-E-N-T-I-A-L
~~~: ~ Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Chapter II
1. Purpose.
On behalf of USIB, DIA will maintain and publish catalogs
containing descriptions of intelligence data stored in an
automated form and of computer programs and associated equip-
ment. The purpose of the catalogs is to facilitate the exchange
of information among the members of the Intelligence Community,
thereby avoiding unnecessary duplication of effort.
2. Seope. '
a. This Instruction applies to all USIB agencies.
b. All intelligence files and programs which are considered
by the reporting agency to be of interest to other USIB
agencies will be described, provided catalog publication
procedures are in accordance with existing security regulations
of the reporting agency.
c. The classification of these descriptions will be kept
as low as possible.
d. It is not required that non-DoD agencies submit in-
formation on inactive files or on programs under development.
3. Definitions. For the purpose of this instruction, the
following definitions will apply:
a. Master file. A file containing relatively permanent
information which is a combination of data that is evntained in
no other file. Individual data elements will be standard and
maybe contained in, or derived i'rom, various master files.
Only master files containing intelligence information and
ancillary files needed to process these files, such as an index
or thesaurus, will be reported. Derivative files will
not be reported in this system.
b. Automated file. A machine-processable file stored on
punched cards, paper tape, magnetic tape, drums, or disks. Film
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
II-2
transparencies of all types are excluded, but independent indices
to film transparencies are included if they are stored on one
of the media mentioned herein.
c. Computer program. The complete sequence of machine
instructions necessary to solve a problem or accomplish a
processing task whether-this sequence is called subroutine,
routine, program, or some other term. Manufacturers' programs
which are commercially available to all users are excluded
unless major modifications have been made to the programs, in
which case, the modifications should be described.
d. Tape block. For the purpose of this instruction,
the term 'Rape block" is the same as "physical record,"
which is defined as "a segment of data inscribed on a record-
ing medium and physically delimited in some fashion, e.g.,
written on a magnetic tape or disk and preceded and followed
by end of record gaps,. or punched on a single card."
e. Logical record. A collection of data elements closely
.enough related to be customarily processed as a unit within a
computer even though, in an external recording medium, the same
stream of data may occupy any number of physical records or any
portion of one physical record. Contrasted with "physical
record."
4. Use of 80-column cards. The FPCS is predicated and guided
by the principle that an action is initiated and controlled by
a series of 80-column:, punched, EAM cards.
a. File and program descriptor cards, each containing a
unique card identification, will be used as a basis for mantain-
ing the FPCS. These cards are grouped as follows;
(1)
File descriptor cards;
Card format 1 Descriptive file title
Card format 2. Geopolitical areas and fCle
dependency
Card format 3 Miscellaneous file descriptions
Card format 4 Programs used to process the file,
substantive data elements, and
narrative description of the file
purpose
C=O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
a-O-N-F-I-D-E-N-T-I-A-L
II-3
(;2)
Program descriptor cards:
t;ard
format
5
Descriptive program title
Gard
format
6
Software
dependency
t;ard
format
7
Minimum
equipment and special
features
needed to run program
Card format 8
Abstract
describing the program
b. The punched card actions can result in an addition to
the catalog, a change to the catalog, or a deletion to the
catalog. Except for the addition of a new file or program
description, the card identification must match the identi-
fication or a record in the catalog, or all data being sub-
mitted on the card will be rejected.
c. To change any part of a file or program description,
the complete card description must be resubmitted with the data
and the date of the description properly updated. For file
descriptions these would include all format 1 through 4 cards;
for program descriptions, all format 5 through 8 cards.
d. To delete a file reference to the catalog, card format 1
will be submitted. To delete a program reference to the catalog,
card format 5 will be submitted. Detailed instructions are
provided in subsequent chapters.
5. Card dai_a content.
a. Positive identification and control in the FPCS is
provided by uniquely identifying each file~or program description
with an identification in columns 1 through 16 of each punched
card. The following information is contained in these
identification columns:
(1)
Report originator (Unit Identification Code)
(;~) File or program identifier (assigned by report
originator)
(3) Card format number
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
II-4
(4) Card security classification or card security control
(5) Card handling/reieasablity
(6) Card action (addition, change, or deletion to the
catalog).
b. File descriptor cards, numbered l through 4, contain the
following additional information.
(1) Card format 1.
(a) Descriptive title of the file,
(b) Highest security of file description cards.
(c) Highest handling of file description cards.
(2) Card format 2.
(a) Geopolitical area(s) covered by the file
(geopolitical) codes are those given in the current DIA instruction
65-5 series plus ZZ for worldwide (see Annex- 2.) :: ': .
(b) Dependency on other files.
(3) Card format 3.
(a) File security classification or fi:Le security
control .
(b) File handling/releasability.
(c) Intelligence activities supported by the file.
(d) Intelligence subjects covered by the file.
(e) Date of file description (report date).
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9.
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
t:-O-N-F-I-D-E-N-T-I-A-L
II-5
Date file became (will become) automated.
Earliest (oldest) date of information in
the file.
(h) File update cycle.
(i) File currency.
(j) Approximate number of logical records in
the file.
(k) Designed logical record size.
(f)
(g)
(1)
(m)
Estimated annual file growth.
Logical record type (fixed, variable
,
mixed) .
(n) Data storage medium (cards, paper tape,
magnetic tape, disk, drum).
(o) Magnetic tape block, if applicable.
(p) Disk magnetic tape recording made, if
applicable.
(q) File order.
(r) File exchange count.
(s) Equipment make and model.
(4) Card format 4.
(a) Card sequence numbers ~'~-~2, programs used
to process this file.
(b) Card sequence numbers 1~-59, substantive data
G-t)-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
(c) Card sequence numbers 6;Qf-69, narrative
description of file purpose. (See footnote on page IV-29).
c. Program descriptor cards (format 5 -through 8) contain,
in addition to the card identification, the following information:
(1) Card format 5.
(a) Security classification or security control
of the program.
(b) Handling/releasability of the program.
(c) Descriptive title of the program.
(d) Highest security of program description
(e) Highest handling/releasability of program
description cards.
(2) Card format 6.
(a) Program status.
(b) Program documentation status.
(c) Date of program automation:
(d) Program :run frequency.
(e) Program size.
(f) Program language.
(g) Software dependency.
(h) Software Source.
(3) Ca.r.d format 7.
(a) Equipment manufacturer and model.
(b) Date of this program description (date of
report) .
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
II-7
(c) Program exchange count.
(:d) Minimum equipment and special features
3aeeded to run program.
(4) Card format 8. Abstract describing program.
fi. Submissions
=t. The information required by this Instruction will be
~~ubmitted on punched cards accompanied by a machine listing of
k.i~e submitted cards, The card decks and listings will be
~:~ansmitted in accordance with established security procedures.
>>. All reports will be batched and submitted by each agency and
ri:;~,.-,~~and on 1 February, 1 May, 1 August, and 1 November,
r'l:o~~rc~ximately 20 days will be allowed prior to system update.
All cards within a batch will be grouped by card format
sequencae within each file or program description.
ei.. Cards sent by mail will be accompanied by one 8~-8kr
}ar1~~.t~_iitt of the cards, double spaced.
~. J~1NAP 128 should be consulted for cards transmitted
l nrc,ugh the AUTODIN network.
. Ii Rio action has occurred during a quarter, a negative
r e~7rorr_-, by message, will be submitted as follows:
~1) By Doll agencies: UNCLAS FOR DIAMS.REF DIAM 65-8-1.
NF-,GAT IVE .
X27 ~3y non-DoD agencies: UNCLAS FOR DIAMS. REF
I;~IB FPCS, NEGATIVE.
Defense Intelligence Agency
Washington, D. C. 20301
1~1'TN: ADPS Center '
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Chapter III
CARD IDENTIFICATION FILE AND PROGRAM DESCRIPTIONS
Card identification is the key to processing any .action in the
File and Program Catalog System (FPCS). It is contained in the first
sixteen columns of every card which is submitted and provides positive
identification and control. This identification will be covered in
detail in this chapter and thereafter will b~ shown as basic card '
identification in the detailed explanation for each card format. This
identification receives processing edits in accordance with these
instructions. Improper identification data on any card will cause a
rejection. of all data submitted on that card.
Card No. Card
. Cols. Chars. Item Edit
* 1-6 6 Report originator (alpha, numeric, or blank): A,N,b
Six or less alpha or numeric characters (left-
. justified) to indicate the originator of the
report. The DoD standard Unit Identification
Code (UIC) will be used. See pages III-6 and'. 7.
This field (columns 1-6) will not be left blank.
~ 7-.12 6 File or program identifier (alpha, numeric, or A,N,b
blank): Six or less alpha or numeric-char-
acters (left-justified) commencing with card
column 7 to represent the file or program
designation assigned by the report originator
which uniquely identifies the file or program
within the reporting organization. All alpha
and numeric characters are acceptable.
Special characters are not permitted. Thais
field (cohunns 7-12) will not be left blank.
~ 13 1 Card format number (numeric): Enter the N
appropriate card format number.; A blank is
not permitted. One of the following card
format numbers must be used:
Card format No.
Card type
1~
File description card 1
2
File description card 2
C-O-N-F-I-D-E-N-T-I,A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
. C-O-N-F-I-D-E-N-T-I-A-L
Detailed coding instructions for each card
format number are provided in subsequent
chapters.
~ 14 1 Card security classification or card A
security control (a:lgha): One alpha char-
. acter representing the classification or
control of the information entered in each
card. The use of control codes, where
appropriate, takes precedence over the use
of classification codes. A blank is not per-
muted. One of the fallowing classification,
.control or combination codes must be used.
Classification
Code
Description
T Top Secret
S Secret
C Confidential
M Confidential --.Modified
Handling Authorized
0 For Official Use Only
U Unclassified
Control Code Description Additional Codes
R SAO controlled F = TZ
Z SSO controlled G = 5Z
E SIOP controlled H = CZ
NOTE l: The additional codes above are
appropriate combinations of classifica-
tion and control codes.
Approved For R~lease~ 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
III-3
NOTE 2: Although each card is coded
separately with a classification or control
code, the file or program report must be
submitted as a complete package. The
package must be transmitted in accordance
with the procedure required by the highest
classification code or the control code
used in one or more of the cards prepared
for a file or program report. Every effort must be
made to use the minimum classification code
which still protects the information on that
card in accordance with existing security
regulations. Use control codes only when
absolutely necessary..
NOTE 3: If none of the above codes are
adequate for security purposes, the
reporting organization will notify DIA
(ATTN: DAMS) through appropriate channels,
specifying the requirement and requesting
.that a code be assigned.
NOTE 4: This field will be filled in by NSA
and CIA with the same information that is
contained in columns 79 and 80 of cards
type 1 and 5. '
~ 15 1 Card handling/releasability (alpha}: One A
alpha character representing the handling/
releasability of the information entered in
each card. Handling/releasability codes
are used. to indicate the dissemination
restrictions of the information entered
in each card. A blank is not permitted.
One of the following handling/releasability
codes must be used:
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
~ 16 1 Action Code (alpha): One alpha character to
indicate the type action required for the report
submission. A blank is not permitted. One of
the following action codes must be used on each
card format submitted:
Code bescription
A Addition of a new file or program
.description to the FPCS.
C Changing information on an existing file
or program description.
NOTE: Once a file or program description
is added to the FPCS, operations on data
elements within these descriptions are
considered changes, whether data elements
are added, changed, or deleted.
Deletion of an existing file or program
description from the FPC;S.
NOTE: The action code t'D" is used only
on card formats 1 and 5 when the report
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001!09/05 : CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A00050035U002-9
C-O-N-F-I-D-E-N-T-I-A-L
originator desires to delete the
entire file or program description from
the system. When the "D" is used on
card format 1, the FPCS maintenance pro-
gram automatically deletes the information
associated with the file description
obtained from card formats 2, 3, and 4.
Similarly, the "D" on card format 5
automatically deletes the information
associated with the program description
obtained from card formats 6, 7, and 8.
NOTE: See Annex 1 for sample file and
program descriptions.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
UNIT IDENTIFICATION CODES
The codes listed below are extracted from the JCS Standard Com-
mand and Control Unit Identification Code (UIC) now (October, 1965)
in process of preparation. As of 1 July 1965, the Secretary of
Defense has directed all DoD activities to implement a si.x-digit UIC.
For sake of convenience, JCS has allocated codes to selected non-
DoD Government agencies, including all USIB agencies, as shown below.
COMMAND OR AGENCY A.BBREV. UIC
AA.C (Alaskan Air Cmd) JAAAA~1
ACIC (Aeron.Chart & Info Ctr) JAAFPPJ
ACSI, DA W~ZIAA.
AEC (Atom. Energy Com. ) H999fd5
AFNIN JAFHTQI
AFSOUTH JA.HTA.QI
AFSTRIKE JA.IWDQ1
4444 RTW JANDVpl
AIC N0586A
AFTAC. (Same code as AFNIN)
ALCOM (See CINCA.L) -
ALSAFRON ~ N629jd5
AMS W~BWAA
ARSOUTH WQIALAA
ARSTRIKE W~GSAA
CIA. (Central Int. Agency) -
C INCAL Ulld~~~
CINCLANT U2~~~'~'
C INCONAD U 3~~'~~
CINCEUR (See USCINCEUR)
CINCPAC ~ U5~'~f~~
CINCSAC U8~~~'~
544 ARTW JABWPQI
2nd RTS JAHDKf~
8th RTS JAHDK~
15 RTS JAHDMQI
CINCSOUTH (See UNSCINCSOUTH)
C INC STRI KE U 7l~~,~l~
D IA H~3 jd~J~l
ENGTE-MI (map & Geod. Div, Wf~~MAA
Directorate of Topo & Mil. Eng)
EUCOM (See USCINCEUR)
EUCOM FLINT CTR
COMMAND OR AGENCY ABBREV. UIC
F ICEUR Nf~47 6A
VQ-2 N~9946
FICPAC N63186
VQ-1 Nl~993~1
FSTC (For. Sci. & Tech Ctr,
AR) Wp1KPAA.
FTD (For. Technology Div,
AFSC) JAEWYQ!
LANTCOM (See CINCLANT)
LANTELT
LANT INT CTR (See AIC)
N57~1~'2
NAVEUR N57~~3
NAVOCEANO N623J~6
NAVSOUTH N63397
NORAD (See CINCONAD)
NSA. (Nat. Security Agency] H999~1
ON T N~~1~115
PACAF JA.GSW~
13 AF JAAVD~
13 ATF (p) (Air Task Force ,
proving)
6499 SG (Listed by AF as SUT) JAIJZ~
67th RTS JA.HDNC1
PACFLT N57~'j~l
PACOM (See CINCPAG)
PACOM FLINT CTR
USp~lf~
5AC (See CINCSAC)
SAC/JSTPS U8~~I~~
50UTHCOM (See USCINC50UTH)
STATE (Dept of State) H999~7
STZC (Sei.&Tech,Int.Ctr,Navy) N63~'79
STRIKE (See CINCSTRIKE)
U4~~1l~
FBI (Fed. Bur. of Investig.) H999J~6
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release`2001/09/05 :CIA-RDP80B01139A000500350002-9
}'
III-7
COMMAND OR AGENCY ABBREV.
UIC
TACCMD (,t~'TAC 3,s part of
TAC CMS
JA IWDk7
USAFb~ ~
JAATS~1
497th RTS
JAHDU~
71;"3 SPE G}3
JAHUY~!
7,~9 SG (Lasted by AFASUT)
JAIMZg
ARAL
W~AKAA.
,~f~SAREUR
WJ~A.NAA
f 513 Int Corps Gp
WBVAAA
ETC (Eng. :l'opographic Ctr)
W~6BVAA
USARPAC,
W~ARAA
500 Int Corps Gp
WBVGAA
USCINCEUR
U4p1p11~p~
USCINCSOUTH
U6~1J~~I~
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
C-~O-~N-F -1-D-E-N-'i?-I-A-L
Chapter. IV'
FIFE DESCRIPTION
Section A
CARD FOR_MA,T' 1
Car?d No. Card
Cols. Chars.
Edit
~:L-16 1.6 Card identification (alpha, numeric, or blank.): A,N,b
Detailed coding instructions for card identi-?
fication are covered in Chapter III. Enter
the numeric character ,Tl? in card column 13
for card format 1 entries.
NOTE: When card format 1 is used for the
deletion of an existing file description
from the FPCS, complete card identification
must be provided in accordance with the
detailed coding instructions i.n Chapter. III;
the alpha character "Dtt is entered in card
column 16 (action code); and card columns
17-80 are Left blank.
~'1~7-'7z 56 Descriptive title of the file (alpha, numeric, A,N,S,b
special character., o.r. blank): Fifty-si:x card
colurrins of free text (left-justified) .~ommenc-
ing with. card column 1.7 :for the dese:rip~L-:ive
title of the file which has been ident:iP:i.ed
in card columnsz-12 of the card identific~at:ion.
All alpha and numer.i.c characters a:re aciceptable.
Only the fol;Low:i:~tg special char'a?~teY;s a:re
acceptable:
Character
Description
.
Period
Comma
(
Oper:~ing
Closing
(left) parenthesis
(r:ight) parent:hes:i.s
Slash (virgule)
-
Hyphen
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
The descriptive title will be used for key-
word perrrn~ted indexing. An.y word comprised
exclusively of numbers (numeric characters)
will not be indexed. (For example: In
"51 AAA" the T'S1" will not be indexed;
"51AAA'T would be indexed. A word will be
indexed if it contains at least one alpha-
betical character and if it does not appear
in a list of specifically excluded words
(such as prepositions, conjunctions, and
articles). Special care must be exercised
in the usage of the slash. If used, it
must not appear in the first position of
a word; that is, immediately preceded by
a blank and immediately followed by the word.
73-?8 6 Reserved for DIA use (blank): Leave blank b
'7'a 1 Highest card security classification or_ A
card security control (alpha) .
NOTE: This security classification refers
to the description of the file as given in
this set of four card formats. As such, it
may differ from the actual security classi-
fication of the file as shown in card format
3 below.
One alpha ehara.cter representing the highest
security control code used in one or more of
the cards prepared for this file description.
A blank .i5 not permitted. One o.f the following
c~lassifieation, control or combination codes
must be used:
Classification
Code Description
T Top Secret
S Secret
C: Confidential
M Confidential -- Modified
Handling Authorized
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I'-A-L
O For Official Use Only
U Unclassified
Control Cade Description Additional-Codes
R SAO controlled F = TZ
Z SSO controlled G = SZ
E STOP controlled H CZ
* 80 1 _Highest card handling/releasability A
(alpha): One alpha character represent-
- ing the highest card handling/releasa-
bility code used in one or mope of the
cards prepared for this file description.
A blank is not permitted. One of the
following handling/releas,ability codes
must be used:
CEO-N-F-I-D-E-N-T-I=A-L
Approved For Release 2001/09/0.5 : CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
X No handling/releasability restrictions
Y Other {See abstract in card format#4
far further information)
NO E: See Ainiex 1 for a' sample of
Card format 1, Columns No. 17-80.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05:.CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Section B
CARD FORMAT 2
Card No.
Cols. Chars. Item
-Card
Edit
*1-16 16 Card identification (alpha, numeric, or A,N,b
blank): Detailed coding instructions for
card identification are covered in Chap-
-. ter III. For card format 2 enter the
numeric character 2 in card column 13.
*17-18 2 Card format 2 sequence number:. (numeric):
Two numeric characters representing the
-card format 2 sequence number. A maximum
of 6 cards is permitted. Only the numeric
characters ~!~-J~5 are used in sequential
order. Enter the sequence number ~~ for
the first card.
X19-54 36 Geopolitical area (alpha or blank): A two- A,b
alpha-character code in one or more of the
two-card-column groups for the geopolitical
area (countries, continents,-water area, or
worldwide area) covered by the file. Refer
to the Geopolitical Code for Intelligence
Systems (DIAI 65-5A series), Annex 2', for
the proper code to.be entered. Use continent
and water area codes rather than specific codes
whenever all specific codes under the general
code are included in the file,. In addition,
the alpha characters "ZZ'T for worldwide may be
used.
NOTE: Since NSA is not using the DoD Geopolitical
Code, and cannot use it for entry submissions to
this catalog, NSA will include references to
country or countries covered by the ADP file
in the abstract of Card Format 4 (see page IV-28).
Until a USIB decision is made concerning the new ~:'
Politico-Geographic code developed by CODIB,
CIA will use the current Don Geopolitical Code.
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-~6
Card Card
19-20 First geopolitical area. A
Card columns 19 and 2k1
must be completed for card
.sequence 1~~1 and may be left
blank for subsequent card
format 2 sequence cards.
21-22 Second geopolitical area, A,b
if applicable, or blank.
23-24 Third. geopolitical area, A,b
if applicable, or blank.
25-26 Fourth geopolitical area, A,b
if applicable, or blank.
27-28 Fifth geopolitical area, A,b
if applicable, or blank.
29-30 Sixth geopolitical area, A,b
if applicable, or blank.
31-32 Seventh geopolitical area, A,b
if applicable, or blank.
33-34 Eighth geopolitical area, A,b
if applicable, or blank.
35-36 Ninth geopolitical area, A,b
if applicable, or blank.
37-38 .Tenth geopolitical area, A,b
if applicable, or blank.
39-40 Eleventh geopolitical area, A,b
if applicable, or blank.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-7
41-42 Twelfth geopolitical area, A,b
if applicable, or blank.
43-44 Thirteenth geopolitical .. ?A,b
area, if applicable, or blank.
45-46 Fourteenth geopolitical A,b
area, if applicable, or
blank.
47-48 Fifteenth geopolitical. A,b
area, if applicable, or
blank.
49-50 Sixteenth geopolitical A,b
area, if applicable, or
blank.
51-52 Seventeenth geopalitical A,b
area, if applicable, or
blank.
53-54 Eighteenth geopolitical A,b
area, if applicable, or
blank.
55-72 18 File dependency_ (alpha, numeric, or A,N,b
blank); In one or more of the three
six-card-column groups enter the six
or less alpha or numeric characters
(left-justified within each card
group) representing the file designation
-code which uniquely identifies other
files within the reparting organization
on which the file. identified in card
columns 7-12 is dependent. If the file
is not dependent upon any other files
within the reporting organization, this
data element is left blank. '
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002=9 .
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-8
Card Card
Cols. Item
55-60 First dependent file desig- A,N,b
nation, if applicable, or
.blank.
61-66 Second dependent file desig- A,N,b
nation, if applicable, or
blank.
67-72 Third dependent file desig- A,N,b
nation, if applicable, or
blank.
' 73-80 Reserved for DIA use (blank): Leave b
blank.
NOTE: If more space is required for
reporting geopolitical area or file
dependency codes, continuation cards
may be used by repeating card identi-
fication (card columns 1-16) plus a
unique card format 2 sequence number
(~1-~15) in card columns 17-18. Geo-
political area codes must be confined
to card columns 19-54 on the continuation
cards, since file dependency codes may be
continued in the same cards. Conversely,
file dependency codes must be confined
to card columns 55-72 on the continuation
cards since geopolitical area codes may
be continued on the same cards. Through
the use of card format 2 sequence numbers,
a maximum of 108 geographic areas and a
maximum of 18 file dependency identifiers
can be recorded
NOTE: See:Anhex 1 for sample of Card.;
Format 2, Columns 17-80.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
' IV- 9
Section C
i
CARD FORMAT 3
Card
Cols.
No.
Chars.
*1-16
16
X17
1
Card identification (alpha, numeric, or A,N,b
blank): Detailed coding instructions
for .card identification are covered in
Chapter III. For card format 3 enter
the numeric character.3 in card column
blank is not permitted. One of the follow-
ing classification, control or combination codes
must. be :.used:
File security classification or security A
control (alpha): One alpha character
representing the classification or control
of the information contained in the file.
The use of control codes takes precedence
over the use of classification codes. A
Classification Code Description
Card
T Top Secret
S Secret
C Confidential
M Confidential -- Modified
Handling Authorized
0 For Official Use Only
U Unclassified
Control Code Description Additional Codes
R SAO controlled F = TZ
Z SSO controlled G = SZ
E SIOP controlled H = CZ
NOTE: This is-the classification or control
placed on the data contained within the file
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-10
for which the file description is prepared
and not the classification or control of the
information contained on this card
* 18 1 File handlin~/releasability (alpha}: One A
alpha character regresenting the handling/
releasability of the information contained
in the file. Handling/releasability codes
are used to indicate the dissemination
restrictions of the information contained
within the file. A blank is not permitted.
One of the following handling/releasability
codes must be used:
NOTE l: This is the handling/releasability
caveat assigned to the information contained
within the file for which the file description
is prepared and not the handling/releasability
of the information contained on this card,
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
NOTE 2: Special handling designations
such as "Controlled Dissemination" and
"No Dissemination Abroad" will be noted
at beginning of narrative (card format 4),
if required.
19-21 3 Intelligence activity supported by
the file (alpha or blank): One alpha
character in one or more of the three
one-card-column groups for the intelli-
gence activity which the file supports.
A,b
Card Card
Cols. Content _Edit
20 Second activity code, if ,: A,b
appropriate, or blank.
19 First activity code.
21 Third activity code, if _ A,b
appropriate, or blank.~i
The intelligence activity codes area
listed below:
Code Description
A Collection
B Biographic intelligence
C Communication intelligence
(inc. traffic analysis, crypt-.
analysis)
D Dissemination
E Electronic intelligence.
F Estimates
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-12
G Counterintelligence (inc. security,
counterespionage)
H Installation intelligence (inc.
targetting, vulnerability analysis,
penetration analysis, damage
assessment)
I Current intelligence (inc. indications,
warning)
J Area analysis (inc. terrain analysis,
escape and evasion, urban area
analysis)
M Mapping and charting
0 Military capabilities (inc. order
of battle analysis, military
logistics)
R Reconnaissance exploitation [inc.
overhead photo indexing, photo
interpretation)
S Scientific and technical intelli-
gence
U Economic intelligence
V Foreign trade
W Production
X Telecommunication
Y Transportation
Z Population
*22-27 6 File Intelligence Sub-iect Codes (ISC) N,b
(numeric or blank): A three-riurneric-
character ISC in one or both of the two
three-card-column groups for the major
information contained within the file.
The first three positions of the ISC as
given in the chapter summaries of the ISC
manual are used for this purpose. This
section is reproduced in Attachment 3
for coding convenience and to enable
those activities which may not have an ISC
manual to code this data element. When a
file could possibly use all or a majority
of ISC codes, use the alpha code "999" in
card columns 22-24.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-D-N-F-I-D-E-N-T-T-A-L
Card Card
Cols. Content Edit
*22-24 Major ISC. These three card N
columns must be completed..
Blanks are not permitted.
25-27 Secondary ISC, if appropriate N,b
or blank.
*28-31 4 Date of file description (numeric): N
Four numeric characters to .indicate
the current date (year and month) of
this file description. '
Card Card
28-29 Year. Two numeric;.
characters indicating the
last two numbers of the
year.
30-31 Month. Two numeric.
characters from ~l to 12
indicating the month.
*32-35 ~ 4 Date of file automation (numeric): N
Four numeric characters to indicate
.the date (year and month): that the
file became or will become operational
as an automated file.
Card Card
32-33 Year. Two numeric characters N
indicating the last two num-
bers of the year.
34-35 Month. Two numeric characters
from X11=12 indicating the
month.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
t:-O-N-F-I-D-E-N-T-I-AFL
*36-39 4 Earliest date of information in file
(numeric): Four numeric characters
to indicate the date (year and month)
of ,the earliest (oldest) information
in the file.
Card
Cols. Content
36-37 Year. Two numeric
characters indicating the
last two numbers of the year.
38-39 Month. Two numeric
characters ~l to 12
indicating the month.
? 40 1 File update _cycle (alpha) : One
alpha character indicating the up-
date cycle of the file.
Code Description
N Not applicable (inactive file}
R_ On line/real time
D Daily
W Less often than daily through
weekly
M Less often than weekly through
monthly
Q Less often than monthly through
quarterly
S Less often than quarterly through
semiannually
Y Less often than semiannually through
yearly
V Variable use pattern
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
' ~ C-O-N-F-I-D-E-N-T-I-A-L
IV-].b
*41-43 3 File currency (alpha and numeric): A,N
One alpha and two numeric
characters to indicate the~time
.lag between the latest date of in-
formati~on in the file and the actual
date the file was updated.
Card Card
41 Unit of time lag. One A
alpha character to
indicate the unit of time
lag between the latest
date of information in the
file and the actual date
the file was updated. A
blank is not permitted. One
of the following-codes must
be used:
Code .Description
N None (not applicable)
H Hours
D Days
M Months
F Final update inactive file)
4Z-43 Amount of-time lag. Two N
numeric characters~~with
a leading zero if necessary
to indicate the amount of
time lag between the latest
date of information in the
file and the actual. date
the file was updated, based
upon the unit of time lag
entered in card column 41.
C-O-N-F-I-D-E-N-T-I-A-L
Approved-For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
NOTE: If the code "N"
is entered in card column
41, enter the two numeric
characters ~Id (zero-zero).
If the code *rF,~ is entered
in card column 41, enter
the last two numbers for
the year of the latest date
of information in the file.
44-47 4 Approximate number of logical records N,A
(numeric and alpha): Three numeric
characters and one alpha character
to indicate the approximate number of
logical records in the file.
Card Card
Cols . Content_ _ __ Edit
44-46 Approximate number of log- N
ical records. Three
numeric characters with lead-
ing zeros, as necessary, to
indicate the approximate
number of logical records in
the file based upon the unit
of measure entered in card
column 47.
47 Unit of measure. One ~~~ A
alpha character to indicate
the unit of measure for the
approximate number of logical
records entered in card columns
44-46. One of the following
codes may be used: U=Units,
H-Hundreds, T-Thousands,
S=Hundreds of Thousands,.
M~lillions .
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
48-51 4 Logical record size (numeric and alpha): N,A
Three numeric characters and one alpha
character to indicate the maximum number
of BCD (6 bit) characters designed for
each logical record.
Card
Cols. Content
Card
Edit
48-50 Logical record size. N
Three numeric char-
acters with leading zeros,
as necessary, to
indicate the maximum number-
of BCD (6 bit) character
positions in each logical
.record within the file,
based upon the unit of
measure entered in card
column 51.
51 Unit of measure. One
alpha character to
indicate the unit of
a measure for the number
of characters entered in
card columns 48-50.
One of the following codes
may be used:
Code Description
U Units
H Hundreds
T Thousands
S Hundred- thousands
M Millions
Approved For Release 2001/09/05: CIA-RDP80B01~139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-18
52-55 4 Estimated annual file growth rate
(numeric and alpha): Three numeric
and one alpha character to indicate
the. estimated number of logical
records by which the file grows on
an annual basis.
Card Card
52-54 Growth rate. Three numeric N
characters with leading
zeros, as necessary, to
indicate the estimated
number of logical records
by which the file grows
on an annual basis, based
ugon the unit of measure
entered in card column 55.
55 Unit of measure. One a~.pha A
character to indicate :the
unit of measure for the num-
ber of logical records
entered in card columns
52-54. One of the following
codes may be used:
Code Description
U Unit
H Hundreds
T Thousands
S Hundreds of thousands
M Millions
NOTE: If the file is static,
column 55 may contain an alpha
rrUtt and columns 52-54 may
contain numeric zeros.
C-O-N-F-I-D-E-N-T-I-A-L
N,A
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I! A-L
56 1 Logical record type (alpha):
One alpha character to indicate
' the logical record type for the
logical records within the file.
One of the following codes may be
used:
Code Description
^_
F Fixed length
V: Variable length
M Mixed
* 57 1 Storage medium (alpha): One alpha
character to indicate the storage
medium of the file. A blank is not
permitted. One of the following codes
must be used:
Code Description
C Cards
P Paper tape
T Magnetic tape
Disk
Drum
58-61 4 Magnetic tape block (numeric and
alpha): Three numeric and one
alpha characters to indicate t~e
maximum number of BCD characters
of a tape block, when the alpha code
"T" is entered in card column 57.
Card ~ Card
Cpls ,-~- Content Edit
5.8-60 Tape block size. Three; N
numeric characters with:
leading zeros, as
necessary, to indicate the
maximum number of BCD
C-O-N-F-I-D-E-N-T-I A-L
N,A
Approved For Release 2001/09/05: CIA-RDP8060'I i 39A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
IV-20
character-positions in a
tape block, based upon the
unit of measure entered in
card column 61.
61 Unit of measure. One alpha
character to indicate the
unit of measure for the
number of characters entered
in card columns 58-60., One
of the following codes may
be used:
Code Description
U Units
H Hundreds
T Thousands
S Hundred Thousands
M Millions
* 62 1 Disk or tare recording mode (alpha):
One character to indicate disk or tape
recording mode. One of the following
codes must be used when card es~lumn 5r7,
storage medium, contains the alpha
character "D" or "T":
Code Description
B Binary
D Binary coded decimal
M Mixed
63 1 File order (alpha): One alpha
character to indicate the order
in which the file is stored fort
processing. One of the following
codes may be used:
C-O-N-F-I-D-E-N-T-I-;A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-#-N-T-~-A-L
IV-21
Code Description
R Random or mixed
S Sequential
64-65 2 Exchange count (numeric): Two
numeric characters with leading
zeros,~as necessary, to indicate
the number of other organizations. who
have received copies of the file, either
on?a one-time or recurring basis.
Enfer ~~ (zero-zero) for none. Enter.
99 for 99 and over. Oniy the:-.numeric
characters ~~`-99 are permttec~
66-72 7 Equipment manufacturer and model
(alpha, numeric, or blank): Seven
or less alpha or numeric characters
commencing with card column 66 to
indicate the data processing equip-
mpnt manufacturer and model of the
equipment used for processing. the
file. One of the codes taken-from
the code sheets for equipment~~models
one pages IV-23 and 24 may be used.
~~i~
NOTE l: Card columns 66-68 contain a
three-alpha-character manufacturerTs bode
(left-justified). Card columns 69-72
contain four or less alpha and numeric
character (right-justified) toy indicate
equipment model. +I
N~3TE 2: New or special equip>hents shoulii
be obtained from $OS circular;;A-55 or
referred to DIA for code assignment to be
added to the. special code name computer
list. Special code. name computers are
1!eft-justified.
C-O-N-F-I~-D-E-N-T-;I ;A-L
~u
A,N,b
Approved For Release-2001/09/05: CIA-RDP80B0''~ 139A000500350002-9
 Approved For Release 2001109/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-i-A-L
N-22
73-80 8Reserved for DIA use .(blank);
Leave blank.
NOTE: See Annex I for a
sample of Card Format 3, Columns
~. 17-8D.
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 C-O-N-F-I-D-#-N-T-I-A=L
Approved For' Release 2001/09/05: CIA-RDP80B01139A000500350002-9
IV-23
IDENTIFICATION OF COMPUTER MODELS
.Manufacturer and Model Code
Advanced Scientific Instru-
menu:
-210 .. ...........?,.......ASI 210
2100..,...... ...:'...,..,ASI 2100
Autonetics Division (North '
American Aviation Co.):
RECOMP II .................AUT REC2
Burroughs Corp.;
160 ...............x,.....-..BUR 160
204 .......................BUR 204
205........................,BUR 205
220 ................`:_.._._...: BUR 220
250 .......................BUR 250..
263 ...............~.....,..BUR 263
280 ...:...................BUR 280
283 ...............:.......BUR 283
D825 ..............:.......BUR D825
E101 ..................:...BUR E101
E102 ......................BUR E102
5000 ......................BUR 5000
5500........ ...............BUR-5500
Control Data Corp.:
160 ..........:.....,'.......CDC 160
160A ......................CDC 160A
636 .......................CDC-636
924 .......................CDC 924
1604 .....................CDC 1604
3100..- ....................CDC 3100
3200 ......... ............CDC 32D0
3600 ......................CDC 3600
3800 ......................CDC 3800
6600 ......................CDC 6600
8090 ......................CDC 8090
G15 .......... ............CDC Gi5
G20 ........................CDC G20
D12..... ... .........CDC D12
Computer Control.Corp,:
DP24... ................CMC DP24
.Digital Equipment Coxp.:
PDP-1 ............. .......DEC PDPl
PDP-4 .....................DEC PDP4
PDP-5 ................:....DEC PDPS
PDP-6 ...:.................DEC PDP6
PDP-7 .....................DEC PDP7
E1-Tropics:
ALWAC LII-E ................ELT ALW3
Electronic Assoc, Inc.:
231R .. ... ................EAi 231R
General Dynamics:
4020... .... .....:.......GDY 4020
General ~lectrie Corp.:
205...,......................GEL 205
215 .. .....................GEL 215
225...'' .....................GEL 225
235..;:,.,... . ...............GEL 235
412.........- ...............GEL 412
625... .................GEL 625
General Mills:
ECS..~::~ ....................GEM ECS
.General Precision, Inc.:
LGP 2I:i..........;i,,.,,,,,.GNP LG21
LGP 30 .. ...... ...........GNP LG30
Libra cope 3055.,....,,,,.,GNP 3055
RPC 40QO ...................GNP 4000
Honeywel;l,, Inc. ; ~~
200,, ,,,,,,,,,,,,,,,,,,,,HON 200
400..;~1 ....................HON 40.0
$OO..., ....................:HON 800
1800..~;......:.,.:~.........HON 1800
International Business Machines
Corg..
305.... .....................IBM 305
360....' ........ ...........IBM 360
650.... . ....................IBM 650
700 series ......:..........IBM 7-
1130..:I ..........:.........IBM 1130
1400 s~ries ....:...........IBM 14-
1620..' ....................IBM 1620
1710..:,...........,!.:.....,.IBM 1710
1800. LI.......,.............IBM 180D
7000 s!eries...: .......... .IBM 7-
Internati!onal Telephone and?Tele-
graph.
7300.. .,.,,,,...,,ITT 7300
Monroe Calculating Machine Co.;
Monrobgt XI.. ..........MON XI
NationalCash Register Co.:
304.. . .....................NCR 304
C-O-N-F~-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B0~.1~9A000500350002-9
 Approved For Release 20D1/09/05 : CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Manufacturer and Model Code
National Cash Register Co.-Conttd.
31.5 .......................NCR 315.
390.........? ..............NCR 390
Not Determined.. .....:.......NOT DET
Pacific Data Systems:
1020.... ................PDS 1020
Pacl contained in card format
rl is the identification.of those
~~rograms used to process this file.
'I`he identification code will be the
name code used to describe programs
1~i this system (see Chapter ITI,
c:~ird Identi:t'ication, columns 7-12) .
I;ac~h program identification will be
:,cparated from the adjacent one by a
ta~ma. 1i. programs frorn the Formatted
Pile Sysi:em (fi'ti) are used, indicate
(~li s by entering ~'FFS~' followed by
;~rre Blank and the program identification.
Data foY~ this information will be
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-IV-T-I-P,-L
i~
IV-~7
entered {left-justified) ebtnmencing
with card column 19 If eeiii-
tinuation cards are~~used, care-must
be exercised to insure. proper data
flow from one card to the next. -
All alpha and numeric characters
may be used. The only special
character permitted is the 'comma
to separate data entries. .'The last
entry for each card must end with
a comma. '
Substantive data elements ';{alpha, ' A,N,S,b
numeric, special eharacteri,'or
blank)r A maximum of 5~1 cards
is allowed, card sequences~'1~~-59. ~ ''!
The second type of informa'ti!on
contained in card format 4 ins
the names of all substanti~t data
__.~.
elements in the file. There is
room for two such entries ~'rv~r each
.card sequence used for a tet~al of
100 entries. Standard abbreviations
or clear mnemonics should bey used.
Special technical contents,~ncluded
iri the file for programming purposes
.need not be named. For anj~`~file con-
taining over 100 data elemen~fis, the
data elements should be gr~-uped-into
their next larger category for sub-
stantive naming. For exampi~:~, if
a large file included datalon installa-
tion dimensions, orientatipn~, roof
evver, and floor area, the data may ~'
,be grouped together and identified as
building descriptions (bldgi~ descrip.) .`
All-alpha and numeric characters are
acceptable. Only the follmv~ang
special characters may be ua~ed:
,,ij
!lii ii
,,~
C-O-N-F-I-D-E-N-T-I-A-L i'
Approved For Release 2001/09/05: CIA-RDP80B0'1~139A000'50035A002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
Character Description
Period
Comma
( Opening (left) parenthesis
) Closing {right) parenthesis
- Hyphen
Card No. ,
Cols. Chars. Content
Card
Edit
14-45 27 First substantive data A,N,S,b
element, T~~se card
columns must be com-
pleted for e~rd se-
quence ].~. nter data
(left-,~ustif~ed)
commencing with card
column 19.
46-72 27 Second substantive A,N,S,b
data element, if
applicable,~~or blank.
*19-72 54 Narrative description of the purpose of A,N,S,b
(Continued) the file~(alpha, numeric, special char-
acter, or blank): The last information
contained in card format 4 i~:a narra-
tive description of the purpose of the
file. This narrative is used to explain
why the file is maintained a~,dl, what nos
produced from it, such as names of
reports or identification of ;,extracted
subsets of data produced iri automated
form. If ten cards are sufficient,
enter the narrative (left-jur~tified)
commencing with card column 19 of card
Approved-For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B0'~139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
sequence 6~.~ If eont~.nuation Garda
are used, care must be exercised to
insure proper data flow from-one card
to the next. Hyphenation must be
avoided from are card to the next.
All alpha and numeric characters are
aceepfiable. Only the following
special characters may be used:
Character Description ~~
~_
Period
Comma ;: a
Opening deft) parenthesis
Closing (right) parenthesis
Hyphen
73-80 8 Reserved for DIA use (blank)
Leave lank
,:,~ .
;,
r;;~
...NOTE : ' See .' Annex. 1. ~: ~ . for a sample of
Card Format 4, Columns No. 17-80 .';
*If more than ten cards are required,
the narrative may begin in cards r~n
10-59 by placing 'a slash in card iir~
column 19 of the first card to contain
the narrative. The free text should
immediately follow the slash and may
continue through card 69. The s1a~slh
is reserved for this. purpose in ca;~d
format 4. ~ ~ i
C-O-N-F-I-D-E-N-T-I-A-L
Approved Fob- Release 2001/09/05: CIA-RDP80B0''i 139A00.0500350002-.9
~ii~
 i~
Approved F6r Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Chapter V
PROGRAM DESCRIPTION
Section A
i
Card Forimat 5
i
Card identification (alpha;,~numeric,
or blank) : Detailed coding; ,in-
Card
Edit
A,N,b
structions for card identification' are
covered in Chapter III. Eater the
numeric. character T'5" in curd colwim
13 for card format 5 entries.
~Pz?u~ram security classification or
security control (alpha) : f'?ne alpha
character representing the classi-
fication or control of the information
contained in the program. The use of" "
control codes takes precedence over
the use of classification codes.- A
blank is not permitted. One of the
following classification or contro
codes must be used: ,,,,
+Classification code- Description
Top Secret
Secret":
Confidential ;~
Confidential--Modified
Handling Authorized
For Ofificial Use Only
Unclassified
C-O-N-F-I-D-E-N-T-I-A-L
~:: L,
Approved-For Release 2001/09/05: CIA-RDP80B0r1139A00:0500350002-9
__ 1
~~
~,
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
V-2
NOTE: This is the classifica-~ion or .
control glared an the data contained within
the program :For which the program des-
cription is prepared and pat tie classi-
ficaton or control of the inf~armaton
contained. on this card.
* 18 1 Program handling/releasability,,(aipha):
One alpha character regresentir}g-the;!
handling/releasability of the?information
.contained in the program. Handling/
releasability codes are. used to
indicate the dissemination re~trictians
of the information contained within
the program. A blank is not permitted.
Orie of the following handling/releasability
codes must be used:
N0~ TE 1: This is the handlin~releasability
caveat assigned to the information captained
Within the program for which~,the program
description is prepared and r~qt the ~uandling/
neleasability of the informa~~on contained on
this card.
C-0-N-F-I-D-E-N-T-7~A-L
Approved For. Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved Fdr Release 2001/09/05: CIA-RDP80B~1139A000500350002-9
C-O-N-F-I-D-E-N-T-I-~-'L
NOTE 2: Special handling designations
such as "Controlled Dissemination" and
"No Dissemination Abroad" c~~.ll be noted
at beginning of narrative (card f?rmat 8),
f~ re~u.red. ~ '
i~, ii
(alpha, numeric, special character,
or blank): Fifty-four card columns
of free text (left-justified)
commencing with card column 'i9 for the
descriptive title of the program which-
has-been identified in card~coiumns
7-12 of the card identificatia~n, Ail
alpha and numeric charaeter:~ are accept-
able. :Only the fallowing :,special
characters are acceptable:
Character
Description
_~~~
(
i
r
Period_ ~_
Comma
Opening
~~; i
__ :_ ~ _,_,
~ ~'
(left) parenthesis
Closing
(rights parenthesis
/
Slash (virgule);;; '
-
Hyphen ~
The descriptive title wilt./:be used~for
keyword permuted indexing.''Any word com-
prising exclusively of numbers (numeric
characters) will not be indexed. .(For
example: In "5i AAA" the "51" will not
be indexed; "51AAA" would be indexed. ;A
ward will be indexed if it::oontains at
least one alphabetical character and if it
does not appear in a-list of specifically
excluded words (such as prepositions, con-
junctions, and articles).. ~~Speciai' care
must be exercised in the usage of the slash.
If-used, it must not appear in the~~first
position of a word; that is,; immediately
preceded by a blank and imrrt~diatel'y fo:l:low-
ed by the word. ~ '
C-O-N-F-I-D-E-N-T-I-A-L
I{
,;~. Approved For Release 2001/09/05: CIA-RDP80B01~139A000500350002-9
*19-72 54 ! Descriptive title of the program A,N,S,b
 Approved For Release 2001/09/05 :CIA-RDP8i0B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
For O~'ficial Use Only
Unclas~if.ied ~~
1?'
C-O-N-F-I-D-E-N-T-I-~,;~L
rl's~
rir~
Approved. For Release 2001/09/05 :CIA-RDP80i~3;01139A000500350002-9
_ .:.:: i i _ _:
__ ~ ,iG~
73-78 6 Reserved for DIA use (blank):
Leave blank.
NOTE: When card format 5 is used~for
the deletion of an ~xistin~~'file a
description from the FPCS,'eomplete
card identification ;must be.provided
%n accordance with the detailed
coding instructions in Chagter III;
the alpha character "D" is~ centered in
card column 16 (action code); and
card columns 17-8~ are left blank.'
*79 1 _u_i chest card security classification
or card security. control (alpha):
One alpha character representing the
highest security classification code
or highest security control code used
in one or more of the cards.pregared
for this program description. A blank
is not permitted. Qne of the following
classification ar_edntrol eades must__ _:
~~ be used: (Control code tak~~ precedence.)
,;
- Classification code Descri~ztion _
ri:,
T Top Ss~ret
S Secre~i~
C Confidential
M Confidential--Modified
Handling Authorized
25X1A'
 25X1A gpproved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 C -O-N-F- I -D-E-N-~- I-1~-L
CARD FURI~AT 6
Ite
.Card
'. Edit'
*1-16 16 '~ Card identification. (alpha~~,numeri~,
or blank) : Detailed coding' in-
structions for card identi~'cation
are covered in Chapter ITI:~ For
card format 6 enter the numeric
character 6 in card column.~13..
Program status (alpha),: On'e alpha
.character representing the!atatus
of the program identified 'in card
columns 7-12 of the card identi-
Description
Operational
Design
Documentation status. (alph~~:
One alpha character representing-
the documentation status of~the
program. A blank is not permitted..
One of the following codes .must be
used: r
Cade Description
fication. A blank ~s~not permittec}.~
One of the following codes i~nust be ~
used: '
N
Approved For Release 200.1/09/05: CIA-RDR'~QB01139A000500350002-9
~,n
Approved For, Release 2001/09/05 :CIA-RDP~OB01139A00050035Q002-9
None ,.',; I
Complete (includingiflow charts,
program listings,- narrative,-
operating 3:nstructibns, etc):
Partial (including one ar more of
above). ~ .
 I
Approved For Release 2001/09/05: CIA-RDP80B01139A000~500350002-9
i
*19-22 4 Date of program automation
(numeric): Four numeric char-
. acter to indicate the date (year
and month) that the ',program became
or will become operational :(columns
19-20 mandatory)
Card
Cols. Content
Card
Edit
X19-20 Year. Two numeric' N
characters indicate
ing the last two num-
bers of the year.~~
21-22 Month. Two numeric
characters from ~l to
12 indicating the
month.
~~~
23 - 1 rog_ram run fre ~ n v (alpha)
One alpha character indicating
the run frequency of the pr,aigram. ;
One of the following codes must
be used. A blank is not permitted.
Code Description
R On line/real time
D Daily
W Less often than dai3~~n through weekly
M Less often than weekly through monthly
Q Less often than monthly through quarterly
S Less often than quarterly through semi-
annually '
f Less often than semiannually through
yearly
V Variable use patterx~,~
I ~:;
i~ .
Approved For Release 2001/09/05: CIA-RDP80Bd'1'139A000500350002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
V-8
24_27 4 Approximate number of core locations N,A
(numeric and alpha) : Three numeric
characters and one alpha character
to indicate the approximate number of
BCp core ~.ocations or computer words
required by the program.
Card Card
Cols. Content
24-26 Approximate number of N
core locations. Three
numeric characters with
leading zeros, as neces-
sary, to indicate the
approximate .number of .BCD
core locations (this number
is expressed in terms of
computer wordy for other
than BCD computers) re-
quired by the program,
based upon the unit of
measure entered in card
column; 27. Blanks are not
permitted.
27 Unit of measure. One /
alpha character to
indicate the unit of
measure for the
approximate number of
core locations entered in
card columns 24-26. A
blank is riot permitted.
One of the following codes
must be used:
Code Description
U Units
H .Hundreds
T Thousands
S Hundred thousands
M Millions
C-O-N-F-I-D-E-N-T-I-A-L
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
t:-O-N-F-I-D-E-N-T-I-A-L
V- ~I
arlri-37 10 Program_1_an na.a e (numeric) N
Three numeric characters repre-
senting the language used to write
i.his program. Blanks are not
permitted. Enter the data (left-
justified) commencing with card
cyolumn 28. One of the codes on the
list on pales V-1L and 12 must be used.
~~iS-71_ 34 Software dependency (alpha, numeric,
special characters, or blank):
inter the name of the external soft-
ware needed to run this program.
f;nter the data (left-justified)
r~ornmencin~ with card column 38.
X11 alpha and numeric characters
are acceptable. Only the follow-
ing special. characters may be
used: This field (columns 38-71)
will not be left blank.
l:haracter Description
Period
i; ornma
t)pening (left) parenthesis
t; losing (right) parenthesis
S1_ash (virgule)
Ii~~phen
1 Software _source (alpha) : Enter one
~~i: (.hE~ 1'ol.lowing alpha codes to
I.de~ntity the source of the s~~ft~aa~~e
~~a~~ied in card columns 3~i-71..
(;ode_ Descmiptiun
1, Focal software
i~[ Manu:L'acturer i s software
A,N,S,b
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
 i
Approved; For Release 2001/09/05 :CIA-RDP80i601139A000500350002-9
oaf Card Format 6 Golumns ~to.~:! :~7-t~
.Leave blank.
;~
G-0-N-F-I-D-E-N-~-I-A-L
App.roved For`Release 2001/09/05 :CIA-RDP80B01139A000500350002,9
~f~~
C-O-N-F-I-D-E-N-T-~I~A-L
Manufacturer's software',
looally modified
Other than local or mariu-
fa~eturer's software
Othet than local: or manu-
facturerTs software,
loealiy modified.
~3-80 $ Res__e_rved_for DIA use (blank):
 Approved For Release 2001/09/05: 'CIA-RDP80B01139A000500350002-9
V-11
;.IDENTIFICATION OF COMPUTER LANGUAGE~CODES
Machine
ACT I
ACT' II7:
ACUxE
ADAPT-
. AIMACO
ALCOM
ALMOST
ALGP
ALGOL
ALTAC
ALTRAN
APT~III
ARGUS
ASAP
AUTOCODE
AUTOCODER
BEFAP
BELL
BLESSED
CAGE
CALZNT
CAP:::
CASE SOAP
CLiP
COBOL
.COBOL 60
COBOL 61
-COBOL NARRATOR
CODAP
COL~,SL
COMPAt'T
COMPASS
DAP '
DAS ;
DAT~CODE
EASX,
_ESCAPE
EAS'~CODER
CODE. TD
BE USED
110 FACT
x:111 FAP
112 FARGO
X113 FAST
114 FLIP
115 FLOWMATIC
116 FORAST
~'-117 FORMOST
'l18 FORTRAN I
''li9 FORTRAN II
120 FORTRAN IV
-121 FORTRANSIT
A~22 FORCOM
123 FORTRAN
124 FCP
~'. X125 FORGO
~1~.28 GAP
130 GECOM
]l31 GP
',132 GPX
7150 INTERCOM
;7151 IT
152 ITL V
Z6El JOVIAL
7L 7 0 KS
Il75 LAS
ll77 LEAP
7178 LIST
179 MAD
7180 MADCAP
13181 ~ M:GSHAP
1182 MAP
X90 NFAT
:'7;91 NELIAC
1 x:92 NUCOM
19 3 NYAP
-200 ORBIT
?01 OPAL
.:205 OSAS ,
Approved Fpr Release: 2001/09/05 : CIA,RDP80B0~ 139A000500350002-9
CODE TO
BE USED
001
002
003
004
005
006
007
008
009
010
017_
012
013
01~
015
016
017.
040
041
042
060
061
.062
063
064
065
066
067
068
069
070
071
072
089
090
091
100
101
102.
 ~ ' .r,.y.
Approved For Release 2001/09/05 :CIA-RDP80~01139A000500350002-9
I
CODE TO
TO USED
i~
!' LANGUAGE
CODE TO
BE-USED
LANGUAGE
206
PAL
272
UTMOST
207
'PAP ,
27.5
VFAP
210
.PINT
280
WIZ
211
POGO
281
WIZOR
212
PROCOM
290
X6
213
~PAK
300
Z~
220 ~~
:DAFT IV 3
301
AAS
221
2EI,~ODE
3.05
ACT IV
222
2IP~ 3000
31m
B'AP
223
720AR
311.
BASIC ASSEMBLER
224
)1PG
315
CAT-C4
229
$4
32a
CAP-MT
230
:SAC
321
CL 1
231
:iAIC
3'L2
CL 2
232
:3AL
325
CT
233
:;ALT ~ ,
3$0
CL,MTRAN
234
:;AP
385.
DANTRAN
235
SCAT
339
FLIT
2 36
:iCOPAC
341
F~Il,OCO
237
SCRAP
34F3
FORTRAN 400
238
iLAP
34~
FORTRAN 63
2 39
SLEUTH
345
I'BMAP
240
SNAP
35~Q
INTERFOR
241
SOAF
3~'~.
I!PS
242
:iPACE
35~
LANGLEY
243
SPAR
35:3
MACRO
244
SPEED
356
METASYMBOL
245
STAR
3~0
NAPS
246
STRAP
365
NOBAS
247
SPS
3.66
OSAP
248
SURGE
373
PSEUDO
249
SPURT
376
SEACOM/SAASAP
252
SYMBO "C"
380
SHARE
260
7'AB60L
3$4
SNOBOL
261
~'AC.
3.8&
SOS
262
9'AS6
390
SYMBO TMD"
263
7'RANSUSE
3,95
SYMBOL
264
7'.ASK
4!(p0
T~MA
270
IINISAF
405
TQPS
271
tiSE '
4+1q
XMAS
~$0..
SAAL
~~,
Approved For Release 2001/09/05 :CIA-RDP;$(~B01139A000500350002-9
 Approved Fo'r Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
C-O-N-F-I-D-E-N-T-i-AFL
V-13
Section C
;~~i
lily
~r~j
Approved For Release 2001/09/05 :CIA-RDP80B011`39A000500350002-9.
i~
Card No. ~ , i' ~ ' ~ Card
' Edit
*1-16 ' 16 ~`~ Card identification (alpha;_ numeric ' A, N, b
or blank) :. Detailed cooling ~, ~instruc-
7 in card-column 13. I
format 7 enter the numeric character
covered in Chapter III. Farlcard
bons for card identificatoh are
representing the carol formaft'~ 7
sequence number. Only the':numeric
;characters ~~-~5 are used inise-
,(numeric): Two numeric characters
;Card format 7 see~u.ence numb{~~r
i.e., ,kJ'1-;~5, are used when ~ it is
;necessary to submit more data for I
;the data elements requested in card
;columns 32-72 of the firstl~card.
~i ~ rl
-quental order. Enter the sequence
number ~,~ for the first card. I
I,i
;:NOTE: Additional sequence numbers, '~
*19-25 ~ ~'Euuipment manufacturer and;rn~idel 'A, N, b
(alpha, numeric, or blank) '.
Seven or less alpha or numeric
character commencing with eatd
;.column 19 to indicate the delta
i processing equipment manufa~turex ~
and model of the equipment eased- ~'
for running this program. :One of
the codes taken-from the ec~de sheet
for equipment models present+~d under
card 3 may be used. A blanld' is not
'.permitted in card columns 19T~1.
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
t:-O-N-F-I-D-E-N-T-I-A=L
NOTE 1. Card columns 19-21 contain a three-
alpha-character manufaetur~t's code.
Card columns 22-24 contain four or less
alpha and numeric characters (right-
~justitied) to indicate equipment model.
NOTE 2: New or special equipments should
be obtained from BoB ciret~lar A-55 or re-
ferred to DIA for code assignment to be
added to the special code name computer
list. Special code name computers are
left-justified.
26-29
.~,.
4 Date of program description's
(numeric) : Four characters to
indicate the current date .(year
and month) of this program des-
cription.
'!
Card ~?~i
~+Card
Cols. Contents I~j
Edit
26-27 Year . Two numeric ':.1 t: ,~ N
characters indicati~ig
the last two numbersi ~ r~
of the year. l
28-29 Month. Two numeric;
~~haracters from ~1 to
t2 indicating the
month. ~,
1
r? N
30-31 2 Exchange count .[numeric) : ~r .
Two numeric characters witI}~,
leading zeros, as necessary5~ to
indicate the number of other
organizations who have recgved
copies of the program.. Ent~err 99 i
for 99 and over. Only the, ~r~himeric
rt ~,
~;-O-N-F-I-D-E-N-T-I-A-;L
l
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 i,,
Approved For Release 2001/09/05 :CIA-RDP80B,(~1139A000500350002-9
~:
C-O-N-F-I-D-E-N-T-I,-A-L i ,~,
~;;
Approved Fo~-~ Rel'ease 2001/09/05 :CIA-RDP80BQ1139A000500350002-9
characters ~Ikf-99-are permitted..
*32-72 41 `Minimum set of equipment and ~speeial ~ .
.must be exercised to insure prwper
switches, etc., are entered (Ieft-
justified), in free form, commen-
cing-with-card column 32. If~f;
continuation cards are used,'c~re
.card readers, floating point, Sense
features required to run this,;pro-
-gram (alpha, numeric,, special';
character, blank): Minimum s;et of~
equipment and special featurs
required to run this program,; such
as core size, number of tape }nits,
- Hyphen ~ ;~
~.~
( Opening " (left) parenthesis
~~ ) Closing (right) parenthesis
~; ,~ _ Slash (vir~a.le) ~~~
,! ,~1
Period I
I , Comma
Cheraster Description
.data flow from one card to thy;next.
A11 alpha-.and numeric characlrs
are acceptable. Only the fol~bwing
special characters maybe used':
73-80 S Reserved for DIA use (blank) ~TI~~.
Card Format 7, Columns Na. 17rfi~$0'.
:~; i
,,~~
'4 ~ ~. ~.
NClTE . See ,Anire~t .~1 :fvr . a': sarnp~.e Hof .
Dave blank ~ ; ( ~
~,~
C-O-N-F'-I-D-E-N-T-i~~-~A-L
A,N,S,b.
 Approved For Release 2001/09/05: CIA-RDP$0B01139A000500350002-9
C-O-N-F-I-D-E-N-T-I-A-L
Card
cols.
No.
chars.
~1-16
16
*17-18
2
*i9-72
5~E
Card identification (alpha, numeric, A, N, b
or blank): Detailed coding instruc-
tions for card identification are
covered in chapter III. ~1-For card
format 8 enter the numeric character
8 in card column 13.
Card format 8 se ence number N
(numeric): Two numeric characters
representing the oard fo,rrrat 8
sequence number. A rnaxirr}um of 16
cards is permitted. Onlyithe numeric
characters ~l~-15 are used in sequential
orde~.~. Enter the sequencq number ~k~
for the first card.
NOTE: Additional sequence nwnbers, i.e.,
,PI1-15, are used when it ~ necessary to
submit more data for the~~data elements
requested in card column~nl9-72 4f the
first card.
Abstract describing the ~#rogram A,.N,B,b
(alpha, numeric, speciaL!,characters,
blank): This abstract is used to
explain why the program ~s main-
tained and what is produeld from it.
The abstract should incl?dJe a des-
cription of the inputs, processing, out-
puts, and any program limitations.
Where master data files ire created pr
processed, the file identification code
C-O-N-F-I-D-E-N-T-IAA-L
l i
Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
 Approved For. Release 2001/09/05 :CIA-RDP80B01'139A000500350002-9
73~8U
Approved-Foy Release 2001/09/05.:-CIA-RDP80601'139A000500350002-9
data flow from one card to the next:.-
- Hyphenation must be avoided from one
card to the next. Ail alpha,~nd
numeric characters are acceptable.
Only the following special eharac~ers
may be used: `'
V-17
used to describe files in tHs
system (see Chapter IiI, Card-
Identification, columns 7-12)' ~~
should be used. Enter the da''ta
(left-justified), in free forn5;
commencing with card column'19. '
~f more space is required, c~ontin-
uativn cards may be used.. I~'
continuation cards .are used,':eare
must be exercised to insure 'p'roper ~~
Ch~-racter
Pormat 8~ Columns No, l7~-$O.I~`
Descrir~tion
Period
Comma ' j , ,
Opening''~left) parenthesis
Closing~~(rght) parenthesis
Slash ' I ?:
HYphen ' ?.
~,.
Reserved-for DIA'use (blank)':~:Leave blank
~~
i
N?TE: See Annex 1 for a , sam~a~.e of Card
C-O-N-F-I-D-E-N-T-I-A-L
I
 :~'(~;N~
~-~-z-s-~-~-Q-T-~~u-o-~
Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
cn
rn
Appn~g,~egs~-~Q~/09tA5 : CIA-RDP80B01139A
 Approved For Release 2001/09/05 :CIA-RDP80B01139A000500350002-9
Approved~o~r ~e`~~s~ ~d1/~9~0~-CIA-RDP80B01139A~'0~5QQ350002-9
 ~~~~v~,d~gK~gle~sp~-~AB1/09/05 :CIA-RDP80B01139A000500350002-9
~NU~ c
A
p TU~~ ~
ono .~i ~ R~s~R~~
.
~ - o ono F~l,~ ~~~~Z
d
A~ka(~~ei~~t/09/05: -RDP80B0~'1~39A000 50002-9
 Approved For Release 2001/09/05: CIA-RDP80B01139A000500350002-9
xxx:,xxxx
~~~.~~~~
~ w w ~ ~ ~o ~o
~ ~ ~ w ~ ~ ~
0 0 0 0 0 0 0
w w w w w w w
0 0 0 0 0.0 0
0 0 0 0 0 0 0
0 0 0 0 0 0 0
~ N~ N N N N
~~
o N
F-' N
NN
W N
LPN
V7N
rnN
~.! N
W N
lON
OIiJ
NW
NW
WW
~P.W
U1 W
rnW
~.1 W
OD W
lOW
O.P
I-~ ~h
N.P
W ~P
.A ~A
ll1,p
rn,t~
J ~
OOiP
10~P
Oll1
F--'lJt
NV1
wln
~~n
~~
rn~
.~~.n
aaln
~uv1
tarn
'fern
N01
W01
.P 01
1.7101
0101
J rn
0001
~rn
OJ
F-'J
NCI
~PJ
1J1~.1
rnv
J v
(JO ~.1
1DJ
Approved Fo f a e 0/ C A-RDP80B01139A000500350002-9
z-~- -~-~- ~ - - -o-
- ~ ..
 svl+~o~a z-~-~-s-~-$-~-~-,~-x-o-a
Approved'-For Release 200.1/09/05 :CIA-RDP8DB01139A000500350002-9
~
N O
~ ''
O
VI Q
~'~(~,~~ O G
~
~
o
ao o
'~~'~NA~^pR
,
~ ~
O N
N N
N N
W N
~F+ N
U1 N
O1 N
"^J N
Oo N
lU N
O W
N W
N W
W W
.~a W
U't W
O't W
v W
W W
~D W
O ~P.
F-' ~
N ~P
W ~P
~P ~P
tJt .p.
d1 ,P
+1 .R
00 iP
tD A'+
O U7
!-~ lfi
N (Jt
W tJ1
.P. U1
U1 U1
131 tIl
V lJt
00 U1
CU U7
O Q1
F-' O~
N 01
W 01
/Cr C1
lJl fT
C1 Q1
V O~
OD 01. .
4G Qt
O ~I
Nit
J
W ~ "-
~P V
~ v
CT1 ~1
V +!
Approved For- Release
2001/09/05 :CIA-RDP80B01139iF1000500350002-9
 Approved For Release 7001/09/05 ? CI 80B01139A0005'00350002-9
~g~ ,
rn
w
r
~o N
O N
F-+, N
N N
0
J
O
~o
~o
oN
rN
~P N
U7 N
01 N
~I N
00 l J
W N
O W
rw
N W
W W
.P W
u~ w
rn w
-- ?- a~'rcjN~TOR
FILE
OR PRp6,~
ID,~NTIEIER
ACA n ~,
R$~
QR n~
EAS
~~
I~rTY
DATE '~- STATU'~..
()F PROD.
~M AUTO
G.~ RUN F~QUEN r1ATION
A,pp Y
ROk. NO --~
? pF CORE
LOCAm,
PROG~M
AGE
W ~l
~ J
V) J
O~ ~i
V ~.1
ao .~
~o ~
CQ.
14ESERVED .
V C-
00 D1
O ~..1
ONS
Approved For Release~001/09/05.: CIA-RDP80B01139A000500350002-9
 ~-~-z-~-.~-~-a-z-3-.>