I think I have an accurate recollection of an LSoft technical person saying once that this should not be done with a digest that is still in the process of being compiled and has not yet gone out to distribution, as this throws something or other out of synch. I don’t know if there is some kind of work-around to avoid this.

Charles Clausen
ppml-info.org

On Sun, 10 Jun 2018 00:47:30 -0700, Randy Ryan <[log in to unmask]> wrote:

>I haven't done this since 16d so can't guarantee the exact steps, but you can
>test first before committing.
>
>Generally, you would issue a HOLD list command, then GET the digest.  Edit and
>then PUT the DIGEST with the NOLock command, then FREE the list.
>
>You can test this first by just seeing if you can Get the digest
>
>GET <listname> DIGEST NOLock pw=password
>
>If that works, then
>HOLD <listname> pw=
>GET <listname> DIGEST pw=
>PUT <listname> DIGEST NOLOCK pw=
>

############################

To unsubscribe from the LSTOWN-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1