ͻ
                                                                             
           CID Utility - PC/3270 V3.0 for WIN-OS/2 2.0 (PCSWOCID)            
                                                                             
Developed by Barry Cunningham, IBM Personal Systems Competency Center, Dallas
        (c) Copyright IBM Corporation 1992,1993. All Rights Reserved.        
                                                                             
͹
                                                                             
 Who should keep reading about this utility program?  someone who...         
                                                                             
   ...has IBM Operating System/2 Version 2.0 (*1)                            
                                                                             
   ...has IBM Personal Communications/3270 Version 3.0 for Windows(TM)       
   and wants to run it in the WIN-OS/2 environment of OS/2 2.0               
                                                                             
   ...has IBM Network Transport Services/2 (*2)                              
                                                                             
   ...would like to use either NetView Distribution Manager/2 V2.0 or        
   the LAN CID(*3) Utility of NTS/2 to install, configure, and distribute    
   PC/3270 V3.0 Windows mode from a code server to multiple OS/2 2.0         
   workstations                                                              
                                                                             
 (TM) Windows is a trademark of the Microsoft Corporation                    
                                                                             
 (*1) OS/2 ServicePak REXX is a prerequisite on the CID code server.         
                                                                             
 (*2) NTS/2 provides the 802.2 Virtual Device Driver required to support     
      the 802.2 configuration of PC/3270 for Windows V3.0 under WIN-OS/2.    
                                                                             
 (*3) CID = Configuration, Installation, and Distribution                    
͹
                                                                             
 What's a brief summary of the PCSWOCID utility?                             
                                                                             
   ...PCSWOCID supports the unattended configuration, installation, and      
   distribution of Personal Communications/3270 V3.0 for Windows from        
   a local or redirected drive when running under WIN-OS/2 of OS/2 2.0.      
   Instead of adding multiple icons to the Program Manager of WIN-OS/2,      
   PCSWOCID adds a single icon to the Desktop of OS/2's Workplace Shell,     
   even allowing control over WIN-OS/2 settings via keywords placed in the   
   specific response file.  PC/3270's actual install program generates       
   parameter files in flat ASCII format (.WS extension), which may then      
   serve as general response files.  Another program module of PC/3270       
   (PCSBAT.EXE) creates files (.BCH extension) that may be manually edited   
   for use as specific response files.  PCSWOCID stores progress information 
   in local history and error logs in the CID client target directory,       
   PCSWOCID.HST and PCSWOCID.ERR respectively.  If and as specified in the   
   /L1: and /L2: parameters of PCSWOCID, remote copies of these history and  
   error log files are also updated.  PCSWOCID generally conforms to the     
   specifications outlined in the "Configuration, Installation and           
   Distribution (CID) Product Enablement Guidelines" document to be included 
   in ITSC Bulletin GG24-3781, including return code support to the software 
   distribution manager.                                                     
