Conference iosg::all-in-1_v30

    
    Hi Trevor,
    
    When the PRVAPP field is changed the Script CM_SM_SWITCH_PRVAPP.SCP is
    submitted to the Script symbiont. As long as the procedure runs the
    actual new value of the PRVAPP is not valid for the user (e.g. PRVAPP
    changes from P -> A. The user would be a Maintainer, but as long as the
    procedure runs s/he cannot be one).
    
    The CREATE$FAIL field is used by SM to indicate whether or not the
    creation of an account succeeded. The values used are 0,1 and 2. CM
    uses this field for 'the same' purpose, but uses value 3 (This won't
    conflict with SM activities). As long as the procedure runs in the Script 
    symbiont, the value will be set to 3 and the initialization of CM
    checks this value to see if it can continue. When the procedure
    finishes, it is reset.
    
    3 Doesn't mean failure, 3 means 'temporary being edited, no access
    allowed'. Did the procedure in the Script symbiont ever finish?
    
    Ciao,
    
    	Simon
    
    
     

    Hi Simon,
    
    	Thanks for your help, this looks like why the create$fail is always 
    wrong.
    
Server queue OA$SCRIPT_BRITISH, idle, on node::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC /LIBRARY=BRITISH /OWNER=[SYSTEM] /PROCESSOR=OA$SCRIPT_SYMBIONT 
  /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR /SCHEDULE=(NOSIZE)

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
    952  CM_SM_SWITCH_PRVAPP
                         ALLIN1           21  Retained on error
       %JBC-E-SYMDEL, unexpected symbiont process termination
       -SYSTEM-S-NOTALLPRIV, not all requested privileges authorized
         Submitted 26-JUN-1992 09:26 /FORM=DEFAULT /PARAM=("TALBOT","3","TALBOT") /PRIORITY=100
         File: _$255$DUA71:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;1 /SETUP=("MANAGER",)
         Completed 26-JUN-1992 09:26 on queue OA$SCRIPT_BRITISH

     74  CM_SM_SWITCH_PRVAPP
                         ALLIN1           21  Retained on error
       %JBC-E-SYMDEL, unexpected symbiont process termination
       -SYSTEM-S-NOTALLPRIV, not all requested privileges authorized
         Submitted 11-JUL-1992 19:54 /FORM=DEFAULT /PARAM=("CROOKS","0") /PRIORITY=100
         File: _$255$DUA71:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;1 /SETUP=("MANAGER",)
         Completed 11-JUL-1992 19:54 on queue OA$SCRIPT_BRITISH

     80  CM_SM_SWITCH_PRVAPP
                         ALLIN1           21  Retained on error
       %JBC-E-SYMDEL, unexpected symbiont process termination
       -SYSTEM-S-NOTALLPRIV, not all requested privileges authorized
         Submitted 11-JUL-1992 20:02 /FORM=DEFAULT /PARAM=("CROOKS","3") /PRIORITY=100
         File: _$255$DUA71:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;1 /SETUP=("MANAGER",)
         Completed 14-JUL-1992 11:44 on queue OA$SCRIPT_BRITISH

    951  CM_SM_SWITCH_PRVAPP
                         ALLIN1           21  Retained on error
       %NONAME-E-NOMSG, Message number 00000002
         Submitted 29-JUL-1992 09:52 /FORM=DEFAULT /PARAM=("TALBOT") /PRIORITY=100
         File: _$255$DUA71:[ALLIN1.LIB_SHARE]CM_SM_SWITCH_PRVAPP.SCP;1 /SETUP=("MANAGER",)
         Completed 29-JUL-1992 09:54 on queue OA$SCRIPT_BRITISH
    
    
    The entry 951 is the latest casualty, any ideas on why this happens?
    
    -TRev

    
    Hi Trevor,
    
    Can you recall how you edited your account. Via option 'E', via direct
    calls to the forms PROFIL or SM$PROFILE (like <FORM xxx), or any other
    way?
    It's strange that job 951 doesn't have a second parameter, which should
    be the current value of CREATE$FAIL before submitting the procedure.
    
    The first check in the procedure is if at least the 2 parameters are
    supplied. If not, a mail message is created and sent to the
    MANAGER/you. If errors occur during creation or sending of the message
    the status of the 'batch job' will be set to 2 which sets the status to
    'Retained on error'. This seems to have happened to you.
    
    Ciao,
    
    	Simon

    Hi Simon,
    
    	The edit was done via the menu option E.
    
    Before I read your last reply, I read notes 988,888,883,594 and 322 all
    relating to script symbiont problems. I have followed the advice in
    these and re-built the queue etc.
    
    Now when the E is done the job gets submitted to the queue, terminates
    without being retained and sends no message to the manager account. The
    user account is still non operational with the create$fail = 3 .
    
    I then do a <write change to set create$fail to be blank
    this lets the user account work.
    Next I Edit again(via menu) from the manager account the user profile and 
    change PRVAPP field , again job is sent to queue, no errors, no retains no
    mail and account gets locked with create$fail = 3.
    
    -Trev

    Hi,
    
    I changed the WRITE CHANGE statement to store create$fail = "0"
     
    and the second param appeared and the account when changed via the
    script now works o.k. looks like supplying a blank was the knock on
    problem after the queue packed up.
    
    Thanks for your help
    
    -Trev