Kbase 11935: Release Notes for Double-Byte Progress: 6.4A (Asian Progress
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Release Notes for Double-Byte Progress: 6.4A (Asian Progress
Release Notes for 6.4A Double-Byte Enabled Progress
Purpose and Organization
This document describes new features, functionality, and limitations
on PROGRESS Release 6.4A, the Double Byte Enabled version of PROGRESS
for Microsoft Windows environment. It is organized as follows:
A. Overview of PROGRESS 6.4A
B. Microsoft Windows PROGRESS Specific Considerations (Issues
not directly related to Double Byte Enabling)
1. Installation/Configuration Tips
2. Limitations and Restrictions
3. Known Bugs
C. Double-Byte Specific Considerations
1. Procedures Enhanced for Double Byte Support
2. Limitations and Restrictions
3. Known Bugs Possibly Related to Double Byte
Enabling
More details on the specific functionality of this release may be
found in the PROGRESS documentation, and in the Documentation Bulletin
"Double Byte PROGRESS".
----------------------------
A. OVERVIEW OF PROGRESS 6.4A.
PROGRESS Version 6.4A is the double byte enabled version of PROGRESS
for Microsoft Windows, and is based on PROGRESS Version 6.2 for
Microsoft. This version has been enhanced to support the display and
manipulation of double byte character sets, such as Japanese (Kanji),
Chinese and Korean. Enhancements have been made to many areas which
which must manage text strings. Specific functions impacted have been
listed below, and futher infomation can be found in the Documentation
Bulletin "Double Byte Enabled PROGRESS" with this package.
----------------------------
B. MICROSOFT WINDOWS PROGRESS SPECIFIC CONSIDERATIONS
B.1 INSTALLATION/CONFIGURATION TIPS
o INSTALLATION
If you choose to install PROGRESS in non-default directories
(directories other than \DLC and \DLCLOAD), PROGRESS can create only
the destination directories if the parent directories already exist.
For example,if you installed to \USR\DLC and \USR does not exist, then
PROGRESS returns the following error message:
INSTALL ERROR (06): Unable to make directory c:\usr\dlc
However, if you create the parent directory (in this example \usr)
beforehand, you can successfully install the software.
o CREATING ICONS AND GROUPS
If there is not enough memory for the install to create the groups and icons,
they can be done after the install. Make sure you quit out of the
install first, then type the following command from the newly
installed disks:
win instgrp exetlr.tab
This will start windows and create the PROGRESS groups and icons.
o DLC ENVIRONMENT VARIABLE
For PROGRESS MS-Windows to work, the DLC environment variable
must be set. Be sure to include the drive letter and the complete
pathname. For example, SET DLC=C:\DLC.
o PIFS FOR PROGRESS DOS EXECUTABLES
The PROGRESS Windows installation process creates Program Information Files
(PIFS) for the utilities. However, the tailoring of these files is
incomplete. If you choose to install PROGRESS somewhere other than
c:\dlc, you must tailor the PIFS manually to indicate the startup
drive and directory.
Consult your windows documentation for the correct procedure for
editing PIFS. Edit these files:
rundosmw.pif
prodb.pif
proutil.pif
prolib.pif
proshut.pif
quoter.pif
cmpdb.pif
prodel.pif
prolog.pif
After you edit the files, save them in the %DLC% directory. See the
Installation Notes for more information.
o MESSAGE BUFFER SIZE (-Mm) STARTUP PARAMETER
The Message Buffer Size (-Mm) startup parameter is fixed at 512 for a client
client or server running on an SPX network with -N SPX. For example,
specifying -Mn 1024 is invalid.
o NETWORKING - SPX PROTOCOL
Novell continues to update support files for MS-Windows and
the IPX/SPX protocol. The following is a list of files required for
the effective operation of PROGRESS for MS-Windows Release 6.4A.
IPX.COM Version 3.10 or higher.
NWIPXSPX.DLL Version 1.31 or higher.
VNETWARE.386 Version 1.04 Build 92-045 or higher.
NETWARE.DRV Version 2.00 Release, Build 92-044 or higher.
VIPX.386 Version 1.11 (920213) or higher.
TBMI2.COM Version 2.1 or higher (MS-Windows 3.1 and DOS 5.0)
or
TBMI.COM Version 1.0 or higher.
For 386Enhanced Mode Windows verify that the system.ini file has the
following line in the 386 Enhanced section:
network=*vnetbios,vnetware.386,vipx.386
For Standard Mode Windows execute either TBMI2.COM or TBMI.COM prior
to executing windows.
These files are a subset of the NetWare Workstation Kit
for DOS/Windows v2.0 available from Novell Corp.
------------------------------
B.2. WINDOWS-RELATED LIMITATIONS AND RESTRICTIONS
o PROLOG UTILITY LIMITATION
There are upper and lower limits on the size of a log file in which
the utility will work. The upper limit is approximately 39K and the
lower is approximately 3K. If the size of the log file is outside
of these limits, the PROLOG utility will appear to have worked, but it
will not change the size of the log file.
o INDEX DEACTIVATION
Deactivate indexes through the Index Editor. Deactivating indexes
through the Administration menu in the Data Dictionary deactivates the top
index. For example, in the customer file there are three indexes:
Cust-num, State, and Zip. If you use the Administration menu to de-
activate Zip, it deactivates Cust-num as well as Zip.
o NEW NETBIOS WARNING MESSAGE
There is a new error message that can occur during Multi-user startup:
"Netbios not proven, PROGRESS continues."
This is a warning message that implies either you are running a
Netbios. Progress does not recognize at startup or that Netbios is
not loaded. It should work if Netbios is loaded. This message will
occur if you're using IBM's Netbios or a Netbios that uses interupt 5c
o NLM/DOS SERVER AND "DATABASE UNAVAILABLE" ERROR
If you have problems connecting to a server and receive either
"Database unavailable" or "Cannot locate database" errors, try using
the startup parameter on both the server startup and client
startup. The database name and the (-S) startup are case sensitive.
If caps are used on the server, they must be used on the client.
o LANGUAGE - DOS STATEMENT
If the PROGRESS for MS-Windows client becomes disconnected from a
remote database when a non-windows application, a DOS session, or the
DOS statement used while you are connected to a remote PROGRESS server
using SPX Protocol, then verify that the latest release of Netware's
MS-Windows is being used and refer to the section on NETWORKING - SPX
PROTOCOL in this document.
o USAGE INFORMATION FOR KEYCODES 651 THROUGH 654 UNDER WINDOWS
CODE NAME USAGE
651 LEFT-MOUSE-DOWN Sent when the left mouse button is
pressed inside a CHOOSE. This is sent
before the button is released.
652 LEFT-MOUSE-MOVE Sent when the mouse is moved while
the left button is pressed inside a CHOOSE.
Currently, this Keycode is not implemented.
653 MIDDLE-MOUSE-UP Sent when the middle button of a three-
button mouse is released.
654 RIGHT-MOUSE-UP Sent when the right button is released.
o PUT CONTROL AND FORM HEADER (PAGE-TOP)
If you use PUT CONTROL out to a printer and you also have a FORM
HEADER (PAGE-TOP), the FORM header will not display on the first page of
output.
o LANGUAGE (OUTPUT TO PRINTER)
Under Windows, you can choose either of two possible printing modes:
- Default mode. In this mode, PROGRESS uses the MS-Windows
device drivers. This mode is sufficient for all basic printing
that does not use any printer access control codes (whether
selected by PUT, PUT CONTROL, or DISPLAY statements).
- Windows pass-through printing (WPP). In this mode, PROGRESS
bypasses the Windows device drivers. So you can send
control codes (such as POSTSCRIPT commands) directly to the
printer with the PUT, PUT CONTROL or DISPLAY statements.
NOTE: When you use WPP mode with a POSTSCRIPT printer, standard
reports as those produced by the Data Dictionary or RESULTS, do not
print properly.
WPP mode can be enabled in either of two ways. You can explicitly
enable mode at PROGRESS startup or PROGRESS automatically switches to
WPP mode if you perform certain operations.
To explicitly enable WPP mode at startup, specify one of the following PROGRESS
startup parameters:
-wpp Enables WPP mode for the session.
-wpconvert Enables WPP mode and automatically converts OEM
characters to the ANSI character set before
sending them to the printer. This conversion is
required to correctly print some international
character sets. (This conversion is also per-
formed in default mode.)
-wplf Enables WPP mode for the session and modifies
the end-of-line behavior. Normally, in WPP mode
each output line ends with a carriage return and
a linefeed character. When you specify the -wp
parameter, only a linefeed character is sent at
the end-of-line.
When you enable WPP mode at PROGRESS startup, the mode remains in
effect the entire PROGRESS session.
PROGRESS automatically switches to WPP mode under the following
conditions:
- The first output you perform after sending output to the printer
is a PUT CONTROL statement. You can switch to WPP mode, for
example by executing the statement PUT CONTROL NULL.
- You execute a DISPLAY or PUT statement to the printer with ESC (ASCII
decimal 27) as the first character. This statement must be the first
output you send to the printer; otherwise, you will receive an error
error message that refers to mixed modes.
- You specify PAGE-SIZE 0 for a non-POSTSCRIPT printer.
In each of these cases, WPP mode remains in effect until OUTPUT CLOSE is
executed.
When using WPP mode, be aware that different print drivers send
different initialization sequences to the printer. For example, if you switch
switch to WPP mode for a POSTSCRIPT printer by executing a PUT CONTROL
NULL statement the printer is left in an odd state. The "initmatrix"
POSTSCRIPT command fixes this. For more information about this command
refer to your POSTSCRIPT documentation.
If you receive a printer error that refers to mixed modes, try using
WPP for the entire session.
For some printers, you must disable the Windows Print Manager when you use WPP
use WPP mode. This is the case, for example, if you are using an HP
LaserJet Printer.
If you are using a POSTSCRIPT printer in default mode, you must ensure that the
the Paper Size on the Configuration Setup menu is set to "note 8 1/2 X
11". You must also set the Margins on the Options submenu to Default
(not None). Otherwise, you will lose some characters at the page top
or left margin of your printout.
o WRITE CACHE UTILITIES
To ensure database integrity, place your database files, before-image file,
and after-image file on disk volumes where write caching is disabled. When
write caching is enabled, PROGRESS cannot be certain that database
blocks are written as planned. If a system failure occurs, database
blocks may be lost and your database may become corrupted.
o DBANALYS ON MULTI-VOLUME DATABASE
If your database is larger than 65.5MB, an erroneous message "free
chain circular list" appears when you run a DBANALYS. Ignore this
message.
o FTP TCP/IP CONNECTION
The "get_ipx:jet ipconfig:noerror" message appears when you connect
to a UNIX database using FTP. This is a normal status message.
o PROSHUT FOR DOS AND MS-WINDOWS
You can now use the PROSHUT utility from a DOS or MS-WINDOWS client
may disconnect users from or shut down any remote broker/server,
including NLM. You can use PROSHUT as described in the PROGRESS System
Administration manual, but you must also include the client start-up
parameters required to use the network protocol expected by the remote
broker/server (that is spx). With PROGRESS for Windows, the PROSHUT
command must be done from a DOS window.
------------------------------
B.3. KNOWN BUGS IN PROGRESS FOR MICROSOFT WINDOWS
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. You should convert the previous variable-length to a
fixed-length extent. To work around this problem, do not use the
PROSTRCT ADD command. Instead, create a new structure file. Define
all all of the extent you want to use, including any new extents.
Create a new empty multi-volume database and use the PROCOPY command
(or the PROBKUP and PROREST commands) to copy the contentss of the old
database to the new one.
o PROREST UTILITY
Restoring an incremental backup out of sequence causes you to lose
data. For example, if you restore incremental 2, then restore in-
cremental 1, you lose data restored from incremental 2. PROGRESS
returns a message that tells you the tapes are out of sequence, but
there is no warning about the data loss.
o PROGRESS INTERNAL STACK ERRORS
If the PROGRESS internal stack size is exhausted, there is a possi-
bility of Unrecoverable Application Error to occur after the PROGRESS
error message appears. These PROGRESS error messages usually refer to
increasing the size of that startup parameter.
o PRODB UTILITY
The PRODB command does not work properly on a network drive when the
source and the target names are the same.
o PROLIB - LARGE NUMBERS OF .R FILES
Adding large numbers of .R files to an r-code library can cause
PROGRESS to return "STGET out of storage errors." Usually the number
is quite large (900+) and it is recommended that you place the files
in multiple libraries
=============================================================
C. DOUBLE BYTE SPECIFIC CONSIDERATIONS
C.1. FUNCTIONS ENHANCED FOR DOUBLE BYTE SUPPORT
The following functions have been MODIFIED to support double byte text:
LENGTH
OVERLAY
SUBSTRING
The following function has been added:
IS-LEAD-BYTE
The following functions have been double byte enabled (are capable of properly
handling double byte text):
APPLY
ASC
CAPS
CHR
ENCODE
ENTRY
FILL
INDEX
KEYFUNCTION
LASTKEY
LC
LOOKUP
MATCHES
NUM-ENTRIES
PUT CURSOR
PUT SCREEN
R-INDEX
READKEY
SEARCH
STRING
TRIM
Please refer to the Documentation Bulletin "Double Byte Enabled
PROGRESS for specific information on these functions.
----------------------------
C.2. DOUBLE BYTE LIMITATIONS AND RESTRICTIONS
o R-CODE COMPATIBILITY
Due to the enhancements made to string functions to support double
byte character data, this version is not R-CODE Compatible with any
version of PROGRESS. This means that any PROGRESS programs compiled
using other versions of PROGRESS must be recompiled to run with this
version.
o NEC 600x400 RESOLUTION MONITORS
In order to support the 600 x 400 resolution of the NEC monitor, the
displayed number of lines in PROGRESS windows have been reduced from
25 to 22 for this monitor specifically. Because the fonts used by
Asian versions MS-WINDOWS to display double byte characters are larger
than those used by English versions to display single byte characters,
the normal PROGRESS default display of lines (25) is not able to fit
on the screen. All other monitors will display the 25 line default.
o DOUBLE-BYTE CHARACTER REPRESENTATIONS OF NUMBERS
The Double Byte character set includes represenations of most single
byte characters, including numbers. PROGRESS does not treat these
double Byte numbers as numbers, ie, they have no actual value. They
will be treated as text. Single byte represented number will behave
as usual.
o DOUBLE-BYTE CHARACTERS AND CASE SENSITIVITY
Some languages contain double byte character representations of the
standard English alphabet (roman characters). Similar to the above,
the functions CAPS and LC have no effect on double byte characters or
the byte representation of these roman characters. These double byte
roman characters will only be treated as normal double byte symbols.
o KEYCODE FUNCTION
The KEYCODE function will return -1 value when passed a double byte
character.
o KEYFUNCTION FUNCTION
The KEYFUNCTION function returns NULL for any double byte key value.
o OVERLAY FRAMES
When OVERLAY frames are removed from the screen, the underlying
frames are automatically refreshed.
Normally, when a frame is removed, only the characters which lie under it are
are repainted. However, it is possible that a frame could cut a
double byte character in half when it overlays that character. In
order to ensure double byte characters are left only half displayed
when the frame is cut, the entire frame is also repainted. This will
result in a apparent "refresh" of all the underlying frames on the
screen.
o DOUBLE-BYTE CHARACTER EDITORS
Some FEP's (Kanji character editors) cause the screen to be
repainted with incorrect colors. This repainting causes the
PROGRESS "INSERT" mode display in the lower right hand corner to
disappear, although the keyboard in still in insert mode.
o "-geometry" STARTUP PARAMETER
Use of the "-geometry" startup option is not recommended in Version 6.4A.
o PROGRESS 6.4A AND PRINTING
There are a variety of printers which support double byte character
output. These may be distinguished both by the double byte standard
supported and by the number of print positions used to output a
character. With this release Double Byte Enabled PROGRESS, only
"Shift-JIS" type printers are supported. "JIS" type printers are not
supported. Additionaly, PROGRESS only supports printers which output
one byte per print position (a double byte character must be output
over two print positions.). Printers which display a double byte
character with one and one half print positions are also not supported
----------------------------
C.3. KNOWN BUGS POSSIBLY RELATED TO DOUBLE BYTE ENABLING
o PRINTING TO A DEVICE NOT DEFINED
Printing to an undefined device will cause a fatal error. For example, if an
if OUTPUT TO LPT2 is done and LPT2 is not defined or there is not a
printer, a fatal error will occur and a reboot of the PC is needed.
Progress Software Technical Support Note # 11935