͹
                                                                             
 What added function do I gain by using PCSWOCID instead of the PC/3270 V3.0 
 Windows mode installation program?                                          
                                                                             
   ...automatic configuration of poll buffer size for standard mode WIN-OS/2 
   in PCSTSR.BAT of PC/3270 V3.0 Windows mode, running PCSSETUP.EXE is not   
   necessary                                                                 
                                                                             
   ...unattended installation PC/3270 V3.0 Windows mode using general        
   response files, filename.WS workstation profiles, natively generated by   
   PC/3270 V3.0 Windows mode                                                 
                                                                             
   ...automatic creation and update of a single icon on the Desktop of       
   OS/2's Workplace Shell instead of the addition of multiple icons to the   
   Program Manager of WIN-OS/2 (*1)                                          
                                                                             
   ...automatic tuning of WIN-OS/2 Settings for link types selected in       
   PC/3270 V3.0 windows mode workstation profiles (filename.WS)              
                                                                             
   ...optional control of WIN-OS/2 Settings through the specific response    
   file [WIN-OS/2_Settings] section (*2) (*3)                                
                                                                             
   ...automatic configuration of multiple 802.2 link stations at least to    
   the number of unique 802.2 gateway addresses encountered in general       
   response files (filename.WS) referenced in a specific response file       
   (filename.RSP)                                                            
                                                                             
   ...deletion of unwanted local PC/3270 V3.0 Windows mode files through the 
   specific response file [Delete_Unwanted_Files] section (see PCSWOCID.RSP  
   and PC/3270's INSTALL.TXT for more information)                           
                                                                             
   ...unattended support of the PC/3270 V3.0 Windows mode "INSTALL /N"       
   installation option allowing installations with a small disk space        
   requirement (*4)                                                          
                                                                             
 (*1) User must add icons to WIN-OS/2 full screen program manager manually.  
                                                                             
 (*2) The first OS/2 ServicePak level of PMWP.DLL module is required on      
 the CID client to support manual control of WIN-OS/2 Settings because       
 SysCreateObject's setup string is limited to 255 characters with the        
 3/30/92 level of PMWP.DLL.                                                  
                                                                             
 (*3) WIN-OS/2 Setting DOS_SHELL is reserved by PCSWOCID.                    
                                                                             
 (*4) The network runtime path is not verified since a LAN requester may     
 not be installed yet.                                                       
͹
                                                                             
 What function do I loose by using PCSWOCID instead of the PC/3270 V3.0      
 Windows mode installation program?                                          
                                                                             
   ...PCSWOCID does not migrate existing PC/3270W V2.0 configurations.       
                                                                             
   ...PCSWOCID does not add any icons to the WIN-OS/2 full screen Program    
   Manager, but only adds a single Workplace Shell program object to the     
   OS/2 Desktop.                                                             
͹
                                                                             
 Where is all the documentation for PCSWOCID?                                
 Where are the Keyword=Value pairs documented?                               
                                                                             
   ...PCSWOCID.TXT is the file you are reading now.                          
                                                                             
   ...PCSWOCID.RSP is a sample specific response file documenting PCSWOCID   
   Keyword=Value pairs; note that PC/3270 V3.0 Windows mode Keyword=Value    
   pairs from filename.WS workstation profiles are used but not documented.  
͹
                                                                             
 What is the NTS/2 suggested directory structure assumed for the CID server  
 throughout the rest of this "README" file?                                  
                                                                             
 <drive>:\CID\Ŀ                                                          
                                                                            
                  IMGĿ                                                  
                                                                           
                  EXE  PCSWINV3                                        
                                                                           
                  DLL  PRODUCTX                                        
                                                                           
                  LOG  ...                                             
                                                                            
                  RSP                                                     
                                                                            
                  ...                                                     
͹
                                                                             
 At what "level" of CID does PCSWOCID run?                                   
                                                                             
   ...PCSWOCID has only been tested in a production level CID environment    
   as opposed to a maintenance system CID environment.  In other words, the  
   OS/2 Workplace Shell must be active.  To date, PCSWOCID only works with   
   WIN-OS/2 and not with Microsoft (R) Windows (TM).  Also, PC/3270 V3.0 for 
   Windows must not be active during execution of PCSWOCID.                  
                                                                             
 (R) Microsoft is a registered trademark of the Microsoft Corporation.       
                                                                             
 (TM) Windows is a trademark of the Microsoft Corporation.                   
͹
                                                                             
 Where do I place PCSWOCID files on the CID server?                          
                                                                             
   ...PCSWOCID.EXE belongs in the \CID\IMG\PCSWINV3 directory                
                                                                             
   ...PCSWOCID.TXT belongs in the \CID\IMG\PCSWINV3 directory                
                                                                             
   ...COMMENTS.TXT belongs in the \CID\IMG\PCSWINV3 directory                
                                                                             
   ...PCSWOCID.MAC belongs in the \CID\DLL directory (OS/2 DPATH of client)  
                                                                             
   ...PCSWOCID.DLL belongs in the \CID\DLL directory (OS/2 LIBPATH of client)
                                                                             
   ...PCSWOCID.PRF belongs in the \CID\CLIENT directory                      
                                                                             
   ...PCSWOLCU.CMD belongs in the \CID\CLIENT directory                      
                                                                             
   ...EMPTY.FIL    belongs in the \CID\LOG\PCSWINV3 directory (see NOTE:)    
                                                                             
   ...PCSWOCID.RSP belongs in the \CID\RSP\PCSWINV3 directory                
                                                                             
   ...LAN8022.WS   belongs in the \CID\RSP\PCSWINV3 directory                
                                                                             
   ...SDLC.WS      belongs in the \CID\RSP\PCSWINV3 directory                
                                                                             
   ...SNADFT.WS    belongs in the \CID\RSP\PCSWINV3 directory                
                                                                             
 NOTE: These files and associated sub-directories are created automatically  
 by running "pkunzip -d pcswocid.zip" from within the \CID directory on the  
 CID code server.  The EMPTY.FIL enables the automatic creation of the       
 sub-directory \CID\LOG\PCSWINV3.                                            
͹
                                                                             
 What other directories or files must be prepared before running PCSWOCID?   
 How do I prepare the PC/3270W V3.0 image directory on the CID server?       
 How do I build my general and specific response files?                      
                                                                             
   ...run "INSTALL /A" of PC/3270 V3.0 Windows mode (see PC/3270's           
   INSTALL.TXT) to create an image directory on the CID server such as       
   \CID\IMG\PCSWINV3 (CID clients need read-only access to this directory)   
                                                                             
   ...filename.WS workstation profiles serve as general response files,      
   belong in the \CID\RSP\PCSWINV3 directory on the CID server, and are      
   created using PC/3270 V3.0 Windows mode (PCSWS.EXE).  Sample general      
   response files SDLC.WS, LAN8022.WS, and SNADFT.WS referenced in the       
   sample specific response file PCSWOCID.RSP were created in this manner.   
                                                                             
   ...filename.RSP files serve as specific response files, belong in the     
   \CID\RSP\PCSWINV3 directory on the CID server, and are prepared by...     
                                                                             
      1) creating filename.BCH batch profiles using the PC/3270 V3.0 Windows 
         mode PCSBAT.EXE utility                                             
                                                                             
      2) copying these filename.BCH batch profiles to new filename.RSP       
         specific response files; mandatory file extension of .RSP           
                                                                             
      3) adding any desired sections from the PCSWOCID.RSP sample specific   
         response file to your filename.RSP specific response files          
                                                                             
      4) adding any desired Keyword=Values to override those referenced in   
         your general response files, filename.WS workstation profiles       
                                                                             
   ...when using the NetView Distribution Manager/2 V2.0 as the software     
   distribution manager, use the sample change control profile               
   \CID\CLIENT\PCSWINV3\PCSWOCID.PRF to a build change control file.         
                                                                             
   ...when using the NTS/2 LAN CID Utility (LCU) as the software             
   distribution manager, use to sample LCU command file                      
   \CID\CLIENT\PCSWOLCU.CMD or incorporate appropriate portions into your    
   own LCU command file.  Your own LCU command file might be named           
   \CID\CLIENT\DEFAULT.CMD or \CID\CLIENT\xxxxxxxx.CMD where "xxxxxxxx" is   
   the NETBIOS name of a particular CID client workstation.                  
