OCS POLICY AND PROCEDURES MANUAL

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP78-03948A000100020001-5
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 98
• Document Creation Date: November 16, 2016
• Document Release Date: March 15, 2000
• Sequence Number: 1
• Publication Date: January 12, 1970
• Content Type: MF

.. .,
approved For Rel~se 2000/05/08 :CIA-RDP78-039-000100020001-5}
12 January 1970
25X1A
MEMORANDUM FOR: OCS Division and Staff Chiefs
SUBJECT : OCS Policy and Procedures Manual
The attached Table of Contents indicates the preliminary plan for
the Procedures Manual. There are no changes planned for the arrange-
ment and titles of sections; however, the order and content of chapters
will be flexible to some degree.
All pages will be printed on a Policy and Procedures Handbook Form
3153, which was created for the purpose of organization and control of
the manual, The format of the information within the manual is discussed
in Topic 1.2.2, of the Introduction which is part of the attachment.
As each chapter is completed, it will be distributed to Division and
Staff Chiefs for review. It is planned to allow two weeks for review.
Any additions, deletions, corrections, etc. , should be forwarded to _
~. Comments which are received within the two-week period will be
synthesized into the final version.
25X1A
Computer Science Advisor, OCS
Attachment: a/s
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
25X1A
 e 2000/05/08 :CIA-RDP78-039A000100020001-5
OflFice of C?mputer Services
SECTION
P~LI~Y ANa PRt~-CEDURES HANDBC~t~K
CHAPTER
SECTION (Title
)
DATE
T
CHAPTER Ttt a
PAGE
1.0 Introduction '
1.1
Purpose of Manual
1.2
Organizsaion of Manual '
2.Q Crganizatior of OCS
3.0 Computer Center-Facilities
3.1
Hours of Operation
3.2
Operation During Weather.Emlergenciss
3.3
Security and Access
3.4
Tours of the Computer Center
. ,
3.5
Using the Facilities of-the Computer Center
3.6
Hardware Facilities '
3.7
Software.'Fa,cilities .
.3.8
Peripheral Devices
LL.O Pro,~ect Man~.gement and Control
LL.1
Pro~~ct Initiation Procedure -
4.2
Production Procedure
4.3
Computer Cen er Scheduling '
4.4
Production Contro]. '
4.5
Quality Control
4.6
Priority-Scheduling
4.7
Reporting Deficient products
4.8
Technical Assiatande
FORM 3153 ' ~ '
7.69 (08.13.95)
 ~~ ~ ~
ice o omputer Services
SECTION
POLICY AND PROCEDURES HANDBOOK
CHAPTER
SECTION (Tit e)
DATE
CHAPTER T t e
-'
PAGE
4.9
r
Vital Material Protection. ,
4.10
Proiect Design Check List
4.11
Equipment Requests
4.12
Technical Assistance
5.0 Processing Standards
5.1
Hardware Standards
5.2
Tape Labels ,
5.3
-Paper Tape
5.4
Printer.Graphics and Diagraph Code
5.5
Print Image Tape Standards
5.6
Storage Management
5.7
Core~Usage and Allocation ,
5.8
Catalcaging a Prodedure
5.9
Tape Library..
5,10
Job Submission and Processing
3.11
Operating System Updates
5.12
Operating-Rules
5'.13.
Operating Instruotio~s
5.14
Personnel Restrictions and Machine Roon Rules
5.15
File Security
? -RDP7$-039A000100020001-5
 Of'1=ice of Computer Services
POLICY AND PROCEDURES HANDBOOK-
SECTION (Tit e)
CHAPTER 7'x t e
""'`
r
6.0 Programming Sta,ndards~ (
6.1
Programming-Languages
6.2
System Programming
6.3
Language Conventions
~':~.'-
Flowcharting
6.5
Coding
6.6
Label Conventiors
6.7
Message Formats
6.8
Program Testing-
?
6.9
~.
Ope~a.ting Instructions
7.0 Documentation
7.1
Documente~~ion Files
7.2
Updating Job and Program Status Files
7.3
Job Documentation
7.4
Utility Programs
8.0 Forma, Records, and Requests
8.1
Design and Procurement of New Forms ,
$.2
Computer Services Request Form (Form 930)..
8.3
Speed I~tter (Form 1831)
8.4
Priam Pro~'ect Record (Form 2277)
8.5
Program Descripter Record (Form 2278)
8.6
Format Specifications (Form 2337)
 Approved For Rele 2000/05/08 :CIA-RDP78-03~dA000100020001-5
Office of C?mputer Services
SECTION
POLICY AND PROCEDURES HANDBOOK
CHAPTER
SECTION (Tlt e)
DATE
CHAPTER T t e
PAGE
$.7 Computer Request Form (Form 2737).
$.$ EAM Procassin~ Request Form (Foam 2$75)
1 dnnrnvarl Fnr Ralaaca 7Mf1/fly/f1R ? ~Id_Rr1P7R_f13QdRdflflfl'Iflflfl7flflfl'I_~ 1
FORM p (Cq 108.1 8.391
7.69 J~7 _
 ~, 100020001-5
SEC71 N
Office of Computer Services 1
POLICY AND PROCEDURES HANDBOOK CHAPTER
SECTION (Title)
Introduction
CHAPTER ~T t e
Purpose of the Manual
DATE
? January 1970
PAGE
1
~?~?~ This_manual,describes the OCS policies and procedures to be followed
when initr~ating, programming, documenting, and processing jobs in OCS.
The manual contains the organization and function of OCS and its divisions
in order that one may better understand and effectively utilize its.servic,es
and facilities, a description of the OCS computer .facilities; and standard
practices. fo.r having a .job approved for development in O.CS and for the
programming,.~testing;' documentation, production; and filing of the~job:
The objectives of the Policy and Procedures Handbook are:
to promote uniform documentatign and ?desi~n of -jobs ,within the
Agency for computer: users:._
to`~relate tho;.needs and requirements of those offices .with
,~ frequent inter:-office contacts.
o disseminate Agency. procedures'which concern the computer.
. -user. ~ ,:.
to establish a 'refer,ence for.`the new- employee. `
FORM' ~7I15J
T?~G ~oe?~a?ast
 O~~ce o~F Compufer Services N 1
POLICY AND PROC~DUR~S I~ANDBOOK
Organization of the Manual ~ 1
Introduction ~ 7 January 1970
1.2.1 Contents
The manual is composed of eight sections. Section 1. 0 is a general
discussion of the manual. Section 2. 0 provides information on the structure
and services available within OCS. Section 3. 0 describes the OCS computer
facilities, operating policies of the computer center, and lists the current
hardware and software facilities available to users.
Sections 4. 0, ~.0, 6. 0,
and 7. 0, provide standards and practices for all phases of project develop-
ment, implementation, and operation. Section 8. O contains information
regarding all forms, .:records, and requests which apply to OCS functions and
services.
Each section of the .manual is divided into chapters which .are further
1.2.2 Format
divided into topics. :The table. of contents for the manual lists the sections
and .chapters. Each section is preceded by a .section table, of contents which
gives the reference number and page number of each chapter and-topic within
the section.
Pages are numbered consecutively within each section, beginning with
page 1. Illustratiori"s are -not included in the page numbering sequence.
Illustrations will be referred to as Figure 1, Figure 2; etc. and will not be
page numbered unless a~i l:ltzstration contains more than one page. t~"ar this
purpose the page number will indicate the page within the illustration; i. e. ,
 Office of Computer Services
POLICY AND PROCEDURES HANDBOOK
CONFIDENTIAL
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 Approved For Releas pp~~pp~~ ~~,,II RDP78-03948A000100020001-5
~UIV~~IY~
Office of Computer Services
POLICY AND PROCEDURES- HANDBOOK
The classification of Confidential
' is based upon the collection of the
procedures which provide. a
. complete summary of internal ?
operations. Individual pages of
' this manual may be utilized on ?an
unclassified basis after securing
appropriate approval from the
Approved For~~~~~~CIV~~ 8 :CIA-~~~'$t~'3~~~S~F~0~~~2~dOQ~is?
CIV I ~i~
 SECTION
Office of Computer Services
POLICY AND PROCEDURES HANDBOOK CHAPTER
SECTION (Tit e) DATE
t~.~_.~-_ _- _~ 3_~u._]-y 1g
CHAPTER Ttt e) PAGE
~~
1.0 Introduction
1.1
Purpose of P~1anual*
2/4/70
1.2
Organization of Manual*
2/4/70
2.0 Organization of OCS
3.0 Computer Center Facilities
3.1
Using the Facilities of the Computer
Center* 2/3/70
3.2
Hours of Operation*
2/2/70
3.3
Security and Access*
2/2/70
3.4
Tours of the Computer Center*
2/2/70
3.5
Hardware Facilities *
7/2/71
3.6
Software Facilities
3.7
Peripheral Devices*
5/18/71
4.0 Project Management Control
4.1
Project Initiator Procedure
4.2
Production Procdure
4.3
Computer Center Scheduling*
2/10/70
4.4
Production Control*
2/11/70
4.5
Quality Control*
2/11/70
4.6
Reporting Deficient Products*
2/l2/70
4.7
Technical Assistance*
2/19/70
4.8
Priority Scheduling
4.9
Equipment Requests
4.10 Interoffice Cooperation
5.0 Processing Standards
5.1
Assigning Tapes to Projects*
2/g/70
5.2
Operating System Updates*
2/g/70
5.3
Job Card Format*
2/g/70
5.4
Control of Data Processing Media*
2/19/70
5.5
Hardware Standards
5.6
Tape Labels
5.7
Paper Tape*
5/17/71
5.8
Core Usage
5.9
Cataloging a Procedure
*Chapter
Completed
FOR 53
7.69
 Of~iee of Computer Services
S T
POLICY AND PROCEDURES HANDBOOK
CHAPTER
SECTION (Title)
DATE
Table of Contents
_ 23_Jul_y 19_7_1
~l
_ ___
CHAPTER T1t e) ~~ ~ ~-'
PAGE
DATE
5.10 Job Submissions and Processing
5.11 Printer Graphics and Diagraph Code*
5/14/71
5.12 Print Image Tape Standards
5.13 Storage Management
5.14 Operating Rules
5.15 Operating Instructions
5.16 Personnel Restrictions and Machine Room
Rules
5.17 File Security
5.18 1136 P1otter*
7/8/71
6.0 Programming Standards
6.1 Programming Languages
6.2 System Programming
6.3 Language Conventions
6.4 Flowcharting
6.5 Coding
6.6 Label Conventions
6.7 Message Formats
6.8 Program Testing
6.9 Operating Instructions
7.0 Documentation
7.1 Documentation Files
7.2 Updating Job and Program Status Files
7.3 Job Documentation
7.4 Utility Programs
8.0 Forms, Records, and Requests
8.1 Design and Procurment of New Forms*
2/9/70
82 Computer Services Request Form (Form 930)
8.3 Speed Letter (Form 1831)
8.4 Prism Project Record (Form 2277)*
2/9/70
85 Program Descripter Record (Form 2278)
8.6 Format Specifications (Form 2337)
8.7 Computer Request Form (Form 2737)*
2/6/70
8.8 EAM Processing Request Form (Form 1875)
8.9 OCS Charge Record Form (Form 2865)*
2/19/70
*Chapter Completed
FORM
7.69
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Ofl"ice of Computer Services
SECTION
1
POLICY AND PROCEDURES HANDBOOK
CHAPTER
SECTION (Tit e) ~
DAT
Introduction __~ __
5 Februar_Y 1970
CHAPTER T1t e)
PAGE
ection Table o ont n
Page
1. 1 Purpose of the Manual.
1
1 . 2 Organization of the Manual
2
1.2.1 Contents. .
2
1.2.2 Format. .
2
1.2.3 Page Numbering.
2
FORM 3153
7.89 (Ot-13.35)
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Office of Computer Services
SECTION
1
POLIC`E' AND PROCEDURES HANDBOOK
CHAPTER
1
SECTION ( itle)
DATE
Introduction _ ______ __
-
4 Fe
bruar
y 19
70
CHAPTER Ttt e)
_
_
_
PAGE v
Pur ose of the Manual
1
This manual describes the OCS policies and procedures to be
followed when initiating, programming, documenting, and processing
projects in OCS. The manual contains the organization and function
of OCS and its divisions in order that one may better understand and
effectively utilize its services and facilities, a description of the
OCS computer facilities; and standard practices for having a project
approved for development in OCS and for the programming, testing,
documentation, production, and filing of the job.
The objectives of the Policy and Procedures Handbook are:
1, to promote uniform documentation and design of jobs
within the Agency for all computer users.
2, to relate the needs and requirements of those offices
with frequent inter-office contacts.
3, to disseminate Agency procedures which concern the
computer user.
4, to establish a reference for the new employee.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
FORM 3153 (OB- 13.35)
7.69
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Ofl?ice of Computer Services
SECTION
1
POLICY' AND PROCEDURES HANDBOOK
CHAPTER
2
SECTION (Title) ~
DATE
Introduction __~ ______~ __
_ 4 Febru~y 1970
CHAPTER Tit e)
PAGE
Or anization of the an
2
1. 2, 1. Contents
The manual is composed of eight sections, Section 1. 0 is a
general discussion of the manual. Section 2, 0 provides informa-
tion on the structure and services available within OGS. Section
3. 0 describes the OCS computer facilities, operating policies of
the computer center, and lists the current hardware and software
facilities available to users. Sections 4. 0, 5. 0, 6. 0, and 7, 0
provide standards and practices for all phases of project develop-
ment, implementation, and operation. Section 8. 0 contains
information regarding all. forms, records, and requests which apply
to OCS functions and services. Section 9. 0 is a glossary of terms.
1.2.2. Format
Each section of the manual is divided into chapters which are
further divided into topics. The table of contents for the manual
lists the sections and chapters. Each section is preceded by a
section table of contents which gives the reference number and
page number of each chapter and topic within the section,
1.2.3. Page Numbering
Pages are numbered consecutively within each section, begin-
ning with page 1. Illustrations are not included in the page number-
ing sequence. Illustrations will be referred to as Figure 1, Figure
2, etc. , and will not be page numbered unless an illustration
contains more than one page, For this purpose, the page number
will indicate the page within the illustration; i, e. , 1 of 1 , 1 of 2.
For example: Figure 1. Title (1 of 7)
FORM q I'c3~
7-69 J :JJ (08.13.35)
 OCS POL-CYAND PROCEDURES HANDBOOK AUTHOR(S)/TW(6) (INITIALS)
