Software_Release_Bulletin_Jun79 Software Release Bulletin Jun79
Software_Release_Bulletin_Jun79 Software_Release_Bulletin_Jun79
User Manual: Software_Release_Bulletin_Jun79
Open the PDF directly: View PDF 
.
Page Count: 77
| Download | |
| Open PDF In Browser | View PDF |
.'",
Honeywell, .
()
-
SOFTWPtRE AElEf'1SE
SERIES 60
BlJllET~fl
LEVEL 66
SOFTWARE RELEASE BULLETIN
FOR
CP-6 APL, RELEASE 1.0
o
PRODUCT NUMBER
SFL 6121
JUNE, 1979
o
©
1979', Honeywell Information Systems Inc.
o
CONTENTS
o
Section I
Page
Introduction
1-1
Supporting Documentation
Section II
General Information
General Description
2-1
2-1
Section III
Installation Instructions
3-1
Section IV
Tips and Techniques
4-1
Section V
Known Errors
5-1
o
iii
APl.O
o
SECTION I
INTRODUCTION
This Software Release Bulletin (SRB) documents release
1.0 of the CP-6 APL processor.
This product operates on Control Program - Six (CP-6)
software on Series 60 Level 66 hardware.
SUPPORTING· DOCUMENTATION
The following document describes this product:
o
Title
Order Number
LADC
79-6
APL Language Reference Manual
"
o
1-1
APl-O
o
SECTION II
GENERAL~INFORMATION
GENERAL DESCRIPTION
APL is an interactive programming language designed for scientific
and engineering applications. In addition to being a powerful
language, APL is easy for the beginner to learn and use. APL
has also found ready acceptance in many accounting application
areas.
o
Highlights:
Operates under CP-6 as a shared processor
Compatible superset of the IBM APLSV program language
Batch or on-line operation
Operation from CP-6-supported terminals without APL
character set
APLSV features
File I/O capability
Fast formatted output
Compound statements
Transparent I/O
All normal CP-6 functions available at an APL terminal
o
2-1
APl.O
o
SECTION III
INSTALLATION INSTRUCTIONS
CONTENTS OF DISTRIBUTION
This product is distributed in the form of a Run Unit and is
included as part of the CP-6 Release Tape. The Run Unit is
identified as:
File Name:
APL
Account
:SYS
o
o
3-1
APl.O
o
SECTION IV
TIPS AND TECHNIQUES
This section contains information to assist the site in the
initial installation of this product.
o
1.
The CP-6 APL Processor, in its original BETA test release
form, is an absolutely plain run unit with well demarcated
procedure and data sections, no special privileges and no
overlays.~ -Subsequent releases will modi·£.y this
to add selected privileges and a single level overlay
structure. Any standard procedures used. to install processors
in the :SYS account are applicable to APL.
2.
The ZA6 module contains patch space as follows:
ZA6$PATCHI
ZA6 PATCHO
ZA6-PATCH6
(procedure)
(static . )
(constant )
100 words
120 words
20 words
Standard RUM patching mechanisms will be employed.
3.
Since sealed workspaces are given access controls which specify
APL as the access vehicle, it is inadvisable to install APL
'in accounts other than :SYS. Additionally, when processor
privi.leges a:.r.:e.added, they will be unavailable unless the :r:un
unit resides in:SYS.
o
4-1
.
APl.O
o
SECTION V
KNOWN ERRORS
This section contains a description of the known errors in this release.
ERROR
SEVER:I:TY
IMPACT
Response to asynchronous events
is incomplete
2
Disconnect, over limits,
error situations, ZAP and (i
a lesser extent) breaks can
result in a damaged
workspace.
Shared Variables
2
Results in a "Nonce" error.
Processor not yet overlaid
2
Procedure requires 55K as
opposed to planned 25K.
Status data is 3K per user
as opposed to planned 2K.
Slow Performance
2
Most operators are slower
than CP-V counterpart even
on 560.
Maximum memory feature authorization
not yet available to the processor
3
Oversized workspace files
cannot be copied into an
already large workspace
when user has a restricted
memory allocation.
o
o
5-1
Honeywell
()
SOFTWI1AE AElE"f1SE
BLJllET~r1
~~--------------------------------------------------------------------
SERIES 60
LEVEL 66
SOFTWARE RELEASE BULLETIN
FOR
CP-6 BASIC, -RELEASE 1.0
o
PRODUCT NUMBER
SFL 6122
JUNE, 1979
o
©
1979", Honeywell Information Systems Inc.
'"
BS1.O
o
CONTENTS
o
Page
1-1
section I
Introduction
Supporting Documentation
section II
General Information
General Description
2-1
2-1
Section III
Installation Instructions
3-1
Section IV
Tips and Techniques
4-1
Section V
Known Errors
5-1
Appendix A
Updates to Reference Manual
A-l
o
iii
BSl.O
o
SECTION I
INTRODUCTION
This Software Release Bulletin (SRB) documents release
1.0 of the CP-6 BASIC processor.
This product operates on Control Program - Six (CP-6)
software on Series 60 Level 66 hardware.
SUPPORTING DOCUMENTATION
The following document describes this product:
Title
Order Number
o
BASIC Language Reference Manual
LADC 78-9
o
1-1
BSl.O
o
SECTION II
GENERAL INFORMATION
GENERAL DESCRIPTION
BASIC is a programming language designed to· be easy to teach,
learn and use, allowing users with little or no programming
experience to create, debug and execute programs via an on-line
terminal. Such prog·rams are usually small to medium sized
applications 9f a computational nature. The CP-6 implementation
is a unified processor consisting of a root or service module
in continuous use, a compiler used during object program
generation, and an execution support module used during program
execution and utility operations.
It is a compiler, not an
interpretive processor, but differs from most compilers in
that object programs are generated directly into users storage
space and a separate 'load' process is bypassed. In this
implementation the compilation and execution processes are
in conununication via the continuously resident root module.
o
o
Highlights:
Conforms to minimal ANS BASIC standard
Conversa tion.al
Immediate syntax checking of input
Can be used in both on-line and batch modes
Editing and compilation/execution modes of 'operation
Direct execution capability
Fast in-core compilation
Efficient object code generation'
Minimum compiler core requirements
Safe/fast compile option
Extensive print editing and formatting capability
Extensive intrinsic functions and matrix operations
Computed GOTO capability (multiple-path branching)
File input/output capability
Chaining facility
Variable program size
Compilation and run-time diagnostics
Restore statement for re-use of data
Multiple line functions allowed
No fixed limit to the number of constants
Computation carried out in double precision or
single precision at user option
Chaining facility includes context preservation
2-1
BS1.0
o
SECTION III
INSTALLATION INSTRUCTIONS
CONTENTS OF DISTRIBUTION
This product is distributed in the form of a Run Unit
and is included as part of the CP-6 Release Tape. The
Run Unit is identified as:
File Name:
BASIC
Account:
:SYS
o
o
3-1
BS1.O
o
SECTION IV
TIPS AND TECHNIQUES
This section contains information to assist the site
in the initial installation of this product.
1.
P1ade run unit BASIC in :SYS to make it an unshared
processor.
2.
Patch space begins at the symbol '0'
One hundred words are provided.
o
o
4-1
BS1.0
o
SECTION V
KNOWN ERRORS
This section contains a description of the known errors
in this release.
ERROR
1.
o
SEVERITY
User Defined Function
capability not checked
. out
IMPACT
1
This feature may not
work properly
String arrays in single
precision will work
2 __
String arrays'. in double
precision mode are not
properly dynamically
redimensioned
2
3.
DET function not checked
out
2
4.
The statement "SHOW DIM"
with the blank following
the DIM gives an error
3
Without blank works
5.
Multiple use of AND and
OR does not compiJ.e
properly
3
Change to simple
logical statements
which work properly
6.
IF < relation statement>
THEN assignment does not
compile properly
3
Statement compiles
properly if LET is
used before the
assignment
7.
Compiler has not been
checked out in shared
mode
3
Compiler" works in
unshared mode
o
5-1
BSI.O
o
APPENDIX A
UPDATES TO REFERENCE MANUAL
The following pages represent updates to the CP-6 BASIC
Language Reference Manual, Publication number LADC 78-9
dated December, 1978. They contain descriptions of several
new features that were implemented since the manual was
printed. These features are in the following categories:
o
o
o'
New Edit Commands
New BASIC Statements
New BASIC Functions
o
o
A-I
BS1.0
o
New Edit Commands
1.
AUTO
The AUTO command causes automatic line numbering. If
an error is made in typing a statement, the line number
is repeated. Typing an unaccompanied carriage return
terminates the operation. The syntax is:
AUT [OJ.
[nJ[,mJ
where
n is .the starting line number.
m is the increment.
o
2.
BATCH
The BATCH command enters jobs into the batch stream.
no command is specified, a RUNH command is inserted,
following the command to load the specified file.
If
BAT[CH] [PW = passwordJ
[,
(command) J
fid
[, nJOB CARD options" J , [tlresource card"J
3.
BUILD
The BUILD command creates a file that contains embedded
commands and direct statements. The NSAVE, NRESAVE, NSEAL,
. FETCH, CFETCH and SEQUENCE commands are designed to
operate on build-mode type files.
The BUILD prompt is
a line number followed by a colon. BUILD mode programs
can only be edited using the BUILD conunand. The user
may type BUILD followed by the line number to be replaced.
When BUILD prompts with the line number, the user should
type the new line. Escape from BUILD mode is via a null
line (carriage return). The syntax is:
o
BUI[LDJ en] [,m]
A.-2
BSl.O
o
where
n is the starting line number.
rn is the increment.
4.
Build Mode Commands
The following commands are for use in conjunction with
BUILD mode.
a. NSAVE
The NSAVE command saves a file without line numbers.
The syntax is:
NSAlVEJ
fid
b. NRESAVE
The NRESAVE command resaves a file without line numbers.
The syntax is:
o
NREfSAVEJ
fid
c. FETCH
The FETCH command loads a file that does not have line
numbers. The fetched file must have been build by EDIT
or BASIC. The line numbers generated correspond to
the key of the record read.
FETICH]"
fid
d. CFETCH
The CFETCH command perform a clear and load of a non
line-number file.
CFEITCH] -
fid
e •. NSEAL
The NSEAL command seals and saves a non line-numbered
file.
The syntax is:
NSE[AL] .:- fid
o
A-3
BSl.O
o
f.
SEQUENCE
The SEQUENCE command renumbers (with pseudo line
numbers) a non line-numbered file (see BUILD) .
Although these files do not have line numbers in
their 'saved' format, pseudo line numbers are appended
when the program is 'fetched'. The syntax is:
SEQ[UENCE]
[ri][,m][,r]
where
n is the starting line number m is the increment
r is the range (see LIST)
5.
o
CALC
The CALC command allows entry of non-line numbered
statements. Expressions are evaluated and printed
when they are typed. The calculator mode prompt is
an asterisk. An unaccompanied carriage return
terminates the operation. The syntax is':
CAL~]
6.
CATALOG
The CATALOG command list either -the BASIC created files in
a given account or all the files, regardless of type.
CAT[ALOG][ACCT
=
account] [,ALL]
where
account
ALL
7.
specifies the account to be listed
specifies that all file types are t<;> be listed
END
The END command returns the user to IBEX (see SYS).
8.
o
FASTER/FASTEST
The FASTER or FASTEST commands cause a compile and execute
with greater levels of code optimization than either
RUN or FAST. The syntax is:
FASTER[Hl
FASTEST[H]
A-4
BSl.O
o
9.
GO
The GO command resumes execution a£ter a break condition.
The syntax is:
GO
Modified Edit Commands
RENUMBER
A range specification (same as LIST) has been added to
RENUMBER. The syntax is:
REN[UMBER] [n], [m], [rJ
n is the starting line number.
m is the increment.
r is the range.
o
o
A-5
BSl.O
o
New BASIC Statements
1.
IBEX
The IBEX statement passes the input string to IBEX for
"execution as an IBEX conunand. The syntax is:
[line]
2.
IBEX str-expr
IF ... THEN •.. ENDIF
A block structured capability has been added to IF ... THEN.
The synrax is:
IF
o
expr
sl
s2
THEN
sn
ENDIF
Note:
3.
IFs
may not be nested.
IF ... THEN ... ELSE
A block structured else clause has been added to IF ... THEN.
The syntax is:
IF
expr
sl
s2
THEN
sn
ELSE
sl
s2
sn
END IF
o
Note:
An ELSE clause may not contain an IF.
A-6
BSl.O
4.
LINK
LINK allows transfer to any load module in the system.
A command line can also be passed. The syntax is:
[line]
5.
LINK
str-expr [, str - exp]
PROMPT
PROMPT will set the runtime prompt character to any
string less than 32 characters long. The syntax is:
[line] PROMPT
6.
str-expr
WHEN
Two new forms of the WHEN statement have been added.
The syntax is:
[line] WHEN MONERR
[line] WHEN LIBERR
o
GOTO":'
GOTO
line I ERROR
line I ERROR
WHEN MONERR is similar to WHEN ERROR except that
it applys to· CP-6 monitor· errors only.
WHEN LIBERR is similar to WHEN ERROR except that
it applys to CP-6 common library errors only.
Modified BASIC Statements
1.
Successive involution .
... ·-Successive involutions are evaluated left to right as
~f required by the ANS standard.
Parenthesis are not
required.
2.
PRINT lists
A.print list cannot start with a colon.
o
A-7
BS~.O
o
New BASIC Functions
1.
DET
DET returns the determinant of a matrix.
DET
2.
The syntax is:
(aname)
Error functions
Three new functions have been added to augment the
WHEN statement.
ERT
o
returns the type of error:
1 = Monitor error.
2 - Common library error.
3 = BASIC runtime error.
LBE
returns the correct library error number.
Prints zero if no error.
MNE
returns the correct monitor error number.
Prints zero if no error.
o
A-8
Honeywell
_eJ
SOFTWflFiE AElEflSE BLJllETHl
SERIES 60
LEVEL 66
SOFTWARE RELEASE BULLETIN
-FOR
CP-6 FORTRAN, RELEASE 1.0
o
PRODUCT NUMBER
SFL 6120
JUNE, 1979
o
© 1979', Honeywell Information Systems Inc.
FTl.O
o
CONTENTS
o
Page
1-1
Section I
Introduction
Supporting Documentation
Section II·
General Information
General Description
2-1
2-1
Section III
Installation Instructions
3-1
Section IV
Tips and Techniques
4-1
Section V
Known Errors
5-1
o
iii
FTl.O
o
SECTION I
INTRODUCTION
This Software Release Bulletin (SRB) documents release
1.0 of the CP-6 FORTRAN processor.
This product operates on Control Program - Six (CP-6)
software on Series 60 Level 66 hardware.
SUPPORTING DOCUMENTATION
The following document describes this product:
o
Title
Order Number
FORTRAN Language Reference Manua
LADe 79-9
o
1-1
FTl.O
o
SECTION II
GENERAL INFORMATION
GENERAL DESCRIPTION
This language processor is a comprehensive algebraic progranuning
language consisting of a compiler and an extensive library of
subprograms.
It is a superset of most available FORTRAN
languages, containing many extended language features to
facilitate program development and checkout. The compiler is
designed to produce efficient object codes, thus reducing
execution time and core requirements.
Highlights:
o
Compatibility with American National Standard (ANS)
-The language elements are compatible with the ANS
FORTRAN 77 specification. Significant features include:
IF-THEN-ELSE statement
CHARACTER variables
Expanded I/O capabilities with OPEN, CLOSE, and
INQUIRE statements.
Features and Benefits:
Extended Language Features - Contains many language
facilities, not found in other FORTRAN systems,
which provide more flexibil.i ty and ease o£ use in
program development. The extended features are:
o
Extended assignment statements
N-dimensional arrays with generalized bounds
Expressions in output lists
Global variables
Generalized DATA statement
Generalized End-of-File processing
Generalized REPEAT statement
Automatic double precision
Generalized subscripts
Compound statements
Global statement labels
Direct I/O (define file)
2-1
FT1.O
o
INSTALLATION INSTRUCTIONS
CONTENTS OF DISTRIBUTION
This product is distributed in the form of a Run Unit
and is included as part of'the CP-6Release Tape. The
Run Unit. is identified as:
File Name:
FORTRAN
Account:
:SYS
o
o
3-1
FT1.O
o
SECTION IV
TIPS AND TECHNIQUES
This section contains information to assist the site in the
initial installation of this product.
o
The FORTRAN 77 compiler is a shared processor. It can be
run as either a strung out (non overlayed) processor, or as
an overlayed processor. The overlayed version of the processor
is about 1/3 the size of the non overlayed version of the
processor.· However, if the FORTRAN 77 compiler is, typically,
a heavily used processor on the CP-6 system, it would probably
be more advantageous to use the strung-out version of the
compiler instead of the overlayed version of the compiler
(faster terminal response time-no overhead for fetching of
compiler overlays) .
o
4-1
FT1.0
o
SECTION V
KNOWN ERRORS
This section contains a description of the known errors
in this release.
SEVERITY·
ERROR
Checkout of the Code
Generator has not been
completed
o
o
5-1
1
IMPACT
This product will be
completed and released
on August 30, 1979
...
,I
Honeywell
{\
SOFTWARE AElEPISE
BlJllET~rl
-~~-----------------------------------------------------------------------
SERIES 60
LEVEL 66
SOFTWARE RELEASE BULLETIN
FOR
CP-6 TEXT, RELEASE 1.0
o
PRODUCT NUMBER
SFP 6121
JUNE, 1979
o
©
1979, Honeywell Information Systems Inc.
BS1.O
o
CONTENTS
o
Page
1-1
Section I
Introduction
Supporting Documentation
Section II
General Information
General Description
2-1
2-1
Section III
Installation Instructions
3-1
section IV
Tips and Techniques
4-1
Section V
Known Errors
5-1
o
iii
TXl.O
o
·SECTION I
INTRODUCTION
This Software Release Bulletin (SRB) documents release
1.0 of the CP-6 TEXT processor.
This product operates on Control Program - Six (CP-6)
software on Series 60 Level 66 hardware.
SUPPORTING DOCUMENTATION
The following document describes this product:
o
Title
Order Number /
LADC
TEXT Reference Manual
79-8
o
1-1
TXl.O
o
SECTION II
GENERAL INFORMATION
GENERAL DESCRIPTION
TEXT is the text formatter of the CP-6 text processing system
that provides the capability to create, edit, and print documents
through typewriter-like terminals. The TEXT command language
is simple to use and-is oriented toward the nonprogrammer.
Secretaries, technical writers, and others not familiar with
computers can learn to use TEXT in a short period of time.
o
Highlights:
TEXT is a,- time and money saving aid in document preparation,
which features:
Automatic margin justification
,Automatic page numbering
Rapid accurate proof preparation
Reduced proofreading time
Rapid reprint capability
Rapid access and modification of data
Password protection of documents as required
o
2-1
TXl.O
o
SECTION III
INSTALLATION INSTRUCTIONS
CONTENTS OF DISTRIBUTION
This product is distributed in the form of a Run Unit and is
included as part o£ the CP-6 Release Tape. The Run Unit is
identified as:
File Name:
TEXT
Account
:SYS
o
Two data files are identified as:
File Name:
Account :
File Name:
Account
:ZTERRMSG
:SYS
:ZTH$HELP
:SYS
The file :ZTERRMSG contains the TEXT error messages; The file
:ZTH$HELP contains the data for the HELP option of TEXT.
o
3-1
"
TXl.O
o
SECTION IV
TIPS AND TECHNIQUES
This section contains information to· assist the site in the
initial installation. of this product.
TEXT is installed by boo:ting the CP-6 release tape.
installation actions are necessary.
No special
For differences between CP-V TEXT and CP-6 TEXT see the CP-6
Conversion Guide Section 4.l3~
For transfer of CP-V TEXT files see the CP-6 Conversion Guide
Section 6.7.
o
To obtain a brief description o£ all the TEXT formatting
commands, enter the following:
! TEXT X ON ME (HELP)
o
4-1
TXl.O
o
SECTION V
KNOWN ERRORS
This section contains a
this release.
descript~on
1.
The output to the line
printer is not yet
fully supported.
2.
If an option with a
parameter is specified
e.g. (HELP=CK) an
erroneous error message
is printed.
3.
The parameters A, E, and
o on header blocks and
footer blocks cannot be
used in arbitrary
sequence. Either A can
be used or E and 0 can
be used.
o
o
5-1
of the known errors in
3
The line printer can only
be used for proofreading
copies
3
None. It will be mentioned
in the manual
o
SERIES 60 LEVEL 66
SOFTWARE RELEASE BULLETIN
FOR
SORT/MERGE, RELEASE 1.0
PRODUCT NUMBER
o
JUNE, 1979
(c)
o
1979, Honeywell Information Systems, Inc.
o
CONTENTS
Section I
Introduction
Supporting Documentation
Page
1
0
o
Section II
General Information
General Description
2
Section III
Installation Instructions
2
Section IV
Techniques for Using
SORT/MERGE
3
Section V
Known Errors
4
Section VI
Shortfalls
4
I·
o
SECTION I
INTRODUCTION
This Software Release Bulletin (SRB) d09uments release
1.0 of the CP-6 SORT/MERGE processor.
This product operates on Control Program - Six (CP-6)
software on Series 60 Level 66 hardware.
SUPPORTING DOCUMENTATION
The following document describes this product:
o
Order "NUInber
Title
Draft
SORT/MERGE Reference Manual
o
2
o
SECTION II
GENERAL INFORMATION
The CP-6 Sort and M~rge p~ocessors provide all of the
functions planned for these products. Not all of these
functions have been fully t.ested and some are limited pend{ng
future operating system developments.
Initial ReteaseL{mitaf:.fonsand Restrict-ion:s:
Tape Processing
Although the Sort and Merge contain the-logic to
process tape fifes, this facility has not--been
thoroughly checked out.
Label Processing
There are several restrictions on user label processing:
1)
The s'tructured definition of the label buffers for
user label, processing -witt become- effective- _wi th
Monitor~~~rsiori R. -Until that ti~e, the labe~
buff~r ~iil contain only the-array of l~bels and
not t.he label count word~
2)
User labefs must be exact'ly 80 bytes long. There
may be no more than four labels piaced in the label
buffer by the user labeling subroutine.
3)
If the user lab~lI~g iubroutine takes an alternate
return, the Sort -or Merge witl come-to ~n abnormal
termination.
o
SECTION III
INSTALLATION INSTRUCTIONS
CONTENTS OF DISTRIBUTION
This product is distributed in the form of a Run Unit and·is
included as_part of the CP-6 Release Tape. The Run Unit is
identified as:
File Name:
SORT/MERGE
Account:
o
:SYS
-3-
o
SECTION IV
TECHNIQUES FOR USING -SORT/MERGE
Creating Run-Units with Coexistent Sort:
User programs that are to co-exist with a Sort execution
can be buil t in-to run -uni ts - in -'one of two ways:
o
~rograms
that can ~tilize fhe COBOL-shared subroutine
library may be linked as follows:
!LINK user-object-~riits,;
ZL_ELEMENT_OU, : LIBRARY ,XUP$PARSE. : LIBRARY, ;
OVER user-run-unit- (DCBSLOTS=34, SHAREDLIB=:SHARED~COBOLj
o
o
Programs that cannot utilize the COBOL s":i1.ared sUbroutine
'library may be liliked -as follows:
!LINK user-object-units,;
ZL -ELEMENT OU.: LIBRARY, ZL - SHARED OU. : LIBRARY ,
XUP$PARSE.:LIBRARY, CSEQU-::LIBRARYi
OVER user~run-unit (DCBSLOTS=34)
i
Creating Run-units with Coexistent Merge:
User programs that are to co~exist with a Merge execution
can be built into run~units in one of two ways:
o
Programs that can utilize_ the COBOL shared subroutine
library may be linke~ as follows:
!LINK user~object-units,;
Z-L ELEMENT
LIBRARY , XUP$PARSE. : LIBRARY , i
OVER user-run':':'unlt (DCBSLOTS=l7,- SHAREDLIB=:SHARED_COBOL)
au. :
o
Programs that cannot utilize the -COBOL shared subroutine
library may belink~d a~ f61l6ws:
!LINK user-6bject-units,;
ZL-ELEMENT OU.:LIBRARY,ZL SHARED OU.:LIBRARY,i
ZUP$PARSE.:LIBRARY,CSEQU.:LIBRARY;
OVE~ user-run-unit
(DCBSLOTS=l7)
o
-4-
o
SECTION V
KNOWN ERRORS
None at the present.
SECTION VI
SHORTFALLS
User label proces~ing will
second beta site.
o
o
ho~~b~ a~~ilabi~
until the
Hone)'"fell
o
SOFTWARE RELEASE BULLETIN
SERIES 60 (LEVEL 66)/6000
COBOL-74
SOFTWARE RELEASE BULLETIN
o
June, 1979
o
HONEYWELL INFORMATION SYSTEMS, INC., 5250 WEST CENTURY BOULEVARD, LOS ANGELES, CALIFORNIA 90045, TELEPHONE 213/649-6870
o
Sec. I
INTRODUCTION
Supporting Documentation
Memory Requirements
COBOL--74 Support of -OM-IV
Sec. II GENERAL INFORMATION
G-eneral Description of COBOL
COBOL-74 Interface with Systems Software
Invoking the Compiler
Compiler Options
Linking the OU
Executing the RU
Run-time Facilities
File I/O
SORT/MERGE
RW
DEBUG
IPC (CALL/CANC) LIT only
o
Sec. III COBOL-74 EXTENSIONS
Multiple-Entry Pt
User Label Proc.
Debug Schema
Initialize
Examine
Block Clause
Shorable User Object Code
Read into VLR
!.___ Charae1:er '.slew
Data name up to 32 Ch
Sec. IV
INSTALLATION PROCEDURE
.. _
-.~---.
"
.....
.. -----~-.-~--"- ...
--.•.-..
-~--
-------
""-
----.,
o
~-
.- -
--
-.....-~- -
------------------
Sec.-V
INVOKING THE COMPILER
Sec. VI
COMPILER OPTIONS
Sec. VII'
KNOWN ERRORS
Sec. VIII
SHORTFALLS FROM RELEASE 1.0 SPECIFICATIONS
Appendix A
~
Functionality Dependent on Language Interpretation
-
-1-
o
SECTION I
INTRODUCTION
This Software Release Bulletin (SRB) documents release
CP-6.l of the Series 60 (Level 66)/6000 COBOL fANS COBOL
X3.23~1974) compiler package.
This compiler packa'ge" is
hereafter referred to as COBOL-74.
This release of COBOL-74 is supported by Series 60 '(Level
66)/6000 hardware operating with CP-6 software.
SUPPORTING DOCUMENTATION
-
The following documents apply to this software release:
Title
CP-6 COBOL-74 Reference Manual
o
o
-2-
o
MINIMUM. MEMORY REQUIREMENTS
Systems on which COBOL-74 programs are to be compiled and
.' executed must have at least 70 K words of memory.
COBOL-74 SUPPORT OF· DM-IV DATA MANAGER
COBOL-74 is the host language compiler for the CP-6 Data
Manager I~D-S/II. COBOL-74 is used to process I-D-S/II
data when such data is in the COBOL-74 User Working Area
(UWA). This working area exists ..only if.I-D-S/II data is
to-be processed by the COBOL-74 program. Data is transferred
in and out of the UWA by I-D-S/II-routines.
o
o
-3-
SECTION II
o
GENERAL INFORMATION
GENERAL DESCRIPTION OF COBOL-74
COBOL is a programming language used throughout the world for
programming business data processing applications. The COBOL
language was developed by a group of computer users and manufacturers and the first documentation was distributed in April,
1960. Since then, COBOL has undergone many changes and
extensions resulting from manufacturer experience with COBOL
implementation and user experience- with COBOL programming for
Computers of many sizes and configurations. These changes and
extensions are embodied in this version of the language termed
ANS COBOL, x3,23-l974.
COBOL-74 is byte-oriented rather than word-oriented and all
character data is internally processed as eight-bit characters
rather than six-bit charac~ers.
COBOL-74 INTERFACE WITH SYSTEM SOFTWARE
The COBOL-74 relation~hip with system software is as follows:
o
---.-.-.. - . - . . . . .-.. . . . . -..-. O'--;h~
activity.
o
o
op:;~~~ng syst:m:~Ti~:-shaii:~
batch
control the various steps within the compilation
Interface with source input M$SI.
u
~'l
'~ (-}-~':e
-4-
o
o
, 0
Interface with job control language. '
Interface with update lines M$UI.
o
Places object code on object unit file M$OU.
o
Object program interface with input/output system
for logical and physical I/O.
o
Places diagnostics and hard copy information on
system output M$LO.
o
Interface with the Linker.
o
Interface with following intermediate files:
STARl
STAR2
STAR3
4 STAR
5 STAR
GSTAR
o
Consecutive
Consecutive
Random file
Consecutive
Consecutive
Consecutive
file
file
file
file
file
COBOt-74 RUN-TIME FACILITIES
COBOL-74 object programs are execut'ed in conjunction with
major run-time support packages which provide the, following
COBOL-74 run-time facilities:
o
File Input/Output facility
o
SORT/MERGE facility.
o
Report Writer facility.
o
Debug facility.
o
Inter-Program Communication facility.
(call "literal"
only)
File Input/Output Facility
COBOL-74 uses CP-6 monitor file management services to
accomplish the required file I/O for object program execution.
The I/O ,functions provided by CP-6 are as follo~s:
o
-5-
o
o
Sequential I/O:
Provides the capability to access records of a
file in established sequence. The sequence is
established when the records are written to the
file. "Sequentia.L" I/O "2l:lso" provides "f"or" :the "
"specification of rerun poi"nts "and the sharing
of memory areas among files.
o
Relative I/O:
Provides the capability to access records of a
mass storage file in either a random or sequential
manner. Each record in" a relative file is uniquely
identified by ~n integ~r value greater than zero
which specifies the record's ordinal position in
the file.
o
Indexed .I/O:
Provides the capability to access records of a mass
storage file in either a random or sequential manner.
Each ":record in an indexed file is uniquely identified"by' the value of a key within that record.
o
SORT/MERGE Facility
The SORT/MERGE facility provides the capability to order one or
more files of records, or to combine two or more identically
ordered files of records, according to a set of user specified
keys contained within each record. Optionally, a user may
apply some special processing to each of the individual records
by input or output procedures.. This special processing may be
applied before and/or after the records are ordered by the sort
or after the records have been combined by the merge.
Report Writer Fa'cili ty
The Report Writer facility provides for producing formatted
reports by specifying the physical appearance of the report
rather than requiring specification of the detailed procedures
necessary to produce the report.
o
A hierarchy of levels is used to define the logical organization
of a report~ Each report is divided into report groups, which
in turn are divided into sequences of items.. This hi~rarchial
structure permits explicitr"eference" to a report group with
implici t reference to other levels in the ~hie_archy..
A report
group contains one or more items to be presented on one or
more lines.
-6-
,0
The Report Writer facility emphasizes organization, format,
, and contents of an output report. Although a rep'ort can be
'produced using the standard COBOL language, the Report Writer
lang~age characteristics provide a more concise method for
· report structuring and report 'production. Much of the
Procedure Division coding which would normally be supplfed by
the user is instead supplied by the Report Writer Control
System (RWCS). Thus, the user is relieved of writing
procedures fo"r' moving data, constructing print lines, counting
lines on a page, numbering pages, producing heading and
footing lines, recognizing the end of logical data subdivisions,
updating sum counters, etc. All of these operations are
accomplished by the RWCS fr9m source language statements that
appear primarily in the Report Section of the Data Division of
the source program.
Debug Facility
The Debug facility assists in error detection by:
o
~elected
o
Monitoring trarisfers of, control to user
procedures durl.ng program execution.'
o
Monitoring values of user selected data items during
program execution.
The user suppl~_~d statements required to accomplish such
moni toring are inclu"ded in the source program and can be
compiled or not depending on the presence of absence of
the WITH DEBUGGING MODE clause in the source program. After
the user statements have been compiled into the program, they
can be' executed or ignored at object program execution according
to the, setting-of . a run--time., switch.. 'llhe d.ecisions concerning
what to monitor and 'what information to display on the output
device are explicitly at the discretion of the user. The main
purpose of the COBOL Debug facility is to provide convenient
access to such information.
Inter-Program Communication Facility
Inter-Program Communication is a facility through which a
program can communicate with one or more- other programs. The
communication is provided by the fOllowing:
o
o
The ability to transfer control from one program to
another program within a run unit.
o
The ability for both programs to have access to the
same data items.
-7-
SECTION III
o
o
o
COBOL 74 EXTENSIONS
0
Initialize
0
Examine
0
Block Clause
0
Multiple Entry Point
0
Debug Schema
0
COBOL-74 CP"':6 Options
0
Shareable User Object Code
0
CALL with Literal Name
-8-
o
MULTIPLE ENTRY POINTS
· The user may specify an ENTRY phrase
Division header of the Inter-Program
to allow multiple entry points to be
program. The syntax construct is as
PROCEDURE DIVISION
[ENTRY
[USING
in the Procedure
Communication facility
defined in a COBOL-74
follows:
data-name-l
section-name-l
J
[, data-name-2] ..•.
Gsection-name-2].
'"
J·
The first six characters of the section-name specified in an
ENTRY phrase must be unique in any given run unit of which
the referenced section is a member.
If both the USING phrase and the ENTRY phrase are present in
the Procedure Division header, the rules for calling a
section-name within an ENTRY phrase are identical to those
specified for calling a program-name.
o
.---------
THE CALL 'LITERAL' RESTRICTION
o
The CALL "literal" format must be used only to
invoke subprograms.
Refer to Section XIV of the COBOL-74 User's Guide for
additional information concerning inter-program communication.
o
-9-
o
SECTION IV
INSTALLATION PROCEDURES
This softwa"re release is supported by Series 60 (Level 66)
6000 hardware operating with CP-6 software. Systems on which
COBOL-74 programs are to be compiled and executed must have
at least 70K words of memory.
CONTENTS OF DISTRIBUTION
The following magnetic tape comprises the physical element
of this software release:
Software Library Number
Description
CP-6 Processor tape
o
o
-10-
o
CP-6 PROCESSOR TAPE
The CP-6 processor tape will contain the following files for
. COBOL:
File
Number
#1
Description
COBOL-74 compiler in system
loadable format
COBOL-74 run-time subroutine
object library
#3
o
o
COBOL/SORT shared library
~ll-
o
SECTION V
INVOKING THE COMPILER
The compiler-J.s invoked by using the standard invocation
line . . For example:
(over)
( ori ) (fid OU,) (fid L¢) (Options)
(onto)
where: fid SI
fid-UI
fid-OU
fid-LO
designates
designates
designa-tes
designates
a source input. file,
an update file,'
an output f'ile,
a lis,tingfile.
If an update file is specified, '1t must not be n-ull.
If an output file is not specified, the output unit will
be written to the *G file •
. If a listing file is not specified, the listing will he
returned to the terminal ~f entered from time sharing or
if the job is entered as a batch job, the listing will be
sent to the on=line printer.
..
o
o
.
..
,
For further information concerning. the standard invocation
line reference the Programmer '-9 Reference Manual.
-12-
SECTION VI
o
COBOL-74 COMPILER OPTIONS
The following -list represents the CP-6 COBOL-74 compiler
options. The (N) inaicates that th~ option is not to be
applied.
(M) indicates the minimal set of the option.
The - underline indicates those options that ar-e implied
if no options have been indicated on the'!COBOL JCL.
If
any 9ptions are specified, then all options tha-t are desired
must be explicitly declared.
(Reference CP-6 Processor
Standards and Conventions for detailed information on the
CP-6 compiler options.)
DESCRIPTION
OPTION
0
(N) SO _
new source file including updates
(N)OU
object unit is desired
(N)LS
source listing is desired
(N)LO
sYmbolic object listing de'sired
**
(M)PMtAP)
(N)
(M) DM (AP)
(N)
(N)WA(RN)
-,
data map list
list the warning messages
-(M) XR(EF)
(N)
create a cross-reference listing
SR (CH) (LIST) -
library f{le ~eaich list
(N)UI
update the source
*
o
procedure map list
(M) SC (HEMA)
(N)
create a debug schema
(N)UR(EF)
list unreferenced data items
The f6110wing list represents the COBOL-74 CP-6 compiler
options that are local to the COBOL-74 compiler.
-13-
o
o
Op·TION
COpy
DESCRIPTION
COPY' statements are included in the
source
DUMP
compiler dump if aborted
IDS
create an IDS sub-schema LIst
CLST
create a copy list
RESEQ
resequence the.source in columns 1-6
REPLACE
a repface clause is pres'ent
DEBUG
the
SUB
the source program being compiled
.is a" subprogram not a main program
sour6~ program contains debug
statements
If PMAP is declared, all En·-t:ry Labels, proc"edure labels,
section labels, and individual source statements should have
a corresponding relative memory location listed. IF MPMAP
is declared, unlabeled source statements should not have a
corresponding location listed.
If DMAP is declared, all Data Division entries should have a
corresponding relative memory location listed,. If MDMAP is
declared only level 01 or 77 data items will have the
corresponding relative location listed.
If SCHEMA is declared, all. schema items are included in the
debug schema. If MSCHEMA:is declared, referenced schema items
only will be included in the debug schema .. '
In the case where no options are indicated. (i. e., ! COBOL)
the compiler should assume LS, . QU, MSCHEMA·,~nvARN·. NWARN
is al.ways assumed unless specifically turned on (WARN).
If OU and NSCHEMA are specified with DM, or PM as other options,
the compiler will over-ride NSCHEMA w~th SCHEMA. If OU and
NSCHEMA are specified with LO, MDM,orMPM as qther options,
the compiler will over-ride NSC~EMA.· wi th MSHEMA.
o
-14-
o
SECTION VII
KNOWN ERRORS
•
1. If the user does not specify an OU file as the COBOL
invocation line, the compiler is to default to the *G file.
At the current time if an OU file is not specified the
compiler will abort. This error should not greatly impact
the user since an OU file is normally specified.
(Low
severity problem)
2.
If a COBOL program contains DISPLAY' statements, and if
the run unit of the program is executed from a remote terminal, the output from the DISPLAY statements will always be
displayed on the remote terminal. This problem could impact
users who want to direct this output to some other device
or file. (Moderate severity level.).
3. The SO option causes the COBOL Compiler to produce
binary output rather than the CP-6 format. This error will
not allow users to create new source files that have been
updated by UI files or COpy files.
(High severity problem.)
0
4.• Data names greater than 27 characters in length are
not processed correctly by the compiler. This problem should
. not place a burden on the user.
(Low severity problem.)
5. SWITCH STATUS - Several tests fail due to switch settings.
The problem may be in the incorrect setting of switches or in
the intepretation of the switches.
(Low severity problem.)
6. Three tests fail due to the incorrect sign on a single
character value.
(Moderate.severity problem.)
7.
The c'ompiler accounting is inco'rrect -- it always lists
the figure of 240K of core' as the space allocated to the
processor.
(Low severity problem.)
8. Call with "Literal Name" does not work for a test program.
(Moderate severity problem.)
o
-15SECTION VII
()
SHORTFALLS FROM SPECIFICATIONS
I.
To be rectified or implemented between now and
General Release 1.0.
A.
Keyed file processing.
B. -An M$DO facility for outputting diagnostic messages.
()
()
C.
Although use of the rerun, same area and multi-file
clauses are inappropriate for CP-6, the same area
clause should not produce an execution time error.
D.
RESEQ option availability
E.
User label processing to satisfy Sort and conversion
considerations.
F.
UNGMAP invocation by the compiler
·
• I
-16:-
.
o
APPENDIX A
FUNCTIONALITY DEPENDENT ON LANGUAGE INTERPRETATION
Two language items have been submitted to the American National
Standard COBOL Committee
(X3J4)
and
the
Federal
COBOL
Interpretation Committee (FCIC) for resolution. The results of
these interpretations may affect object code in future software
releases. The two items are:
1.
UNSTRING Statement
UNSTRING
identifier~
DELIMITED BY ALL (
id,entifier}
l~teral
DELIMITER IN identifier-5.
o
The Standard is not clear whether a single occurrence
of the delimiter is moved to the 'DELIMITER IN' field,
or all contiguous occurrences of the delimiter are
moved
to that field.
Currently, all contiguous
occurrences of the delimiter are moved
to·
the
I DELIMITER IN I
field.
However, since the CODASYL Journal ofDe~elopment
(JOD) was recently changed, the interpretation may
specify that only one occurrence of the delimiter can
be moved to the 'DELIMITER IN r field.
In the example:
UNSTRING identifier-l DELIMITED BY ALL
"AB" INTO identifier-4 DELIMITER IN
identifier-5, identifier-7.
Given:
o
ID-l
ID-4
ID-5
ID-7
PIC
PIC
PIC
PIC
X (10)
X(8)
X(8)
X(8)
VALUE 12ABABABCD n
VALUE SPACE.
VALUE SPACE.
VALUE SPACE.
If
•
...:
~
-17-
o
Currently, the results would be:
ID-4 :: l2l6l61616l616
ID-5 :: ABABAB16l6
ID-7 :: CD}ljlz$lz$lzSl6l6
possible results after interpretation:
ID-4 = l2l616}lj16l6l6
ID-S :: AB}616l6161616
ID-7 = CD
Recommendation:
If use of the
identifier}
••• ALL {
••• DELIMITER IN •••
literal
phrase of the UNSTRING statement is required, test
the contents of the identifier that receives the
delimiter for both a single occurrence and multiple
occurrences of that delimiter.
o
2.
COpy Statement
The Standard is not clear whether or not the COpy
statement is functional when it is used in a paragraph
within
the
Identification
Division
(within
a
conunent-entry). Currently, the compiler will attempt
to
process
the
COPY statement wheneve~ it is
encountered,
including
occurrences
within
a
conunent-entry.
interpretation being studied by the X3J4 and FCIC
committees suggests that if the COBOL word COpy does
not immediately follow the paragraph header where a
comment-entry may occur, the word COpy is part of the
conunent-entry and is therefore not functional. If
COpy is the first word following the paragraph header
within
the
Identification
Division
and it is
syntactically correct, it is a
functional
COpy
statem,ent.
An
o
-18-'
o
NOTE:
The CODASYL COBOL language
committee
has
deleted comment-entries from the JODi however,
this does not affect the current version of the
Standard (1974)"
Recommendation:
If use of the COpy statement is required within a
paragraph of the Identification Division, ensure
that the word COpy is the first word in the
paragraph.
(This
suggestion applies only to
paragraphs within the Identification Division.)
o
o
S R B OUTLINE
I.
II.
INTRODUCTION
A.
Purpose
B.
CP-6 Features
C.
Supporting Publications
HARDWARE CONSIDERATIONS
A.
Central System
B.
Front End Processor
III. RELEASE CONTENT
A. PO Tape
B.
Processor tapes
C.
Known Problem Areas
IV. INSTALLING CP-6
A.
Hardware preparation
B.
Booting
C.
Beginning Production
·,
.'
ROUGH DRAFT DQJBLE SPACE
for Larry Feldman
Page 1
o
S
R B
Introduction
Section 1
This Software Release Bulletin (SRB) describes the A90
release of Honeywell Control
• I
Program-S ix (CP-6) for Honeywell Seri es 60 Level 66 mainframes.
Included are summary
descriptions of significant features, the hardware requirements, a detailed list of release
contents with known problems designated, and a guide to installation of CP-6 on the·(as-th-e?} ',)_.
target hardware.
CP-6 is a comprehensive, multi-use operating system designed for Honeywell Series 60
Level 66 mainframes configured with Honeywell minicomputers.
Three operational modes
of access are provided:
o
o
o
0
Time sharing
. Batch processing
Remote processing
CP-6 supports these access modes with balanced service and no inherent emphasis on any
single access mode.
Programs do not require alteration to run in any particular access
These modes are designed to operate concurrently.
can be simultaneously resident in memory.
Several programs utilizing different modes
The system design allows the user to select only
the mode or modes required for a given task.
mode or multiple modes are used.
mode.
CP-6 perfoorms equally well whether a singl e
CP-6 functional elements are essentially the same for all
programs, regardl ess of the access mode.
CP-6 time sharing provides a highly productive environment suited to online program development
and debugging.
Features include:
o
Up to 500 interactive time sharing terminals may be connected to the system.
o
Rapid access and response from CP-6 creates an atmosphere in which each time
sharing user appears to have the entire system dedicated to his tasks.
o
o
Highly interactive response that is practically independent of system load.
o
Access to all types of peripheral devi ces.
o
Support of a wi de variety of terminals.
S RB
o
Page 2
o
Dynamic timing algorithms that can be set for each individual terminal.
o
Terminal access without translation, providing transparent control for special
pu rpose devi ces •
CP-6 batch processing provides maximum utilization of system resources by minimizing
conflicts in resource use.
Features include:
o
Up to 500 batch jobs can be processed concurrently.
o
Batch jobs can be submitted from on-line terminals or remote work stations.
o
Batch jobs are channeled into the stream best able to handle the individual
requirements of the job, consistent with throughput and resource constraints
determined by installation management.
o
System recovery preserves the batch queue.
CP-6 remote processing provides flexible communication between CP-6 and a variety of
s
'-;)
remote terminals using synchronou{protocols.
Features include:
o
Remote terminals and associated devices can be organized into work stations.
o
Work stations can range from a simple card reader/line printer combination
. to a complete,· large-scale computer system with an assortment of peripheral
o
devi ces.
o
Communication with any supported device at one or several remote sites.
o
Any time sharing terminal can be used as the operator's console for a
CP-6 work station
o
A CP-6 system can act as a central site to several remote terminals and as
a remote terminal to other computers, simul taneously. ,
o
Dynamic modification of workstation definition during system operation.
CP-6 FEATURES -"
CP-6 equals and exceeds the industry standards for performance, convenience, and costeffi ci ency.
EASE OF USE:
o
A simple, yet comprehensive execution control language that is common to all
access modes.
o
o
An extensive HELP facility that provides' information about the system and its
proces~ors
o
•
System default conventions that minimize the need for execution control commands.
.'
SRB
o
()
Page 3
Terminal personality that includes type-ahead, echoplex, and a variety of
escape and control key-ins, .providing an unparalleled interactive interface.
o
Qui ck term ina I response.
o
Program and data file compatibility
o
A comprehensive remote batch system that allows entry of jobs from a variety
In
all modes of access.
of terminals.
o
System I/O design allows the writing of handlers that permit access to special
devices.
o
The installation can supply command processors to tailor system use to specific
applications.
OPTIMIZED FILE MANAGEMENT:
o
A single central file management system.
o
Files are compatible across operating modes and language processors.
o
File access is device independent.
o
Graduated levels of file access security.
o
Comprehensive file backup system.
o
Fit e integri ty assured by system recovery.
o
Self-contained "sets" of disk packs provide removable public file segments.
"
o
AN EFFICIENT MONITOR:
o
Event-driven, priority-adjustable scheduler.
o
Full utilization of hardware addressing and security features.
o
Shared re-entrant programs and system processors.
o
A comprehensive, easily-accessed set of system services.
o
High I/O performance via tree-structure file indexes with several forms of
I/O caches and program disassociated buffering.
o
Multiprogramming and--multiprocessing. ':
MINIMAL OPERATIONS COST:
o
A small staff requirement for installation and system support.
o
Hardware is easy to maintain ••
o
System recovery does not require operator intervention and automatically
determines the appropriate level of recovery.
o
o
System can be run without an operator in attendance.
o
Online hardware diagnostics are available at time sharing terminals at both
local and remote sites.
·
.~
SRB
o
()
Page 4
On-line remote access software debugging and patching facilities are
available.
o
Full system use accounting.
SYSTEM HIGHLIGHTS:
o
An integrated performance moni tor that measures system performance
simultaneously with normal operation.
o
Majority of operating system and processing code is written in a highIevel structured language (PL-6).
o
A modern, extensive data base management system that is interfaced with
o
C(SO L, APL, FO RTRAN, PL-6, IDP, and assembly language.
\:;
Communi cation wi th other operation systems through ANS label ed tape and the
(.
HASP and 2780 communications protocols.
o
A sophisticated debugger that can be run in either the interactive or batch
environment, and which possesses a comprehensive set of functions suitable
for debugging FORTRAN, PL-6, COBOL, GMAP-6 and other language programs.
o
o
Common calling sequences generated by all languages, allowing programs
written in several languages to be loaded and run together.
I~
o.
I'
<'.. ,.
Up to 256 K word of procedure and data with up to 128 Kcord;) of data
addi ti ona I •
o
Superior hardware assures a secu re envi ronmen t.
o
More concurrent batch streams can be defined with priority, class, and
dependent job scheduling.
o
A common command language controls on-line and batch jobs.
o
Any standard remote or local terminal can be defined as an operator consol e.
o
APL, BASIC, COBOL, FORTRAN, RPG-II and TEXT are improved to a level
exceeding current commercial st·ate-of-the-art.
o
Hierarchical budget accounting for control of system charges and usage.
o
Remote communications concentrators provide fast local response, error control
over long lines, and economical use of lines via full-duplex protocols.
o
o
Comprehensive user documentation.
o
Additional file access methods, and the ANS labels and blocking methods are
supported.
*****
~9~~
)-L~~~~~
~~
a.-U~~
~-.
Title
Order No.
CP-6
CP-6
CP-6
CP-6
CP-6
CP-6
1'BO
TED
rrBO
TBO
TBO
TBD
........~~~-~.
LADC ID No.
78-1
79-10
79-3
79-11
79-12
79-9
Concepts and Facilities
Programmer Reference ~1anual
Monitor Services Reference Manual
System Support Reference Manual
Operators' Manual
DELTA Reference Manual
;TL ~..:LLL~ ~ ~L
~~~~~~;
~)~~~~~
~.~~~~.
-
LADe..
TBD
TBD
TBD
TBD
TBD
CP-6
CP-6
CP-6
CP-6
CP-6
TBD
CP-6
TBD
CP-6
TBO
TBD
TBD
TBD
CP-6
CP-6
CP-6
CP-6
TBD
CP-6
GMAP-6 Reference Manual
FORTRAN 77 'Language Reference Manual
COBOL-74 Language Reference Manual
SORT/MERGE Reference Manual
I-D-S/II Programmer Reference Manual For
COBOL-74 Users
I-D-S/II Data Base Administrator .Reference
Manual
Interactive Database Processor (lOP)
Reference Manual
TEXT Reference Manual
BASIC Language Reference Manual
APL Language Reference Manual
Report Program Generator II (RPG II)
Language Reference Manual and CP-6
Supplement
PL-6 Language Reference Manual
ID tJo.
79-13
79-7
79-2
78-10
79-4
79-5
79-14
79-8
78-9
79-6
79-15
78-5
S RB
ROUGH DRAFT
Larry Feldman
SECTION 3
Release
Content
The CP-6 release package consists of this document, the supporting documentation,
and two types of magneti c tapes; the fi rst type, known as the PO tape, is a bootobl e
copy of the CP-6 operating system, complete with the files and service processors
required to make CP-6 operational;
the second type, known as the processor tape(s),
consists of the remaining service processors, various unsupported tools found useful,
and language processors ordered by the customer.
The PO tape consists of the following:
o
AARDVARK, the bootstrap and mini-JIG system used to load CP-6 into memory.
o
Firmware for the tape, disk, and unit record subsystems.
Firmware tapes
are also distributed separately by Honeywell Field Engineering Division{FED).
o
A core image of the basic CP-6 monitor.
o.
XDELTA,.· the system debugger and patch processor.
o
TIGR, the Table Initializing and Generation Routine.
TIGR constructs
tables for the actual hardware running CP-6 and other system tables
related to installation defined parameters, e.g., total number of users
o
allowed _~:mthe system.
r'
S
GHOST, l\-i:ystem initialization ghost
GHOST 1 neads the sysf'em ghosf~
the servic'e processors and various control files from the PO tape .
...-'
The following system ghosts are present on the PO tape:
o
ELF
( Error Loggi ng Faci I i ty)
Logs system-detected errors on
permanent storage.
o
FEPANLZ
Debugs and down-line loads the front end processors.
o
INSYM
Processes job control card decks and terminal-initiated
batch jobs.
o
KEYIN
Processes input and output to the operator's console.
o
OUTSYM
Processes files destined for
spooled devices, e.g., line
printers and card punches
o
PRESCAN
Processes all batch JCL prior to submission to the multi-
batch-scheduler.
S RB
L. Feldman
Page 2
.. / )
(:"/
o
( Startup and Logon User Shost)
SLUG
Starts up all batch,
time sharing and ghost/~;ers on CP-6; log~ on remote operator's
y
consoles; mul ti -batch schedulei:--;)
o
TEMPLAT
Creates the operator interface used by K EYI N.
o
RCVR2: 2
In the event of a general system crash or single-user
l,
abort, generates a dump file of pertinent data for later analysis.
o
PIG
(Pack Initialization Ghost)
Controls the mounting and
access to the fi Ie management pack sets.
o
FROG
(Front - end Operations Ghost
Controls flow of
h "'·... i-,
certain messages between the front-ends
and the .Jast--s·Ystem.
The following service processors are on the PO tape:
o
CONTROL
Displays and sets values for various system parameters
which affect the performance and behavior of CP-6.
o
DELTA
The general purpose program debugger.
Performs patching of service processors.
o
EFT
(Efficient File Transfer)
o
IBEX
(Interactive and Batch EXecutive)
for CP-6.
o
lOGON
The file maintenance processor.
The co mmand program
It controls the flow of execution for all users of the system.
Initializes each user created by SLUG to default para-
meters established by SUPER.
o
pel
General purpose file transfer utility.
o
SPIDER
Permits dynamic installation, deletion, and replacemen~
of shared processors.
o
SUPER
Defines valid logon ids and establishes maximum and
(' Il.
default limits for users logging ~5 in those accounts.
o
VOLINIT
Initializes the headers on disk packs used by PIG and
performs surface checks.
The following control files are present on the PO tape:
o
::FEP
The down-line load file used by FEPANLZ to initialize
the front end processors (FEP).
SRB
L. Feldman
Page 3
o
~,FEPCTL
Contains the FEP configuration data.
o
~OCKEY
Contains the information defining the operator interface
of KEYIN.
r ", J-
/
~~)-
.....
o
OC!KEyiS
Source file used to create the :OCKEY file.
o
:OCMSG
Contains the information defining the format of output
messages generated by KEYI N.
1-
o
o
, " ).......
OC.::MSG_~S
f-
Source file used to create the :OCMSG file
CONTROL[s Contains a set of CONTROL commands defining
operational parameters and batch partitions.
o
:ERRMSG
Contains the text of all error messages generated by the
CP-6 operati ng system and its servi ce processors.
********
S RB
l . Feldman
KNOWN PROBLEM AREAS
This section of the SRB documents the currently known problem areas of CP-6;
a
problem is defined as a feature planned for general release which does not work in
the present integration (QUAIL).
The problems are broken down into three categories:
1.
Planned for general release, not in QUAIL.
2.
Planned for A¢q general release but deferred to later general releases.
3.
F¢q
CP-V features not in the
A~¢
CP-6 release.
The QUAIL problem list is in two sections, general capabilities and service processors.
GENERAL CAPABILITIES
Job Management
OA--t..
~
o
Full authorization checks for batch jobs .is not available.
o
Batch interface with system console does not have full complement of
messages.
Lo~)oV\
o
Fogo.:; password
scrambl ing is not performed.
Accounting
o
Job-step accounting is not available.
o
Forms accounting is not available.
o
Job history file is not complete.
o
Accounting staf"istics during recovery are not generated.
Resource Management
o
Allocation by attribute is not complete.
o
Online resource allocation is not available.
o
Authorization check is not performed.
Commun i ca tions
o
FEP information for STATS display is not available.
o
F EPCO N I the front-end control processor lis not avai labl e.
o
2780/3780 and binary (transparent) HASP support is not available.
o
Connection of CP-6 as a slave HASP workstation is not available.
,
S RB
L. Feldman
Page 2
o
Formatted printout of FEP dumps by FEPANLZ is not available.
o
L6XDELTA is not available.
o
A synchronous features not available:
--.
""""
.
- AUTOSAVE on line disconnect.
~
~
- Autobacd detection of any but 300 or 1200 batd terminals.
- Paper tape support.
- Logical pagination.
- ESC-W sequence.
0..-
- Read time-out.
Operatieft;r Interface
File Management
Recovery
Online Diagnostics
0
POLTS does not support CP-6 unit record devices.
0
COLTSis not a va iI a b Ie.
0
MOLTS is not available.
0
PACT is not available.
0
Independent distribution of FED diagnostic and firmware tapes is not available.
0
SYSCO N is not availabl e.
Error Lagging
0
C.PU startup/shutdown records. are not logged.
0
System identification records are not logged.
0
Timestamp records are not logged.
0
Diagnostic
0
Channel mailbox contents are not logged.
0
Resource exhausted entri es are not fogged.
0
MPC errors and statistics are not logged.
0
S i ngJ e-bi t correction errors are not Jogged.
0
Extended status on I/O errors is not fogged.
user is not logged.
f
S RB
L. Feldman
Page 3
I/O System RMA
o
Retry channel errors on different path
o
Retry on MPC errors is not available.
o
Thresholding of errors is not available.
IS
not available.
SERVICE PROCESSORS
o
[
IBEX features not available on incomplete!
- DISPLAY command options
- HELP command is not available.
- ACCEPT command is not available.
- TERMINAL command options.
- RELEASE command is not available.
RESOURCE command for online users is not available.
- CH ECK command is not available.
- STATUS command is nat ia~
- LIMIT command problem:
If user requests a service limit greater than he is
authorized for, a garbled error message is generated.
.j
- SET command problems:
2.
If more than one ACCESS option is specified, only the last is used.
If multiple serial numbers are specified as part of the fid, only the
last is used.
- Interactive problems:
If a command passed by ~~C results in an error other than syntax, IBEX
loo~n
2.
f
the error.
{:I
tarting a program uroer" DELTA while
In
control-Y
mode causes IBEX
- Call ing sequence probl ems:
J l f source field is not specified but abject or listaut fields are, the
i~pf'Fit DCB's are erroneously assigned.
~Lower case E or EDIT does not make it to the processor.
S RB
L. Feldman
Page 4
- GOTO problem:
~e
GOIO command is issued from a tenninal, the next command is ignored.
- BATCH command problem:
~~J!JOB
~ work.
card in the file to be batched is continued, the command will not
- SAVE command problem:
~s
o
[
for I BEX use a re no t pro tec ted fram a ! SA VE 0 VER fil e command.
LINK features incomplete or not available:
~~
brary searching for unresolved references
mporary run un i ts.
ertain privileges for the target run unit.
ssignment of DCBs to the related command line fields.
o
pel features incomplete ar not available~
[
- Certai n MOD IFY command options.
- Tabs handl i,ng is not correct.
-C ME I NTO IDS FILE does not work.
o
C RATES
features incomplete or not available:
- No known problems.
o
[
EDIT features incomplete or not available;
- No known probl ems
o
[
CO NTROL features incomplete or not available:
- No known probl ems.
o
[
SYSCON features inc~mplete or not ava~lable.
s, S Cot-J ___ ,~,t ",~!LI... ~ QUA JL
- Mopp~Ag-o-¥;'rttte,J-resot1rC"e-nome-int0--d8.\lr{;e7-10.M-number'1-ond-chonneJ-«
flumbet.-Q
o
[ .. SUPER features incomplete or not available:
- Synchronous device TERMINAL definition
- Various PROFILE options
- STATIO N definition
- WSN definition
- DEVICE definition
-FORMS definition
S RB
L. Feldman
Page 5
- PIG interface for file management account authorization.
- LIST does not display all items which may be defined.
o
o
DEF features in.c;omplete o~ not availafle:
- De: F ..M. ~ ~~~r~~""" ~ LJA I L
VOLINIT
~-~~...-- '<
- No known problems.
o
DELTA features incomplete or not available.:
- Expression evaluation is very primative
- COBOL and FORTRAN specific input system
- COBOL and FORTRAN array displays
- Structure display with elements broken out
- Floating point and decimal input
- Data break
points
- Update and extension of attachments
- Display of variable length items
- 0 N CALLS tracing
- Trace transfer wi th shared Ii brari es
- Display auto variables not in current frame
- RUM interface problems:
1.J DISPLAY does not work
2.
LET does not work
3.
DeB's, start address, and privileges can not be modified.
- ANLZ interface problems:
1.
No resul ts on M $ ALIB return
2.
DISPLAY does not work
3.
LET does not work
*****
c6~~~~~F-'*,,-L
o
:;-~~~
~~~~
cP-v
"
o
'-- ~ JJ-'
n
·
___ • ~.
.A
II
.R~J~
c9~ J.--t--
"'+
~ ~ .->~
~j..,~'-'
cP-v
~ ~ ~ cP-~
o
DLT-'2..o00
o
:l741
o
o
VISTA
~~h...,-....~~
~
~A
O.tt-R4-~~<""~~
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37 Create Date : 2014:12:02 16:30:01-08:00 Modify Date : 2014:12:02 16:09:43-08:00 Metadata Date : 2014:12:02 16:09:43-08:00 Producer : Adobe Acrobat 9.55 Paper Capture Plug-in Format : application/pdf Document ID : uuid:747e93a3-089b-c742-b44d-7a0c2f188400 Instance ID : uuid:2200082f-e474-3441-bce3-55c8c29f2b33 Page Layout : SinglePage Page Mode : UseNone Page Count : 77EXIF Metadata provided by EXIF.tools