BIM-PC/TRANSFER HOST TO PC FILE TRANSFER UTILITY INSTALLATION AND OPERATIONS GUIDE. Release 1.7 (COPYRIGHT 1998, B I MOYLE ASSOCIATES, INC.

Transcription

1 HOST TO PC FILE TRANSFER UTILITY INSTALLATION AND OPERATIONS GUIDE Release 1.7 (COPYRIGHT 1998, B I MOYLE ASSOCIATES, INC.) BIM-PC/TRANSFER is a proprietary product of B I Moyle Associates, Inc. It cannot be reproduced, changed, copied, or stored in any form (including, but not limited to, copies on magnetic media) without the express prior written permission of B I Moyle Associates, Inc.

2 Copyright Notice BIM-PC/TRANSFER is a proprietary product of B I Moyle Associates, Inc. It cannot be reproduced, changed, copied, or stored in any form (including, but not limited to, copies on magnetic media) without the express prior written permission of B I Moyle Associates, Inc. BIM-PC/TRANSFER contains two components, a mainframe component and a PC component. The PC component is distributed in four versions, one for each of the following environments: 1) Microsoft Windows 95/98 or NT 2) Microsoft Windows 3.1 3) OS/2 4) MS-DOS or PC-DOS You are hereby granted the right to install the Microsoft Windows and/or the OS/2 versions of the PC component of BIM-PC/TRANSFER on as many PCs as you require, as long as all of the PCs you install it on connect to and use the same mainframe component of BIM-PC/TRANSFER. The DOS version of the PC component of BIM-PC/TRANSFER uses a DOS-Extender developed by Phar Lap Software Inc. The run-time license agreement between BIM and Phar Lap Software Inc. requires that each distribution diskette from BIM be installed on a single PC. If the PC is a server of a network, then all PCs connected to the server can share the same version. If you have multiple DOS PCs, not connected to a server, that you want to run BIM-PC/TRANSFER, additional distribution diskettes are available from BIM for a small fee. This documentation applies to Release 1.7 of the program product BIM- PC/TRANSFER. Original Printing...11/01/98 Last Revised...05/20/99

3 TABLE OF CONTENTS GETTING STARTED...1 Introduction... 3 Features of BIM-PC/TRANSFER... 4 PC/TRANSFER Overview... 6 Download Procedure... 8 Upload Procedure... 9 New for This Release Migration Requirements System Requirements Installation for a VSE Host VSE Installation Step 1 - Load Distribution Tape VSE Installation Step 2 - Release Install Job VSE Installation Step 3 - Supply LIBDEF VSE Installation Step 4 - Define the Host Control File VSE Installation Step 5 - Define Host Activity Log File VSE Installation Step 6 - CICS/VS Table Additions VSE Installation Step 7 - BIM-TMAN Setup VSE Installation Step 8 - Customization VSE Installation Step 9 - Activating the TCP/IP Interface VSE Installation Step 10 - PC Program Installation Installation for a MVS Host MVS Installation Step 1 - Load Distribution Tape MVS Installation Step 2 - Install SVC MVS Installation Step 3 - Customize JES Interface MVS Installation Step 4 - Define the Host Control File MVS Installation Step 5 - Define Host Activity Log File MVS Installation Step 6 - CICS/VS Table Additions MVS Installation Step 7 - BIM-TMAN Setup MVS Installation Step 8 - Customization MVS Installation Step 9 - PC Program Installation Connecting the PC to the Host BIM-PC/TRANSFER Connection Settings Single Connection Definition Connection Profile Definitions Profile List Dialog Profile Details Dialog Using Connection Profiles In Manual Transfers Using Connection Profiles In Automatic Transfers LU2 Settings TCP/IP Settings APPC Settings LU2/3270 Connections Using Microsoft Windows HLLAPI Application Interface PATH Statement DLL Specification Verify Session ID BIM-PC/TRANSFER Configurator LU2/3270 Connections Using OS/ HLLAPI Application Interface Verify Session ID LU2/3270 Connections Using DOS BIMDOSCK Program I

4 TABLE OF CONTENTS IRMA(DCA) E78+ Special Processing...56 TLINK Special Processing...56 TCP/IP Connections to the Host...57 Overview...57 Activating the Listen Task...57 APPC Connections Using Microsoft Windows or OS/ APPC Connection Overview...58 VTAM Definitions on the Host for APPC...59 CICS Definitions on the Host for APPC...60 BIM-PC/TRANSFER Definitions for APPC...61 PATH Statement for Windows version...61 APPC Interface Configuration on the PC...61 IRMA Workstation for Windows (APPC)...62 RUMBA (APPC)...63 DynaComm/Elite (APPC)...64 Communications Manager/2 for OS/2 (APPC)...65 IBM Personal Communications PC/3270 (APPC)...66 Attachmate Personal Client (APPC)...67 Logon/Logoff Scripts...69 #LOOK...69 #AT...70 #SEND...70 #BYE...71 Example Logon Script...72 Example Logoff Script...73 Example Automatic Transfer Scripts...73 BIMLOGON - Logon/Logoff Script Recorder...74 Option Pull Down...74 File Pull Down...75 Recording A Script...75 Security Overview...78 Security for Host Maintenance...78 Security for Transfers...78 User Security Groups...79 Dataset Access Security...79 VSAM Security...80 Access Security Definitions...80 USING BIM-PC/TRANSFER...83 Using The PC Transfer Program - BIMFTR(x)...85 Starting the PC Program from within Microsoft Windows 95/98 or NT 4.x...85 Starting the PC Program from within Microsoft Windows 3.1 or NT 3.5.x...85 Starting the PC Program from within OS/ Starting the PC Program from the DOS Command Line...86 Signing On...88 PC File Transfer Window...89 File Pulldown...90 Transfer Pulldown...92 Help Pulldown...93 Dialog Boxes...94 General Settings Dialog...94 Interface Settings Dialog...96 Log Settings Dialog...97 II

