Imhub1mdf ver
%PMDF-I-VERSION, PMDF version is PMDF V6.3
AlphaServer DS25 running OpenVMS Alpha V8.3
PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007

with latest version of PMAS


pmdf_logmas_master.log contains error messages like

12-DEC-2007 16:04:10.24: Bad news. Message failed with status A9C80FA, exiting


Hunter suggested that this might be down to channelcnt being too low so I
increased that massively - it is now 3072

But that didn't make any difference.

Others are reporting similar problems eg on an IA64 VMS system

File: PMAS_4_LIST_MASTER.LOG;31065 Row: 1 Col: 1 ( 0%) Dir: Forward
12-DEC-2007 18:20:00.21: Bad news. Message failed with status A9C80FA, exiting
%DCL-W-ACTIMAGE, error activating image PMDF_EXE:MASTER.EXE
-CLI-E-IMGNAME, image file $1$DGA10:[PMDF.][IA64_EXE]MASTER.EXE;
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-EXBYTLM, exceeded byte count quota
%SYSTEM-W-DEVNOTALLOC, device not allocated
%SYSTEM-F-NOLOGNAM, no logical name match

which maybe implicates bytlm but in that case the system account's bytlm was
set to Bytlm: 3000000

I know for the dispatcher SMTP connections, POP and IMAP connections have their
own bytlm limit set in pmdf_tableISPATCHER.CNF but is there any similar
setting for the channels in some other file or is it controlled by the system
account setting ?

Hunter is suggesting this is a PMDF rather than PMAS problem.




David Webb
Security team leader
CCSS
Middlesex University