Kbase 11223: VMS 6.2L Functionality Changes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
VMS 6.2L Functionality Changes
INTRODUCTION:
=============
This Technical Support Knowledgebase Entry describes the
FUNCTIONALITY changes in PROGRESS 6.2L on VMS.
WHY YOU NEED TO KNOW THIS:
==========================
The changes in functionality are significant. The BACKUP, PROLIB and
BATCH utilities have changed. This entry will help you determine
whether user's applications will be affected, and whether you need to
make changes to maintain existing application functionality.
THE /BATCH Option
In previous versions of PROGRESS on VMS, if you use the /BATCH option
WITHOUT the /NOINTERACTIVE qualifier, the PROGRESS session is NOT
submitted as a batch job. Instead, it is executed in the current
process stream. In addition, if you use /BATCH=xxx$BATCH where
xxx$BATCH is a different queue, the same behavior results.
In 6.2L, if you use the /BATCH option PROGRESS creates a
NEW batch process to the specified queue, or to the default queue if
none is specified. Users should REVIEW DCL command procedures that
use the /BATCH option to verify that the command procedure
will be in line with the new functionality.
When submitting a Progress batch command from a batch job, you must
use the /NOINTERACTIVE qualifier. To have the previous functionality,
of the /BATCH command, use the /NOINTERACTIVE qualifier INSTEAD of the
/BATCH qualifier. When used incorrectly, terminal I/O errors may
result in the log files.
Temporary submit files used for batch submissions are removed before
the batch job invokes PROGRESS, which prevents the files from
being left in directories, due to process aborts and abnormal term-
ination.
The naming convention of log files has been modified to "PROBATCH +
the decimal value of the process id of the submitting process".
BACKUP Functionality
PROGRESS Version 6.2L will allow you to backup databases to multiple
tape volumes. Each tape volume must be initialized prior to executing
the backup procedure. Tapes that have been initialized and
used do not need to be re-initialized. PROGRESS will simply overwrite.
Users are no longer required to issue the MOUNT command prior to load-
ing the tapes for backup, or to issue the DISMOUNT command between
tape volumes.
PROLIB Functionality
PROGRESS Version 6.2L now allows case-insensitive execution of .r code
as well as declaration of libraries in the PROPATH in both UNIX and
VMS style.While PROLIB will accept any ASCII file into the library,
only .r files can be executed. When a file "myfile.p" is specified,
PROGRESS
will search the PROPATH for "myfile.p", but it will NOT search the
library for it. The purpose of PROLIB is to increase performance by
decreasing the search time for .r code. Running .ps out of the
library defeats this purpose.
CLIENT and SERVER Fixes
A significant number of changes have been made to the multiuser code,
both local and remote, in the broker, server, and client product.
Stack dumps when CLIENTs are being disconnected using PROGRESS MONITOR
should no longer occur. The likelihood of error 1007 - "unexpected
wakeup from..." has been reduced, if not eliminated. Overall, Version
6.2L is now more stable and robust. Please encourage your VMS users
to upgrade to PROGRESS 6.2L.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
Release Notes for PROGRESS 6.2L on VMS
Progress Software Technical Support Note # 11223