5 TABLE OF CONTENTS File Dialog Download Selection Dialog Generic LIBQUE Values for Downloads Download Destination Dialog Upload Selection Dialog Generic LIBQUE Values for Uploads ASCII Translation Option CRLF Transfer Option Transfer Status Dialog Using The PC Automatic Transfer Program - BIMAFT(x) Starting BIMAFT(x) from within Microsoft Windows 95/98 or NT 4.x Starting BIMAFT(x) from within Microsoft Windows 3.1 or NT 3.5.x Starting BIMAFTO from within OS/ Starting BIMAFTD from the DOS Command Line BIMAFT(x) Main Program Window File Pull Down Process Pulldown Help Pulldown Auto Settings Dialog Script Recording Signon Dialog Execute PC Program Dialog Automatic Transfer Options Dialog Host Transfer Send to Netname Dialog Automatic Transfer Script #KEEP #SENDTO #SIGNON #OPTION #IFEXISTS #IFNOTEXISTS #ENDIF #DOWNLOAD #UPLOAD #TRANSFER #EXEC #COPY #RENAME #MOVE #ERASE #HOSTAFT #START #PROMPT Labels #IF #GOTO #END Sample Scripts Host Initiated Automatic File Transfer (HOSTAFT) Overview Monitoring HOSTAFT Status HOSTAFT Script Overview HOSTAFT Script Variable Substitution III

6 TABLE OF CONTENTS Activating/Deactivating HOSTAFT on The PC Activating A HOSTAFT Script for Processing Activating A HOSTAFT Script In Batch VTAM Definitions for BIMFTRBC CICS Definitions for BIMFTRBC VSE JCL to Execute BIMFTRBC MVS JCL to Execute BIMFTRBC Commands and Operands for BIMFTRBC OPTION Command CONNECT Command HOSTAFT Command UPARM Command Activating a HOSTAFT Script with a CICS Application File Upload Scripts Processing Options #PROMPT Labels #IF #INCLUDE #GOTO data line Variable Substitution #END Sample Script Host Customization using the FTRM Transaction Adding / Changing Definitions PF Key Summary System Menu System Options Screen Category Definition List Category Definition Screen User Definition List User Definition Screen VSAM Profile List VSAM Profile Definition Screen SAM Profile List SAM Profile Definition Screen Download/HOSTAFT Script List Download/HOSTAFT Script Definition Screen Dataset Access List Dataset Access Definition Screen Access Security Definitions Access Level and Array Entries Variable Substitution Generic Masks Processing Overview Access Security Definitions (List) Access Security Definitions for POWER Common Fields Access Security Definitions for EDIT Access Security Definitions for Scripts Access Security Definitions for ICCF Access Security Definitions for LIBR IV

7 TABLE OF CONTENTS Access Security Definitions for JES Access Security Definitions for CICS Temporary Storage HOSTAFT Status List HOSTAFT Status Detail Screen Special PF Keys General Script Information Fields Individual PC Status Fields HOSTAFT Log Display Screen HOSTAFT Activate Script Screen TCP/IP Connection Options Viewing The Host Transfer Activity Log (FTRL) PF Key Summary Transfer Activity Log Display Transfer Event Display Printing The Host Transfer Activity Log Sample Report Program BIMFTRPR VSE JCL to Execute BIMFTRPR MVS JCL to Execute BIMFTRPR Commands and Operands for BIMFTRPR Syntax PRINT Command Field List Operands Field name Keywords Field name Relational Operators (list) formats and rules Rules for numbers as values Rules for Date and Time values Rules for strings as values Sample Print Commands BIMFCV - File Conversion Utility Customizing BIMFCV File Conversion Scripts Comments Processing Options Field Definitions Record Descriptions #PROMPT Labels #IF #GOTO #ERROR #GROUPBEG - Group Begin #GROUPEND - Group End #CRLF #INSERT Literal #LINE #END #SKIP Record Special Requirements for BIMFCV Putting it all together (1) - A Simple Fixed Length Record File (2) - A variable file containing multiple record types V

8 TABLE OF CONTENTS Files Containing a COBOL OCCURS DEPENDING ON clause Processing ASCII Files Character Strings Testing Your Script Driver Specifications BIMFTRD$ - IND$ Driver (VSE Only) BIMFTRDC - VSAM Cluster Driver BIMFTRDD - Partitioned Dataset Driver (MVS Only) BIMFTRDE - BIM-EDIT Library Driver BIMFTRDF - BIM-EPIC and SAM Dataset Driver (VSE Only) BIMFTRDI - ICCF Library Driver (VSE Only) BIMFTRDJ - JES Access Driver (MVS Only) BIMFTRDL - VSE Library Driver (VSE Only) BIMFTRDM - CICS Temporary Storage Access BIMFTRDP - POWER Queue Driver (VSE Only) BIMFTRDQ - Sequential (QSAM) Dataset Driver (MVS Only) BIMFTRDR - VSE Library Access Using BIM-EDIT (VSE Only) BIMFTRDT - CICS Transient Data Upload Driver BIMFTRDV - VSAM Dataset Driver (Using Profiles) BIMFTRDX - Download/HOSTAFT Script File Access VSE/SP Interactive Interface User Security Exits Format / Selection Exits Default Translate Tables MESSAGES BIMFCV Error Messages BIMFTR-7nn Error Messages Messages From Host During Transfer FTRL Transaction Messages FTRM Transaction Messages BIMFTRBC Messages BIMFTRLB Messages BIMFTRFI Messages BIMFTRPR Messages BIMFTRxx-nnnn Messages Allocation / Deallocation Errors EIBRESP Codes VSE XPCC Response Codes POWER XPCC Response Codes APPENDIX A How To Code Commands (Syntax) VI

9 GETTING STARTED Page 1

10 Page 2 Introduction

11 Introduction BIM-PC/TRANSFER is a PC-Host File Transfer System that allows data to be transferred between any PC that is running a 3270 Emulator or an APPC interface, and a host computer running CICS or BIM-TMAN. HOST TO PC FILE TRANSFER Versions of the PC progam are available for Microsoft Windows 3.1, 3.11, 95/98, NT, OS/2, MS-DOS, and PC-DOS. BIM-PC/TRANSFER requires a 3270 emulator package, an APPC interface, or a TCP/IP connection be installed on the PC. Refer to the section System Requirements on page 14 for a list of the supported emulators and interfaces. The following types of data can be transferred to and from the PC depending on your host operating system: BIM-EDIT members VSE Librarian (LIBR) members POWER jobs and reports in the RDR, PUN, or LST queues VSAM datasets VSE VSAM-Managed-SAM datasets VSE SAM datasets BIM-EPIC managed SAM datasets CICS Transient Data (uploads to CICS only) CICS Temporary Storage Queues Files contained in the VSE Host Transfer File (IND$) ICCF members (download to PC support only) JES reports in the output or hold queues (download support only) Job submission to the JES internal reader queue Partitioned Dataset (PDS) members MVS Sequential Datasets (QSAM) Introduction Page 3

