Consultor Eletrônico

SUMMARY:

This solution contains additional release notes for ICL3000 Version 6.2G02 for the UNIX 486 platform.

EXPLANATION:

Media type: 3 1/2 diskette
Extract command: mount /dev/dsk/f0t /mnt
Install command: /mnt/proinstall


Software notes:

- This release was ported with Oracle Version 6.
- This release supports Embedded SQL (HLI) for C.

Online backups:

The use of the -o (overlap factor) is not supported in this
release. You must restore the incremental backups exactly the
same way as you did when you backed them up to avoid problems.
For example:

proshut demo -C online /dev/rst8
proshut demo -C online /dev/rst8 incremental -o 2

If you skip any of the incrementals during a retoration of the
full backup, you receive an error message that indicates the
tapes are out of sequence and the restore fails.

Solution: Make sure all backups are restored in exact
order.

Fast Track (convft):

If you use the convft utility to convert your database to a Fast
Track database, you must set the PROEXE environment variable
first:

PROEXE=/usr/dlc/_progres;export PROEXE
convft database-name

Fast Track (500 file limit):

Unlike earlier versions, Fast Track Version 6.2F (or later)
enables you to choose from more than 500 files when you create
QBF's, reports or forms. There is no limit to the number of files
you can select. However, because of internal changes to the Fast
Track code, you must recompile any QBF's or menus that have
been generated with earlier versions of Fast Track in order to
run them under Version 6.2F or later.

Index deactivation:

If you are deactivating indexes, do it through the Index Editor.
Deactivating indexes through the Admin menu in the Dictionary
deactivates the top index.

For example:

There are three indexes in the the customer file
(Cust-num, State, and Zip). If you choose to deactivate Zip,
through the Admin menu, Cust-num is deactivated as well as
Zip

ORACLE ldemo:

The ldemo script that resides in subdirectory ora in the
directory where you install Progress (for example,
/usr/dlc/ora/ldemo) will not work with the Query/Runtime or
Runtime product. The script makes schema modifications that these
products do not support.

Remote gateways:

In Progress Version 6.2F and later, you can remotely access an
ORACLE or RMS database. To do this, you must install a Version
6.2F or later core Progress product (for example, PADS,
4GL&RDBMS, Query Report, or Runtime) on the machine that runs
your Progress application and on the machine that hosts your non-
Progress database.

Progress Versions 6.2F and later do not trap the CTRL-C if you
use it with a remote ORACLE gateway. If you use CTRL-C within a
transaction, you are disconnected from the remote ORACLE server
with the following message on your client:

** Disconnected by the server, code 7 (706).

Also, the remote ORACLE server's log will contain the following
error messages:

SERVER: SYSTEM ERROR: oratmstrt: transaction
already started (1473)
SERVER: ** Please save file name core for
analysis by PSC. (439)
SERVER: logout usernum 0, userid, on (739).

PROBUILD:

When you run PROBUILD, the $PROLOAD/eucapp/euc.pl file must have
at least read and write permissions (rw-rw-rw-), otherwise you
get the error:

** Cannot find or open euc.pl errno 13

To avoid this error, change the permissions on the euc.pl file as
follows:

chmod 666 $PROLOAD/eucapp/euc.pl

where $PROLOAD is an environment variable set to where you have
the dlcload directory installed (/usr/dlcload) by default.

You can now use PROBUILD to build an executable with a remote
gateway configurable element. For example, if you need to access
a remote ORACLE database, select your networking protocols and
Remote ORACLE Gateway at the Configurable Elements screen.

If you need to access your non-Progress database locally, you
must purchase the Progress 4GL and RDBMS software and the
Database Gateway software. If you do not have this combination of products, you cannot load the standard gateway into your
executable. (See Chapter 1 in the Progress 3GL Interface Guide
for more information.)

Connecting databases:

You must use the -Nv 12 startup option to connect a 6.2F01 client
to a Version 5, 6.2A-6.2F (or later) Progress server.

Multi-Volume Databases - PROSTRCT ADD:

If you define a variable length extent and then use the PROSTRCT
ADD command to add another variable length extent, the command
does not work correctly.
It should convert the previous variable-length to a fixed-length
extent, but it does not.

Solution: To workaround this problem, do not use the PROSTRCT ADD
command. Instead, create a new structure file (.st).
Define all of the extents you want to use, including
any new extents. Create a new void multi-volume
database and use the PROCOPY command (or the PROBKUP
and PROREST commands) to copy the old database to the
new one.

TLI/Streams and remote clients:

The ICL3000 uses TLI/Streams for inter-process communications and
networking. Therefore, when you start a remote server or a remote
client, you must give the following startup options:

- For a Remote Server (PROSERVE):

proserve <dbname> -S <service> -H <host> -N TLI
-Nd /dev/tcp

- For a Remote Client (mpro):

mpro <dbname> -S <service> -H <host> -N TLI -Nd
/dev/tcp

The default network device is /dev/tcp. If you use an alternate
device, you must specify the -Nd (Network Device) option.

X-Windows:

In order to build an X-Windows module using PROBUILD, you must
choose TLI as well as X-Windows from the Configurable Elements
menu.

RESULTS with ORACLE and Rdb gateways:

To run RESULTS for Version 6 with an ORACLE or Rdb gateway, the
gateway must be Version 6.2G or later.

ORACLE and Rdb gateways:

In Progress Version 6.2G and later, ORACLE and Rdb gateways use
only one index-cursor per buffer.(Prior to Version 6.2G, there is
one index cursor for each different WHERE clause).


This change enables the Next option in the RESULTS query module
to work with these gateways. As a result, you cannot use code
similar to the following:

FOR EACH cust WHERE name BEGINS "a":
FOR EACH cust WHERE cust-num > 1: ...
END.
END.

This type of code produces a "No nested FOR EACH" error message.
Instead, define a buffer for each inner FOR EACH loop. For example,
you can use code similar to the following:


DEFINE BUFFER cust-buf FOR cust
FOR EACH cust WHERE name BEGINS "a":
FOR EACH cust-buf WHERE cust-num > 1: ...
END.
END.