Subversion Repositories Kolibri OS

Rev

Blame | Last modification | View Log | Download | RSS feed

  1. -----------------------------------------------------------------------
  2. [Installation notes for VM/CMS port of UNZIP 5.32 and ZIP 2.2]
  3. Additional notes from Ian E. Gorman (4/98):
  4.  
  5. I have not fully tested ZIP and UNZIP in VM (for example, I have not
  6. tried all the options), so ZIP 2.2 for VM and UNZIP 5.32 for VM
  7. should be regarded as beta versions.  Try them out before you decide
  8. that you can depend on them.
  9.  
  10. Most of the work for the VM port has been done by others, but I have
  11. made some changes and compiled on a more recent version of VM/CMS.  It
  12. is possible that I have introduced new problems or undone some of the
  13. solutions found by previous authors.
  14.  
  15.  
  16. Installation
  17. ============
  18.  
  19. The executables are stored in CMS "PACK" format instead of being
  20. stored in ZIP archives.  This format takes a little longer to
  21. download, but installation is slightly simpler.
  22.  
  23.  
  24. Installing UNZIP
  25. ----------------
  26.  
  27. The UNZIP executable is supplied as the binary file UNZIP.MOD, in the
  28. CMS "PACK" format.
  29.  
  30. You must get the UNZIP.MOD file on to your system as a binary file in
  31. fixed recording mode, block size 1024.
  32.  
  33. If you are using FTP in CMS, you can get the file in the correct
  34. format with the LOCSITE and BINARY commands.  Assuming that the UNZIP
  35. executable is stored on the remote site as unz532vm.mod, you could
  36. issue the following commands
  37.  
  38.     FTP where.ever.com
  39.     <enter user id and password and other stuff>
  40.     BINARY
  41.     LOCSITE FIX 1024
  42.     GET unz532vm.mod
  43.     QUIT
  44.  
  45. If you are using a 3270 terminal session to upload from a PC, you can
  46. upload the file in the correct format with the SEND command:
  47.  
  48.     SEND unz532vm.mod A: unz532vm mod a1 (RECFM F LRECL 1024
  49.  
  50. If your 3270 emulator does not have the SEND command, but is a GUI
  51. application, it may allow you to upload from the menu bar.  If so,
  52. set your options to binary, VM/CMS, fixed record length, and a length
  53. of 1024 before you upload.
  54.  
  55. When you get the PACKed file on your CMS minidisk, you convert it to
  56. an executable module by using the COPY command with the UNPACK option:
  57.  
  58.     COPY unz532vm mod a unzip module a1 (UNPACK OLDDATE REPLACE
  59.  
  60. You can omit the OLDDATE and REPLACE options if you want to.
  61.  
  62.  
  63. Installing ZIP
  64. --------------
  65.  
  66. The ZIP executable is supplied as the binary file ZIP.MOD, in the CMS
  67. "PACK" format.
  68.  
  69. You must get the ZIP.MOD file on to your system as a binary file in
  70. fixed recording mode, block size 1024.  Assuming that the file is
  71. stored as zip22vm.mod, you can get the file the same way you got the
  72. UNZIP.MOD file:
  73.  
  74.     Using FTP:
  75.  
  76.         FTP where.ever.com
  77.         <enter user id and password and other stuff>
  78.         BINARY
  79.         LOCSITE FIX 1024
  80.         GET zip22vm.mod
  81.         QUIT
  82.  
  83.     Using 3270 file transfer:
  84.  
  85.         SEND unz532vm.mod A: unz532vm mod a1 (RECFM F LRECL 1024
  86.  
  87. When you get the PACKed file on your CMS minidisk, you convert it to
  88. an executable module by using the COPY command with the UNPACK option:
  89.  
  90.     COPY zip22vm mod a zip module a1 (UNPACK OLDDATE REPLACE
  91.  
  92.  
  93. Installing Documentation
  94. ------------------------
  95.  
  96. Once you have UNZIP running, you can use it to extract documentation
  97. from ZIP archives.
  98.  
  99. You can transfer the ZIP archives to VMV/CMS as a binary file with any
  100. record length.  A record length of 1 will work fine:
  101.  
  102.     via FTP:
  103.  
  104.         FTP where.ever.com
  105.         <enter user id and password and other stuff>
  106.         BINARY
  107.         LOCSITE FIX 1
  108.         GET zip22vm.zip zipdoc.zip
  109.         GET unz532vm.zip unzipdoc.zip
  110.         QUIT
  111.  
  112.     via 3270 session:
  113.  
  114.         SEND zip22vm.zip A: unzipdoc zip a1 (RECFM F LRECL 1
  115.         SEND unz532vm.zip A: zipdoc zip a1 (RECFM F LRECL 1
  116.  
  117. Once you have the ZIP archives, extract the documentation to the minidisk of
  118. your choice by using the -d option:
  119.  
  120.     unzip -a -d A2 unzipdoc.zip
  121.     unzip -a -d A2 zipdoc.zip
  122.  
  123. The "-a" option is required because the documents are archived as
  124. ASCII text files, but they must be converted to EBCDIC to read them
  125. in VM/CMS.
  126.  
  127.  
  128. Notes
  129. =====
  130.  
  131. Different EBCDIC Character Sets
  132. -------------------------------
  133.  
  134. The documentation may look strange on your system, because UNZIP
  135. translates from ASCII to "Open Systems" EBCDIC (IBM-1047).  Unless
  136. you are a software developer, you are probably using a different
  137. kind of EBCDIC (like US EBCDIC, IBM-037).  This causes some character
  138. codes to display as different characters.  For example, the character
  139. codes that display as square brackets in IBM-1047 will display as
  140. e-acute and a-grave in IBM-037.
  141.  
  142. You can use the IBM ICONV utility to translate documents from one
  143. character set to another:
  144.  
  145.     ICONV old doc a new doc a1 (FROMCODE IBM-1047 TOCODE IBM-037
  146.  
  147.  
  148. IND$FILE protocol
  149. -----------------
  150.  
  151. This is the method by which files are transferred via 3270 sessions
  152. between PC and mainframe.
  153.  
  154. If you know how to transfer files via 3270 session between PC and
  155. mainframe, you know as much as you need to know about IND$FILE.
  156.  
  157. If your mainframe has IND$FILE, and your 3270 emulator does file
  158. transfers, you can use your emulator to transfer files between PC
  159. and mainframe.
  160.