12 Features of BIM-PC/TRANSFER Transfers are normally initiated and controlled by the PC. In this mode, the host side acts as a server, responding to the requests from the PC. The Host Initiated Automatic File Transfer feature (HOSTAFT) of BIM- PC/TRANSFER allows transfers to be initiated by the host, via a batch job stream, or a CICS application program. The host side of BIM-PC/TRANSFER can either run under CICS or BIM- TMAN. BIM-TMAN is a VTAM application platform available separately from BIM. The PC-to-host connection can be LU2, APPC, or for VSE systems that have TCP/IP for VSE from Connectivity Systems, a TCP/IP connection can be used. An on-line transaction (FTRM) is provided by BIM-PC/TRANSFER. This is used to define to the host the types of transfers that are to be supported, and which PC users are allowed to perform them. A Transfer Activity Log can be maintained by the host side of BIM- PC/TRANSFER in a VSAM RRDS dataset. An on-line transaction (FTRL) is provided for viewing this log. A Transfer Log can also be maintained at each PC. All transfers can be secured on the host using signon authorization. An extensive set of security options are available to limit access to host datasets, reports, and members to appropriate PC users. A user exit can also be written to perform security checks not normally supported by BIM- PC/TRANSFER. Transfers can be performed by request using the PC program BIMFTR(x), or can be automated by using the PC program BIMAFT(x). PC program BIMFTR(x) performs transfers in response to a series of queries and selections by the PC user. PC program BIMAFT(x) is an automated transfer program. This program uses a script that defines which transfers are to be performed. The scripts can be constructed manually using the text editor within BIMAFT(x) or any other PC text editor. The scripts can also be constructed using a 'record' feature of BIMAFT(x). Data can be transferred in either EBCDIC or ASCII, with or without CRLF separation. A script language is provided for both the PC and the Host for use during all downloads. Scripts can be used for record selection and data format conversions. The PC script can also be used for other file conversions. Page 4 Introduction

13 A PC upload script can be used to concatenate PC files, and/or wrap host JCL around files during uploads. Introduction Page 5

14 PC/TRANSFER Overview This section provides a brief overview of the transfer process on the PC. The PC program is relatively easy to use, and is shipped in four versions: 1) a 32-bit version for Microsoft Windows NT/95/98 (BIMFTRT.EXE) 2) a 16-bit version for Microsoft Windows (BIMFTR.EXE) 3) a 32-bit version for OS/2 (BIMFTRO.EXE) 4) a 16-bit version for DOS (BIMFTRD.EXE) Help panels are available in the PC program that provide more information regarding its operation. Refer to the section Using The PC Transfer Program - BIMFTR(x) on page 85 for a more detailed description of its use. The PC program requires that a 3270 emulator, an APPC interface, or a TCP/IP interface be running on the PC. The 3270 emulator must support the HLLAPI application interface. The APPC interface is not supported in DOS. The TCP/IP interface is only supported in VSE. If using a 3270 emulator, the PC user must establish a 3270 session with the CICS or BIM-TMAN on the mainframe side of BIM-PC/TRANSFER before starting the PC program. If you are using BIM-TMAN, you must also select transaction FTRT from the BIM-TMAN menu. The PC user will be required to enter a userid and password each time the PC program is started. BIM-PC/TRANSFER - PC File Transfer (95/NT) File Transfer Debug Help Upload... Download... Select all... Transfer... Accept... Accept All... Selected Items BIMDWDF.LST <-DNLD-- PWR,LST,BIMDWDF 143 LD3 1 AUPTS2.LST <-DNLD-- PWR,LST,AUPTS LD3 1 ALANE2.FTS --UPLD-> EDIT,DDW,ALANE2 FTS BIMDWDF.ASM <-DNLD-- EDIT,DDW,BIMDWDF ASM BIMDWDG.ASM <-DNLD-- EDIT,DDW,BIMDWDG ASM Available Items - 4 entries for Category POWER Queue Access Job Job Line Page Name Numbr Sfx CDP Rem S CC Form Date Time Count Count BIMSPLTX 3968 QD3 1 CMPL 08/11/96 13:18: BIMFTRSX 125 QD6 1 07/15/96 20:48: BIMFTRCM 130 QD6 1 07/15/96 20:40: BIMFTRDX 131 QD6 1 07/15/96 20:40: Page 6 Introduction

15 The main program window, shown above, is divided into two list boxes. Initially, both lists are empty. As you select items for upload and/or download, the upper list will fill in with the pending transfers. The lower list is filled in response to a download query request. Access to host files is based on what BIM-PC/TRANSFER refers to as Transfer Categories. Categories define the type of information that can be transferred, and which PC users can have access to the information. A dialog similar to the one shown below is displayed when BIM-PC/TRANSFER needs to known what category is desired for a specific transfer. The dialog will only contain the categories that the specific PC user is authorized for. VSE: Host Access BIM-EDIT Library Access ICCF Library Download Access Host Transfer File Access (IND$) VSE Library Access (LIBR) POWER Queue Access VSAM Dataset Access by Profile VSAM Cluster Access MVS: Host Access BIM-EDIT Library Access JES Queue Access Partitioned Dataset Access Sequential Dataset Access VSAM Dataset Access by Profile VSAM Cluster Access A download (from mainframe to PC) request is a multi-step process. First, you need to select the mainframe category that you wish to download from, and then you will need to supply some selection criteria for that category. Once the selection criteria is set, this program will enter into a conversation with the mainframe to obtain a list of available files for download purposes. The list of available files is put into the lower list box in the main window. You can then select one or more files for download by clicking with the PC mouse on the relevant entry in the list. An upload (from PC to mainframe) request is also a multi-step process. Here, you will first select the PC file that is to be uploaded to the mainframe. Then you will determine the category to upload the file into and fill out necessary identifying information specific to that category. In neither case will the actual file transfer occur at this time. Instead, your selection will be placed in the upper list box in the main window. You can review and/or change your selections prior to transfer by clicking with the PC mouse on the appropriate selection entry. When you are ready to transfer data to or from Introduction Page 7

