[PDF](+32👁️) Télécharger ibm :: sage :: SAGE Programming Agency 1971 pdf
From the bitsavers.org collection, a scanned-in computer-related document.
ibm :: sage :: SAGE Programming Agency 1971Télécharger gratuit ibm :: sage :: SAGE Programming Agency 1971 pdf
PREFACE
This manual is designed to familiarize Air Force personnel with the
unique mission of 26 NORAD Region's SAGE Programming Agency. Non-
technical language will be used so that both programmers and opera-
tions, command and staff personnel will have a common reference con-
cerning the scope of computer program design, documentation, mainte-
nance, and testing responsibilities. Lack of clear communications
between operations personnel (the users) and computer technicians has
probably been the single greatest impediment to effective use of any
computer system. This is an effort to minimize this difficulty.
i
20 August 1970
TABLE OF CONTENTS
SAGE Programmer Agency Mission Statement 1-1
The Computer Program 2-1
History of SAGE Programming Agency 3-1
Nature of the Job and the People 4-1
Work Functions (General) 5-1
Technical Tasks (Specific) 6-1, 6-2
Organization
Organizational Description 7-1
Organizational Chart 7-2
Functional Chart 7-3
Operational Design Process Outlined 8-1
Program Design Process Outlined 8-2
Version Production Process Outlined 8-3
Job Descriptions
Computer Systems Analyst ' 9-1
Computer Systems Programmer 9-2
ii
MISSION OF SAGE PROGRAMMING AGENCY
Provide technical programming support of SAGE computer programs to
insure that, at all echelons of command within Aerospace Defense Com-
mand, Commanders can:
1. Exercise timely command and control over weapons and weapons
support systems.
2. Conduct the air battle on a real-time basis.
3. Coordinate operational actions with and give support to oper-
ational echelons above, below, and adjacent to them.
4* Facilitate implementation of orders and instructions from
NORAD to NORAD Region Combat Centers.
5. Provide timely air battle information to the NORAD Combat Oper
ations Cent'er.
6. Maintain a high level of combat readiness through the use of
simulation, evaluation, and recording functions of the SAGE program
system.
1-1
THE COMPUTER PROGRAM
The computer cannot accomplish its functions unless responding to a
set of instructions. These instructions are known collectively as a com-
puter program. Discrete areas within this set of instructions are called
subprograms .
Each operation carried on within a Direction Center during the proc-
essing of an air defense problem is controlled by a separate subprogram.
All subprograms together constitute the SAGE program system called the
SAGE Operational Program.
The air defense program may be divided up into major functional
blocks such as the air surveillance or weapons direction area. The air
surveillance area consists of a group of subprograms which compile and
process information on air movements while the weapons direction portion
uses surveillance data to direct the defense of a given area with mis-
siles or manned aircraft. Some other major functional areas are displays,
simulation, data reduction, and recording. In each area, subprograms
perform a complex function automatically or semi-automatically as deter-
mined by operations personnel through a system of switch actions capable
of modifying the automatic features of the program system.
The SAGE Operational Program together with the facility and utility
program systems which support it is still the most complex computer pro-
gram system in operation today.
2-1
HISTORY OF THE SAGE PROGRAMMING AGENCY
Since 1965, Air Force personnel at Luke AFB have been developing
the capability to accomplish computer programming tasks required to
support the Aerospace Defense Mission.
In 1966, the SAGE programming contractor, System Development Cor-
poration, was tasked to train Air Force officers and NCO's to handle
program maintenance functions. The results of this initial effort
were highly successful. Air Force personnel rapidly acquired the tech-
nical knowledge necessary to handle routine site maintenance tasks.
Following this initial "Blue Suit" transition at all SAGE Direction
Centers and Combat Centers, 26 Air Division (then 27 Air Div) continued
training to handle test and acceptance as well as SAGE system maintenance
functions.
On 3 June 1968, 27 Test and Acceptance Agency was officially assigned
the responsibility for verification of contractor-designed computer pro-
grams and for system maintenance of these programs. By June 1969, the
success of Air Force personnel in handling their technical responsibilities
indicated that "Blue Suit" training should be further expanded to include
the more sophisticated programming functions of design and version pro-
duction.
In November 1969, Commander, ADC, ordered that plans be drawn up and
implemented to increase the capability of 26 Test and Acceptance Agency
to handle all SAGE computer programming functions performed by contractor
personnel. As a result, field site manning was reduced from nine to five
programmers and 26 Test and Acceptance Agency manning was increased by
twenty- one systems analysts and computer programmers. System Development
Corporation was contracted to provide training in those areas which Air
Force personnel required upgrading.
On 1 July 1970, 26 Test and Acceptance Agency was redesignated 26
SAGE Programming Agency (26DOSP) to more accurately identify the increased
scope of technical responsibilities.
Upon completing formal training (15 July 1970) Air Force systems
analysts and computer programmers began on-the-job training to develop and
refine procedures to design changes to the SAGE program system.
On 30 June 1971, 26 NORAD Region will accept full responsibility for
total technical support of the SAGE computer program system, thereby saving
ADC more than $3.5 million per year without reducing Air Defense capability.
3-1
O
THE NATURE OF THE JOB AND THE PEOPLE
The most common question asked of systems analyst/computer programmer
personnel is--what do you do and why is it necessary? Too often the
answer given is loaded with technical terms and abbreviations which con-
fuse the asker, establish a communications block, and ultimately result
in minimizing the effectiveness of programming support.
Changes to SAGE computer programs are a continuing requirement. Most
operational decisions affecting air defense strategy, tactics, weapons
design, weapons capabilities, and organizational configurations have a
major impact upon computer programs used within the system. In many
cases, these decisions can be implemented rapidly in current programs.
This responsiveness is directly related to the well documented SAGE pro-
gram system in existence. However, some operational changes may require
major changes within the program system. The impact of these major changes
may act as restraints to implementing changes or result in technical analy-
sis to find alternate or interim measures of satisfying operational require-
ments .
THE MAJOR TASK. OF 26 SAGE PROGRAMMING AGENCY IS TO CONVERT OPERATIONAL
REQUIREMENTS INTO CHANGES TO COMPUTER PROGRAMS . The translation of require-
ments from prose to computer language is a technical task which requires
the use of , many skills. Within 26 SAGE Programming Agency, analysts and
programmers have many different educational backgrounds which are needed
to handle technical tasks: Mathematics, engineering, and computer science
degrees are balanced by English, history, and general science education,
all of which provide a necessary supplement to Air Force training in com-
puter programming. In addition, the requirement for operational knowledge
of air defense functions is met by officers and NCO‘s who have been assigned
to SAGE Direction Centers as weapons controllers and aircraft control and
warning technicians for several years prior to training as computer pro-
grammers. This mix of technical and operational skills insures that realis-
tic responsiveness to operational requirements is obtained.
4-1
SAGE PROGRAMMING AGENCY WORK FUNCTIONS
Operational Design - Consists of designing and documenting changes to
the SAGE system as directed by ADC. Design Change Suggestions are
analyzed to determine feasibility, validity, and operational impact; a
document is produced which states how the Design Change will be accom-
plished.
Design Implementation - Consists of flow charting and otherwise document-
ing the program code required to implement the modifications specified
by operational design changes. The implementation process includes cod-
ing, testing, and submitting necessary changes to all technical documents
for publication.
Version Assembly - Consists of those technical tasks required to incorpo-
rate all approved changes onto a new SAGE Master Tape.
Version Testing - A series of realistic simulated environment tests and
live environment tests used to verify that the SAGE computer program
system operates according to system specifications.
Program Maintenance - Analysis and response to suspected computer program
problems reported by users and test personnel. The result of maintenance
tasks will' be timely repair of verified problems or clarification of
technical and operational documents which were referenced in the reports.
26 Air Division Support - To provide 26 Air Division operations with a
SAGE Master Tape configured to reflect the current Air Division environ-
ment. This tape is regularly updated to reflect changes to local geogra-
phy, telling capabilities, input sources such as long range radars, and
other characteristics unique to 26 Air Division.
5-1
SAGE PROGRAMMING AGENCY TECHNICAL TASKS
1. Requirements Analysis - to insure correct interpretation of require-
ments for a program change, identify intra/inter system impact, and iden-
tify a design for consideration.
2. Design Development and Evaluation - to select and specify the design
that will be implemented to meet Command requirements.
3. Documentation - to record and disseminate information necessary for
program design, testing, and updating operational specifications and user
document s .
4. Program Design - to develop program change specifications to satisfy
operational design requirements.
5. Program Coding - to add, change, or delete program instruction
sequences and encoded parameters so that changed programs satisfy program
change specifications.
6. Communications Pool Generation (COMPOOL, dictionary ) - incorporate
new or revised compool requirements.
7. Master Tape Production - reassemble all systems using the new compool
and load all programs on the newly assembled tape.
8. System Change and Correction Monitoring - the analysis of present
and future changes affecting the programs, equipment, and operational
procedures .
9. Operational Program Monitoring - providing quality control of the
operational computer program by monitoring program change documents and
implementing changes to maintain a high quality program system.
10. S ystem Adaptation - insuring that the local operational program
system reflects the current environment.. This includes data collection,
calculation, coding, verification, and the writing and publication of
required documentation.
11. Local Change Activity - the design, coding, and testing of approved
emergency changes, test changes, and other site-unique features loaded
(or to be loaded) on the local program tapes.
12. Tape Load - the mechanics of readying the computer program for
local use to include accumulating and preparing the load inputs, key-
punching, computer operation, and tape comparison/duplication.
13. Test Preparation - the development of test inputs, checklists or
event lists; the establishment of analysis methods and procedures; the
planning and coordination of test activities with other agencies.
6-1
14. Test Conduct - the performance of functions which verify or check
out the operational program systems, including manning of consoles,
monitoring test progress, generation of outputs, and the collection of
pre-planned data.
15. Test Analysis - the reduction of test output data, verification
of program quality, and documentation of test results.
16. Version Turnover Documentation - the preparation and publication
of information pertinent to the content and use of the new computer
program version.
17. Error Detection and Resolution - the recognition and categorizing
of program problems including investigation, reporting, and problem
resolution. This activity requires familiarization with the relation-
ship of the program to associated equipment and related operational
procedures .
18. Technical Communications - the activities required for the inter-
change of technical information including the production of formal
documents, the planning and participation in meetings and workshops.
19. Utility and Support Program Application - in depth knowledge and
use of those programs necessary for performing program maintenance.
20. Special Project Support - the application of programming skills
to the development and implementation of special projects designed to
improve air defense systems.
6-2
ORGANIZATIONAL DESCRIPTION
The SAGE Programming Agency is organized under 26 DCS /Operations
at Directorate level and is managed by a senior computer systems staff
officer who directs and coordinates the varied work functions involved.
Each systems analyst and programmer is assigned to one of the
Divisions within the Directorate which has responsibility for a segment
of the SAGE program system. Aircraft Control & Warning Technicians and
computer operators are assigned to those functional areas which best
use their combined operational and technical skills.
Analysts and programmers are responsible for acquiring and main-
taining current technical knowledge of operational specifications and
program logic within their assigned functional area as well as a work-
ing understanding of operational problems and procedures.
Interlaced with the formal functional organization and crossing
established organizational channels, a product oriented sub-organization
exists. Each product (SAGE Program Change) authorized by ADC is assigned
to a Product Coordinator in one of the functional Divisions. This analyst
chairs an analysis team and manages the design and implementation of the
assigned product throughout the production cycle of the change. The
technical work involved in operational design and design implementation
is accomplished primarily through this sub-organization of Product Coord-
inators. Quality control of over-all production is accomplished by the
Management Control Division which monitors the status of all products
and verifies quality and reliability.
Effective support of the SAGE system is provided through a coordi-
nated team effort within the SAGE Programming Agency as w^ll as active
liaison with operations and hardware maintenance personnel. Daily
contact with programmers at all SAGE field sites insures that program
problems are rapidly identified and resolved; timely preventative actions
provide maximum program reliability.
7-1
ORGANIZATION SAGE PROGRAMMING AGENCY
COMPUTER
OPERATIONS
BRANCH
DOCUMENT
SUPPORT
BRANCH
SAGE PROGRAMMING AGENCY FUNCTIONS
Management
Control
Division
Quality Control Monitoring
Training Coordination
Proficiency Evaluation
Design Monitoring
Management Analysis
Systems Testing
Canadian Forces Coordination
Utility
Systems
Division
Site Production & Reduction System J
Data Reduction
Reduction Unlimited (RUN)
General Item & Table Proc (GIANT)
Normative Operations
Recording Method (NORM)
SCORE
Universal Simulator (UNIS3M)
Weapons
System
Division
Interceptor Guidance
BOMARC Guidance
Air Defense Artillery
Weapons Simulation
Data Link
Displays
Switches
Northern Tier Project (NOTIP)
Surveillance
Systems
Division
Telling
Height
Real Time Quality Control (RTQC)
Radar Inputs
Tracking
Manual Inputs
Identification
Master Tape Assembly
Geography
COMPOOL
Facility Programs
S tar tover/ Switchover
Program Control
Reduction Systems Operation
Tape Load
Honeywell Programming
Technical Library
Document Production
7-3
OPERATIONAL DESIGN PROCESS
SYSTEMS
REQUIREMENTS
ANALYSIS
1. Define task: Feasibility, validity, operational advisability.
2. Analysis Team Meeting or consultation with other designers/
programmers.
3. Document all coordination and require Analysis Team Members to
sign off report.
SYSTEMS
OPERATIONAL
ANALYSIS
1. Detailed examination of design requirements in terms of:
a. Operational Requirements.
b. Impact on Ops Specs.
c. Impact on Program Systems Specs.
2. During production of first draft of Analysis Documents,
checklists/detailed document formats are used to insure that
full coordination has occurred.
DOCUMENT PRODUCTION
1. Analysis Reports.
2. Analysis Team Study Reports.
3. Design Ghange Suggestions.
4. Program Change Request.
5. Program Design Change.
6. Changes to official documents as a result of above.
8-1
PROGRAM DESIGN PROCESS
PROGRAM DESIGN
1. Program Design Specifications:
a. Flow Charts o
b. Prose Description.
c. Identify System/ Program Interface, Document/Compool/
Initial Data Changes.
2. Review of Design Specifications by Product Coordinators, Divi-
sion Chief, and Designers in other affected areas:
a. Are requirements being met?
b. Are Design Specifications detailed enough to permit
coding by any other programmer?
c. Is design rational cost effective?
Programming effort - Space - Program Operating Time.
PROGRAM CODING AND
SUBPROGRAM TESTING
1. Code from Design Specifications.
2. Produce a Test Plan:
a. Inputs/Outputs required to test each subprogram.
b. Test Tool available — are new tools required?
c. Define Initial Conditions.
d. Recording requirements.
e. Specify required environment and test methods.
PRODUGT TESTING
1. Subprogram Testing by Programmer.
2. Assembly Testing by Product Coordinator.
3. System Testing by Version Coordinator.
8-2
8-3
VERSION PRODUCTION PROCESS
SYSTEMS TESTING
1*. Allocation o£ new compool.
2. Reassemble all systems using
new compool.
3. Re-load Facility Programs,
Symbolic Correctors, and
Compool.
4. Overload base modifications
of operations programs.
5. Load Symbolic Corrector
History.
6. Load Initial Data.
7. Verify Base Maintenance
Master.
8. Load Initial Data for Test
Environment.
9. Cycle check Base Mainte-
nance Master.
1. Receipt and initial check
of each new product.
2. Prepare Product Test Plan.
3. Load Products weekly.
4. Perform Product Tests until
Product Acceptance:
a. On-Line Printout/
Desk Check.
b. Blue Room Tests IAW
Test Plan.
c. Open Problem Reports
Integrated Systems Test
Procedures:
1. Update ISTP Documents.
2. Develop Special Tests.
3. Prepare Test Tools:
a. UNISIM Tapes .
b. Duplex Sets of
SIM Tapes and
Duplex Telling
Tools.
c. SIM Tapes to
generate MORT
Recording req's
to analyze and
test Utility
and Support
programs .
d. ROSE: Replay
for Over-all
System Eval. ;
enables repeti-
tion of Identical
Test Conditions
for problem
analysis.
4. Prepare Test Scripts.
5. Run Tests.
COMPUTER SYSTEMS ANALYST
A. Job Descriptio n. Designs, develops, tests and/or maintains computer
programs and/or program systems to satisfy specific operational require-
ments .
B. Major Duties ;
1. Designs computer programs and/or program systems to meet operational
requirements by performing such duties as meeting with ADC representatives
and in-house users to establish and clarify program specifications, deter-
mining and recommending appropriate problem-solving methods and means to
accomplish desired objectives.
2. Develops computer programs from approved design specifications by
preparing detailed flow diagrams, writing computer language instructions,
devising appropriate tests for debugging and verifying programs, and
ensuring that the generated output conforms to design criteria and speci-
fications .
3. Maintains assigned programs by analyzing generated output and/or
error reports to detect, program deficiencies, determining and developing
appropriate error corrections, testing corrections to verify their accur-
acy, and incorporating subsequent modifications into original programs to
produce updated versions.
4. Designs, implements, analyzes, and supervises large-scale system
tests to verify that the computer program system operates under a wide
variety of conditions.
5. Responsible for preparing such documentation as design specifica-
tions, program descriptions, operating guides, and users’ manuals to assure
that the objectives, instructions, and unique features of assigned pro-
grams are communicated clearly and effectively to intended audiences.
6. Performs evaluations in the development, implementation, ar.d
maintenance of assigned programs including assessing existing software
of potential application, reviewing completed programs for possible
refinements, investigating the appropriateness of design change suggestions,
verifying that required modifications have been tested and integrated, and
ensuring that revisions have been made to affected documentation.
7. Maintains and applies a working knowledge of all equipment and
program interfaces to facilitate the testing and integration of assigned
programs ,
8. Determines and establishes realistic schedules to meet established
completion dates. Monitors and evaluates the progress of assigned projects,
and coordinates with external and internal users/operational representatives
to ensure an effective, reliable end product.
9-1
COMPUTER SYSTEMS PROGRAMMING OFFICER
A. Job Description . Performs beginning professional programming assign-
ments under the supervision and/or guidance of higher level programming
personnel.
B. Major Duties ;
1. Designs computer programs under the general direction of super-
visors or more senior programming personnel to establish and clarify pro-
gram specifications, determine and recommend appropriate problem-solving
methods and means to accomplish desired objectives.
2. Develops computer programs from approved design specifications by
preparing detailed flow diagrams, writing computer language instructions,
defining test requirements, and ensuring that the generated output
conforms to design criteria and specifications.
3. Maintains assigned programs by analyzing generated output and/or
error reports to detect program deficiencies, determining and developing
appropriate error corrections, testing corrections to verify their accuracy,
and incorporating subsequent modifications into original programs to
produce updated versions.
4. Designs, implements, and analyzes tests for computer programs to
ensure that new programs of modifications to existing programs conform
to design specifications.
5. Produces and maintains documentation pertaining to specifically
assigned programs to assure that their objectives, instructions, and
unique features are communicated clearly and effectively to intended
audiences.
6. Consults with supervisors and similar level programmers concerning
problems related to assigned areas, changes which affect areas beyond
immediate, assignments, and various programming tasks as required to affect
timely completion of assignments.
Zf
<-®"
DEPARTMENT OF THE AIR FORCE 26DOS 01 55-3
Headquarters, 26 Air Division (ADC)
Luke Air Force Base, Arizona 85301 10 November 1971
Operations
CODING CONVENTIONS & RESTRICTIONS
To standardize the assignment and control of final letter identifiers
for program correctors.
1. Responsibility . 26D0S personnel will comply with the following
coding conventions and restrictions in the generation of programs and/
or program coding for the SUOP system. The responsible division chief
may authorize deviation, after coordination with DOSM. Programs or
coding which are now in violation of the procedure specified in this
01 are to be corrected as the programs are upmoded, and/or a new corn-
pool generated.
2. References :
a. TM 3010, FAST Complex User Manual.
b. TM 3233, COSEAL Utility System Manual.
3. Coding Conventions :
a. Programs . All programs will be identified by a three (3) letter
symbolic name; i.e., TRK, W0M.
b. Program Mod Designators . The program mod designators will be as
follows :
(1) SUOP Operational Programs . The mod designators for these
programs will consist of two (2) letters. The first letter will denote
the type of program; i.e., DC = D, FAST = F, etc. The second letter
denotes the mod update identification; i.e., SIS DE, FCP FC.
(2) SUOP Pseudo Programs (Adaptations) . The mod designator
procedures are:
(a) Operations Tapes (Future and Current) . The mod desig-
nator will consist of a digit and a letter. The digit indicates the
version applicability and the letter denotes the sequence alphabetical
order of the modifications. The alphabetical designator will be changed
each time there is a corrector deck submitted; i.e., CXS IC = program
CXS , Version 51 applicability, the third change.
This 01 supersedes 26DOS 01 55-3, 19 Jan 71
OPR: DOSM
26DOS 01 55-3
(b). TNR , 25 and 75 Air Div Tapes . The mod designator for
these tapes will consist of two characters. The first being a unique
designator; T = TNR, X = 25 Air Div, and F = 75 Air Div; the second will
identify the modification using the letters A through Z and returning to
A. , i
Note : DOSC will maintain a log of all pseudo programs and their mod
designators. This log will be made available on request and it will con-
tain listings for both the current and future versions of all four (4)
types of configurations; Ops, TNR, 25, and 75 Air Div.
c. Tables . All tables will be identified by a three (3) letter
symbolic name and a digit; i.e., ARM0, TTY0.
d. Items . Items will be identified by a four (4) letter symbolic
name; i.e., TIDY , ARDI, etc.
e. Location Identifiers :
(1) Within main body of program, locations will be identified
by two (2) digits and a letter; i.e., 10A, 35N, etc.
(2) Final address or corrector pool locations will be identified
by two (2) digits and two (2) letters; i.e., 10AB, 35NC, etc.
4. Coding Restrictions are as follows :
a. Tags will be maintained in an alpha-numberic sequence in order
to facilitate troubleshooting and program correction.
b. The number of registers between program tags will be limited to
less than one hundred (100) to facilitate program modification.
c. Program constants will normally be located in the 60 region of
the programs.
d. Regions within a program will be referenced to by the two (2)
digit identifier; i.e,, 21 region, 35 region.
e. Areas of a program are defined as two (2) digits and a letter;
i.e., 15B area, 42A area.
f. Whenever possible, program adaptation will be contained in a
pseudo program. All references should be made to compool- defined items
and table tags.
g. Macro and Command instructions may not be utilized for opera-
tional programming.
h. CPO Tags . - Compool overrides (CPOs) are not to be used in pro-
gram assemblies.
2
26DOS 01 55*3
i. Reference to Compool . Reference to compool- defined items is
to be in symbolic form only; e.g., P0S31 TIDY; not FCL 12.
j. I/O Interrupt . An "add class" instruction must not be followed
by "STA" or "STAA" instructions because the "A" register may not be
cleared due to the I/O Interrupt feature.
k. The pseudo instruction "PGM" will appear in the second register
of all programs.
l. An extraneous exit from a TTB instruction should exit to an
address as if a legal value had been found.
m. SYC coding over deleted areas should be avoided because it
severely decreases the effectiveness of automatic updating tools.
5. Symbolic Corrector Card and Deck Conventions . The following proce-
dures will be adhered to by SPA personnel when generating corrector
decks for load to the SUOP and RUN systems.
a. Card column information for program data on SYC correctors is
contained in paragraph 1.2.1, Chapter 2, FAST User Manual.
b. Card column information for program data on COMPOOL corrector
cards is contained in paragraph 1.2.2, Chapter 2, FAST User Manual.
c. Card column information for program data on ETS corrector cards
is contained in paragraph 2.3, Chapter 2, FAST User Manual.
d. Card column information for program data on MOR0 card is con-
tained in Volume 2, Chapter 4, COSEAL Manual.
e. In order to assist in tape load and card handling procedures,
the corrector decks will contain the following additional information:
(1) SYC Card Columns :
0001 556 77 7 8
1587 893 01 2 0
AAA BB CCCC DDD EEEEEEEfG — -
AAA = Three (3) character program ident.
BB = Two (2) character program mod designator for correctors
to operational programs only. Pseudo adaptation program
corrector need not have these designators punched.
CCCC = Four (4) letter SUOP file ident. Applicable to IDT cards only .
17,58,72,80 = FAST Manual Content.
DDD = Three (3) digit sequence number, starting at 000 on the IDT
card and numbered consecutively through and including the
END card.
EEEEEEE = Seven (7) character corrector ident.
3
2 6 DOS 01 55-3
f = Modification/Reissue letter or digit.
G = Modification letter to a dash one (-1).
Sample idents in card columns 63 through 71:
PCs = 06Pc051, 22PC071A, 07PC0161.
MCs - 66MC059, 69MC010A, 66MC0521.
SPCs = SPC2555, SPC2599A, SPC26001A.
ARs * 22AR001 , 07AR002A, 20AR0011A.
NMs
i = 07NM001.
PD
= 07PD001.
Sample
Corrector Deck:
0 0
0 12
3 4
5
6
7 7
1 5
8 7 5
6 0
9
3
2 7
SKD DB
IPGD IDT
SKD DB
000
07PC061
SKD DB
C BPX
10BB
001
07PC061
10B +01
SKD DB
BPX
10BC
002
07PC061
SKD DB
END
003
07PC061
Note : All program IDT cards will contain the SUOP file ident in card
columns 8-11 and the program mod designator in card columns 40-41.
0
— t w —
(2) ETS Card Columns:
1
55
6
7
7
7
8
7
67
5
2
5
9
AAAA
BBBBBBBBB
C
DDDDEE
AAAA * Four (4) letter SUOP file ident. All cards.
17/56 * FAST Manual Content.
BBBBBBBBB = Same as columns 64 through 71 of SYC correctors.
C * Either P for production release values or S for site-unique
values.
DDDD = Master sequence number received from DOSC.
EE s Deck sequence number.
(3) C0MP00L Correctors will use the same additional informa-
tion card format as for SYC cards.
(4) MQR0 i
0
0
0-1
1
1
1
4
4-4
5- 5
5-6
1
6
8 0
2
6
7
4
7-9
4 7
9 2
AAAAAA
BBB
CCCCC
DDD
EEEE
FFFF
4
2 6 DOS 01 55-3
AAAAAA =
BBB =
ccccc =
*17/44 =
DDD =
EEEE =
FFFF =
MOR0 Identifier; i.e., MOR0 51.
Sequence number.
Compool and mod identifier.
Programmer supplied values per COSEAL, Volume 2, Chapter 4.
Unique entry identifier (octal value).
Indexing value (optional decimal value).
Number of registers to be recorded (optional decimal value).
*These will be the only values supplied by the programmer. All other
card columns will be assigned by DOSU.
HERBERT J. SUSKIN, Lt Colonel, USAF
Director of SAGE Programming Agency
DCS /Operations
5
DEPARTMENT OF THE AIR FORCE 26DOS 01 55-6
Headquarters, 26 Air Division (ADC)
Luke Air Force Base, Arizona 85301 11 November 1971
Operations
ADAPTATIONS AND INITIAL DATA CHANGE PROCEDURES
(66/69 MCs)
Establishes the procedures for updating the adaptation geography, and
initial conditions for the 26 NORAD Region and/or the Test NORAD Region
(TNR) environments.
1 . References :
a. TM 3255/XXX - Analytical Compendium, Volumes 1, 2, and 3.
b. 26DQS 01 55-3, Coding Conventions and Restrictions.
c. 26DQS 01 55-8, Program Errors.
d. 26D0S 01 55-10, SU0P Master Tapes.
2. Responsibility . 26D0S personnel will comply with the following
procedures when generating changes to either the Active Air or Test
environments .
3 . Terms Explained :
a. Test N0RAD Region (TNR). A SU0P tape containing the mythical/
live environment required by the SAGE Programming Agency (SPA) in order
to develop, test, and evaluate the new SAGE products/versions.
b. 66MC - A document produced in TPR format issued in support of
changes to the Region's Active Air Defense (AAD) adaptation, geography,
and initial conditions and when completely compatible, card for card,
with the TNR data base will be authorized for load to the TNR tape.
c. 69MC - A document produced in TPR format issued in support of
changes in the TNR environment , adaptation, geography and initial
conditions or to load AAD changes which cannot be loaded on a card- for -
card basis because of an effect on the mythical environment.
4. Procedures . When a requirement exists to change either the AAD or
TNR environments, the following procedures apply:
Supersedes 260PM 01 55-6, 21 Oct 69
OPR: 26DOSM
26DOS 01 55-6
a ^ The programmer will review the requirement, determine the type
of change required (a 66MC , 69MC, or possibly both), and obtain the
appropriate number (s) from DOSM.
b. If a PIR was the basis for the change, the programmer will close
it by indicating that the problem was due to an adaptation error, giving
the 66/69 number, per reference "c."
c. The programmer will develop, test, and evaluate the correctors.
The provisions of references "a" and "b" will be adhered to in the pro-
duction of the card decks .
d. When the programmer is satisfied that the correctors operate as
required, he will produce and submit a final draft of the MC, through
his division chief, to DOS for typing. The MCs will be in TPR format
and contain the following:
" 1 .
Subject/Title:
2.
System/Version/Program:
3.
Reference:
4.
Descriptive Data:
5.
Document Changes (to include,
changes to the TM-820 series
in exact format and content,
documents) :
6.
Miscellaneous Comments:
7.
Program Data:"
When
66/69 MCs are to be loaded to
both the current and the
future versions, the programmer will submit two corrector decks and two
load requests to DOSM.
f. When the required change is common to both the current and future
versions and the corrector deck is not completely compatible with the
future version, due to NMs or PDCs, a dash one (-1) change will be gener-
ated and submitted by the programmer.
g. The programmer will have DOSC produce the necessary tape load
request(s) and five (5) copies of a multi listing. He will complete the
tape load request(s), have it signed by his division chief, and submit
it together with the corrector deck(s) to DOSM, where they will be handled
as outlined in reference "d." He will deliver the five copies of the
multi listing to DOS, where they will be attached to the main body of the
MC.
2
DOS 01 55-6
h. When unclassified , DOS will produce five copies of the MC,
attaching the multi listing. When completed, DOS will notify the
programme*- that the MC is ready for proofreading.
i. When classified , DOS will produce three copies of the MC,
attaching the multi listing. When completed, DOS will notify the
programmer that the MC is available for proofreading.
j. When the programmer is satisfied that the MC is correct, he
will forward the MC to DOSM for coordination and distribution. If
classified, he will forward a Document Coordination Sheet (26AD Form
70) to DOS and DOSM for coordination, to DOSC in order for them to
extract the classified TM-820 changes, and to the other division
chiefs for their information.
5 . Pi s tr ibution :
a. When unclassified , five copies will be distributed as follows:
(1) The original to the issuing programmer for the Area Note-
book.
(2) One copy to DOSM for inclusion into the appropriate Ver-
sion Description (VD) and then for file.
(3) One copy to DOS for his information and then for the DOS
read file.
(4) One copy each to the 2 6 NR BUIC sites.
b. When classified , three copies will be distributed as follows:
(1) The original filed in the DOS safe. A document coordina-
tion will be circulated through DOS, DOSM, and the other division
chiefs for their information.
(2) One copy each to the 26NR BUIC sites.
6. Attachments:
a. Attachment 1 contains a listing of all the SUOP adaptation
programs and the responsible divisions.
b. Attachment 2 contains a listing of all the SUOP initial condi-
tions, table blocks, and the responsible divisions. Reference "a' 1 will
be used to determine whether an item is site unique, production release,
optional, and the authorized values.
HERBERT J. SUSKIN, Lt Colonel, USAF
Director of SAGE Programming Agency
DCS/Operations
2 Atch
1. Adaptation Programs
2. Initial Conditions Assignments
3
26DOS 01 55-6
ADAPTATION PROGRAMS AND RESPONSIBLE DIVISION
Program
DOS Divi
AAA
DOSW
APP
DOSC
BAP
DOSW
BUG (50 Region)
DOSW
BUK
DOSS
GAP
DOSC
CXA
DOSS
CXS
DOSS
DAD
DOSW
FLO (50 Region)
DOSS
GFR
DOSS
GUM
DOSW
GUV
DOSS
LUV
DOSS
MAG
DOSW
MHA
DOSS
MIA
DOSS
MOM
DOSS
RCP
DOSW
SAD
DOSW
SMB (50 Region)
DOSW
SSS
DOSW
TEE (50 Region)
DOSS
TOT
DOSS
TRN (50 Region)
DOSS
TRU
DOSS
WAM
DOSW
YAK
DOSW
YXN
DOSS
Attachment I
4
26DOS 01 55-6
ADAPTATION PROGRAMS AND RESPONSIBLE DIVISION
Program
DOS Division
AAA
DOSW
APP ;
DOSC
BAP
DOSW
BUG (50 Region)
DOSW
BUK
DOSS
GAP
DOSC
CXA
DOSS
CXS
DOSS
DAD
DOSW
FLO (50 Region)
DOSS
GFR
DOSS
GUM
DOSW
GUV
DOSS
LUV
DOSS
MAG
DOSW
MHA
DOSS
MIA
DOSS
MOM
DOSS
RCP
DOSW
SAD
DOSW
SMB (50 Region)
DOSW
SSS
DOSW
TEE (50 Region)
DOSS
TOT
DOSS
TRN (50 Region)
DOSS
TRU
DOSS
WAM
DOSW
YAK
DOSW
YXN
DOSS
Attachment 1
4
DOS 01 55-6
h. When unclassified , DOS will produce five copies of the MC,
attaching the multi listing. When completed, DOS will notify the
programmer that the MC is ready for proofreading.
i. When classified , DOS will produce three copies of the MC,
attaching the multi listing. When completed, DOS will notify the
programmer that the MC is available for proofreading.
j. When the programmer is satisfied that the MC is correct, he
will forward the MC to DOSM for coordination and distribution. If
classified, he will forward a Document Coordination Sheet (26AD Form
70) to DOS and DOSM for coordination, to DO SC in order for them to
extract the classified TM-820 changes, and to the other division
chiefs for their information.
5. Distribution :
a. When unclassified , five copies will be distributed as follows:
(1) The original to the issuing programmer for the Area Note-
book.
(2) One copy to DOSM for inclusion into the appropriate Ver-
sion Description (VD) and then for file.
(3) One copy to DOS for his information and then for the DOS
read file.
(4) One copy each to the 26NR BUIC sites.
b. When classified , three copies will be distributed as follows:
(1) The original filed in the DOS safe. A document coordina-
tion will be circulated through DOS, DOSM, and the other division
chiefs for their information.
(2) One copy each to the 26NR BUIC sites.
6 . Attachments :
a. Attachment 1 contains a listing of all the SUOP adaptation
programs and the responsible divisions.
b. Attachment 2 contains a listing of all the SUOP initial condi-
tions, table blocks, and the responsible divisions. Reference "a 11 will
be used to determine whether an item is site unique, production release,
2 Atch
1. Adaptation Programs
2. Initial Conditions Assignments
optional, and the authorized values.
HERBERT J. SUSKIN, Lt Colonel, USAF
Director of SAGE Programming Agency
DCS/Operations
3
* /* * >
DEPARTMENT OF THE AIR FORCE 26DOS 01 55-7
Headquarters 26 Air Division (ADC)
Luke Air Fcrrce Base, Arizona 85301 7 December 1971
i
v Operat ions
CODING SHEETS AND KEYPUNCH PROCEDURES
Establishes the procedures for DOS progrannners to have cards (AF Form
1500) keypunched and standardize the numbers, letters, and special
characters to be used.
1. General. LGK-MR has indicated that they will assist in keypunching
cards for DOS programmers on a work load-permitting basis.
2. Responsibility . DOS personnel will comply with the following pro-
cedures when requiring assistance in keypunching cards.
3. Procedures :
a. Individual programmers will:
(1) Fill out the programming coding sheet (ADC Form 298),
insuring that all numbers, letters, and special characters adhere to
Attachment 1.
(2) Turn in the coding sheet to NCOIC, DOS.
b. NCOIC will:
(1) Have the coding sheet delivered to NCOIC, LGK-MR, in Build-
ing 241 on base.
(2) When notified that the cards are completed, have them picked
up and deliver both the coding sheet and cards to the H-200 operator.
c. H-200 operator will:
Produce an 80/80 of the card deck and notify the programmer that
his coding sheets, cards, and 80/80 are available for pick up.
HERBERT J. SUSKIN, Lt Colonel, USAF 1 Atch
Director of SAGE Programming Agency , Coding Symbols
DCS /Operat ions
This 01 supersedes 260PM 01 55-7 dated 20 October 1969
OPR: D0SM
-r
# 26DOS 01 55-7
EXAMPLE CODING SHEE7 MARKINGS
Letters
ABCDE FGHI JKL
MNOPQRSTlli/WX
Y Z
Numbers
1234 5 6789 /
Symbols
4 :
Attachment 1
26DOS 01 55-8
DEPARTMEN
Lire la suite
- 4.31 MB
- 15
Vous recherchez le terme ""
32
42
9492
