 HISTORY of MISH:       The MASH program:   B 	The  MISH  program  was  created from a program called MASH.  TheI     MASH  program  was  used  to convert and create a file which could be I     transmitted  on a HASP reader stream.  These files had to be 80 bytes I     bytes  in length and could contain binary data.  The MASH program has      the following features:    	o  Uses HASP data compression. * 	o  Allows conversion of any type of file.. 	o  File attributes stored in a header record.6 	o  Format acceptable for HASP and 2780 punch streams. 	o  Written in RSX MACRO-11.5 	o  Runs on RSX-11M/M+ and VMS in compatibility mode.          The MISH Program:   B 	There was a need to transfer files on the HASP reader streams andI     also  to  be able to transfer these files using the RSXNET and VAXNET I     programs.  It  seemed  logical then to convert the output of the MASH I     program  into printable ASCII to accomplish this need.  At this time, I     the  MASH  program was converted into MISH.  The MISH program has the      following features:    	o  Uses HASP data compression. * 	o  Allows conversion of any type of file.1 	o  File attributes stored in two header records. 7 	o  Format acceptable for HASP and 2780 reader streams. 8 	o  Format acceptable to the RSXNET and VAXNET programs.8 	o  Format acceptable to the VMS Code Management System.: 	o  Base character for the ASCII conversion is '%' ('$'+1)3 	   to allow easy file inclusion in VMS batch jobs. ; 	o  Conversion is 2 bytes into 3 printable ASCII bytes with = 	   a maximum record size of 78 bytes (reader stream max=80).  	o  Written in RSX MACRO-11.5 	o  Runs on RSX-11M/M+ and VMS in compatibility mode.          VMS MISH Program:   B 	All  seemed  well  with the MISH and MASH programs until VMS V4.0I     was released.  Now the Application Migration Executive (AME) used for I     running compatibility programs on VMS became a layered product called I     VAX-11/RSX.  Existing  sites  could  obtain the first release of this I     product free of charge if they were upgrading from a previous version I     of VMS, otherwise there was a fee.  There was also a need to run MISH =     on the Micro-VAX which doesn't include compatiblity mode.   B 	Thus,  MISH needed to be rewritten to run on any VMS system.  TheI     language  chosen was the new FORTRAN available on VMS V4 since it now I     contains  extensions which allow easy access to the RMS structures to I     obtain  the file attributes.  Also, the source modules created can be B     easily included in the VAXNET program also written in FORTRAN.     B 	Since  the MISH and MASH programs had much common code, I decidedI     to  include the features of both programs in the VMS MISH.  To select I     MISH  mode,  which is the default, the /ASCII qualifer is used and to I     select  MASH  mode, the /BINARY qualifier is used.  I also discovered I     during  the  rewrite that the compression routine could be optimized. I     This optimization resulted in the following savings when used with an #     executable file during testing:        OLD:, 	Program  Blocks In  Blocks Out  Records Out, 	-------  ---------  ----------  -----------' 	MISH        30          42         283 ' 	MASH        30          29         174        NEW:5 	Mode     Blocks In  Blocks Out  Records Out  Savings 5 	----     ---------  ----------  -----------  ------- 2 	ASCII       30          40         264         192 	BINARY      30          27         168          6  J      Since most file transfers are done at slow speeds (300 or 1200 baud),;      the above savings will be significate on larger files.           XMODEM Qualifier:  B 	It's  obvious from the above statistics that conversion of binaryI      data  to  ASCII is expensive.  Since the VAXNET program supports the I      XMODEM  protocol, I decided to allow the option of generating a file I      suitable  for transfer using XMODEM in binary mode.  When the XMODEM I      qualifier  is specified, BINARY mode is selected and the record size I      is  changed to 128 (size of an XMODEM data block).  Since the XMODEM I      protocol  has  better  error  checking  than the VAXNET protocol and ;      allows binary transfers, I prefer to use this program.           Design Notes:  B 	o  The  header  record  is not compressed which forces one or twoB 	   header  records  for  MASH  and MISH respectively.  The header; 	   record should be compressed just like any other record.   B 	o  The UIC stored in the VMS header record is only a word insteadB 	   of a longword to be compatible with the PDP-11 programs.  ThisB 	   UIC is used for identification of where the file came from, it, 	   is not used when decompressing the file.  B 	o  The  maximum size of the file name stored in the header recordB 	   is limited to 31 characters.  This limitation is imposed to beB 	   compatible  with  the  PDP-11  programs.   This causes no realB 	   problem  except  that the file name in the header record can'tB 	   be used when the file is decompressed. In this case, an outputB 	   file name must be specified. During compression, anything overB 	   the  limit  is  overwritten  with the file attributes which is+ 	   much more important than the file name.   2 	o  Access Control Lists (ACL's) are not retained.