16 the mainframe, select the transfer option from the File Menu. Both uploads and downloads may be mixed within a transfer operation. In summary, a transfer is a two step procedure: 1) the file or files for transfer are selected, and 2) the transfer process is started for all selected files. Similar looking dialog boxes will be presented to you for both upload and download operations. The sequence of appearance will differ somewhat as well as the specific contents of the individual dialog box. The following is a step-bystep overview of the selection process. Download Procedure Click on the File Menu selection and choose Download. You will then see a menu of available host categories that you may choose to download from. (If you don't get a menu, the mainframe portion of the BIM- PC/TRANSFER program may not be completely installed.) Choose the category you wish to download from and click on the left mouse button. You will be presented with a dialog asking you for selection criteria for the particular category you have chosen. The selection fields, their contents and requirements vary by category. Information is supplied in the Help Index for those categories supplied by BIM. When you have made your selection entries, click on the OK button. Your request will be sent to the host for resolution. The mainframe will review your selection criteria and return a list of files matching your entries. This file list will be placed in the lower of the two list boxes in the main window. When the mainframe process is completed, you can choose one or more files from the list for download. When you choose a file for download, you will be presented with a dialog that allows you to specify the PC file characteristics and transfer options. Page 8 Introduction

17 Upload Procedure Click on the File Menu selection and choose Upload. You will be presented with the PC file dialog that allows you to locate and select a PC file for upload to the mainframe. Once you have selected the file, you will need to choose the mainframe category to upload the file into. A list of available categories will be presented. After selecting the category, you will need to supply identifying information for the mainframe. The information requirements vary according to the category you selected. In each case, when the selection process is complete, the file will be placed in the upper list box. Transfer will not occur until you request it from the Transfer option on the File Menu. Introduction Page 9

18 New for This Release New for Release 1.7 New for Release 1.6 This section highlights the new features that have been added to this release of BIM-PC/TRANSFER. Detailed information on each of these features can be found in the remainder of this manual. New SAM and BIM-EPIC managed dataset support has been added via a new driver (BIMFTRDF). Refer to section REF _Ref \h BIMFTRDF - BIM-EPIC and SAM Dataset Driver (VSE Only) on page 322 for more information. A new operand (OLEN=) has been added to the File Conversion Script field definition. Refer to page 275 for more information. New "Connection Profiles" are supported in the 32-bit Windows versions of the PC program. Refer to section "Connection Profile Definitions" on page 41 for more information. #PROMPT, #GOTO, #IF statements have been added to Automatic Transfer Scripts. Refer to section "Automatic Transfer Script" on page 126 for more information. LU3270 Logoff Scripts are now supported. Refer to section "Logon/Logoff Scripts" on page 69 for more information. New support has been added for TCP/IP connections between the PC and a VSE host running TCP/IP for VSE from Connectivity Systems. New VSAM Cluster Access Support via a new driver (BIMFTRDC). Refer to section BIMFTRDC - VSAM Cluster Driver on page 308 for more information. New CICS Temporary Storage Access Support via a new driver (BIMFTRDM). Refer to section BIMFTRDM - CICS Temporary Storage Access on page 339 for more information. Most drivers now support the specification of a generic LIBQUE which will generate a new dialog on the PC containing the matching LIBQUE values. The PC user than selects the requested LIBQUE from this new dialog. Refer to sections Generic LIBQUE Values for Downloads on page 100 and Generic LIBQUE Values for Uploads on page 104 for more information. The BIM-EDIT driver has been expanded to provide access to BIM-EDIT mail items. Refer to section BIMFTRDE - BIM-EDIT Library Driver on page 315 for more information. Page 10 New For This Release

19 New for Release 1.5 New for Release 1.4 New for Release 1.3 New 32-bit versions of the PC programs are now available for Microsoft Windows 95/98 and NT. Connections to CICS and BIM-TMAN can now be automated by use of a Logon Script. Refer to section Logon/Logoff Scripts on page 69 for more information. The security controls for access to host data has been greatly enhanced. Refer to the new section Access Security Definitions on page 221. Increased transfer rates are now possible with LU2/3270 connections when using certain emulators. Refer to field Struct. Fields on page 46 for more information. A new Automatic Transfer script command #START has been added. This can be used to started transactions on the host when a transfer has been completed. Refer to page 145 for more information. Two new dialogs have been added to the PC program for download processing. They are used to specify defaults for download processing options, and to override individual download processing options as each transfer is requested. Refer to Defaults Button on page 101, and Category Options Button on page 103 for more information. The method for specifying the Download Script Name on the PC has changed for most transfer categories. Refer to section Download Script Name on page 101 for more information. A new Host Initiated Automatic File Transfer feature (HOSTAFT) has been added. This allows host programs and/or applications to control when file transfers occur to and from PC s. Refer to section Host Initiated Automatic File Transfer (HOSTAFT) starting on page 157 for more information. You can now define up to four additional transaction codes in CICS or BIM- TMAN for controlling FTRM processing. Each transaction can be defined with its own security, viewing and/or updating authority. Refer to section ALT MAINT TXN CODES on page 190 for more information. VSAM Scripts have been expanded and renamed to Download Scripts. They can now be used for all downloads, not just VSAM downloads. A new host activity log has been added. Refer to the sections Viewing The Host Transfer Activity Log (FTRL) on page 249, section VSE Installation Step 5 - Define Host Activity Log File on page 20, and section MVS Installation Step 5 - Define Host Activity Log File on page 31. Support for remote VSAM dataset access in CICS has been added. Refer to the section Remote Files in CICS on page 356. Support for replacing VSAM datasets defined with the REUSE option has been added. Refer to the EMPTY driver data option on page 359. New For This Release Page 11

20 Migration Requirements Changes from Release 1.6 Changes from Release 1.5 Changes from Release 1.4 Changes from Release 1.3 The following sections cover the changes in the installation and use of BIM-PC/TRANSFER that may be required if you are migrating from an earlier release. If you plan on using the new SAM and/or BIM-EPIC dataset support, the new Driver (BIMFTRDF) and BIM-EPIC interface module (BIMEPACC) must be added to the CICS PPT or RDO as described in the Installation Section. No installation changes required for this release unless you want to make use of one or more of the new features that have been added. The new Drivers (BIMFTRDC and BIMFTRDM) must be added to the CICS PPT or RDO as described in the Installation Section. If you plan on using the new TCP/IP interface, you will need to add definitions for programs BIMFTRI2 and BIMFTRIP and transactions FTRI and FTRP as described in the Installation Section. There is also a new installation step VSE Installation Step 9 - Activating the TCP/IP Interface described on page 24. No installation changes required. You may want to make use of the new security controls for access to host data. Refer to the new section Access Security Definitions on page 221. Two new dialogs have been added to the PC program for download processing. They are used to specify defaults for download processing options, and to override individual download processing options as each transfer is requested. Refer to Defaults Button on page 101, and Category Options Button on page 103 for more information. The method for specifying the Download Script Name on the PC has changed for most transfer categories. Refer to section Download Script Name on page 101 for more information. A new module (BIMFTRHC) must be added to your CICS definitions. It is required for HOSTAFT processing. Refer to the section VSE Installation Step 6 - CICS/VS Table Additions on page 21 and section MVS Installation Step 6 - CICS/VS Table Additions on page 32. Page 12 Migration Requirements

21 Changes from Release 1.2 Changes from Release 1.1 If you will be using the new HOSTAFT feature, you may need to increase the size of your BIM-PC/TRANSFER Host Control File. Additional records are added and maintained on the control file for each HOSTAFT Script that is activated for processing. VSAM Scripts have been expanded and renamed to Download Scripts. They can now be used for all downloads, not just VSAM downloads. A new module (BIMFTRSM) must be added to your CICS definitions. It is required for VSAM transfers. Refer to the section VSE Installation Step 6 - CICS/VS Table Additions on page 21 and section MVS Installation Step 6 - CICS/VS Table Additions on page 32. A new host activity log has been added. Refer to the sections Viewing The Host Transfer Activity Log (FTRL) on page 249, section VSE Installation Step 5 - Define Host Activity Log File on page 20, and section MVS Installation Step 5 - Define Host Activity Log File on page 31. This new feature also requires a new CICS transaction (FTRL) and two new programs (BIMFTRL and BIMFTRLD). Refer to the section VSE Installation Step 6 - CICS/VS Table Additions on page 21 and section MVS Installation Step 6 - CICS/VS Table Additions on page 32. (VSE Only) You must migrate the host software for BIM-PC/TRANSFER to release 1.2 before installing the 1.2 release on your PCs. If you are using BIM-TMAN on the host, you must migrate to BIM-TMAN release 2.0C or above prior to installing this release of BIM-PC/TRANSFER. The format of the BIM-PC/TRANSFER control file on the host has changed. Refer to VSE Installation Step 4 - Define the Host Control File on page 19 for the new IDCAMS define parameters. A conversion program has been provided to convert your existing control file to the new format. To convert your existing file, perform the following steps: 1) Define a new control file using the IDCAMS step from Installation Step 4. Do not run the initialize program BIMFTRFI shown as step 2 of that job. 2) Run the following conversion Job, changing the DLBL names as required: // JOB CONVERT // DLBL BIMFTRI,'BIMPCTFR.R11.CONTROL.FILE',,VSAM <== old file // DLBL BIMFTRF,'BIMPCTFR.R12.CONTROL.FILE',,VSAM <== new file // LIBDEF PHASE,SEARCH=lib.sublib // EXEC BIMFTRFC,SIZE=AUTO /& A new host module (BIML62CI) has been added. It is used for the APPC interface. Refer to VSE Installation Step 6 - CICS/VS Table Additions on page 21 for the CICS definition required for this new module. Migration Requirements Page 13

