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

Conference clusta::acms

Title:ACMS comments and questions
Notice:This is not an official software support channel. Kits 5.*
Moderator:CLUSTA::HALLAN
Created:Mon Feb 17 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4179
Total number of notes:15091

4169.0. "login-f-clifail after delta time patch" by CSC32::J_HENSON (Don't get even, get ahead!) Thu May 15 1997 13:51

I want to post this information in case others encounter this.  

There is a delta-time patch that Digital is currently asking customers
to install.  It removes a 9999 day restriction on the some of the
lib$ time routines.  The official ECO names are vaxlibr0x_070
and alplibr0x_070, where x is some number.

I just finished a call with a customer who had installed this eco
on a openvms vax v6.1 system running acms 3.3b.  After installing
the eco, he was unable to start acms.  When he tried to do this,
it failed with the following errors.

%acmsopr-e-strtupsyserr,...
-acmsops-e-accdied,...
-login-f-clifail,...
%acmsopr-f-error,..

To make a long story short, the cause of this failure was that
the librtl*.exe routines which reside in sys$share, and which the
eco replaces, had their protection changed.  In this particular
case, the change was due more to the way in which the customer
updated them than anything else.  For this customer, the 
protection was changed from (rwed,rwed,rwed,re) to (rwed,rwed,re,).
Changing the protection back to it's original setting (for librtl.exe
as well as librtl*.exe) corrected the problem.  An alternate
solution was to grant all default privs to the acc_username account
and the tsc_username account.

I don't know if others will encounter this, but I'm sharing what I've
learned just in case.

Jerry
T.RTitleUserPersonal
Name
DateLines