[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ucrow::desktop_acms

Title:DECtp Desktop for ACMS
Moderator:UCROW::GIBSON
Created:Mon Sep 24 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:859
Total number of notes:3034

854.0. "cannot restart ACMSDI unless restart UCX first" by HGOV08::KENNETH () Thu May 15 1997 04:49

Hi,

My customer is have a similar problem with notes entry #628 of this 
conference.  Whenever the ACMSDI server is stops (or exit by some reason),
it cannot be restart unless UCX is shutdown and reboot.

The error is ACMSDI-F-ERRDURRPCINIT, Error during RPC initialization
for package acmsdi_pkg.

The customer is running ACMSDI V2.1 and UCX V3.2 ECO6.

Is there any solution or workaround yet?

Thanks for your help in advance.

Kenneth Leung
T.RTitleUserPersonal
Name
DateLines
854.1UCROW::GIBSONThu May 15 1997 08:5432
    Kenneth,
    
    Yes the problem was located. They can install the latest release V2.3
    that contains the various fixes and updates. Alternatively if they 
    are not prepared to do a version upgrade they can install an ECO kit.
    
    If your customer is running V2.0 install ECO3, use the directory that
    matches the machine type and VMS version.
    
    d ucrow::acms_desktop$pubdir:[v20.eco3]
    
    Directory ACMS_DESKTOP$PUBDIR:[V20.ECO3]
    
    AXP_V6.DIR;1               1   5-MAR-1996 15:12:36.22  (RWE,RWE,RE,RE)
    VAX_V5.DIR;1               1   5-MAR-1996 15:12:37.74  (RWE,RWE,RE,RE)
    VAX_V6.DIR;1               1   5-MAR-1996 15:12:38.78  (RWE,RWE,RE,RE)
                                                                         
    If they are on V2.2, use its ECO1, including the client updates.
    
    ucrow_dev> d acms_desktop$pubdir:[v22.eco1]
    
    Directory ACMS_DESKTOP$PUBDIR:[V22.ECO1]
    
    ALPHA_V6.DIR;1             1  19-SEP-1996 13:02:46.19 
    MSW31.DIR;1                1   4-OCT-1996 11:43:39.64 
    NT.DIR;1                   1   8-OCT-1996 10:03:20.45 
    VAX_V5.DIR;1               1  19-SEP-1996 13:02:54.65 
    VAX_V6.DIR;1               1  19-SEP-1996 13:02:51.73 
    WIN95.DIR;1                1   8-OCT-1996 10:03:13.54 
    
    
    	/Tom
854.2Already running V2.0 ECO3, but still get the problemHGOV08::KENNETHFri May 16 1997 00:3012
    Hi Tom,
    
    Thanks for your help.  May be I missed in .1, the customer is already
    running V2.0 ECO3.  He found that the TCP/IP connection to the clients
    are already closed when the ACMSDI server dies.  But he have to restart
    UCX in order to let ACMSDI server startup again.
    
    Any ideas?  Is this version V2.0 still supported?
    
    Thanks again for your help.
    
    Kenneth Leung
854.3V2.0 support statusUCROW::KNEELANDThu May 22 1997 13:1414
In general ACMS Desktop positions itself with ACMS for software
related support and development issues.  ACMS notes conference 
topic #4147, cross posted as a reply to this note, addresses recent
discussion regarding support of older ACMS releases.

Desktop Engineering has not applied any ECO related work to 
the V2.0 release (2 releases back from the shipping version 
2.3 since Aug. '96. We have been providing problem analysis 
support for V2.0 with upgrade recommendations where appropriate.




854.4ACMS notes topic #4147UCROW::KNEELANDThu May 22 1997 13:1528
              <<< CLUSTA::TPSSPUBD$:[NOTES$LIBRARY]ACMS.NOTE;1 >>>
                        -< ACMS comments and questions >-
================================================================================
Note 4147.1              ACMS V4.0-1, how much longer ?                   1 of 1
CATMAN::DEFELICE                                     21 lines  10-APR-1997 15:54
                    -< re: ACMS V4.0-1, how much longer ? >-
--------------------------------------------------------------------------------
Software engineering and product management are currently evaluating
the issues involved in providing support for older versions of the
ACMS product.  Although, to date, we have been providing problem
analysis on older ACMS versions, such as V4.0-1, we have not been
performing coding changes to resolve problems.  In some situations
where further problem analysis is required, or when reported problems
have already been resolved in a newer shipping version, we have
requested that the customer perform an upgrade.

ACMS V4.2 is scheduled to ship starting later this month and ACMS V4.1
has been shipping since December 1995.  ACMS V4.1 has been deployed
successfully throughout the world, and ACMS V4.2, which provides
futher product enhancements, will be available to our customers via
the USSSB (4/24) and CONDIST (Alpha 5/23, VAX 6/13).

We would encourage our customers to upgrade to these newer versions so
that ACMS Engineering can provide the highest level of product and
customer support.

Regards,
Bob Defelice	ACMS Engineering Manager