PMAS PMDF channel log files overflowing file version number - VMS

This is a discussion on PMAS PMDF channel log files overflowing file version number - VMS ; Gentle folk, How are people handling the problem of PMAS log file version numbers exceeding the VMS maximum version number? We're a relatively small site, and currently receive about 20,000 spam messages/day. Recently I've started getting messages that the MASTER ...

+ Reply to Thread
Results 1 to 11 of 11

Thread: PMAS PMDF channel log files overflowing file version number

  1. PMAS PMDF channel log files overflowing file version number


    Gentle folk,

    How are people handling the problem of PMAS log file version
    numbers exceeding the VMS maximum version number?

    We're a relatively small site, and currently receive
    about 20,000 spam messages/day. Recently I've started
    getting messages that the MASTER log files for the spam
    filtering channels are getting close to the maximum.
    See the attached messages below.

    Usually it takes several attempts to get rid of them all so the
    log file version number can be reset to 1, since the rate of incoming
    messages usually keeps several recent, high-version-number log files
    locked for a while -- which presumably is why PMDF can't eliminate them
    on its own.

    Presumably one could redefine the PMDF log file directory logical
    frequently so that individual directories of log files don't overflow
    and can be cleaned up later, but this seems like a real kludge.

    We're running

    LNS61$ pmdf ver
    %PMDF-I-VERSION, PMDF version is PMDF V6.3
    Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007
    and

    X-PMAS-Software: PreciseMail V2.4-3 [071029b] (lns61.lns.cornell.edu)


    Thanks for whatever help you can provide.

    Selden
    ======
    Selden E. Ball, Jr.

    Cornell University Voice: +1-607-255-0688
    Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    LT105 R. R. Wilson Laboratory http://www.lepp.cornell.edu/~seb/
    Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB
    ==========================

    Content-type: multipart/digest; boundary="Boundary_(ID_dLL9zfBcT+538emskm7Q5g)"

    --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    Return-path:
    Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    (PMDF V6.3-x11 #31231) id <01MMGE8FI5XS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    13 Oct 2007 00:32:08 -0400 (EDT)
    Date: Sat, 13 Oct 2007 00:32:07 -0400 (EDT)
    From: SYSTEM@LNS61.LNS.CORNELL.EDU
    Subject: CONVERSION log file needs attention
    To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    Message-id: <01MMGE8FI7TE8XCQK8@LNS61.LNS.CORNELL.EDU>
    X-VMS-To: IN%"POSTMASTER"
    X-VMS-Cc: SYSTEM
    MIME-version: 1.0
    Content-type: TEXT/PLAIN; CHARSET=us-ascii

    The log file version for the CONVERSION channel has hit or exceeded
    your preset warning level (25000). You should delete
    all versions of the log file for this channel now to avoid problems
    later. The log file for this channel is:

    PMDF_ROOT:[LOG]CONVERSION_MASTER.LOG

    --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)

    Return-path:
    Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    (PMDF V6.3-x11 #31231) id <01MMGE8H40DS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    13 Oct 2007 00:32:10 -0400 (EDT)
    Date: Sat, 13 Oct 2007 00:32:10 -0400 (EDT)
    From: SYSTEM@LNS61.LNS.CORNELL.EDU
    Subject: PMAS log file needs attention
    To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    Message-id: <01MMGE8H429E8XCQK8@LNS61.LNS.CORNELL.EDU>
    X-VMS-To: IN%"POSTMASTER"
    X-VMS-Cc: SYSTEM
    MIME-version: 1.0
    Content-type: TEXT/PLAIN; CHARSET=us-ascii

    The log file version for the PMAS channel has hit or exceeded
    your preset warning level (25000). You should delete
    all versions of the log file for this channel now to avoid problems
    later. The log file for this channel is:

    PMDF_ROOT:[LOG]PMAS_MASTER.LOG

    --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)

    Return-path:
    Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    (PMDF V6.3-x11 #31231) id <01MMORXKTO688WYRMT@LNS61.LNS.CORNELL.EDU>; Fri,
    19 Oct 2007 00:31:21 -0400 (EDT)
    Date: Fri, 19 Oct 2007 00:31:21 -0400 (EDT)
    From: SYSTEM@LNS61.LNS.CORNELL.EDU
    Subject: PMAS log file needs attention
    To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    Message-id: <01MMORXKTP428WYRMT@LNS61.LNS.CORNELL.EDU>
    X-VMS-To: IN%"POSTMASTER"
    X-VMS-Cc: SYSTEM
    MIME-version: 1.0
    Content-type: TEXT/PLAIN; CHARSET=us-ascii

    The log file version for the PMAS channel has hit or exceeded
    your preset warning level (25000). You should delete
    all versions of the log file for this channel now to avoid problems
    later. The log file for this channel is:

    STM$DISK:[PMDF_LOG]PMAS_MASTER.LOG

    --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)--

  2. RE: PMAS PMDF channel log files overflowing file version number

    Hi Selden,

    I have a perl procedure which will take any wildcard
    file spec and clean it up (you end up with the n versions
    you want to keep starting at 1 (oldest) going up to n
    (newest). Well, at least highest to lowest version numbers,
    assuming you haven't done something like renumbering in
    a weird order.

    Hein VanDenHeuvel had a very nice perl one-liner to do
    this as well, but I can't find it in my private gmail
    archives, try dropping him a line:

    heinvandenheuvel@gmail.com

    I'll be glad to send you my perl script if it would
    help you out. It has been invaluable for cleaning up
    the cr%p that ends up, for instance, in SSH* log files,
    which run up to 32767 really fast.

    Oh, this was also a topic on Decuserve/Eisner as well
    when SSH locked up there with a 32767 in a SSH log file,
    IIRC.

    Sigh. We could use 64-bit version numbers. Well, maybe
    3 versions is enough.

    I guess a purge/collapse command line switch would have
    helped.

    Carl Friedberg
    friedberg@esb.com
    www.esb.com
    The Elias Book of Baseball Records
    2007 Edition

    > -----Original Message-----
    > From: Selden E Ball Jr [mailto:SEB@LNS62.LNS.CORNELL.EDU] On Behalf
    > Of Selden E Ball Jr
    > Sent: Tuesday, October 30, 2007 10:31 AM
    > To: info-pmdf@process.com
    > Subject: PMAS PMDF channel log files overflowing file version number
    >
    >
    > Gentle folk,
    >
    > How are people handling the problem of PMAS log file version
    > numbers exceeding the VMS maximum version number?
    >
    > We're a relatively small site, and currently receive
    > about 20,000 spam messages/day. Recently I've started
    > getting messages that the MASTER log files for the spam
    > filtering channels are getting close to the maximum.
    > See the attached messages below.
    >
    > Usually it takes several attempts to get rid of them all so the
    > log file version number can be reset to 1, since the rate of incoming
    > messages usually keeps several recent, high-version-number log files
    > locked for a while -- which presumably is why PMDF can't eliminate
    > them
    > on its own.
    >
    > Presumably one could redefine the PMDF log file directory logical
    > frequently so that individual directories of log files don't overflow
    > and can be cleaned up later, but this seems like a real kludge.
    >
    > We're running
    >
    > LNS61$ pmdf ver
    > %PMDF-I-VERSION, PMDF version is PMDF V6.3
    > Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    > PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31
    > 2007
    > and
    >
    > X-PMAS-Software: PreciseMail V2.4-3 [071029b] (lns61.lns.cornell.edu)
    >
    >
    > Thanks for whatever help you can provide.
    >
    > Selden
    > ======
    > Selden E. Ball, Jr.
    >
    > Cornell University Voice: +1-607-255-0688
    > Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    > LT105 R. R. Wilson Laboratory
    > http://www.lepp.cornell.edu/~seb/
    > Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    > Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB =
    > 44284::SEB
    > ==========================
    >
    > Content-type: multipart/digest;
    > boundary="Boundary_(ID_dLL9zfBcT+538emskm7Q5g)"
    >
    > --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    > Return-path:
    > Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    > (PMDF V6.3-x11 #31231) id
    > <01MMGE8FI5XS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    > 13 Oct 2007 00:32:08 -0400 (EDT)
    > Date: Sat, 13 Oct 2007 00:32:07 -0400 (EDT)
    > From: SYSTEM@LNS61.LNS.CORNELL.EDU
    > Subject: CONVERSION log file needs attention
    > To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    > Message-id: <01MMGE8FI7TE8XCQK8@LNS61.LNS.CORNELL.EDU>
    > X-VMS-To: IN%"POSTMASTER"
    > X-VMS-Cc: SYSTEM
    > MIME-version: 1.0
    > Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >
    > The log file version for the CONVERSION channel has hit or exceeded
    > your preset warning level (25000). You should delete
    > all versions of the log file for this channel now to avoid problems
    > later. The log file for this channel is:
    >
    > PMDF_ROOT:[LOG]CONVERSION_MASTER.LOG
    >
    > --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >
    > Return-path:
    > Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    > (PMDF V6.3-x11 #31231) id
    > <01MMGE8H40DS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    > 13 Oct 2007 00:32:10 -0400 (EDT)
    > Date: Sat, 13 Oct 2007 00:32:10 -0400 (EDT)
    > From: SYSTEM@LNS61.LNS.CORNELL.EDU
    > Subject: PMAS log file needs attention
    > To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    > Message-id: <01MMGE8H429E8XCQK8@LNS61.LNS.CORNELL.EDU>
    > X-VMS-To: IN%"POSTMASTER"
    > X-VMS-Cc: SYSTEM
    > MIME-version: 1.0
    > Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >
    > The log file version for the PMAS channel has hit or exceeded
    > your preset warning level (25000). You should delete
    > all versions of the log file for this channel now to avoid problems
    > later. The log file for this channel is:
    >
    > PMDF_ROOT:[LOG]PMAS_MASTER.LOG
    >
    > --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >
    > Return-path:
    > Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    > (PMDF V6.3-x11 #31231) id
    > <01MMORXKTO688WYRMT@LNS61.LNS.CORNELL.EDU>; Fri,
    > 19 Oct 2007 00:31:21 -0400 (EDT)
    > Date: Fri, 19 Oct 2007 00:31:21 -0400 (EDT)
    > From: SYSTEM@LNS61.LNS.CORNELL.EDU
    > Subject: PMAS log file needs attention
    > To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    > Message-id: <01MMORXKTP428WYRMT@LNS61.LNS.CORNELL.EDU>
    > X-VMS-To: IN%"POSTMASTER"
    > X-VMS-Cc: SYSTEM
    > MIME-version: 1.0
    > Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >
    > The log file version for the PMAS channel has hit or exceeded
    > your preset warning level (25000). You should delete
    > all versions of the log file for this channel now to avoid problems
    > later. The log file for this channel is:
    >
    > STM$DISK:[PMDF_LOG]PMAS_MASTER.LOG
    >
    > --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)--


  3. RE: PMAS PMDF channel log files overflowing file version number

    Tom,

    Thanks!

    I also have the problem with the CONVERSION channel.
    Am I correct that the commands

    $ define/system/exec PMDF_HOLD conversion
    [...]
    $ deassign/system/exec PMDF_HOLD
    $ pmdf submit conversion

    would stop and restart it?

    s.

    > The utility in pmdf that resets the logfile version numbers is called by
    > the nightly return job. You may want to set up a maintenance procedure
    > of your own that will stop the PMAS channel, then run the procedure to
    > reset the file versions.


    > include something like this in the procedure....


    > $define/system/exec PMDF_HOLD pmas !to stop any additional pmas channel
    > processes from starting.
    > $
    > $@PMDF_COM:PMDF_CHECK_LOGS.COM
    > $ deassign/system/exec PMDF_HOLD
    > $ pmdf submit pmas


    > If your file versions are growing at such a rate that doing this once a
    > day is not sufficient, then you could set up the maintenance procedure
    > to run periodically as often as necessary.


    > this is just a suggestion.



    > Regards,
    > Tom Welker
    > Process Software - Senior Support Specialist
    > 800-722-7770 Support line: 800-394-8700
    > welker@process.com




  4. RE: PMAS PMDF channel log files overflowing file version number

    Someone else mentioned this, but I just wanted to restate
    the obvious: you can rename an open file. That's what
    started me writing my procedure. I would purge down
    the sshd logfiles, and then have a picket fence of version
    numbers. Being compulsive, I wanted to make sure the lowest
    numbered version ended up as ;1, and the versions would
    increase monotonically. It just seems like the right
    thing to do. And it's the only way I've found to assure
    that I really lower the highest version number to something
    really small.

    Again, anyone who wants a copy of my ugly perl script is
    welcome to it. Just ask.

    Carl Friedberg
    www.comets.com

    > -----Original Message-----
    > From: Tom Welker [mailto:welker@process.com]
    > Sent: Tuesday, October 30, 2007 12:06 PM
    > To: info-pmdf@process.com
    > Subject: RE: PMAS PMDF channel log files overflowing file version
    > number
    >
    > The utility in pmdf that resets the logfile version numbers is called
    > by
    > the nightly return job. You may want to set up a maintenance
    > procedure
    > of your own that will stop the PMAS channel, then run the procedure
    > to
    > reset the file versions.
    >
    > include something like this in the procedure....
    >
    > $define/system/exec PMDF_HOLD pmas !to stop any additional pmas
    > channel
    > processes from starting.
    > $
    > $@PMDF_COM:PMDF_CHECK_LOGS.COM
    > $ deassign/system/exec PMDF_HOLD
    > $ pmdf submit pmas
    >
    > If your file versions are growing at such a rate that doing this once
    > a
    > day is not sufficient, then you could set up the maintenance
    > procedure
    > to run periodically as often as necessary.
    >
    > this is just a suggestion.
    >
    >
    > Regards,
    > Tom Welker
    > Process Software - Senior Support Specialist
    > 800-722-7770 Support line: 800-394-8700
    > welker@process.com
    >
    >


  5. Re: PMAS PMDF channel log files overflowing file version number

    In article <01MN4Q3I2KB68Y4WU8@LNS62.LNS.CORNELL.EDU>, Selden E Ball Jr writes:
    >
    >Gentle folk,
    >
    >How are people handling the problem of PMAS log file version
    >numbers exceeding the VMS maximum version number?
    >
    >We're a relatively small site, and currently receive
    >about 20,000 spam messages/day. Recently I've started
    >getting messages that the MASTER log files for the spam
    >filtering channels are getting close to the maximum.
    >See the attached messages below.
    >

    Have you got master_debug defined on those channels (or on the defaults line) ?
    If not then I'd have a look at the contents of those log files since I'd
    suspect it indicates some error is occurring.
    I am not seeing gigantic numbers of

    CONVERSION_MASTER.LOG
    or
    PMAS_MASTER.LOG


    files.


    >Usually it takes several attempts to get rid of them all so the
    >log file version number can be reset to 1, since the rate of incoming
    >messages usually keeps several recent, high-version-number log files
    >locked for a while -- which presumably is why PMDF can't eliminate them
    >on its own.
    >

    You should be able to rename the locked files.

    I got a program called prune.com from somewhere which I run regularly
    for things like the OSU webserver net$server.log files


    -------------

    $ if p1.eqs."" then inquire/nopunc p1 "_File: "
    $ if p1.eqs."" then exit
    $ say :== write sys$output
    $ if f$search(p1).eqs."" then goto nofile
    $ filename = f$element(0,".",p1)
    $ if filename.eqs."." then goto huh
    $ filetype = f$element(1,".",p1)
    $ if filetype.eqs."." then goto huh
    $ directory 'p1'
    $ purge 'p1'
    $ rename 'p1';* .prune;
    $ rename 'filename'.prune;* .'filetype';
    $ directory 'p1'
    $ exit
    $huh:
    $ say "Huh?"
    $ sh sym p1
    $ sh sym filename
    $ sh sym filetype
    $ exit
    $nofile:
    $ say "%PRUNE-E-NOEXISTS, file doesn't exist \''p1'\"
    $ exit

    -----------------------------------------------------

    Hope that helps

    David Webb
    Security team leader
    CCSS
    Middlesex University


    >Presumably one could redefine the PMDF log file directory logical
    >frequently so that individual directories of log files don't overflow
    >and can be cleaned up later, but this seems like a real kludge.
    >
    >We're running
    >
    >LNS61$ pmdf ver
    >%PMDF-I-VERSION, PMDF version is PMDF V6.3
    > Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    > PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007
    >and
    >
    >X-PMAS-Software: PreciseMail V2.4-3 [071029b] (lns61.lns.cornell.edu)
    >
    >
    >Thanks for whatever help you can provide.
    >
    >Selden
    >======
    >Selden E. Ball, Jr.
    >
    >Cornell University Voice: +1-607-255-0688
    >Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    >LT105 R. R. Wilson Laboratory http://www.lepp.cornell.edu/~seb/
    >Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    >Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB
    >==========================
    >
    >Content-type: multipart/digest; boundary="Boundary_(ID_dLL9zfBcT+538emskm7Q5g)"
    >
    >--Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >Return-path:
    >Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    > (PMDF V6.3-x11 #31231) id <01MMGE8FI5XS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    > 13 Oct 2007 00:32:08 -0400 (EDT)
    >Date: Sat, 13 Oct 2007 00:32:07 -0400 (EDT)
    >From: SYSTEM@LNS61.LNS.CORNELL.EDU
    >Subject: CONVERSION log file needs attention
    >To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    >Message-id: <01MMGE8FI7TE8XCQK8@LNS61.LNS.CORNELL.EDU>
    >X-VMS-To: IN%"POSTMASTER"
    >X-VMS-Cc: SYSTEM
    >MIME-version: 1.0
    >Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >
    >The log file version for the CONVERSION channel has hit or exceeded
    >your preset warning level (25000). You should delete
    >all versions of the log file for this channel now to avoid problems
    >later. The log file for this channel is:
    >
    > PMDF_ROOT:[LOG]CONVERSION_MASTER.LOG
    >
    >--Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >
    >Return-path:
    >Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    > (PMDF V6.3-x11 #31231) id <01MMGE8H40DS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    > 13 Oct 2007 00:32:10 -0400 (EDT)
    >Date: Sat, 13 Oct 2007 00:32:10 -0400 (EDT)
    >From: SYSTEM@LNS61.LNS.CORNELL.EDU
    >Subject: PMAS log file needs attention
    >To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    >Message-id: <01MMGE8H429E8XCQK8@LNS61.LNS.CORNELL.EDU>
    >X-VMS-To: IN%"POSTMASTER"
    >X-VMS-Cc: SYSTEM
    >MIME-version: 1.0
    >Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >
    >The log file version for the PMAS channel has hit or exceeded
    >your preset warning level (25000). You should delete
    >all versions of the log file for this channel now to avoid problems
    >later. The log file for this channel is:
    >
    > PMDF_ROOT:[LOG]PMAS_MASTER.LOG
    >
    >--Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >
    >Return-path:
    >Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    > (PMDF V6.3-x11 #31231) id <01MMORXKTO688WYRMT@LNS61.LNS.CORNELL.EDU>; Fri,
    > 19 Oct 2007 00:31:21 -0400 (EDT)
    >Date: Fri, 19 Oct 2007 00:31:21 -0400 (EDT)
    >From: SYSTEM@LNS61.LNS.CORNELL.EDU
    >Subject: PMAS log file needs attention
    >To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    >Message-id: <01MMORXKTP428WYRMT@LNS61.LNS.CORNELL.EDU>
    >X-VMS-To: IN%"POSTMASTER"
    >X-VMS-Cc: SYSTEM
    >MIME-version: 1.0
    >Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >
    >The log file version for the PMAS channel has hit or exceeded
    >your preset warning level (25000). You should delete
    >all versions of the log file for this channel now to avoid problems
    >later. The log file for this channel is:
    >
    > STM$DISK:[PMDF_LOG]PMAS_MASTER.LOG
    >
    >--Boundary_(ID_dLL9zfBcT+538emskm7Q5g)--


  6. Re: PMAS PMDF channel log files overflowing file version number

    david20@alpha2.mdx.ac.uk wrote:
    >
    > I got a program called prune.com from somewhere which I run regularly
    > for things like the OSU webserver net$server.log files
    >

    Ken bows or ducks, as appropriate. :-) Glad you find it useful!

    -ken
    >
    > -------------
    >
    > $ if p1.eqs."" then inquire/nopunc p1 "_File: "
    > $ if p1.eqs."" then exit
    > $ say :== write sys$output
    > $ if f$search(p1).eqs."" then goto nofile
    > $ filename = f$element(0,".",p1)
    > $ if filename.eqs."." then goto huh
    > $ filetype = f$element(1,".",p1)
    > $ if filetype.eqs."." then goto huh
    > $ directory 'p1'
    > $ purge 'p1'
    > $ rename 'p1';* .prune;
    > $ rename 'filename'.prune;* .'filetype';
    > $ directory 'p1'
    > $ exit
    > $huh:
    > $ say "Huh?"
    > $ sh sym p1
    > $ sh sym filename
    > $ sh sym filetype
    > $ exit
    > $nofile:
    > $ say "%PRUNE-E-NOEXISTS, file doesn't exist \''p1'\"
    > $ exit
    >
    > -----------------------------------------------------
    >
    > Hope that helps
    >
    > David Webb
    > Security team leader
    > CCSS
    > Middlesex University
    >
    >
    >
    >> Presumably one could redefine the PMDF log file directory logical
    >> frequently so that individual directories of log files don't overflow
    >> and can be cleaned up later, but this seems like a real kludge.
    >>
    >> We're running
    >>
    >> LNS61$ pmdf ver
    >> %PMDF-I-VERSION, PMDF version is PMDF V6.3
    >> Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    >> PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007
    >> and
    >>
    >> X-PMAS-Software: PreciseMail V2.4-3 [071029b] (lns61.lns.cornell.edu)
    >>
    >>
    >> Thanks for whatever help you can provide.
    >>
    >> Selden
    >> ======
    >> Selden E. Ball, Jr.
    >>
    >> Cornell University Voice: +1-607-255-0688
    >> Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    >> LT105 R. R. Wilson Laboratory http://www.lepp.cornell.edu/~seb/
    >> Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    >> Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB
    >> ==========================
    >>
    >> Content-type: multipart/digest; boundary="Boundary_(ID_dLL9zfBcT+538emskm7Q5g)"
    >>
    >> --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >> Return-path:
    >> Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    >> (PMDF V6.3-x11 #31231) id <01MMGE8FI5XS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    >> 13 Oct 2007 00:32:08 -0400 (EDT)
    >> Date: Sat, 13 Oct 2007 00:32:07 -0400 (EDT)
    >> From: SYSTEM@LNS61.LNS.CORNELL.EDU
    >> Subject: CONVERSION log file needs attention
    >> To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    >> Message-id: <01MMGE8FI7TE8XCQK8@LNS61.LNS.CORNELL.EDU>
    >> X-VMS-To: IN%"POSTMASTER"
    >> X-VMS-Cc: SYSTEM
    >> MIME-version: 1.0
    >> Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >>
    >> The log file version for the CONVERSION channel has hit or exceeded
    >> your preset warning level (25000). You should delete
    >> all versions of the log file for this channel now to avoid problems
    >> later. The log file for this channel is:
    >>
    >> PMDF_ROOT:[LOG]CONVERSION_MASTER.LOG
    >>
    >> --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >>
    >> Return-path:
    >> Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    >> (PMDF V6.3-x11 #31231) id <01MMGE8H40DS8XCQK8@LNS61.LNS.CORNELL.EDU>; Sat,
    >> 13 Oct 2007 00:32:10 -0400 (EDT)
    >> Date: Sat, 13 Oct 2007 00:32:10 -0400 (EDT)
    >> From: SYSTEM@LNS61.LNS.CORNELL.EDU
    >> Subject: PMAS log file needs attention
    >> To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    >> Message-id: <01MMGE8H429E8XCQK8@LNS61.LNS.CORNELL.EDU>
    >> X-VMS-To: IN%"POSTMASTER"
    >> X-VMS-Cc: SYSTEM
    >> MIME-version: 1.0
    >> Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >>
    >> The log file version for the PMAS channel has hit or exceeded
    >> your preset warning level (25000). You should delete
    >> all versions of the log file for this channel now to avoid problems
    >> later. The log file for this channel is:
    >>
    >> PMDF_ROOT:[LOG]PMAS_MASTER.LOG
    >>
    >> --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)
    >>
    >> Return-path:
    >> Received: from LNS61.LNS.CORNELL.EDU by LNS61.LNS.CORNELL.EDU
    >> (PMDF V6.3-x11 #31231) id <01MMORXKTO688WYRMT@LNS61.LNS.CORNELL.EDU>; Fri,
    >> 19 Oct 2007 00:31:21 -0400 (EDT)
    >> Date: Fri, 19 Oct 2007 00:31:21 -0400 (EDT)
    >> From: SYSTEM@LNS61.LNS.CORNELL.EDU
    >> Subject: PMAS log file needs attention
    >> To: POSTMASTER@LNS61.LNS.CORNELL.EDU, seb@LNS61.LNS.CORNELL.EDU
    >> Message-id: <01MMORXKTP428WYRMT@LNS61.LNS.CORNELL.EDU>
    >> X-VMS-To: IN%"POSTMASTER"
    >> X-VMS-Cc: SYSTEM
    >> MIME-version: 1.0
    >> Content-type: TEXT/PLAIN; CHARSET=us-ascii
    >>
    >> The log file version for the PMAS channel has hit or exceeded
    >> your preset warning level (25000). You should delete
    >> all versions of the log file for this channel now to avoid problems
    >> later. The log file for this channel is:
    >>
    >> STM$DISK:[PMDF_LOG]PMAS_MASTER.LOG
    >>
    >> --Boundary_(ID_dLL9zfBcT+538emskm7Q5g)--
    >>


    --
    - Ken
    ================================================== ===============
    Ken Connelly Associate Director, Security and Systems
    ITS Network Services University of Northern Iowa
    email: Ken.Connelly@uni.edu p: (319) 273-5850 f: (319) 273-7373


  7. Re: PMAS PMDF channel log files overflowing file version number


    It is also possible to clear out all these log files in a fully
    automated way, without stopping and restarting the queue via PMDF_HOLD.
    The key things are

    1. Delete the log files starting at the lowest version number and work
    upward.

    2. If the delete fails, RENAME the open file to something else.

    We have a system checker that calls CHECK-LOG-VERSIONS.COM, which looks
    for any log files with a version approaching 32767. It calls
    KILL-ALL-VERSIONS.COM to delete them if found. Both files can be
    downloaded via anonymous FTP from ftp.eurokom.ie

    ---------------------------------------------------------
    Tom Wade | EMail: tee dot wade at eurokom dot ie
    EuroKom | Tel: +353 (1) 296-9696
    A2, Nutgrove Office Park | Fax: +353 (1) 296-9697
    Rathfarnham | Disclaimer: This is not a disclaimer
    Dublin 14 | Tip: "Friends don't let friends do Unix !"
    Ireland


  8. Stability of Process' pmdf symbiont?


    Gentle folk,

    I'm considering switching from using VMS batch queues to
    using Process' own VMS symbiont for scheduling PMDF channel
    jobs. Supposedly it has a lot less overhead, not creating
    irrelevant log files as batch jobs do, for example.

    What are people's current experiences using Process' symbiont?

    We're running
    LNS61$ pmdf ver
    %PMDF-I-VERSION, PMDF version is PMDF V6.3
    Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007

    Thanks for whatever experiences you can share.

    Selden
    ======
    Selden E. Ball, Jr.

    Cornell University Voice: +1-607-255-0688
    Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    LT105 R. R. Wilson Laboratory http://www.lepp.cornell.edu/~seb/
    Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB

  9. Re: Stability of Process' pmdf symbiont?

    I've been running that way for a LONG time, Selden. No problems at all
    with it.

    - ken

    Selden E Ball Jr wrote:
    >
    > Gentle folk,
    >
    > I'm considering switching from using VMS batch queues to
    > using Process' own VMS symbiont for scheduling PMDF channel
    > jobs. Supposedly it has a lot less overhead, not creating
    > irrelevant log files as batch jobs do, for example.
    >
    > What are people's current experiences using Process' symbiont?
    >
    > We're running LNS61$ pmdf ver
    > %PMDF-I-VERSION, PMDF version is PMDF V6.3
    > Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    > PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007
    >
    > Thanks for whatever experiences you can share.
    >
    > Selden
    > ======
    > Selden E. Ball, Jr.
    >
    > Cornell University Voice: +1-607-255-0688
    > Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    > LT105 R. R. Wilson Laboratory
    > http://www.lepp.cornell.edu/~seb/
    > Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    > Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB


    --
    - Ken
    ================================================== ===============
    Ken Connelly Associate Director, Security and Systems
    ITS Network Services University of Northern Iowa
    email: Ken.Connelly@uni.edu p: (319) 273-5850 f: (319) 273-7373


  10. Re: Stability of Process' pmdf symbiont?

    In article <01MN7JGF313C8Y4WU3@LNS62.LNS.CORNELL.EDU>, Selden E Ball Jr writes:
    >
    >Gentle folk,
    >
    >I'm considering switching from using VMS batch queues to
    >using Process' own VMS symbiont for scheduling PMDF channel
    >jobs. Supposedly it has a lot less overhead, not creating
    >irrelevant log files as batch jobs do, for example.
    >
    >What are people's current experiences using Process' symbiont?


    We have used the process symbiont since we first started using PMDF in about
    1995 - never had any problems.

    David Webb
    Security team leader
    CCSS
    Middlesex University

    >
    >We're running
    >LNS61$ pmdf ver
    >%PMDF-I-VERSION, PMDF version is PMDF V6.3
    > Digital Personal WorkStation running OpenVMS Alpha V7.3-2
    > PMDF_SHARE_LIBRARY version V6.3-x11; linked 19:47:06, May 31 2007
    >
    >Thanks for whatever experiences you can share.
    >
    >Selden
    >======
    >Selden E. Ball, Jr.
    >
    >Cornell University Voice: +1-607-255-0688
    >Laboratory for Elementary-Particle Physics FAX: +1-607-255-8062
    >LT105 R. R. Wilson Laboratory http://www.lepp.cornell.edu/~seb/
    >Dryden Road Internet: SEB@LEPP.CORNELL.EDU
    >Ithaca, NY, USA 14853-8001 HEPnet/SPAN: LNS62::SEB = 44284::SEB


  11. Re: Stability of Process' pmdf symbiont?

    Hi Selden,

    >I'm considering switching from using VMS batch queues to
    >using Process' own VMS symbiont for scheduling PMDF channel
    >jobs. Supposedly it has a lot less overhead, not creating
    >irrelevant log files as batch jobs do, for example.
    >
    >What are people's current experiences using Process' symbiont?


    It works very, very well. Much more efficient than batch jobs.
    The only time I've ever had a problem was at daylght savings time change,
    when a VMS bug would cause the symbiont to fail. The last time I saw this
    was OpenVMS Alpha V7.3 but it doesn't seem to be a problem in 7.3-2 or 8.3.

    Regards,

    Jeremy Begg

+ Reply to Thread