From: brent@uwovax.uwo.ca (Brent Sterner)
Subject: Re: %BACKUP-E-NOMSG >>> Answer summary.
Organization: University of Western Ont, London
Date: Tue, 15 Sep 1992 14:29:06 GMT

In article <1992Sep14.152218.1@uwovax.uwo.ca>, brent@uwovax.uwo.ca (Brent Sterner) writes:
>    OK, I've been doing other work for too long.  I have a user who
>    complained that backup produced the following diagnostics:
> 
>      %BACKUP-E-NOMSG, Message number 00A38012
> 
> 	and
> 
>      %BACKUP-W-NOMSG, Message number 00A38410

	I received a bunch of email indicating the reason (thanks again
	to you all).  The following summarizes some things others might 
	find interesting as well.  The order is the order I found them
	in my mailbox this morning...

From: "Ian Evans @ Space Telescope Science Institute" <EVANS@fos.stsci.edu>
Subject: Re: %BACKUP-E-NOMSG, Message number 00A38012 ???
To: BRENT@uwo.ca

$ set message sys$message:sysmgtmsg
$ exit %x00A38012
%BACKUP-E-OPENOUT, error opening !AS as output
$ exit %x00A38410
%BACKUP-W-ACCONFLICT, !AS is open for write by another user

	[This is the answer supplied by all other respondees.]


From: "Ken Fairfield; [415] 926-2924 SLAC" <FAIRFIELD@SCS.SLAC.STANFORD.EDU>
Subject: Re: %BACKUP-E-NOMSG, Message number 00A38012 ???
To: brent@uwovax.uwo.ca

Get hold of a copy of TRYMSG.COM: it goes through a SET MESSAGE/F$MESSAGE
loop for all the message files in SYS$MESSAGE.  The first copy of TRYMSG
that I saw came from Douglas A. Gordon at DEC.  I've enhanced the original
and redistributed it at times, as have others...

	[Dan Wing actually sent it to me.  Copy follows.]

The other thing you might consider would be to add the line:

	$SET MESSAGE SYS$MESSAGE:SYSMGTMSG

at the beginning of the command file that runs your BACKUP job.  Then you'll
get the full context of the messages (that is, the file name in question).

	[Good advice.  Another thought follows...]


From: "A. Mahendra Rajah, System Manager" <MAHENDRA@Meena.CC.URegina.CA>
Subject: Re: %BACKUP-E-NOMSG, Message number 00A38012 ???
To: BRENT@uwo.ca

	[Sent be a subset of the above.]


From: Dan Wing <DWING@UH01.Colorado.EDU>
Subject: Re: %BACKUP-E-NOMSG, Message number 00A38012 ???
To: INFO-VAX@SRI.COM
Cc: BRENT@uwo.ca

	[The common answer was included 1st.  Then this tidbit...]

You can avoid the anoyying "Message number nnnn" messages by lowering the
users' FILLM (in SYSUAF) to something smaller than CHANNELCNT (in SYSGEN).
There's a DSNlink article that recommends FILLM be at least 15 less than
CHANNELCNT.

If this is really a "user", you may want to (or you may not want to!) tune
their username to use BACKUP efficiently per the VMS V5.2 release notes.

	[This is a "user", but an administrative one.  He was actually
	copying files from one dis to another.]


Also see attached .COM file.


$! MESSAGE.COM - get text of a message number
$!
$! P1 = message number (integer)
$!
$! Sample usage:
$!   @TRYMSG %X0000002A
$!
$!  EDIT DATE  EDIT  BY   DESCRIPTION
$!  ---------  ----  ---  ---------------------------------------
$!   2-SEP-92  102   DGW  Handle and display errors caused by 
$!                        "%SYSTEM-F-IVSECIDCTL".
$!  13-AUG-92  101   DGW  Added SET MESSAGE/DELETE (per David P. Murphy,
$!                        <murphy@npri6.npri.com>) to remove effect of SET
$!                        MESSAGEs.
$!  13-AUG-92  100   DGW  Documented, upcased, added 'no message found'.
$!
$!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
$
$
$  IF F$TYPE(P1) .NES. "INTEGER" 
$  THEN
$    WRITE SYS$OUTPUT "P1 must be an INTEGER"
$    GOTO DONE
$  ENDIF
$
$  P1 = F$INTEGER(P1)
$  WRITE SYS$OUTPUT F$FAO("Searching for all messages with value %X!XL",P1)
$  MESSAGE_FOUND = 0
$
$LOOP:
$  FILENAME = F$SEARCH("SYS$MESSAGE:*.EXE;")
$  IF FILENAME .EQS. "" THEN GOTO DONE
$
$  WRITE SYS$OUTPUT F$FAO("!5* Checking !AS", FILENAME)
$  DEFINE/USER_MODE SYS$OUTPUT NLA0:    ! ignore "%SYSTEM-F-IVSECIDCTL" errors
$  DEFINE/USER_MODE SYS$ERROR NLA0:
$  SET noON
$  SET MESSAGE 'FILENAME'
$  IF .NOT. $STATUS THEN WRITE SYS$OUTPUT "(Error using above file: ", F$MESSAGE($STATUS), ")"
$  SET ON
$  TEXT = F$MESSAGE('P1')
$
$  IF F$EXTRACT(0,7,TEXT) .EQS. "%NONAME" THEN GOTO LOOP
$  IF F$LOCATE("-NOMSG,",TEXT) .NE. F$LENGTH(TEXT) THEN GOTO LOOP
$  WRITE SYS$OUTPUT TEXT
$  WRITE SYS$OUTPUT ""
$  MESSAGE_FOUND = 1
$  GOTO LOOP
$
$DONE:
$  IF .NOT. MESSAGE_FOUND THEN WRITE SYS$OUTPUT -
     F$FAO("No messages found in SYS$MESSAGE for %X!XL",P1)
$  SET MESSAGE/DELETE
$  EXIT


From: rankin@EQL.Caltech.Edu (Pat Rankin)
Subject:  Re: %BACKUP-E-NOMSG, Message number 00A38012 ???
To: brent@uwo.ca

	[The common answer was included 1st.  Then another
	 bit similar to what Dan Wing stated...]

     Now, the hard part.  Since VMS V5.2, BACKUP tries to process as many
files in parallel as possible.  The user's open-file quota (FILLM) and
the system CHANNELCNT parameter control how many can be accessed at once.
If FILLM is too large, all available channels may be in use when/if BACKUP
gets around to trying to issue a warning or error message.  When that
happens, sysmgtmsg.exe can't be accessed and you end up with the numeric
code instead.  (It may be possible that other quotas relating to queued i/o
could come into play too; I'm not sure.)



From: Jerry Leichter <leichter@lrw.com>
To: BRENT@uwo.ca
Subject: re: %BACKUP-E-NOMSG, Message number 00A38012 ???

	[Jerry provided the same answer as everyone else.]



From: "George Cornelius, 530 Hilton, 4-4809" <cornelius@mayo.edu>
Subject: Re: %BACKUP-E-NOMSG, ...
To: BRENT@uwo.ca

	[George provided the same answer as everyone else.]

--
Brent Sterner                       Manager, Academic Technical Support
Fast:       <BRENT@uwo.ca>          <129.100.2.13>
Telephone:  (519)661-2151 x 6036    Fax:   (519)661-3486
Slow:  Computing & Communications Services, Natural Sciences Building
       The University of Western Ontario, London, Ontario, Canada  N6A 5B7