Development fix 17D-002D contains code which allows LISTSERV to decode incoming files in VMSDUMP format. It makes life easier for VMS users in two respects: 1. You no longer have to remember not to use your SEND/FILE/VMSDUMP alias when sending files to LISTSERV. 2. LISTSERV can now decode VMSDUMP files sent to a list for the benefit of mail-only recipients. All sequential file formats are supported, with the exception of UNDEFINED. The prefix portion of VFC files is discarded. Relative and indexed files are not supported. It does NOT change any of the following: - Indexed files for VMS packages and other RMS-specific files, including VFC, must still be stored on LISTSERV as foreign files: the ability to decode VMSDUMP files did not suddenly add full RMS capabilities to CMS. - While it is now possible to store BACKUP savesets (which SEND/FILE/NETDATA cannot handle due to buffer size limitations) on LISTSERV as native CMS files without loss of data, this is still not the recommended method to make savesets available on LISTSERV, as JNET's RECEIVE command creates a variable format file even when the input file had fixed format on the VM system. A simple CONVERT/FDL step can fix this problem, but end users are not likely to understand FDL files. - Support for the generation of VMSDUMP files (ie 'GET X.COM F=VMSDUMP') is not included. You are welcome to try sending "weird" files to LISTSERV to test out the code, but please use either your own server or SEARN. Eric