It's the execcom file that does not exist. The mcaapexec is the correct file. I do not know where the execcom reference came from. It's not in the alias file nor a directory or file on the server. It was not created for this list. So why does it reference it at all? This is how I set up the list: PUT MCAAPEXEC-L.LIST PW=xxxxxxx * * MCAAPEXEC Executive Committee * * Review= Private * Subscription= By Owner,confirm * Send= Private * Notify= Yes * Reply-to= List * Files= No * Validate= No * Editor = [log in to unmask] * Notebook= Yes,/projects/list/mcaapexec,Monthly,Private * Confidential= Yes * Owner= [log in to unmask] (Bonnie Erskine) * Owner= [log in to unmask] (Eugenia Marcus MD) * ####Mcaapexec-l LIST mcaapexec-l: "|/usr/local/bin/lsv_amin /projects/list/spool mcaapexec-l" owner-mcaapexec-l: "|/usr/local/bin/lsv_amin /projects/list/spool owner-mcaapexec-l" mcaapexec-l-request: "|/usr/local/bin/lsv_amin /projects/list/spool mcaapexec-l-request" mcaapexec-l-search-request: "|/usr/local/bin/lsv_amin /projects/list/spool mcaapexec-l-search-request" mcaapexec-l-server: "|/usr/local/bin/lsv_amin /projects/list/spool mcaapexec-l-server" Then go to: cd /projects/list and issue the following commands: mkdir mcaapexec chown listserv /projects/list/ mcaapexec chmod u=rwx /projects/list/ mcaapexec ----- Original Message ----- From: <[log in to unmask]> To: <[log in to unmask]> Sent: Tuesday, May 30, 2000 12:28 PM Subject: Re: List being held. > On Tue, 30 May 2000 12:19:35 EDT, "Margaret J. Brandt" <[log in to unmask]> said: > > > >>> Error X'00000011' opening file = > > /projects/list/execcom/mcaapexec-l.log0005 <<< > > What does 'ls -ld /projects/list/execcom' show? And if that exists, it should > be owned by your listserv userid, and be mode 'rwx'. > > Also, check 'ls -l /projects/list/execcom/mcaapexec-l.log*' and see if > any of the logs exist... > > > -- > Valdis Kletnieks > Operating Systems Analyst > Virginia Tech >