I suggest, not specifically for LISTSERV, the following form of distributing program systems (for initial installation) as well as updates. 1. One and ONLY ONE file shall be sent, LOGICALLY, *BUT* it may be broken up into numerically sequenced pieces for transmission convenience. 2. A file enveloping format be used that allows multiple files sent as one file (inside the one file mandated by 1. above). Sorry, but this rules out NETDATA format until IBM corrects that deficiency. DISK and CARD formats will work. 3. The one file shall contain two to four files: A. Instructions for the human to read. B. ONE FILE containing inside all the files needed to install. C. (Optional) a procedure (EXEC) to do the installation. D. (Optional) a program to break up the file in B. 4. The file described in 3B shall use the same file format as the main file, or the unformatting program (3D) shall be included along side the collection (3B). Thus, there will be TWO layers for the actual files that are to be installed. Using formats such as CARD DUMP will make sure that not too much overhead is introduced into the distributions. By having it organized logically as one single file, it can be handled very easily by many commands that expect just one file. All the levels can be easily archived and retrieved as needed. Here is a graphic example of this organization as it might be used for LISTSERV: ( symbol \ is a reverse slash in case it comes out otherwise ) / READTHIS MEMO / various / / files / SYSTEM PACKAGE --=< to LISTSERV V1$5N ---=< \ be \ ( INSTALL EXEC ) \ installed \ \ ( CARD MODULE ) Note that if the outer packaging format is DISK DUMP, CARD MODULE should be included if the inner packaging is CARD DUMP (suggested). /phil