home *** CD-ROM | disk | FTP | other *** search
/ Monster Media 1993 #2 / Image.iso / os2 / pcswocid.zip / PCSWOCID.TXT < prev    next >
Text File  |  1993-07-08  |  22KB  |  277 lines
  1. ╔═════════════════════════════════════════════════════════════════════════════╗
  2. ║                                                                             ║
  3. ║           CID Utility - PC/3270 V3.0 for WIN-OS/2 2.0 (PCSWOCID)            ║
  4. ║                                                                             ║
  5. ║Developed by Barry Cunningham, IBM Personal Systems Competency Center, Dallas║
  6. ║        (c) Copyright IBM Corporation 1992,1993. All Rights Reserved.        ║
  7. ║                                                                             ║
  8. ╠═════════════════════════════════════════════════════════════════════════════╣
  9. ║                                                                             ║
  10. ║ Who should keep reading about this utility program?  someone who...         ║
  11. ║                                                                             ║
  12. ║   ...has IBM Operating System/2 Version 2.0 (*1)                            ║
  13. ║                                                                             ║
  14. ║   ...has IBM Personal Communications/3270 Version 3.0 for Windows(TM)       ║
  15. ║   and wants to run it in the WIN-OS/2 environment of OS/2 2.0               ║
  16. ║                                                                             ║
  17. ║   ...has IBM Network Transport Services/2 (*2)                              ║
  18. ║                                                                             ║
  19. ║   ...would like to use either NetView Distribution Manager/2 V2.0 or        ║
  20. ║   the LAN CID(*3) Utility of NTS/2 to install, configure, and distribute    ║
  21. ║   PC/3270 V3.0 Windows mode from a code server to multiple OS/2 2.0         ║
  22. ║   workstations                                                              ║
  23. ║                                                                             ║
  24. ║ (TM) Windows is a trademark of the Microsoft Corporation                    ║
  25. ║                                                                             ║
  26. ║ (*1) OS/2 ServicePak REXX is a prerequisite on the CID code server.         ║
  27. ║                                                                             ║
  28. ║ (*2) NTS/2 provides the 802.2 Virtual Device Driver required to support     ║
  29. ║      the 802.2 configuration of PC/3270 for Windows V3.0 under WIN-OS/2.    ║
  30. ║                                                                             ║
  31. ║ (*3) CID = Configuration, Installation, and Distribution                    ║
  32. ╠═════════════════════════════════════════════════════════════════════════════╣
  33. ║                                                                             ║
  34. ║ What's a brief summary of the PCSWOCID utility?                             ║
  35. ║                                                                             ║
  36. ║   ...PCSWOCID supports the unattended configuration, installation, and      ║
  37. ║   distribution of Personal Communications/3270 V3.0 for Windows from        ║
  38. ║   a local or redirected drive when running under WIN-OS/2 of OS/2 2.0.      ║
  39. ║   Instead of adding multiple icons to the Program Manager of WIN-OS/2,      ║
  40. ║   PCSWOCID adds a single icon to the Desktop of OS/2's Workplace Shell,     ║
  41. ║   even allowing control over WIN-OS/2 settings via keywords placed in the   ║
  42. ║   specific response file.  PC/3270's actual install program generates       ║
  43. ║   parameter files in flat ASCII format (.WS extension), which may then      ║
  44. ║   serve as general response files.  Another program module of PC/3270       ║
  45. ║   (PCSBAT.EXE) creates files (.BCH extension) that may be manually edited   ║
  46. ║   for use as specific response files.  PCSWOCID stores progress information ║
  47. ║   in local history and error logs in the CID client target directory,       ║
  48. ║   PCSWOCID.HST and PCSWOCID.ERR respectively.  If and as specified in the   ║
  49. ║   /L1: and /L2: parameters of PCSWOCID, remote copies of these history and  ║
  50. ║   error log files are also updated.  PCSWOCID generally conforms to the     ║
  51. ║   specifications outlined in the "Configuration, Installation and           ║
  52. ║   Distribution (CID) Product Enablement Guidelines" document to be included ║
  53. ║   in ITSC Bulletin GG24-3781, including return code support to the software ║
  54. ║   distribution manager.                                                     ║
  55. ╠═════════════════════════════════════════════════════════════════════════════╣
  56. ║                                                                             ║
  57. ║ What added function do I gain by using PCSWOCID instead of the PC/3270 V3.0 ║
  58. ║ Windows mode installation program?                                          ║
  59. ║                                                                             ║
  60. ║   ...automatic configuration of poll buffer size for standard mode WIN-OS/2 ║
  61. ║   in PCSTSR.BAT of PC/3270 V3.0 Windows mode, running PCSSETUP.EXE is not   ║
  62. ║   necessary                                                                 ║
  63. ║                                                                             ║
  64. ║   ...unattended installation PC/3270 V3.0 Windows mode using general        ║
  65. ║   response files, filename.WS workstation profiles, natively generated by   ║
  66. ║   PC/3270 V3.0 Windows mode                                                 ║
  67. ║                                                                             ║
  68. ║   ...automatic creation and update of a single icon on the Desktop of       ║
  69. ║   OS/2's Workplace Shell instead of the addition of multiple icons to the   ║
  70. ║   Program Manager of WIN-OS/2 (*1)                                          ║
  71. ║                                                                             ║
  72. ║   ...automatic tuning of WIN-OS/2 Settings for link types selected in       ║
  73. ║   PC/3270 V3.0 windows mode workstation profiles (filename.WS)              ║
  74. ║                                                                             ║
  75. ║   ...optional control of WIN-OS/2 Settings through the specific response    ║
  76. ║   file [WIN-OS/2_Settings] section (*2) (*3)                                ║
  77. ║                                                                             ║
  78. ║   ...automatic configuration of multiple 802.2 link stations at least to    ║
  79. ║   the number of unique 802.2 gateway addresses encountered in general       ║
  80. ║   response files (filename.WS) referenced in a specific response file       ║
  81. ║   (filename.RSP)                                                            ║
  82. ║                                                                             ║
  83. ║   ...deletion of unwanted local PC/3270 V3.0 Windows mode files through the ║
  84. ║   specific response file [Delete_Unwanted_Files] section (see PCSWOCID.RSP  ║
  85. ║   and PC/3270's INSTALL.TXT for more information)                           ║
  86. ║                                                                             ║
  87. ║   ...unattended support of the PC/3270 V3.0 Windows mode "INSTALL /N"       ║
  88. ║   installation option allowing installations with a small disk space        ║
  89. ║   requirement (*4)                                                          ║
  90. ║                                                                             ║
  91. ║ (*1) User must add icons to WIN-OS/2 full screen program manager manually.  ║
  92. ║                                                                             ║
  93. ║ (*2) The first OS/2 ServicePak level of PMWP.DLL module is required on      ║
  94. ║ the CID client to support manual control of WIN-OS/2 Settings because       ║
  95. ║ SysCreateObject's setup string is limited to 255 characters with the        ║
  96. ║ 3/30/92 level of PMWP.DLL.                                                  ║
  97. ║                                                                             ║
  98. ║ (*3) WIN-OS/2 Setting DOS_SHELL is reserved by PCSWOCID.                    ║
  99. ║                                                                             ║
  100. ║ (*4) The network runtime path is not verified since a LAN requester may     ║
  101. ║ not be installed yet.                                                       ║
  102. ╠═════════════════════════════════════════════════════════════════════════════╣
  103. ║                                                                             ║
  104. ║ What function do I loose by using PCSWOCID instead of the PC/3270 V3.0      ║
  105. ║ Windows mode installation program?                                          ║
  106. ║                                                                             ║
  107. ║   ...PCSWOCID does not migrate existing PC/3270W V2.0 configurations.       ║
  108. ║                                                                             ║
  109. ║   ...PCSWOCID does not add any icons to the WIN-OS/2 full screen Program    ║
  110. ║   Manager, but only adds a single Workplace Shell program object to the     ║
  111. ║   OS/2 Desktop.                                                             ║
  112. ╠═════════════════════════════════════════════════════════════════════════════╣
  113. ║                                                                             ║
  114. ║ Where is all the documentation for PCSWOCID?                                ║
  115. ║ Where are the Keyword=Value pairs documented?                               ║
  116. ║                                                                             ║
  117. ║   ...PCSWOCID.TXT is the file you are reading now.                          ║
  118. ║                                                                             ║
  119. ║   ...PCSWOCID.RSP is a sample specific response file documenting PCSWOCID   ║
  120. ║   Keyword=Value pairs; note that PC/3270 V3.0 Windows mode Keyword=Value    ║
  121. ║   pairs from filename.WS workstation profiles are used but not documented.  ║
  122. ╠═════════════════════════════════════════════════════════════════════════════╣
  123. ║                                                                             ║
  124. ║ What is the NTS/2 suggested directory structure assumed for the CID server  ║
  125. ║ throughout the rest of this "README" file?                                  ║
  126. ║                                                                             ║
  127. ║ <drive>:\CID\────┐                                                          ║
  128. ║                  │                                                          ║
  129. ║                  ├──IMG──┐                                                  ║
  130. ║                  │       │                                                  ║
  131. ║                  ├──EXE  ├──PCSWINV3                                        ║
  132. ║                  │       │                                                  ║
  133. ║                  ├──DLL  ├──PRODUCTX                                        ║
  134. ║                  │       │                                                  ║
  135. ║                  ├──LOG  └──...                                             ║
  136. ║                  │                                                          ║
  137. ║                  ├──RSP                                                     ║
  138. ║                  │                                                          ║
  139. ║                  └──...                                                     ║
  140. ╠═════════════════════════════════════════════════════════════════════════════╣
  141. ║                                                                             ║
  142. ║ At what "level" of CID does PCSWOCID run?                                   ║
  143. ║                                                                             ║
  144. ║   ...PCSWOCID has only been tested in a production level CID environment    ║
  145. ║   as opposed to a maintenance system CID environment.  In other words, the  ║
  146. ║   OS/2 Workplace Shell must be active.  To date, PCSWOCID only works with   ║
  147. ║   WIN-OS/2 and not with Microsoft (R) Windows (TM).  Also, PC/3270 V3.0 for ║
  148. ║   Windows must not be active during execution of PCSWOCID.                  ║
  149. ║                                                                             ║
  150. ║ (R) Microsoft is a registered trademark of the Microsoft Corporation.       ║
  151. ║                                                                             ║
  152. ║ (TM) Windows is a trademark of the Microsoft Corporation.                   ║
  153. ╠═════════════════════════════════════════════════════════════════════════════╣
  154. ║                                                                             ║
  155. ║ Where do I place PCSWOCID files on the CID server?                          ║
  156. ║                                                                             ║
  157. ║   ...PCSWOCID.EXE belongs in the \CID\IMG\PCSWINV3 directory                ║
  158. ║                                                                             ║
  159. ║   ...PCSWOCID.TXT belongs in the \CID\IMG\PCSWINV3 directory                ║
  160. ║                                                                             ║
  161. ║   ...COMMENTS.TXT belongs in the \CID\IMG\PCSWINV3 directory                ║
  162. ║                                                                             ║
  163. ║   ...PCSWOCID.MAC belongs in the \CID\DLL directory (OS/2 DPATH of client)  ║
  164. ║                                                                             ║
  165. ║   ...PCSWOCID.DLL belongs in the \CID\DLL directory (OS/2 LIBPATH of client)║
  166. ║                                                                             ║
  167. ║   ...PCSWOCID.PRF belongs in the \CID\CLIENT directory                      ║
  168. ║                                                                             ║
  169. ║   ...PCSWOLCU.CMD belongs in the \CID\CLIENT directory                      ║
  170. ║                                                                             ║
  171. ║   ...EMPTY.FIL    belongs in the \CID\LOG\PCSWINV3 directory (see NOTE:)    ║
  172. ║                                                                             ║
  173. ║   ...PCSWOCID.RSP belongs in the \CID\RSP\PCSWINV3 directory                ║
  174. ║                                                                             ║
  175. ║   ...LAN8022.WS   belongs in the \CID\RSP\PCSWINV3 directory                ║
  176. ║                                                                             ║
  177. ║   ...SDLC.WS      belongs in the \CID\RSP\PCSWINV3 directory                ║
  178. ║                                                                             ║
  179. ║   ...SNADFT.WS    belongs in the \CID\RSP\PCSWINV3 directory                ║
  180. ║                                                                             ║
  181. ║ NOTE: These files and associated sub-directories are created automatically  ║
  182. ║ by running "pkunzip -d pcswocid.zip" from within the \CID directory on the  ║
  183. ║ CID code server.  The EMPTY.FIL enables the automatic creation of the       ║
  184. ║ sub-directory \CID\LOG\PCSWINV3.                                            ║
  185. ╠═════════════════════════════════════════════════════════════════════════════╣
  186. ║                                                                             ║
  187. ║ What other directories or files must be prepared before running PCSWOCID?   ║
  188. ║ How do I prepare the PC/3270W V3.0 image directory on the CID server?       ║
  189. ║ How do I build my general and specific response files?                      ║
  190. ║                                                                             ║
  191. ║   ...run "INSTALL /A" of PC/3270 V3.0 Windows mode (see PC/3270's           ║
  192. ║   INSTALL.TXT) to create an image directory on the CID server such as       ║
  193. ║   \CID\IMG\PCSWINV3 (CID clients need read-only access to this directory)   ║
  194. ║                                                                             ║
  195. ║   ...filename.WS workstation profiles serve as general response files,      ║
  196. ║   belong in the \CID\RSP\PCSWINV3 directory on the CID server, and are      ║
  197. ║   created using PC/3270 V3.0 Windows mode (PCSWS.EXE).  Sample general      ║
  198. ║   response files SDLC.WS, LAN8022.WS, and SNADFT.WS referenced in the       ║
  199. ║   sample specific response file PCSWOCID.RSP were created in this manner.   ║
  200. ║                                                                             ║
  201. ║   ...filename.RSP files serve as specific response files, belong in the     ║
  202. ║   \CID\RSP\PCSWINV3 directory on the CID server, and are prepared by...     ║
  203. ║                                                                             ║
  204. ║      1) creating filename.BCH batch profiles using the PC/3270 V3.0 Windows ║
  205. ║         mode PCSBAT.EXE utility                                             ║
  206. ║                                                                             ║
  207. ║      2) copying these filename.BCH batch profiles to new filename.RSP       ║
  208. ║         specific response files; mandatory file extension of .RSP           ║
  209. ║                                                                             ║
  210. ║      3) adding any desired sections from the PCSWOCID.RSP sample specific   ║
  211. ║         response file to your filename.RSP specific response files          ║
  212. ║                                                                             ║
  213. ║      4) adding any desired Keyword=Values to override those referenced in   ║
  214. ║         your general response files, filename.WS workstation profiles       ║
  215. ║                                                                             ║
  216. ║   ...when using the NetView Distribution Manager/2 V2.0 as the software     ║
  217. ║   distribution manager, use the sample change control profile               ║
  218. ║   \CID\CLIENT\PCSWINV3\PCSWOCID.PRF to a build change control file.         ║
  219. ║                                                                             ║
  220. ║   ...when using the NTS/2 LAN CID Utility (LCU) as the software             ║
  221. ║   distribution manager, use to sample LCU command file                      ║
  222. ║   \CID\CLIENT\PCSWOLCU.CMD or incorporate appropriate portions into your    ║
  223. ║   own LCU command file.  Your own LCU command file might be named           ║
  224. ║   \CID\CLIENT\DEFAULT.CMD or \CID\CLIENT\xxxxxxxx.CMD where "xxxxxxxx" is   ║
  225. ║   the NETBIOS name of a particular CID client workstation.                  ║
  226. ╠═════════════════════════════════════════════════════════════════════════════╣
  227. ║                                                                             ║
  228. ║ Where are all the PCSWOCID command line parameters documented?              ║
  229. ║                                                                             ║
  230. ║   ...Invoke PCSWOCID without any parameters to see descriptions of the      ║
  231. ║   supported command line parameters as follows:                             ║
  232. ║                                                                             ║
  233. ║PCSWOCID  -  PC/3270 V3.0 for WIN-OS/2 2.0 CID Utility  -  "Revision Date"   ║
  234. ┌─────────────────────────────────────────────────────────────────────────────┐
  235. │             PCSWOCID[.EXE] /R:[<drive><path>]<filename[.RSP]>               │
  236. │                           [/G:[<drive><path>]]                              │
  237. │                           [/S:[<drive><path>]]                              │
  238. │                           [/T:[<drive><path>]]                              │
  239. │                           [/N:<drive><path>]                                │
  240. │                           [/L1:[<drive><path>]<filespec>]                   │
  241. │                           [/L2:[<drive><path>]<filespec>]                   │
  242. ├─────────────────────────────────────────────────────────────────────────────┤
  243. │            [<drive><path>] defaults to the current <drive><path>            │
  244. ├─────┬───────────────────────────────────────────────────────────────────────┤
  245. │ /R: │ Specific Response File, based on filename.BCH and PCSWOCID.RSP        │
  246. │ /G: │ General Response File Path, filename.WS workstation profiles          │
  247. │ /S: │ Source Path, "INSTALL /A" PC/3270 V3.0 for Windows disk images        │
  248. │ /T: │ Target Path, new or existing PC/3270 V3.0 for Windows installation    │
  249. │ /N: │ Network Runtime Path, "INSTALL /A" PC/3270 V3.0 Windows disk images   │
  250. │ /L1:│ Remote History Log, duplicate of Target Path PCSWOCID.HST log file    │
  251. │ /L2:│ Remote Error Log, duplicate of Target Path PCSWOCID.ERR log file      │
  252. └─────┴───────────────────────────────────────────────────────────────────────┘
  253. ║Developed by Barry Cunningham, IBM Personal Systems Competency Center, Dallas║
  254. ║          (c) Copyright IBM Corporation 1992. All Rights Reserved.           ║
  255. ╠═════════════════════════════════════════════════════════════════════════════╣
  256. ║                                                                             ║
  257. ║ How can I get suggestions or comments about this utility to the             ║
  258. ║ Personal Systems Competency Center(PSCC) or inquire about other             ║
  259. ║ offerings?                                                                  ║
  260. ║                                                                             ║
  261. ║   ...Print out the COMMENTS.TXT file in the \CID\IMG\PCSWINV3 directory     ║
  262. ║   and return it to the PSCC according to instructions given on the form.    ║
  263. ║                                                                             ║
  264. ║ Where can I address technical questions about this utility to other users   ║
  265. ║ or to the author?                                                           ║
  266. ║                                                                             ║
  267. ║   ...Utilize the OS2INST CFORUM on the IBM OS/2 BBS (on IBMPC internally).  ║
  268. ║   Call 1-800-547-1283 for more information regarding the IBM OS/2 BBS.      ║
  269. ║                                                                             ║
  270. ╠═════════════════════════════════════════════════════════════════════════════╣
  271. ║                                                                             ║
  272. ║ What are some PCSWOCID special tips and techniques?                         ║
  273. ║                                                                             ║
  274. ║   ...Invalid program invocation errors will not be recorded in the remote   ║
  275. ║   error log unless a valid /L2: is specified as the first parameter.        ║
  276. ╚═════════════════════════════════════════════════════════════════════════════╝
  277.