[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference share::zap

Title:	Zap Technical Conference
Notice:	ZAP Version 5.3 is available. See note 1.1
Moderator:	ZAPDEV::MACONI

Created:	Mon Feb 24 1986
Last Modified:	Mon May 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	170
Total number of notes:	492

156.0. "EXIT ($FORCEX) RETURNS NONAME-W-NOMSG" by KERNEL::BARKERH () Thu Dec 01 1994 14:33

    Hi,

    I have a customer using ZAP 5.0 who has been experiencing the following
    problem:

     On testing out ZAP with the EXIT ($FORCEX) action and when
     the image which the process is in exits, the following message is
     returned from ZAP:

     %NONAME-W-NOMSG, Message number 00000000

     Despite this message, ZAP seems to have worked, stopping the image the 
     process was executing. Note the customer can always replicate this 
     message from ZAP.

    Is anyone aware of a fix for this version, or whether the problem is
    fixed in later versions of ZAP.

    Thanks,

    Henry

T.R Title User Personal
Name Date Lines

156.1 Have not seen it before ZAPDEV::MACONI The Doctor is In Fri Dec 02 1994 13:18 13

T.R	Title	User	Personal Name	Date	Lines
156.1	Have not seen it before	ZAPDEV::MACONI	The Doctor is In	`Fri Dec 02 1994 13:18`	13
	Hello, I do not recall this specific message before. ZAP uses a customized error message file and has no error code 0 error messages. I assume that this error is actually returned by one of the system service calls when the EXIT procedure is run. You mention that this error is reproduceable. When the error occurs, does ZAP increment the error count shown in the ZAP$MONITOR system logical name? Is it one specific image or user that causes this error or does it occur all the time? Keith Maconi

Hello,

	I do not recall this specific message before.  ZAP uses a customized
error message file and has no error code 0 error messages.  I assume that this
error is actually returned by one of the system service calls when the EXIT
procedure is run.

	You mention that this error is reproduceable.  When the error occurs,
does ZAP increment the error count shown in the ZAP$MONITOR system logical
name?  Is it one specific image or user that causes this error or does it
occur all the time?

					Keith Maconi