PLATFORM: Progress for OpenVMS VAX and OpenVMS Alpha
SOFTWARE RELEASE: 8.1A03
INSTALL COMMAND: See Below
These release notes describe problems specific to the OpenVMS implementation of Progress. Please reference your Progress 8.1A release notes to reference general Progress issues.
1. GENERAL ISSUES
1.1 Product Versions Supported
This release supports the following versions of the OpenVMS operating system:
VAX: VAX/VMS V5.5-2, VAX/VMS V6.0, OpenVMS V6.1, V6.2, V7.0, V7.1
Alpha: OpenVMS V6.1, V6.2, V7.0. V7.1
This release has been qualified on the following networking variants:
UCX V3.3 (TCP/IP Services for OpenVMS)
UCX V4.0, UCX V4.0A, UCX V4.1 (TCP/IP Services for OpenVMS)
TCPware V5.0-3B (Process Software TCP/IP Services for OpenVMS)
DECnet Phase IV
Pathworks Client V5.0C
Pathworks Server V5.1
This release has been qualified on the following CDD versions:
CDD V5.3, V6.1
1.2 Removal of TK-50 Media for OpenVMS Alpha
For OpenVMS Alpha, this is the first release of PROGRESS that will not be distributed on TK-50 tape. If you install PROGRESS from TK-50 on OpenVMS Alpha, you must switch to either CD-ROM or 4mm DAT.
1.3 Installation from SYSTEM Account
PROGRESS must be installed from a fully privileged account. The SYSTEM account is recommended but an equally privileged account may be used if necessary.
1.4 Use of DEC C Sharable Library
If you are running VMS/VAX V5.5-2 or V6.0, you will have to install the DEC C Run Time Library included on your PROGRESS distribution media before you install PROGRESS. This kit is provided to Progress Software Corporation by Digital Equipment Corporation and is supported by Digital. Installation of this kit is completed via the VMSINSTAL procedure. To install, load your installation media and type the following command from a privileged account:
@SYS$UPDATE:VMSINSTAL AACRT060 ddcu:
where 'ddcu:' is the tape installation media (TK, MU, MK, etc.).
If you are installing from CD-ROM, type the following from a privileged account:
@SYS$UPDATE:VMSINSTAL AACRT060 ddcu:[DECC_RTL_VAX]
where 'ddcu:' is the CD-ROM installation media device (DU, DK, etc.).
The installation utility will ask you some questions; accept the default answers and let the installation proceed.
Once the DEC C Run Time Library installation is complete, you may proceed with your PROGRESS installation.
If you are running any other version of the operating system, the required DEC C libraries are already included on your system and installation of this special kit is not necessary.
1.5 Transfering Encrypted Sources to OpenVMS
Due to the different OpenVMS file formats, encrypted source files transfered to OpenVMS must be transfered in variable length format. This can be done with the bundle/unbundle utilities provided in the Toolkit installation option. Failure to transfer these files correctly will result in syntax errors during compilation.
1.6 Use of C Compiler for ESQL/C
Progress Software has been made aware of a number of issues when compiling C source code to be included in an ESQL client image. Progress Software uses Digital's DEC C V5.0 compiler to compile Progress source code into the objects which are provided in the Progress directories on your system. Progress uses and recommends the use of the following syntax and qualifiers when compiling:
$ cc /decc /standard=relaxed_ansi /g_float -
/prefix_library_entries=all_entries -
/Assume=Writable_String_Literals -
/warnings=disable=(implicitfunc)
Refer to your DEC C documentation or the HELP command for details about the various qualifiers used. See the [.HLC.EXAMPLES]COMPILE.COM procedure under the "DLC" directory for an example compilation procedure.
If you are using an earlier version of the DEC C compiler, Progress strongly recommends that you upgrade your DEC C compiler to at least V5.0. If you do not upgrade you may receive link time warnings about symbols that do not exist. These symbols may be defined in the later compiler version, but not in the earlier versions.
If you are using the Digital's VAX C compiler, Progress strongly recommends you investigate upgrading to at least the DEC C V5.0 compiler. Using the VAX C compiler you will receive link time warnings about symbols that do not exist. In order to rectify the symbols from VAX C, you must add the following line to the load script (by default LDHLIC.COM) created for you when you used the
PROBUILD.COM procedure:
SYS$SHARE:VAXCRTL/SHARE
This line should be added directly above the "stack=20" line. This will resolve any symbols used by the VAX C compiler.
1.7 Use of ".D" and ".DF" file extensions
The .D and .DF extensions are "reserved" to Progress Software Corporation in order to signify database data and definitions files. When the Progress image discovers it is reading a .D or .DF file it believes that it is loading the database and thus ensures the format of the file to be in "STREAM_LF" format. Thus if you use .D or .DF for your own personal data files and then read them into Progress, Progress will convert your file format if it is not STREAM_LF. This caused some confusion in the 7.3C release which first introduced this
issue and caused some problems.
1.8 Use of DFS mounted disks for databases
Progress does not support the use of DFS mounted devices to access database files from Progress.
2. NEW FEATURES
2.1 PROGRESS Setup File Provided
The command procedure PROGRESS_SETUP.COM is now provided with
PROGRESS for OpenVMS to allow easy setup of the logicals needed to run PROGRESS. This command procedure is placed in the destination
directory where PROGRESS is installed (your DLC directory). Please
see this setup file for more information about using PROGRESS_SETUP.COM.
This file will be used by the multi-user database servers and DataServers in order to locate the currently installed version of Progress.
2.2 Use of UNIX command line format for Progress on VMS systems
Changes were made to the Progress command line parsing routines to allow for use of UNIX like commands to execute images on your VMS system. Thus, if you set the symbol as follows:
PROUTIL :== $BIN:_PROUTIL.EXE
You will be able to execute commands such as:
PROUTIL "-C" aimage truncate dbname
It is very important to use the double quotes ("") when specifying CAPITALIZED switches; otherwise, the DEC C RTL will force the use of lowercase. Thus a -C would eventually be interpreted as -c.
The command this does not work correctly with the PROGRESS/STRUCTURE commands which would be equivalent to the UNIX "prostrct" commands.
2.3 Shared memory, backing store, and the use of PRO$NOSHM logical
In versions of Progress prior to V8.1A01, if you defined the logical PRO$NOSHM to be 1, Progress would not create a disk backing store file with the name "<dbname>.SHM", rather it would only create a system global section for shared memory when starting a server for a database.
Starting with V8.1A01, this will now become the default. That is, by default when starting a database server, the <dbname>.SHM file will not be created. If you would like to revert to prior functionality, define the following logical in your system startup procedures:
$ DEFINE /SYSTEM PRO$KEEP_SHM 1
2.4 RMS DataServer image now provided
In this release of Progress, the RMSSRV.EXE file has been provided for you, so that you are not required to PROBUILD a new one for the release. You still may choose to PROBUILD if you wish.
3. DOCUMENTATION VARIANCES
3.1 New PROLIB option, "CODEPAGE"
A new option has been added to the PROLIB image. The documentation will list the option on in UNIX format as "-codepage", you may access this on VMS by using the "/CODEPAGE=cpname" qualifier on VMS, where cpname is the name of the codepage you will be using.
3.2 Database Converstion Qualifiers
To access the CONV68 or CONV78 utilities to convert your database from either V6 or V7 format you may use the following command sequence:
PROGRESS/UTILITY=CONV68 <dbname>
or
PROGRESS/UTILITY=CONV78 <dbname>
Be sure to back up your database before attempting the conversion, especially if you have a multivolume database. A VMS restriction limiting the length of database extents to 64 characters was removed for V8, but the change to the database is done is such a way that it is not allowed to be backed out. A VMS COPY of the ".db" file should be made in case the conversion fails.
3.3 Using the "REPAIR" qualifier for Multi Volume Databases
The REPAIR qualifier has been added to PROGRES/STRUCTURE command. This command mimics the UNIX "prostrct repair" and has syntax as follows:
PROGRESS/STRUCTURE/REPAIR=<repair.st> <mv-dbname>
3.4 Running the Progress Application Server
In order to run the Progress Application Server, you must use the foreign command syntax and provide parameters to the images as they are defined for the UNIX systems in the documentation. A VMS foreign command is a way to run VMS images directly from DCL without needing to provide a command definition file (file.CLD). You must first define a symbol to point at the image you wish to run, then invoke the image from the symbol as follows:
proapbk := $BIN:_proapbk.exe
proapbk "-S" myservc "-H" myhost "-N" tcp
This will start an application server using the service name "myservc" on the current node from which a client can connect to and run code from as defined in the Application Server documentation.
In order to assist you, a "starter" command file is provided at BIN:PROAPBK.COM. Customize the command file as necessary for your environment. It is meant to be modified and enhanced, not just as a use as is file.
3.5 Use of the Oracle Dataserver
Included in your documentation is the V7 Oracle Guide for VMS. Please refer to this guide for general information regarding the use of the Oracle dataserver. The V8 Oracle Dataserver documentation is also included with your documentation. Please refer to it for new V8 Query Tuning features.
3.6 Oracle Dataserver documentation errors
In the V8 Systems Administration Guide, Appendix B the description for
building the Remote ORACLE Dataserver is incorrect for linking the
Progress.exe.
In the examples that follow, the name and location of the options file
should be the name and location of where you specified in PROBUILD.
If you are using V7.0 of Oracle:
$@[ORACLE7.ROOT.RDBMS]LNDCIC2.COM PROGRESS.EXE LDORASRV/OPT
If you are using V7.1, 7.2 or 7.3 of Oracle:
$@[ORACLE7.ROOT.RDBMS]LNOCIC.COM PROGRESS.EXE LDORASRV/OPT
4. SOFTWARE CORRECTION NOTES
4.1 Database Accessibility from either VAX or Alpha Operating System
A restriction from the V7 releases preventing the same database file to be opened from either a VAX or an Alpha system without truncating the .BI file has been removed. It is now possible to access your database from a VAX system and then access the same file from an Alpha system. However, you still must select either a VAX or an Alpha system to be the main server system. This change only deals with having the ability to access the database from either platform in case of primary node failure.
4.2 New Default Setting for Century (-yy) Parameter
For PROGRESS Versions 8.2A, 7.3E and 8.1A01, the default setting for the Century (-yy) parameter is now 1950. Prior to these versions of PROGRESS, the -yy default was 1900. The -yy parameter controls how a 2-digit year gets expanded into a 4-digit year. It does not define a "default" century. Instead, it defines a 100-year period in which it is safe and legal to use 1 or 2-digit year designations. The new default is in preparation for the year 2000.
Changing -yy to 1950 will cause PROGRESS to look at any 2-digit year "nn" and make it be 19nn if nn is >= 50, and 20nn if nn is < 50. This means that:
01/01/99 will be 01/01/1999 and
01/01/00 will be 01/01/2000
With this new default, the following line (if run on December 31, 1999):
DISPLAY TODAY TODAY + 1.
gives the following output:
12/31/99 01/01/00
Similarly, the following line (if run on Jan 1, 2000):
DISPLAY TODAY - 1 TODAY.
gives the same output as above.
If you do not want to use the new default, you can set -yy to 1900 and
PROGRESS will behave exactly as before.
If you want to change the setting of the -yy parameter, you should choose a 100-year span like 1920 to 2020, or perhaps 1910 to 2010. The setting you choose should best cover the dates you have to accommodate, such as birthdays and future mortgages (30 yr future dates, etc.). Once you have set -yy to a suitable setting, you can use a 2-year date format ("99/99/99") for dates inside the range you define. You should use a 4-year date format ("99/99/9999") for dates falling outside of the range you define.
4.3 Missing "ADM" source files. (V8.1A01)
The "ADM" source files were inadvertantly left out of the V8.1A Commercial Release archives. These files are now included in this release.
4.4 Progress "DLC:HELLO." file has wrong information. (V8.1A01)
The V8.1A Commercial Release inadvertantly included the field test copy of the "DLC:HELLO." file. This release resolves this problem.
4.5 Fix problem with overwritten value used in /message_buffer_size or "-Mm" (V8.1A01)
This release resolves a problem where the /message_buffer_size" was
being ignored at server startup.
4.6 Remove Progress Core dump when use VMS system service sys$forcex (V8.1A01)
This release resolves a problem where if you used your own crafted
routine to perform a sys$forcex on a client connection, the database server would crash.
While this release does resolve the database server crashing problem,
Progress Software reminds you that performing a forced exit on a client which is in the middle of a transaction or micro-transaction will cause the database server to be shut down. This is due to the desire to protect your data at all costs. Progress Software strongly recommends the usage of the forced exit through the Progress defined interfaces. To do this, a "PROGRESS/MULTI_USER=SHUTDOWN/DISCONNECT=<pid>", where <pid> is the
Extented PID listed in a "SHOW SYSTEM" command or the "pid" listed in the Progress MONitor display.
4.7 OS-DELETE does not allow for deletion of specific version of a file. (V8.1A01)
This release resolves a problem where the Progress 4GL command OS-DELETE would only delete the most current version of a file. Thus if you had 3 files such as :
foo.bar;3
foo.bar;2
foo.bar;1
and you attempted to do an OS-DELETE("foo.bar;2"), the foo.bar;3 would be erroneously deleted.
4.8 Removal of code to set Max Record Size and Long Record Length (V8.1A01)
This release removes some code which forced the maximum record size and longest record length of a file to be 256 when created with the 4GL syntax "OUTPUT TO". This code caused problems for existing applications which copied/appended output files created with earlier versions of Progress. The original problem reported to Progress was the inability to use the VMS DCL "TYPE/TAIL" utility with files created by the "OUTPUT TO" statement.
Making this change will not allow TYPE/TAIL to work correctly again;
however, by either adding the following line to your 4GL code immediately after the "OUTPUT CLOSE" statement or by issuing the same command at the DCL $ prompt you will get the same results:
VMS SILENT "SET FILE/ATTRIBUTES=(MRS=256,LRL=256) <filename>"
Where <filename> is the file you have created. You must have at least
OpenVMS V6.1 or greater to issue this command.
4.9 Cannot connect to 8.1A AppServer from 8.2A client. (V8.1A01)
This release resolves a problem connecting an 8.2A Progress client to an V8.1A Progress AppServer.
4.10 Fix usage of 4GL syntx "RETURN NO-APPLY" (V8.1A01)
This release fixes a problem which allows the use of the 4GL syntax
"RETURN NO-APPLY" from within a persistent procedure to get the effect
of "RETURN NO-APPLY" without resorting to "RETURN ERROR" (which as of
8.1A, causes an UNDO of the procedure from which it is returning).
4.11 Closing via sqldynclose() causes hang. (V8.1A01)
This release resolves a problem where calling sqldynclose, using the
SQL_STMTCLS option for multiple cursors, with the closes not in the
same order as the opens caused a hang.
4.12 PROPATH issues (V8.1A01)
This release fixes a problem with PROPATH where Progress did not find
the correct version of a file that existed in multiple areas within the PROPATH. This problem was seen when the PROPATH consisted entirely of ROOTED logicals (define/translation=concealed) and the PROPATH was defined to not look in the current working directory (no "," as a PROPATH element). The client attempted to run a procedure which ran another procedure out of the PROPATH. In the case seen, the second procedure run was not from the correct directory. A case example:
topfoo
foo1 foo2 foo3
progs progs progs
bar.p foo.p foo.p
foo.p bar.p bar.p
Where each foo.p uses the 4GL syntax: "display running foo#/foo.p", and # is the number of the directory. The bar.p does a "run progs/foo.p".
Defining the path as follows:
define/trans=conc foo1 disk:[topfoo.foo1.]
define/trans=conc foo2 disk:[topfoo.foo2.]
define/trans=conc foo3 disk:[topfoo.foo3.]
define propath "foo1,foo2,foo3"
When running in the procedure editor "run progs/bar.p", Progress returned "Running foo2/foo.p".
4.13 "REMOVE" option to PROGRESS/STRUCTURE/REMOVE= doesn't include AI removal. (V8.1A01)
This release fixes a problem where the ability to remove an AI file from a multivolume database through the command interface was missing.
The command syntax is: PROGRESS/STRUCTURE/REMOVE=AI <dbname>
4.14 Open Interface Broker shuts down upon client connection request. (V8.1A01)
This release fixes a problem in the Open Interface Broker where a
client attempting to make a connection the Broker would shutdown before starting an Open Interface Driver. The bug existed only when the Broker was using the TCP/IP protocol for network transport.
While this bug was found in the OI Broker, it could also exist in other Progress images, and has been fixed there as well.
4.15 SEARCH function fails to find file if it cannot READ it (V8.1A01)
This release resolves a problem where Progress would fail to find a file using the 4GL "SEARCH" command if the file was either already open (and thus locked by RMS for shared reads) or if the file didn't have the read privilege available.
4.16 OS-COPY command not working correctly for RMS Sequential files (V8.1A01)
This release fixes a problem where using the OS-COPY command in Progress incorrectly copied an RMS "sequential" formatted file to a stream_lf file.
4.17 Cannot open network file (V8.1A02)
This release resolves a problem in using the <ESC>-O or "File" menu
option to open a networked file. Prior to the fix, the file would not
be opened and Progress would display an error dialog box stating that the file could not be opened because the "file may be too large to open".
A networked file uses the following syntax:
nodename::disk:[directory]file.p
4.18 Saving "Untitled" buffer, saves wrong record format for file. (V8.1A02)
This release resolves a problem where saving the untitled buffer as a
new file, saved it using a "variable record format". The file is now
saved as expected in "Stream_LF record format".
4.19 Unable to PROBKUP with AFTER_IMAGE file. (V8.1A02)
This release resolves a problem where running PROBKUP on a database with after imaging enabled was unable to supply the after image file name argument. The following sequenced produced the error:
progress/create sports sports
progress/util=aimage_begin/after_image=sports.ai sports
progress/after_image=sports.ai sports
<do some processing - such a "create customer". and exit from progress.>
progress/backup sports sports
<results in error>:
You must supply the -a ai-file-name parameter. (875)
%PROGRESS-F-BADEXIT, Abnormal termination has occured
4.20 Progress Roll Forward Utility on VMS does not support endtime and endtrans (V8.1A02)
This release resolves a problem where the Roll Forward utility on VMS
did not support the "endtime" and "endtrans" qualifiers through the CLI to Progress. The following are the commands in UNIX format:
rfutil sports -C roll forward -a sports -C endtime yyyy:mm:dd:hh:mm:ss
rfutil sports -C roll forward -a sports -C endtrans transaction-number
This has been now fixed. Utilize the new options on VMS using the
"/ENDTRANS=" or "/ENDTIME=" qualifiers to the Roll Forward Utility.
The the following commands will now work:
$ progress/utility=roll_forward/after_image=sports -
/endtime=yyyy:mm:dd:hh:mm:ss sports
$ progress/utility=roll_forward/after_image=sports -
/endtrans=transaction-number sports
Where the "yyyy:mm:dd:hh:mm:ss" is replaced by a valid year, month, day, hour, minute, and second value and the "transaction-number" is replaced by a number representing the transaction number to roll forward to. See the Progress System Administration Reference for details.
4.21 SAVE INTO option for source code compilation incorrectly saves file. (V8.1A02)
The SAVE INTO option of the compile statement did not append the path of the source program. Page 161 of the language reference manual A-F states:
If you specify a relative pathname for the source file, that pathname is appended to the SAVE INTO path. For example:
PROPATH "/pro1/source".
COMPILE test/proc1.p SAVE INTO /pro1/obj.
In the example, progress should save the source file "/pro1/source/test/proc1.p" as "/pro1/obj/test/proc1.r". Instead it
was saved to "/pro1/obj/proc1.r", ignoring the pathname of the source file.
This has now been fixed and the file is saved correctly.
4.22 Watchdog disconnects dead user with no evidence of login(V8.1A03)
This release solves the problem where the watchdog was detecting dead
users which appeared to never have been logged in. The user had
actually started to login, and exited before writing the login message to the log file.
4.23 Hangup signal crashes the database (V8.1A03)
This release solves the problem that the Hangup signal can occaisionally cause the database to crash. This can occur in the following situations:
(1) when the user could be immediately disconnected and a message was printed to the screen.
(2) when a user is killed while it is backing out a transaction.
4.24 Remote Time check crashed database (V8.1A03)
This release solves the problem that the failure of a call to get the time on a remote machine crashed the database.
If the remote time call fails, the call will be retried, getting the time from the local machine.
5. UNRESOLVED ISSUES
Progress Software has identified the following issues that are yet resolved.
5.1 Client LOGIN Fails on Long Database Path
A remote login will fail if the database path name is too long. For remote dataservers, this includes user name and password. The server log will post the following message:
SRV 0: Login refused; client has version 17 and server has version 40.
Do not use database paths greater than 50 characters. A database path is defined as:
<device>:[directory]<database name>.DB
5.2 PROAIW, PROBIW, PROAPW PROCEDURES Located in BIN not DLC
The documentation incorrectly states the location of these utility
procedures as being in the DLC directory. They are located in the BIN
directory. The BIN logical can be defined as:
$ DEFINE BIN <device>:[DLC.BIN]
Then the procedures can be run:
$ @BIN:PROBIW
You must have privileges to write to the "BIN:" directory; otherwise, you must copy the file to your current working directory and run it from there since the command file creates a command file which is then used to run the selected writer image in the background.
5.3 BULKLOAD Must be Run Where Data is Located
You must run BULKLOAD from the directory where the data is located or PROGRESS will generate the following errors:
Data input file "<filename>.d" could not be opened. (1505)
Bulk load aborted near "<filename>" because of errors. (1507)
5.4 Installation From a Search List Directory Structure
Make sure that the target directory (i.e., the DLC directory)of your PROGRESS installation does not include a search list of logical names.
For example, do not try to install into SYS$SYSROOT:[DLC], because
SYS$SYSROOT is a search list logical. Pick a specific location or
use the default SYS$SYSDEVICE:[DLC]. The target directory can be on a
logical disk that is a stripe set, a shadow set, or a multivolume set,
as long as it is one logical device.
5.5 Error from PROINSTALL
If you get the following error from PROINSTALL.COM:
TERM not found in VVTERMCAP file
your terminal is not recognized. This is likely to happen if your
terminal type has not been set correctly with the OpenVMS SET TERMINAL
command or you have the logical PROTERM defined in the system logical
name table or within your SYS$SYLOGIN.COM or LOGIN.COM procedures. To resolve this, issue the SET TERMINAL command to correctly set your
terminal type or clear the PROTERM definition with the OpenVMS DEASSIGN command or define PROTERM as follows:
$ define PROTERM VT100
5.6 Error from PROINSTALL
Getting the "Device already allocated" message that means that the tape device was not DEALLOCATED after backing down the first saveset from the tape and before running PROINSTALL. You must DEALLOCATE the tape device before your installation can continue successfully.
5.7 CTRL/U Key Functions the Same as CTRL/X
In the Application Development Environment, the CTRL/U character is
documented as performing a "BACK-TAB" function. Due to the way the
OpenVMS Terminal Driver works, CTRL/U is equated to CTRL/X and performs a "GO" function.
5.8 Use of DECnet/OSI
Progress Software does not support DECnet/OSI in Phase V mode. You must be running DECnet in Phase IV compatibility mode. In addition, it has been determined that using a Windows for Workgroups V3.11 client does not work in all cases.
5.9 Editing Progress-Created Files From Non-OpenVMS Editors
If you edit PROGRESS created and/or provided files from non-OpenVMS
editors, the file attributes of the resulting file may be changed by
the editor from the type PROGRESS had created and expects to find. In particular, some editors change STREAM_LF files to some other format.
The "Record Format" field of OpenVMS DIRECTORY/FULL command will display the format of the file. It may be necessary to convert the file back to STREAM_LF in order for PROGRESS to read it. Use the following OpenVMS command to set your file attributes correctly again:
$ SET FILE /ATTRIBUTES=RFM:STMLF <file>
Also, since the record length may be affected as well, use the following command to correctly reset it:
$ SET FILE /ATTRIBUTES=LRL:32767 <file>
5.10 DECnet client using service name in use to another database.
Due to DECnet creating service name objects while the system is running, it is possible to receive one of two messages when attempting to make a client connection using DECnet when a database server is not running for the service name chosen and the service name is already servicing another database. For example, if two database startups were as follows:
PROGRESS /MULTI=START /SERVICE=NAME1 /NETWORK=DECNET DB1
PROGRESS /MULTI=START /SERVICE=NAME1 /NETWORK=DECNET DB2
The second startup would fail, but if a client unknowingly attempted a LOGIN to DB2 using service NAME1, it may receive one of the following errors:
Disconnected from server because database name was incorrect.(437)
Server rejected login.(700)
or
Error reading socket,ret=1 errno=8420 (778)
The first error message is the correct one, but the second one is misleading. Two extra messages were added to help the client decipher the failure:
Check to ensure there is an active server for the database.
Check to ensure the service name is not in use for another database.
Progress hopes this helps clear up client confusion as to why the attempted connection has failed.
5.11 Application Server has no DECnet capabilities
The Progress Application Server does not support DECnet for its clients. Progress only supports TCP/IP as the client front end to the Application Server.
It is possible to have the Application Server connect to a database
server that is being served using DECnet by using optional Application Server connect parameters or by having the P-Code run by the Application Server connect to the database via DECnet.