.title On Line Information System Example

.comment****************************************************************
.comment* Copyright Micro Focus Limited 1993-94. All Rights Reserved.  *
.comment* This demonstration program is provided for use by users of   *
.comment* Micro Focus products and may be used, modified and           *
.comment* distributed as part of your application provided that you    *
.comment* properly acknowledge the copyright of Micro Focus in this    *
.comment* material.                                                    *
.comment****************************************************************

.define @cobcli  @1
.define @rtserr  @2
.define @direct  @3
.define @exegnt  @4
.define @main @7

.comment ************** Title of .hnf file ************
.context @main
.browse #1 @0 @cobcli
.topic A few questions frequently asked of Technical Support

:p.

:dl.

:dt. \i \p\aCOBCLI\v@cobcli\v\i \p
:dd. \bcobcli\p Not Found

:dt. \i \p\aRTSERR\v@rtserr\v\i \p
:dd. RTS Errors

:dt. \i \p\aDIRECT\v@direct\v\i \p
:dd. Directive Hierarchies

:dt. \i \p\aEXEGNT\v@exegnt\v\i \p
:dd. \b.exe\p vs \b.gnt\p Files

:edl.

.comment ************** QUESTION 4: EXE & GNT **************
.context @exegnt
.browse #1 @direct @0
.topic How does an .exe file differ from a .gnt file?

:p. The biggest difference between an \b.exe\p file and a \b.gnt\p file is
that \b.gnt\p (generated) code files are fully relocatable and swappable
under the memory management of the Run-Time Environment, where
industry-standard \b.exe\p files are subject to the memory management of the
resident operating system.

:p. If you are using DOS, Windows or OS/2, see the chapter \bCreating
Applications\p in your \bPC Programmer's Guide\p for more information.

.comment ************** QUESTION 3: DIRECTIVES *************
.context @direct
.browse #1 @rtserr @exegnt
.topic Directive Hierarchy
:i1.directive hierarchy

:p. How should the Compiler directives be managed?

:p. The Compiler processes directives in the following order:

:dl tsize=20 break=fit.

:dthd. \uLocation\p
:ddhd. \uDescription\p

:dt. Default values
:dd. These are what the directives are set to by default.

:dt. \bcobol.dir\p file
:dd. The values in your \bcobol.dir\p file.

:dt. Operating system command line
:dd. The values secified on the operating system command line.

:dt. $SET
:dd. A directives control statement you can insert in your program.

:dt. DIRECTIVES
:dd. Two directives (called DIRECTIVES and USE) enable you to specify
directives to be read from a file.

:edl.

:p. For more information, see your \bCOBOL System Reference\p.

.comment ************** QUESTION 2: RTS ERRORS *************
.context @rtserr
.browse #1 @cobcli @direct
.topic RTS Errors
:i1. RT198 error

:p.What is causing run-time error 198?

:p.These are some possible reasons:

:ul.

:li.Not enough memory
:li.Not enough file handles
:li.Called module not found

:eul.

.comment ************** QUESTION 1: COBCLI *****************
.context @cobcli
.browse #1 @0 @rtserr
.topic cobcli.lbr or cli.lbr not found
:i1. cobcli not found
:i1. cli not found
:i1. Installation problems
:i1. Can't run Workbench
:i1. Workbench doesn't come up

:p. Why does COBOL (or Toolset, Toolbox or Workbench) appear to be
unable to find the files \bcobcli.lbr\p or \bcli.lbr\p?

:p. Check to ensure that your COBDIR and LIB environment variables are
pointing to the COBOL system directories. You can either do this through
Setup or by setting the environment variables manually at the command
line, or in your \bautoexec.bat\p file (for DOS, Windows and OS/2) or
\b.login\p file (for UNIX).

.comment *** End of ONLEX.TXT **