͹
                                                                             
 Where are all the PCSWOCID command line parameters documented?              
                                                                             
   ...Invoke PCSWOCID without any parameters to see descriptions of the      
   supported command line parameters as follows:                             
                                                                             
PCSWOCID  -  PC/3270 V3.0 for WIN-OS/2 2.0 CID Utility  -  "Revision Date"   
Ŀ
             PCSWOCID[.EXE] /R:[<drive><path>]<filename[.RSP]>               
                           [/G:[<drive><path>]]                              
                           [/S:[<drive><path>]]                              
                           [/T:[<drive><path>]]                              
                           [/N:<drive><path>]                                
                           [/L1:[<drive><path>]<filespec>]                   
                           [/L2:[<drive><path>]<filespec>]                   
Ĵ
            [<drive><path>] defaults to the current <drive><path>            
Ĵ
 /R:  Specific Response File, based on filename.BCH and PCSWOCID.RSP        
 /G:  General Response File Path, filename.WS workstation profiles          
 /S:  Source Path, "INSTALL /A" PC/3270 V3.0 for Windows disk images        
 /T:  Target Path, new or existing PC/3270 V3.0 for Windows installation    
 /N:  Network Runtime Path, "INSTALL /A" PC/3270 V3.0 Windows disk images   
 /L1: Remote History Log, duplicate of Target Path PCSWOCID.HST log file    
 /L2: Remote Error Log, duplicate of Target Path PCSWOCID.ERR log file      

Developed by Barry Cunningham, IBM Personal Systems Competency Center, Dallas
          (c) Copyright IBM Corporation 1992. All Rights Reserved.           
͹
                                                                             
 How can I get suggestions or comments about this utility to the             
 Personal Systems Competency Center(PSCC) or inquire about other             
 offerings?                                                                  
                                                                             
   ...Print out the COMMENTS.TXT file in the \CID\IMG\PCSWINV3 directory     
   and return it to the PSCC according to instructions given on the form.    
                                                                             
 Where can I address technical questions about this utility to other users   
 or to the author?                                                           
                                                                             
   ...Utilize the OS2INST CFORUM on the IBM OS/2 BBS (on IBMPC internally).  
   Call 1-800-547-1283 for more information regarding the IBM OS/2 BBS.      
                                                                             
͹
                                                                             
 What are some PCSWOCID special tips and techniques?                         
                                                                             
   ...Invalid program invocation errors will not be recorded in the remote   
   error log unless a valid /L2: is specified as the first parameter.        
ͼ