wrb, gjw, jls
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
13 04 73
SUBSECTION (TITLE)
PAGE
TABLE OF CONTENTS
1 of 2
3.1.1
3.1.2
3.1.3
FUNCTIONS
FACILITIES
USER TOOLS
3. 2
HOURS OF OPERATION
3.2.1
3.2.2
3. 2. 3
3.2.4
GENERAL
PRIME TIME
NON- PRIME TIME
EMERGENCY TIME
3. 3
3.4
STAFFING
ACCESS SECURITY
3.4.1
3. 4. 2
3.4.2.1
3.4.2.2
3.4.2.3
3. 4. 3
GENERAL
ACCESS DURING NORMAL DUTY HOURS
Permanent
Temporary
Escort-Required
ACCESS AFTER NORMAL-DUTY HOURS
3.5
COMPUTER CENTER TOURS
3.6
HARDWARE
3.6.1
GENERAL
3.6.2
SYSTEM INTERRELATED DEVICES
3. 6. 3
SYSTEM-DEDICATED DEVICES
3.6.4
SYSTEM-SWITCHABLE DEVICES
3.7
SOFTWARE~~~
3.8
TAPE LIBRARY
3.8.1 GENERAL
3. 8. 2 STAFFING
3.8.3 EQUIPMENT
=~~This subsection is being developed.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OCS POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(S) (INITIALS)
wrb, gjw, jls
BBCTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
13 04 73
SUBSECTION (TITLE)
PAGE
TABLE OF CONTENTS (Continued) Illustrations
2 of 2
Fi ure
3. 3
3.6-1
3. 6-2
3. 6-3
3. 6-4
Title
Total-Support Staffing Coverage
System-Interrelated Devices
System-Dedicated Devices--Major Systems
System-Dedicated Devices--Peripheral Systems
System-Switchable Devices
0/05/08 :CIA-RDP78-03948A000100020001-5
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 A roved or Re
QC S POLICY AND PROCEDURES HANDBOOK
(INITIALS)
SECTION (TITLE)
ILi OCS COMPUTER CENTER
REV NO. DATE
1 13 04 73
SUBSEGTION (TITLE)
PAGE
3. 1 GENERAL
3. 1-1
The OCS Computer Center is dedicated to expeditiously and efficiently answering
Agency requirements for data processing. The Center, through Operations
Division staff, provides software and utility program and production control
support to all customers. Questions about services and how to obtain them
after reading the information herein, should be directed to Chief, Customer
Services Section, X4045. These questions should form the basis for future
updates to this section.
The Center is designed and operated with computer hardware, software, and
staff to provide general computer support to the entire Agency. New hardware
and software are under constant evaluation by computer specialists (such as
the Advanced Projects Staff or Technical Services Branch) to identify and
respond to new requirements and changing Agency priorities. Staffing is
addressed in subsection 3. 3, hardware in 3. 6, and software in 3. 7.
To assure users of good service, they should be familiar with the information
described in Sections IV and V. Section IV, Project Management Control,
addresses control procedures from job initiation through production, quality,
securing technical assistance, and reporting deficient products. Section V,
Processing Standards, describes procedures and standards necessary to use
the Computer Center's facilities. Members of the Operations Division are
available to advise and assist users with any questions or problems.
Potential users also may find. that it is advantageous to consult with or operate
through one of the OCS applications programming divisions or staffs, especially
for substantive problems. For example, ~-the Scientific Applications Division
develops and/or converts programs utilizing mathematical, statistical, or
numerical-analysis techniques to solve problems in the areas of physical
sciences, electrical and aerospace engineering, mathematical simulation, etc.
The Management Support Division is staffed with a support group, the Design
Integration Staff, that generally is responsible for the quality of the, software
developed in this division, and for the software design of systems using the
Generalized Information Management System (GIMS).
Operations Division is staffed with personnel (specifically the Technical
Services Branch) that are prepared to aid in the solution of specific hard-
ware/software/programming problems. Consult the Guide to Office of
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 AUTHOR(B)/TW(3) (INITIALS)
OCS POLICY AND PROCEDURES HANDBOOK
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
1
13 04 73
BU?SECTION (TITLE)
PAGE
3. 1 GENERAL
3. 1-2
Computer Services, especially the "Functional Directory" attachment, to deter-
mine the appropriate organization or individual t0 contact. Unusual hardware/-
software requests should be transmitted through the Information Processing
Coordinator, .one of which has been appointed for each Agency Directorate.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(8) (INITIALS)
lfr 'w
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
1
13 04 73
SUBSECTIpN (TITLE)
PAGE
3. 2 HOURS OF OPERATION
3. 2-1
The OCS Computer Center operates 24 hours per day, 7 days per week, except
for certain preapproved Holidays. Hours of operation are categorized as during
prime time, non-prime time, and emergency.
Job scheduling for all systems during all hours of operation are described in
Section IV, "Project Management Control.'' It is suggested that the reader
reference Section IV also for terminology definitions such as "job categories, "
"priority service," "certified/non-certified terminals," etc.
Prime time is the hours from 0800 to 1800, Monday through Saturday, with
all processing facilities available and the Point accessible. Prime time is
scheduled to meet the following objectives:
w .Provide less than 2-hour turnaround time (TT) for Category C
jobs requiring less than 15 minutes' CPU time.
? Complete processing of all Category C jobs submitted by 1430 hours
by 1700 hours, that require less than 15 minutes' CPU time.
? Provide timely service to Category A job requests.
? .Provide timely response to Interactive Systems users.
Another service provided during prime time is current system status infor-
mation by calling the following extensions:
Information Extension
Interactive Systems:
CP/CMS . . 6801
Online OS information
(non-CP/CMS),,,,,,,,, 7766
ASP, for special processing
requests , 7766
Point, for batch job informa-
tion . .4292
.Automatic status report of
batch systems 7433
Approve or a ease 48A000100020001-5
 AUTHOR(S)/TW(S) (INITIALS)