22 System Requirements BIM-PC/TRANSFER was developed and tested on systems using: VSE/ESA Releases 2.1, 2.1.2, 2.2 and 2.3 MVS/ESA 5.2, OS/390 Release 2.4 CICS/VSE Releases 2.2, 2.3 CICS/MVS Releases 2.1.2, 3.1, 3.3, 4.1 BIM-TMAN Release 2.0F BIM-EDIT Releases 5.0A-C, 5.1A-B, 5.2A-B Microsoft Windows 3.1, 3.11, Windows 95/98, Windows NT 4.0 OS/2 Warp 3.0 BIM-PC/TRANSFER should function on CICS/VSE releases 1.7 and above, and most recent releases of VSE, MVS/XA and MVS/ESA. The IND$ interface of BIM-PC/TRANSFER will only function on CICS/VSE 2.2 and above. It also requires a 3270 connection. It will not function with an APPC connection. The BIM-EDIT interface of BIM-PC/TRANSFER requires that the host system be running release 5.0A or above of BIM-EDIT. The BIM-EPIC managed dataset support requires BIM-EPIC release 6.1B at PTF level EP61B041 or above. Four versions of the PC program are provided: 1) a 32-bit version for Microsoft Windows 95/98 or NT 2) a 16-bit version for Microsoft Windows 3.1 3) a 32-bit version for OS/2 4) a 16-bit version for MS-DOS or PC-DOS. This requires a 286 or better PC, a VGA compatible monitor, and at least 2 MB of memory. The 16-bit Windows 3.1 version can be run in Windows 95/98 and/or NT as long as you are using a 3270 or APPC emulator that provides a 16-bit HLLAPI interface. The 32-bit Windows 95/98/NT version requires a 3270 or APPC emulator that provides a 32-bit HLLAPI interface. Supported LU2/3270 Interfaces: The following PC 3270 emulators have been tested with the 32-bit Windows 95/98/NT version of BIM-PC/TRANSFER: Page 14 System Requirements

