Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!samsung!psuvax1!psuvm!SPCVXA!TERRY From: TERRY@SPCVXA (Terry Kennedy, Operations Mgr) Newsgroups: bit.listserv.pmdf-l Subject: RE: error getting file parameter Message-ID: Date: 3 Feb 90 04:52:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 26 Approved: NETNEWS@PSUVM Gateway Errors-to: postmast@YMIR.BITNET X-Organization: St. Peter's College, US X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: IN%"ipmdf@ymir",IN%"lschultz@wooster" X-VMS-Cc: TERRY Comments: Warning -- RSCS tag indicates an origin of POSTMAST@YMIR X-To: ipmdf@YMIR, lschultz@WOOSTER Lee Schultz writes: > The PMDF software worked fine for about an 1-1/2 hours. Then it seemed to > get stuck, repeating the following error message (in L_MASTER.LOG in > pmdf_root:[log]) over and over and over.....: > %PMDF-W-V5DETECT, MAIL CNCT block not found -- assuming VMS V5 > %PMDF-F-GETFILERR, Error getting file parameter off command line > -CLI-W-ABSENT, entity or value absent from command string The first error is actually normal. In PMDF 3.0, PMDF looked around in MAIL to determine whether the system was running VMS V4 or V5. PMDF V3.1 now has seperate images for VMS V4 and V5, so this message is a historical one. I be- lieve Ned has stated that it will be going away in a future release (probably once V4 support is dropped). We had the second error every now and again when we were on VMS V5.2. It was actually non-fatal (at least for us). I think Ned said it was a problem in the VMS side of things. I haven't seen it since we went to V5.3. In any event, queued files will be retried the next time the periodic deliver job runs. You could change the interval to a shorter period if you like. I think the default is four hours, but you can trim that way down. We had it at 15 minutes while we were sufferinf from the problem. Terry Kennedy St. Peter's College