OC S POLIGY AND PROCEDURES HANDBOOK
lfr gjw
SECTION (TITLE)
REV NO.
DATE
III OCS COMPU TER CENTER
1
13 04 73
SUBSECTION (TITLE)
PAGE
3.2 HOURS OF OPERATION
3. 2-2
Non-prime time is all hours other than prime time (reference 3. 2. 2) unless
time is declared to be of an emergency nature (reference 3. 2. 4); specifically,
from 1800 to 0800 hours, Monday through Saturday, and 1800 hours Saturday
to 0800 hours Monday (includes all of Sunday).
Automatic non-prime time scheduling is designed to maximize throughput and
minimize costs. The objectives to be realized during non-prime time are as
follows:
? Provide the Agency with emergency computing service.
? Process prearranged priority job requests.
? Process batch load remaining from prime time.
? Provide limited interactive service.
Emergency time is during any number of conditions declared to be critical
by nature, such as: inclement weather--earthquakes, storms, floods, droughts;
major power failures; threats to the safety and stability of this country (nuclear,
war, air); emergency conditions occurring within the Headquarters building;
emergency conditions confined to the Computer Center; etc.
Written procedures for operating during emergencies are maintained in the
Center's Supervisors' office, and available to all chief operators and super-
visors. Staffing during emergency conditions is described in subsection 3. 3,
"Staffing. "
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 O S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(S) (IN1TlAL5)
gjw
SEGTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
13 04 73
SUB3EGTION (TITLE)
PAGE
3. 3 STAFFING
3. 3-1
Total staffing support consists of personnel trained to .plan, organize, and
control the operation of the computer and pheripheral data-processing equip-
ment (reference 3. 6) on a 24-hour basis (reference 3. 2) to effectively meet
Agency processing requirements.
The complement of staffing is illustrated in Figure 3. 3. Computing services
are available 24 hours per day; however, staffing support is scheduled com-
mensurate with the Agency's workload. Since most Agency employees' pro-
ductive work is anywhere from 0900 to 2000 hours, the heaviest staff support,
accordingly, is provided during these hours.
Staffing support is divided into three shifts--day, evening, and midnight--
each overlapping into the next shift by one-half hour to provide smooth transi-
tion from one shift to another. Also, split shift coverage occasionally is
assigned to meet certain prescheduled processing requirements. Shift assign-
ments are on a two-week rotational basis, by teams, with emphasis toward
ensuring that all equipment operations are properly represented, and that all
personnel are properly trained (continuous training, as required, is enforced).
The shift schedule is enforced seven days per week, including weekends and
Holidays; however, the staffing complement, for example, for a day shift of
a normal work day (e. g. , Monday) would differ from a day shift of a Holiday
or Sunday.
It should be noted that--although operational support is available 24 hours per
day, coverage during non-prime time (eves, mids, weekends, and Holidays)
must be -pre coordinated with the Computer Processing Branch (CPB), X6572.
During emergency conditions (such as inclement weather), supervisory
personnel determines and contacts the appropriate individuals to staff and
maintain uninterrupted operational, hardware, and software support.
Questions resulting from review of this subsection or for information not
covered herein, should be directed to the Chief, CPB, or his alternate.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 O S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S) TW(S) (INITIALS)
gjw
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
13 04 73
9URSECTION (TITLE)
PAGE
3.3 STAFFING
3.3-2
2300!
2200
0300
1400 ~
0400
s
~~090~2000
0100
0200
1500 ~
1000
1100
1200
13 0 `
Figure 3. 3. Total-Support Staffing Coverage
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 -
C~CS POLICY AND PROCEDURES HANDBOOK
'4UTHOR(S)/TW(s) (INITIALS)
wrb 'w
SECTION (TITLE)
REV NO.
DATE
III . OCS COMPUTER CENTER
1
13 04 73
SUBSECTION (TITLE)
PAGE
3.4 ACCESS SECURITY
3.4-1
Procedures have been designed and implemented for security purposes to
protect against ungainful access to the OCS Computer Center's computer
area. These procedures are divided into two groups--access during and
access after normal duty hours (not to be confused with "Hours of Operation,"
described in subsection 3.2)--each of which are described herein. Access
privileges to the computer area also are classed by requirement--individuals
requiring unrestricted (or "Easy") access (reference 3.4.2. 1, "Permanent")
and individuals requiring intermittent access (reference 3.4.2. 2, "Temporary").
Names of individuals approved for either of these access classes are listed on
Security Office-compiled, -monitored, and -maintained access lists which
remain in effect both during and after normal duty hours.
3. 4. 2 ACCESS DURING NORMAL DUTY HOURS
A receptionist furnished by the Security Office (SO) controls traffic to/from
the Center's computer area from 0730 to 1730 hours Monday through Friday.
Access to the computer area, determine+~ and approved by the Operations
Division Chief and OCS Security Officer, is controlled according to type--
permanent, temporary, or escort required--each of which are described
in the following paragraphs.
3.4.2.1 Permanent
Only personnel responsible for daily operations (and integrity thereof) in the
computer area (e. g. , computer operators, Customer Engineers, systems
programmers, etc.) with proper security clearances gain "permanent access"
status, which allows unrestricted movement within/to/from the area. The
names of these personnel are maintained on the "OCS Access List, Easy
Access With Badge Indicators, " a copy of which is kept at the Center's OS
Receptionist's desk. These ersonnel are 25X1/
25X1A This indicator remains until such time
the employee no longer requires permanent status.
3.4.2.2 Temporary
Personnel with the requirement to gain periodic access to the Center's
computer area gain "temporary-access" status (e. g. , certain management
types directly associated with the Center's activities, technical writers
0001
5
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OC S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/T1A~(S) (INITIALS)
wrb gjw
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
1
13 04 73
SUB9ECTlON (TITLE)
PAGE
3.4 ACCESS SECURITY
3.4_2
25X1A
25X1A
020001-
that must gain periodic access to meet docomentation requirements, software
programmers requiring periodic immediate access to the equipment/operators,
etc.) are allocated "temporary-access" status. Basically, this status allows
the same freedom within the computer area as "permanent-access" status
except on entrance to and exit from the co
3. 4. 2. 3 Escort Required
3.4.3 ACCESS AFTER NORMAL DUTY HOURS
Procedures after normal duty hours are similar to those during normal duty
hours. The major exception is the absence of an OS Receptionist, whose
duties then are assumed by Control Point personnel.
The Section Chief and/or senior Operator are responsible for maintaining
and enforcing proper access security (reference 3. 4, 2). Other methods are
available to provide access security of the Center (after hours). In the event
that the doors to GC03 are secured, call X429.2 for admittance (the Center
normally is staffed 24 hours per day, 7 days per week).
5
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 O
C S POLICY AND PROCEDURES HANDBOOK
AUTHOR(&)/TW(8) (INITIALS)
wrb gjw
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
1
13 04 73
SUBSEGTION (TITLE)
PAGE
3.5 COMPUTER CENTER TOURS
3.5-1
Tours are conducted through the Center's computer area for a variety of purposes
and people. The ADP Training Staff frequently arranges for and conducts tours
as part of their A.DP-orientation courses; staff outside of OCS arrange tours for
familiarization of the dynamic changes that occur within the Center to adjust
to Agency changing requirements; annual tours are conducted for families of
Agency personnel; etc.
Operations Division personnel are available to conduct tour. s; however, tours
may be conducted by other knowledgeable and approved OCS personnel.
The following are procedures relative to arranging/conducting Computer Center
tours:
? All tours must be coordinated in advance with the Chief, Operations
Division, or his representative, X4465.
? Existing space conditions of the Center limit group size to six to
eight, to permit adequate hearing and visibility,
? Non-Agency people must secure prior approval of the OCS Security
Officer, X4011, to participate in a tour.
? It is suggested that a list of visitor names, badge numbers, and
organization be submitted in advance to the receptionist for sign-in
procedures--this saves time and avoids confusion at the entrance
to the computer area.
? It is the responsibility of whomever conducts the tour to ensure
the security of all equipment during the tour--such as advising
the participants that no equipment is to be touched (especially
buttons and switches), or only the equipment being described at
any given time is appropriate subject matter, etc.
? 4 A000100020001-5
Approved For Release 2000/05/08 :CIA=RDP78-03948A000100020001-5
 OC S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TVY(S) (INITIALS)
'w 'ls
SECTION (TITLE)
REV NO. DATE
III OCS COMPUTER CENTER
2 13 04 73
SUBSEGTION (TITLE)
PAGE
3.6 HARDWARE
3.6-1
Computer Center hardware devices are grouped in three specific configurations,
as follows:
? System-Interrelated Devices (reference 3.6. 2 and Figure 3.6-1)
A roved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
? System-Dedicated Devices (reference 3.6.3 and Figures 3. 6-2
and 3.6-3)
? System-Switchable Devices (reference 3. 6.4 and Figure 3. 6-4)
Users are requested to refer to the appropriate vendor-published documentation
for hardware descriptions and capabilities.
3. 6. 2 SYSTEM-INTERRELATED DEVICES
The Center's major computers are configured to perform the functions of the
ASP (Attached Support Processor) and Interactive Systems (reference sub-
section 3. 7, "Software") currently utilized to realize the Agency's processing
requirements, as follows:
Com
uter
ASP
Interactive
p
Main
Support
CP/CM5
OS Online
360/195
X
X
360/65-1
X
360/65-2
X
X'~?
X
360/67-1
X
X~~
X
360 /67-2
X
X>~~
X
X
Note that the 360/67-2 primarily is used for development.
~~~These computers would be run only as a LASP (they would not
support any other CPUs)
Figure 3.6-1. System-Interrelated Devices
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OC S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(S) (INITIALS)
gjw jls
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
2
13 04 73
SUBSECTION (TITLE)
PAGE
3.6 HARDWARE
3.6-2
Hardware that is dedicated to only one computer system is listed in Figures
3.6-2 for the major systems, and 3.6-3 for the peripheral systems. Each
piece of dedicated equipment is listed by model/type, quantity, and device
name for each system.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 r ved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
OCS POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(8) (INITIALS)
~W ~1S
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
2
13 04 73
SUBSECTION (TITLE)
PAGE
3.6 HARDWARE
3.6-3
Dedicated Device
M
S
ajor
ystem
Model/Type
Quantity
Device Name
IBM 360/65-1
2065-H
1
Processing Unit
1052-7
1
Printer-Keyboard
2365-2
1
Processor Storage
2860-3
1
Selector Channel
2870-1
1
Multiplexer Channel
6990
1
Selector Subchannel 1
6991
1
Selector Subchannel 2
4273
1
Multiplexer Channel Extension
2000
1
Ampex Large-Core Storage (LCS)
IBM 360/65-2
2065-IH
1
Processing Unit
1052-7
1
Printer-Keyboard
2365-2
3
Processor Storage
2860-3
1
Selector Channel
1850
1
Channel-to-Channel Adapter
2870-1
1
Multiplexer Channel
6990
1
Selector Subchannel 1
6991
1
Selector Subchannel 2
4273
1
Multiplexer Channel Extension
2000
1
Ampex Large-Core Storage (LCS)
IBM 360/67-1
2067-1
1
Processing Unit
1052-7
1
Printer-Keyboard
2365-2
4
Processor Storage
2$60-3
1
Selector Channel
1850
1
Channel-to-Channel Adapter
2870-1
1
Multiplexer Channel
6990
1
Selector Subchannel 1
6991
1
Selector Subchannel 2
0757
1
Multiplexer Extension
Figure 3. 6-2. System-Dedicated Devices--Major Systems
Sheet 1 of 2
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OCS POLICY AND PROCEDURES HANDBOOK AUTHOR(S)/TWCS) (INITIALS)
gjw jls
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
2
13 04 73
SUBSECTION (TITLE)
PAGE
3.6 HARDWARE
3.6-4
Dedicated Devices
M
S
ajor
ystem
Model-/Type
Quantity
Device Name
IBM 360/67-2
2067-1
1
Processing Unit
1052-7
1
Printer-Keyboard
2365-2
2
Processor Storage
2860-3
1
Selector Channel
1850
1
Channel-to-Channel Adapter
2870-1
1
Multiplexer Channel
6990
1
Selector Subchannel 1
0757
1
Multiplexer Extension
IBM 360/195
3195-K
1
Processing Unit
3851
1
Extended Channels
3060-1
1
System Console
3080-1
1
Power Unit
3080-2
1
Power Unit
3080-3
1
Power Unit
3085-1
1
Power-Distribution Unit
3086-1
1
Coolant-Distribution Unit
7412-1
1
Console
3215-1
1
Console Print Keyboard
2880-2
1
Block Multiplexer Channel
2860-3
1
Selector Channel
1850
1
Channel-to-Channel Adapter
2860-2
1
Selector Channel
2870-1
1
Multiplexer Channel
6990
1
Selector Subchannel 1
6991
1
Selector Subchannel 2
Figure 3.6-2. System-Dedicated Devices--Major Systems
Sheet 2 of 2
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OCS POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(8) (INITIALS)
gjw jls
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
2
13 04 73
SUBSECTION (TITLE)
PAGE
3.6 HARDWARE
3.6-5
Peripheral
Dedicated Device
System
Model/Type
Quantity
Device Name
IBM 360/20-1
2020-C2
1
Processing Unit
1403-N1
1
Printer
1416-1
1
Train Cartridge
2415-1
1
Magnetic Tape Unit and Control
2560-A1
1
Multifunction Card Machine
IBM 360/20-2
2020-C2
1
Processing Unit
1403-N1
1
Printer
1416-1
1
Train Cartridge
2415-1
1
Magnetic Tape Unit and Control
2560-A1
1
Multifunction Card Machine
CDC Page Reader
915
1
Optical Page Reader
8022
1
Page Reader Controller
8092B
1
Teleprogrammer
8096
1
Teletypewriter
8291
1
Paper-tape Punch
8299
1
Paper-tape Reader
0601
1
Magnetic Tape Transport
8193
1
Magnetic Tape Controller
CalComp Plotter
0900
1
Plotter Control
900-1136
1
Interface
1136
1
Drum Plotter
937
1
Magnetic Tape Unit
Bunker-Ramo
BR90
1
Terminal
Figure 3.6-3. System-Dedicated Devices--Peripheral Systems
Sheet 1 of 2
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OC S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(S) (INITIALS)
gjw jls
8ECTlON (TITLE)
REV NO. DATE
III OCS COMPUTER CENTER
2 13 04 73
SUBSECTION (TITLE)
PAGE
3.6 HARDWARE
3.6-6
Peripheral
Dedicated Device
System
Model/Type
Quantity
Device Name
COMTEN
T3670
1
Processor
T3016
3
Multiplexer Channel Expansion
T4001
1
Console
T2017
1
Bisynchronous Modem Interface
Module
T2040
1
Bisynchronous Modem Interface
Module Extension
DatagraphiX
4360
1
Micromation Printer with an
(Stromberg)
F230 Universal Camera
Figure 3.6-3. System-Dedicated Devices--Peripheral Systems
Sheet 2 of 2
A roved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OCS ,POLICY AND PROCEDURES HANDBOOK
?`UTHOR(S)/TW(S) (INITIALS)
g~w ~ls
SECTION (TITLE)
REV NO. DATE
III OCS COMPUTER CENTER
2 13 04 73
SUBSECTION (TITLE)
PAGE
3.6 HARDWARE ~
3.6-7
Other than the central processing units (CPUs) or main frames, the operators'
consoles, and the connecting channels, most of the equipment comprising the
Center is switchable. These devices may be switched to/from various com-
puter systems via the four IBM 2914 Switching Units.
Figure 3. 6-4 is representative of the types of devices that are switchable.
Because of the dynamic requirements levied on the various systems, it is
not possible to accurately list all of the devices and applicable systems at
any given time. The illustration includes the device name, model/type,
quantity, and systems to which the device may be switched as of the above
date.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OC~pp~~IGY ANDePROC
N
EDURES HA
DBOOK
gjw jls
SECTION (TITLE)
REV NO. DATE
III OC5 COMPUTER CENTER
2 13 04 73
SUBSECTION (TITLE) ~
PAGE
3. 6 HARDWARE
.3 (,
5witchable Device
IBM 360 Systems
Model/T e
Quantity
Device Name
195
65-1
65-2
67-1
67-2
These charts will follow.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5'
 OC POLICY AND PROCEDURES HANDBOOK
Au=rHOR(s) jrw(s) (INITIALS)
wrb gjw
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
13 04 73
SUBSECTION (TITLE)
PAGE
3. 8 TAPE LIBRARY
3. 8-1
The tape library, adoubly-secured area located in GC0309A, Headquarters
building,. is a vault within a vault; specifically, the library itself is a vaulted
area within the Computer Center (GC03), which also is a vaulted area.
The library is operated 24 hours per day with its own access-control procedures
under the direction of the Chief, Computer Processing Branch.
Users are requested to familiarize themselves with the rules and procedures
governing tape library functions (reference Section V).
The tape library is staffed 24 hours per day, commensurate with staffing of
the Computer Center (reference subsection 3. 3). Normally,. the library is
staffed with three personnel during the heavy dayshift activities, and one
during both the evening and midnight shifts; however, if unusual circumstances
prevail, extra coverage is provided, accordingly.
If circumstances are such that no support is required (such as during an
approved and prearranged Holiday), the area is secured and vaulted, but with
personnel "on call" in case of an emergency.
3.8.3 EQUIPMENT
The tape library is furnished with the following:
? Independent alarm system to alert personnel of impending
emergency conditions.
Independent wet-pipe sprinkler system for emergency fire
conditions.
? Approximately 15, 000 reels of tape, with both slimline cases
and selfloading cartridges (emphasis is on total stocking with
selfloading cartridges), and both 800-bpi and 1600-bpi tested
tapes (emphasis is on total stocking with 1600-bpi tested tapes).
~ Tape storage racks to accommodate the approximately 15, 000
magnetic tapes.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 AUTHOR(S)/TW(S) (INITIALS)
OCS POLICY AND PROCEDURES HANDBOOK wrb gjw
SECTION (TITLE)
REV NO.
DATE
III OCS COMPUTER CENTER
13 04 73
SUBSECTION (TITLE)
PAGE
3. 8 TAPE LIBRARY
3. 8_2
? KYBE TMS Model 70 Tape Cleaner/Verifier.
? KYBE Tape Cleaner.
? GKI Magnetic Tape Erasures {three units)--these units are approved \
by the Office of Security as being adequate to comply with effective
degaussing procedures.
? IBM 2741 Communications Terminal--used for TAPE FETCH
operations for jobs already in the system.
? Computer-Link Corporation's Model 650 Disk Pack Inspector--
for verifying mechanical tolerances and cleaning the individual
disk surfaces.
? Randomex Model 235 Disk Pack Cleaner.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 rove or a ease -
O POLIC
A
P
> -
Y
ND
ROCEDURES HANDBOOK
SECTION (TITLE)
REV NO. DATE
IV PROJECT MANAGEMENT AND CONTROL
O1 06 73
SUBSECTION (TITLE)
PAGE
Table of Contents
4-i of ii
4, 1
GENERAL
4. 2
PROJECT INITIATION
4. 2, 1
PROCEDURE
4. 2, 2
AUTHORITY
4, 2. 3
APPROVAL
4, 2, 4
APPROVAL NOTIFICATION
4. 3
PRODUCTION RESPONSIBILITY
4, 3, 1
GENERAL
4, 3. 2
CUSTOMER
4. 3, 3
CUSTOMER SERVICES SECTION (TSB/OPS/OJCS)
4. 3, 4
REQUIRED USER DOCUMENTATION FOR CSS SUPPORT
4, 4
SCHEDULING COMPUTER CENTER RESOURCES
4. 4, 1 GENERAL
4, 4. 2 PROCESSING REQUIREMENT CATEGORIES
4. 4, 3 REQUESTING COMPUTER PROCESSING
4, 4. 4 PRIME- TIME SCHEDULING ALGORITHMS
4. 4. 4, 1 General
4.4.4.2 ASP Scheduling Priorities
4. 4. 4. 3 ASP Print Output Priority
4. 5, 1 GENERAL
4. 5, 2 CPB USER ASSISTANCE
4. 5. 3 REPORTING USER PROBLEMS
4. 6 PROCESSING INTEGRITY (nearing completion)
4. 6, 1 POLICY
4. 6. 2 VERIFICATION PROCEDURES
4. 6. 2, 1 ASP System Output
4. 6. 2. 1. 1 SYSOUT A Listing:
A -Unrelated Data
B - Completene s s
C -Accuracy of Operator-Invoked WTP Messages
D -Online Punched-Card Output Requests
E -Peripheral Output Requests
4, 6. 2, 1. 2 A.BEND Codes
4. 6. 2.1.3 JCL Error Messages
4. 6. 2, 1.4 Online-Generated Punched-Card Output Requests
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OJ ~~~ov~~~~r?Art~r e~~~sce~ UORES HANDBO
OK
SECTION (TITLE)
REV NO.
DATE
IV PROJECT MANAGEMENT AND CONTROL
01 06 73
SUBSECTION (TITLE)
PAGE
Table of Contents
4-ii of ii
4.6.2.2
IBM 360/67-1 Interactive System Output
4. 6 , 2. 2.
1
Printer Output
4. 6, 2. 2.
2
Punched-Card Output
4. 6. 2. 3
Peripheral System Output
4. 6. 2. 3.
1
Multiproduct Job
4.6.2. 3.
2
Unique Product
4, 7 COMPUTER-RELATED EQUIPMEN'~ REQUESTS (being developed)
4.7.1 GENERAL
4. 7. 2 TYPES
4.7.2.1 General
4. 7. 2. 2 Remote Terminal Devices
4. 7. 2. 3 Peripheral Equipment
4.7.2.4 ...
4. 8 QUALITY CONTROL (being developed)
4.8.1 GENERAL
4.8.2 RESPONSIBILITY
4. 8. 3 ORGANIZATION REVIEW GROUP (ORG)
4. 8.4 CHANGE CONTROL PROCEDURES
4.8.5 .,.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 CSC
POLICY AND PROCEDURES HANDBOOK
AUTHOR(S) TW(5) (INlT1AL5)
gjw
SECTION (TITLE)
REV NO.
GATE
IV
PROJECT MANAGEMENT AND CONTROL
22 05 73
SUBSEC
TION (TITI..E)
PAGE
4.1
GENERAL
4.1
This .section provides guidelines on how to obtain and use services provided by
the Office of Joint Computer Support (OJCS), and the procedures implemented
by Operations Division personnel to provide and protect the effectiveness of
these services.
A prospective customer normally approaches OJCS with a programming problem
or task for either a partial or total solution, which OJCS terms .as "projects. "
Form 2277, PRISM Project Record (reference 4. 2. 1 and Section VIII), provides
the prospective user with a simple vehicle on which to register this problem,
which is used for costing and data control purposes.
The publication entitled A Guide to OCS, especially the "Functional Directory"
attachment, is a useful tool to guide potential users or customers to OJCS
services.
The remainder of this section documents basic customer /OJCS relationships,
prudent resource management, and the minimum control necessary for orderly
operation of a large computer center, such as the OJCS Computer Center.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 O S POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(3) (INITIALS)
wrb gjw
SEC710N (TITLE)
REV NO.
DATE
IV PROJECT MANAGEMENT AND CONTROL
22 05 73
SU9SECTION (TITLE)
PAGE
4.2 PROJECT INITIATION
4. 2-1
When an individual or office (potential customer) is ready to formally request
OJCS services, it is assumed that a set of processing requirements (termed
by OJCS as a project) .exists. The potential customer must first complete and
submit a Form 2277, "PRISM Project Record, " to the Director of OJCS for
review and action. Following the Director's approval and acceptance of the
proposed project, the Form 2277 is the vehicle by which a unique identifier
and common reference to all phases of activity is formulated for the project.
The potential customer also should accompany the form with any other perti-
nent facts that would aid in the OJCS Director's determination of which OJCS
resources are being tasked, especially if the OJCS Applications Programming
Division support is required.
OJCS endeavors response to `all requests, and exercises value judgement on
a particular project only on request. The requesting office holds the respon-
sibility to ensure the validity of its request for OJCS services and that the
expenditures are to the benefit of the mission of the office and Agency.
The Director, OJCS, must ensure that OJCS resources are adequate before
approving acceptance of any proposed project. OJCS systems or programming
resources are limited and must be coordinated with one of the OJCS program-
ming divisions. Most requirements for "normal" computing hardware can be
accommodated; however, "unusual" hardware/software requirements should be
directed through the requesting office's Directorate Information Processing
Coordinator (reference subsection 4. 7, "Computer-Related Equipment Requests").
4.2.4 APPROVAL NOTIFICATION
Following the OJCS Director's decision to accept a project, a copy of the
approved Form 2277 is returned to the requesting office as OJCS' official
agreement to support the project.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 AUTHOR(S)/TW(S) (INITIALS)
OCS POLICY AND PROCEDURES HANDBOOK
'w
SECTION (TITLE)
REV NO.
DATE
IV PROJECT MANAGEMENT AND CONTROL
22 05 73
SUBSECTION (TITLE)
PAGE
4. 3 PRODUCTION RESPONSIBILITY
4. 3-1
After a project has been programmed and successfully tested, the requesting
office, itself, may assume the responsibility for production processing (refer-
ence 4. 3. 2) or submit it to the Customer Services Section (CSS/TSB/OPS)
(reference 4. 3. 3). The following addresses the responsibilities of each
decision.
If the requesting office elects to assume production processing responsibility,
OPS will continue providing hardware support, as requested. However, the
original PRISM Project number and office designation must be specified for
such requests. The customer also must ensure that only the minimum number
of necessary magnetic tapes be assigned and retained for his use by the tape
library, and that current, adequate backup files are maintained.
4. 3. 3 CUSTOMER SERVICES SECTION
If the requesting office elects to submit .the px?oject to OJCS for production
processing, procedures must be coordinated with the Customer Services
Section (CSS) as early as possible during the testing stage. CSS advises the
customer as to the required documentation that must be supplied (reference
4. 3. 4), and coordinates other details, as required.
CSS' responsibility to -the project includes the following:
? Scheduling computer resources.
? Backup files.
? Input control.
? Output verification.
? Program modification in the event of OS or ASP changes.
? Cataloging datasets and programs, as required.
? Program optimization. ?
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 AUTHOR(S)/TW(3) (INITIALS)
O POLICY AND PROCEDURES HANDBOOK
gjw
SECTION (TITLE)
REV NO. DATE
IV
PROJECT MANAGEMENT AND CONTROL
22 05 73
SUBSECTION (TITLE)
PAGE
4. 3
PRODUCTION RESPONSIBILITY
4. 3-2
? Ensuring timely delivery of output products to proper destination.
? General "trouble shooting" activities to protect the integrity of
the project.
4. 3..4 REQUIRED USER DOCUMENTATION FOR CSS SUPPORT
The following lists information that must be furnished and forms that must be
completed and submitted to the Chief, CSS, prior to CSS's acceptance of project
production responsibility. Section VIII provides the instructions for completing
each of the forms. CSS also assists users in completing all forms and selecting
only those necessary for project production documentation for their particular
project.
? Copy of "PRISM Project Record," Form 2277 -- this form
initially was completed and submitted when the individual or
office formally requested OJCS services (reference subsection 4. 2,
"Project Initiation").
? "Program Descriptor Record,'" Form 2278 -- used to provide a
brief program description, including program language and ver-
sion, list of modules used and where they are located in the system,
and core requirements (including minimum and maximum trans -
actional variations, etc. ).
? "Reports -Printer Setup and Distribution," Forrn 2968a -- used to
provide customer-desired printing instructions.
"Computer Processing Request," Form 273? -- used as the
vehicle to submit certain (not all) jobs for processing and
control by the Computer Center.
? "Record Format Descri tion," Form 2968 -- used to describe
the inherent features of a program record; its fields--number,
name, length, type (alpha or numeric), and description of each--
are listed.
? Other Required Information -- deemed necessary by GSS to ensure
processing continuity and integrity, such as:
a. System and/or program flowcharts.
b. Sample "expected" out ut roduced from the ob'ect
Approved For Release0~/pE$r: ~b~~DP~,~~4~~Q~,'~Q,0020001-'~
 QCS POLICY AND PROCEDURES HANDBOOK
AuTHORisi%-rwcsi (INITIALS)'
g~ W
86CTION (TITLE)
REV NO.
GATE
IV PROJECT MANAGEMENT AND CONTROL
22 05 73
SUBSECTION (TITLE)
PAGE
4. 3 PRODUCTION RESPONSIBILITY
4. 3-3
c. "Run Schedule" -- processing daily, weekly, monthly,
quarterly, etc.
d. Rerun procedures, in the case of an abnormal job
termination (ABEND).
~ Data Backup Forms;
a. "Data Backup Questionnaire" -- to be completed if
no data backup support is required other than that
provided by the OJCS Tape Library.
25X1A b. "'Data Backup Request" -- to be completed for
data that is deemed irreplaceable and of vital impor-
tance to the Agency.
c. "Headquarters Data Backup Request" -- accompanied
by a justification memorandum, to be completed for
data of the highest priority and sensitivity that must
be accessible in less than 24 hours--usually 30 minutes
or less.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OC POLICY AND PROCEDURES HANDBOOK AUTHOR(8 Tw(s) (INITIALS)
~W
SECTION (TITLE)
REV NO. DATE
IV PROJECT MANAGEMENT AND CONTROL
2 22 05 73
$UB9ECTION (TITI?E)
PACE
4.4 SCHEDULING COMPUTER CENTER RESOURCES
4.4-1
This subsection describes the procedures in effect for scheduling the Attached
Support Processor (ASP) resources provided by the Computer Center, the char-
acteristics that form processing requirement categories (reference 4.4. 2)
designed to encourage effective scheduling, and methods by which customer/-
Center communications are enforced.
Control, as described herein, is directed toward the ASP System as being the
"standard" system on which most Agency work is processed. The other
systems, such as interactive and peripheral, are addressed elsewhere in
this document.
The objectives of controlled scheduled processing are as follows:
? Establish and maintain procedures for optimum utilization of
resources.
? Effectively and expeditiously accommodate all of the processing
requirements levied on the Center.
? Maximize service to the user, especially during "prime time"
(reference 3. 2).
? Effectively communicate submitter requirements to the Center,
and, in turn
Provide the submitter with current project/system status informa-
tion.
Successful achievement of these objectives depends on operator/customer
cooperation and understanding relative to available hardware/software
resources. Also, it should be noted that Operations Division personnel can-
not evaluate the urgency or relative priority of computer processing require-
ments, nor can individuals submitting work for a third party. This responsi-
bility rests with the customer, who should exercise objectivity in selecting
his requirement categories, and consideration of the fact that any job processed
will impact turnaround time on all other jobs submitted.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OCS POLICY AND PROCEDURES HANDBOOK
AUTHOR(S)/TW(S) (INITIALS)
gjw
SECTION (TITLE)
REV NO.
DATE
IV PROJECT MANAGEMENT AND CONTROL
2
22 05 73
SUBSECTION (TITLE)
PAGE
4.4 SCHEDULING COMPUTER CENTER RESOURCES
4.4-2
Scheduling of computer processing resources is based on the specific require-
ments of the job. Processing requirements are categorized into the following
five areas:
Category Description
A Category A represents an urgent processing request
that must be processed during prime time by a specified
time and date, regardless of the run characteristics or
resources (reference 4. 4. 5). This type of request must
be approved by the Director (or his alternate) of the
office for which the job is to be processed.
B Category B requests are such, that they require monitor-
ing by a specific programmer (determined by the sub-
mitter) during processing to correct errors as they
occur. Operations alerts the submitter when the job is
to be started, and the submitter acts accordingly.
C Category C requests are submitted for processing during
prime time (normally) with an "ASAP" turnaround time.
D Category D represents processing completion by 0800
hours the following morning.
E Category E requests are processed on a "time-available-
basis, " but must be completed no later than the time and
date specified on the Form 2737--usually at least 24 hours
after being submitted.
4. 4. 3 REQUESTING COMPUTER PROCESSING
Form 2737, "Computer Processing Request, " (reference Section VIII) must be
used to request all computer processing, regardless of category (reference 4.4. 2),
which should include all applicable run characteristics. Operations Division
schedules the Center's resources based (by category) on the general algorithms
described in paragraph 4.4.4.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 OCS POLICY AND PROCEDURES HANDBOOK
AUTHOR S TW(S) ~ )
gjw
SECTION (TITI-E)
REV NO.
DATE
IV PROJECT MANAGEMENT AND CONTROL
2
22 05 73
SUBSEGTION (TITLE)
PAGE
4.4 SCHEDULING COMPUTER CENTER RESOURCES
4.4- 3
PRIME-TIME SCHEDULING ALGORITHMS
Category A jobs are processed before all other jobs, regardless of their char-
acteristics. A .queue is reserved for A-jobs, and only under extreme situations
would they be aborted while being processed.
The ASP System has five initiators, each of which has its own queue with equal
priority. Following completion of A-job processing, the queues are filled and
scheduled according to certain setup and core requirement criteria. Under
special conditions, a queue with slack time may be loaded with jobs that don't
conform to the criteria for that queue. It should be noted that a job with the
least number of setups and least-required CPU time generally is scheduled
at a higher processing priority. Users should estimate their CPU time as
accurately as possible to take advantage of the scheduling algorithms (refer-
ence 4.4.4.2).
The JCL JOB card contains a TIME parameter to be used to specify maximum
CPU time, e. g. ,
/ /jobname JOB (suboperands), userID, REGION=nnnK,
/ / TIME=nnnn, CLASS=~A through E>
where, nnnK equals core size, and nnnn equals minutes (maximum four digits).
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 AUTHOR(S) TW(S) (INITIALS)
O POLICY AND PROCEDI)RES HANDBOOK
w
SECTION (TITLE)
REY NO. DATE
IV PROJECT MANAGEMENT AND CONTROL
2 22 05 73
SUBSECTION (TITLE)
PAGE
4.4 SCHEDULING COMPUTER CENTER RESOURCES
4.4-4
4. 4. 4. 2 ASP Scheduling Priorities
The criteria that determine priority scheduling under the ASP System range
from 00 through 09 (priority 02 is reserved for processing work by the
Center's operators). Classes A, D, and E are scheduled permanently for
processing as follows:
Class Priority
A 09
D O1
00
The criteria that determine scheduling priority for Class C jobs are as
follows:
Core
Run Time minutes)
Requirement
sl
s4
57
x12
sly
x1440
260
08
07
06
05
04
03
320
06
06
04
03
410
06
04
03
16383
03
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 AUTHOR(S)/TW(S) ( INlTlALS)
OC POLIGY AND PROGEDl1RES HANDBOOK
gjw.
SECTION (TITL.E)
REV NO. DATE
IV PROJECT MANAGEMENT AND CONTROL
2 22 05 73
SUBSECTION (TITLE)
PAGE
4.4 SCHEDULING COMPUTER CENTER RESOURCES
4.4-5
4. 4. 4. 3 ASP Print Output Priority
After job processing is complete, another set of criteria determines the priority
at which a job is printed, specifically the number of lines to be printed, except
in the case of Classes.A, D, and E jobs, as follows:
Priority
14
13
12
11
10
09
08
07
06
05
04
03
02
O1
00
Lines
s 1000
s 2000 and all Class A jobs.
s 3000
s 4000
s 5000
s 6000
~ 7000
s 8000
9000
x10000
X15000
?~
8.2 Computer Services Request Form (Form 930)
8.3 Speed Letter (Form 1831)
8.4 Prism Project Record (Form 2277)~~<
8. 5 Program Descripter Record (Form 2278)
8. 6 Format Specifications (Form 2337)
8. 7 Computer Request Form (Form 2737)>?<
8. 8 EAM Processing Request Form (Form 2875)
8. 9 OCS Charge Record Form (Form 2865)~~
~~Chapter Completed
FORM 3 ~prov
7?fi9 - (08.13.35)
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
_!
SECTION
Office of Computer Services
POLICY i~ND PROCEDURES HANDBOOK CHAPTER
SECTION (Title) - DATE
Forms
Re
d
,
cor
s, and Requests 9 February 1970
CHAPTER (T:t e) --- __
Design and Procurement of Forms
8.1.1. OCS Records Manager
The OCS Records Management Office is responsible for
revising and reordering existing forms and approving new
forms. All action taken on forms will be coordinated through
the OCS Records Management Officer.
8. 1. 2. Request for Additional Forms
Stock replenishment is controlled by the Office of Logistics.
Periodically, they send a Form 30A to the OCS Administrative
Office, indicating the amount of forms they have on hand and what
action is recommended. If additional forms are required, the
administration office prepares a Form 70 and submits it to Forms
Management Services,
8.1.3. New Forms or Revisions to Existin Forms
Forms may be created or revised by submitting a REQUEST
FOR APPROVAL OF FORM (Form 30), along with example
form to your Division Chief. The form is evaluated and approved
by the Division Chief and then submitted to Records Management
Officer/OCS. After approval by the Records Manager, the form
is submitted to the Records Administration Staff, which is
responsible for coordinating the records and having the forms
printed.
8.1.4. Request for Special Printer Paler
Requests for a specific type of printer paper are initiated by
completing a REQUISITION FOR MATERIALS AND/OR SERVICES,
(Form 88), with subsequent approval by the Division Chief.
Processing of the form is coordinated through the OCS Supply
Officer and the Processing Control Branch of the Office of
Logistics who evaluate the forms for general use. After approval
of the form, the OCS Supply Officer officially requests the
printer paper from the Office of Logistics, It is the responsibility
of the requesting party to determine the size of the initial order
as well as the stock level to be maintained.
FORM q I
7.69 J (08.13.35)
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
C'Jffice of Computer Services
POLICY AND PROCEDURES HANDBOOK
SECTION (Title)
Documentation
CHAPTER (TYt e) `
PRISM Proiect Record (Form 22771
3.4.1. Purpose
9 Februar~1970
PAGE
The purpose of Form 2277 is to give OCS management effective
control over computer projects and to provide a unique identifica-
tion for each project.
The objective is to establish a project number and description
which, when associated with an appropriate user code, can be
used to summarize OCS activity related to a particular project/
customer, A degree of judgment is involved in defining the
scope of a project; e. g. , it is not desirable to establish a project
for each program or computer report and, on the other hand,
the scope should not be so broad that it will not provide meaningful
information about a particular area of interest.
Provision is made for pseudo-projects which consist of an
unbounded number of unrelated programs or sequence of programs
in which some explainable generic relationship exists. This should
be explained in the Brief Description of the project.
Form 2277 is submitted by the Project Leader whenever the
Division Chief or other appropriate official has approved the
project as an OCS task and responsibility. It is submitted to the
Director/Office of Computer Services in triplicate for approval.
A project number and title are assigned to be used in the PRISM
Project Register. From OCS, the form is sent (in triplicate) to
the Chief, Production Control Branch, where the project is
entered into the PRISM Project Register. The form is then sent
to the tape librarian, where the name of the person to receive
the tape lists is recorded. An approval copy containing the
appropriate project number and name is returned to the project
leader.
8.4. 2. Instructions for Completing Form 2277
1, Project Number - A unique three (3) position numeric job
identifier assigned by D/OCS after the form has been reviewed
and approved by D/OCS and C/PCB. When using this control
FORM ~ I
7'69 (08.13.35)
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Office of Computer Services
SECTION
8
POLICI~ AND PROCEDURES HANDBOOK
CHAPTER
4
SECTION (Title)
DATE
Documentation
~~
9 Februar~r 1970
CHAPTER (Ttt e)
PAGE
PRISM Project Record Form 2277
number, the two-digit alpha-numeric customer office code is
used as a prefix. This then becomes a five (5) position identifier
for all listings, cards, and storage data as well as machine
accounting.
2. Project Name -This is the short title assigned by the user
and is a maximum of ten (10) alpha/numeric characters, Most
users find it desirable to use an acronym as a meaningful short
title .
3. Date -Date of submission.
4. New, Change, or Deletion -Indicate one. If change or
deletion is noted, indicate disposition of data storage media.
5. Customer Office(s) -Enter the customer office(s).
6. Customer Code -Enter the customer code.
Note: The list of customer office and customer
codes is classified and is maintained separately
from this manual.
7. Send Tape Lists To -Enter person responsible for scratching
tapes.
8. Computers Used -Enter the computer(s) to be used.
9. Languages -Enter the primary computer language of
the project.
10, OCS Contact -Assigned by OCS. This should be an OCS
individual who has primary responsibility to the customer and is
most knowledgeable of the job requirements.
11. Customer Contact -Assigned by the user. This should be
the person and office that is requesting OCS service and the contact
for any questions or problems.
FORM q I~Ji (OB? 13.35)
7.69 J J
 ,_Appr~oved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
?ffice of Computer Services
POLIO AND PROCEDURES HANDBOOK
SECTION (Tit e)
Documentation
CHAPTER Tlf e
I~RT,r,M Project RP~c~rd (Form 2277)
SECTION
CHAPTER
9 F
4
ebruary 1970
12. Brief Description of Project -This should be a general
description of the particular project and its objectives. It should
include information on the purpose, type of activity, products,
and any other pertinent information (limited to 150 positions of
data,),
13. Submitted By -Enter the name of the submitter.
14, D/OCS -Approved by D/OCS or his representative.
15, C/PCB -Received and registered by C/PCB; project
number is assignede
16e Tape Librarian -Notifies librarian of the new project
nurnbe r ,
FORM
7.69 ~ (08-13.35)
 Office of Computer Services
SECTION
8
POLICY AND PROCEDURES HANDBOOK
CHAPTER
SECTION (Title) ~
TE 7
DA
-------
/
V February 1970
-- _ _
CHAPTER Tit e
PAGE
om uter Pro es"sin a nest orm 273
~
,,,
~
8. ?, 1. General
The Computer Processing Request Form comprises an
original and two copies. To submit a job for computer process-
ing, the form must be filled out and submitted with the job.
Copy three (3), after time stamping, will be returned to the
job submitter as his receipt and authorization to pick up the
completed job. The first two copies are retained by Opera-
tions. Instructions are printed on the back of each 2737,
When copy three (3) is ,presented to pick up work, the last
name and initials of the individual to whom this job is released
is entered in the "Released To" box. Copy two (2), with
appropriate operations comments, and copy three (3) are
returned to the submitter. Copy one (1) is retained by Opera-
tions
If copy three (3) has been misplaced, it will be the responsi-
bility of the job submitter to insure that it is not presented to
the Computer Coordination Staff by an unauthorized individual.
This could result in a violation of security or in release of
proprietary data to an unauthorized individual.
8. 7. 2. Instruction for Completing Form 2737
LOG NUMBER - A unique log number is preprinted on each form.
The submitter enters his office code preceding this log number.
Office codes are classified and are maintained separately from
the Procedures Notebook.
RUN OF - It is anticipated that normally "1 of 1"
will be entered here. If it is necessary to have jobs processed
in sequence, then explicit instructions should be entered in the
special instructions space as to the steps the operator should
take if one of the jobs terminates abnormally before the success-
ful completion of all jobs.
TIME IN -Filled in by Operations Division; indicates time when
the request is received.
FORM
7.69 ~ (08.13.35)
A roved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Office of Computer Services
SECTION
8
POLICY AND PROCEDURES HANDBOOK
CHAPTER
7
SECTION ( it e) -
DATE
Documentation
~~~~ ~---~ -
6 February 1970
CHAPTER Ttt e)
~~
PAGE -T~_
Com uter Processin e Form 2737
TIME AVAILABLE -Filled in by Operations Division; indicates
time when the job is ready for pick-up.
TIME RELEASED -Filled in by Operations Division; indicates
time job is picked up by the customer,
PROJECT NUMBER - A five-digit control number assigned to
each job by the submitter. The first two digits are the office
code of the office for which the job is being processed, and the
last three digits are the project number as assigned on the
PRISM Project Record Form 2277 (see Section 8.4)
Note: OCS should only be charged for test
runs if the production runs will be
charged to OC5.
PROJECT/PROGRAM NAME -The valid project name that has
been assigned and approved on the PRISM Project Record
(Form 2277). Can be followed by program name if desired.
O/P CLASS -The security classification of output data. (Include
an indication of any special systems control. )
MACHINE USED -The major computer on which the job is to be
processed; e, g. , 360/65, Spectra ?0/45, etc.
SUBMITTER'S NAME AND EXTENSION - Submitter's last name,
initial, and telephone extension.
EST. RUN TIME -The estimated run time in minutes on the
major computer used. A) MVT or Time Sharing =estimated CPU
time. B) Other =estimated elapse time.
MAX. RUN TIME - A) MVT =maximum time allowed before the
system cancels the job. B) Other =the maximum run time in
minutes a job should be allowed to process before being terminated
by Operations.
FORM
x.69 3~ 108.13.36)
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Of?~ice of Computer Services
SECTION
s
POLICY iat~ID PROCEDURES HANDBOOK
CHAPTER
7
SECTION (Title) ~
DATE
Documentation _ ~~_ _
-- -
6 February 1970
- --
CHAPTER TYt e) _
PAGE
Com uter Processin Re uest r 2
DATE AND TIME NEEDED -This should be a realistic indication
of absolute requirements and is used with Requirement Cate-
gories A, B, and E only.
RELEASED TO -Signed by person to whom job is released.
REQ CATEGORY -Filled in by the submitter with the proper
category code. (Refer to 4, 3. 2. Requirement Categories. )
TYPE OF RUN -Checking the box to the left of "OS" indicates
a 360/Operating System run; a run other than OS MVT is indicated
by checking OTHER and entering designator (e. g. , 360/20,
70/45, etc.) in the space provided. Also, the appropriate word
designating the process, i. e. , test or production, must be
checked. If the job library is to be updated, check LIB UPDATE.
VOLUMES -Device -Refer to legend on back of the form and
fill in appropriate code, For direct access devices, indicate
only other than system volumes. Unit -Refer to legend and fill
in appropriate code. Volume No. - (a) Tapes -Required from
user for input. Entered by operator for output. (b) Direct Access
Devices -Required from user for input and output. I/O - Enter
"I" for input volumes or "0" for output volumes. Density -
Refer to legend and fill in appropriate code.
Disposition -
(a) Tapes -When using the code T (Temp Save) the number of
days the tape is to be saved must be included in the following
format (T - X and X =the number of days to be saved, maximum
of 30 days). When a code other than S, T, or R is placed in the
blank for disposition, all pertinent information regarding printing,
punching, or plotting should be specified in the special instruc-
tions. This should include such information as BCD, Binary,
Odd Parity, Even Parity, 7-Track, 9-Track, Calcomp Plotter,
or Benson Lehner, etc,
If listing is requested, one or more of the following options
must be specified.
7.69 (08.13.35)
FORM 3153 ?
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Office of Computer Services
SECTION
8
POLICY AND PROCEDURES HANDBOOK
CHAPTER
~
7
SECTION (Tit e)
DATE
Documentation _ _________ _
6 Februar r~1970
_
CHAPTER (Ttt e)
_
PAGE
rm 2737
Program Control - ASA, machine code, 7010 or 7090 carriage
control characters must be specified.
Line Spacing -Single, double or triple must be specified.
Data Sets - If more than one, the number of data sets must be
specified.
If specific instructions are not provided, no action will be
taken. (This does not apply to the operating system standard
print tapes, )
(b) Direct Access Devices -Prior arrangements must be made
with the Operations Division for reserving or saving of any
direct access volumes.
Label -The label description entered on the in ut and output
volumes, The first word of a label should be a project name.
Also enter MOUNT MESSAGE. Referred to in the program
(see Le end).
Paper Size - If not filled in, 14 7/8" X 11" is assumed.
Number of Copies - If not filled in, one copy is assumed.
Form Number - To be filled in when requesting special form
paper only. (If not filled in, standard 14 7/8" X 11" is assumed. )
Carriage Tape - If not filled in, 11" standard is assumed. 60
lines per page is printed.
Train or Chain - If not filled in, PN is assumed.
PUNCH O/P -Check if punch output is produced.
CORE DUMP -Check if core dump is desired when job is
terminated because of operator action.
FORM - --r------ - -- --------- ---------- -
~-gg 315 (08.13.35)
 Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