23 Attachmate Personal Client RUMBA 95/NT for the Mainframe IBM Personal Communications AS/400 and 3270 NS/Elite Plus The following PC 3270 emulators have been tested with the 16-bit Windows version of BIM-PC/TRANSFER: Attachmate Personal Client EXTRA! for Windows IRMA Workstation for Windows NS/3270 FORVUS Emulator for Windows IBM PC/3270 TLINKW from Xener Corporation RUMBA Memorex 1472/PC for Windows Passport DynaComm/Elite The following PC 3270 emulators have been tested with the OS/2 version of BIM-PC/TRANSFER: Communications Manager/2 from IBM IBM Personal Communications AS/400 and 3270 The following PC 3270 emulators have been tested with the DOS version of BIM-PC/TRANSFER: MultiCom 3270/CUT IBM PC/3270 TLINK from Xener Corporation Attachmate Extra! IRMA Workstation for DOS Banyon Vines Other 3270 emulators may also work as long as they support the HLLAPI application interface as documented by IBM. Supported APPC Interfaces: The following APPC interfaces have been tested with the 32-bit Windows 95/98/NT version of BIM-PC/TRANSFER: Attachmate Personal Client RUMBA 95/NT for the Mainframe IBM Personal Communications PC/3270 The following APPC interfaces have been tested with the 16-bit Windows version of BIM-PC/TRANSFER: IRMA Workstation for Windows RUMBA APPC Client DynaComm/Elite IBM Personal Communications PC/3270 The following APPC interfaces have been tested with the OS/2 version of BIM-PC/TRANSFER: System Requirements Page 15

24 Communications Manager/2 from IBM All of the above APPC interfaces have been tested using a token-ring connection to the host. Attachmate Personal Client and IRMA Workstation for Windows have also been tested with a DFT connection to the host. Supported TCP/IP Interfaces: This release of BIM-PC/TRANSFER only supports a TCP/IP connection to a VSE host running TCP/IP for VSE from Connectivity Systems. Other interfaces may be added in future releases. Page 16 System Requirements

25 Installation for a VSE Host Load/object Library BIM-PC/TRANSFER/VSE is shipped on an unlabeled tape or cartridge containing one card-image file. When this tape is loaded into your RDR Queue, there will be one POWER job which will catalog the following modules to your libraries: BIMFTR99 BIMFTRBC BIMFTRCM BIMFTRD$ BIMFTRDC BIMFTRDE BIMFTRDF BIMFTRDI BIMFTRDL BIMFTRDM BIMFTRDP BIMFTRDR BIMFTRDT BIMFTRDV BIMFTRDX BIMFTRFC BIMFTRFI BIMFTRFT BIMFTRHC BIMFTRI1 BIMFTRI2 BIMFTRIP BIMFTRL BIMFTRLB BIMFTRLD BIMFTRM BIMFTROD BIMFTRPR BIMFTRSM BIMFTRTT BIMFTRXP BIML62CI BIMXMC00 BIMXPC00 BIUAPMD BIULUMD FTRT common subroutine Batch command interface for HOSTAFT FTRT command processing FTRT driver for IND$ access FTRT driver for VSAM Cluster access FTRT driver for BIM-EDIT access FTRT driver for SAM and BIM-EPIC dataset access FTRT driver for ICCF access FTRT driver for VSE Library (LIBR) access FTRT driver for CICS Temporary Storage FTRT driver for POWER access FTRT driver for VSE Library access via BIM-EDIT FTRT driver for CICS Transient Data uploads FTRT driver for VSAM dataset access FTRT driver for script dataset access Control file conversion from release 1.1 format Control file initialization Host customization HOSTAFT application/command interface FTRT input processing FTRI input processing for TCP/IP TCP/IP started task Activity log display mapset LIBR server Activity log display Customization program mapset FTRT output processing Activity log print program Service module for VSAM dataset access EBCIDIC/ASCII translate table FTRT script processing APPC interface program Host module used by LIBR interface Host module used by POWER XPCC interface Host module used by BIM-EDIT interface Host module used by BIM-EDIT LU 6.2 interface Installation for VSE Page 17

26 BIMFTRPW.OBJ Source Library BIMFTRDS.E BIMFTRFX.A BIMFTRHC.A BIMFTRHC.C BIMFTRSX.A BIMFTRJ1.A BIMFTRJ2.A BIMFTRJ3.A BIMFTRS1.A Password encode/decode for exit programs Customization macro for exit programs Sample formatting/selection exit HOSTAFT application COMMAREA for Assembler HOSTAFT application COMMAREA for COBOL Sample security exit Job to define/initialize the host control file BIMFTRF Job to define/initialize the host activity log BIMFTRL Job to define the required CICS RDO entries Sample CICS FCT entries VSE Installation Step 1 - Load Distribution Tape Mount the distribution tape on a tape drive and enter the following POWER/VSE command on the console: S RDR,cuu where cuu is the address of the tape drive. VSE Installation Step 2 - Release Install Job Alter the POWER job (BIMPCTFR) that was loaded in the RDR Queue to run in a partition that has labels established for link editing. A RDR,BIMPCTFR,DISP=D,CLASS=? VSE Installation Step 3 - Supply LIBDEF When job BIMPCTFR starts up, it will pause allowing you to enter a // SETPARM statement for the library.sublibrary that you want to contain BIM-PC/TRANSFER. * // SETPARM SUBLIB='LIB?.SUBLIB?' * // PAUSE ENTER ABOVE SETPARM AS REQUIRED When the installation job is complete, review the printed output for errors. Common problems that may occur during the installation job are: Your library is full. The SETPARM statement was omitted or improperly declared. Install job was run in a partition not set up for Link Editing. Page 18 Installation for VSE

27 VSE Installation Step 4 - Define the Host Control File The Host side of BIM-PC/TRANSFER requires a VSAM KSDS control file that is used to define the types of transfers that are allowed, and optionally, who can perform them. This control file is not used to store the actual data being transferred, therefore, the amount of space required for the file will be minimal. The RECORDS ( ) should work fine for most installations, unless you have a large number of users you will be defining, or will be using the HOSTAFT feature extensively. Define and initialize the control file using the following jobstream. This jobstream is provided in source member BIMFTRJ1.A: // JOB INIT * STEP 1 - DEFINE CONTROL FILE // EXEC IDCAMS DEFINE CLUSTER ( - NAME(BIMPCTFR.CONTROL.FILE) - RECORDS( ) - KEYS(64 0) - NOREUSE - FREESPACE(15 10) - RECORDSIZE( ) - SHAREOPTIONS(4) - SPEED - VOLUMES(vvvvvv) - ) - DATA ( - NAME(BIMPCTFR.CONTROL.FILE.DATA) - CISZ(8192) - ) - INDEX ( - NAME(BIMPCTFR.CONTROL.FILE.INDEX) - ) /* * STEP 2 - INITIALIZE CONTROL FILE // DLBL BIMFTRF,'BIMPCTFR.CONTROL.FILE',,VSAM // LIBDEF PHASE,SEARCH=lib.sublib // EXEC BIMFTRFI,SIZE=AUTO INITIALIZE CONTROLFILE /& The initialization program in step 2 (BIMFTRFI) will define a CATEGORY record for the most commonly used drivers. This will allow you to begin using BIM- PC/TRANSFER without performing much, if any, on-line customization. Remember to add the following DLBL to your CICS or BIM-TMAN startup JCL: // DLBL BIMFTRF,'BIMPCTFR.CONTROL.FILE',,VSAM Installation for VSE Page 19

