Kbase 12665: 6.2M13 Windows Release Notes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
SUMMARY:
This document describes limitations and new features for the release
of PROGRESS Release 6.2M under Microsoft Windows.
o NEW COMPRESSED INSTALL
PROGRESS 6.2M is in compressed form on the media. The install is the same
same as previous DOS-WINDOWS products, except for an added step.
After the files are copied to the designated directory, they are de-
compressed by the PROGRESS install process.
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.
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)
before you can successfully install the software.
o CREATING ICONS AND GROUPS
If their 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 6.2M directories:
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 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 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
incoomplete If you choose to install PROGRESS somewhere other than
c:\dlc must edit the PIFs manually to indicate the startup drive and
directories. 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 NETWORK VERSION (-Nv 12) STARTUP PARAMETER
PROGRESS provides a new switch to allow client access to older servers.
If you are connecting to a PROGRESS Release 5 or Release 6.2A-6.2F
server you must set the -Nv start-up option to 12 on the client.
This is documented in the Version 6 Documentation Bulletins V and higher.
o R-CODE COMPATIBILITY
There is no r-code compatibility between 6.2M and any PROGRESS releases
lower than 6.2Hxx. Therefore, you must recompile previous applications
to use them with PROGRESS release 6.2M. However, PROGRESS r-code is
interchangeable among 6.2Hxx, 6.2J0x and 6.2M DOS, OS/2, and Windows
products.
o MESSAGE BUFFER SIZE (-Mm) STARTUP PARAMETER
The Message Buffer Size (-Mm) startup parameter is fixed at 512 for a client
or server running on an SPX network with -N SPX. For example,
specifying -Mm 1024 is invalid.
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
of these limits, the PROLOG utility will appear to have worked, but it
will not change the size of the log file.
o FAST TRACK (500 FILE LIMIT)
Unlike lower releases, FAST TRACK Release 6.2Hx and higher
enables you to choose from more than 500 files when creating QBFs,
reports, menus, 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 re-compile any QBFs, reports, menus, or forms generated
with lower releases of FAST TRACK to run them under Release 6.2H01 or
higher.
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
deactivate Zip, it deactivates Cust-num as well as Zip.
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 should convert the previous variable-length to a fixed-length
extent does not. To work around this problem, do not use the PROSTRCT
ADD command. Instead, create a new structure file. Define all of the
extents you want to use, including any new extents. Create a new empty
multi-volume database the PROCOPY command (or the PROBKUP and PROREST
command) to copy contents 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
incremental 1, you lose the data restored from incremental 2. PROGRESS
returns a message which tells you the tapes are out of sequence, but
there is no warning about data loss.
o PROGRESS APPLICATION DEVELOPMENT SYSTEM (PADS)
When you run PROBUILD, the application prompts you for the directory
where you want to install the load script (link script). Use the
default directory that is your current directory. The configuration
utility does not work properly if you specify any directory other than
the default directory.
The euc.p procedure used during the PROBUILD is now in an r-code
library EUC.PL. Therefore, you must now place the r-code library in
the PROPATH.
For example:
PROPATH=%PROPATH%;%DLC%\dlcload\eucapp\euc.pl
o PROBUILD AND MICROSOFT C V7.00 AND VISUAL C++ V1.0
PROGRESS 6.2M13 supports the PROBUILD utility with the Microsoft C v7 and
Visual C++ V1 (c8) using correct startup objects and runtime libraries.
o PROGRESS INTERNAL STACK ERRORS
If the PROGRESS internal stack size is exhausted, there is a
possibility that an Unrecoverable Application Error to occur after the
PROGRESS error message appears. These PROGRESS error messages usually
refer to increasing this startup parameter.
o HLIDEMO AND WINDOWS PROGRESS
When using the HLIDEMO, it is not possible to connect a PROGRESS
release server with SPX using the -Nv 12 startup parameter. You must
connect using PROGRESS v6.2h0x or higher database.
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.2M.
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.
o NEW STARTUP PARAMETER: -facename
The -facename startup parameter enables you to use different fonts
during a PROGRESS session. Only fixed-spaced fonts are supported.
This startup parameter must be lowercase.
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 that Progress does not recognize at startup or that Netbios is
not loaded. This should work if Netbios is loaded. This message will
occur if you are using IBM's Netbios or a Netbios that uses interrupt
5.
o NLM/DOS SERVER AND "DATABASE UNAVAILABLE" ERROR
If you have problems connecting to a server and recieve either
"Database unavailable" or "Cannot locate database" errors, try using
the (-S) 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 is used while you are connected to a remote PROGRESS
server using the SPX Protocol, then verify that the latest release of
Netware MS-Windows toolkit is being used and refer to the section on
NETWORKING - SPX PROTOCOL in this document.
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 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
involved is quite large (900+) and it is recommended that you place
the files in multiple libraries
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 sent
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 report
such 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 WPP mode at PROGRESS startup or PROGRESS automatically switches
WPP mode when 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
performed 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 -wplf
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 for the entire PROGRESS session.
PROGRESS automatically switches to WPP mode under the following
conditions.
- The first output you perform after sending output to the print
device, 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
decimal 27) as the first character. This statement must be the
first output you send to the printer; otherwise, you received
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
output 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
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 Paper Size on the Configuration Setup menu is set to "note 8 1/2 X 11".
11" You must also set the Margins on the Options submenu to Default
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.
Note: The latest release of the SmartDrive disk cache utility included with
MS-Windows 3.1 can now act as a write cache.
o DBANALYS ON MULTI-VOLUME DATABASE
If your database is larger than 65.5MB, an erronous message "free
chain is a circular list" appears when you run a DBANALYS. Ignore
this message.
o RESULTS INSTALL
When you install RESULTS as an add-on product, there are three ways to
implemented it. One is to reinstall PROGRESS with RESULTS. Another
is to install RESULTS as an update to PROGRESS. Yet another is to
replace each instance of DLC with the proper directory in every batch
file where you install RESULTS.
o PRODB UTILITY
The PRODB command does not work properly on a network drive when the
source and target names are the same.
o PROSHUT AND TCP/IP
The supplied PROSHUT executable supports SPX, NETBIOS, and FTP
TCP/IP. If you need PROSHUT for another type of TCP/IP, you must
perform a PROBUILD for that specific flavor of TCP/IP.
o LAN MANAGER TCP/IP
Because Microsoft does not support the LAN MANAGER TCP/IP .dll files,
PROGRESS is unable to support LAN MANAGER TCP/IP.
o FTP TCP/IP
PROGRESS MS-Windows release 6.2M now supports FTP TCP/IP v2.10 through v2.20.
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 6.2M CLIENTS TO RDB GATEWAY
All 6.2M clients going to RDB Gateway on VMS have to upgrade their VMS
PROGRESS release to 6.2L10 or higher. There have been significant
changes to the RDB Gateway on both the VMS and DOS sides.
o RDB RECORD LOCKING WITH REMOTE MS-WINDOW CLIENTS
PROGRESS MS-Windows version 6.2m13 eliminates possible deadlocks
between two remote clients trying to access RDB data via the RDB
remote gateway.
o AS/400 CLIENT: SCHEMA HOLDER - SPX PROTOCOL
If the AS/400 schema holder is to be connected via the SPX protocol,
you start the AS/400 database with "-Mm 512" to allow compatibility
with the SPX protocol also being used.
o AS/400 CLIENT: MULITPLE AS/400 SYSTEMS
The -H startup parameter is used to connect to multiple AS/400 systems.
The value must be in uppercase.
o 6.2M13 MS-WINDOW CLIENT AND 6.2J PROGRESS/400 SERVER
Currently the 6.2J server performs revision checks at the database
level however the 6.2M13 client performs revision checks at the file
level. To workaround this problem, do the following:
1. Start the client session with the -is (ignore stamp) startup
option. If you do not do this, you will receive the following
error:
"Timestamp conflict, rebuild schema holder or use -is option".
Rebuilding the schema holder will not work in this case, because
the definitions dumped using the 6.2J server utility contain the
old level checking.
2. Select one of two options to direct the client to the 6.2J
server. a. Use the -Sn (server name) startup parameter when
connecting to the AS/400 database. (ie. -Sn PROSNA.PROGSRV211)
Note: PROGSRV211 is the library where the 6.2J server resides
on the AS/400, and PROSNA is the name of the program that starts
the server.
b. Move the two files PROSNA and BATPROSNA from library PROGSRV211
to the system library (ie. QSYS).
If the client cannot locate the server, this message will appear when
when you attempt to connect to the AS/400 database: "Unexpected
code from ReceiveAndWait. Error during initial receive from
AS/400".
Users running 6.2M13 client with the new server version 6.2M, will not
encounter these incompatibilities since both products use the same
revision level checking, and the 6.2M server has a utility to move the
server programs to the QSYS directory.
o LAN FASTPATH SUPPORT
PROGRESS MS-Windows release 6.2m13 now has Lan FastPath support.
o PROSHUT FOR DOS AND MS-WINDOWS
You can now use the PROSHUT utility from a DOS or MS-WINDOWS client
machine to disconnect users from or shut down any remote broker/server,
including DOS and NLM. You can use PROSHUT as described in the
PROGRESS System Administration II 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, -N spx). With PROGRESS
With PROGRESS for Windows, the PROSHUT command must be done from DOS
only from a DOS window.
o LAN WORKPLACE FOR DOS V4.1 SUPPORT
PROGRESS for Windows now supports Lan Workplace for DOS.
o PROGRESS STACK (-s)
The PROGRESS stack size can now be increase to 63.
o DATE FIELD
Problems involving the date field have been addressed.
o DOS SILENT
Timing problems with DOS SILENT have been addressed.
o WINSOCK.DLL REV 1.1
PROGRESS 6.2M13 now supports WINSOCK 1.1 and has been verified on FTP,
Netmanage, PCNFS, and Wollongong.
o MS-WINDOWS NT
PROGRESS version 6.2M13 now has MS-Windows NT support.
o AS/400 RECORD LOCK
Record locking problems associated with clients connecting to an AS/400 database
have been fixed.
o LOCAL ORACLE V6 DATABASE SUPPORT
PROGRESS now supports LOCAL Oracle version 6 database access.