Conference cookie::sls

2217.0. "SLS-F_ANSRECERR running RMU backup" by CSC32::V_HEINICKE () Wed Mar 12 1997 10:13

Hi,

I have a customer who is trying  to run RMU backups and recevies the following
error:

%SLS-F-ASNRECERR, failed to assign recording notification mailbox _STC2$MBA1683:

Following is the portion of the log that shows the problem.  I do have the
complete log in my directory should that be needed.

$       SPAWN/NOWAIT/PROCESS=DBSYBK_3374_1 -
                /INPUT=_NL: -
                /OUTPUT=SLS$SYSBAK_LOGS:DBSYSBAK_00023374_1.LOG; -
                @SLS$SYSTEM:SLS$DBSYSBAK_SPAWN.COM "/NODEBUG"
%DCL-S-SPAWNED, process DBSYBK_3374_1 spawned
$!
$ CONTINUE_BACKUP:
$       DEASSIGN ERRMESS
$       IF DO_NODE .NES. "" THEN DEASSIGN MNSCUDB_ROOTA
$       IF DO_NODE .NES. "" THEN DEASSIGN SYS$NODE
$!
$! - Get sub-process PID
$!
$       GETMBX_TIM := 0 0:2:0.0                 ! set up timeout for GETMBX
$       SET NOON                                ! disable ON processing
$PID_LOOP:
$       GETMBX RECMBX_1                 ! read process id
%SYSTEM-W-TIMEOUT, device timeout
$       IF $STATUS THEN GOTO PID_GOTIT          ! see if we got it
$       SHOW PROCESS SYSBAK_3374_1      ! if not, see if it exited
%SYSTEM-W-NONEXPR, nonexistent process
$       IF $STATUS THEN GOTO PID_LOOP           ! still there, try again
$       STATUS_1 = $STATUS              ! exited, save status
$       STATE_1 = "FAILED"              ! Change the current state
$       SET ON                                  ! enable ON processing
$       FINISHED = RUNNING                      ! do termination processing
$       FINISHED_RETURN := PID_DONE
$       GOTO FINISHED
$FINISHED:   
$       CLOSE RECCHN_1
$       DEASSIGN RECMBX_1
$       I = PID_1
$       PID_1 :=
$!      Check for an innermode failure from the sysbak subprocess.
$       status_string = ""
$       logical_name_status = "SLS$$INNERMODE_ERROR_" + I
$       status_string = -
            f$trnlnm(logical_name_status,"LNM$SLS$VALUES","","EXECUTIVE")
$       if status_string .nes. ""
$       endif
$       SET NOON
$FINISHED_WAIT_LOOP:
$       MSG = F$ENVIRONMENT("MESSAGE")          ! Save settings of SET MESSAGE
$       SET MESSAGE/NOFACIL/NOTEXT/NOSEV/NOIDENT! Disable message display
$       X = F$GETJPI (I, "PRCNAM")              ! ignore %SYSTEM-W-NONEXPR, ...
$       TMPSTS = $STATUS
$       SET MESSAGE/FACILITY/SEVERITY/IDENTIFICATION/TEXT                      *
$       IF .NOT. TMPSTS THEN GOTO FINISHED_WAIT_DONE
$FINISHED_WAIT_DONE:
$       SET ON
$!
$! - Display sub-process output, if any
$!
$       X := SLS$SYSBAK_LOGS:SYSBAK_00023374_1.LOG;
$       X :=
$       IF X .NES. "" THEN GOTO LOG_PRINT
$       X := SLS$SYSBAK_LOGS:DBSYSBAK_00023374_1.LOG;
$       X := SLS$ROOT:[SYSBAK.SYSBAK_LOGS]DBSYSBAK_00023374_1.LOG;1
$       IF X .EQS. "" THEN GOTO NO_LOG_PRINT
$LOG_PRINT:
$       SET NOON
$       WRITE SYS$OUTPUT -
"******* Beginning subprocess output for FILES_1 *******"
******* Beginning subprocess output for FILES_1 *******
$       TYPE SLS$ROOT:[SYSBAK.SYSBAK_LOGS]DBSYSBAK_00023374_1.LOG;1
$!
$!*  COPYRIGHT (c) 1993 BY DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETT*
$!
$!
$!      S L S $ D B S Y S B A K _ S P A W N . C O M
$!
$! This procedure issues the RUN command on the DBSYSBAK.EXE image after
$! settting appropriate process parameters.
$!
$ set verify
$ set process/dump
$ run/NODEBUG sls$system:sls$dbsysbak.exe
%SLS-F-ASNRECERR, failed to assign recording notification mailbox _STC2$MBA1454:
-SYSTEM-W-NOSUCHDEV, no such device available
$       WRITE SYS$OUTPUT -
"******* End subprocess output for FILES_1 *******"
******* End subprocess output for FILES_1 *******
$       DELETE SLS$ROOT:[SYSBAK.SYSBAK_LOGS]DBSYSBAK_00023374_1.LOG;1
%DELETE-W-FILNOTDEL, error deleting SLS$ROOT:[SYSBAK.SYSBAK_LOGS]DBSYSBAK_00023*
-RMS-E-FLK, file currently locked by another user

There is a similar note in  1544.

Any help would be greatly appreciated.

Thanks,

Victoria

    Hi Victoria,
    
    Since talking to you, I've looked more closely at the problem...
    
      - The SYSBAK.COM modification recommended by Bart in note #1544
        has not been included in any official version of SYSBAK.COM
        (don't know why - except that it was never reported using IPMT).
    
      - The change looks safe and is clearly the intended functionality
        which is to check if the DBSYSBAK_pid_n subproc exists (not the
        (SYSBAK_pid_n subproc).  The risk might be that another problem
        is preventing SYSBAK from ever receiving the message, but there
        are checks later on to handle that, so this shouldn't cause
        a hang.
    
    I think your customer should try making the change.  But regardless
    of whether it works or not, please send us an ipmt case as a reminder
    to test and get the change into V2.9.
    
    thanks,
    Marty

    Hi,
    
    I spoke to the customer who was experiencing the %SLS-F-ASNRECERR
    error.  Another specialist on our team had suggested he modify some
    process resources back in January because he wasn't seeing the
    'nonexistant process' error reported in note 1544.  The customer has
    made those recommended changes since working with Victoria.  The
    increased process quotas appear to have solved the problem, or
    at lease the customer thinks it did since he hasn't experienced the 
    problem since the 12th of March.
    
    The SLS account's process quotas where low for their FILLM of 500. 
    Increased BIOLM to 500 and BYTLM to 160000.
    
    
      %X0B169F6C - %SLS-F-ASNRECERR, failed to assign recording
    notification
                   mailbox !AS
    
         FACILITY:     [tbd]
         EXPLANATION:  An error was encountered while assigning a channel
                       to the recording pass mailbox during a system
                       backup or an RMU backup.
         USER ACTION:  See the additional displayed messages for
                       information and the description of $ASSIGN in the
                       "OpenVMS System Services Reference Manual".  Check
                       your process quota and privileges (should have
                       NETMBX and TMPMBX).
         SEVERITY:     FATAL