[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

21.0. "UIC format error?" by EN::HIDER (Paul Hider) Fri Jul 18 1986 14:11

 
  I am getting the following unexpected errors in ZAP.LOG
  It seems to be happy with other UIC's entered in the same format.

[Zap: Idle process deletion utility, Version 3.4]
[Zap: Starting at 18-JUL-1986 10:32:00.58]
[Zap: reading exception file (zap$dir:zap.dat) at 18-JUL-1986 10:32:01.47]
[Zap: Illegal format for uic specification]
[     - Uic must be in numeric format     ]
[51,500]	*		all		30		message
[Zap: Illegal format for uic specification]
[     - Uic must be in numeric format     ]
[51,501]	*		all		30		message
[Zap: Illegal format for uic specification]
[     - Uic must be in numeric format     ]
[51,502]	*		all		30		message
[Zap: Illegal format for uic specification]
[     - Uic must be in numeric format     ]
[51,503]	*		all		30		message
[Zap: Idle sensitivity level is 100]
[Zap: Process traceback is ENABLED]
[Zap: Image debug is ENABLED]
T.RTitleUserPersonal
Name
DateLines
21.1Bug - Fixed v1.5, work around...MRMFG3::K_MACONIThe DoctorMon Jul 21 1986 09:5613
    The error is caused because Zap checks the UIC number to insure
    that it does not exceed [377,377].  This will be fixed in the
    next release of Zap, version 3.5.
    
    From the error messages displayed, it appears that you want to
    specify a 30 minute timeout for all users in the 51 uic group.
    This can be done by using the command:
    
    [51,*]	*	all	30	message
    
    instead of specifying each uic.  Although the routine which reads
    in the uics can not currently handle greater than [377,377], the
    main routines are able to work with wildcards in those ranges.