28 VSE Installation Step 5 - Define Host Activity Log File The Host side of BIM-PC/TRANSFER can optionally maintain a transfer activity log. This log requires a VSAM RRDS file. Define and initialize the activity log file using the following jobstream. This jobstream is provided in source member BIMFTRJ2.A: // JOB INIT * STEP 1 - DEFINE ACTIVITY LOG FILE // EXEC IDCAMS DEFINE CLUSTER ( - NAME(BIMPCTFR.LOG.FILE) - RECORDS(100) - NOREUSE - NUMBERED - RECORDSIZE( ) - SPEED - VOLUMES(vvvvvv) - ) - DATA ( - NAME(BIMPCTFR.LOG.FILE.DATA) - CISZ(4096) - ) /* * STEP 2 - INITIALIZE ACTIVITY LOG FILE // DLBL BIMFTRL,'BIMPCTFR.LOG.FILE',,VSAM // LIBDEF PHASE,SEARCH=lib.sublib // EXEC BIMFTRFI,SIZE=AUTO INITIALIZE LOGFILE /& The initialization program in step 2 (BIMFTRFI) will format the log file. Each transfer requires two log records. One when the transfer starts, and one when it completes. Specify the RECORDS operand with the number of events that you want to maintain in the log file. The log file is a wrap-around file. Once the file is filled, the oldest records in the file are overwritten. You can increase the size of the log file by defining a new, larger file, copying the existing log file to the new file using an IDCAMs REPRO, and executing step 2 of the above jobstream to re-initialize the new file. The initialize step will detect that it is an existing file, and update the control record to account for the expanded size. Remember to add the following DLBL to your CICS or BIM-TMAN startup JCL: // DLBL BIMFTRL,'BIMPCTFR.LOG.FILE',,VSAM Page 20 Installation for VSE

29 VSE Installation Step 6 - CICS/VS Table Additions The following entries are required in the CICS that will be used for the Host side of BIM-PC/TRANSFER. Omit this step if you will be using BIM-TMAN instead of CICS. DFHPCT TYPE=ENTRY,TRANSID=FTRT,PROGRAM=BIMFTRI1, X (note 1) SCRNSZE=ALTERNATE,TWASIZE=256 (note 3) DFHPCT TYPE=ENTRY,TRANSID=FTRM,PROGRAM=BIMFTRFT, X (note 4) SCRNSZE=ALTERNATE DFHPCT TYPE=ENTRY,TRANSID=FTRL,PROGRAM=BIMFTRLD, X SCRNSZE=ALTERNATE DFHPCT TYPE=ENTRY,TRANSID=FTRI,PROGRAM=BIMFTRI2 (note 5) DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRI1 DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRI2 (note 5) DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRIP (note 5) DFHPPT TYPE=ENTRY,PROGRAM=BIMFTROD DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRCM DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRFT DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRL DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRLD DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRM DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRD$ DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDC DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDE DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDF DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDI DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDL DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDM DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDP DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDT DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDR DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDV DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRDX DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRHC DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRSM (note 2) DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRXP DFHPPT TYPE=ENTRY,PROGRAM=BIMFTRTT DFHPPT TYPE=ENTRY,PROGRAM=BIMFTR99 DFHPPT TYPE=ENTRY,PROGRAM=BIML62CI DFHPPT TYPE=ENTRY,PROGRAM=BIMEPACC (note 6) Installation for VSE Page 21

30 If you are using RDO, make the following definitions. A jobstream to perform this is provided in source member BIMFTRJ3.A: CEDA DEFINE GROUP(FTR) PROF(FTRALT) SCRNSIZE(ALT) UCTRAN(No) CEDA DEFINE GROUP(FTR) PROG(BIMFTRCM) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRD$) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDC) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDE) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDF) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDI) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDL) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDM) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDP) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDT) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDR) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDV) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRDX) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRFT) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRHC) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRI1) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRI2) LANG(A) (note 5) CEDA DEFINE GROUP(FTR) PROG(BIMFTRIP) LANG(A) (note 5) CEDA DEFINE GROUP(FTR) PROG(BIMFTRL) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRLD) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRM) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTROD) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRTT) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTRSM) LANG(A) (note 2) CEDA DEFINE GROUP(FTR) PROG(BIMFTRXP) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMFTR99) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIML62CI) LANG(A) CEDA DEFINE GROUP(FTR) PROG(BIMEPACC) LANG(A) (note 6) CEDA DEFINE GROUP(FTR) TRAN(FTRL) PROG(BIMFTRLD) PROF(FTRALT) CEDA DEFINE GROUP(FTR) TRAN(FTRM) PROG(BIMFTRFT) PROF(FTRALT) (note 4) CEDA DEFINE GROUP(FTR) TRAN(FTRT) PROG(BIMFTRI1) PROF(FTRALT) (note 1) TWASIZE(256) (note 3) CEDA DEFINE GROUP(FTR) TRAN(FTRI) PROG(BIMFTRI2) PROF(FTRALT) (note 5) CEDA DEFINE GROUP(FTR) TRAN(FTRP) PROG(BIMFTRIP) PROF(FTRALT) (note 5) Note 1: Note 2: Note 3: Note 4: Note 5: Note 6: If you change the transaction id FTRT to some other value, you must also change the PC programs INI files (BIMFTR.INI and BIMAFT.INI). Find the line in each INI that reads: TRANSACTION FTRT, and change the FTRT to the new value you have selected. If you want to access a VSAM dataset in a remote CICS system, you must define a program/ppt entry for module BIMFTRSM in the CICS system that owns the dataset. The TWASIZE operand is only required if you intend to use the VSE Host Transfer (IND$) interface. You can define up to 4 alternate transactions for use in viewing and customizing the Host Control File. Refer to ALT MAINT TXN CODES on page 190 for more information. The entries for FTRI, FTRP, BIMFTRI2 and BIMFTRIP are only required if you plan to use TCP/IP connections. The entry for BIMEPACC is only required if you plan to transfer BIM-EPIC managed datasets using driver BIMFTRDF. This module is shipped with the BIM-EPIC product. Page 22 Installation for VSE