Office of Computer Services
SECTION
s
POLICI~ AND PROCEDURES HANDBOOK
CHAPTER
7
SECTION (Title)
DATE
Documentation _____
~'_ ~~~~'-
_6 Febr~~~r~22
CHAPTER (Tit e)
PAGE
Cam uter Processin Re uest Form 2737
MAXIMUM CORE REQUIREMENTS -For MVT and Time
Sharing, the maximum core to be used must be
entered.
SPECIAL INSTRUCTIONS -Reserved for speci
al instructions
to Operations.
OPERATOR COMMENTS - To be filled in by Operations when
appropriate.
START/STOP TIME -This time includes set-up time. (Filled
out only for non-O/S processing. )
LEGEND
Unit Device
Disposition
NNN = Phys Address T =Tape
L =List Tape
XXX =Symbolic Device Name C =Data Cell
P =Punch Cards
D =Disk
PL =Plot Tapes
If this option is used, the Drive
PT =Punch Paper Tape
volume serial number
D -Dupe
indicated in the DD card
S =Perm Save~~
must be placed in the label
T =Temp Savex=
blank surrounded by
R -Release
parentheses.
Density
2 = 200 bpi
5=556 bpi
8 = 800 bpi
16 = 1600 bpi
~~~ Perm Save =Indefinite retention
=~~=~~Temp Save =Specified in days up to a maximum of 30 days
FORM q'~A
7.69 J 33 (08.13.351
 Office of Computer Services
SECTION
8
POLICY AND PROCEDURES HANDBOOK
CHAPTER
SECTION (Tit e)
DATE
Forms, Records, and Requests
19 February 1970
__
CHAPTER (T1t e)
PAGE
OCS Char e Record Form Form 28b5
8.9.1 Purpose
The OCS Charge Record Form has been designed with two copies.
Any time anon-OCS volume is brought into the Computer Center, this
form must be completely filled out and submitted with the volume.
Copy two, after time stamping, will be given to the submitter as his
receipt and authorization to pick up the volume. The first copy is
retained by Operations. The label portion of Copy one contains a
five-digit sequence number preceded by a "Z", which is attached to
the volume. While this volume is in the Computer Center, it should
always be referred to by this number.
When Copy two is presented to pick up a volume, the last name
and initials of the individual to whom this volume is released is
entered in the "RELEASED NAME" box of Copy one. Copy two can
be destroyed, Copy one is time-stamped out and retained by Opera-
tions. The "Z" label should be removed from the volume,
If Copy two has been misplaced, it will be the responsibility of
the submitter to insure that Copy two is not presented to Production
Control by an unauthorized individual. This could result in a viola-
tion of security or in release of proprietary data to an unauthorized
individual.
It should be noted that this system is designed as a means of
temporary storage only. Volumes entered in this system will be
held for thirty (30) days only and then returned to the user unless
prior arrangements have been made.
8.9.2 Instructions For Completing Form 2865
SUBMITTED BY The last name and first initial of the
submitter.
EXTENSION The telephone extension of the submitter.
OFFICE CODE The office code of the submitter (if unknown
or non-existent, enter office name).
LOG NUMBER If a given volume is to be linked to a computer
run, the log number of the #2737 should be
indicated here.
FORM
7.69
A roved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
3 (08.13.35)
 OE(1:'ice of Computer Services
SECTION
$
POLIO' AND PROCEDURES HANDBOOK
CHAPTER
9
SECTION (Title) -
DATE
Forms Records ,and Requests ~_
19 Februa~1970
CHAPTER Tit e)
PAGE
OCS Char e Record Form- Form 2865)
CLASSIFICATION The security classification of the volume.
(If the volume is blank and data is to be
recorded on it by OCS, the classification of
this data should be used. )
RECEIVED-DATE- The date and time the volume entered the
TIME Computer Center (time stamp).
RELEASED-NAME The last name and first initial of the
individual picking up the volume .
RELEASED-DATE- The date and time the volume leaves the
TIME Computer Center (time stamp).
DESCRIPTION Any descriptive information that can be
given about the volume (i. e. , the physical
label of the tape if there is one).
FORM
7.69
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
-J
(OB- 13.35)
 SEC
