Kbase 13577: OS/2 config for Progress/Windows v7 in WIN-OS/2 environment
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
OS/2 config for Progress/Windows v7 in WIN-OS/2 environment
PROGRESS Version 7 AS/400 Client/Server
under OS/2 - the WIN-OS/2 Environment.
I. OVERVIEW
-----------
The following information outlines the details for configuring an OS/2
workstation for PROGRESS/Windows version 7 in an WIN-OS/2 environment
with SNA and LFP connections to an AS/400.
The IBM operating system OS/2 2.x supports the ability to run
MS-Windows 3.x based applications on the OS/2 desktop.
This feature in conjunction with Extended DOS PC Support, OS/2 PC
Support, OS/2 Communications Manager and LAN Adapter and Protocol Support
(LAPS) provide all the necessary tools to run PROGRESS/Windows version 7
client/server to an AS/400. Below is a list of these products and
their required version levels.
Product Version
------- -------
- OS/2 2.11
- Communications Manager/2 version 1.10
- LAN Adapter and Protocol Support 2.20 (supplied with CM/2 1.1)
- Extended DOS PC Support/400 v2r3
- OS/2 PC Support/400 v2r3
PROGRESS on MS-Windows based machines is designed to use the IBM PC
Support interface for client/server communication to an AS/400. In
version 2 release 3 of the Extended DOS PC Support product, IBM
enables Virtual DOS Machine (VDM) applications (i.e. DOS & Windows apps) to
use OS/2 communications facilities via the DOS PC Support router API.
This support enables both DOS/Windows applications and OS/2 applications
to share the communications adapters. This capability, known as the Virtual
Device Driver (VDD) works in conjunction with the OS/2 PC Support VDM
Router Server (VDMSERV.EXE). The VDM Router Server translates DOS PC
Support router API requests into Communications Manager APPC requests
and passes them on the Communications Manager. The VDM Router Server
also communicates with the OS/2 Router (STARTRTR) for such things as
retrieving the remote system name. Detailed in each of the following
sections is the configuration requirements, summarized as :
- Extended DOS PC Support/500 V2R3 Configuration.
- OS/2 PC Support/400 V2R3 Configuration
- Additional OS/2 Communication Configuration
- PROGRESS/Windows version 7 Application Settings
- Hardware Resources
- Alternative Configurations
II. Extended DOS PC Support/400 V2R3 Configuration
--------------------------------------------------
The Extended DOS PC Support/400 configuration program allows you
to choose whether to use OS/2 communications for DOS. A new entry,
VDMR, is added to your CONFIG.PCS file. There are 3 possible
values for the VDMR entry:
VDMR 0 - Always start the "native" Extended DOS PC
Support/400 Router.
VDMR 1 - Always start the "virtual" router to use OS/2
communications.
VDMR 2 - Use the virtual router if available, otherwise
use the native router.
Below is a screen from the CFGPCS utility, From the initial menu,
select "General Options" and then select "OS/2 communications for DOS".
Choose either "Yes" or "When Available", to add the VDMR 1 or VDMR 2
entry to CONFIG.PCS.
--- CFGPCS --- Extended DOS PC Support/400 --------------------------------
| |
| General Options for PC Support |
| |
| Select one of the following. |
| |
| Location of PC Support functions |
| Update personal computer applications |
| Error logging options |
| National language options |
| Administration options |
| Select DOS Support |
| Microsoft Windows and DOS 5.0 options |
| > OS/2 communications options for DOS |
---------------------------------------------------------------------------
--- CFGPCS --- Extended DOS PC Support/400 --------------------------------
| |
| General Options for PC Support |
| |
| ======================================================================= |
| | OS/2 Communications Options for DOS | |
| | | |
| | Allows you to use OS/2 communications for the Extended DOS version | |
| | of PC Support in DOS sessions. | |
| | | |
| | Use OS/2 communications | |
| | for DOS . . . . . . . . . . . . . . . . 1. Yes | |
| | 2. No | |
| | > 3. When available | |
| ======================================================================= |
| |
---------------------------------------------------------------------------
III. OS/2 PC Support/400 V2R3 Configuration
-------------------------------------------
The OS/2 PC Support/400 configuration program allows you to choose
whether to enable "OS/2 Communications for DOS". If the support is enabled
then the device drivers for VDM support are added to the OS/2 CONFIG.SYS:
CONFIG.SYS entries to enable DOS VDM support
...
DEVICE=C:\PCSOS2\EHNPCVDD.SYS
DEVICE=C:\PCSOS2\EHNPCPDD.SYS
...
And the command to start the OS/2 VDM Server Router (VDMSERV.EXE)
is added to STARTPCS.CMD:
...
:SVDMSERV
VDMSERV /Z
@IF ERRORLEVEL 20 GOTO EXIT
:EVDMSERV
--- CFGPCS --- OS/2 PC Support/400 ----------------------------------------
| |
| General Options for PC Support |
| |
| Select one of the following. |
| |
| Location of PC Support functions |
| Update personal computer applications |
| Error logging options |
| National language options |
| Administration options |
| > OS/2 communications options for DOS |
| |
---------------------------------------------------------------------------
--- CFGPCS --- OS/2 PC Support/400 ----------------------------------------
| |
| General Options for PC Support |
| |
| ======================================================================= |
| | OS/2 Communications Options for DOS | |
| | | |
| | Allows you to use OS/2 communications for the Extended DOS version | |
| | of PC Support in DOS sessions. | |
| | | |
| | Configure OS/2 communications | |
| | for DOS . . . . . . . . . . . . . . . . > 1. Yes | |
| | 2. No | |
| ======================================================================= |
| |
---------------------------------------------------------------------------
IV. Additional OS/2 Communication Configuration
-----------------------------------------------
Communications Manager/2
------------------------
Support for the DOS Virtual Router Interface does not require
any special configuration requirements in CM/2 other than
normal 5250 emulation and as such it will not be covered here.
LAN Fast Path
-------------
To support LAN Fast Path (LFP) in the WIN-OS/2 environment, two
special device drivers supplied with LAPS are required. These
drivers provide the virtual NetBIOS and IEEE 802.2 support which
enables the sharing of the network adapter by multiple DOS (LFPWIN)
and OS/2 (CM/2) communications programs. Make sure the following
entries have been added to CONFIG.SYS (LAPS v2.2 will add these
entries when a network adapter is configured).
...
DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
...
Also, when loading the LFPWIN.EXE TSR be sure to specify the "-o"
option. This option instructs LFPWIN to perform a logical open
of the adapter, and is required in the WIN-OS/2 environment.
Shared Folders
--------------
If you intend to use PC Support/400 Shared Folders, configure
the drives under OS/2 PC Support/400. This will allow all
sessions (DOS, OS/2 and Windows) to "see" the network drives.
Using DOS PC Support/400 Shared Folders, while possible, will allow
only the single DOS session to "see" the network drives. The
Shared Folders feature of PC Support/400 is not required for
PROGRESS AS/400 client/server communications.
V. PROGRESS/Windows version 7 Application Settings
--------------------------------------------------
After all the communications options are configured, it is
necessary to "add" PROGRESS/Windows to the OS/2 Workplace Shell
Desktop. There are multiple ways to accomplish this task. The
OS/2 Migration Utility detailed below, while not necessary the
simplest, it is the most complete.
The OS/2 Desktop provides the ability to "migrate" applications to
the desktop. The migration utility provides the ability to add
OS/2, DOS and Windows applications to the OS/2 Desktop and at the
same time provide the correct program settings for proper operation.
Providing the correct program setting is very important especially for
Windows based applications that utilize OS/2 communications features.
It is also possible to add PROGRESS to the desktop by copying an
existing program icon (or program template from the template folder)
and manually changing the program settings. The OS/2 Migration
Utility is a more fool proof method to accomplish this task.
OS/2 Migration Utility
----------------------
On the OS/2 Desktop under "System Setup" you will find a program
icon "Migrate Applications". This is the Migration Utility, that
we will use to "add" PROGRESS to the Desktop. The migration utility
will search the specified list of drives for applications that are
listed in the migration database. To load PROGRESS, we can provide
a custom migration database in which we can provide all the correct
program settings for PROGRESS to execute. Below is a sample of the
source file "WINAPPS.TXT" that is used to create a custom migration
database "WINAPPS.DAT". This sample defines the a single "Windows"
application, "PROGRESS/400 v7.3a (PCS)" that is identified (and
searched for) by it's executable name (e.g. _proas4.exe). The OS/2
command "PARSEDB" (run from the \OS2\INSTALL directory) is used to
create the database from the source text file:
PARSEDB DBTAGS.DAT WinApps.txt WinApps.DAT
The WinApps.DAT file is then used by the Migration utility to "Add"
PROGRESS to the desktop. The important feature of creating a migration
database is that we can control the program settings. The sample listed
shows settings that are recommended for proper operation of PROGRESS in
an AS/400 client/server environment. Here are of few of the settings
explained:
- FOLDER Name of the folder (e.g. program group) where
the program icon for PROGRESS is created.
- WORK_DIR Working directory, this parameter is ignored
for non-OS/2 program icons. This can create
a real annoyance. You cannot set the current
directory to an application/database directory.
- DOS_AUTOEXEC OS/2 allows you to specify an alternative
name to the default "autoexec.bat" startup
batch file and pass parameters to it. This
example uses a batch file "pro73a.bat" and
also passes a parameter "PCS" to it. See the
listing of pro73a.bat below for details.
- COMMON_SESSION This option determines whether OS/2 loads
a separate Windows VM for this session or shares a
Windows VM (like a real Windows machine) with other
Windows applications. Setting this off has an adverse
affect on memory consumption, although it will allow
multiple copies of PROGRESS to run concurrently
without interfering with one another.
REM ===========================================================================
REM Winapps.txt -- migration data for PROGRESS v7 Windows.
REM Use the following OS/2 command from \OS2\INSTALL directory
REM to create a migration database. Run the "Migrate Applications" utility
REM under the "System Setup" folder with the new database, WinApps.DAT.
REM This will add the Program Icon for v7 PROGRESS in a folder.
REM
REM PARSEDB DBTAGS.DAT WinApps.txt WinApps.DAT
REM ============================= data begins ==============================
REM ---------------------------------------------------------------------------
REM PROGRESS v7.3A AS/400 (PCS interface)
REM ---------------------------------------------------------------------------
NAME _proas4.EXE // PROGRESS executable name
TITLE PROGRESS/400 v7.3a (PCS)
TYPE Windows
ASSOC_FILE NULL
DEF_DIR \win73
FOLDER PROGRESS
PARAMETERS -p _desk.p
WORK_DIR \win73\demo
COMMON_SESSION ON // OFF to start multiple copies
WIN_RUNMODE ENHANCED
SESSION_MODE WINDOWED
DOS_AUTOEXEC c:\vdmstart\pro73a.BAT PCS
DOS_BACKGROUND_EXECUTION ON
DOS_HIGH ON
DOS_RMSIZE 640
DOS_UMB OFF // Must be OFF for lfpwin
DPMI_DOS_API ENABLED
DPMI_MEMORY_LIMIT 64
DPMI_NETWORK_BUFF_SIZE 8
EMS_FRAME_LOCATION NONE
IDLE_SECONDS 0
IDLE_SENSITIVITY 75 // value affects performance
INT_DURING_IO ON
KBD_CTRL_BYPASS NONE
MOUSE_EXCLUSIVE_ACCESS OFF
REM ============================= data ends ==============================
The WinApp.txt source text file references a startup autoexec file
(DOS_AUTOEXEC) listed below.
REM ===========================================================================
REM pro73a.bat -- startup batch file for v7 PROGRESS and PC Support/400
REM
REM This batch file sets PROGRESS environment variables and optionally
REM loads PC Support/400 if parameter %1 is present.
REM Optionally loading PC Support/400 allow this same batch file to be
REM used to load both PROGRESS and a DOS command prompt with the same
REM environment settings.
REM
REM ===========================================================================
@ECHO ON
PATH .\;C:\OS2;C:\OS2\MDOS;C:\OS2\MDOS\WINOS2;c:\bin;c:\util;c:\pcs;
set PROMPT=pro73A $p$g
set DLC=k:\u\73a\dlc
set PROCFG=%DLC%\progress.cfg
set PROSRV=%DLC%\_mprosrv
set PROMSGS=%DLC%\promsgs
set PROCONV=%DLC%\convmap.cp
set DLCDB=%DLC%
set PROBUILD=%DLC%\probuild
set PROLOAD=%DLC%\probuild
set DLCLOAD=%DLC%\probuild
set PROEXE=win _prowin -wx
set PATH=%PATH%;%DLC%\bin.win;
set PROPATH=.;%DLC%\gui;
REM --- Start PCSupport/400 in DOS VDM ---
REM --- conditional load of PCSupport if an arg 1 is present ---
if (%1x)==(x) goto COMPLETE
SET EHNP=C:\PCS
SET EHNL=2924
c:
cd \pcs
pcsxi
REM --- Virtual Router does not prompt for userid/password ---
startrtr config.pcs
pcswin /B=48
cd c:\util\lfpwin -o
:COMPLETE
@echo on
REM ============================= end ========================================
VI. Hardware Resources
----------------------
To support a PROGRESS v7 AS/400 client on OS/2 requires a PC workstation
with quite a lot of horsepower. CPU's less that 486/33 or 486/66 will
most likely yield unsatisfactory performance. Also, the software
requirements necessary to support this environment demand a machine
with a minimum of 32MB of memory. Although OS/2 does support virtual
memory (e.g. memory overcommit), performance on a machine with less than
32MB will suffer. It is assumed that most installations will also have
a LAN environment (e.g. Netware, IBM LAN Server) which is accounted for
in the 32MB requirement.
VII. Alternative Configurations
-------------------------------
The following is a list of possible alternative configurations to
both reduce the 32MB memory requirement and decrease PROGRESS
startup time.
Netware for SAA
---------------
It is possible to run PROGRESS v7 on OS/2 to the Netware for SAA
server if the OS/2 workstation is also running Netware Requester
for OS/2. This configuration removes the requirement for Comm Mgr/2,
DOS PC Support/400 and OS/2 PC Support/400 thus significantly
reducing the memory needed. If you can already support the Netware
for SAA environment from DOS/Windows it is fairly simple to enable it
for OS/2. Using Novell's OS/2 Install tool, you have to Enable "IPX Support
for DOS and Windows". This loads a virtual IPX driver in VDM's. This
allows the Netware SAA router (strnrtr.exe) to be started from a DOS
session (or from an autoexec.bat startup batch file from a Windows session).
Remember the CSNA parameter must be correctly set in CONFIG.PCS and the
Netware Requester for OS/2 must be running.
Decreasing PROGRESS Load Time
------------------------------
Starting up PROGRESS v7 in the WIN-OS/2 environment can take
considerable time since OS/2 must perform 2 additional steps
before running the PROGRESS executable. Below is a list of those
steps.
1. Run the startup autoexec.bat file.
- set environment variables.
- start DOS PC Support/400.
- start LFPWIN
- etc.
2. Start the Windows VM.
3. Start the PROGRESS executable.
It is possible to get PROGRESS to load faster by first loading
another Windows application that will perform steps 1 and 2 listed
above. Choosing a simple Windows application (CLOCK.EXE) will keep
the memory requirements down.
When you attempt to start PROGRESS, OS/2 will find an existing
Windows VM running and use it for the PROGRESS. This will eliminate
the startup overhead of running autoexec.bat and loading the Windows VM.
Note, this option is only applicable to Windows apps running in a
Common Session.
Reference
---------
OS/2 Version 2.1 "Installation Guide".
OS/2 Version 2.1 "Using the Operating System".
Using V2R3 DOS and OS/2 PC Support/400 under OS/2 2.1 (Red Book) GG24-4070-00
OS/2 2.11 Unleashed 2nd Edition, David Moskowitz, David Kerr, SAMS Publishing
Progress Software Technical Support Note # 13577