31 Add the following FCT entry for the BIM-PC/TRANSFER Control File. This is provided in source member BIMFTRS1.A: DFHFCT TYPE=DATASET,DATASET=BIMFTRF - ACCMETH=(VSAM,KSDS,KEY), - RECFORM=(VARIABLE,BLOCKED), - SERVREQ=(READ,UPDATE,ADD,DELETE,BROWSE), - STRNO=2,BUFNI=2,BUFND=3,LSRPOOL=NONE, - FILSTAT=(ENABLED,OPEN) If you will be using the Host Activity Log of BIM-PC/TRANFSER, add the following FCT entry. This is provided in source member BIMFTRS1.A: DFHFCT TYPE=DATASET,DATASET=BIMFTRL - ACCMETH=(VSAM), - RECFORM=(FIXED,BLOCKED), - SERVREQ=(READ,UPDATE,ADD,DELETE,BROWSE), - STRNO=2,BUFND=3,LSRPOOL=NONE, - FILSTAT=(ENABLED,OPEN) BIM-PC/TRANSFER contains a feature that allows VSAM datasets to be transferred to and from PC s by specifying their cluster name. This feature requires one or more generic FCT entries that BIM-PC/TRANSFER will temporarily use during the actual transfers. Refer to section Cluster Name Transfer Feature on page 203 to determine if you will need these FCT entries. Sample FCT entries for this feature are included in source member BIMFTRS1.A. VSE Installation Step 7 - BIM-TMAN Setup Skip this step if you will not be using BIM-TMAN for the host side of BIM- PC/TRANSFER. Add the following definitions to your BIM-TMAN DEFINE command: FILE(BIMFTRF,U,3,KS) - FILE(BIMFTRL,U,3,RR) - TRAN(FTRT,BIMFTRI1,'PC/TRANSFER INITIATE',DISP,1) - TRAN(FTRL,BIMFTRLD,'PC/TRANSFER ACTIVITY LOG',DISP,1) - TRAN(FTRM,BIMFTRFT,'PC/TRANSFER MAINTENANCE',DISP,1) - TRAN(FTRI,BIMFTRI2,'PC/TRANSFER TCP/IP TRAN',DISP,1) - TRAN(FTRP,BIMFTRIP,'PC/TRANSFER TCP/IP INIT',DISP,1) - Refer to the BIM-TMAN documentation for details of these operands. Unlike CICS, BIM-TMAN does not require programs to be predefined to it such as CICS PPT entries. You can ignore any reference in this manual to program definitions if you are only using BIM-TMAN. The entries for FTRI and FTRP are only required if you will be using TCP/IP connections between your PCs and the host. Installation for VSE Page 23

32 You can define up to 4 alternate maintenance transactions in addition to FTRM, for use in viewing and customizing the Host Control File. Refer to ALT MAINT TXN CODES on page 190 for more information. Except for the FILE operands for BIMFTRF and BIMFTRL shown above, you will only need to provide additional FILE operands for the following types of VSAM datasets: 1) Datasets defined in VSAM profiles that you need to upload into. You do not need FILE operands for datasets transferred using the Cluster Name Transfer Feature described on page ) Datasets that require more than 3 strings for concurrent download access. The FILE operand has the following format: FILE(name,access,strno,type) where: name DLBL name of the VSAM dataset access dataset access type I = input only (default) U = update L = load mode strno VSAM number of strings (default is 3) type VSAM cluster type KS = Keyed Sequence ES = Entry Sequence RR = Relative Record BIM-TMAN also requires that DLBLs be present for all VSAM datasets to be accessed, and that all programs be available in LIBDEF search chains. VSE Installation Step 8 - Customization VSE Installation Step 4 - Define the Host Control File created several CATEGORY definitions for your initial use. These default definitions will allow most installations to begin using BIM-PC/TRANSFER immediately. To review these definitions, bring up the CICS or BIM-TMAN system containing the above definitions, and use the FTRM transaction. CATEGORY definitions are used to define which transfers are allowed using BIM-PC/TRANSFER. Refer to the section Host Customization using the FTRM Transaction on page 184 for more information. VSE Installation Step 9 - Activating the TCP/IP Interface Skip this step if you will not be using TCP/IP connections between the host and your PCs. Page 24 Installation for VSE

33 Before performing this step, review section TCP/IP Connection Options on page 248. If you are running BIM-PC/TRANSFER in CICS, add the following entry to your CICS startup and shutdown PLTs: DFHPLT TYPE=ENTRY,PROGRAM=BIMFTRIP If you are running BIM-PC/TRANSFER in BIM-TMAN, add the following operand to the BIM-TMAN DEFINE command in your startup JCL: STARTUP(FTRP) - The value specified for FTRP must match the tranid defined for program BIMFTRIP. VSE Installation Step 10 - PC Program Installation Install the PC program on the PCs that will be transferring data. You may have several diskettes depending on which versions of the PC software you have ordered. The section Connecting the PC to the Host on page 39 contains information for activating the LU2 and/or APPC connections between the PC and the host. VSE Installation Step 10a - Microsoft Windows 95/98 or NT 4.x Insert the installation diskette containing the Windows 95/98/NT version of BIM-PC/TRANSFER in a drive on your PC. Click the Start button, and select the Run entry. Enter the following command in the RUN dialog box: A:SETUP.EXE where A: is the diskette drive containing the BIM-PC/TRANSFER PC installation diskette. VSE Installation Step 10b - Microsoft Windows 3.1, 3.11, and NT Insert the installation diskette containing the Windows or Windows NT version of BIM-PC/TRANSFER in a drive on your PC. Select Run from the Program Managers File menu and enter the following command in the RUN dialog box: A:SETUP.EXE where A: is the diskette drive containing the BIM-PC/TRANSFER PC installation diskette. Installation for VSE Page 25