TION (Title)
Processing Standards
_ _._l~suly__~Z1~_
CHAPTER T.et e) 1136 Plotter
SECTION
Approved~1~la~s~~ : ~-78-03948A000 0020001-5
-
'~"'~------- -
5.18.1, General
The CALCOMP 1136 Plotter is now fully operational.
It has a 36 and 13 inch drum, 9-track input, and can
operate as an 1136 or a 565 simulator.
For details on the complete CALCOMP basic software
package, see Programming CALCOMP Pen Plotters, copies
of which are available from OCS/ATS, ext. 7331.
5.18.2. 565 Simulation
Plot data for the CALCOMP 565 Plotter can be plotted
on the 1136 if it is generated on a 9-track tape with
the following DD cards;
//GO.PLOTAPE DD UNIT=(2400 ? DEFEP,),LABEL=(~BLP),
// DISP=(NEW,KEEP),VOL=SER=CAL565
The actual plotting time will be reduced by a
factor of 2'~ and the amount of tape written by a factor
of 4.
5.18.3. 1136 Plotting
The 1136 will plot at over three times the speed
of the 565, and a much shorter tape file will be generated
(in some instances one-tenth as much) on the 360/65. If
the 36-inch drum is requested, you can plot up to 33
inches in the Y direction. If the 13-inch drum is
requested, you can plot up to 11 inches in the Y direction.
You should try to use the 1136 software rather than the
565 simulator to take full advantage of the shorter tape
record, which get$ the job off the 360/65 quicker, and
faster 1136 operation when it plots as an 1136 rather
than a 565 simulator.
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
?69 3153
(08.13.35)
 SECTION
