That would be true for any pmdf channel that is processed by the master
program.

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



> -----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 12:11 PM
> To: info-pmdf@process.com
> Subject: 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.
> > $
> jobs to end>
> > $@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

>
>
>