From:	MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX" 30-JAN-1993 02:58:18.49
To:	info-vax@sri.com
CC:	
Subj:	Re: V5.5-2 BACKUP-E-NOMSG

Dr. Kenneth H. Fairfield writes:
>In article <1993Jan27.153028.307@vulcan.resmel.bhp.com.au>, matthews@vulcan.resmel.bhp.com.au writes:
>> Since upgrading to v5.5-2 I occasionally get the following error from backup
>> when it has completed a image backup disk to disk:
>> 
>> %BACKUP-E-NOMSG, Message number 10A3800A
>> 
>> Can someone explain to me the meaning/purpose of this error message?
>
>BACKUP error messages are in SYS$MESSAGE:SYSMGTMSG.EXE.  You can do:
>
>	$ SET MESSAGE SYS$MESSAGE:SYSMGTMSG
>	$ WRITE SYS$OUTPUT F$MESSAGE(%X10A3800A)
>	%BACKUP-E-OPENIN, error opening !AS as input
>
>I put the above SET MESSAGE command in every comand file I use to do
>a BACKUP.  If you had done so, the "!AS" would've been filled in with
>the name of the file BACKUP had trouble with.
>
>    I hope you get the "meaning/purpose" now...
>
>		-Ken



    yes, that works, but it doesn't address the REAL problem,
    which is why BACKUP isn't displaying the proper error message
    text. You shouldn't have to do a SET MESSAGE before running
    BACKUP.

    The real problem is one of quotas. BACKUP is running out of
    some quota and is therefore unable to map SYSMGTMSG.EXE
    and display the error message text. The usual culprit is the
    process' FILLM quota. Digital recommends a FILLM quota for the
    process running BACKUP of the SYSGEN quota CHANNELCNT - 15, but
    not higher, otherwise BACKUP may run out of channels.  In that
    case it is unable to open SYSMGTMSG to display proper error text.

    Another quota that could affect BACKUP is the process' BYTLM quota.
    The process quotas for BACKUP are discussed in
    SYS$EXAMPLES:USING_BACKUP.TXT, .PS, and .DECW$BOOK.


    colin sewell
    h.a.simons ltd.
    vancouver, bc
    "simons/g=colin/s=sewell"@mhs.attmail.com