Appra~iii~r~el~s~'1~D0~1'5/~B,CVOf~StDP78-03948 008100020001-5
POLICY AND PROCEDURES HANDBOOK CHAPTER
18
DATE
_1.5 July. _1971_
PAGE
1136 Plotter 2
5.18.4. Initialization
A call to PLOTS will initiate the PLOT subroutine
and assign the logical unit of the output device.
CALL PLOTS (EDEN)
where LDEV is the FORTRAN logical tape number for the
plotter output.
A DD card must be used to assign data set FTOnF001,
where n=EDEN, to an appropriate tape unit. Assuming
LDEV=8, sample DD cards follow:
//GO.FT08F001 DD UNIT=(2400 ? DEFER),
// LABEL=(,BLP),DISP=(NEW,KEEP),
// DCB=(i2ECFM=VS,LRECL=484,BLKSIZE=488),
// VOL=SER=PT1136
Note that you no longer have to set up a buffer in
your FORTRAN program, but you must assign your own
logical tape number and set up the DCB yourself. The
1136 has a fixed buffer size so you should use the DCB
parameters as shown above.
5.18.5. SYMBOL
The SYMBL4 subroutine is now called SYMBOL. A
dummy SYMBO4 routine, which in turn calls SYMBOL, will
be added in case you forget.
Calls to SYMBOL fall into two categories. The first
type plots a string of characters or. a single character
corresponding to the alphanumeric data defined by IBCD
when NCHAR~.
CALL SYMBOL (XPAGE,YPAGE,IBCD,ANGLE,NCHAR)
Approved For Release 2000/05/08 :CIA-RDP78-03948A000100020001-5
7.69 (08.13.35)
FORM 3153
 . - Stl. ~ 1 Vrv
Apprdu7'~dCl~~e~e~ ~29~'~'05~'~~A~$RDP78-03948
CHAPTER
POLICY AND PROCEDURES HANDBOOK 18
DATE
_l 5 J_u_ly _1971_
CHAPTER T1t e) ~~~ PACE
3
36 Plotter
5.18.5. SYMBOL (con't)
IBCD may be an array, a single variable, or a
character literal.
NOTE : NCHAR must ~.
TABLE 1 shows the characters available in the 360
SYMBOL subroutine. Three special characters that are
control characters and not plotted symbols are included
in the table.
Backspace {BS, HEX 11) causes the following
character to be plotted over the preceeding one.
Carriacle Return (CR, HEX 15) causes the following
character to be plotted below the first character in
the present call. The spacing between lines is 5/7
the height of the characters.
Null (NUL, HEX 19) is a null character and causes
a no space.
The second type of call to SYMBOL plots a single
symbol as selected by the integer value of INTEQ when
NCHAR