| The proper method to make images immume from Zap is to place the
following command in the ZAP.DAT file.
[*,*] image_x all * nomessage
Remember that the ZAP.DAT file is read sequentially, so if an
idle time limit is set for a user above this command, the image
will not be immune for that user.
If you have the correct command in your ZAP.DAT file, please check
the version of Zap that you are executing ($ Analyze/image Zap$dir:Zap)
and send me a copy of your ZAP.DAT file (and version level) and
I will check it for you.
Send the data to: MRMFG1::K_MACONI /SUBJECT="ZAP BUG"
The solution to the problem will be posted as a reply to this note.
Keith Maconi
|
| Here is the problem that I found:
The following section was extracted from the sites ZAP.DAT
file. Note that most of the PMS programs have a seperate line
for each program. However, at the end, there is a generic
command for the rest of the programs. It is PMS?.
Unfortunately, the ? operates exactly the same as the % does
in VMS (The ? will be changed to %, along with * support in
version 3.5). This means that only four letter programs which
begin with PMS are excluded. To exclude the rest of the
programs, you would need to specify PMS?????? (Assuming that
none of the programs are greater than nine characters in
length).
Keith Maconi
! Image name - Any valid image name up to 39 characters. Legal wild-
! cards are * for any image, and ? for any character in
! the given position.
!
! Applications
[*,*] pmsuirqp all * nomessage
[*,*] pmsuprqp all * nomessage
[*,*] pmsxirqp all * nomessage
[*,*] pmsxprqp all * nomessage
[*,*] pms? all * nomessage
!
[Zap: Idle process deletion utility, Version 3.3]
[Zap: Starting at 8-SEP-1986 11:17:28.35]
[Zap: reading exception file (zap$dir:zap.dat) at 8-SEP-1986 11:17:29.90]
[Zap: Idle sensitivity level is 5]
[Zap: Process traceback is ENABLED]
[Zap: Image debug is DISABLED]
[Zap: reading warning message file (zap$dir:zap.msg) at 8-SEP-1986 11:17:30.93]
[Zap: Warning message is 1 characters long]
[Zap: TXA4:MANERO logged out at 12:08:31.54 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSMMENU.EXE;15]
[Zap: TXH6:ROUTHIER logged out at 12:11:31.78 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSMMENU.EXE;15]
[Zap: TXE0:BUSHWAY logged out at 12:41:46.50 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSULAB.EXE;8]
[Zap: TXA3: MANERO logged out at 13:43:32.17 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSULAB.EXE;8]
[Zap: TXH5: BROWNE logged out at 14:16:36.89 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSMMENU.EXE;15]
[Zap: TXA0: MANERO logged out at 14:36:32.52 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSMMENU.EXE;15]
[Zap: TTC7: CRAVEN logged out at 15:02:47.02 after 30 min idle time]
[ image = $1$DUA13:[MCSPROD.PMS.EXE]PMSMMENU.EXE;15]
[Zap: Exiting at 9-SEP-1986 08:58:32.62]
|
|
After Zap was upgraded to version 3.5, the problems reported
went away. It seems that there is a bug in all versions of
Zap from 3.0 to 3.4, which causes the program to become
confused when attempting to match image names. When the old
wildcard "?" was used, it was unable to make image names match.
Version 3.5 of Zap corrects this problem and also changes the
wildcard format to match that of VMS. When the upgrade is done,
the Zap.dat file must be replaced due to new formats of some
of the commands.
|