[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

232.0. "Problem with granting PRVAPP" by LEMAN::REGINA (Carrie's in the carrot land) Fri Mar 13 1992 10:20

    Running BL122D (from straight V2.4) we are having problems
    giving PRVAPP privs to some of the users. For the moment it
    looks as if the problem is only there with NAME.CHRISTIAN
    type profiles.
    
    The script CM_SM_SWITCH_PRVAPP dies without log or meaning-
    full message. It does not leave the profile in a proper state,
    as those users get "your profile is being edited" when trying
    to access CM. We tried to give A, user gets OA$PRVAPP granted
    VMS-wise. 
    
    Thanks for any hint.
    Regina
    
T.RTitleUserPersonal
Name
DateLines
232.1Works fine hereSIOG::T_REDMONDThoughts of an Idle MindSat Mar 14 1992 14:566
    I have just tried to create an account (BL122D) using the "normal"
    Digital Europe lastname.firstname naming convention. It worked fine.
    
    Can you post an example of the log file where the problem happens?
    
    Tony
232.3ok on latest baselevelIOSG::TYLDESLEYMon Mar 16 1992 09:5119
    Regina,
    
    Hi. I have created a mumble.foo type user on the ~very latest~
    baselevel here, and then went to MGT MUA E and edited the PRVAPP 
    field. It all seemed to work as expected, and the script
    CM_SM_SWITCH_PRVAPP changed the value in the PRVAPP field as 
    required (although the "you will be notified" message was a little
    quirky, since the change was immediate!) and it set #SM_APP_CHANGE to 2
    and the create$fail flag to 3.
    
    I suspect that you may be seeing a bug that Simon has fixed in the 
    latest baselevel; I think he had some to do around the editing of this
    field, but he can confirm this. If it is not fixed when you get a later 
    baselevel, then we will have to look at the conditions of the script
    dispatch (SUBMIT_SCRIPT ( SCRIPT = "OA$LIB:CM_SM_SWITCH_PRVAPP.SCP",    
    P1 =       etc..)
    
    Cheers
    DaveT
232.4It still does not work under BL123ALEMAN::REGINACarrie's in the carrot landMon Mar 30 1992 11:0271
    I upgraded to  BL123A, created a brand new account BROWN.JAMES,
    tried to put A in OA$PRVAPP, and it still does not want to do it.
    
    The only trace I found was a A1SUB.LOG. Diskquota is enabled 
    and enough! But then, I get the same A1sub.log with another account
    that works. 
    
    Hereafter the A1SUB.log, the A1TRACE and the A1$SCRIPT output.
    
    Thanks for any hint. Regina 


BROWN
USER1:
       Owner         Username           UIC       Account  Privs Pri Directory

james brown          BROWN          [2000,12]     JC9 EIS  Normal  4 USER1:[BROWN]
%DCL-I-SUPERSEDE, previous value of SYS$COMMAND has been superseded
%SYSMAN-I-NODERR, error returned from node BEST1
-SYSTEM-F-NODISKQUOTA, no disk quota entry for this UIC
%SEARCH-I-NOMATCHES, no strings matched
%DCL-E-OPENOUT, error opening USER1:[BROWN.ALLIN1]NEWDB.TMP; as output
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%DCL-W-UNDFIL, file has not been opened by DCL - check logical name
%DELETE-W-SEARCHFAIL, error searching for USER1:[BROWN.ALLIN1]NEWDB.TMP;0
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%UAF-I-MDFYMSG, user record(s) updated
    
Queue Display:
==============
    
Server queue OA$SCRIPT_ENGLISH, on BEST1::, mounted form DEFAULT
    /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC 
    /LIBRARY=ENGLISH /OWNER=[SYSTEM] /PROCESSOR=OA$SCRIPT_SYMBIONT 
    /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR /SCHEDULE=(NOSIZE)

  Jobname         Username     Entry  Blocks  Status
  -------         --------     -----  ------  ------

  CM_SM_SWITCH_PRVAPP
                  ALLIN1         980      21  Retained on error
    %NONAME-E-NOMSG, Message number 00000002
    Submitted 30-MAR-1992 09:19 /FORM=DEFAULT /PARAM=("BOWERS.HILARY","3") 
    /PRIORITY=100
    File: _BEST1$DUA1:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;2 
        /SETUP=("MANAGER",)

  CM_SM_SWITCH_PRVAPP
                  ALLIN1         988      21  Retained on error
    %NONAME-E-NOMSG, Message number 00000002
    Submitted 30-MAR-1992 09:46 /FORM=DEFAULT /PARAM=("BROWN.JAMES","0") 
    /PRIORITY=100
    File: _BEST1$DUA1:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;2 
        /SETUP=("MANAGER",)

  CM_SM_SWITCH_PRVAPP
                  ALLIN1         999      21  Retained on error
    %NONAME-E-NOMSG, Message number 00000002
    Submitted 30-MAR-1992 10:07 /FORM=DEFAULT /PARAM=("BROWN.JAMES","0") 
    /PRIORITY=100
    File: _BEST1$DUA1:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;2 
        /SETUP=("MANAGER",)


TRACE Output:
=============

Removed to save space in notesfile. Contact Note author or Graham (IOSG::) Pye
for full text.

232.7KERNEL::SMITHERSJLiving on the culinary edge....Tue Mar 31 1992 09:576
    This looks like the same problem as 322.* 
    
    Try out the command procedure detailed in one of the replies
    and I believe it should work.
    
    julia
232.8Does not work on BL122D eitherLEMAN::REGINACarrie's in the carrot landTue Mar 31 1992 11:068
    I do not have a general problem with the script processor,
    no co-exsystems, the right image installed, no cluster,
    no customs. It just does not work for NAME.FIRST kind of
    accounts. Can s.o. confirm that this works on their system,
    please? I just tried on another (BL122D) system and *it
    does not work either*. /rhr
    
    
232.9Also fails on my BL123A UTRTSC::SCHOLLAERTHalf Dutch - Half BelgiumTue Mar 31 1992 12:0216
    re.7
    
    > This looks like the same problem as 322.* 
    
    Its not. When this problem occurs, the entry will be
    "starting" forever. 
    
    re.8
    
    > accounts. Can s.o. confirm that this works on their system,
    
    I can reproduce the "BROWN.JAMES" problem on my system (BL123A 
    with fix of note 322).
    
    BROWN.JAMES used in SM MDQ RQU (also runs the script processor)
    works fine.
232.10FixedUTRTSC::SCHOLLAERTHalf Dutch - Half BelgiumTue Mar 31 1992 13:3022
    Found it. Username is used for temp file specs in
    OA$LIB:CM_SM_SWITCH_PRVAPP.SCP. VMS does not like the dot.

    OA$LIB:CM_SM_SWITCH_PRVAPP.SCP contains:

        GET #CM_A1_USER = OA$SMB_PARAMETER_1 \-
         GET #SM_FAILURE_LOG_NAME = #SM_WARNING_LOG_NAME = -
            #SM_SUCCESS_LOG_NAME  = 'OA$SWITCH_PRVAPP_' #CM_A1_USER '.LOG' \-
         GET #CM_ERROR_NAME = "OA$SWITCH_PRVAPP_ERR_" #CM_A1_USER ".LOG" \-
         GET #CM_SWITCH = 1


    Possible fix:

        GET #CM_A1_USER = OA$SMB_PARAMETER_1 \-
        parse_user #cm_a1_user \-
         GET #SM_FAILURE_LOG_NAME = #SM_WARNING_LOG_NAME = -
            #SM_SUCCESS_LOG_NAME  = 'OA$SWITCH_PRVAPP_' $parse_user_name '.LOG'-
         GET #CM_ERROR_NAME = "OA$SWITCH_PRVAPP_ERR_" $parse_user_name  ".LOG" -
         GET #CM_SWITCH = 1
                                                                         
232.16Another workaroundCESARE::EIJSAll in 1 PieceFri Apr 03 1992 12:0019
    
    Re .10)
    
    The PARSE_USER will only supply 9 characters to $PARSE_USER_NAME, which
    might be too short. Another workaround is:
    
            GET #CM_A1_USER = OA$SMB_PARAMETER_1 \-
             MAKE_FILE_NAME #CM_TMP,#CM_A1_USER,".LOG" \-
             GET #CM_TMP = FILE$.NAME:18[#CM_TMP] \-
             GET #SM_FAILURE_LOG_NAME = #SM_WARNING_LOG_NAME = -
                #SM_SUCCESS_LOG_NAME  = 'OA$SWITCH_PRVAPP_' #CM_TMP '.LOG' \-
             GET #CM_ERROR_NAME = "OA$SWITCH_PRVAPP_ERR_" #CM_TMP ".LOG" \-
             GET #CM_SWITCH = 1
    
    The ':18' is there to prevent the filenames to be longer than 39 char.
    
    Ciao,
    
    	Simon
232.17Solution Now in STARSXLII::FDONOHUEFri May 08 1992 18:587
    
    This is now available in STARS.  Please bare with us, there is
    alot of information on V3.0 now available, but also alot of
    information that still requires review etc.  
    
    Faith Donohue
      
232.19failure failsUTRTSC::SCHOLLAERTAJAX beats Feyenoord again and againWed Dec 02 1992 20:5436
    Hello,
    
    Customer reported that after applying the fix for this problem as described
    in STARS (Simon's code), job still retains on error with the same
    error number.
    
    This was caused by the fact that there are two more lines of code
    which use the username to construct a file spec. These lines
    are ONLY executed when the script fails to send a mail message
    to the MANAGER.
    Copy of the boilerplates to OA$LOG fail.
    
    These are the lines I modified to fix the whole script.
    
        GET #CM_A1_USER = OA$SMB_PARAMETER_1 \-                           
        MAKE_FILE_NAME #CM_TMP,#CM_A1_USER,".LOG" \-                     
        GET #CM_PARSED_A1_USER = FILE$.NAME:18[#CM_TMP] \-
        GET #SM_FAILURE_LOG_NAME = #SM_WARNING_LOG_NAME = -              
            #SM_SUCCESS_LOG_NAME  = 'OA$SWITCH_PRVAPP_' #CM_PARSED_A1_USER  '.LOG' \- 
        GET #CM_ERROR_NAME = "OA$SWITCH_PRVAPP_ERR_" #CM_PARSED_A1_USER  ".LOG" \-   
            GET #CM_SWITCH = 1                                               

	      GET #CM_TMP = "OA$LOG:" FILE$.NAME[#TEMPLATE1] "_" -
	        #CM_PARSED_A1_USER FILE$.TYPE[#TEMPLATE1]
	      COPY/FILE #TEMPLATE1 #CM_TMP
	    .END_IF
	    .IF FILE$.STATUS[#TEMPLATE2] EQ 1
	     .THEN
	      GET #CM_TMP = "OA$LOG:" FILE$.NAME[#TEMPLATE2] "_" -
	        #CM_PARSED_A1_USER FILE$.TYPE[#TEMPLATE2]
	      COPY/FILE #TEMPLATE2 #CM_TMP
    
    Regards,
    
    Jan