| New
in: |
Feature
Summary |
Detail
of Feature |
Benefit
of Feature |
| +V4
|
Syntax
support |
NetCOBOL
supports:
Object-Oriented COBOL
COBOL
68, 74, 85, 89 addendum
X/OPEN®
COBOL
IBM® VS
COBOL II
IBM® OS/VS
COBOL
Micro
Focus® COBOL™
|
You
can use your favorite COBOL programming language
dialect.
You can
use your existing COBOL code.
|
| V7 |
|
Supports
a special register SORT-CORE-SIZE to for specifying the amount
of memory to be used in PowerBSORT sort/merge operations |
Gives
greater program control of sort/merge operations. |
|
| +V4 |
|
CBL_ Routines |
Provides
greater compatibility with Micro Focus COBOL
programs. |
| +V4.2 |
|
Underscore "_" in user-defined
words |
" " |
| +V4.2 |
|
78-level named literals
|
"
" |
| V6 |
|
SCREEN
SECTION CONTROL clause. |
"
" |
| V6 |
|
Calculator-style
input of numbers for SCREEN SECTION ACCEPTs (behavior configured
at run-time using the screen definition file).. |
Convenient,
intuitive input of numeric data for your users. |
| +V4.2 |
|
Invoke case-sensitive program
names |
You can work with languages that are case sensitive
(such as C). |
| V5
+V6 |
|
TYPE
and TYPEDEF, including a STRONG TYPDEF to check matches
of group items. |
You can ensure that different
data items referring to the same data structures have
identical definitions. |
| V5 |
|
Define
external names for programs, classes and methods using the
"AS literal" phrase. |
| V6 |
|
STORED-CHAR-LENGTH
function added to return the length of a string ignoring trailing
spaces. |
Simple
coding of frequently used calculation. |
| V6 |
|
For
fixed format source files, the compiler ignores characters
in column 81 and beyond to ensure source synchronizes with
debugger. |
Consistent
debugging results for those using fixed format source. |
| V6 |
|
COB_ICON_TITLE
call added to configure the titles in main, screen and console
windows. |
Greater
control of application appearance. |
| V8 |
|
BINARY-CHAR,
BINARY-SHORT, BINARY-LONG, and BINARY-DOUBLE integer numeric
data types. |
Facilitates
sharing integer numeric data with other languages. |
| V8 |
|
Hexadecimal
numeric literal (H”xx”) |
Provides
a numeric literal that can be specified in hex and greater
compatibility with Micro Focus COBOL programs. |
| V8 |
|
ADVANCING
phrase in WRITE statements for line sequential files |
Provides
greater compatibility with Micro Focus COBOL programs. |
| V8 |
|
You
can write simple COBOL programs to process deadlocks that
occur with linked databases by using the USE FOR DEADLOCK
procedures and calling the Deadlock Exit subroutine |
Allows
you to cope with database deadlocks within your code. |
|
| |
Compiler
Options |
Numerous
compiler options control compiler behavior and code generation. |
Provides
control of compiler output and behavior. |
| V8 |
|
ASCOMP5
option causes USAGE BINARY, USAGE COMP, or USAGE COMPUTATIONAL
items to be treated as if they were defined with USAGE COMP-5. |
Helps
improve the performance of some programs or make their data
exchangeable with programs using other languages or vendors. |
| V8 |
|
INITVALUE
option allows you to specify the default initial value for
data items that do not have a VALUE phrase |
Provides
compatibility with other COBOLs that have initialized storage
differently from NetCOBOL. Lets you be sure how storage is
being initialized. |
| V8 |
|
The
compiler provides listings containing information on data
areas by specifying the MAP option. |
Provides
more information that is useful when debugging programs. |
| V9 |
|
SSOUT option extended to allow data to be appended to an existing file when DISPLAY statement output is directed to a file. |
Provides option of maintaining a cumulative log of DISPLAY statement output over multiple program executions. |
|
| |
Runtime
Environment Variables |
Numerous
runtime environment variables support configuration of runtime-specific
information such as filename mappings, directing messages,
debug options, print file control etc. |
Allows
configuration of details that are best determined at run time. |
| V8 |
|
You
can configure the date retrieved by COBOL applications in
ACCEPT … FROM DATE statements and the CURRENT-DATE function,
by using the @CBR_JOBDATE environment variable. |
Lets
you set the date to be used by the program independent of
the machine date. |
| V8 |
|
Automated
functions are provided for concatenating files and appending
to existing files, by using the MOD and CONCAT options in
the file-identifier environment variable. |
Provides
more options for handling files. |
| V8 |
|
You
can specify the severity code at which runtime messages are
output. |
Makes
it possible to output the level of messages appropriate to
your operating environment. |
|
| V7 |
Parameter
Checking |
For
internal programs checks the conformance of parameters
between calling and called programs. |
Provides
automated checking in an area in which tracking bugs can be
difficult. |
| V8 |
|
Extended
to check for conformance of parameters when calling external
programs. |
|
|
| V5
|
Configurable
library extensions |
The
extensions of COBOL source libraries can be configured using
the LIBEXT compiler option. |
Greater
flexibility in naming source files. |
|
| |
RDBMS
access |
You
can use embedded SQL to access the following databases:
- SQL
Server
- Oracle
- Informix
- Sybase
- Any
ODBC-compliant database
|
Access
your company's data without complex database conversions. |
| V4.2 |
|
Extensive
setup instructions |
|
| V5
|
|
Literal
values can be defined for parameters in ODBC stored procedures. |
|
| V6 |
|
Group
items can be used as host variables. (Host variables no longer
need to be at the 01 level) |
|
| V6 |
|
Provides
an ODBC cursor library that provides positional UPDATE and
DELETE whether or not the data source supports these features. |
|
| V7 |
|
Performance
of interfacing to ODBC databases improved. |
Faster
application execution when using ODBC. |
| V8 |
|
USE
FOR DEADLOCK procedures let you escape from deadlock situations. |
Provides
a programmatic route for handling deadlocks. |
| V9 |
|
CURSOR close on database commit supported |
|
| |
|
Varbinary data can be extracted from SQL into PIC X fields |
|
| |
|
When calling a SQL stored procedure in COBOL, you can specify indicator variables for the parameters to detect NULL values being passed back from the procedure |
|
| |
|
The return value from a stored procedure is made available in the SQLERRD item. |
|
|
| |
COBOL
File Handling |
Supports
all COBOL file types (sequential, line sequential,
relative and indexed). Provides fast, reliable file handling. |
You
can rely on the integrity of your data and give great
response times to your users. |
| V6 |
|
@CBR_TRAILING_BLANK_RECORD
environment variable provides option to remove trailing blanks
from line sequential records. |
Less
space occupied by line sequential files. |
| V6 |
|
Maximum
indexed file size increased to 3.4GB for BSAM files. |
Greater
storage capacity for large applications. |
| V7 |
|
Maximum
sequential and line sequential file sizes for BSAM files
increased to the maximum file size allowed by the operating
system. |
You
can create sequential and line sequential files as large as
you like. |
|
| V4 |
OLE
server access |
OLE
server support is built into a special class
supplied with OO COBOL. It includes the ability to:
Invoke
OLE server methods
Get
and Set OLE server properties
Get
and Set OLE arrays |
Integrate
(into your applications) functions from application tools
(such as Excel) that provide OLE Servers. |
|
| |
Integrates
with VB and other languages |
NetCOBOL
and Visual Basic can be combined so that:
COBOL
programs call VB routines
VB
routines call COBOL programs
COBOL
and VB debuggers can run concurrently. |
You
have the flexibility to use COBOL business handling
in VB applications and VB interface
handling in COBOL applications.
Having
both debuggers working concurrently reduces the guesswork
for mixed-language debugging. |
| V8 |
|
COBOL
programs can share external data items with C program external
variables of the same name. |
Provides
another option for sharing data between applications. |
|
| V5 |
Event
log |
Run-time
error messages and application messages can be written
to an event log. |
Improved
tracking of application events - particularly important in
multi-threaded code. |
|
| |
Print
support |
Combine
PowerFORM overlays (pre-printed forms substitute) with regular
print files.
Control
print features from within the program - e.g. paper type,
orientation, fonts, and point sizes. |
Regular
COBOL print reports can be given improved presentations with
little or no coding changes. |
| V5 |
|
Regular
print files can be printed double-sided under program
control. |
|
| V5
|
|
Greater
control of binding margin direction, binding margin width,
and origin of printing (uses VALID/INVALID function). |
|
| V6 |
|
Supports
use of a font number table, allowing print files to use
any number of fonts. |
|
|
| |
Project Manager |
"Programming
Staff" from earlier versions has been enhanced and renamed
"Project Manager". It includes: |
After
defining your project structure (how programs and source
files are related), Project Manager takes care
of dependencies – for example which programs need
to be recompiled when you change a particular source file.
You can focus on programming.
Configuration management helps you control
developments across your team.
|
| V7 |
|
Tree
View and List Views (all/editable files)
of project (application) structure.
COBOL
sensitive editor. |
| V4
|
|
Integrated with PowerGEM configuration management.
Compile,
link, debug, build, execute, sensitive to
any changes to sources or objects. |
| V4 |
|
Integrated with OO tools.
Customizable
menus. |
| V4 |
|
Includes
easy movement of projects from folder to folder. |
| V4.2 |
|
C
run-time library option |
| V5 |
|
Supports creation of CORBA client and server applications
through Interstage add-on.
|
| V6 |
|
Interstage
Object Director supported by both COBOL85 and OOCOBOL.
Interstage Transaction Director supported. |
| V5
+V6 |
|
Supports invocation of precompilers, with invocation
details configurable across multiple source files.
|
| V5 |
|
New
Run-time Environment Setup tool incorporated (so the Run-time
Environment Setup dialog is no longer displayed when applications
start executing) |
| V6 |
|
Build
multiple projects |
Simplified
updating/management of related projects. |
| V6 |
|
Compiler
picks up options (such as copy library folders) from environment
variables. |
Allows
several projects to share the same options. |
| V6 |
|
Project
Manager accepts any extension for COBOL source files. |
Greater
flexibility in constructing projects. |
| V6 |
|
Able
to specify EXE and DLL version number information. |
Helps
your users to track your program versions. |
| V7 |
|
Provides
Properties dialog for setting project properties, including
a comment/description |
Easier
handling of project properties. |
| V7 |
|
Contains
links and functions to support development of applications
for/on a remote platform such as Solaris. (Requires NetCOBOL
for Solaris V7) |
Provides
the convenience of Windows tools for developing Solaris applications. |
|
+V7
|
Documentation |
Full
documentation set provided online.
Integrated Documentation Viewer gives access to all online
documentation from a single point - whether in PDF, HTML,
or Windows Help format. |
Easy
access to extensive COBOL and product information.
|
| V7 |
|
PDF
documentation format enhanced and put into 8.5 x 11page size. |
Makes
for easier printing of selected
|
| "+Vn"
in the "New in:" column indicates a feature that contains
new or improved elements as well as existing
elements. When "+Vn" is in Italics, it refers to the italicized
detail items. The number n indicates the release in which
the new feature was introduced. |
