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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

309.0. "Strange `UDP error messsage' (V3.0)" by JOCKEY::MARSHALLJ (Glad that the devil is red ......) Tue Mar 24 1992 09:21

    Hi,
    
    A customer is currently running BL122 of V3.0 on VMS V5.4-2.
    
    We are getting some strange, intermittent errors which are described
    below, and I can't see any mention of this in the Diamond FT notes file
    so I wondered if anyone could suggest where to start looking to find
    the cause ?
    
    We currently have a problem with users intermittently getting the
    message 'Not privileged to execute function directives in UDPs' when they 
    try to do really normal things, like Create a WP document, or EXit,
    'Intermittently' meaning, they can use the options for most of their 
    session, but then suddenly, with no apparent pattern, or indication, or 
    cause, they get hit by this message. I have been having to stop their 
    processes to let them login again and carry on. It looks like a corruption 
    of something held in memory for the users concerned (possibly). I am unable
    to recreate it at will at the moment, as there is no pattern, but if
    anyone can shed any light, I'd be extremely grateful.
    
    Thanks in advance,
    John
T.RTitleUserPersonal
Name
DateLines
309.1Check PRVUDPFNCSIOG::T_REDMONDThoughts of an Idle MindTue Mar 24 1992 10:248
    What values are PRVUDPFNC and PRVUDPDCL set to?  The first is probably
    stopping functions being executed if it isn't set (it's a profile
    flag).
    
    The UDPs may contain some processing which can't operate without the
    ability to execute functions...
    
    Tony
309.2Upgrade used to turn them off - fixedIOSG::SHOVEDave Shove -- REO-D/3CTue Mar 24 1992 14:2610
    Did you deliberately turn off the new privs (PRVUDPFNC and PRVUDPDCL)
    for your users?
    
    If not, you might want just to turn them all on (PRVOWN and PRVVIEW as
    well, if you have no reason to turn them off).
    
    The upgrade procedures used to set them off - as this could break
    applications, in the SSB kit the upgrade will set them all on (Y).
    
    Dave.
309.3Which BL122??AIMTEC::PORTER_TTerry Porter, ALL-IN-1 Support, Atlanta CSCTue Mar 24 1992 15:389
Which BL122 are you running, I forget how many there were in all but do a
<version and if it is not BL122D dated 24-Jan-1992 try upgrading. 

I assume this is a regestered FT site, in which case call the CSC for more
specific help.

Regards,

Terry
309.4Same thingKERNEL::SALMONJJason SalmonWed Nov 25 1992 16:396
    Hello,
    I've got a customer with the same problem can anyone tell me what the
    outcome was please ?
    
    
    Jason.
309.5Have you checked the flags?OK4ME::CAFE3Jack CreamerWed Nov 25 1992 17:4813
    
    Jason,
    
    In the account(s) that are getting the errors, what are the values of
    the flags given in .1?  Someone will correct me if I'm wrong, but if 
    these flags are set to "N", then the user won't be able to run UDP's 
    that contain explicit function calls.  I would be more specific, but I
    don't have my V3.0 manuals handy.
    
    HTH,
    
    Jack 
    
309.6Are they using UDPs in the first place?DUBSWS::EIJSWed Nov 25 1992 17:5810
    
    Another questions is:
    
    Are you sure that the activities (like the ones mentioned in .0) are
    done with regualr ALL-IN-1 menu options? Meaning, are you sure no UDPs
    are used? These flags shouldn't impact any DO Script processing.
    
    Ciao,
    
    	Simon
309.7KERNEL::SALMONJJason SalmonThu Nov 26 1992 10:5713
    
    re.5
    The values were set to N
    
    re.6 
    The customer tells me that he has no UDP's on his system.
    
    The Problem happens after a while. If they log out and then back in
    again the problem has gone away.
    Only common factor seems to be that the users affected are heavy usage
    users.
    
    Jason.