Kbase 9178: Release notes for Sequent PTX V6.2G04
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Release notes for Sequent PTX V6.2G04
910730-gfs01
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: Sequent PTX
MEDIA TYPE: High Density Cartridge Tape
SOFTWARE RELEASE: 6.2G04
EXTRACT COMMAND: cpio -iudcvBm </dev/rmt/ts0
INSTALL COMMAND: ./proinstall
MACHINE NOTES:
OPERATING SYSTEM NOTES:
TERMINAL NOTES:
SOFTWARE NOTES:
o 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 or you will have
problems. For example,
proshut demo -C online /dev/rst8
proshut demo -C online /dev/rst8 incremental -o 2
After restoring the full backup, if you skip any of the
incrementals, you receive an error message indicating that
the tapes are out of sequence and the restore fails.
Workaround: Make sure all backups are restored in exact order.
o 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
o Fast Track (500 file limit)
---------------------------
Unlike earlier versions, Fast Track Version 6.2F and
above enables you to choose from more than 500 files when
creating QBF's, reports or forms. Now 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 generated with earlier versions of Fast Track to run
them under Version 6.2F or above.
o REMOTE GATEWAYS
---------------
In PROGRESS Version 6.2F and above, 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 where you
are running your PROGRESS application and on the machine
hosting your non-PROGRESS database.
o REMOTE ORACLE GATEWAY
---------------------
While using the remote ORACLE gateway, if you press
CTRL-C during a transaction, you are disconnected from
the remote ORACLE server.
o PROBUILD
--------
o When running PROBUILD, the $PROLOAD/eucapp/euc.pl file must
have at least read and write permissions (rw-rw-rw-), otherwise
you will 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.
o 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, just select your networking
protocols and REMOTE ORACLE GATEWAY at the CONFIGURABLE
ELEMENTS screen.
o Connecting Databases
--------------------
You must use the -Nv 12 startup option to connect a 6.2F
or above client to a Version 5 or 6.2A-6.2F PROGRESS server.
o 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.
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.
o Prorest Utility
---------------
Restoring an incremental backup out of sequence will
cause you to lose data. For example, if you restore
incremental 2, then restore incremental 1, you will lose
the data restored from incremental 2. You receive a
message telling you that the tapes are out of sequence,
but you are not warned about the data loss.
o ORACLE and Rdb Gateways
-----------------------
From PROGRESS Version 6.2G on, ORACLE and Rdb gateways
only use one index-cursor per buffer. (Prior to Version
6.2G, there was 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.
o 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.
o Extended File Descriptor Tables
-------------------------------
Sequent users running a PROGRESS server that requires many file
descriptors may receive the following error message:
SYSTEM ERROR: unable to open or create (file #),
error 24 (354)
This message occurs when the PROGRESS server requests more file
descriptors than the operating system makes available. To solve
the problem, you need to:
o Set the MAXNOFILE and NOFILEEXT variables in the kernel
configuration file (param.c).
o Regenerate the kernel.
o Set the PROGRESS File Descriptor startup parameter (-Mv).
See the next section for details.
Set the MAXNOFILE and NOFILEEXT Variables
-----------------------------------------
The MAXNOFILE variable specifies the maximum number of open
files for a specific number of processes. The NOFILEEXT
variable specifies the number of processes that can access
the maximum number of file descriptors.
The default number of file descriptors available to a process on
Sequent machine is 20. However, a PROGRESS server needs at least
30 file descriptors to run. Therefore, the defualt value for the
MAXNOFILE variable is set to a minimum of 30 so your system can
run PROGRESS. But if your PROGRESS server needs more than 30
file descriptors, you need to change the MAXNOFILE value.
For example, if you need 40 more file descriptors than the
default of 30, set the MAXNOFILE to 70 (30 default + 40
additional file descriptors).
You then need to set the NOFILEEXT variable to determine the
number of processes that can access the maximum number of file
descriptors. Since each server needs 2 processes, you need to
consider the number of servers that you want to run with the
MAXNOFILE value. For example, if you have 3 servers that need
to run with 70 file descriptors, set the NOFILEEXT variable at
6 (2 processes x 3 servers).
You may need to adjust the following variables within the
kernel for the increased user activity: maxusers, NPROC,
and MAXUPRC.
Regenerate the Kernel
---------------------
Once you set the variables, regenerate the kernel. For details
on how to regenerate the kernel, see the "Reconfiguring the
PTX Kernel" section in the Sequent PTX System
Administration manual.
Set the PROGRESS File Descriptor Startup Parameter
--------------------------------------------------
After you set the variables and regenerate the kernel, you
must use the File Descriptor (-Mv) startup parameter the next
time you use PROGRESS so the server can request the additional
number of file descriptors.
For example, if you need 40 additional file descriptors when
starting a PROGRESS server with database mydb, enter:
: proserve mydb -Mv 40
NOTE: The system cannot provide file descriptors beyond the
number set for the MAXNOFILE variable in the kernel.
Therefore, the -Mv startup parameter number added to
the previously described default value of 30 should
total a number that is less than or equal to the number
set for the MAXNOFILE variable. For example, if the
MAXNOFILE variable equals 70, the File Descriptor
startup parameter should be 40 or less (40 + 30 = 70).
Progress Software Technical Support Note # 9178