=========================================================================
M I C R O F O C U S
V4.1.10
Running Under The DG/UX
Operating System Version R4.11MU03
On The AViiON
=========================================================================
SUPPLEMENTARY INFORMATION
=========================
TABLE OF CONTENTS
=================
INTRODUCTION
ON-DISK SUPPLEMENTS
SUPPLEMENTARY INFORMATION
INTRODUCTION
============
The purpose of this document is explained in the main release notes.
This document is updated at each maintenance release.
ON-DISK SUPPLEMENTS
===================
Your COBOL system contains the following on-disk supplements. The
subsection headings show releases when they were released or updated.
The letter codes give the following details about the document:
ER Describes an early release feature.
AS Provided for Application Server users who don't get the books
V4.1.10
=======
V4.1.06
=======
callfh.1 Enhanced Callable File Handler
dais.1 COBOL/DAIS Developer's Kit
From V4.0
=========
Documents in this subsection are carried forward to V4.1 from V4.0.
Existing V4.0 documents not listed in this section are withdrawn.
changes.1 Compatibility With Previous Releases
appserv.1 Application Server
config.1 AS Run-time Configuration
fhutil.1 AS File Handler Utilities
running.1 AS Running
terminfo.1 AS Terminfo Entries
rebuild.1 AS Rebuild
SUPPLEMENTARY INFORMATION
=========================
This section gives notes supplementing your manuals. Entries are grouped
by component.
COBOL Shared Libraries
----------------------
o SVR4 uses LD_LIBRARY_PATH for the library search path environment
variable, while AIX uses LIBPATH.
o Some COBOL shared libraries have filenames longer than 14 characters.
If your operating system has alternative file systems, use a
filesystem with support for long filenames to install or save the
shared libraries.
o To continue using previous versions of shared libraries after they
have been updated, on SVR4 enter:
mkdir /dir/oldlibs
ln libcobol.so.1.0.3101 /dir/oldlibs/libcobol.so.1.0
LD_LIBRARY_PATH=/dir/oldlibs:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
and on AIX enter:
mkdir /dir/oldlibs
ln libcobol.so.1.0.3101 /dir/oldlibs/libcobol.so.1.0
LIBPATH=/dir/oldlibs:$LIBPATH
export LIBPATH
-added V4.0.07
-modified V4.1.10
Directives for Compiler
-----------------------
o The HOST-NUMMOVE(2) directive is Early User Syntax support. You must
use the EARLY-RELEASE directive to enable this feature. This
directive might change or be removed in a later revision of this
product.
This directive is provided to improve compatibility with IBM
mainframe compilers for a subset of MOVE statements involving
numeric/alphanumeric data types and numeric/numeric data types.
This directive affects both the Syntax check and Generate phases.
This directive does not provide 100% compatibility with the IBM
mainframe behavior, but does provide emulation for the most common
cases.
You cannot use the HOST-NUMMOVE(2) directive in conjunction with the
HOST-NUMMOVE directive.
-added V4.0.07
o The HOST-NUMCOMPARE(2) directive is Early User Syntax support. You
must use the EARLY-RELEASE directive to enable this feature. This
directive might change or be removed in a later revision of this
product.
This directive is provided to improve compatibility with IBM
mainframe compilers for a subset of IF statements involving
comparisons between numeric data items and numeric literals.
This directive affects both the Syntax check and Generate phases.
This directive does not provide 100% compatibility with the IBM
mainframe behavior, but does provide emulation for the most common
cases.
You cannot use the HOST-NUMCOMPARE(2) directive in conjunction with
the HOST-NUMCOMPARE directive.
-added V4.0.07
Fileshare Version 2
-------------------
o The following supplements the chapter "Fileshare Version 2" in your
Toolbox Reference).
Support for CCI Trace in Fileshare
----------------------------------
You can activate CCI trace at the Fileshare Server by specifying:
/tr cci
when starting Fileshare. To ensure that no unauthorized persons gain
access to the CCI trace information, CCI trace can only be enabled if
a supervisor password is submitted. This password must match the
FSVIEW supervisor password specified in a Fileshare password file.
Therefore a password file must be specified to use when the Fileshare
Server is started. The administrator responsible for doing this must
create this password file.
When starting Fileshare with the "/tr cci" option you are prompted to
enter the supervisor password. If the password is accepted, use of
CCI trace is enabled. A second prompt asks if CCI trace should be
activated immediately or not. CCI trace can be subsequently toggled
on and off by pressing the F3 key.
CCI picks up its trace options from the setting of the CCITRACE
environment variable at the Fileshare Server. Please see the chapter
"Common Communications Interface" for details of CCI trace options.
Example
-------
To create a password file containing an FSVIEW supervisor password,
enter:
fs /pf password.fil /u FSVIEW /pw abracadabra
This creates the password file password.fil containing the reserved
user id FSVIEW (in upper case) entry with a password abracadabra.
When starting the Fileshare Server with the "/tr cci" option, specify
the password file:
fs /s server1 /tr cci /pf password.fil
Note: If the password file includes only the FSVIEW supervisor
password entry, Fileshare application logon security will
not be activated by specifying the /pf option.
When the Fileshare Server starts, it prompts you to enter the
supervisor password. If this is accepted, it then asks if you want
CCI trace active immediately. Reply "y" or "n".
-added V4.0.07
Integrated Preprocessor
-----------------------
o The preprocessor CP (used by preprocessors to handle copyfiles)
has a directive LIMITED-SEARCH (abbreviation LS), which you can use
to reduce compile time when certain conditions are met. It is likely
to be of most use when source files are distributed around a network.
When this directive is set, CP only looks for copyfiles in the
directories specified in the COBCPY environment variable; it does not
look in the directory where the main source file is. Also, it does
not use the copyfile extension in the OSEXT directive, just COPYEXT.
By using LIMITED-SEARCH, and carefully choosing the directories in
the COBCPY environment variable and the file extensions in the
COPYEXT directive, you can greatly reduce the number of file
searches.
=========================================================================
Micro Focus, Animator, and COBOL Workbench are registered trademarks of
Micro Focus Limited.
Object COBOL, CCI, Dialog System, Fileshare, Operating System Extensions,
OSX, Panels, and Professional COBOL are trademarks of Micro Focus
Limited.
IBM, OS/2, and PC are registered trademarks of International Business
Machines Corporation.
Windows is a trademark of Microsoft Corporation.
UNIX is a registered trademark of X/Open Company Limited.
=========================================================================
@(#)Vrn/sup.1/////07/25Apr97/nrV
Copyright (C) 1992-97 Micro Focus Limited