[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

113.0. "ZAP V5.0 known problems" by ZAPDEV::MACONI (The Doctor is In) Tue May 05 1992 15:46

The following problems have been found in the current release of DEC ZAP for
VMS V5.0.

  o  The ZAP$RUN_STATUS function CLOSE does not work.  The monitor will always
     open the newest history file unless it does not exists or it locked by
     another user.

	-  Workaround:  Rename the .DAT file to a different file name.

	-  Fix:  Problem will be corrected in V5.1

  o  No warning messages are sent to users when their idle time limit is
     suddenly decreased due to a rule change.  This can cause users to be logged
     out with no warning - although they are actually idle.

	-  Workaround:  As documented in reference manual - care should be
		taken when using the FROM and UNTIL time qualifiers.

	-  Fix:  A new configuration parameter, MIN_WARNING, will be included
		in V5.1 that will insure that the user is given a minimum
		warning time.

  o  The monitor can loose processes in certain situations where systems with a
     low MAXPROCESSCNT have a high number of process creations.  This problem
     will result in numerous NOSUCHPRC errors in the log file.  The monitor will
     be unable to kill the process in the process slot.

	-  Workaround:  Restart the monitor if the error count climbs too
		quickly.

	-  Fix:  Problem will be corrected in V5.1

  o  Some files in the ZAP$DIR: directory are incorrectly protected when
     created for the first time.

	-  Workaround:  Set the file protection as desired and then place an
		ACL in the ZAP$DIR: directory file such as:
		(DEFAULT_PROTECTION,S:WRED,O:WRED,G:RE,W)

	-  Fix:  V5.1 will specify a default protection in all procedures that
		will be used if the ACL is not present.

T.R	Title	User	Personal Name	Date	Lines
113.1	V5.1 IFT sites requested - V5.1 wishlist items	ZAPDEV::MACONI	The Doctor is In	`Wed May 13 1992 18:11`	4
	DEC ZAP for VMS V5.1 will be entering IFT soon. IFT sites are requested. Requests should be sent to: ZAPDEV::MACONI Wishlist items should be posted as replies to this note.
113.2	ALL-IN-1 /BROADCAST and warning messages	ZHSS05::FREUND	Wener Freund / SWAS DM BOIS Zuerich	`Sat Jun 13 1992 06:20`	12
	If in ALL-IN-1-IOS broadcast trapping is enabled no warning messages will be displayed (in both %line and noline mode). ALL-IN-1 displays normal REPLYs at the line 24 when broadcast trapping is enabled. It would be just great if this could be fixed in V5.1. Regards Werner
113.3	This is not a bug with ZAP.	ZAPDEV::MACONI	The Doctor is In	`Mon Jun 15 1992 10:47`	21
	It is not considered to be a problem with ZAP that you choose to disable broadcast messages on your terminal or via ALL-IN-ONE. Broadcast messages are not guaranteed to be delivered. This is because broadcast messages can easily be filtered or disabled so that no delivery occurs on the users terminal, such as by the SET BROADCAST command. If you choose to disable message broadcasts, then it is your responsiblity to realize that these messages will not be delivered. Since ALL-IN-ONE is actually trapping the broadcast messages, the BRKTHRU service indicates a successful delivery. However, since ALL-IN-ONE also includes an inactivity timer, there should be no need to ZAP anyone who is running ALL-IN-ONE. Just use the ALL-IN-ONE timer and when the user is exited from ALL-IN-ONE, then ZAP will take over. However, if you would like to filter broadcast messages and use ZAP, you should know that the ZAP monitor broadcasts messages using the USER16 broadcast group. Keith Maconi
113.4	Wildcard '*' may not be used more than once	ZAPDEV::MACONI	The Doctor is In	`Mon Oct 19 1992 17:28`	23
	The following bug has been reported: On string values that allow the wildcard character '', use of the wildcard value '' more than once does not work. Actual problem: ZAP incorrectly parses strings which contain more than one '' character and truncates all text after the first '' character. That means that the following is how ZAP would translate the following strings: * -> * xyz -> xyz xyz -> xyz xyz -> xyz xyz* -> xyz* xy... -> x* x -> * Resolution: This problem will be corrected in version 5.1. Until then, limit the wildcard character '*' to once per string only.